Debug

The method of capturing coexistence log is illustrated below:

For FreeRTOS

Tool

Ameba Trace Tool

AT cmd: AT+WLDBG=coex log FF

Coex Log for freertos is closed by default and use AT cmd “ AT+WLDBG=coex log FF “ in Trace tool can open and capture the log dynamically. AT cmd “ AT+WLDBG=coex log 0” can close the coex log.

Example

As shows, select and open the UART, then send AT cmd mentioned in 4.1.1.2, Trace Tool is ready to capture. After coex test, close the UART and then capture will be stopped, and click “Open Dir”, the log file “BT_xxxx_xx.bin” will show in directory.

Besides coex log file, we also need”COEX.trace”. When sdk image is built, “COEX.trace” will be generated in image directory of the wlan driver’s core. Use AmebaSmart as an example, if wlan driver’s core is KM4, the “COEX.trace” is in directory “amebasmart_gcc_project/project_np/asdk/image/” as follows .

For Linux

Tool

Any tool for serial port can capture Linux coex logs, include “Ameba Trace Tool”.

AT cmd: ATWZ dbg coex log FF

Coex Log for Linux is closed by default and use AT cmd “ ATWZ dbg coex log FF “ in Trace tool can open and capture the log dynamically. AT cmd “ ATWZ dbg coex log 0 “ can close the coex log.

Example

As shows, select and open the UART, then send AT cmd mentioned in 4.1.2.2, coex logs will be shown in tool.