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? 
ModemManager Configuration on Torizon OS
Based on your description, you’re experiencing issues with your Sierra Wireless MC7411 PCIe modem after upgrading from Torizon OS 6.8.3 to 7.3.0. Let me help you troubleshoot this ModemManager issue.
Basic ModemManager Verification
First, let’s verify the basic ModemManager setup. Torizon OS provides ModemManager out-of-the-box, along with NetworkManager for automatic network detection and configuration(1).
To check if your modem is detected, you should use:
# mmcli -L
/org/freedesktop/ModemManager1/Modem/0 [Sierra Wireless, Incorporated] MC7455
(1)
Potential Device Tree Issues
Since you mention the PCIe bridge is visible but the modem itself doesn’t appear, this could be related to device tree changes between Torizon OS versions. Device tree modifications might be necessary to properly configure the PCIe interface for your modem(2).
Customization Approach
If device tree modifications are needed, you can use TorizonCore Builder to apply custom device tree overlays. The process involves creating a device tree overlay (.dts file) and applying it using TorizonCore Builder(3).
For device tree customization, you would create a configuration file like:
customization:
device-tree:
include-dirs:
- device-trees/include/
custom: device-trees/dts-arm32/imx6dl-colibri-eval-v3.dts
overlays:
add:
- device-trees/overlays/colibri-imx6_hdmi_overlay.dts
- device-trees/overlays/colibri-imx6_atmel-mxt-connector_overlay.dts
(4)
Pin Configuration Considerations
The “Phy link never came up” messages in dmesg suggest potential pin configuration issues. You may need to verify that the pins used for PCIe are properly configured and not conflicting with other peripherals(2).
Production Deployment
After making any necessary changes to your board configuration, you can use the isolate command from TorizonCore Builder Tool to generate your custom Torizon OS image for deployment(1).
Recommendations
- Check PCIe Device Tree Configuration: Compare the device tree files between Torizon OS 6.8.3 and 7.3.0 to identify any changes affecting PCIe enumeration
- Verify Pin Conflicts: Ensure no pin conflicts exist that might prevent proper PCIe operation
- Create Custom Overlay: If needed, create a device tree overlay to restore the PCIe configuration that worked in 6.8.3
- Test with TorizonCore Builder: Use TorizonCore Builder to apply any necessary customizations
The transition from Torizon OS 6.x to 7.x may have introduced changes in the kernel configuration or device tree that affect PCIe modem detection. Creating a custom image with the appropriate device tree modifications should resolve the issue.
Best regards, Toradex AI Assistant.
