![]() If necessary, empty partitions are inserted in front of or behind the partition to ensure that the alignment is correct. "Ensure the alignment of the start or the end of the partition by specifying a dict with a start or end key respectively, where the value is the number of bytes to align to. ![]() Take a look at Partition Manager - Configuration file format - align:dict: Let me answer the question about the empty partitions first Is this a bug in the partition manager output? Could you please explain how to interpret the output. Nonetheless mcuboot is located at 0x18200: boot is successful. One looking at the partition manager report would expect mcuboot in slot 1 us located at 0x1c000 (s1_image, 48 kB). However, when B0 boots mcuboot from slot 1, it printsīut wait, according to the partition manager report 0x18200 is EMPTY_1. When B0 boots mcuboot from slot 0, it printsĪccording to the partition manager report, it is s0_image - mcuboot. Do they exist to fill in the gaps to make partitions aligned on the flash page boundaries? If so, is it possible to pick sizes such that there are no EMPTY_x areas? What are the EMPTY_0 and EMPTY_1 areas? I tried changing sizes of B0 and mcuboot partiions and these EMPTY_x areas seem to be moving around. I built peripheral_hr_coded sample and looking into the partition manager report (I trucated the output):
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |