[SilverDesertRain]

I have a DSL 302T modem which was giving me trouble (Getting disconnected very frequently) so I updated it with 300T firmware but the same problem. I learned a lot from the Italian forums using Systran (I don't speak or understand Italian...sorry) I then updated it to 500T with the GT701-WG-Recovery tool. I then wanted to experiment so I updated it to 502T then tried something else but in the end by modem died. It will not connect to the ethernet...only the power led is on.
Anyway I bought a brand new DSL 302T modem and updated it with the latest Russian Firmware for 300T. Then I wanted to change it to 502 T or 500T but I couldn't do it. My modem is dead now but it connect to the ethernet port and I can communicate with it through Telnet but it won't start.
I have tried everything that I know but it wouldn't start. Maybe the new modem is protected because the flash will not erase. The IP of the Modem for some reason is 10.8.8.10 and not 10.8.8.8. or 192.168.0.1 etc
I have gone again into the forums and found a tool called CICLaMaB. The version 1.9.96 works for me but the version 2.0.1 does not...maybe because of the modem IP 10.8.8.10
With the version 1.9.96 I get the following.

CICLaMaB ver. 1.9.96
modem/router info:
bootloaderVersion 0.22.02
flashsize 0x00200000
usb_prod N/A
mtd0 0x900a0000,0x901f0000
mtd1 0x90010000,0x900a0000
mtd2 0x90000000,0x90010000
mtd3 0x901f0000,0x90200000
RETR env
226 Transfer complete.
RETR env
226 Transfer complete.
Parametri impostati:
- Autoload on
- Partizionamento mtd0 e mtd1 per D-Link DSL-300/2T


---------------------------------------------------------------
SETENV autoload,1
200 SETENV command successful
SETENV mtd0,0x900a0000,0x901f0000
200 SETENV command successful
SETENV mtd1,0x90010000,0x900a0000
200 SETENV command successful
SETENV mtd3,0x901f0000,0x90200000
200 SETENV command successful
TYPE I
200 Type set to I.
PASV
227 Entering Passive Mode (192,168,1,1,189,153).
RETR config.xml
150 Opening BINARY mode data connection for file transfer.
226 Transfer complete.
TYPE I
200 Type set to I.
PASV
227 Entering Passive Mode (192,168,1,1,189,153).
RETR env
150 Opening BINARY mode data connection for file transfer.
226 Transfer complete.
MEDIA FLSH
200 Media set to FLSH.
TYPE I
200 Type set to I.
PASV
227 Entering Passive Mode (192,168,1,1,189,153).
STOR filesystem mtd0
Cancellazione partizione mtd0. Attendere...
550 Flash erase failed.
Il comando č fallito: STOR filesystem mtd0
TYPE I
200 Type set to I.
PASV
227 Entering Passive Mode (192,168,1,1,189,153).
STOR kernel mtd1
Cancellazione partizione mtd1. Attendere...

I just don't know what to do...maybe if I could change the IP address of the modem from 10.8.8.10 to either 192.168.0.1 or 10.8.8.8 will make things work. I don't know much about Linux...only a windows XP user.


Please if anyone can help me then I will be very thankful.
Thanks in advance.

[marven]

The IP address wouldn't matter. Anyway you could change it as follows:

At the windows command prompt write the following command:
ftp 10.8.8.10 (don't push enter)
switch off the modem then switch it on and count till 2 or 3 then promptly
push enter
you must see the ADAM2 ftp server login screen
enter "adam2" (without quotes) as login and password, then enter the following commands:

bin
quote MEDIA FLSH
quote SETENV my_ipaddress,10.8.8.8
quote REBOOT

Try again with CICLaMaB: choose 302t partitioning. Don't chose any other partitioning scheme for any reason! That could be very dangerous!

Be careful with firmwares! Don't upload 500t or 502t firmwares on 302t, you could kill your modem; 302t has a 2 MB flashrom, 500t and 502t have a 4 MB flashrom instead.

If you couldn't revive the modem, ftp to ADAM2 again as mentioned above and enter the following commands:

bin
quote MEDIA FLSH
get env

that will download the "env" file on your PC in the command prompt folder, tipically something as
c:\documents and settings\username

Please post the env file content, it could be useful for debugging. Also post the firmware filenames you are using.

[SilverDesertRain]

Thanks for your kind reply

I tried the FTP change IP thing...everything was done but after the reboot the modem's IP was still 10.8.8.10

I tried the CICLaMaB but I get the same problem...I have put my IP settings as follows
IP address: 192.168.1.2
Subset mask: 255.255.255.0
Default gateway: 192.168.1.1
This is my ENV file...please note that the modem is 302T which I had updated it with the 300T Russian firmware when it was working.


memsize               0x00800000
flashsize             0x00200000
modetty0              38400,n,8,1,hw
modetty1              38400,n,8,1,hw
bootserport           tty0
cpufrequency          150000000
sysfrequency          125000000
bootloaderVersion     0.22.02
ProductID             AR7DB
HWRevision            Unknown
SerialNumber          none
my_ipaddress          10.8.8.10
maca                  00:0F:3D:8A:9E:D6
prompt                Adam2_AR7DB
firstfreeaddress      0x9401d328
req_fullrate_freq     125000000
mtd0                  0x900a0000,0x901f0000
mtd1                  0x90010000,0x900a0000
mtd2                  0x90000000,0x90010000
mtd3                  0x901f0000,0x90200000
autoload              1
usb_vid               0x0
usb_pid               0x0
usb_man               N/A
usb_prod              N/A
usb_serial            00:0F:3D:8A:9E:D7
usb_board_mac         00:0F:3D:8A:9E:D7
usb_rndis_mac         00:0F:3D:8A:9E:D8
crash                

In my old modem I had upgraded the modem into 500T and 502T with 300t 302t 30xt@500t_by_ArTiKO versione FORZA C and 302T_to_502T_recovery_tool (nsp.ar7wrd.squashfs.img & ram_zimage_pad.ar7wrd.nsp.squashfs) but this was done with the GT701-WG-Recovery tool and not CICLaMaB.

This new modem will not work with GT701-WG-Recovery tool for some reason.

As for the firmwares I have the following:



1- 300t 302t 30xt@500t_by_ArTiKO versione FORZA C

2- 302T_to_502T_recovery_tool by Zwanky

dsl30xt_to_500t_20050715_066test1_adsl2_firmware (This one killed by last modem !!!...now it is not connecting to the computer...the Ethernet port doesn't detect it !)

3- dsl300Tto500T_241204_03rc3_firmware

4- DSL-300T_FW_v1.00B02T02.UK.20040618

5- DSL-300T_V1.00B02T02.RU.20050422

6- DSL-302T_EU

7- DSL-500T.V1.00B02T02.RU.20050223

8- DSL-502T_FW_v1.00B02T02.UK.20040611

Please help me...I just can't figure it out my myself. I have read most of the forum discussions but there isn't a solution there.
Is there a way to fix the old dead modem ? Or should I throw it in the trash....

Thanks for your time and help....  

[marven]

dsl30xt_to_500t_20050715_066test1_adsl2_firmware (This one killed by last modem !!!...now it is not connecting to the computer...the Ethernet port doesn't detect it !)

Unfortunately you are not alone...  
That firmware is bugged, all few forum's users that tried it they killed their modem, but for what I know they revived it in a way or another...

The first thing to do is to discover if adam2 is still alive...

If you used the tiupgrade utility inside the package, probably the adam2 address is changed to 192.168.1.1... try that IP

For the other modem, in the env file everything seems OK... maybe also the mtd3 partition has some recording problem.

Try
1) Put the following network settings and try again with Ciclamab

IP address: 10.8.8.11
Subnet mask: 255.255.255.0
Default gateway: 10.8.8.10

2) a hardware reset

3) Have a config.xml file (it doesn't matter which), connect again to adam2  and send the following commands (it causes an mtd3 reset in the config space only, hopefully that stress could "awake" the recording function of the env part of mtd3):

bin
quote MEDIA FLSH
put config.xml "config.xml mtd3"
quote REBOOT

Let me know if you can get a shell prompt via telnet, it could be usefull for other tries.

About the firmwares, the most appropriate for the 302t is the Zwanky-Danyduck version:
http://digilander.libero.it/danyduck/fs_zwanky-danyduck.img
which is the Zwanky fw + integrated emule fix script.
As for the Zwanky fylesystem the kernel must be the original 302t one.

[SilverDesertRain]

Thanks again for your kind help...  

As for the old modem...well it is completely dead becuase the computer doesn't recognize it (A network cable is unplugged), all you get is the power status lead on.
Even if Adam2 is still alive, he is trapped in the garden of DSL-302T for the rest of the eternity... Don't know if Eve is there with him...

Now for the new modem well I tried the FTP with the config.xml but I get the same problem...modem is still dead.

I tried using the CICLaMaB ver. 1.9.96 but the same problem...the new version of the CICLaMaB doesn't seem to work with me for some reason.

As for a  shell prompt via telnet...I don't know much about telnet let alone a shell prompt...

Is it possible that the modem a new version and it protected from firmware upgrades...500T etc...?

Thanks for you time.  

[marven]

As for the old modem...well it is completely dead becuase the computer doesn't recognize it (A network cable is unplugged), all you get is the power status lead on.

In adam2 mode the power led only is on, the modem isn't dead, it's only in coma status (perhaps it's happy with Eve, we don't know!   ) so before considering it a paper holder, try again with adam2, with the recovery tool (ip address 192.168.0.99 gw 192.168.0.1 sm 255.255.255.0) and with adam2app (http://wireless.com.pt/forum/download.php?id=5459)
With adam2 and adam2app try the following Ip addresses:

169.254.87.1
192.168.0.100
10.48.88.66
192.168.178.1
10.1.1.1
5.8.8.8
10.8.8.8
192.168.1.1
192.168.0.1

put x.x.x.99 as ip address (change the xes with the proper nrs)  and 255.255.255.0 as subnet mask...

Is it possible that the modem a new version and it protected from firmware upgrades...500T etc...?

For what I know it isn't protected. I remember a similar problem was solved by a user sending the command "erase" via serial interface... I'll check the thread...
Maybe it's a problem of messing in the env variables, sometimes happens they show OK but are really wrong. If that's the case you could try to delete and rewrite them with the adam2app tool.
 

[marven]

This is the thread I mentioned before
https://www.ilpuntotecnico.com/forum/i...t=45&#entry7134
But the problem was different... adam2 was apparently dead but really it was alive and accessible via serial port, that could be a solution for the other modem...
That user says he sent the "erase" command via serial port then ftp'ed to adam2 at the address 10.8.8.8 (I dont' know if he tried 10.8.8.8 via ethernet before...)

[SilverDesertRain]

Thanks again marven,

I tried the adam2app but the old modem could not be revived because the ethernet port seems to be dead...I don't know how you can use the serial port ? There is no serial port in the modem, just USB and Ethernet. Do you connect the serial port to the USB via same adaptor ?

As for the new modem...still the same problem. The flash won't erase no matter what I try. I have tried the adam2app but when I try to send a file to the modem to the flash, the program crashes and does not repond. I can upload things from the modem like config and env.

Thanks for your patience...  

[marven]

how you can use the serial port ? There is no serial port in the modem, just USB and Ethernet. Do you connect the serial port to the USB via same adaptor ?

The serial port is inside the modem. You have to open it. Look at the Ciclamab online help, there's a schematic of the serial adapter...
Here:
http://www.seattlewireless.net/index.cgi/ADAM2
you can read a lot about adam2 and the serial commands...  

[SilverDesertRain]

Thanks again...

The link is not working I'm afraid.

So isn't there any solution for the new modem...why will the flash not be erased ?

Thanks

[marven]

Thanks again...

You are welcome!  

The link is not working I'm afraid.

I tried it just now, it's working...

So isn't there any solution for the new modem...why will the flash not be erased ?

My hypothesis are:

The worst ones:
1) The flashrom or some other hardware component is broken;
2) Adam2 is corrupt and doesn't work properly;
In these condition the serial adapter is useless... maybe an extreme hope with the serial adapter for the hypothesis 2)

