I have a couple of the new Connect ME CF/W JTAG devices, and I have had enough headaches trying to recover them after something happens to the image in the flash. Recently I have also received several of Connect ME S (instead of C wrong order) that I tried to change and upload the binary image file of our application (compiled on the F version of NetOS).
Whenever I try replacing the f/w from the admin html screen, I get:
Unable to update firmware: Invalid image header
I decided to replace the E firmware with B version, and got the same answer. But the B firmware has the TFTP client in the diagnostics mode, so then I jumpered pin 18 (MFGI) to GND, and did the following (ftpapp.bin is compiled under NetOS 6.0f):
[i][b]
-------------------------- TFTP Related Options --------------------------
- Show current TFTP settings. 2) Enter TFTP settings.
- Get file from TFTP server.
Enter choice (ESC to exit-TFTP Related Options)[123] :2
Enter TFTP filename [ftpapp.bin]: ftpapp.bin
Enter IP address [..84.34]:
Enter network mask [255.255.252.0]:
Enter network gateway [..84.1]:
Enter network TFTP server [..84.232]:
Enter choice (ESC to exit-TFTP Related Options)[123] :3
Working, please wait …
TFTP() returned Success: 313258 bytes
Enter choice (ESC to exit-TFTP Related Options)[123] :
---------------------------- Diagnostic Tests ----------------------------
t) ->TFTP related choices. h) ->Hardware tests.
m) Quick memory test (seconds). M) Long memory test (minutes).
V) Show VPD data. 1) Erase NVRAM from flash.
2) Erase the BOOTPARM from flash. 3) Erase the OS from flash.
4) Put TFTP’d OS file into flash. 5) Run OS.
Enter choice (ESC to exit-Diagnostic Tests)[thmMV12345] :4
Loaded Image is Invalid!
[/b][/i]
So basically, I see no way to replace the firmware on the S types so far. I can only try to return them in exchange for the custom ones. Please post if you have any ideas how to circumvent this problem.
I also want to plea for the return of the diagnostics option on C type. It was an only option to fix ME after something happened to the image. We are planning to have our technicians upload the f/w to the devices, and I know Ill soon end-up with bag full of mishaps. If Digi cannot return the diagnostics mode for all custom devices, can someone please at least show me how can I implement something similar on our devices? I think I read somewhere in these forums that Erick (egawtry) made something like the diagnostics mode, but I cannot find the article. I also dont have much time to spend hacking this device, though I want to know more about it projects have their deadlines.