EM7455 not recognised anymore after usbmode change

[Flachzange]

I have a EM7455 VID: 1199 PID: 9075.

The modem was working fine so war. I wanted to change to usbmode 6 to allow firmware update via qmi.

If I remember correctly, the usbmode before change was 8.

I used swi_setusbcomp.pl « scripts - wwan.git - Utilities for configuring and using wwan interfaces like the Ericsson F3507g on a Linux system to do that change.

(The same script and procedure worked fine on a dell branded EM7455)

The script ran through successfully, but after restarting the modem I neither have, qmi nor AT access. Basically no interface is created. There is neither a /dev/ttyUSB nor a /dev/cdc-wdm device.
The device is recognised by lsubs though.

dmesg says:

usb 2-2: config 1 has an invalid interface number: 8 but max is 3
usb 2-2: config 1 has no interface number 1

Attaching the same device to Windows, I only get a single unknown device:

USB\VID_1199&PID_9075&MI_08

With a little trial and error I was able to install a windows driver which translates to

Sierra Wireless EM7455 Qualcomm® Snapdragon™ swmbbnode device 03

But nothing else, it is also not usable in Windows.

Can some help by explaining what happened here, i.e. in which mode the modem is currently in? How can I leave it?

I alread found this thread: EM7455 stuck with no tty nor cdc-wdm devices

But the situation is different to mine. I have not messed with VID/PID.

Thanks!
Chris

[jyijyi]

Why don’t you change the mode by “AT!USBCOMP?” ?
I am not sure if those perl script is officially supported…

BTW, does this help?

Em7430 no com port after vid:pid change

Some idea like this one: I also see the qcserial.c in MBPL usb driver where you might add your pid: [image]

Em7430 no com port after vid:pid change

oh god, i did fix this by many many wierd steps on both Windows10 and Ubuntu 20.04, thanks you @dl5162 , this .nvu is helpful to change the pid, so driver and usb bus can be detected, my works are: using physical pc, dont use virtual machine with usb passthrough because the vm host will not detect usb bus without driver Clean the hardware, m2 pin, m2 adapter pin to avoid pin missing or short must know the device usb setting, i remember it was 3 so i plug it on usb 3.0 port Plug in on windows 1…

[Flachzange]

Thanks @jyijyi

I am a few steps further.

Installing the generic drivers with DisableUsbCompAutoUpdate=0 brought back 4 devices in device manager but still not recognised.

VID: 1199 PID: 9075 seems to be a (rare) Fujitsu variant.

I managed to get some Fujitsu drivers and they indeed installed properly.

I flashed the latest firmware via ftd2 successfully. Here it become also clear that this is a Fujitsu device

OEM PRI: 9904948 001.007 Fujitsu-EU

I am able to access the modem via AT commands now. So I want to change VID/PID now to generic ones:

AT
OK
ATI3
Manufacturer: Sierra Wireless, Incorporated
Model: EM7455
Revision: SWI9X30C_02.39.00.00 rF194F7CA76D79E jenkins 2024/06/05 05:36:47
MEID: 35907306281123
IMEI: 359073062811231
IMEI SV: 23
FSN: LF916288900310
+GCAP: +CGSM


OK
AT!ENTERCND="A710"
ERROR

If I understood correctly, this means a non-standard password is set.

Can you confirm? Anything I can do here?

@jyijyi

Why don’t you change the mode by “AT!USBCOMP?” ?

Because I simply did not know and followed one of the first instructions I found, but if the password lock is true I could anyhow not made it.

Any further advice appreciated

[jyijyi]

What do you want to do now actually?
Unlock the module by a password?
I think you need to contact Fujitsu to get the password

[Flachzange]

I want to change the VID/PID so that my Linux system can actually recognise it with its default driver

[jyijyi]

i don’t know the password for AT!ENTERCND…
how about using something like ?

echo xxxx xxxx > /sys/bus/usb-serial/drivers/qcserial/new_id

EM7565 driver/firmware issue

You can disconnect the usb, use "sudo rmmod qcserial " And then check modinfo of qcserial, check the path and see if it is newly compiled

[Flachzange]

Yes, I would need to recompile, but that is actually not worth the effort for this cheap modem.

I am curious about the following. When I got the modem in usbmode 8 in the first place, i.e. with MBIM. The modem was recognised by the default windows driver and by the default linux driver…

Only when I changed the usbmode to 6 with QMI the driver issue occured.

Why is that the case?

[jyijyi]

does your linux system install the MBPL driver (i.e. qmi_wwan) for the QMI interface?

https://source.sierrawireless.com/resources/airprime/software/mbpl/mbpl-software-latest/#sthash.ZXRwiiKx.O8Q2Ct4m.dpbs

[Flachzange]

I installed the driver but does not make any difference. For the sake of completeness:

[  205.599820] usb 2-2: new high-speed USB device number 7 using xhci_hcd
[  205.729817] usb 2-2: config 1 has an invalid interface number: 8 but max is 3
[  205.729835] usb 2-2: config 1 has no interface number 1
[  205.730436] usb 2-2: New USB device found, idVendor=1199, idProduct=9075, bcdDevice= 0.06
[  205.730453] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  205.730461] usb 2-2: Product: EM7455
[  205.730468] usb 2-2: Manufacturer: Sierra Wireless, Incorporated
[  205.730473] usb 2-2: SerialNumber: LF91628890031028

Also the qmi device is not created

[jyijyi]

how about using something like ?

echo xxxx xxxx > /sys/bus/usb-serial/drivers/qcserial/new_id

EM7565 driver/firmware issue

You can disconnect the usb, use "sudo rmmod qcserial " And then check modinfo of qcserial, check the path and see if it is newly compiled

You might also need to open qmi_wwan.c and qcserial.c to add the VID PID