EM9190: Data Connection without MBIM

IoT Modules MC/EM Series
1

Hi,

Is there any way to establish data connection in EM9190 other than using MBIM interface?

Thanks,
Monisha

2

what is the problem of using MBIM interface?

What is the current response of the followings for your module?

AT!ENTERCND="A710"
AT!USBCOMP?
at!USBCOMP=?
Ati3
3

Thanks for replying.
As MBIM is required to establish data connection, the linux (uCLinux) which we are using doesn’t support MBIM.
To get this MBIM working, we tried cross compiling the MBIM source code with our uclibc toolchain (which we procured )and it resulted in various missing dependencies. And fixing the missing library is becoming a never ending task. And we are not sure whether MBIM could be cross-compiled with uclibc toolchain.

So, that’s the reason we are looking for alternatives to establish data connection.

4

What is the response of the followings for your module?

AT!ENTERCND="A710"
AT!USBCOMP?
at!USBCOMP=?
Ati3
5

Here are the responses,

AT!USBCOMP?
Config Index: 1
Config Type: 4 (USBIF-MBIM-V2)
Interface bitmask: 00001009 (diag,modem,mbim)

OK

AT!USBCOMP=?
!USBCOMP:
AT!USBCOMP=,,
- configuration index to which the composition applies, should be 1

- 1:Generic (Not supported),
2:USBIF MBIM (Not supported),
3:RNDIS (Not supported),
4:USBIF MBIM V2 (Supported),
5:USBIF RMNET (Not supported),
6:USBIF MBIM_V2_CUSTOM (Supported)

- DIAG - 0x00000001,
ADB - 0x00000002,
MODEM - 0x00000008,
MBIM - 0x00001000,
RmNET - 0x00000100,
e.g.
9 - diag,modem interfaces enabled
1009 - diag,modem,mbim interfaces enabled

OK

ATI3
Manufacturer: Sierra Wireless, Incorporated
Model: EM9190
ReIMEI: xxxxxxxxxxxxxxx
IMEI SV: 24
FSN: xxxxxxxxxxxxxx
+GCAP: +CGSM

OK

6

Why there is no FW version in your ATI3???

I just found that there is RMNET.

Have you tried the followings?


AT!ENTERCND="A710"
at!USBCOMP=1,4,109
7

Oops, some serial issues. But, here you go

ATI3
Manufacturer: Sierra Wireless, Incorporated
Model: EM9190
Revision: SWIX55C_03.10.07.00 e32f05 jenkins 2022/12/14 16:18:06
IMEI: xxxxxxxxxxxxxxx
IMEI SV: xx
FSN: xxxxxxxxxxxxxx
+GCAP: +CGSM

OK

AT!ENTERCND=“A710”
OK

AT!USBCOMP=1,4,109
OK

AT!USBCOMP?
Config Index: 1
Config Type: 4 (USBIF-MBIM-V2)
Interface bitmask: 00000109 (diag,modem,rmnet0)

OK

Why are we setting it to RMNET?

8

I want to see if your module can use RMNET

Can you reset the module and see if it can go internet via RMNET by the following MBPL procedure?

9

I checked AT!USBCOMP? after resetting the module. It’s been set to RMNET.

Config Index: 1
Config Type: 4 (USBIF-MBIM-V2)
Interface bitmask: 00000109 (diag,modem,rmnet0)

OK

But, AT!SCACT =1,1 results in “+CME ERROR: 30” error

10

did you follow the procedure here?

Did you try the MBPL connection manager?

11

Yes, I followed the procedures. Couple of things I wanna mention here is

  1. the qmicli command did throw something. I don’t know whether this could be counted as an error.

sudo qmicli --device=/dev/cdc-wdm0 --wds-noop --client-no-release-cid
[/dev/cdc-wdm0] Client ID not released:
Service: ‘wds’
CID: ‘15’
2. I’ m using Ubuntu 20.04 and the MBPL drivers of version 32. Mobile Broadband Package for Linux (SDK, Drivers, Documentation)

One more question
Seems like, we need to use libqmi to establish data connection even though the module is configured to work in RMNET? Because again libqmi is a glib based library which turns out to be a problem for my requirement.

12

if you cannot use qmi or mbim, then i have no idea what you can use for data connection

you might try ppp dial up through AT command port, but not sure if this is officially supported

13

Hmm okay, then qmi or mbim is needed to get the data connection.
Sure, we will look on PPP dial up and one more query, what is the AT command to change the modem interface from RMNET to MBIM?

14

how about this ?



AT!ENTERCND="A710"
at!USBCOMP=1,4,1009
AT!RESET
15

Thanks for the quick response!

16

Which dependencies were you missing?