https://devzone.nordicsemi.com/f/nordic-q-a/49715/how-to-see-log-in-bootloader-if-app-moves-into-bootloaderHello, Nordic. I use SDK15.3.0, s340 softdevice, nrf52840. Recently, I am testing dfu service. So I merge App, softdevice, and bootloader. Dfu service&#39;s test has done very well. But I don&#39;t see any Log in bootloader. I also use pca10056_ble_debugen-USTelligent Community 13Mon, 15 Jul 2019 11:47:15 GMThttps://devzone.nordicsemi.com/thread/198433?ContentTypeID=1Mon, 15 Jul 2019 11:47:15 GMT137ad170-7792-4731-bb38-c0d22fbe4515:e62b81c4-f62d-4922-9125-f8e0e0840857Vidar Berg<p>Hello,</p> <p>RTT uses a section of RAM to hold log messages which are accessed by the debugger. When you connect the debugger, it will automatically search through RAM to locate this block and start retrieving the log messages. The problem is that it&#39;s not stored at a fixed address, so the block will be placed at a new address when the device &quot;jumps&quot; from the bootloader to the application (and vice versa). The solution is to place it at a fixed address in your bootloader and application. Please refer to Hung&#39;s answer here:&nbsp;<a href="https://devzone.nordicsemi.com/f/nordic-q-a/20708/rtt-logging-from-application-started-by-bootloader/80814#80814">https://devzone.nordicsemi.com/f/nordic-q-a/20708/rtt-logging-from-application-started-by-bootloader/80814#80814</a>&nbsp;</p><div style="clear:both;"></div>