Clarification on Bootloader on nRF52840

RE: Clarification on Bootloader on nRF52840

Einar Thorsrud — Tue, 29 Oct 2024 09:40:22 GMT

If you build a proejct with a bootloader, and look in the build folder, you will see that you have an MCUboot project as well as your application. From nRF Connect for VS Code, you can expand on the project, and you should see something like this (exactly how it looks depend a bit on SDK version and if you are using sysbuild or not, this screenshot is without sysbuild):

And in the same way, you can use the file explorer to look at it in the build folder, where you see MCUboot in addition to the application you are buildng where you included the bootloader to the project:

RE: Clarification on Bootloader on nRF52840

Yashaswini S — Tue, 29 Oct 2024 04:45:14 GMT

Hi,

The code for MCUboot is located under bootloader/mcuboot/.

This file will cannot see at project workspace.

I have shared file here, in that only can see child image cofiguration, here how it is linked to bootloader code.

RE: Clarification on Bootloader on nRF52840

Einar Thorsrud — Mon, 28 Oct 2024 13:02:34 GMT

When you configure your project to use a bootloader (or two if you use an upgradable bootlaoder), these bootloader(s) are added as child image(s). (Techincally this terminologi is used up to sysbuild which is the default from nRF Connect SDK 2.7.0, but the over al principle remains the same). If you look at the build process and the build output you will see that it is not just your application that is built, but also MCUboot, which is a separate project, but the build systsem handles it for you. The code for MCUboot is located under bootloader/mcuboot/.

[quote user=""]Another thing is How can we check the mcumgr commands are running, how it is taking via uart.[/quote]

Can you elaborate on this question?