BLE secure bootloader example can't output RTT log

[bijian]

I use PCA10040 V0.9.0 to run SDK15 bootloader example: F:\Nordic\nRF5_SDK_15.0.0_a53641a\examples\dfu\secure_bootloader\pca10040_ble_debug\arm5_no_packs.

1. erase full chip using nrfgo studio

2. compile this example

3. program softdevice

4. download this example

I find LED1 and LED2 is on, and BLE adv name is DfuTarg. And it is connectable. But there isn't any log in the RTT viewer! So what's the matter with this?

[Vidar Berg]

The debug example has RTT logging enabled by default so it should work. Did you remember to set the target interface to SWD in the RTT viewer configuration?

 

If that doesn't help, try to upload the .hex file below and see if you get the same result. It's merged with the softdevice so you don't need to program it separately.  

 

secure_bootloader_ble_s132_pca10040_debug.hex

 

[bijian]

It's still not worked,. And I also try different versions of  RTT viewer, but still no log. I try other examples in the SDK15, they have log. So what happened to the bootloader example?

[bijian]

I run the  \nRF5_SDK_15.0.0_a53641a\examples\dfu\secure_bootloader\pca10040_ble_debug\arm5_no_pack. And get this hex file,you may need to program softdevice first.

3000.nrf52832_xxaa_s132.hex

[Vidar Berg]

Here is part if the output I got after I programmed 3000.nrf52832_xxaa_s132.hex. Confirms that RTT logging is enabled at least. 

Suggest to try the following in case there is an issue with the RTT viewer:

• Open the keil project in \nRF5_SDK_15.0.0_a53641a\examples\dfu\secure_bootloader\pca10040_ble_debug\arm5_no_pack
• program Softdevice and bootlaoder
• Start a debug session in Keil
• Run JLinkRTTClient.exe and see if it displays the log messages

[bijian]

Yes, I got log when run JLinkRTTClient.exe. It's so strange. Maybe there are some unknown issues with my RTT viewer. When you run my hex file, do you get log from  your RTT viewer with your DK board?

[bijian]

Enter keil debug mode,then run RTT viewer,I got log. So It may be the segger jlink RTT's problem.

[bijian]

Now let me make a summary about my problem. RTT Viewer can be used stand-alone, opening an own connection to J-Link and target or in parallel to a running debug session, attaching to it and using this existing J-Link connection. when RTT Viewer is used stand-alone,there is not any log, and  it is used in parallel to a running debug session in keil, it can output log. I'm trying to solve this problem.

[Vidar Berg]

It does sound like RTT viewer problem. Have you tried to use upgrade to the latest version from Segger, and does it help if you do a pin reset while the RTT viewer is connected? 

[bijian]

Now there is log in RTT viewer suddenly. I don't remember what I changed make it work normally.  I'm trying to find what on earth cause this problem. So thank you for you help.

[bijian]

I think the problem is in your first Reply.The Target Device of my RTT viewer is NRF51822_XXAA, but I didn't realize this, because I seldom change this, I think it is NRF52832_XXAA by default . I should notice this first. I'm sorry about this.