BLE secure bootloader example can't output RTT log

RE: BLE secure bootloader example can't output RTT log

bijian — Thu, 07 Jun 2018 09:39:08 GMT

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.

RE: BLE secure bootloader example can't output RTT log

bijian — Thu, 07 Jun 2018 09:10:16 GMT

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.

RE: BLE secure bootloader example can't output RTT log

Vidar Berg — Thu, 07 Jun 2018 08:15:48 GMT

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?

RE: BLE secure bootloader example can't output RTT log

bijian — Thu, 07 Jun 2018 07:32:44 GMT

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.

RE: BLE secure bootloader example can't output RTT log

bijian — Thu, 07 Jun 2018 06:16:52 GMT

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

RE: BLE secure bootloader example can't output RTT log

bijian — Thu, 07 Jun 2018 00:18:01 GMT

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?

RE: BLE secure bootloader example can't output RTT log

Vidar Berg — Wed, 06 Jun 2018 11:27:29 GMT

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

RE: BLE secure bootloader example can't output RTT log

bijian — Wed, 06 Jun 2018 09:02:02 GMT

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.

devzone.nordicsemi.com/.../3000.nrf52832_5F00_xxaa_5F00_s132.hex

RE: BLE secure bootloader example can't output RTT log

Vidar Berg — Wed, 06 Jun 2018 08:53:05 GMT

Could you upload your bootloader .hex file so I can try it here? The bootloader uses the same logger module as the other SDK examples, so there shouldn't be any difference.

RE: BLE secure bootloader example can't output RTT log

bijian — Wed, 06 Jun 2018 02:17:31 GMT

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?

RE: BLE secure bootloader example can't output RTT log

Vidar Berg — Tue, 05 Jun 2018 06:35:55 GMT

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.

devzone.nordicsemi.com/.../secure_5F00_bootloader_5F00_ble_5F00_s132_5F00_pca10040_5F00_debug.hex