Documentation

Mistake on this page? Email us
Docs › Porting devices › Building and configuring Device Management Client › Error handling and debugging › Debugging devices running Izuma Device Management Client

Debugging devices running Izuma Device Management Client

Device Management Client comes with its own debug tracing, mbed-trace. You can activate the trace from the example application by defining it as a build time configuration.

To enable tracing in Mbed OS, change mbed-trace.enable in mbed-app.json from null to 1:

"mbed-trace.enable":1

To enable tracing in Linux, change the application's define.txt as follows:

add_definitions(-DMBED_CONF_MBED_TRACE_ENABLE=0)

to

add_definitions(-DMBED_CONF_MBED_TRACE_ENABLE=1)

Clean and recompile the application after the changes. In case of a PC build, re-generate the makefiles using CMAKE.

Serial communication settings for your terminal:

  • Baud rate: 115200.
  • All other settings: match the standard defaults: 8 bits, 1 stop bit, no parity (115200-8-N-1).

Tip: If you are using Mbed OS, familiarize yourself with the generic Mbed OS debugging documentation, or the tutorial on serial communication. If you are using Linux, GDB is a good tool for debugging call stacks and other backtrace call flows.

Previous