Simon Glass | cf29816 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 1 | menu "Boot options" |
| 2 | |
| 3 | menu "Boot images" |
| 4 | |
| 5 | config ANDROID_BOOT_IMAGE |
| 6 | bool "Enable support for Android Boot Images" |
| 7 | default y if FASTBOOT |
| 8 | help |
| 9 | This enables support for booting images which use the Android |
| 10 | image format header. |
| 11 | |
| 12 | config FIT |
| 13 | bool "Support Flattened Image Tree" |
Alexandru Gagniuc | 92055e1 | 2021-09-02 19:54:21 -0500 | [diff] [blame] | 14 | select HASH |
Simon Glass | cf29816 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 15 | select MD5 |
| 16 | select SHA1 |
Alexandru Gagniuc | eb5171d | 2021-09-02 19:54:17 -0500 | [diff] [blame] | 17 | imply SHA256 |
Simon Glass | cf29816 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 18 | help |
| 19 | This option allows you to boot the new uImage structure, |
| 20 | Flattened Image Tree. FIT is formally a FDT, which can include |
| 21 | images of various types (kernel, FDT blob, ramdisk, etc.) |
| 22 | in a single blob. To boot this new uImage structure, |
| 23 | pass the address of the blob to the "bootm" command. |
| 24 | FIT is very flexible, supporting compression, multiple images, |
| 25 | multiple configurations, verification through hashing and also |
| 26 | verified boot (secure boot using RSA). |
| 27 | |
Simon Glass | d6b318d | 2021-12-18 11:27:50 -0700 | [diff] [blame] | 28 | config TIMESTAMP |
| 29 | bool "Show image date and time when displaying image information" |
| 30 | default y if CMD_DATE |
| 31 | help |
| 32 | When CONFIG_TIMESTAMP is selected, the timestamp (date and time) of |
| 33 | an image is printed by image commands like bootm or iminfo. This |
| 34 | is shown as 'Timestamp: xxx' and 'Created: xxx'. If this option is |
| 35 | enabled, then U-Boot requires FITs to have a timestamp. If a FIT is |
| 36 | loaded that does not, the message 'Wrong FIT format: no timestamp' |
| 37 | is shown. |
| 38 | |
Simon Glass | cf29816 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 39 | if FIT |
| 40 | |
| 41 | config FIT_EXTERNAL_OFFSET |
| 42 | hex "FIT external data offset" |
| 43 | default 0x0 |
| 44 | help |
| 45 | This specifies a data offset in fit image. |
| 46 | The offset is from data payload offset to the beginning of |
| 47 | fit image header. When specifies a offset, specific data |
| 48 | could be put in the hole between data payload and fit image |
| 49 | header, such as CSF data on i.MX platform. |
| 50 | |
Simon Glass | 6f3c2d8 | 2021-02-15 17:08:10 -0700 | [diff] [blame] | 51 | config FIT_FULL_CHECK |
| 52 | bool "Do a full check of the FIT before using it" |
| 53 | default y |
| 54 | help |
| 55 | Enable this do a full check of the FIT to make sure it is valid. This |
| 56 | helps to protect against carefully crafted FITs which take advantage |
| 57 | of bugs or omissions in the code. This includes a bad structure, |
| 58 | multiple root nodes and the like. |
| 59 | |
Simon Glass | cf29816 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 60 | config FIT_SIGNATURE |
| 61 | bool "Enable signature verification of FIT uImages" |
| 62 | depends on DM |
| 63 | select HASH |
Alexandru Gagniuc | 61416fe | 2021-07-29 11:47:18 -0500 | [diff] [blame] | 64 | imply RSA |
| 65 | imply RSA_VERIFY |
Simon Glass | cf29816 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 66 | select IMAGE_SIGN_INFO |
Simon Glass | 6f3c2d8 | 2021-02-15 17:08:10 -0700 | [diff] [blame] | 67 | select FIT_FULL_CHECK |
Simon Glass | cf29816 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 68 | help |
| 69 | This option enables signature verification of FIT uImages, |
| 70 | using a hash signed and verified using RSA. If |
| 71 | CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive |
| 72 | hashing is available using hardware, then the RSA library will use |
| 73 | it. See doc/uImage.FIT/signature.txt for more details. |
| 74 | |
| 75 | WARNING: When relying on signed FIT images with a required signature |
| 76 | check the legacy image format is disabled by default, so that |
| 77 | unsigned images cannot be loaded. If a board needs the legacy image |
| 78 | format support in this case, enable it using |
| 79 | CONFIG_LEGACY_IMAGE_FORMAT. |
| 80 | |
| 81 | config FIT_SIGNATURE_MAX_SIZE |
| 82 | hex "Max size of signed FIT structures" |
| 83 | depends on FIT_SIGNATURE |
| 84 | default 0x10000000 |
| 85 | help |
| 86 | This option sets a max size in bytes for verified FIT uImages. |
| 87 | A sane value of 256MB protects corrupted DTB structures from overlapping |
| 88 | device memory. Assure this size does not extend past expected storage |
| 89 | space. |
| 90 | |
Simon Glass | ad74aed | 2021-07-14 17:05:31 -0500 | [diff] [blame] | 91 | config FIT_RSASSA_PSS |
Simon Glass | cf29816 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 92 | bool "Support rsassa-pss signature scheme of FIT image contents" |
| 93 | depends on FIT_SIGNATURE |
Simon Glass | cf29816 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 94 | help |
| 95 | Enable this to support the pss padding algorithm as described |
| 96 | in the rfc8017 (https://tools.ietf.org/html/rfc8017). |
| 97 | |
| 98 | config FIT_CIPHER |
| 99 | bool "Enable ciphering data in a FIT uImages" |
| 100 | depends on DM |
| 101 | select AES |
| 102 | help |
| 103 | Enable the feature of data ciphering/unciphering in the tool mkimage |
| 104 | and in the u-boot support of the FIT image. |
| 105 | |
| 106 | config FIT_VERBOSE |
| 107 | bool "Show verbose messages when FIT images fail" |
| 108 | help |
| 109 | Generally a system will have valid FIT images so debug messages |
| 110 | are a waste of code space. If you are debugging your images then |
| 111 | you can enable this option to get more verbose information about |
| 112 | failures. |
| 113 | |
| 114 | config FIT_BEST_MATCH |
| 115 | bool "Select the best match for the kernel device tree" |
| 116 | help |
| 117 | When no configuration is explicitly selected, default to the |
| 118 | one whose fdt's compatibility field best matches that of |
| 119 | U-Boot itself. A match is considered "best" if it matches the |
| 120 | most specific compatibility entry of U-Boot's fdt's root node. |
| 121 | The order of entries in the configuration's fdt is ignored. |
| 122 | |
| 123 | config FIT_IMAGE_POST_PROCESS |
| 124 | bool "Enable post-processing of FIT artifacts after loading by U-Boot" |
Siew Chin Lim | 1bc2089 | 2021-03-01 20:04:11 +0800 | [diff] [blame] | 125 | depends on TI_SECURE_DEVICE || SOCFPGA_SECURE_VAB_AUTH |
Andrew Davis | 042e87e | 2022-05-04 15:52:28 -0500 | [diff] [blame] | 126 | default y if TI_SECURE_DEVICE |
Simon Glass | cf29816 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 127 | help |
| 128 | Allows doing any sort of manipulation to blobs after they got extracted |
| 129 | from FIT images like stripping off headers or modifying the size of the |
| 130 | blob, verification, authentication, decryption etc. in a platform or |
| 131 | board specific way. In order to use this feature a platform or board- |
| 132 | specific implementation of board_fit_image_post_process() must be |
| 133 | provided. Also, anything done during this post-processing step would |
| 134 | need to be comprehended in how the images were prepared before being |
| 135 | injected into the FIT creation (i.e. the blobs would have been pre- |
| 136 | processed before being added to the FIT image). |
| 137 | |
Ravik Hasija | 7a01882 | 2021-01-27 14:01:48 -0800 | [diff] [blame] | 138 | config FIT_PRINT |
| 139 | bool "Support FIT printing" |
| 140 | default y |
| 141 | help |
| 142 | Support printing the content of the fitImage in a verbose manner. |
| 143 | |
Simon Glass | cf29816 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 144 | if SPL |
| 145 | |
| 146 | config SPL_FIT |
| 147 | bool "Support Flattened Image Tree within SPL" |
| 148 | depends on SPL |
Alexandru Gagniuc | 92055e1 | 2021-09-02 19:54:21 -0500 | [diff] [blame] | 149 | select SPL_HASH |
Simon Glass | cf29816 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 150 | select SPL_OF_LIBFDT |
| 151 | |
| 152 | config SPL_FIT_PRINT |
| 153 | bool "Support FIT printing within SPL" |
| 154 | depends on SPL_FIT |
| 155 | help |
| 156 | Support printing the content of the fitImage in a verbose manner in SPL. |
| 157 | |
Simon Glass | 6f3c2d8 | 2021-02-15 17:08:10 -0700 | [diff] [blame] | 158 | config SPL_FIT_FULL_CHECK |
| 159 | bool "Do a full check of the FIT before using it" |
| 160 | help |
| 161 | Enable this do a full check of the FIT to make sure it is valid. This |
| 162 | helps to protect against carefully crafted FITs which take advantage |
| 163 | of bugs or omissions in the code. This includes a bad structure, |
| 164 | multiple root nodes and the like. |
| 165 | |
| 166 | |
Simon Glass | cf29816 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 167 | config SPL_FIT_SIGNATURE |
| 168 | bool "Enable signature verification of FIT firmware within SPL" |
| 169 | depends on SPL_DM |
Klaus Heinrich Kiwi | bdb7f26 | 2021-02-09 15:41:54 -0300 | [diff] [blame] | 170 | depends on SPL_LOAD_FIT || SPL_LOAD_FIT_FULL |
Klaus Heinrich Kiwi | 6ce2813 | 2021-02-09 15:41:53 -0300 | [diff] [blame] | 171 | select FIT_SIGNATURE |
Simon Glass | cf29816 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 172 | select SPL_FIT |
Simon Glass | 0c6bdbb | 2021-07-10 21:14:25 -0600 | [diff] [blame] | 173 | select SPL_CRYPTO |
Alexandru Gagniuc | 0721209 | 2021-09-02 19:54:19 -0500 | [diff] [blame] | 174 | select SPL_HASH |
Alexandru Gagniuc | 61416fe | 2021-07-29 11:47:18 -0500 | [diff] [blame] | 175 | imply SPL_RSA |
| 176 | imply SPL_RSA_VERIFY |
Simon Glass | cf29816 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 177 | select SPL_IMAGE_SIGN_INFO |
Simon Glass | 6f3c2d8 | 2021-02-15 17:08:10 -0700 | [diff] [blame] | 178 | select SPL_FIT_FULL_CHECK |
Simon Glass | cf29816 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 179 | |
Simon Glass | b53541f | 2021-09-25 19:43:39 -0600 | [diff] [blame] | 180 | config SPL_FIT_SIGNATURE_MAX_SIZE |
| 181 | hex "Max size of signed FIT structures in SPL" |
| 182 | depends on SPL_FIT_SIGNATURE |
| 183 | default 0x10000000 |
| 184 | help |
| 185 | This option sets a max size in bytes for verified FIT uImages. |
| 186 | A sane value of 256MB protects corrupted DTB structures from overlapping |
| 187 | device memory. Assure this size does not extend past expected storage |
| 188 | space. |
| 189 | |
Philippe Reynes | 5d39c93 | 2021-10-15 11:35:03 +0200 | [diff] [blame] | 190 | config SPL_FIT_RSASSA_PSS |
| 191 | bool "Support rsassa-pss signature scheme of FIT image contents in SPL" |
| 192 | depends on SPL_FIT_SIGNATURE |
| 193 | help |
| 194 | Enable this to support the pss padding algorithm as described |
| 195 | in the rfc8017 (https://tools.ietf.org/html/rfc8017) in SPL. |
| 196 | |
Simon Glass | cf29816 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 197 | config SPL_LOAD_FIT |
| 198 | bool "Enable SPL loading U-Boot as a FIT (basic fitImage features)" |
| 199 | select SPL_FIT |
| 200 | help |
| 201 | Normally with the SPL framework a legacy image is generated as part |
| 202 | of the build. This contains U-Boot along with information as to |
| 203 | where it should be loaded. This option instead enables generation |
| 204 | of a FIT (Flat Image Tree) which provides more flexibility. In |
| 205 | particular it can handle selecting from multiple device tree |
| 206 | and passing the correct one to U-Boot. |
| 207 | |
Alexandru Gagniuc | df51ae7 | 2021-03-29 12:05:15 -0500 | [diff] [blame] | 208 | This path has the following limitations: |
| 209 | |
Bin Meng | 6e847f6 | 2021-05-10 20:23:29 +0800 | [diff] [blame] | 210 | 1. "loadables" images, other than FDTs, which do not have a "load" |
Alexandru Gagniuc | df51ae7 | 2021-03-29 12:05:15 -0500 | [diff] [blame] | 211 | property will not be loaded. This limitation also applies to FPGA |
| 212 | images with the correct "compatible" string. |
Oleksandr Suvorov | a3a1afb | 2022-07-22 17:16:13 +0300 | [diff] [blame] | 213 | 2. For FPGA images, the supported "compatible" list is in the |
| 214 | doc/uImage.FIT/source_file_format.txt. |
Alexandru Gagniuc | df51ae7 | 2021-03-29 12:05:15 -0500 | [diff] [blame] | 215 | 3. FDTs are only loaded for images with an "os" property of "u-boot". |
| 216 | "linux" images are also supported with Falcon boot mode. |
| 217 | |
Simon Glass | cf29816 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 218 | config SPL_LOAD_FIT_ADDRESS |
| 219 | hex "load address of fit image" |
| 220 | depends on SPL_LOAD_FIT |
| 221 | default 0x0 |
| 222 | help |
| 223 | Specify the load address of the fit image that will be loaded |
| 224 | by SPL. |
| 225 | |
| 226 | config SPL_LOAD_FIT_APPLY_OVERLAY |
| 227 | bool "Enable SPL applying DT overlays from FIT" |
| 228 | depends on SPL_LOAD_FIT |
| 229 | select OF_LIBFDT_OVERLAY |
| 230 | help |
| 231 | The device tree is loaded from the FIT image. Allow the SPL is to |
| 232 | also load device-tree overlays from the FIT image an apply them |
| 233 | over the device tree. |
| 234 | |
| 235 | config SPL_LOAD_FIT_APPLY_OVERLAY_BUF_SZ |
| 236 | depends on SPL_LOAD_FIT_APPLY_OVERLAY |
| 237 | default 0x10000 |
| 238 | hex "size of temporary buffer used to load the overlays" |
| 239 | help |
| 240 | The size of the area where the overlays will be loaded and |
| 241 | uncompress. Must be at least as large as biggest overlay |
| 242 | (uncompressed) |
| 243 | |
| 244 | config SPL_LOAD_FIT_FULL |
| 245 | bool "Enable SPL loading U-Boot as a FIT (full fitImage features)" |
| 246 | select SPL_FIT |
| 247 | help |
| 248 | Normally with the SPL framework a legacy image is generated as part |
| 249 | of the build. This contains U-Boot along with information as to |
| 250 | where it should be loaded. This option instead enables generation |
| 251 | of a FIT (Flat Image Tree) which provides more flexibility. In |
| 252 | particular it can handle selecting from multiple device tree |
| 253 | and passing the correct one to U-Boot. |
| 254 | |
| 255 | config SPL_FIT_IMAGE_POST_PROCESS |
| 256 | bool "Enable post-processing of FIT artifacts after loading by the SPL" |
| 257 | depends on SPL_LOAD_FIT |
Andrew Davis | 042e87e | 2022-05-04 15:52:28 -0500 | [diff] [blame] | 258 | default y if TI_SECURE_DEVICE |
Simon Glass | cf29816 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 259 | help |
| 260 | Allows doing any sort of manipulation to blobs after they got extracted |
| 261 | from the U-Boot FIT image like stripping off headers or modifying the |
| 262 | size of the blob, verification, authentication, decryption etc. in a |
| 263 | platform or board specific way. In order to use this feature a platform |
| 264 | or board-specific implementation of board_fit_image_post_process() must |
| 265 | be provided. Also, anything done during this post-processing step would |
| 266 | need to be comprehended in how the images were prepared before being |
| 267 | injected into the FIT creation (i.e. the blobs would have been pre- |
| 268 | processed before being added to the FIT image). |
| 269 | |
| 270 | config SPL_FIT_SOURCE |
| 271 | string ".its source file for U-Boot FIT image" |
| 272 | depends on SPL_FIT |
| 273 | help |
| 274 | Specifies a (platform specific) FIT source file to generate the |
| 275 | U-Boot FIT image. This could specify further image to load and/or |
| 276 | execute. |
| 277 | |
| 278 | config USE_SPL_FIT_GENERATOR |
| 279 | bool "Use a script to generate the .its script" |
Bin Meng | 84dee33 | 2021-05-10 20:23:41 +0800 | [diff] [blame] | 280 | default y if SPL_FIT && (!ARCH_SUNXI && !RISCV) |
Simon Glass | cf29816 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 281 | |
| 282 | config SPL_FIT_GENERATOR |
| 283 | string ".its file generator script for U-Boot FIT image" |
| 284 | depends on USE_SPL_FIT_GENERATOR |
| 285 | default "arch/arm/mach-rockchip/make_fit_atf.py" if SPL_LOAD_FIT && ARCH_ROCKCHIP |
| 286 | default "arch/arm/mach-zynqmp/mkimage_fit_atf.sh" if SPL_LOAD_FIT && ARCH_ZYNQMP |
Simon Glass | cf29816 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 287 | help |
| 288 | Specifies a (platform specific) script file to generate the FIT |
| 289 | source file used to build the U-Boot FIT image file. This gets |
| 290 | passed a list of supported device tree file stub names to |
| 291 | include in the generated image. |
| 292 | |
| 293 | endif # SPL |
| 294 | |
| 295 | endif # FIT |
| 296 | |
Simon Glass | ef5e389 | 2022-04-24 23:31:06 -0600 | [diff] [blame] | 297 | config BOOTSTD |
| 298 | bool "Standard boot support" |
| 299 | default y |
| 300 | depends on DM && OF_CONTROL && BLK |
| 301 | help |
| 302 | U-Boot supports a standard way of locating something to boot, |
| 303 | typically an Operating System such as Linux, provided by a distro such |
| 304 | as Arch Linux or Debian. Enable this to support iterating through |
| 305 | available bootdevs and using bootmeths to find bootflows suitable for |
| 306 | booting. |
| 307 | |
| 308 | Standard boot is not a standard way of booting, just a framework |
| 309 | within U-Boot for supporting all the different ways that exist. |
| 310 | |
| 311 | Terminology: |
| 312 | |
| 313 | - bootdev - a device which can hold a distro (e.g. MMC) |
| 314 | - bootmeth - a method to scan a bootdev to find bootflows (owned by |
| 315 | U-Boot) |
| 316 | - bootflow - a description of how to boot (owned by the distro) |
| 317 | |
| 318 | config BOOTSTD_FULL |
| 319 | bool "Enhanced features for standard boot" |
| 320 | default y if SANDBOX |
| 321 | help |
| 322 | This enables various useful features for standard boot, which are not |
| 323 | essential for operation: |
| 324 | |
| 325 | - bootdev, bootmeth commands |
| 326 | - extra features in the bootflow command |
| 327 | - support for selecting the ordering of bootmeths ("bootmeth order") |
| 328 | - support for selecting the ordering of bootdevs using the devicetree |
| 329 | as well as the "boot_targets" environment variable |
| 330 | |
Simon Glass | 31aefaf | 2022-04-24 23:31:13 -0600 | [diff] [blame] | 331 | if BOOTSTD |
| 332 | |
Simon Glass | a91492b | 2022-04-24 23:31:27 -0600 | [diff] [blame] | 333 | config BOOTSTD_BOOTCOMMAND |
| 334 | bool "Use bootstd to boot" |
| 335 | default y if !DISTRO_DEFAULTS |
| 336 | help |
| 337 | Enable this to select a default boot-command suitable for booting |
| 338 | with standard boot. This can be overridden by the board if needed, |
| 339 | but the default command should be enough for most boards which use |
| 340 | standard boot. |
| 341 | |
| 342 | For now this is only selected if distro boot is NOT used, since |
| 343 | standard boot does not support all of the features of distro boot |
| 344 | yet. |
| 345 | |
Simon Glass | 31aefaf | 2022-04-24 23:31:13 -0600 | [diff] [blame] | 346 | config BOOTMETH_DISTRO |
| 347 | bool "Bootdev support for distro boot" |
| 348 | depends on CMD_PXE |
| 349 | default y |
| 350 | help |
| 351 | Enables support for distro boot using bootdevs. This makes the |
| 352 | bootdevs look for a 'extlinux/extlinux.conf' on each filesystem |
| 353 | they scan. |
| 354 | |
| 355 | This provides a way to try out standard boot on an existing boot flow. |
| 356 | |
Simon Glass | dab2c28 | 2022-04-24 23:31:16 -0600 | [diff] [blame] | 357 | config BOOTMETH_DISTRO_PXE |
| 358 | bool "Bootdev support for distro boot over network" |
| 359 | depends on CMD_PXE && CMD_NET && DM_ETH |
| 360 | default y |
| 361 | help |
| 362 | Enables support for distro boot using bootdevs. This makes the |
| 363 | bootdevs look for a 'extlinux/extlinux.conf' on the tftp server. |
| 364 | |
| 365 | This provides a way to try out standard boot on an existing boot flow. |
| 366 | |
Simon Glass | acfa9bd | 2022-04-24 23:31:17 -0600 | [diff] [blame] | 367 | config BOOTMETH_EFILOADER |
| 368 | bool "Bootdev support for EFI boot" |
| 369 | depends on CMD_BOOTEFI |
| 370 | default y |
| 371 | help |
| 372 | Enables support for EFI boot using bootdevs. This makes the |
| 373 | bootdevs look for a 'boot<arch>.efi' on each filesystem |
| 374 | they scan. The resulting file is booted after enabling U-Boot's |
| 375 | EFI loader support. |
| 376 | |
| 377 | The <arch> depends on the architecture of the board: |
| 378 | |
| 379 | aa64 - aarch64 (ARM 64-bit) |
| 380 | arm - ARM 32-bit |
| 381 | ia32 - x86 32-bit |
| 382 | x64 - x86 64-bit |
| 383 | riscv32 - RISC-V 32-bit |
| 384 | riscv64 - RISC-V 64-bit |
| 385 | |
| 386 | This provides a way to try out standard boot on an existing boot flow. |
| 387 | |
Simon Glass | 126947b | 2022-04-24 23:31:20 -0600 | [diff] [blame] | 388 | config BOOTMETH_SANDBOX |
| 389 | def_bool y |
| 390 | depends on SANDBOX |
| 391 | help |
| 392 | This is a sandbox bootmeth driver used for testing. It always returns |
| 393 | -ENOTSUPP when attempting to boot. |
| 394 | |
Simon Glass | d940924 | 2022-04-24 23:31:22 -0600 | [diff] [blame] | 395 | config BOOTMETH_SCRIPT |
| 396 | bool "Bootdev support for U-Boot scripts" |
| 397 | default y if BOOTSTD_FULL |
| 398 | help |
| 399 | Enables support for booting a distro via a U-Boot script. This makes |
| 400 | the bootdevs look for a 'boot/boot.scr' file which can be used to |
| 401 | boot the distro. |
| 402 | |
| 403 | This provides a way to try out standard boot on an existing boot flow. |
| 404 | It is not enabled by default to save space. |
| 405 | |
Simon Glass | 31aefaf | 2022-04-24 23:31:13 -0600 | [diff] [blame] | 406 | endif |
| 407 | |
Simon Glass | cf29816 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 408 | config LEGACY_IMAGE_FORMAT |
| 409 | bool "Enable support for the legacy image format" |
Andrew Davis | 52dc334 | 2022-05-04 15:52:27 -0500 | [diff] [blame] | 410 | default y if !FIT_SIGNATURE && !TI_SECURE_DEVICE |
Simon Glass | cf29816 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 411 | help |
| 412 | This option enables the legacy image format. It is enabled by |
| 413 | default for backward compatibility, unless FIT_SIGNATURE is |
| 414 | set where it is disabled so that unsigned images cannot be |
| 415 | loaded. If a board needs the legacy image format support in this |
| 416 | case, enable it here. |
| 417 | |
Simon Glass | aefa34f | 2020-09-10 20:21:19 -0600 | [diff] [blame] | 418 | config SUPPORT_RAW_INITRD |
| 419 | bool "Enable raw initrd images" |
| 420 | help |
| 421 | Note, defining the SUPPORT_RAW_INITRD allows user to supply |
| 422 | kernel with raw initrd images. The syntax is slightly different, the |
| 423 | address of the initrd must be augmented by it's size, in the following |
| 424 | format: "<initrd address>:<initrd size>". |
| 425 | |
Simon Glass | cf29816 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 426 | config OF_BOARD_SETUP |
| 427 | bool "Set up board-specific details in device tree before boot" |
| 428 | depends on OF_LIBFDT |
| 429 | help |
| 430 | This causes U-Boot to call ft_board_setup() before booting into |
| 431 | the Operating System. This function can set up various |
| 432 | board-specific information in the device tree for use by the OS. |
| 433 | The device tree is then passed to the OS. |
| 434 | |
| 435 | config OF_SYSTEM_SETUP |
| 436 | bool "Set up system-specific details in device tree before boot" |
| 437 | depends on OF_LIBFDT |
| 438 | help |
| 439 | This causes U-Boot to call ft_system_setup() before booting into |
| 440 | the Operating System. This function can set up various |
| 441 | system-specific information in the device tree for use by the OS. |
| 442 | The device tree is then passed to the OS. |
| 443 | |
| 444 | config OF_STDOUT_VIA_ALIAS |
| 445 | bool "Update the device-tree stdout alias from U-Boot" |
| 446 | depends on OF_LIBFDT |
| 447 | help |
| 448 | This uses U-Boot's serial alias from the aliases node to update |
| 449 | the device tree passed to the OS. The "linux,stdout-path" property |
| 450 | in the chosen node is set to point to the correct serial node. |
| 451 | This option currently references CONFIG_CONS_INDEX, which is |
| 452 | incorrect when used with device tree as this option does not |
| 453 | exist / should not be used. |
| 454 | |
Tom Rini | 25b8ace | 2022-04-02 18:18:57 -0400 | [diff] [blame] | 455 | config SYS_EXTRA_OPTIONS |
| 456 | string "Extra Options (DEPRECATED)" |
| 457 | help |
| 458 | The old configuration infrastructure (= mkconfig + boards.cfg) |
| 459 | provided the extra options field. If you have something like |
| 460 | "HAS_BAR,BAZ=64", the optional options |
| 461 | #define CONFIG_HAS |
| 462 | #define CONFIG_BAZ 64 |
| 463 | will be defined in include/config.h. |
| 464 | This option was prepared for the smooth migration from the old |
| 465 | configuration to Kconfig. Since this option will be removed sometime, |
| 466 | new boards should not use this option. |
| 467 | |
Simon Glass | cf29816 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 468 | config HAVE_SYS_TEXT_BASE |
| 469 | bool |
| 470 | depends on !NIOS2 && !XTENSA |
| 471 | depends on !EFI_APP |
| 472 | default y |
| 473 | |
| 474 | config SYS_TEXT_BASE |
| 475 | depends on HAVE_SYS_TEXT_BASE |
Tom Rini | 55adabb | 2021-07-09 10:39:21 -0400 | [diff] [blame] | 476 | default 0x0 if POSITION_INDEPENDENT |
Simon Glass | cf29816 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 477 | default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3 |
Icenowy Zheng | b6ffd58 | 2022-01-29 10:23:09 -0500 | [diff] [blame] | 478 | default 0x81700000 if MACH_SUNIV |
| 479 | default 0x2a000000 if MACH_SUN9I |
| 480 | default 0x42e00000 if MACH_SUN8I_V3S |
| 481 | default 0x4a000000 if ARCH_SUNXI |
Simon Glass | cf29816 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 482 | hex "Text Base" |
| 483 | help |
| 484 | The address in memory that U-Boot will be running from, initially. |
| 485 | |
Tom Rini | e4d741f | 2022-03-24 17:18:05 -0400 | [diff] [blame] | 486 | config HAVE_SYS_MONITOR_BASE |
| 487 | bool |
| 488 | depends on ARC || MIPS || M68K || NIOS2 || PPC || XTENSA || X86 \ |
Tom Rini | cc1015f | 2022-07-23 13:05:01 -0400 | [diff] [blame] | 489 | || ENV_IS_IN_FLASH || MTD_NOR_FLASH |
Tom Rini | e4d741f | 2022-03-24 17:18:05 -0400 | [diff] [blame] | 490 | depends on !EFI_APP |
| 491 | default y |
| 492 | |
| 493 | config SYS_MONITOR_BASE |
| 494 | depends on HAVE_SYS_MONITOR_BASE |
| 495 | hex "Physical start address of boot monitor code" |
| 496 | default SYS_TEXT_BASE |
| 497 | help |
| 498 | The physical start address of boot monitor code (which is the same as |
| 499 | CONFIG_SYS_TEXT_BASE when linking) and the same as CONFIG_SYS_FLASH_BASE |
| 500 | when booting from flash. |
| 501 | |
| 502 | config SPL_SYS_MONITOR_BASE |
| 503 | depends on MPC85xx && SPL && HAVE_SYS_MONITOR_BASE |
| 504 | hex "Physical start address of SPL monitor code" |
| 505 | default SPL_TEXT_BASE |
| 506 | |
| 507 | config TPL_SYS_MONITOR_BASE |
| 508 | depends on MPC85xx && TPL && HAVE_SYS_MONITOR_BASE |
| 509 | hex "Physical start address of TPL monitor code" |
| 510 | |
Tom Rini | 2f8a6db | 2021-12-14 13:36:40 -0500 | [diff] [blame] | 511 | config DYNAMIC_SYS_CLK_FREQ |
| 512 | bool "Determine CPU clock frequency at run-time" |
Simon Glass | cf29816 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 513 | help |
Tom Rini | 2f8a6db | 2021-12-14 13:36:40 -0500 | [diff] [blame] | 514 | Implement a get_board_sys_clk function that will determine the CPU |
| 515 | clock frequency at run time, rather than define it statically. |
| 516 | |
| 517 | config SYS_CLK_FREQ |
| 518 | depends on !DYNAMIC_SYS_CLK_FREQ |
| 519 | int "CPU clock frequency" |
| 520 | default 125000000 if ARCH_LS1012A |
| 521 | default 100000000 if ARCH_P2020 || ARCH_T1024 || ARCH_T1042 || \ |
| 522 | ARCH_LS1021A || FSL_LSCH2 || FSL_LSCH3 |
| 523 | default 66666666 if ARCH_P1010 || ARCH_P1020 || ARCH_T4240 |
| 524 | default 66660000 if ARCH_T2080 |
| 525 | default 33333333 if RCAR_GEN3 |
| 526 | default 24000000 if ARCH_EXYNOS |
| 527 | default 20000000 if RCAR_GEN2 |
| 528 | default 0 |
| 529 | help |
| 530 | A static value for the CPU frequency. Note that if not required |
| 531 | for a given SoC, this can be left at 0. |
Simon Glass | cf29816 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 532 | |
| 533 | config ARCH_FIXUP_FDT_MEMORY |
| 534 | bool "Enable arch_fixup_memory_banks() call" |
| 535 | default y |
| 536 | help |
| 537 | Enable FDT memory map syncup before OS boot. This feature can be |
| 538 | used for booting OS with different memory setup where the part of |
| 539 | the memory location should be used for different purpose. |
| 540 | |
Simon Glass | 96d0aa9 | 2020-11-04 09:57:35 -0700 | [diff] [blame] | 541 | config CHROMEOS |
| 542 | bool "Support booting Chrome OS" |
| 543 | help |
| 544 | Chrome OS requires U-Boot to set up a table indicating the boot mode |
| 545 | (e.g. Developer mode) and a few other things. Enable this if you are |
| 546 | booting on a Chromebook to avoid getting an error about an invalid |
| 547 | firmware ID. |
| 548 | |
| 549 | config CHROMEOS_VBOOT |
| 550 | bool "Support Chrome OS verified boot" |
| 551 | help |
| 552 | This is intended to enable the full Chrome OS verified boot support |
| 553 | in U-Boot. It is not actually implemented in the U-Boot source code |
| 554 | at present, so this option is always set to 'n'. It allows |
| 555 | distinguishing between booting Chrome OS in a basic way (developer |
| 556 | mode) and a full boot. |
| 557 | |
Tom Rini | 5a44618 | 2022-06-25 11:02:44 -0400 | [diff] [blame] | 558 | config SYS_RAMBOOT |
| 559 | bool |
| 560 | |
Tom Rini | d8ef01e | 2021-08-24 23:11:49 -0400 | [diff] [blame] | 561 | config RAMBOOT_PBL |
| 562 | bool "Freescale PBL(pre-boot loader) image format support" |
Tom Rini | 5a44618 | 2022-06-25 11:02:44 -0400 | [diff] [blame] | 563 | select SYS_RAMBOOT if PPC |
Tom Rini | d8ef01e | 2021-08-24 23:11:49 -0400 | [diff] [blame] | 564 | help |
| 565 | Some SoCs use PBL to load RCW and/or pre-initialization instructions. |
| 566 | For more details refer to doc/README.pblimage |
| 567 | |
Tom Rini | d433c74 | 2022-03-23 17:20:03 -0400 | [diff] [blame] | 568 | choice |
| 569 | prompt "Freescale PBL load location" |
| 570 | depends on RAMBOOT_PBL || ((TARGET_P1010RDB_PA || TARGET_P1010RDB_PB \ |
| 571 | || TARGET_P1020RDB_PC || TARGET_P1020RDB_PD || TARGET_P2020RDB) \ |
| 572 | && !CMD_NAND) |
| 573 | |
| 574 | config SDCARD |
| 575 | bool "Freescale PBL is found on SD card" |
| 576 | |
| 577 | config SPIFLASH |
| 578 | bool "Freescale PBL is found on SPI flash" |
| 579 | |
| 580 | endchoice |
| 581 | |
Tom Rini | d8e8461 | 2022-06-20 08:07:42 -0400 | [diff] [blame] | 582 | config FSL_FIXED_MMC_LOCATION |
| 583 | bool "PBL MMC is at a fixed location" |
| 584 | depends on SDCARD && !RAMBOOT_PBL |
| 585 | |
| 586 | config ESDHC_HC_BLK_ADDR |
| 587 | def_bool y |
| 588 | depends on FSL_FIXED_MMC_LOCATION && (ARCH_BSC9131 || ARCH_BSC9132 || ARCH_P1010) |
| 589 | help |
| 590 | In High Capacity SD Cards (> 2 GBytes), the 32-bit source address and |
| 591 | code length of these soc specify the memory address in block address |
| 592 | format. Block length is fixed to 512 bytes as per the SD High |
| 593 | Capacity specification. |
| 594 | |
Tom Rini | d8ef01e | 2021-08-24 23:11:49 -0400 | [diff] [blame] | 595 | config SYS_FSL_PBL_PBI |
| 596 | string "PBI(pre-boot instructions) commands for the PBL image" |
| 597 | depends on RAMBOOT_PBL |
| 598 | help |
| 599 | PBI commands can be used to configure SoC before it starts the execution. |
| 600 | Please refer doc/README.pblimage for more details. |
| 601 | |
| 602 | config SYS_FSL_PBL_RCW |
| 603 | string "Aadditional RCW (Power on reset configuration) for the PBL image" |
| 604 | depends on RAMBOOT_PBL |
| 605 | help |
| 606 | Enables addition of RCW (Power on reset configuration) in built image. |
| 607 | Please refer doc/README.pblimage for more details. |
| 608 | |
Tom Rini | bb20a10 | 2022-06-25 11:02:46 -0400 | [diff] [blame] | 609 | config SYS_BOOT_RAMDISK_HIGH |
| 610 | depends on CMD_BOOTM || CMD_BOOTI || CMD_BOOTZ |
| 611 | depends on !(NIOS2 || SANDBOX || SH || XTENSA) |
| 612 | def_bool y |
| 613 | help |
| 614 | Enable initrd_high functionality. If defined then the initrd_high |
| 615 | feature is enabled and the boot* ramdisk subcommand is enabled. |
| 616 | |
Simon Glass | cf29816 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 617 | endmenu # Boot images |
| 618 | |
Simon Glass | 75e65cc | 2020-09-10 20:21:14 -0600 | [diff] [blame] | 619 | menu "Boot timing" |
| 620 | |
| 621 | config BOOTSTAGE |
| 622 | bool "Boot timing and reporting" |
| 623 | help |
| 624 | Enable recording of boot time while booting. To use it, insert |
| 625 | calls to bootstage_mark() with a suitable BOOTSTAGE_ID from |
| 626 | bootstage.h. Only a single entry is recorded for each ID. You can |
| 627 | give the entry a name with bootstage_mark_name(). You can also |
| 628 | record elapsed time in a particular stage using bootstage_start() |
| 629 | before starting and bootstage_accum() when finished. Bootstage will |
| 630 | add up all the accumulated time and report it. |
| 631 | |
| 632 | Normally, IDs are defined in bootstage.h but a small number of |
| 633 | additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC |
| 634 | as the ID. |
| 635 | |
| 636 | Calls to show_boot_progress() will also result in log entries but |
| 637 | these will not have names. |
| 638 | |
| 639 | config SPL_BOOTSTAGE |
| 640 | bool "Boot timing and reported in SPL" |
Tom Rini | b340199 | 2022-06-10 23:03:09 -0400 | [diff] [blame] | 641 | depends on BOOTSTAGE && SPL |
Simon Glass | 75e65cc | 2020-09-10 20:21:14 -0600 | [diff] [blame] | 642 | help |
| 643 | Enable recording of boot time in SPL. To make this visible to U-Boot |
| 644 | proper, enable BOOTSTAGE_STASH as well. This will stash the timing |
| 645 | information when SPL finishes and load it when U-Boot proper starts |
| 646 | up. |
| 647 | |
| 648 | config TPL_BOOTSTAGE |
| 649 | bool "Boot timing and reported in TPL" |
Tom Rini | 8bea4bf | 2022-06-08 08:24:39 -0400 | [diff] [blame] | 650 | depends on BOOTSTAGE && TPL |
Simon Glass | 75e65cc | 2020-09-10 20:21:14 -0600 | [diff] [blame] | 651 | help |
| 652 | Enable recording of boot time in SPL. To make this visible to U-Boot |
| 653 | proper, enable BOOTSTAGE_STASH as well. This will stash the timing |
| 654 | information when TPL finishes and load it when U-Boot proper starts |
| 655 | up. |
| 656 | |
| 657 | config BOOTSTAGE_REPORT |
| 658 | bool "Display a detailed boot timing report before booting the OS" |
| 659 | depends on BOOTSTAGE |
| 660 | help |
| 661 | Enable output of a boot time report just before the OS is booted. |
| 662 | This shows how long it took U-Boot to go through each stage of the |
| 663 | boot process. The report looks something like this: |
| 664 | |
| 665 | Timer summary in microseconds: |
| 666 | Mark Elapsed Stage |
| 667 | 0 0 reset |
| 668 | 3,575,678 3,575,678 board_init_f start |
| 669 | 3,575,695 17 arch_cpu_init A9 |
| 670 | 3,575,777 82 arch_cpu_init done |
| 671 | 3,659,598 83,821 board_init_r start |
| 672 | 3,910,375 250,777 main_loop |
| 673 | 29,916,167 26,005,792 bootm_start |
| 674 | 30,361,327 445,160 start_kernel |
| 675 | |
| 676 | config BOOTSTAGE_RECORD_COUNT |
| 677 | int "Number of boot stage records to store" |
Simon Glass | 939b04e | 2021-02-03 06:00:49 -0700 | [diff] [blame] | 678 | depends on BOOTSTAGE |
Simon Glass | 75e65cc | 2020-09-10 20:21:14 -0600 | [diff] [blame] | 679 | default 30 |
| 680 | help |
| 681 | This is the size of the bootstage record list and is the maximum |
| 682 | number of bootstage records that can be recorded. |
| 683 | |
| 684 | config SPL_BOOTSTAGE_RECORD_COUNT |
| 685 | int "Number of boot stage records to store for SPL" |
Simon Glass | 939b04e | 2021-02-03 06:00:49 -0700 | [diff] [blame] | 686 | depends on SPL_BOOTSTAGE |
Simon Glass | 75e65cc | 2020-09-10 20:21:14 -0600 | [diff] [blame] | 687 | default 5 |
| 688 | help |
| 689 | This is the size of the bootstage record list and is the maximum |
| 690 | number of bootstage records that can be recorded. |
| 691 | |
| 692 | config TPL_BOOTSTAGE_RECORD_COUNT |
| 693 | int "Number of boot stage records to store for TPL" |
Simon Glass | 939b04e | 2021-02-03 06:00:49 -0700 | [diff] [blame] | 694 | depends on TPL_BOOTSTAGE |
Simon Glass | 75e65cc | 2020-09-10 20:21:14 -0600 | [diff] [blame] | 695 | default 5 |
| 696 | help |
| 697 | This is the size of the bootstage record list and is the maximum |
| 698 | number of bootstage records that can be recorded. |
| 699 | |
| 700 | config BOOTSTAGE_FDT |
| 701 | bool "Store boot timing information in the OS device tree" |
| 702 | depends on BOOTSTAGE |
| 703 | help |
| 704 | Stash the bootstage information in the FDT. A root 'bootstage' |
| 705 | node is created with each bootstage id as a child. Each child |
| 706 | has a 'name' property and either 'mark' containing the |
| 707 | mark time in microseconds, or 'accum' containing the |
| 708 | accumulated time for that bootstage id in microseconds. |
| 709 | For example: |
| 710 | |
| 711 | bootstage { |
| 712 | 154 { |
| 713 | name = "board_init_f"; |
| 714 | mark = <3575678>; |
| 715 | }; |
| 716 | 170 { |
| 717 | name = "lcd"; |
| 718 | accum = <33482>; |
| 719 | }; |
| 720 | }; |
| 721 | |
| 722 | Code in the Linux kernel can find this in /proc/devicetree. |
| 723 | |
| 724 | config BOOTSTAGE_STASH |
| 725 | bool "Stash the boot timing information in memory before booting OS" |
| 726 | depends on BOOTSTAGE |
| 727 | help |
| 728 | Some OSes do not support device tree. Bootstage can instead write |
| 729 | the boot timing information in a binary format at a given address. |
| 730 | This happens through a call to bootstage_stash(), typically in |
| 731 | the CPU's cleanup_before_linux() function. You can use the |
| 732 | 'bootstage stash' and 'bootstage unstash' commands to do this on |
| 733 | the command line. |
| 734 | |
| 735 | config BOOTSTAGE_STASH_ADDR |
| 736 | hex "Address to stash boot timing information" |
| 737 | default 0 |
| 738 | help |
| 739 | Provide an address which will not be overwritten by the OS when it |
| 740 | starts, so that it can read this information when ready. |
| 741 | |
| 742 | config BOOTSTAGE_STASH_SIZE |
| 743 | hex "Size of boot timing stash region" |
| 744 | default 0x1000 |
| 745 | help |
| 746 | This should be large enough to hold the bootstage stash. A value of |
| 747 | 4096 (4KiB) is normally plenty. |
| 748 | |
| 749 | config SHOW_BOOT_PROGRESS |
| 750 | bool "Show boot progress in a board-specific manner" |
| 751 | help |
| 752 | Defining this option allows to add some board-specific code (calling |
| 753 | a user-provided function show_boot_progress(int) that enables you to |
| 754 | show the system's boot progress on some display (for example, some |
| 755 | LEDs) on your board. At the moment, the following checkpoints are |
| 756 | implemented: |
| 757 | |
| 758 | Legacy uImage format: |
| 759 | |
| 760 | Arg Where When |
| 761 | 1 common/cmd_bootm.c before attempting to boot an image |
| 762 | -1 common/cmd_bootm.c Image header has bad magic number |
| 763 | 2 common/cmd_bootm.c Image header has correct magic number |
| 764 | -2 common/cmd_bootm.c Image header has bad checksum |
| 765 | 3 common/cmd_bootm.c Image header has correct checksum |
| 766 | -3 common/cmd_bootm.c Image data has bad checksum |
| 767 | 4 common/cmd_bootm.c Image data has correct checksum |
| 768 | -4 common/cmd_bootm.c Image is for unsupported architecture |
| 769 | 5 common/cmd_bootm.c Architecture check OK |
| 770 | -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi) |
| 771 | 6 common/cmd_bootm.c Image Type check OK |
| 772 | -6 common/cmd_bootm.c gunzip uncompression error |
| 773 | -7 common/cmd_bootm.c Unimplemented compression type |
| 774 | 7 common/cmd_bootm.c Uncompression OK |
| 775 | 8 common/cmd_bootm.c No uncompress/copy overwrite error |
| 776 | -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX) |
| 777 | |
| 778 | 9 common/image.c Start initial ramdisk verification |
| 779 | -10 common/image.c Ramdisk header has bad magic number |
| 780 | -11 common/image.c Ramdisk header has bad checksum |
| 781 | 10 common/image.c Ramdisk header is OK |
| 782 | -12 common/image.c Ramdisk data has bad checksum |
| 783 | 11 common/image.c Ramdisk data has correct checksum |
| 784 | 12 common/image.c Ramdisk verification complete, start loading |
| 785 | -13 common/image.c Wrong Image Type (not PPC Linux ramdisk) |
| 786 | 13 common/image.c Start multifile image verification |
| 787 | 14 common/image.c No initial ramdisk, no multifile, continue. |
| 788 | |
| 789 | 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS |
| 790 | |
| 791 | -30 arch/powerpc/lib/board.c Fatal error, hang the system |
| 792 | -31 post/post.c POST test failed, detected by post_output_backlog() |
| 793 | -32 post/post.c POST test failed, detected by post_run_single() |
| 794 | |
| 795 | 34 common/cmd_doc.c before loading a Image from a DOC device |
| 796 | -35 common/cmd_doc.c Bad usage of "doc" command |
| 797 | 35 common/cmd_doc.c correct usage of "doc" command |
| 798 | -36 common/cmd_doc.c No boot device |
| 799 | 36 common/cmd_doc.c correct boot device |
| 800 | -37 common/cmd_doc.c Unknown Chip ID on boot device |
| 801 | 37 common/cmd_doc.c correct chip ID found, device available |
| 802 | -38 common/cmd_doc.c Read Error on boot device |
| 803 | 38 common/cmd_doc.c reading Image header from DOC device OK |
| 804 | -39 common/cmd_doc.c Image header has bad magic number |
| 805 | 39 common/cmd_doc.c Image header has correct magic number |
| 806 | -40 common/cmd_doc.c Error reading Image from DOC device |
| 807 | 40 common/cmd_doc.c Image header has correct magic number |
| 808 | 41 common/cmd_ide.c before loading a Image from a IDE device |
| 809 | -42 common/cmd_ide.c Bad usage of "ide" command |
| 810 | 42 common/cmd_ide.c correct usage of "ide" command |
| 811 | -43 common/cmd_ide.c No boot device |
| 812 | 43 common/cmd_ide.c boot device found |
| 813 | -44 common/cmd_ide.c Device not available |
| 814 | 44 common/cmd_ide.c Device available |
| 815 | -45 common/cmd_ide.c wrong partition selected |
| 816 | 45 common/cmd_ide.c partition selected |
| 817 | -46 common/cmd_ide.c Unknown partition table |
| 818 | 46 common/cmd_ide.c valid partition table found |
| 819 | -47 common/cmd_ide.c Invalid partition type |
| 820 | 47 common/cmd_ide.c correct partition type |
| 821 | -48 common/cmd_ide.c Error reading Image Header on boot device |
| 822 | 48 common/cmd_ide.c reading Image Header from IDE device OK |
| 823 | -49 common/cmd_ide.c Image header has bad magic number |
| 824 | 49 common/cmd_ide.c Image header has correct magic number |
| 825 | -50 common/cmd_ide.c Image header has bad checksum |
| 826 | 50 common/cmd_ide.c Image header has correct checksum |
| 827 | -51 common/cmd_ide.c Error reading Image from IDE device |
| 828 | 51 common/cmd_ide.c reading Image from IDE device OK |
| 829 | 52 common/cmd_nand.c before loading a Image from a NAND device |
| 830 | -53 common/cmd_nand.c Bad usage of "nand" command |
| 831 | 53 common/cmd_nand.c correct usage of "nand" command |
| 832 | -54 common/cmd_nand.c No boot device |
| 833 | 54 common/cmd_nand.c boot device found |
| 834 | -55 common/cmd_nand.c Unknown Chip ID on boot device |
| 835 | 55 common/cmd_nand.c correct chip ID found, device available |
| 836 | -56 common/cmd_nand.c Error reading Image Header on boot device |
| 837 | 56 common/cmd_nand.c reading Image Header from NAND device OK |
| 838 | -57 common/cmd_nand.c Image header has bad magic number |
| 839 | 57 common/cmd_nand.c Image header has correct magic number |
| 840 | -58 common/cmd_nand.c Error reading Image from NAND device |
| 841 | 58 common/cmd_nand.c reading Image from NAND device OK |
| 842 | |
| 843 | -60 common/env_common.c Environment has a bad CRC, using default |
| 844 | |
| 845 | 64 net/eth.c starting with Ethernet configuration. |
| 846 | -64 net/eth.c no Ethernet found. |
| 847 | 65 net/eth.c Ethernet found. |
| 848 | |
| 849 | -80 common/cmd_net.c usage wrong |
| 850 | 80 common/cmd_net.c before calling net_loop() |
| 851 | -81 common/cmd_net.c some error in net_loop() occurred |
| 852 | 81 common/cmd_net.c net_loop() back without error |
| 853 | -82 common/cmd_net.c size == 0 (File with size 0 loaded) |
| 854 | 82 common/cmd_net.c trying automatic boot |
| 855 | 83 common/cmd_net.c running "source" command |
| 856 | -83 common/cmd_net.c some error in automatic boot or "source" command |
| 857 | 84 common/cmd_net.c end without errors |
| 858 | |
| 859 | FIT uImage format: |
| 860 | |
| 861 | Arg Where When |
| 862 | 100 common/cmd_bootm.c Kernel FIT Image has correct format |
| 863 | -100 common/cmd_bootm.c Kernel FIT Image has incorrect format |
| 864 | 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration |
| 865 | -101 common/cmd_bootm.c Can't get configuration for kernel subimage |
| 866 | 102 common/cmd_bootm.c Kernel unit name specified |
| 867 | -103 common/cmd_bootm.c Can't get kernel subimage node offset |
| 868 | 103 common/cmd_bootm.c Found configuration node |
| 869 | 104 common/cmd_bootm.c Got kernel subimage node offset |
| 870 | -104 common/cmd_bootm.c Kernel subimage hash verification failed |
| 871 | 105 common/cmd_bootm.c Kernel subimage hash verification OK |
| 872 | -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture |
| 873 | 106 common/cmd_bootm.c Architecture check OK |
| 874 | -106 common/cmd_bootm.c Kernel subimage has wrong type |
| 875 | 107 common/cmd_bootm.c Kernel subimage type OK |
| 876 | -107 common/cmd_bootm.c Can't get kernel subimage data/size |
| 877 | 108 common/cmd_bootm.c Got kernel subimage data/size |
| 878 | -108 common/cmd_bootm.c Wrong image type (not legacy, FIT) |
| 879 | -109 common/cmd_bootm.c Can't get kernel subimage type |
| 880 | -110 common/cmd_bootm.c Can't get kernel subimage comp |
| 881 | -111 common/cmd_bootm.c Can't get kernel subimage os |
| 882 | -112 common/cmd_bootm.c Can't get kernel subimage load address |
| 883 | -113 common/cmd_bootm.c Image uncompress/copy overwrite error |
| 884 | |
| 885 | 120 common/image.c Start initial ramdisk verification |
| 886 | -120 common/image.c Ramdisk FIT image has incorrect format |
| 887 | 121 common/image.c Ramdisk FIT image has correct format |
| 888 | 122 common/image.c No ramdisk subimage unit name, using configuration |
| 889 | -122 common/image.c Can't get configuration for ramdisk subimage |
| 890 | 123 common/image.c Ramdisk unit name specified |
| 891 | -124 common/image.c Can't get ramdisk subimage node offset |
| 892 | 125 common/image.c Got ramdisk subimage node offset |
| 893 | -125 common/image.c Ramdisk subimage hash verification failed |
| 894 | 126 common/image.c Ramdisk subimage hash verification OK |
| 895 | -126 common/image.c Ramdisk subimage for unsupported architecture |
| 896 | 127 common/image.c Architecture check OK |
| 897 | -127 common/image.c Can't get ramdisk subimage data/size |
| 898 | 128 common/image.c Got ramdisk subimage data/size |
| 899 | 129 common/image.c Can't get ramdisk load address |
| 900 | -129 common/image.c Got ramdisk load address |
| 901 | |
| 902 | -130 common/cmd_doc.c Incorrect FIT image format |
| 903 | 131 common/cmd_doc.c FIT image format OK |
| 904 | |
| 905 | -140 common/cmd_ide.c Incorrect FIT image format |
| 906 | 141 common/cmd_ide.c FIT image format OK |
| 907 | |
| 908 | -150 common/cmd_nand.c Incorrect FIT image format |
| 909 | 151 common/cmd_nand.c FIT image format OK |
| 910 | |
Marek Vasut | b55881d | 2021-10-23 03:06:03 +0200 | [diff] [blame] | 911 | config SPL_SHOW_BOOT_PROGRESS |
Jan Kiszka | c1df3d5 | 2021-11-03 15:09:36 +0100 | [diff] [blame] | 912 | bool "Show boot progress in a board-specific manner in SPL" |
Marek Vasut | b55881d | 2021-10-23 03:06:03 +0200 | [diff] [blame] | 913 | depends on SPL |
| 914 | help |
| 915 | Defining this option allows to add some board-specific code (calling |
| 916 | a user-provided function show_boot_progress(int) that enables you to |
| 917 | show the system's boot progress on some display (for example, some |
| 918 | LEDs) on your board. For details see SHOW_BOOT_PROGRESS. |
| 919 | |
Simon Glass | 75e65cc | 2020-09-10 20:21:14 -0600 | [diff] [blame] | 920 | endmenu |
| 921 | |
Simon Glass | 7b6baa3 | 2020-09-10 20:21:15 -0600 | [diff] [blame] | 922 | menu "Boot media" |
| 923 | |
| 924 | config NOR_BOOT |
| 925 | bool "Support for booting from NOR flash" |
| 926 | depends on NOR |
| 927 | help |
| 928 | Enabling this will make a U-Boot binary that is capable of being |
| 929 | booted via NOR. In this case we will enable certain pinmux early |
| 930 | as the ROM only partially sets up pinmux. We also default to using |
| 931 | NOR for environment. |
| 932 | |
| 933 | config NAND_BOOT |
| 934 | bool "Support for booting from NAND flash" |
Simon Glass | 7b6baa3 | 2020-09-10 20:21:15 -0600 | [diff] [blame] | 935 | imply MTD_RAW_NAND |
| 936 | help |
| 937 | Enabling this will make a U-Boot binary that is capable of being |
| 938 | booted via NAND flash. This is not a must, some SoCs need this, |
| 939 | some not. |
| 940 | |
| 941 | config ONENAND_BOOT |
| 942 | bool "Support for booting from ONENAND" |
Simon Glass | 7b6baa3 | 2020-09-10 20:21:15 -0600 | [diff] [blame] | 943 | imply MTD_RAW_NAND |
| 944 | help |
| 945 | Enabling this will make a U-Boot binary that is capable of being |
| 946 | booted via ONENAND. This is not a must, some SoCs need this, |
| 947 | some not. |
| 948 | |
| 949 | config QSPI_BOOT |
| 950 | bool "Support for booting from QSPI flash" |
Simon Glass | 7b6baa3 | 2020-09-10 20:21:15 -0600 | [diff] [blame] | 951 | help |
| 952 | Enabling this will make a U-Boot binary that is capable of being |
| 953 | booted via QSPI flash. This is not a must, some SoCs need this, |
| 954 | some not. |
| 955 | |
| 956 | config SATA_BOOT |
| 957 | bool "Support for booting from SATA" |
Simon Glass | 7b6baa3 | 2020-09-10 20:21:15 -0600 | [diff] [blame] | 958 | help |
| 959 | Enabling this will make a U-Boot binary that is capable of being |
| 960 | booted via SATA. This is not a must, some SoCs need this, |
| 961 | some not. |
| 962 | |
| 963 | config SD_BOOT |
| 964 | bool "Support for booting from SD/EMMC" |
Simon Glass | 7b6baa3 | 2020-09-10 20:21:15 -0600 | [diff] [blame] | 965 | help |
| 966 | Enabling this will make a U-Boot binary that is capable of being |
| 967 | booted via SD/EMMC. This is not a must, some SoCs need this, |
| 968 | some not. |
| 969 | |
Tom Rini | 66e0e2b | 2021-12-11 14:55:50 -0500 | [diff] [blame] | 970 | config SD_BOOT_QSPI |
| 971 | bool "Support for booting from SD/EMMC and enable QSPI" |
| 972 | help |
| 973 | Enabling this will make a U-Boot binary that is capable of being |
| 974 | booted via SD/EMMC while enabling QSPI on the platform as well. This |
| 975 | is not a must, some SoCs need this, some not. |
| 976 | |
Simon Glass | 7b6baa3 | 2020-09-10 20:21:15 -0600 | [diff] [blame] | 977 | config SPI_BOOT |
| 978 | bool "Support for booting from SPI flash" |
Simon Glass | 7b6baa3 | 2020-09-10 20:21:15 -0600 | [diff] [blame] | 979 | help |
| 980 | Enabling this will make a U-Boot binary that is capable of being |
| 981 | booted via SPI flash. This is not a must, some SoCs need this, |
| 982 | some not. |
| 983 | |
| 984 | endmenu |
| 985 | |
Simon Glass | 98eed0d | 2020-09-10 20:21:16 -0600 | [diff] [blame] | 986 | menu "Autoboot options" |
| 987 | |
| 988 | config AUTOBOOT |
| 989 | bool "Autoboot" |
| 990 | default y |
| 991 | help |
| 992 | This enables the autoboot. See doc/README.autoboot for detail. |
| 993 | |
Simon Glass | 95fd4f3 | 2020-09-10 20:21:17 -0600 | [diff] [blame] | 994 | config BOOTDELAY |
| 995 | int "delay in seconds before automatically booting" |
| 996 | default 2 |
| 997 | depends on AUTOBOOT |
| 998 | help |
| 999 | Delay before automatically running bootcmd; |
| 1000 | set to 0 to autoboot with no delay, but you can stop it by key input. |
| 1001 | set to -1 to disable autoboot. |
| 1002 | set to -2 to autoboot with no delay and not check for abort |
| 1003 | |
| 1004 | If this value is >= 0 then it is also used for the default delay |
| 1005 | before starting the default entry in bootmenu. If it is < 0 then |
| 1006 | a default value of 10s is used. |
| 1007 | |
| 1008 | See doc/README.autoboot for details. |
| 1009 | |
Simon Glass | 98eed0d | 2020-09-10 20:21:16 -0600 | [diff] [blame] | 1010 | config AUTOBOOT_KEYED |
| 1011 | bool "Stop autobooting via specific input key / string" |
Simon Glass | 98eed0d | 2020-09-10 20:21:16 -0600 | [diff] [blame] | 1012 | help |
| 1013 | This option enables stopping (aborting) of the automatic |
| 1014 | boot feature only by issuing a specific input key or |
| 1015 | string. If not enabled, any input key will abort the |
| 1016 | U-Boot automatic booting process and bring the device |
| 1017 | to the U-Boot prompt for user input. |
| 1018 | |
Steffen Jaeckel | d199c3a | 2021-07-08 15:57:38 +0200 | [diff] [blame] | 1019 | config AUTOBOOT_FLUSH_STDIN |
| 1020 | bool "Enable flushing stdin before starting to read the password" |
| 1021 | depends on AUTOBOOT_KEYED && !SANDBOX |
| 1022 | help |
| 1023 | When this option is enabled stdin buffer will be flushed before |
| 1024 | starting to read the password. |
| 1025 | This can't be enabled for the sandbox as flushing stdin would |
| 1026 | break the autoboot unit tests. |
| 1027 | |
Simon Glass | 98eed0d | 2020-09-10 20:21:16 -0600 | [diff] [blame] | 1028 | config AUTOBOOT_PROMPT |
| 1029 | string "Autoboot stop prompt" |
| 1030 | depends on AUTOBOOT_KEYED |
| 1031 | default "Autoboot in %d seconds\\n" |
| 1032 | help |
| 1033 | This string is displayed before the boot delay selected by |
| 1034 | CONFIG_BOOTDELAY starts. If it is not defined there is no |
| 1035 | output indicating that autoboot is in progress. |
| 1036 | |
| 1037 | Note that this define is used as the (only) argument to a |
| 1038 | printf() call, so it may contain '%' format specifications, |
| 1039 | provided that it also includes, sepearated by commas exactly |
| 1040 | like in a printf statement, the required arguments. It is |
| 1041 | the responsibility of the user to select only such arguments |
| 1042 | that are valid in the given context. |
| 1043 | |
| 1044 | config AUTOBOOT_ENCRYPTION |
| 1045 | bool "Enable encryption in autoboot stopping" |
| 1046 | depends on AUTOBOOT_KEYED |
| 1047 | help |
| 1048 | This option allows a string to be entered into U-Boot to stop the |
Steffen Jaeckel | 1a4a778 | 2021-07-08 15:57:35 +0200 | [diff] [blame] | 1049 | autoboot. |
| 1050 | The behavior depends whether CONFIG_CRYPT_PW from lib is enabled |
| 1051 | or not. |
| 1052 | In case CONFIG_CRYPT_PW is enabled, the string will be forwarded |
| 1053 | to the crypt-based functionality and be compared against the |
| 1054 | string in the environment variable 'bootstopkeycrypt'. |
| 1055 | In case CONFIG_CRYPT_PW is disabled the string itself is hashed |
| 1056 | and compared against the hash in the environment variable |
| 1057 | 'bootstopkeysha256'. |
| 1058 | If it matches in either case then boot stops and |
| 1059 | a command-line prompt is presented. |
Simon Glass | 98eed0d | 2020-09-10 20:21:16 -0600 | [diff] [blame] | 1060 | This provides a way to ship a secure production device which can also |
| 1061 | be accessed at the U-Boot command line. |
| 1062 | |
Steffen Jaeckel | 3319874 | 2021-07-08 15:57:39 +0200 | [diff] [blame] | 1063 | config AUTOBOOT_SHA256_FALLBACK |
| 1064 | bool "Allow fallback from crypt-hashed password to sha256" |
| 1065 | depends on AUTOBOOT_ENCRYPTION && CRYPT_PW |
| 1066 | help |
| 1067 | This option adds support to fall back from crypt-hashed |
| 1068 | passwords to checking a SHA256 hashed password in case the |
| 1069 | 'bootstopusesha256' environment variable is set to 'true'. |
| 1070 | |
Simon Glass | 98eed0d | 2020-09-10 20:21:16 -0600 | [diff] [blame] | 1071 | config AUTOBOOT_DELAY_STR |
| 1072 | string "Delay autobooting via specific input key / string" |
| 1073 | depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION |
| 1074 | help |
| 1075 | This option delays the automatic boot feature by issuing |
| 1076 | a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR |
| 1077 | or the environment variable "bootdelaykey" is specified |
| 1078 | and this string is received from console input before |
| 1079 | autoboot starts booting, U-Boot gives a command prompt. The |
| 1080 | U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is |
| 1081 | used, otherwise it never times out. |
| 1082 | |
| 1083 | config AUTOBOOT_STOP_STR |
| 1084 | string "Stop autobooting via specific input key / string" |
| 1085 | depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION |
| 1086 | help |
| 1087 | This option enables stopping (aborting) of the automatic |
| 1088 | boot feature only by issuing a specific input key or |
| 1089 | string. If CONFIG_AUTOBOOT_STOP_STR or the environment |
| 1090 | variable "bootstopkey" is specified and this string is |
| 1091 | received from console input before autoboot starts booting, |
| 1092 | U-Boot gives a command prompt. The U-Boot prompt never |
| 1093 | times out, even if CONFIG_BOOT_RETRY_TIME is used. |
| 1094 | |
| 1095 | config AUTOBOOT_KEYED_CTRLC |
| 1096 | bool "Enable Ctrl-C autoboot interruption" |
| 1097 | depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION |
Simon Glass | 98eed0d | 2020-09-10 20:21:16 -0600 | [diff] [blame] | 1098 | help |
| 1099 | This option allows for the boot sequence to be interrupted |
| 1100 | by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey". |
| 1101 | Setting this variable provides an escape sequence from the |
| 1102 | limited "password" strings. |
| 1103 | |
Steffen Jaeckel | 6c0ce6d | 2021-07-08 15:57:37 +0200 | [diff] [blame] | 1104 | config AUTOBOOT_NEVER_TIMEOUT |
| 1105 | bool "Make the password entry never time-out" |
| 1106 | depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION && CRYPT_PW |
| 1107 | help |
| 1108 | This option removes the timeout from the password entry |
| 1109 | when the user first presses the <Enter> key before entering |
| 1110 | any other character. |
| 1111 | |
Steffen Jaeckel | 1a4a778 | 2021-07-08 15:57:35 +0200 | [diff] [blame] | 1112 | config AUTOBOOT_STOP_STR_ENABLE |
| 1113 | bool "Enable fixed string to stop autobooting" |
| 1114 | depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION |
| 1115 | help |
| 1116 | This option enables the feature to add a fixed stop |
| 1117 | string that is defined at compile time. |
| 1118 | In every case it will be tried to load the stop |
| 1119 | string from the environment. |
| 1120 | In case this is enabled and there is no stop string |
| 1121 | in the environment, this will be used as default value. |
| 1122 | |
| 1123 | config AUTOBOOT_STOP_STR_CRYPT |
| 1124 | string "Stop autobooting via crypt-hashed password" |
| 1125 | depends on AUTOBOOT_STOP_STR_ENABLE && CRYPT_PW |
| 1126 | help |
| 1127 | This option adds the feature to only stop the autobooting, |
| 1128 | and therefore boot into the U-Boot prompt, when the input |
| 1129 | string / password matches a values that is hashed via |
| 1130 | one of the supported crypt-style password hashing options |
| 1131 | and saved in the environment variable "bootstopkeycrypt". |
| 1132 | |
Simon Glass | 98eed0d | 2020-09-10 20:21:16 -0600 | [diff] [blame] | 1133 | config AUTOBOOT_STOP_STR_SHA256 |
Steffen Jaeckel | 25c8b9f | 2021-07-08 15:57:40 +0200 | [diff] [blame] | 1134 | string "Stop autobooting via SHA256 hashed password" |
Steffen Jaeckel | 1a4a778 | 2021-07-08 15:57:35 +0200 | [diff] [blame] | 1135 | depends on AUTOBOOT_STOP_STR_ENABLE |
Simon Glass | 98eed0d | 2020-09-10 20:21:16 -0600 | [diff] [blame] | 1136 | help |
| 1137 | This option adds the feature to only stop the autobooting, |
| 1138 | and therefore boot into the U-Boot prompt, when the input |
| 1139 | string / password matches a values that is encypted via |
Joel Peshkin | 652b504 | 2020-11-21 17:18:59 -0800 | [diff] [blame] | 1140 | a SHA256 hash and saved in the environment variable |
| 1141 | "bootstopkeysha256". If the value in that variable |
| 1142 | includes a ":", the portion prior to the ":" will be treated |
| 1143 | as a salt value. |
Simon Glass | 98eed0d | 2020-09-10 20:21:16 -0600 | [diff] [blame] | 1144 | |
| 1145 | config AUTOBOOT_USE_MENUKEY |
| 1146 | bool "Allow a specify key to run a menu from the environment" |
| 1147 | depends on !AUTOBOOT_KEYED |
| 1148 | help |
| 1149 | If a specific key is pressed to stop autoboot, then the commands in |
| 1150 | the environment variable 'menucmd' are executed before boot starts. |
| 1151 | |
| 1152 | config AUTOBOOT_MENUKEY |
| 1153 | int "ASCII value of boot key to show a menu" |
| 1154 | default 0 |
| 1155 | depends on AUTOBOOT_USE_MENUKEY |
| 1156 | help |
| 1157 | If this key is pressed to stop autoboot, then the commands in the |
| 1158 | environment variable 'menucmd' will be executed before boot starts. |
| 1159 | For example, 33 means "!" in ASCII, so pressing ! at boot would take |
| 1160 | this action. |
| 1161 | |
| 1162 | config AUTOBOOT_MENU_SHOW |
| 1163 | bool "Show a menu on boot" |
| 1164 | depends on CMD_BOOTMENU |
| 1165 | help |
| 1166 | This enables the boot menu, controlled by environment variables |
| 1167 | defined by the board. The menu starts after running the 'preboot' |
| 1168 | environmnent variable (if enabled) and before handling the boot delay. |
| 1169 | See README.bootmenu for more details. |
| 1170 | |
Masahisa Kojima | 83f7363 | 2022-05-26 19:09:38 +0900 | [diff] [blame] | 1171 | config BOOTMENU_DISABLE_UBOOT_CONSOLE |
| 1172 | bool "Disallow bootmenu to enter the U-Boot console" |
| 1173 | depends on AUTOBOOT_MENU_SHOW |
| 1174 | help |
| 1175 | If this option is enabled, user can not enter the U-Boot console from |
| 1176 | bootmenu. It increases the system security. |
| 1177 | |
Tom Rini | 69c8a81 | 2022-03-11 09:12:04 -0500 | [diff] [blame] | 1178 | config BOOT_RETRY |
| 1179 | bool "Boot retry feature" |
| 1180 | help |
| 1181 | Allow for having the U-Boot command prompt time out and attempt |
| 1182 | to boot again. If the environment variable "bootretry" is found then |
| 1183 | its value is used, otherwise the retry timeout is |
| 1184 | CONFIG_BOOT_RETRY_TIME. CONFIG_BOOT_RETRY_MIN is optional and |
| 1185 | defaults to CONFIG_BOOT_RETRY_TIME. All times are in seconds. |
| 1186 | |
| 1187 | config BOOT_RETRY_TIME |
| 1188 | int "Timeout in seconds before attempting to boot again" |
| 1189 | depends on BOOT_RETRY |
| 1190 | help |
| 1191 | Time in seconds before the U-Boot prompt will timeout and boot will |
| 1192 | be attempted again. |
| 1193 | |
| 1194 | config BOOT_RETRY_MIN |
| 1195 | int "Minimum timeout in seconds for 'bootretry'" |
| 1196 | depends on BOOT_RETRY |
| 1197 | default BOOT_RETRY_TIME |
| 1198 | help |
| 1199 | The minimum time in seconds that "bootretry" can be set to. |
| 1200 | |
| 1201 | config RESET_TO_RETRY |
| 1202 | bool "Reset the board to retry autoboot" |
| 1203 | depends on BOOT_RETRY |
| 1204 | help |
| 1205 | After the countdown timed out, the board will be reset to restart |
| 1206 | again. |
| 1207 | |
Simon Glass | 98eed0d | 2020-09-10 20:21:16 -0600 | [diff] [blame] | 1208 | endmenu |
| 1209 | |
Philippe Reynes | 9822074 | 2022-03-28 22:56:59 +0200 | [diff] [blame] | 1210 | menu "Image support" |
| 1211 | |
| 1212 | config IMAGE_PRE_LOAD |
| 1213 | bool "Image pre-load support" |
| 1214 | help |
| 1215 | Enable an image pre-load stage in the SPL. |
| 1216 | This pre-load stage allows to do some manipulation |
| 1217 | or check (for example signature check) on an image |
| 1218 | before launching it. |
| 1219 | |
| 1220 | config SPL_IMAGE_PRE_LOAD |
| 1221 | bool "Image pre-load support within SPL" |
| 1222 | depends on SPL && IMAGE_PRE_LOAD |
| 1223 | help |
| 1224 | Enable an image pre-load stage in the SPL. |
| 1225 | This pre-load stage allows to do some manipulation |
| 1226 | or check (for example signature check) on an image |
| 1227 | before launching it. |
| 1228 | |
| 1229 | config IMAGE_PRE_LOAD_SIG |
| 1230 | bool "Image pre-load signature support" |
| 1231 | depends on IMAGE_PRE_LOAD |
| 1232 | select FIT_SIGNATURE |
| 1233 | select RSA |
| 1234 | select RSA_VERIFY_WITH_PKEY |
| 1235 | help |
| 1236 | Enable signature check support in the pre-load stage. |
| 1237 | For this feature a very simple header is added before |
| 1238 | the image with few fields: |
| 1239 | - a magic |
| 1240 | - the image size |
| 1241 | - the signature |
| 1242 | All other information (header size, type of signature, |
| 1243 | ...) are provided in the node /image/pre-load/sig of |
| 1244 | u-boot. |
| 1245 | |
| 1246 | config SPL_IMAGE_PRE_LOAD_SIG |
| 1247 | bool "Image pre-load signature support witin SPL" |
| 1248 | depends on SPL_IMAGE_PRE_LOAD && IMAGE_PRE_LOAD_SIG |
| 1249 | select SPL_FIT_SIGNATURE |
| 1250 | select SPL_RSA |
| 1251 | select SPL_RSA_VERIFY_WITH_PKEY |
| 1252 | help |
| 1253 | Enable signature check support in the pre-load stage in the SPL. |
| 1254 | For this feature a very simple header is added before |
| 1255 | the image with few fields: |
| 1256 | - a magic |
| 1257 | - the image size |
| 1258 | - the signature |
| 1259 | All other information (header size, type of signature, |
| 1260 | ...) are provided in the node /image/pre-load/sig of |
| 1261 | u-boot. |
| 1262 | |
| 1263 | endmenu |
| 1264 | |
Simon Glass | fe5db25 | 2020-09-10 20:21:18 -0600 | [diff] [blame] | 1265 | config USE_BOOTARGS |
| 1266 | bool "Enable boot arguments" |
| 1267 | help |
| 1268 | Provide boot arguments to bootm command. Boot arguments are specified |
| 1269 | in CONFIG_BOOTARGS option. Enable this option to be able to specify |
| 1270 | CONFIG_BOOTARGS string. If this option is disabled, CONFIG_BOOTARGS |
| 1271 | will be undefined and won't take any space in U-Boot image. |
| 1272 | |
| 1273 | config BOOTARGS |
| 1274 | string "Boot arguments" |
| 1275 | depends on USE_BOOTARGS && !USE_DEFAULT_ENV_FILE |
| 1276 | help |
| 1277 | This can be used to pass arguments to the bootm command. The value of |
| 1278 | CONFIG_BOOTARGS goes into the environment value "bootargs". Note that |
| 1279 | this value will also override the "chosen" node in FDT blob. |
| 1280 | |
Simon Glass | 51bb338 | 2020-11-05 10:33:48 -0700 | [diff] [blame] | 1281 | config BOOTARGS_SUBST |
| 1282 | bool "Support substituting strings in boot arguments" |
| 1283 | help |
| 1284 | This allows substituting string values in the boot arguments. These |
| 1285 | are applied after the commandline has been built. |
| 1286 | |
| 1287 | One use for this is to insert the root-disk UUID into the command |
| 1288 | line where bootargs contains "root=${uuid}" |
| 1289 | |
| 1290 | setenv bootargs "console= root=${uuid}" |
| 1291 | # Set the 'uuid' environment variable |
| 1292 | part uuid mmc 2:2 uuid |
| 1293 | |
| 1294 | # Command-line substitution will put the real uuid into the |
| 1295 | # kernel command line |
| 1296 | bootm |
| 1297 | |
Simon Glass | fe5db25 | 2020-09-10 20:21:18 -0600 | [diff] [blame] | 1298 | config USE_BOOTCOMMAND |
| 1299 | bool "Enable a default value for bootcmd" |
| 1300 | help |
| 1301 | Provide a default value for the bootcmd entry in the environment. If |
| 1302 | autoboot is enabled this is what will be run automatically. Enable |
| 1303 | this option to be able to specify CONFIG_BOOTCOMMAND as a string. If |
| 1304 | this option is disabled, CONFIG_BOOTCOMMAND will be undefined and |
| 1305 | won't take any space in U-Boot image. |
| 1306 | |
| 1307 | config BOOTCOMMAND |
| 1308 | string "bootcmd value" |
| 1309 | depends on USE_BOOTCOMMAND && !USE_DEFAULT_ENV_FILE |
Simon Glass | a91492b | 2022-04-24 23:31:27 -0600 | [diff] [blame] | 1310 | default "bootflow scan -lb" if BOOTSTD_BOOTCOMMAND && CMD_BOOTFLOW_FULL |
| 1311 | default "bootflow scan" if BOOTSTD_BOOTCOMMAND && !CMD_BOOTFLOW_FULL |
| 1312 | default "run distro_bootcmd" if !BOOTSTD_BOOTCOMMAND && DISTRO_DEFAULTS |
Simon Glass | fe5db25 | 2020-09-10 20:21:18 -0600 | [diff] [blame] | 1313 | help |
| 1314 | This is the string of commands that will be used as bootcmd and if |
| 1315 | AUTOBOOT is set, automatically run. |
| 1316 | |
| 1317 | config USE_PREBOOT |
| 1318 | bool "Enable preboot" |
| 1319 | help |
| 1320 | When this option is enabled, the existence of the environment |
| 1321 | variable "preboot" will be checked immediately before starting the |
| 1322 | CONFIG_BOOTDELAY countdown and/or running the auto-boot command resp. |
| 1323 | entering interactive mode. |
| 1324 | |
| 1325 | This feature is especially useful when "preboot" is automatically |
| 1326 | generated or modified. For example, the boot code can modify the |
| 1327 | "preboot" when a user holds down a certain combination of keys. |
| 1328 | |
| 1329 | config PREBOOT |
| 1330 | string "preboot default value" |
| 1331 | depends on USE_PREBOOT && !USE_DEFAULT_ENV_FILE |
Patrick Delaunay | 87459da | 2020-10-12 09:47:50 +0200 | [diff] [blame] | 1332 | default "usb start" if USB_KEYBOARD |
Simon Glass | fe5db25 | 2020-09-10 20:21:18 -0600 | [diff] [blame] | 1333 | default "" |
| 1334 | help |
| 1335 | This is the default of "preboot" environment variable. |
| 1336 | |
Simon Glass | 832876a | 2020-09-10 20:21:20 -0600 | [diff] [blame] | 1337 | config DEFAULT_FDT_FILE |
| 1338 | string "Default fdt file" |
| 1339 | help |
| 1340 | This option is used to set the default fdt file to boot OS. |
| 1341 | |
Dzmitry Sankouski | 12a3e1a | 2022-02-22 21:49:52 +0300 | [diff] [blame] | 1342 | config SAVE_PREV_BL_FDT_ADDR |
| 1343 | depends on ARM |
| 1344 | bool "Saves fdt address, passed by the previous bootloader, to env var" |
| 1345 | help |
| 1346 | When u-boot is used as a chain-loaded bootloader (replacing OS kernel), |
| 1347 | enable this option to save fdt address, passed by the |
| 1348 | previous bootloader for future use. |
| 1349 | Address is saved to `prevbl_fdt_addr` environment variable. |
| 1350 | |
| 1351 | If no fdt was provided by previous bootloader, no env variables |
| 1352 | will be created. |
| 1353 | |
| 1354 | config SAVE_PREV_BL_INITRAMFS_START_ADDR |
| 1355 | depends on ARM |
| 1356 | bool "Saves initramfs address, passed by the previous bootloader, to env var" |
| 1357 | help |
| 1358 | When u-boot is used as a chain-loaded bootloader(replacing OS kernel), |
| 1359 | enable this option to save initramfs address, passed by the |
| 1360 | previous bootloader for future use. |
| 1361 | Address is saved to `prevbl_initrd_start_addr` environment variable. |
| 1362 | |
| 1363 | If no initramfs was provided by previous bootloader, no env variables |
| 1364 | will be created. |
| 1365 | |
Simon Glass | cf29816 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 1366 | endmenu # Booting |