Unable to read LOG_DBG in Mesh Light Fixture

[98918atul]

HI,

I want to read all LOG_DBG while i m provisioning my node, for better understanding the provisioning process.

Currently i m getting some logs as shown in the photo.

I want to read all these log in this function.

Please guide us for how to get these logs.

thanks

[Einar Thorsrud]

Hi,

You can get debug messages from Bluetooth mesh by adding this Kconfig: CONFIG_BT_MESH_LOG_LEVEL_DBG=y

[98918atul]

Hi, 

Now i'm able to get debug logs after adding CONFIG_BT_MESH_LOG_LEVEL_DBG=y.

But i'm not able to read all the LOG_DBG that are there in side the functions.

Like in this function.

So please give solution to print these logs also.

Thanks

[Einar Thorsrud]

Hi,

Sorry, I did not spot that that file had it's own log. To get debug logging here, you can set CONFIG_BT_MESH_PROV_DEVICE_LOG_LEVEL_DBG=y.

PS: You can get a hint that this is what you need to do by looking further up in the file, where you see this:

#define LOG_LEVEL CONFIG_BT_MESH_PROV_DEVICE_LOG_LEVEL
#include <zephyr/logging/log.h>
LOG_MODULE_REGISTER(bt_mesh_prov_device);

So that can be a hint in the future, if trying to figure out how to change the log level for a specific module. Or you can search for the config in Kconfig (in the Kconfig search or in VS Code or some other tool you prefer).

[98918atul]

Its working 

Thanks

[98918atul]

Hi, 

If I want to read LOG_DBG present in msg.c, access.c, and transport.c then, how to do it.

I'm only able to get LOG's present in provisioning file.

Please suggest some solution for this.

Thanks

[Einar Thorsrud]

Hi

You can use the same method as explained before to find the relevant configuration here. Take zephyr/subsys/bluetooth/mesh/msg.c first. There you have on line 11:

#define LOG_LEVEL CONFIG_BT_MESH_ACCESS_LOG_LEVEL

So the log level comes from the CONFIG_BT_MESH_ACCESS_LOG_LEVEL Kconfig. Then you can for instance put that in to the Kconfgi search here to get the relevant configs listed (though it is essentially just the config from the .c file with _DBG, _INF, etc appended).

So if you want all logs, you could add CONFIG_BT_MESH_ACCESS_LOG_LEVEL_DBG=y to your prj.conf.

With the similar approach you can find tat for access.c you can use CONFIG_BT_MESH_ACCESS_LOG_LEVEL_INF=y and for transport.c you can use CONFIG_BT_MESH_TRANS_LOG_LEVEL_INF=y.