My MC7710 can't work on Linux after plug-in it to Windows8

[dl5162]

@lotam

@dl5162

since that firmware doesn’t support the AT!UDUSBCOMP command

It is not completely true, a new command is available.
Please check with your Distributor or Sierra contact to get related AT cmd guide.

Thanks! When you mention it, I even believe I saw something about that on this forum…

The truth is that I am now so spoiled with the excellent “source” site that I thought I’d just wait for the documents to appear there, instead of unnecessarily “bothering” my Sierra contact. But I guess I should request a documentation set. I feel a bit like I did with the MC7710 in 2012 though: It is very difficult to know what to ask for without knowing exactly which documents are available. It’s a bit better now though, as I guess I can assume there are updated versions of most of the documents relevant to the MC73xx series.

And just for the record: I like very much what I’ve seen of the MC7455 so far. I really appreciate small improvements like (finally) adding a CDC Union descriptor to the MBIM function. And the support for multiple MBIM IP sessions now makes MBIM a viable alternative to QMI for these modules. Personally I’d like to see a move towards MBIM for embedded usage too. But I understand that both Sierra and your customers are locked into existing software solutions, making both QMI and AT commands necessary. Still hoping that we’ll see more MBIM in embedded as soon as assorted BSPs start using v3.8 or newer kernels. I haven’t actually tested it, but I see no reason why an MC7455 released in the 2nd half of 2015 shouldn’t work out-of-the-box with the mainline cdc_mbim driver released in February 2013. No need for any device ID addition or anything. That in itself should be all the reasons you need for MBIM, IMHO.

But as usual, I am biased

[rfanch3r]

Hi, any advice on getting this working in Arch Arm linux?

Can’t locate UUID/Tiny.pm in @INC (you may need to install the UUID::Tiny module) (@INC contains: /usr/lib/perl5/5.36/site_perl /usr/share/perl5/site_perl /usr/lib/perl5/5.36/vendor_perl /usr/share/perl5/vendor_perl /usr/lib/perl5/5.36/core_perl /usr/share/perl5/core_perl) at ./swi_setupcomp.pl line 8.

[dl5162]

A lot has happened in the 7+ years since that was written. So, while it still is possible to use the hackish perl script, I recommend using libqmi/qmicli instead.

The get/set-usb-composition commands do exactly the same as the perl script:

bjorn@miraculix:~$ qmicli --help-dms|grep swi
  --dms-swi-get-current-firmware                                                                                    Get Current Firmware (Sierra Wireless specific)
  --dms-swi-get-usb-composition                                                                                     Get current and supported USB compositions (Sierra Wireless specific)
  --dms-swi-set-usb-composition=[#]                                                                                 Set USB composition (Sierra Wireless specific)

qmicli can also be used in MBIM mode.

I assume libqmi is packaged for Arch Linux as well. In Debian, the package with qmicli is named libqmi-utils. It’s probably something similar in other Linux distros.

[rfanch3r]

Well the issue I am having is that I am unable to send text msgs, it was suggested that I change this to QMI but I have been using it using mmcli and still getting sms msg blocking.

I do have qmicli installed but do not know how this works compared to mmcli

[dl5162]

I don’t think MBIM or QMI will affect messaging capabilities. That’s just different protocols use to talk to the modem from the host. It doesn’t change how the modem communicates with the network.

[cbldbssr]

I am facing similar issue like posted here:

How to reset MC7750 into QMI and AT-command mode on Linux?

I have two MC7750 modems and one I have configured as, which is exactly what I want: AT!UDUSBCOMP=? 0 - HIP DM NMEA AT MDM1 MDM2 MDM3 MS NOT SUPPORTED 1 - HIP DM NMEA AT MDM1 MS NOT SUPPORTED 2 - HIP DM NMEA AT NIC1 MS NOT SUPPORTED 3 - HIP DM NMEA AT MDM1 NIC1 MS NOT SUPPORTED 4 - HIP DM NMEA AT NIC1 NIC2 NIC3 MS NOT SUPPORTED 5 - HIP DM NMEA AT ECM1 MS NOT SUPPORTED 6 - DM NMEA AT …

However on my system I don’t have any /dev/cdc-wdm* device available, so qmicli cannot really talk to the modem:

# ls -l /dev/cdc-wdm0
ls: cannot access '/dev/cdc-wdm0': No such file or directory

# modprobe cdc_mbim
# dmesg -T
...
[Thu Apr 13 07:08:43 2023] usbcore: registered new interface driver cdc_ether
[Thu Apr 13 07:08:43 2023] usbcore: registered new interface driver cdc_ncm
[Thu Apr 13 07:08:43 2023] usbcore: registered new interface driver cdc_wdm
[Thu Apr 13 07:08:43 2023] usbcore: registered new interface driver cdc_mbim

# ls -l /dev/cdc-wdm*
ls: cannot access '/dev/cdc-wdm*': No such file or directory

[cbldbssr]

Same goes when I load qmi_wwan and qmi_helpers, no /dev/cdc-wdm* device pops up. Not sure how I can switch the modem to !UDUSBCOMP: 6 without access to /dev/cdc-wdm0