|
44 | 44 | config TEXT_SECTION_OFFSET
|
45 | 45 | hex "TEXT section offset"
|
46 | 46 | default 0
|
| 47 | + default 0x200 if BOOTLOADER_MCUBOOT |
47 | 48 | help
|
48 |
| - This sets and offset before the text section and allows booting images |
49 |
| - with custom headers that are inserted at the beginning of the image. |
| 49 | + If the application is built for chain-loading by a bootloader this |
| 50 | + variable is required to be set to value that leaves sufficient |
| 51 | + space between the beginning of the image and the start of the .text |
| 52 | + section to store an image header or any other metadata. |
| 53 | + In the particular case of the MCUboot bootloader this reserves enough |
| 54 | + space to store the image header, which should also meet vector table |
| 55 | + alignment requirements on most ARM targets, although some targets |
| 56 | + may require smaller or larger values. |
50 | 57 |
|
51 | 58 | config HAVE_CUSTOM_LINKER_SCRIPT
|
52 | 59 | prompt "Custom linker scripts provided"
|
@@ -273,6 +280,16 @@ config BOOTLOADER_SRAM_SIZE
|
273 | 280 | This option specifies the amount of SRAM (measure in kB) reserved for
|
274 | 281 | when Zephyr is to act as a bootloader.
|
275 | 282 |
|
| 283 | +config BOOTLOADER_MCUBOOT |
| 284 | + bool |
| 285 | + prompt "MCUboot bootloader support" |
| 286 | + default n |
| 287 | + help |
| 288 | + This option signifies that the target uses MCUboot as a bootloader, |
| 289 | + or in other words that the image is to be chain-loaded by MCUboot. |
| 290 | + This sets several required options in order for the image generated |
| 291 | + to be bootable using the MCUboot open source bootloader. |
| 292 | + |
276 | 293 | config BOOTLOADER_KEXEC
|
277 | 294 | bool
|
278 | 295 | prompt "Boot using Linux kexec() system call"
|
|
0 commit comments