RTT viewer & interrupt

[Stayhungry]

Will uarte interrupt call NRF_LOG_INFO, will run away the possibility of the processor? backend uses RTT

I set uarte receive dma buffer to 10, then the sender to use the 1M baud rate, continue to send data, I log in the uarte interrupt, I found several times before the RTT Viewer shows is correct, behind an error, and lead to my Processor running lost. When I turn off the LOG information, all the data received properly.

Taking into account in addition to SD or RTT, no other interrupt will preempt the uarte interrupt, so I think it is not RTT problem?

[Sigurd]

Hi,

it's not recommended to use UART for retarget and nrf_log since there is no mechanism for managing access to uart. Make sure that you have NRF_LOG_BACKEND_UART_ENABLED set to 0 in sdk_config.h

[Stayhungry]

hi,sigurd. I'm pretty sure I'm using rtt instead of uart to log, and I'm just curious why calling the log in frequent interrupts causes the processor to run away, possibly a stack overflow or whatever. No matter what, turn off the interrupt log no problem ~ Continue to use the log in the main function or elsewhere no problem

[Sigurd]

What do you mean by "processor to run away" ? Where does it get stuck ? Have you tried debugging ?

What SDK version is this?