This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

ENABLE_TRACE

I have a Segger J-Trace Pro and am attempting to enable trace debugging of my application. I have a custom board that breakout out the appropriate Trace Clk and Trace Data[] signals. I have been reviewing the code to enable the ETM trace functionality. There seems to be support as part of the HAL:

https://github.com/NordicPlayground/fw-nrfconnect-zephyr/blob/master/ext/hal/nordic/nrfx/mdk/system_nrf9160.c#L164

The first issue was NRF_TAD_S->CLOCKSTART = TAD_CLOCKSTART_START_Msk not being defined. I found the definitions in both the manual and this file:

http://developer.nordicsemi.com/nRF_MDK/MDK_8_25_0/BSD/Files/nrf9160_bitfields.h

Then, ran into an issue with, (GPIO_PIN_CNF_MCUSEL_TND << GPIO_PIN_CNF_MCUSEL_Pos)

https://github.com/NordicPlayground/fw-nrfconnect-zephyr/blob/master/ext/hal/nordic/nrfx/mdk/system_nrf9160.c#L41

I could not find a definition for GPIO_PIN_CNF_MCUSEL_TND  anywhere including the nrf9160 product specification manual. Could you assist me in configuring the Trace properly to work with J-Trace and the Segger Ozone debugger?

Thank you,

Jonathan Mohlenhoff

Parents Reply Children
No Data
Related