The best ones:
1) The power supply adapter has some problem, try another;
2) You could solve the problem via serial adapter, perhaps with the "erase" command...
3) You could access the modem via telnet.

If you can telnet the modem ad get a shell prompt, because in this condition the flashing software is completly different from adam2, there's a last chance to flash kernel, filesystem, env partition and even adam2 in case...
At the command prompt put the following command:

telnet 192.168.1.1
then enter
root
as login
and your web configuration page password

if everything will go well you'll get a screen like this one:

BusyBox v1.00 (2005.02.14-19:59+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

I'll post you the commands to put kernel, filesystem etc.    

[SilverDesertRain]

Thanks again, Marven...you sure are good

Ok now some background history....This is the 3rd D-Link 302T that I have messed up. The first one is dead with Adam trapped inside. The second one I messed it up by trying the recovery tool to upgrade it to 500T (as I did for the first one) but it failed because it is from the same new breed as the 3rd modem. Anyway the second modem went back to the shop and they replaced me a new one, the 3rd modem (Was still under the Waranty)
Now the 3rd modem did exactly what the 2nd modem did but I still have not taken it to the shop (Still under waranty, one whole year). But the thing is that 4th modem will be the same...so I took it as a challenge to fix the 3rd modem. In the end if I fail...I'll take it back and hopefully they will replace it for a new one.
The thing is with the first one it was easily upgraded with all...telnet, FTP, Recovery tool and CICLaMaB but the new ones are avoiding upgrade...now why will this be.
I'm sure D-Link have done something to the new ones...but there is alway a way as long as a person can think.

I sure have learn a lot...thanks to kind and helpful people like yourself.

Now for the solutions....ok I still have the old power supply from the old one (It's a bit different from the new ones though). Also the old one had a USB driver version 1 while the new ones have version 2 on the installation CD.
As for the link...it works but I have to use a proxy server (blocked by my ISP for some reason)

Thanks again.

[marven]

I'm sure D-Link have done something to the new ones...

Very interesting news. I never heard it before... perhaps D-Link doesn't sell them in Italy... To say the truth D-Link doesn't sell the 302t at all in Italy, we get it from Telecom
Italia with the adsl line or from Ebay (branded Telecom Italia the same ...)
BTW, just for curiosity, may I ask where are you from? Just to also know where the 302t is directly selled by D-Link...

[marven]

Opps... forgot to say there's a very last resort in order to put your modem alive: the JTAG port. I'm hacking about it on my dead 302t...
I didn't revived my modem for the moment but I get very interesting results...
I'll put schematics and so very soon on this thread:
https://www.ilpuntotecnico.com/forum/i...p?showtopic=779
By the way I saw (via jtag) that it's possible to protect some flash rom sectors. On mine there aren't, perhaps on yours there are.

[SilverDesertRain]

Thanks Marven,

I am from a country called Oman, which is next to Dubai. Dubai is the main distributer for D-Link ADSL in the Middle East, The Gulf Region.

J-Tag sounds interesting but I am not electronic oriented...you see I am a surgeon by profession.

Thanks again.