EC25-E modem on Dahlia board with AM62

[matthiasklein]

I am trying to set up a modem with Torizon. It is an EC25-E which is in the Mini-PCIe slot of a Dahlia V1.1D board. The SoM is an AM62 Q 2GB WB IT V1.2A with Torizon 7.

torizon@verdin-am62-XXXXXXXX:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0424:2744 Microchip Technology, Inc. (formerly SMSC) Hub
Bus 001 Device 003: ID 0424:2740 Microchip Technology, Inc. (formerly SMSC) Hub Controller
Bus 001 Device 004: ID 2c7c:0125 Quectel Wireless Solutions Co., Ltd. EC25 LTE modem

torizon@verdin-am62-XXXXXXXX:~$ dmesg | grep wwan
[ 14.307126] qmi_wwan 1-1.3:1.4: cdc-wdm0: USB WDM device
[ 14.309239] qmi_wwan 1-1.3:1.4 wwan0: register ‘qmi_wwan’ at usb-xhci-hcd.4.auto-1.3, WWAN/QMI device, XX:XX:XX:XX:XX:XX
[ 14.309683] usbcore: registered new interface driver qmi_wwan
[ 14.334220] qmi_wwan 1-1.3:1.4 wwu1u3i4: renamed from wwan0

torizon@verdin-am62-XXXXXXXX:~$ lsmod
Module Size Used by
…
qmi_wwan 40960 0
cdc_wdm 28672 2 qmi_wwan
option 61440 0
usbnet 53248 1 qmi_wwan
usb_wwan 24576 1 option
…

torizon@verdin-am62-XXXXXXXX:~$ cat /etc/os-release
ID=torizon
NAME=“Torizon OS”
VERSION=“7.2.0+build.13 (scarthgap)”
VERSION_ID=7.2.0-build.13
VERSION_CODENAME=“scarthgap”
PRETTY_NAME=“Torizon OS 7.2.0+build.13 (scarthgap)”
CPE_NAME=“cpe:/o:openembedded:torizon:7.2.0+build.13”
BUILD_ID=“13”
ANSI_COLOR=“1;34”
VARIANT=“Docker”

(I have replaced the serial numbers / MAC addresses in the outputs above with “X”).

But ModemManager does not recognize a modem:

torizon@verdin-am62-XXXXXXXX:~$ sudo mmcli -L
No modems were found

[ToradexAI]

Hi, I’m the Toradex AI Assistant.

I might make mistakes. Our support team will step in if needed. If I answered your question, please tick the “Solution” checkbox. For follow-up questions to me, please use @ToradexAI in your post.

Did you like my answer?

---

Hello! Thank you for providing the detailed information about your setup.

Your system detects the EC25-E modem at the USB level and loads the qmi_wwan and other relevant drivers, which is a great start. Now, let’s troubleshoot why ModemManager is not seeing the modem.

Please follow these steps:

1. Check if ModemManager is running

First, verify that ModemManager is active:

systemctl status ModemManager

If it’s not running, start it with:

sudo systemctl start ModemManager

Documentation:

Modem Support | Toradex Developer Center

2. Rescan for modems
   After ensuring ModemManager is running, try scanning for modems again:

mmcli -L

Documentation:

Modem Support | Toradex Developer Center

3. Check ModemManager logs for issues

If the modem is still not listed, check the logs for error or warning messages:

journalctl -u ModemManager

This can provide insights if, for example, the device nodes are not exposed correctly or if access permissions are an issue.
Example issue discussion:

modemmanager stuck at registration

0 I have a dual sim iot device which was running Modem manager 1.10 on ubuntu 16.04. Recently upgraded to Modem manager 1.20.0 on ubuntu 22.04. When Switch from first slot to second slot, modem manager is stuck with 3GPP status “registered” with the warning messages [modem0/bearer1] connection attempt #3 failed: Couldn’t find associated QMI port for ‘net/wwp0s29u1u1i10’ It is not the slot/SIM/APN issue because it gets data connection if the device is rebooted with the 2nd slot active. Note:…

4. Verify connections and device nodes

Make sure your modem is physically well-seated and that the correct device nodes (like /dev/cdc-wdm0, /dev/ttyUSB*) are present by running:

ls -l /dev/cdc*
ls -l /dev/ttyUSB*

