LOG_DBG message not appear in LTE while LOG_INF works well

Hi,

The log level for your module is probably set to info. To show debug logs, you must set the log level to debug instead. You can do this by either setting the log level for the specific module, or by setting the default log level for all modules. See Logging in a module for more information on how to do this.

Best regards,

Marte

Where in the Asset_tracker_v2, these settings have been done ?

Hi,

You can set the log level in prj.conf.

Best regards,

Marte

In my project, in prj.conf following is defined

but, the DBG messages of all default modules appear in LTE but that not of manually added module. 

In the custom_module.c file, I have declared following:

LOG_MODULE_REGISTER(custom_module, CONFIG_BMS_MODULE_LOG_LEVEL);

Hi,

The local log level configuration must also be defined in Kconfig. There exists a Kconfig template which makes this much easier. Using this the configuration CONFIG_BMS_MODULE_LOG_LEVEL will be generated if you add the following to your modules Kconfig file:

module = BMS_MODULE
module-str = bms_module
source "subsys/logging/Kconfig.template.log_config"

You will find many examples of how this is done for other modules in the SDK, for example in the Kconfig module files for the Asset Tracket v2, which can be found in asset_tracker_v2/src/modules/. 

You must also remember to set the log level for your module in prj.conf if you want to set it to something other than the default log level.

Another option is to not use optional module log level, and simply register with LOG_MODULE_REGISTER(bms_module), and then set the default log level (CONFIG_LOG_DEFAULT_LEVEL) to debug.

You should find information about all of this in Logging in a module, which I linked to earlier.

Best regards,

Marte

Hi,

The local log level configuration must also be defined in Kconfig. There exists a Kconfig template which makes this much easier. Using this the configuration CONFIG_BMS_MODULE_LOG_LEVEL will be generated if you add the following to your modules Kconfig file:

module = BMS_MODULE
module-str = bms_module
source "subsys/logging/Kconfig.template.log_config"

You will find many examples of how this is done for other modules in the SDK, for example in the Kconfig module files for the Asset Tracket v2, which can be found in asset_tracker_v2/src/modules/. 

You must also remember to set the log level for your module in prj.conf if you want to set it to something other than the default log level.

Another option is to not use optional module log level, and simply register with LOG_MODULE_REGISTER(bms_module), and then set the default log level (CONFIG_LOG_DEFAULT_LEVEL) to debug.

You should find information about all of this in Logging in a module, which I linked to earlier.

Best regards,

Marte

Hi, I have already added the suggested code to kconfig file as shown below:

I observed in the prj.conf only CONFIG_LOG=y is written. Where the LOG level has been set to DBG in default kconfig or .c files in Asset_tracker_v2, I could not find in it ? I searched kconfig.data_module and data_module.c etc .... for cloud, ui, util, modem, sensor etc  ...

Hi,

If you add overlay-debug.conf as overlay config file when building, then the log level of the modules will be set to debug. If not, they should default to info, unless you set the default log level for all modules to debug in prj.conf using CONFIG_LOG_DEFAULT_LEVEL. You can check what the log levels have been set to after building by looking in the file asset_tracker_v2/build/zephyr/.config. If you for example search for CONFIG_SENSOR_MODULE_LOG_LEVEL you will see which level it is set to, for example:

Best regards,

Marte