cannot see CRASHLOG with RTT viewer but can see CRASHLOG in SES ide debugger running

[ant]

I cannot see CRASHLOG with RTT viewer but can see CRASHLOG dumps when SES ide debugger is running.

Is there anything different from the SES ide debugger's dumb terminal and the RTT viewer?

How to see the CRASHLOG dumps in RTT viewer (not in SES debugger)  that the SES ide dumb terminal can readily print out when debugger is running?

[ant]

ok, I tried several times, and what worked to make the crashlog appear is after connecting the jlink and opening RTT viewer and the nrf52840 is at a good voltage level, ~2.8 V+, I wake up my board (by tapping it) and the crashlog shows up - but note that it did not show up the first time I applied good power level with RTT viewer connected

[Øyvind]

Hello,

My apologies for the late reply.  

ant said:

I wake up my board (by tapping it) and the crashlog shows up - but note that it did not show up the first time I applied good power level with RTT viewer connected

What do you mean by tapping it? What project are you using when enabling crash log?

[ant]

There's a motion sensor that sends an interrupt to wake up the nRF52840 by "tapping", it can be a strong "tap" depending on setting but that's not related to this discussion.

The key thing is that the CRASHLOG logging does not show up properly on the RTT viewer, it is truncated even though we increased the buffer size.  

Ideally, after the unit let's say detects a low voltage, it logs it, powers down, then when I plug in the j-link jtag cable onto the board, it wakes up the system and I see the print out of CRASHLOG without truncation. 

[Håkon Alseth]

Hi,

 

Could you share your sdk_config.h? If you're using NRF_LOG, then I'd recommend also upping the define "NRF_LOG_BUFSIZE" and see if this improves the scenario.

 

Kind regards,

Håkon