Custom AT command support in ModemManager

Jose, Shijo Shijo.Jose at hughes.com
Tue Aug 15 23:36:58 UTC 2017


Moving thread (MBIM_CID_DEVICE_SERVICE_SUBSCRIBE_LIST support) form libmbim-devel list.

>> Is there way to send AT commands to the modem via MM?
>>I tired -
>> mmcli -m 0 --command="E0"
>> error: command failed: 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Connected: No AT port available to run command'

> This happens when there is a single TTY and it is already connected, there is no other available channel to send commands. ModemManager doesn't setup CMUX automatically yet.

Can this be manually enabled in M for MBIM devices?

>> Also, can I have MM detect an already connected (plugged-in) USB modem, instead of waiting for a hotplug event?

>If you're using my ModemManager openwrt integration setup, you should have a file in /var/run/modemmanager/events.cache which holds the MM-applicable events that >happened since the system was booted. If you run ModemManager yourself you should be able to start the daemon with the extra --initial-kernel-events=[PATH] argument >pointing to that file. Or, otherwise, see mm_report_events_from_cache() in /etc/modemmanager/modemmanager.common

I don't see my device (cdc-wdm0) in this list when it is already plugged in when the host powers up. How is this list(events.cache) populated?


Thanks,
Shijo


More information about the ModemManager-devel mailing list