bootloader debugging by using app_trace_log()

[Amy]

Hi,

I have some problems with bootloader debugging by using app_trace_log().

My board is pca10028, and I use the SDK 10.0.0 for it. The Keil version is v5.20 and Jlink version is v6.00d.

Since I am a beginner of BLE and Nordic Development, I tested the ble_app_uart_s110_pca10028 example code at first. And everything seems ok for me.

Then I added the app_trace.c, app_uart_fifo.c and other files needed into the bootloader example : dfu_fual_bank_ble_s110_pca10028, and added ENABLE_DEBUG_LOG_SUPPORT to the define list. I then added some log messages.

I compiled it successfully and load it into my board. After the bootloader started, the message I got from UART was like this:

I have looked a lot of posts but I could not solve this problem. The UART_TX_BUG_SIZE is 1024 witch is enough for my case.

How could I solve this problem to make it work?

Thank you.

[Amy]

Hi Hung, Thanks for your reply. I think my bootloader run correctly because I still can use it to do DFU and start the application( the hrs example code).

Since I need to use the DFU function in some reasons, I have to get familiar with it as soon as I can. That's why I am trying to print some debug messages at first.

And for the question F in FAQ part, I think I have already done it before, but I will give a check.

What if I use RTT for debugging? Is it more convenient and suitable? What is the best choice for me to print messages out?

Thank you=)