ModemManager uses these device nodes to communicate with modems.

5. Dahlia board compatibility

Your hardware combination (Dahlia V1.1D, Verdin AM62, EC25-E modem) is supported, and the Mini-PCIe slot is suitable for the cellular modem:

Dahlia Carrier Board | Toradex Developer Center

Dahlia Carrier Board | Toradex Developer Center

---

Please try each step and share the output, especially the results of ModemManager’s status and logs. This will help further pinpoint the issue.

Best regards,
Toradex AI Assistant.

[matthiasklein]

torizon@verdin-am62-XXXXXXXX:~$ journalctl -u ModemManager
Jun 24 15:17:56 verdin-am62-XXXXXXXX systemd[1]: Starting Modem Manager...
Jun 24 15:17:57 verdin-am62-XXXXXXXX ModemManager[541]: <msg> ModemManager (version 1.22.0) starting in system bus...
Jun 24 15:17:57 verdin-am62-XXXXXXXX systemd[1]: Started Modem Manager.
Jun 24 15:18:03 verdin-am62-XXXXXXXX ModemManager[541]: <msg> [base-manager] couldn't check support for device '/sys/devices/platform/bus@f0000/8000000.ethernet': not supported by any plugin
Jun 24 15:18:03 verdin-am62-XXXXXXXX ModemManager[541]: <msg> [base-manager] couldn't check support for device '/sys/devices/platform/bus@f0000/bus@f0000:bus@4000000/4e08000.can': not supported by any plugin
Jun 24 15:18:03 verdin-am62-XXXXXXXX ModemManager[541]: <msg> [base-manager] couldn't check support for device '/sys/devices/platform/bus@f0000/20701000.can': not supported by any plugin
Jun 24 15:18:05 verdin-am62-XXXXXXXX ModemManager[541]: <msg> [base-manager] couldn't check support for device '/sys/devices/platform/bus@f0000/fa20000.mmc/mmc_host/mmc2/mmc2:0001/mmc2:0001:1': not supported by any plugin
Jun 24 15:18:06 verdin-am62-XXXXXXXX ModemManager[541]: <msg> [device /sys/devices/platform/bus@f0000/f910000.dwc3-usb/31100000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.3] creating modem with plugin 'quectel' and '6' ports
Jun 24 15:18:06 verdin-am62-XXXXXXXX ModemManager[541]: <msg> [base-manager] modem for device '/sys/devices/platform/bus@f0000/f910000.dwc3-usb/31100000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.3' successfully created
Jun 27 07:47:25 verdin-am62-XXXXXXXX ModemManager[541]: <msg> [modem0] state changed (unknown -> disabled)
Jun 27 07:47:25 verdin-am62-XXXXXXXX ModemManager[541]: <msg> [modem0] state changed (disabled -> enabling)
Jun 27 07:47:25 verdin-am62-XXXXXXXX ModemManager[541]: <msg> [modem0] power state updated: on
Jun 27 07:47:29 verdin-am62-XXXXXXXX ModemManager[541]: <wrn> [modem0] (quectel) modem reset detected, triggering reprobe
Jun 27 07:47:29 verdin-am62-XXXXXXXX ModemManager[541]: <wrn> [modem0] (quectel) modem reset detected, triggering reprobe
Jun 27 07:47:29 verdin-am62-XXXXXXXX ModemManager[541]: <wrn> [modem0] (quectel) couldn't check SIM swap: could not acquire SIM object
Jun 27 07:47:31 verdin-am62-XXXXXXXX ModemManager[541]: <msg> [device /sys/devices/platform/bus@f0000/f910000.dwc3-usb/31100000.usb/xhci-hcd.4.auto/usb1/1-1/1-1.3] creating modem with plugin 'quectel' and '6' ports
Jun 27 07:47:36 verdin-am62-XXXXXXXX ModemManager[541]: <wrn> [modem0] failed enabling modem: Operation was cancelled
Jun 27 07:49:01 verdin-am62-XXXXXXXX ModemManager[541]: <wrn> [modem1] couldn't start initialization: Transaction timed out
Jun 27 07:49:01 verdin-am62-XXXXXXXX ModemManager[541]: <err> [modem1] fatal error initializing: Fatal error: modem is unusable

What do these ModemManager errors mean?