# Problems updating EM7411 firmware with multiple modules attached by USB

**URL:** <https://forum.sierrawireless.com/t/problems-updating-em7411-firmware-with-multiple-modules-attached-by-usb/22562>\
**Category:** IoT Modules\
**Created:** [January 13, 2021, 7:25pm UTC](https://forum.sierrawireless.com/t/problems-updating-em7411-firmware-with-multiple-modules-attached-by-usb/22562 "2021-01-13T19:25:49Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![brandon.conway](https://avatars.discourse-cdn.com/v4/letter/b/df705f/32.png) [@brandon.conway](https://forum.sierrawireless.com/u/brandon.conway)\
**Post date:** [January 13, 2021, 7:25pm UTC](https://forum.sierrawireless.com/t/problems-updating-em7411-firmware-with-multiple-modules-attached-by-usb/22562/1 "2021-01-13T19:25:49Z")

</div>

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](https://source.sierrawireless.com/resources/airprime/software/fdt/#sthash.udwL7toK.dpbs)) 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](https://forum.sierrawireless.com/t/multiple-module-firmware-update/21744/7) [Multiple module firmware update - #7 by Wiviacom](https://forum.sierrawireless.com/t/multiple-module-firmware-update/21744/7) 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 …

---

<div class="post-metadata">

**Author:** ![Donald](https://avatars.discourse-cdn.com/v4/letter/d/ac8455/32.png) [@Donald](https://forum.sierrawireless.com/u/Donald)\
**Post date:** [January 14, 2021, 8:23am UTC](https://forum.sierrawireless.com/t/problems-updating-em7411-firmware-with-multiple-modules-attached-by-usb/22562/2 "2021-01-14T08:23:04Z")

</div>

Hi @brandon.conway

> [@brandon.conway](#):
>
> c:\CAT7\>fdt2.exe -f SWI9X50C\_01.14.03.00.cwe -multi -usbport 44

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.

---

<div class="post-metadata">

**Author:** ![beachmiles](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/beachmiles/32/9611_2.png) [@beachmiles](https://forum.sierrawireless.com/u/beachmiles)\
**Post date:** [September 21, 2024, 4:32am UTC](https://forum.sierrawireless.com/t/problems-updating-em7411-firmware-with-multiple-modules-attached-by-usb/22562/3 "2024-09-21T04:32:07Z")

</div>

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.