What do you mean exactly by "it doesn't work"? Is configure of modemmanager had not been executed with the above mentioned option? Did you check the configure log made by yocto? Anyway, I think we are off the road here since it became a yocto issue rather than a modem manager one. ________________________________ From: NIKHIL PATIL <[email protected]> Sent: Tuesday, December 29, 2020 1:59:10 PM To: Frederic Martinsons <[email protected]> Cc: Aleksander Morgado <[email protected]>; ModemManager (development) <[email protected]> Subject: Re: Run ModemManager in debug mode
Hi , I created modemmanager_1.6.4.bbappend file and in these i copied above data. i tried these it not worked. Is there another method ? On Mon, Dec 28, 2020 at 3:20 PM Frederic Martinsons <[email protected]<mailto:[email protected]>> wrote: Hi, for adding this to configure option , you need to add EXTRA_OECONF += " --with-at-command-via-dbus" to the modemmanager recipe or create a bbappend in your custom layer. ________________________________ From: ModemManager-devel <[email protected]<mailto:[email protected]>> on behalf of NIKHIL PATIL <[email protected]<mailto:[email protected]>> Sent: Monday, December 28, 2020 9:28 AM To: Aleksander Morgado <[email protected]<mailto:[email protected]>> Cc: ModemManager (development) <[email protected]<mailto:[email protected]>> Subject: Re: Run ModemManager in debug mode Hi Aleksander , How we can add these debug option while build time only on yocto build . any idea ? On Wed, Dec 9, 2020 at 4:08 PM NIKHIL PATIL <[email protected]<mailto:[email protected]>> wrote: Hi Aleksander , We want to add debug option ad build time only , How we can add these debug option while build time only on yocto build side ? ModemManager package is in meta-openembedded layer . build platform :- yocto On Mon, Dec 7, 2020 at 7:09 PM Aleksander Morgado <[email protected]<mailto:[email protected]>> wrote: 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 <[email protected]<mailto:[email protected]>> 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 > <[email protected]<mailto:[email protected]>> 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
_______________________________________________ ModemManager-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
