MCU hanging due to Segger RTT log

RE: MCU hanging due to Segger RTT log

Simonr — Thu, 26 Nov 2020 13:55:27 GMT

Seeing any log messages after setting NRF_LOG_ENABLED to 0 in your project should not be possible. Can you tell me more about your setup, as what you're describing sounds impossible. Are you using an nRF52 DK as a debugger? Are you sure that you're rebuilding and flashing the edited example every time you make any changes?

Also, what SDK example project is this based on? Are you able to recreate the behavior on a Development Kit?

Best regards,

Simon

RE: MCU hanging due to Segger RTT log

potter1234 — Thu, 26 Nov 2020 09:43:24 GMT

It is the nRF52840 you are referring to that keeps running, correct?

--> Yes, it was running but somehow it hanged after a few seconds. And nRF52840 would be normal after I reconnect to SEGGER RTT log again.

If you set the NRF_LOG_ENABLED to 0 are you able to see any log messages at all?

--> Yes, I can still see log printing even after setting it to 0

RE: MCU hanging due to Segger RTT log

Simonr — Wed, 25 Nov 2020 13:42:38 GMT

[quote user=""]if I disconnect my device to J-Link debugger, the mcu keeps running for around 10 seconds and then stops.[/quote]

It is the nRF52840 you are referring to that keeps running, correct?

I think the correct workaround would be to decrease the SEGGER_RTT_CONFIG_BUFFER_SIZE_DOWN (to 16) as this is what is used in most of our example projects. It might be that the MCU needs some time to go through the entirety buffer when this parameter is set too high.

If you set the NRF_LOG_ENABLED to 0 are you able to see any log messages at all?

Best regards,

Simon