Hi
I have a module connect ME 9210 without JTAG and I cleaned the memory flash with comand NAFlashErase and now I can’t comunicate with it, I don’t know what addres, and it dont write on the serial. The orange light is on and yellow light is off.
Help me how can I save the firmware in this module?
By “save the firmware” you mean “save the module from being bricked” correct?
Read this thread Restore ME Module .
Follow the attachment JTAGless module recovery.
I already tried put the pin INIT and MFGI to ground, but the module dont sent anything for the serial. This metodo I was used for recovery other modules, but in this module don’t function. Do you know other methods for recovery this module?
Thanks
André Lessa.
If you erased the entire flash, then you also erased the recovery code, in which case your module is probably bricked.
If you haven’t erased the bootstrap (like da worm mentions) you should know that I have never gotten the serial interface to work on recovery either (not sice the original ME module). Use the TFTP recovery. BTW, if you need a DHCP with the codes mentioned, the standard Linux and Windows ones will work. Remember to disable DHCP on your firewall.
I’ve recovered many regular ConnectME -C modules with the serial recovery method. It’s dog slow, but for one or two modules its faster than remembering how to set up the TFTPD32 to make it work. I’ve never used a 9120 though, so I don’t know if it works there.
I made a download of a TFTP server and DHCP server, but I don’t Know how configure there. Do you have one tftp server and DHCP server that you used? And if You has, Do you has a tutorial that explains how I can configure there?
Thanks
I use TFTPD32 with pretty much the following INI file.
[DHCP]
Lease_NumLeases=0
IP_Pool=50440384
PoolSize=0
BootFile=image.bin
DNS=16885952
Mask=16777215
Gateway=16885952
DomainName=
Lease (minutes)=2880
00:40:9d:38:c7:95=192.168.1.2
AddOptionNumber1=66
AddOptionValue1=192.168.1.1
AddOptionNumber2=67
AddOptionValue2=image.bin
AddOptionNumber3=0
AddOptionValue3=
AddOptionNumber4=0
AddOptionValue4=
AddOptionNumber5=0
AddOptionValue5=
AddOptionNumber6=0
AddOptionValue6=
AddOptionNumber7=0
AddOptionValue7=
AddOptionNumber8=0
AddOptionValue8=
AddOptionNumber9=0
AddOptionValue9=
AddOptionNumber10=0
AddOptionValue10=
[TFTPD32]
BaseDirectory=.
TftpPort=69
Hide=0
WinSize=0
Negociate=1
PXECompatibility=0
DirText=1
ShowProgressBar=1
Timeout=3
MaxRetransmit=6
SecurityLevel=0
UnixStrings=1
Beep=0
VirtualRoot=1
MD5=0
LocalIP=192.168.1.1
Services=5
TftpLogFile=
SaveSyslogFile=syslog.txt
PipeSyslogMsg=0
LowestUDPPort=0
HighestUDPPort=0
MulticastPort=0
MulticastAddress=
PersistantLeases=1
DHCP Ping=0
DHCP LocalIP=192.168.1.1
Max Simultaneous Transfers=100
UseEventLog=0
Console Password=tftpd32
Support for port Option=0
Keep transfer Gui=5
Ignore ack for last TFTP packet=0
I set my PC’s IP address to a fixed 192.168.1.1 (actually, I have a second NIC in my PC with that address) and connect to the Digi via a hub. I’m not using automatic IP addresses, instead I modify the MAC address above to match the Digi I’m working on. This lets me keep other devices on the same network without them re-flashing themselves every time they cycle power.
Hope this helps.
Jeff.
Try Jeff Da Worm’s config. It is all in one, so is simpler.
What I use is SolarWind’s TFTP server, then I configured Windows Server 2008’s DHCP with the IP of the machine with the TFTP server and the filename to retrieve. Go to the DHCP policy screen and do “Add Policy” to add the policies 66 and 69. I leave this running so all I have to do is hook a bad ME to the network and it fixes itself.
Also, like I said, disable your router’s DHCP so it doesn’t conflict.
-Erik