NRF_LOG enabled on DFU BLE disables NRF_LOG in main application

RE: NRF_LOG enabled on DFU BLE disables NRF_LOG in main application

bjorn-spockeli — Fri, 25 May 2018 12:00:58 GMT

It could be that RTT_Viewer is using the wrong RTT structure in RAM, the bootloader will create one and the application will create one, and I think RTT viewer or similar will search first structure located in RAM which likely is the bootloader's.

RE: NRF_LOG enabled on DFU BLE disables NRF_LOG in main application

Eduardo Garcia — Wed, 23 May 2018 15:47:13 GMT

That is correct, however I tried typing "connect" and receive the "Warning: Sent 0 of 8 Bytes" error/issue.

RE: NRF_LOG enabled on DFU BLE disables NRF_LOG in main application

bjorn-spockeli — Wed, 23 May 2018 15:41:38 GMT

Eduardo Garcia: For now I prefer this solution than the link you provided as it fits more with our current system.

By solution, are you referring to the connect again suggestion by Andy?

RE: NRF_LOG enabled on DFU BLE disables NRF_LOG in main application

Eduardo Garcia — Tue, 22 May 2018 15:01:38 GMT

Hello:

Thank you for your response! I have tried what you said, but when I type something while on the application side I get a "Warning: Sent 0 of 8 Bytes". It seems the RTT is not sending anything while on the application! Is there any code that must be done on the App side to make this work?

For now I prefer this solution than the link you provided as it fits more with our current system.

Thanks!

RE: NRF_LOG enabled on DFU BLE disables NRF_LOG in main application

Andy — Mon, 21 May 2018 21:56:23 GMT

You can take a look at this post to make it work "more seamlessly": devzone.nordicsemi.com/.../easy-way-to-merge-bootloader-and-application-rtt-output

RE: NRF_LOG enabled on DFU BLE disables NRF_LOG in main application

Andy — Mon, 21 May 2018 21:54:07 GMT

That's normal. You just have to type "connect" again when the bootloader jumps to the main app.