Is there mistake in my arguments setting on the fdt2.exe console?
Similarly, if I just run one instance but specify only the usbhub argument (i.e., usbhub7 since the hub port number is 7) and removed usbport argument, only one modules gets updated while the other 2 modules are not updated.
Doing this will disconnect the module from the computer (i.e., WWAN modem under Modems disappeared in Device Manager) and set the module into QDLoader mode (which appeared as a COM port device in Device Manager). However when I tried to run the fdt2 using that QDLoader COM port number, it complained about no MBN adapter available.
That means "-d g5k -usbport13 -a -force -multi -f " is making the NO MBN problem???
It’s programming the modules in parallel that’s problematic. It doesn’t work when all instances (i.e. running 3 fdt2.exe at the same time) are run at the same time. Only one of the instances will go through and able to program successfully.
So the spk file is a combined nvu (carrier config files)/cwe (signaling firmware) file, we prefer to push spk files out because it means there is limited scope for customers to pair them incorrectly which can cause nasty side effects.
The spk files are on the source but of you have nvu/cwe files you can create an spk using swicwe (which has to be used on Linux and is only for WP units, not for EM/MC but you could try it I guess).
Works for me, even though windows reports the usb COM port to be 43, 47, 51, 62, etc. I’ve done this with the EM7565 and flashed 4 at once on Windows 10 with a powered usb hub.
Make sure there is a space in there in: -usbport 1