how to enable zigbee log

[pintai]

Hi,

I am debugging the zigbee functionality and would like to enable the zigbee log,already enabled log in prj.conf but no data coming out.What do I have to do to enable log.

[Edvin]

Hello,

Are you sure you mean that you want to enable the zigbee trace? Or do you want to enable normal application logging? They are two different things. Application logs are the ones that you can monitor using a UART or RTT terminal, while a trace log is something that we would have to send to our stack provider to decrypt,  if you suspect that there is a bug in the Zigbee stack (Zboss stack).

Best regards,

Edvin

[pintai]

Hi Edvin，

I want to enable zigbee log.I'm doing zigbee development  so I'd like to use the zigbee log to helped me understand the source code.I just need to enable a log like "TRACE_MSG(TRACE_ZCL1,">> zb_zcl_ias_zone_check_attr_notify buf_param %hd", (FMT__H,  buf_param));"

[Edvin]

I believe you misunderstood my question. The TRACE_MSG() is not something that is intended for your development. 

What you are looking for is the logging module. Do you prefer the log on UART or RTT? I suggest you check out the way that the logging is set up in the sample:

NCS\nrf\samples\zigbee\light_bulb.

E.g. in main.c -> main() it says:

LOG_INF("Starting ZBOSS Light Bulb example");

This will be printed over UART, so if you open the COM port that belongs to your DK using baudrate 115200, you should see this log. If you want more detials, remove the line in prj.conf saying CONFIG_NCS_SAMPLES_DEFAULTS=y, and it should include a timestamp, and you will be able to move the log to RTT if you prefer that.

Best regards,

Edvin

[pintai]

Hi Edvin,

I can see the logs output from the serial port, but I can't see the debugging information output by TRACE_MSG.I'm currently working on the IAS ZONE feature and I need to change the IAS ZONE state with  a button.But now I'm using the zb_zcl_ias_zone_change_status function to change the IAS Zone ,But the IAS ZONE only responded once, so I'm trying to locate my problem via TRACE_MSG.

[Edvin]

Ok, I see. 

Please see:

https://docs.nordicsemi.com/bundle/addon-zigbee-r22-1.0.0/page/configuring/configuring_zboss_traces.html#select_which_zboss_trace_logs_to_print

Relevant KConfigs that  you can set in your prj.conf are:

CONFIG_ZBOSS_TRACE_MASK=0x00000C48
CONFIG_ZBOSS_TRACE_LOG_LEVEL_DBG=y

You can see how to enable the trace logs from different modules in ncs\nrf\subsys\zigbee\kconfig:

config ZBOSS_TRACE_MASK
	hex "Trace mask of ZBOSS stack logs"
	default 0x0000
	range 0x00000000 0xFFFFFFFF
	help
	  Selectively enable Zigbee binary trace logs.
	  The mask value is expected to be a bitwise OR of values assigned to selected modules.

	  Available modules:

	  - 0x04000000 Reserved
	  - 0x02000000 Reserved
	  - 0x01000000 Reserved
	  - 0x00800000 Reserved
	  - 0x00400000 Reserved
	  - 0x00200000 Zigbee NCP: transport (LL)
	  - 0x00100000 Zigbee NCP: command adapters (HL)
	  - 0x00080000 ZCL: Firmware over-the-air upgrade
	  - 0x00040000 IAS zone device: battery monitoring
	  - 0x00020000 Reserved
	  - 0x00010000 MAC lower layer
	  - 0x00008000 MAC layer API calls
	  - 0x00004000 Zigbee Green Power
	  - 0x00002000 Custom components
	  - 0x00001000 Reserved
	  - 0x00000800 Application
	  - 0x00000400 Reserved
	  - 0x00000200 Zigbee Light Link
	  - 0x00000100 Zigbee Cluster Library
	  - 0x00000080 Security
	  - 0x00000040 Zigbee Device Object
	  - 0x00000020 Zigbee Smart Energy
	  - 0x00000010 Application support layer
	  - 0x00000008 Network layer
	  - 0x00000004 MAC layer
	  - 0x00000002 Memory management
	  - 0x00000001 Common

	  For example, to enable traces related to OTA DFU, set this option to 0x00080100.

	  Note: For general debugging purposes, use 0x00000C48.

Best regards,

Edvin