NRF LOG + JLINKRTTClientExe

RE: NRF LOG + JLINKRTTClientExe

bjorn-spockeli — Mon, 11 Nov 2019 13:18:27 GMT

Hi Paul,

there are some users that have placed the Segger Control Block at a specific RAM address when they wanted to get RTT output from both the bootloader and application, see https://devzone.nordicsemi.com/f/nordic-q-a/20708/rtt-logging-from-application-started-by-bootloader/80812#80812

Best regards

Bjørn

RE: NRF LOG + JLINKRTTClientExe

BEplane — Mon, 11 Nov 2019 12:47:44 GMT

That makes sense to the problem I was seeing.

How would I go about making the module static? My initial guess is to change the RTT files to be static, or at leat the buffers. I am unsure of exactly what I would need to change for the module to be static and work through different uploads.

Thank you,

RE: NRF LOG + JLINKRTTClientExe

bjorn-spockeli — Mon, 11 Nov 2019 12:24:58 GMT

Hi Paul

[quote user=""]I have been connecting the JLinkExe, and the JLinkRTTExe in the terminal, then from there I go about loading software in SES, and debugging, adding breakpoints, loading changes. All without touching, or renewing the JLinkExe or JLinkRTTExe. Is this the expected workflow for using the RTT and NRF_LOG_INFO()? Or should the RTT be reconnected everytime I load new code?[/quote]

RTT uses a control block that is located in RAM on the target device, see this page for more information. Everytime you re-compile your code and flash it to the target, you are most likely also shifting the location of this control block. If this happens you will have to reconnect with Jlink. You can also place the control block at a static location in RAM so that the control block is at the same location all the time.

Best regards

Bjørn