Run ModemManager in debug mode

[Aleksander Morgado]

Hey

The --debug option gives you 2 things: debug log and AT command
support via the Command() API.

The mmcli -G DEBUG option only changes the debug log level.

If you need the AT command support via Command() you need either the
--debug option as you were using, or otherwise make sure you build
ModemManager using the --with-at-command-via-dbus configure option

On Mon, Dec 7, 2020 at 11:18 AM NIKHIL PATIL <nikhilvp29 at gmail.com> wrote:
>
> Hi ,
>  I tried to enable using    " mmcli -G DEBUG "  it come successfully enable debug logging level .
>   but , when we run AT command using mmcli we are getting same error as before (error :- modemmanager should in debug mode ).
>   how we can proceed on these ?
>
> On Sun, Dec 6, 2020 at 1:17 PM Aleksander Morgado <aleksander at aleksander.es> wrote:
>>
>> Hey
>>
>> >     After board boots we are changing the ModeManger.service as (ExecStart=/usr/sbin/ModemManager --debug)
>> > but that is not good practice.
>> >
>> >     How We can run ModemManager in debug mode while compiling yocto image itself ?
>> >     build platform = yocto
>>
>> The --debug option gives you 2 things: debug log and AT command
>> support via the Command() API.
>>
>> If it's a change you require always by default in all your builds, you
>> could patch the ModemManager recipe to modify the service file to add
>> the --debug.
>>
>> If you need to enable the debug log only sometimes during runtime, you
>> could use "mmcli -G DEBUG" to change the daemon logging level.
>>
>> If what you need is to unconditionally have AT command support via the
>> Command() API always, you can modify the ModemManager recipe to
>> configure the build with the --with-at-command-via-dbus option, that
>> will enable that API by default regardless of whether --debug is used
>> during runtime or not.
>>
>> --
>> Aleksander
>> https://aleksander.es



-- 
Aleksander
https://aleksander.es