EM7565 driver/firmware issue

IoT Modules MC/EM Series
1

Hi everyone,

in an enterprise environment we are using EM7565 LTE modems with Windows 10 to provide connectivity. However with the latest bunch of modems bought we experience driver/firmware problems. Up to now the EM7576 has an USB Pid/Vid of 1199/9091. All recently acquired modems of this Pid/Vid work flawlessly. However, with the latest bunch there are devices with Pid/Vid 1199/90B1. These modems are not working with the current device driver: In the Windows device management there is an unknown device. Communication with the modem over its serial port is not possible. Thus, sending AT commands does not work. A quick look into the device driver’s inf files suggests, that this Pid/Vid is not supported (completely). From this behaviour there are a couple of questions:

  • Is this a known bug?
  • What are the differences between this two hardware versions?
  • Is a new driver needed?
  • Is there any chance to setup the “new” modem versions with the old working Pid/Vid?

Thank You for any help on this topic.

Norbert

2

have you tried the MBPL linux driver?

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

3

No, since the devices are used with Windows 10.

4

you can see if it works in linux first on virtual machine under Win10

5

Ok, I will give it a try and will report.

6

Ok, I now tried the devices with a fresh installation of Ubuntu. This is the output of ‘dmesg | grep usb’ for a working EM7565device:

[ 2897.097191] usb 1-2: New USB device found, idVendor=1199, idProduct=9091, bcdDevice= 0.06
[ 2897.097194] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2897.097195] usb 1-2: Product: Sierra Wireless EM7565 Qualcomm® Snapdragon™ X16 LTE-A
[ 2897.097196] usb 1-2: Manufacturer: Sierra Wireless, Incorporated
[ 2897.097197] usb 1-2: SerialNumber: UF93778851031546
[ 2897.195158] usb 1-2: Qualcomm USB modem converter now attached to ttyUSB0
[ 2897.226284] usb 1-2: Qualcomm USB modem converter now attached to ttyUSB1
[ 2897.258366] usb 1-2: Qualcomm USB modem converter now attached to ttyUSB2
This device works flawlessly with Ubuntu, no problems in device detection and usage as mobile broadband device. However, linux appears to have similar problems to work with the “new” device of different USB PID/VID.

This is the output of dmesg | grep usb for the second device:
[ 2764.541877] usb 3-1: New USB device found, idVendor=1199, idProduct=90b1, bcdDevice= 0.06
[ 2764.541882] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2764.541885] usb 3-1: Product: Sierra Wireless EM7565 Qualcomm® Snapdragon™ X16 LTE-A
[ 2764.541887] usb 3-1: Manufacturer: Sierra Wireless, Incorporated
[ 2764.541888] usb 3-1: SerialNumber: UF02920385031047

This device is not detected as a mobile broadband modem. No cell device appears and the device is not usable by Ubuntu. May I kindly repeat my question: why do the devices differ in their PID/VID?

7

Have you tried to change pid by AT command

8

No, since there is no serial port due to missing / failing driver either on Windows or Linux it is not possible to send any AT commands.

9

BTW: The 9091 device runs out of the box with Ubuntu, no need to install any additional drivers. If I download the linux drivers as suggested there is only a tar.gz archive with a bunch of *.ko files. How are these files to be installed? There is no documentation of how to get them installed on Linux.

10

I saw there should be AT port

[ 2897.195158] usb 1-2: Qualcomm USB modem converter now attached to ttyUSB0
[ 2897.226284] usb 1-2: Qualcomm USB modem converter now attached to ttyUSB1
[ 2897.258366] usb 1-2: Qualcomm USB modem converter now attached to ttyUSB2

To install mbpl driver, you need to

make clean
make
make install

11

No, the attached messages came from the working modem (with VID 9091). The second device (with VID 90B1) didn’t emit these messages.

In the driver archive MBPL_DRIVERS_R30_ENG1-bin.tar.gz there is just a bin folder containing binaries of the different machine architectures. There is no makefile or an install script.

12

You should download the usb one
( MBPL_DRIVERS_R30_ENG1-usb-src.tar)

13

Ok, did that now. After make clean, make, make install the driver sources compiled successfully and the binaries got installed (copied), After reboot none of my devices do work anymore. They do not appear as a serial device like /dev/ttyUSB*. Further, the device with VID 9091 is not longer detected anymore by Ubuntu and is not longer usable.

14

you mean all of your module are dead?
Or your ubuntu is dead?

15

No, Ubuntu is running normal. The devices are found (at least they are shown by lsusb), but there is no modem functionality anymore and there are no serial ports /dev/ttyUSB*.

16

i check the qcserial.c, it should support PID 90b1

17

Do you have any news about this topic? I’m, running out of ideas especially what to do with the windows driver issue. Is there anybody else having troubles with this issue?

18

What did you see for “modinfo qcserial”?

19

Here is the output of “modinfo qcserial”, see uploaded file.
modinfo_qserial.txt (16.2 KB)

20

i can see 90b1 inside