Problems updating EM7411 firmware with multiple modules attached by USB

IoT Modules
1

I am trying to update the firmware of EM7411 modules in a production test environment that will have one or two EM7411 modules connected at any given time.

I am trying to use the fdt2 tool (from here) to do so. I am able to update via the fdt tool when only a single module is connected. I can use a command line like:
fdt2.exe -f SWI9X50C_01.14.05.00.cwe –multi
to update a unit. I have tried this with just a single module connected and it works.
I used the advice from this forum post Multiple module firmware update - #7 by Wiviacom to determine the -usbport value, however it simply hangs. Is the -usbhub tag a required partner tag to the -usbport? If so how do I determine the -usbhub value?

When using the command line to sepcify the USB port, is seems to hang:

c:\CAT7>fdt2.exe -f SWI9X50C_01.14.03.00.cwe -multi -usbport 44
FDT version: 1.0.1806.0
Awaiting suitable port or adapter …
Enabling selective suspend …
Firmware download failed.
Primary error code: 82 - Failed in checking modem mode.
Secondary error code: 5 - Neither NDIS adapter nor serial port is available.
Device error code: 0x0 - Unknown device error code.

Preexisting images information:
Current:
Firmware:
ImageId:
BuildId:
Configuration:
ImageId:
BuildId:
Final images information:
Current:
Firmware:
ImageId:
BuildId:
Configuration:
ImageId:
BuildId:

OEM PRI:

IMEI:

Total time elapsed: 25125 ms.

Images downloaded:

Press Enter to continue …

2

Hi @brandon.conway

Please try it with fdt2.exe -f filename.cwe -usbport44 -multi
It is OK for me.

Note: It should be -usbport44 instead of -usbport 44 (whitespace removed).

Help to tick “Solutions” if your question is answered.

1 Like
3

Are you sure about the no space between the command switch and the value? It looks like the developers making fdt2.exe in windows crossed the streams for the -usbport and -usbhub switches with like 3+ different methodologies. The cleanest looking log filename and arguments read in occur when you do add a space. Pretty sure the no space option sets the value to -1 and just picks the first device it finds to flash.

This fdt2.exe tool badly needs an update and a simple gui for production programming would be extremely helpful. Have up to 4 firmwares to built a “config” to flash and then have all the modems detected in the system show up (8+) and a flash all button. It would then ideally flash them all in parallel, or maybe do 2 or 4 at a time. Even 1 at a time would be fine.