RTT Log with MCUBoot

RE: RTT Log with MCUBoot

Einar Thorsrud — Mon, 21 Aug 2023 08:41:29 GMT

Hi,

The file you use to update the application via DFU is app_update.bin.

RE: RTT Log with MCUBoot

thang47 — Mon, 21 Aug 2023 01:39:53 GMT

Hi,

Thank you, I flashed the wrong hex file, it should be merg.hex but I used MCUboot to DFU, which hex file to use for OTA. I tried the app_update file but it didn't work.

RE: RTT Log with MCUBoot

Einar Thorsrud — Fri, 18 Aug 2023 08:16:35 GMT

Can you elaborate more? Which exact hex file did you flash? (you need to flash both MCUboot and the signed application, or a merged hex file that includes both, which is simplest. This is called merge.hex. Is that what you flashed?

RE: RTT Log with MCUBoot

thang47 — Fri, 18 Aug 2023 07:18:23 GMT

I made 1 led blinking, but when I add the MCUboot configuration, the led no longer blinks.
I used J Flash and the project's hex file to load the nrf52840 module

RE: RTT Log with MCUBoot

thang47 — Fri, 18 Aug 2023 07:17:10 GMT

Hi,

My problem like the ticket: devzone.nordicsemi.com/.../enabling-mcuboot-does-not-run-application

RE: RTT Log with MCUBoot

Einar Thorsrud — Fri, 18 Aug 2023 07:11:59 GMT

Ah, I see. I focused on the RTT logging and did not notice that that was just a way you observed if the app was running, and that the difference was in adding MCUBoot.

A few questions to understand more

Did you program both MCUBoot and the signed application after having built the project with MCUBoot? (If so, the app should have started.)
Did you do any other changes?
Did you get any error or warnings when building or flashing?
How did you flash?
Have you done any debugging and what have you found out? What exactly does happen when you write "the chip doesn't run"? You could

RE: RTT Log with MCUBoot

thang47 — Fri, 18 Aug 2023 02:16:03 GMT

Hi,

But in my case the chip doesn't run after I add mcuboot configuration

RE: RTT Log with MCUBoot

Einar Thorsrud — Thu, 17 Aug 2023 11:20:12 GMT

Hi,

Is the problem here that you don't get RTT logs from the application when you have RTT logging enabled in MCUBoot? If so it could be that you are seeing a quite common issue, which is related to how the RTT viewer works. By default, it will search for the RTT buffer in memory, and stick with the first it finds. And the bootloader and application will typically not place the RTT buffer at the same location. In that case, you could manually specify where the buffer is as suggested in this post.