Can't load image.bin with HTTPS server on image.bin with HTTP server

Embedded Devices NET+OS
1

We have legacy Connect ME 9210 application that had standard HTTP server AWS web pages. We are updated to HTTP/HTTPS version of the same application. We cannot load the new image.bin with the HTTP/HTTPS server onto the legacy application that is just running the HTTP server? We tried both using the standard Upload Firmware WEB page and using the FTP server. Strange that the FTP server will not allow the image.bin to be copied, how would it know that the file type? We can go backwards though, meaning load the HTTP only image.bin from the HTTP/HTTPS application both through the WEB page and using FTP. We have a development/JTAG board that allows us to run either application from the debugger and load files, however we will need to update fielded units that do not have this capability.
We did a job from scratch a while back and could program the HTTP/HTTPS firmware from the factory image.
I know this is an old (but venerable) product, any suggestions?
Thanks in advance.

2

I did some Wireshark traces and I am very puzzled why one works and one does not. It happens well before any data is transferred so there is nothing I can see that allows the FTP server to inspect the file.
In the good scenario after the STOR command another port is opened and the transfer takes place over that port, while in the bad scenario after the STOR command the digi server aborts the connection before any transfer happens.

Always works: https image.bin installed => transfers http image.bin or transfers https image.bin
Never works: http image.bin installed => transfers https image.bin
Also works: http image.bin installed => transfers http image.bin

I attached PDF of trace.
FtpComparison.pdf (96.5 KB)

3

FYI, I just tried to use the serial recovery procedure by grounding MFGI (GPIO9) and INITn . I was able to XMODEM the file across and it wrote it to flash and then reset. However, it did not boot and instead remained in serial recovery. I was eventually able to reinstall the image.bin using serial recovery but not the one with the HTTPS version of image.bin. This helps as they are short supply and I’m not looking to brick any of them. Is there a way to either delete the image.bin and have it boot into rom.bin or install a factory version of image.bin?

4

Have you looked at the firmware version installed on the device to see if it is the current version? The current version can be found at Digi Connect ME 9210 NET+OS Support Resources

5

  1. I took a new module from stock and was able to program it with the HTTPS version. So it worked with the factory image.bin

  2. I went to the link you provided, and clicking in further I found a patch that only was for image sizes greater than 1280KB. The HTTP image was 860KB while the HTTPS version was 1370KB. I applied the patch and then FTP’d the HTTPS version over and IT WORKED :slightly_smiling_face: This makes sense now since it is size related, not something embedded in the image file. The link to find this patch in case someone else runs into a issue is:
    Digi Connect ME 9210 NET+OS Support Resources

Drop down NET+OS and then download
Fix for 1280KB image size limitation

  1. I’m not sure why the first image bricked it. Although that image was built in 2018, so probably the bug/fix wasn’t yet know or it was built with an older version of NET+OS. Probably enough patches were applied through package manager that it got handled in the latest build.

Thanks Eric you guys provide great support even for older products.