EM9190 not being detected in Linux Ubuntu 20.04.5 EM9191 EM7690
EM9190 DEV KIT BOARD 5304831_REV_4
$ lsusb
command in terminal doesn’t detect the EM9190 [Item: 6001349 ] Sierra Wireless 5G Development Kit.
I have installed MBPL_DRIVERS_R28_ENG1-usb-src.tar suggested in Mobile Broadband Package for Linux (SDK, Drivers, Documentation)
Please Help. Thank you
did you see any new message in dmesg when you plug in the usb of the module?
e.g. something like the followings:
usb 2-2: new SuperSpeed USB device number 2 using xhci_hcd
usb 2-2: config 1 has an invalid interface number: 4 but max is 3
usb 2-2: config 1 has no interface number 2
usb 2-2: New USB device found, idVendor=1199, idProduct=90d3, bcdDevice= 0.06
usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-2: Product: Sierra Wireless EM9191
usb 2-2: Manufacturer: Sierra Wireless, Incorporated
have you checked the PCIE_DIS pin?
Linux is not detecting EM9190 DEV KIT BOARD 5304831_REV_4, connected to my Linux system USB.
I do not see any of the above message or similar message. Actually no message is displayed, plugging in the Dev kit board usb.
then this seems to be related to hardware.
have you checked the PCIE_DIS pin?
So , from what I understood is M.2 Development kit [EM9190 DEV KIT BOARD 5304831_REV_4] by default can be interfaced by PCIe
To interface by USB, the default ‘PCIE_DIS_P20’ pin = low need to be high(connected to 1.8v
My Question is which Pin has 1.8 v in this board EM9190 DEV KIT BOARD 5304831_REV_4 , to connect it to PCIE_DIS_P20, so that I can make USB interface active?
you can see this document section 5:
@jyijyi Thank you. Following the Kit User Guide and using USB Type-C, instead of Debug USB,
USB is detected. In dmesg, I see following related terminal. BUT minicom(serial port access) access to USB, I can’t get AT command working(no response/hangs). Please help.
usbcore: registered new interface driver ftdi_sio
usbserial: USB Serial support registered for FTDI USB Serial Device
ftdi_sio 1-1.2:1.0: FTDI USB Serial Device Converter detected
usb 1-1.2: Detected FT-X
usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUSB0
usbcore: registered new interface driver cdc_wdm
usbcore: registered new interface driver qcserial
usbserial: USB Serial support registered Qualcomm USB modem
usbserial: USB Serial support registered Qualcomm USB modem
qcserial 1-1.4:1.3: Qualcomm USB modem converter detected
usb 1-1.4: Qualcomm USB modem converter now attached to ttyUSB1
qcserial 1-1.4:1.4: Qualcomm USB modem converter detected
usb 1-1.4: Qualcomm USB modem converter now attached to ttyUSB2
…
is your minicom using /dev/ttyUSB1 for AT command communication?
@jyijyi I cannot open minicom on /dev/ttyUSB1. I received message
minicom: cannot open /dev/ttyUSB1: Device or resource busy
Same for /dev/ttyUSB2?
Have you added “sudo”?
Did you use mbpl driver?
Have you tried on windows?
Same for /dev/ttyUSB2? >>>it hangs when using /dev/ttyUSB2 [similar to ttyUSB0 , doesn’t capture the keyboard input and hangs]
Have you added “sudo”? >>>with sudo also does the same. keyboard input not captured for ttyUSB0 & ttyUSB2. For ttyUSB1 can’t connect to minicom
Did you use mbpl driver? >>> Yes mbpl following usb driver is installed in linux. Did make, make install , then reboot as instructed. MBPL_DRIVERS_R28_ENG1-usb-src.tar suggested in Mobile Broadband Package for Linux (SDK, Drivers, Documentation)
Have you tried on windows? >>>In Windows 10 also in putty connecting to specified port COM, putty hangs, doesn’t do anything.
Could it be in usb download mode?
There is a switch for that on dev kit
Switch SW202 is in Boot mode and not in USB Download mode.
@jyijyi Yes, the Switches and Jumpers of my EM9190 board [EM9190 DEV KIT BOARD 5304831_REV_4] is same as yours
then the only difference is the hardware of the module…
do you have another module to test?
BTW, did you install this driver in Windows?
https://source.sierrawireless.com/resources/airprime/software/sdx55-windows-drivers-build-5154/#sthash.R8rPYkpb.dpbs
In my Ubuntu 20.04.5 Linux machine, this is what I see: for $usb-devices. Still not able to communicate with the EM9190 Modem. Please HELP.
T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=480 MxCh= 0
D: Ver= 2.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=1199 ProdID=90d3 Rev=00.06
S: Manufacturer=Sierra Wireless, Incorporated
S: Product=Sierra Wireless EM9190
S: SerialNumber=4H05340********2
C: #Ifs= 4 Cfg#= 1 Atr=a0 MxPwr=500mA
I: If#=0x0 Alt= 0 #EPs= 1 Cls=02(commc) Sub=0e Prot=00 Driver=cdc_mbim
I: If#=0x1 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 Prot=02 Driver=cdc_mbim
I: If#=0x3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none)
I: If#=0x4 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=30 Driver=(none)
I will test another module EM9190 later and I will also try Windows machine with Windows driver later
why this time even no /dev/ttyUSBx?
didn’t you can see it previously?
In this different Linux machine /dev doesn’t display ttyUSBx, with the USB type C connected.
I see ttyUSB0 (in /dev) for this machine when connecting EM9190 board when I connect with debug USB(but not with USB type C). With this ttyUSB0 configuring minicom to this ttyUSB0 part, it still freezes.
In another linux machine, I was able to see /dev/ttyUSB0 , /dev/ttyUSB1 and /dev/ttyUSB2 but minicom freezes and can’t run any AT command.
--------- $dmesg | grep usb
----gives the following log in this Linux terminal, which doesn’t display ttyUSBx for USB type C connection
—displays ttyUSB0, only when Debug USB is connected
[ 19.873952] usbcore: registered new interface driver usbserial_generic
[ 19.873973] usbserial: USB Serial support registered for generic
[ 20.169343] usbcore: registered new interface driver ftdi_sio
[ 20.169362] usbserial: USB Serial support registered for FTDI USB Serial Device
[ 20.169485] usb 3-4: Detected FT-X
[ 20.177402] usbcore: registered new interface driver cdc_ether
[ 20.182530] usb 3-4: FTDI USB Serial Device converter now attached to ttyUSB0
[ 20.226202] usbcore: registered new interface driver cdc_ncm
[ 20.247290] usbcore: registered new interface driver cdc_wdm
[ 20.279880] cdc_mbim 1-1:1.0 wwan0: register ‘cdc_mbim’ at usb-0000:00:04.1-1, CDC MBIM, d6:c9:34:9a:57:72
[ 20.280221] usbcore: registered new interface driver cdc_mbim
[ 21.035517] usbcore: registered new interface driver btusb
[ 21.076069] usb 4-6.1: USB disconnect, device number 4
[ 21.333079] usb 4-6.2: USB disconnect, device number 5
[ 27.117419] audit: type=1400 audit(1667271212.901:3): apparmor=“STATUS” operation=“profile_load” profile=“unconfined” name=“ippusbxd” pid=546 comm=“apparmor_parser”
maybe you try with Windows driver first