enable debug in thingy52

Question

Hello guys. 
 I'm new with nodic nRF52 SDK and I tried to enable debug by setting 1 on "NRF_LOG_ENABLED" in sdk_config.h, but nothing happens in com port criated by Jtag (pca10040). 
 Where is my error? What is the correctly procedure?

Bjørn Kvaale · Accepted Answer

Hi Leoni, 
 Unfortunately, the process is more difficult than this. You will need to first download the Thingy FW code , then take a look at this link to be able to compile the Thingy FW. This link then shows you how to compile the Thingy FW. Remember to set NRF_LOG_ENABLED 1 & NRF_LOG_BACKEND_RTT_ENABLED 1 in sdk_config.h header file to enable logging over RTT. I compiled the debug version of the Thingy FW. 
 Then, you have two options: the proper way via secure dfu bootloader or an easy solution. I would recommend the easy solution at the beginning. 
 The easy solution: Connect your Thingy:52 via a 10-pin SWD cable to the debug out port (P19) on an nrf52DK. Open nrf go studio (you can download it here ( 32 bit or 64 bit ) if you don't have it already). Turn the dev kit & the Thingy devices on. Click on the Segger tab under nrf52 dev boards in Device Manager. Press the erase all button. Click on the Program Softdevice tab & flash the Softdevice v4.0.2 (located here: thingy_fw\external\sdk13\components\softdevice\s132\hex 
). Then, press on the Program Application tab & flash the Thingy application hex file that you compiled in Keil or GCC. 
 Finally, open up the J-Link RTT Viewer program, change specify target device to the dev kit that you have & press the OK button. You should then get debug info via RTT.

Bjørn Kvaale · Answer

I was a bit unsure about what the DEBUG flag does, but it seems like it adds blocking asserts instead of a reset loop when something goes wrong in your code ( see link ). 
 Comparing the preprocessor symbols in Keil with the makefile located at: project\pca20020_s132\armgcc\, I noticed this:

The first picture shows the preprocessor definitions in Keil & the second picture shows the makefile. It seems the makefile sets a -D in front of the preprocessor definitions compared to Keil. If you go a bit further down, you notice that there is already a debug flag set at line 307: 
 ASMFLAGS += -DDEBUG 
 TLDR: The debug flag is already set in the makefile. You are good to go

enable debug in thingy52

Top Replies