https://devzone.nordicsemi.com/f/nordic-q-a/27733/rtt-viewer-interruptWill 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 severalen-USTelligent Community 13Mon, 04 Dec 2017 09:03:49 GMThttps://devzone.nordicsemi.com/thread/109449?ContentTypeID=1Mon, 04 Dec 2017 09:03:49 GMT137ad170-7792-4731-bb38-c0d22fbe4515:19096841-017d-4356-940c-7297602bfb2cSigurd<p>What do you mean by &quot;processor to run away&quot; ? Where does it get stuck ? Have you tried debugging ?</p> <p>What SDK version is this?</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/109448?ContentTypeID=1Fri, 01 Dec 2017 15:38:00 GMT137ad170-7792-4731-bb38-c0d22fbe4515:bff223a9-4205-49a6-8a56-ee464afabc30Stayhungry<p>hi,sigurd. I&#39;m pretty sure I&#39;m using rtt instead of uart to log, and I&#39;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</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/109447?ContentTypeID=1Fri, 01 Dec 2017 15:32:32 GMT137ad170-7792-4731-bb38-c0d22fbe4515:7e1766b0-6cf4-4980-ac8e-0d485a0eed53Sigurd<p>Hi,</p> <p>it&#39;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 <code>NRF_LOG_BACKEND_UART_ENABLED</code> set to 0 in sdk_config.h</p><div style="clear:both;"></div>