Reply
Posts: 24
Registered: ‎07-19-2016

Simplicity Studio HAL configuration Debug Level

Hi All

 

In HAL configuration the debug level menu option has disappeared, despite being mentioned in all the documentation, how do I now select the debug lev3l in the HaSampleLightSoc zigbee examples?

 

Thanks

Ed

Posts: 201
Registered: ‎02-05-2014

Re: Simplicity Studio HAL configuration Debug Level

Good question... The answer is that the Debug Level picklist is redundant now that you have Debug Library plugins in the Plugins tab, so you can turn on one, both, or neither of these plugins to get the equivalent of the old debug levels from the picklist:

 

Debug Basic Library plugin enabled + Debug Extended Library plugin enabled = "Full" debug level.

Debug Basic Library plugin enabled without Debug Extended Library plugin being enabled = "Normal" debug level.

 

Neither Debug Basic Library nor Debug Extended Library plugin enabled = "Off" debug level.

 

Note that since the Debug Extended Library plugin uses Debug Basic Library as a dependency, having the Extended library without the Basic library isn't a valid option here.

 

_zigMaster_

--------
The views represented in this post are the independent views of the author and don't necessarily represent the official views of Silicon Labs.
Highlighted
Posts: 201
Registered: ‎02-05-2014

Re: Simplicity Studio HAL configuration Debug Level

In case someone is wondering, what you get from Debug Extended Library is API Trace events for all stack API calls, a couple of extra sanity checks (asserts) for some edge cases deep in the HAL/stack, and enabling of emberDebugPrintf() API calls for dedicated debug output via the binary debug channel (showing up as "Printf" events in the Network Analyzer event log).  What you get from Debug Basic Library is Virtual UART support (where available for your platform) on Serial 0 of the Console view, NodeInfo traces from a device when you first start a capture from it, and other output trace events logged to Network Analyzer for critical activities occurring in the firmware (e.g. Reset, CoreDump, Assert).

--------
The views represented in this post are the independent views of the author and don't necessarily represent the official views of Silicon Labs.