Storage Partition Usage

I'm also wondering why there is 0x200 flash space not used between the end of the bootloader code and what appears to be the start of the application code. That is, looking at the map file for the application, the start address is listed as 0x0000C200. This should actually start at 0xC000 which is right after the bootloader. What is happening with these empty 0x200 byte buffer between the 2 images?

Thanks,

Pam Keiles

I'm also wondering why there is 0x200 flash space not used between the end of the bootloader code and what appears to be the start of the application code. That is, looking at the map file for the application, the start address is listed as 0x0000C200. This should actually start at 0xC000 which is right after the bootloader. What is happening with these empty 0x200 byte buffer between the 2 images?

Thanks,

Pam Keiles

Hi, 

What I am wondering is how the "storage partition" often defined in the device tree file for BLE solutions is used.

You can locate the build folder and type "ninja partition_manager_report". It will show the memory layout regarding build/partitions.yml.

pkeiles said:

I'm also wondering why there is 0x200 flash space not used between the end of the bootloader code and what appears to be the start of the application code.

Please provide the memory layout as I described above.

Regards,
Amanda

Thanks Amanda,

I was just curious what in the application typically uses the "storage partition" of the flash. I assume that if I remove it and some driver or support SDK code requires it then it will generate a build error. For now I am removing that section.

As for the 0x200 flash space I mentioned, it appears that is some sort of mcuboot pad flash area between the bootloader and application for some reason. I will continue to investigate how these sections are used on my side for now.

Thanks and regards,

Pam