Simon Glass | b45b163 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 1 | menu "Boot options" |
| 2 | |
| 3 | menu "Boot images" |
| 4 | |
| 5 | config ANDROID_BOOT_IMAGE |
Simon Glass | 7f541fc | 2023-09-14 10:55:48 -0600 | [diff] [blame] | 6 | bool "Android Boot Images" |
Simon Glass | b45b163 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 7 | default y if FASTBOOT |
| 8 | help |
| 9 | This enables support for booting images which use the Android |
| 10 | image format header. |
| 11 | |
Simon Glass | e9a089a | 2023-09-14 10:55:49 -0600 | [diff] [blame] | 12 | config TIMESTAMP |
| 13 | bool "Show image date and time when displaying image information" |
| 14 | default y if CMD_DATE |
| 15 | help |
| 16 | When CONFIG_TIMESTAMP is selected, the timestamp (date and time) of |
| 17 | an image is printed by image commands like bootm or iminfo. This |
| 18 | is shown as 'Timestamp: xxx' and 'Created: xxx'. If this option is |
| 19 | enabled, then U-Boot requires FITs to have a timestamp. If a FIT is |
| 20 | loaded that does not, the message 'Wrong FIT format: no timestamp' |
| 21 | is shown. |
| 22 | |
| 23 | menuconfig FIT |
| 24 | bool "Flattened Image Tree (FIT)" |
Alexandru Gagniuc | 650b786 | 2021-09-02 19:54:21 -0500 | [diff] [blame] | 25 | select HASH |
Simon Glass | b45b163 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 26 | select MD5 |
| 27 | select SHA1 |
Alexandru Gagniuc | 8d310ef | 2021-09-02 19:54:17 -0500 | [diff] [blame] | 28 | imply SHA256 |
Simon Glass | b45b163 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 29 | help |
| 30 | This option allows you to boot the new uImage structure, |
| 31 | Flattened Image Tree. FIT is formally a FDT, which can include |
| 32 | images of various types (kernel, FDT blob, ramdisk, etc.) |
| 33 | in a single blob. To boot this new uImage structure, |
| 34 | pass the address of the blob to the "bootm" command. |
| 35 | FIT is very flexible, supporting compression, multiple images, |
| 36 | multiple configurations, verification through hashing and also |
| 37 | verified boot (secure boot using RSA). |
| 38 | |
Simon Glass | e9a089a | 2023-09-14 10:55:49 -0600 | [diff] [blame] | 39 | if FIT |
Simon Glass | 65831d9 | 2021-12-18 11:27:50 -0700 | [diff] [blame] | 40 | |
Simon Glass | b45b163 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 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 | 244705b | 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 | b45b163 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 60 | config FIT_SIGNATURE |
| 61 | bool "Enable signature verification of FIT uImages" |
Simon Glass | e9a089a | 2023-09-14 10:55:49 -0600 | [diff] [blame] | 62 | depends on DM |
Simon Glass | b45b163 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 63 | select HASH |
Alexandru Gagniuc | 1f2e231 | 2021-07-29 11:47:18 -0500 | [diff] [blame] | 64 | imply RSA |
| 65 | imply RSA_VERIFY |
Simon Glass | b45b163 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 66 | select IMAGE_SIGN_INFO |
Simon Glass | 244705b | 2021-02-15 17:08:10 -0700 | [diff] [blame] | 67 | select FIT_FULL_CHECK |
Simon Glass | b45b163 | 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 | 66b00c8 | 2021-07-14 17:05:31 -0500 | [diff] [blame] | 91 | config FIT_RSASSA_PSS |
Simon Glass | b45b163 | 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 | b45b163 | 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" |
Simon Glass | e9a089a | 2023-09-14 10:55:49 -0600 | [diff] [blame] | 100 | depends on DM |
Simon Glass | b45b163 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 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" |
Manorit Chawdhry | f65cdf7 | 2023-07-14 11:22:40 +0530 | [diff] [blame] | 125 | depends on SOCFPGA_SECURE_VAB_AUTH |
Simon Glass | b45b163 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 126 | help |
| 127 | Allows doing any sort of manipulation to blobs after they got extracted |
| 128 | from FIT images like stripping off headers or modifying the size of the |
| 129 | blob, verification, authentication, decryption etc. in a platform or |
| 130 | board specific way. In order to use this feature a platform or board- |
| 131 | specific implementation of board_fit_image_post_process() must be |
| 132 | provided. Also, anything done during this post-processing step would |
| 133 | need to be comprehended in how the images were prepared before being |
| 134 | injected into the FIT creation (i.e. the blobs would have been pre- |
| 135 | processed before being added to the FIT image). |
| 136 | |
Ravik Hasija | 11dac41 | 2021-01-27 14:01:48 -0800 | [diff] [blame] | 137 | config FIT_PRINT |
| 138 | bool "Support FIT printing" |
| 139 | default y |
| 140 | help |
| 141 | Support printing the content of the fitImage in a verbose manner. |
| 142 | |
Simon Glass | b45b163 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 143 | config SPL_FIT |
| 144 | bool "Support Flattened Image Tree within SPL" |
Simon Glass | 2289ca9 | 2023-09-14 10:55:52 -0600 | [diff] [blame^] | 145 | depends on SPL |
Alexandru Gagniuc | 650b786 | 2021-09-02 19:54:21 -0500 | [diff] [blame] | 146 | select SPL_HASH |
Simon Glass | b45b163 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 147 | select SPL_OF_LIBFDT |
| 148 | |
| 149 | config SPL_FIT_PRINT |
| 150 | bool "Support FIT printing within SPL" |
| 151 | depends on SPL_FIT |
| 152 | help |
| 153 | Support printing the content of the fitImage in a verbose manner in SPL. |
| 154 | |
Simon Glass | 244705b | 2021-02-15 17:08:10 -0700 | [diff] [blame] | 155 | config SPL_FIT_FULL_CHECK |
| 156 | bool "Do a full check of the FIT before using it" |
Tom Rini | 0f3d1de | 2022-12-04 10:14:20 -0500 | [diff] [blame] | 157 | depends on SPL_FIT |
Simon Glass | 244705b | 2021-02-15 17:08:10 -0700 | [diff] [blame] | 158 | help |
| 159 | Enable this do a full check of the FIT to make sure it is valid. This |
| 160 | helps to protect against carefully crafted FITs which take advantage |
| 161 | of bugs or omissions in the code. This includes a bad structure, |
| 162 | multiple root nodes and the like. |
| 163 | |
Simon Glass | b45b163 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 164 | config SPL_FIT_SIGNATURE |
| 165 | bool "Enable signature verification of FIT firmware within SPL" |
| 166 | depends on SPL_DM |
Klaus Heinrich Kiwi | ae5073f | 2021-02-09 15:41:54 -0300 | [diff] [blame] | 167 | depends on SPL_LOAD_FIT || SPL_LOAD_FIT_FULL |
Klaus Heinrich Kiwi | c9796e6 | 2021-02-09 15:41:53 -0300 | [diff] [blame] | 168 | select FIT_SIGNATURE |
Simon Glass | b45b163 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 169 | select SPL_FIT |
Simon Glass | a8437ce | 2021-07-10 21:14:25 -0600 | [diff] [blame] | 170 | select SPL_CRYPTO |
Alexandru Gagniuc | 97464ff | 2021-09-02 19:54:19 -0500 | [diff] [blame] | 171 | select SPL_HASH |
Alexandru Gagniuc | 1f2e231 | 2021-07-29 11:47:18 -0500 | [diff] [blame] | 172 | imply SPL_RSA |
| 173 | imply SPL_RSA_VERIFY |
Simon Glass | b45b163 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 174 | select SPL_IMAGE_SIGN_INFO |
Simon Glass | 244705b | 2021-02-15 17:08:10 -0700 | [diff] [blame] | 175 | select SPL_FIT_FULL_CHECK |
Simon Glass | b45b163 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 176 | |
Simon Glass | c0cabbc | 2021-09-25 19:43:39 -0600 | [diff] [blame] | 177 | config SPL_FIT_SIGNATURE_MAX_SIZE |
| 178 | hex "Max size of signed FIT structures in SPL" |
| 179 | depends on SPL_FIT_SIGNATURE |
| 180 | default 0x10000000 |
| 181 | help |
| 182 | This option sets a max size in bytes for verified FIT uImages. |
| 183 | A sane value of 256MB protects corrupted DTB structures from overlapping |
| 184 | device memory. Assure this size does not extend past expected storage |
| 185 | space. |
| 186 | |
Philippe Reynes | 47f3eb2 | 2021-10-15 11:35:03 +0200 | [diff] [blame] | 187 | config SPL_FIT_RSASSA_PSS |
| 188 | bool "Support rsassa-pss signature scheme of FIT image contents in SPL" |
| 189 | depends on SPL_FIT_SIGNATURE |
| 190 | help |
| 191 | Enable this to support the pss padding algorithm as described |
| 192 | in the rfc8017 (https://tools.ietf.org/html/rfc8017) in SPL. |
| 193 | |
Simon Glass | b45b163 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 194 | config SPL_LOAD_FIT |
| 195 | bool "Enable SPL loading U-Boot as a FIT (basic fitImage features)" |
Simon Glass | 2289ca9 | 2023-09-14 10:55:52 -0600 | [diff] [blame^] | 196 | depends on SPL |
Simon Glass | b45b163 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 197 | select SPL_FIT |
| 198 | help |
| 199 | Normally with the SPL framework a legacy image is generated as part |
| 200 | of the build. This contains U-Boot along with information as to |
| 201 | where it should be loaded. This option instead enables generation |
| 202 | of a FIT (Flat Image Tree) which provides more flexibility. In |
| 203 | particular it can handle selecting from multiple device tree |
| 204 | and passing the correct one to U-Boot. |
| 205 | |
Alexandru Gagniuc | 064c9c2 | 2021-03-29 12:05:15 -0500 | [diff] [blame] | 206 | This path has the following limitations: |
| 207 | |
Bin Meng | 91cdcb9 | 2021-05-10 20:23:29 +0800 | [diff] [blame] | 208 | 1. "loadables" images, other than FDTs, which do not have a "load" |
Alexandru Gagniuc | 064c9c2 | 2021-03-29 12:05:15 -0500 | [diff] [blame] | 209 | property will not be loaded. This limitation also applies to FPGA |
| 210 | images with the correct "compatible" string. |
Oleksandr Suvorov | 1777357 | 2022-07-22 17:16:13 +0300 | [diff] [blame] | 211 | 2. For FPGA images, the supported "compatible" list is in the |
| 212 | doc/uImage.FIT/source_file_format.txt. |
Alexandru Gagniuc | 064c9c2 | 2021-03-29 12:05:15 -0500 | [diff] [blame] | 213 | 3. FDTs are only loaded for images with an "os" property of "u-boot". |
| 214 | "linux" images are also supported with Falcon boot mode. |
| 215 | |
Simon Glass | b45b163 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 216 | config SPL_LOAD_FIT_ADDRESS |
| 217 | hex "load address of fit image" |
Simon Glass | dfcedda | 2023-09-14 10:55:51 -0600 | [diff] [blame] | 218 | depends on SPL_LOAD_FIT |
Simon Glass | b45b163 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 219 | default 0x0 |
| 220 | help |
| 221 | Specify the load address of the fit image that will be loaded |
| 222 | by SPL. |
| 223 | |
| 224 | config SPL_LOAD_FIT_APPLY_OVERLAY |
| 225 | bool "Enable SPL applying DT overlays from FIT" |
| 226 | depends on SPL_LOAD_FIT |
| 227 | select OF_LIBFDT_OVERLAY |
| 228 | help |
Hugo Villeneuve | 5c1c6cc | 2023-04-24 16:51:12 -0400 | [diff] [blame] | 229 | The device tree is loaded from the FIT image. Allow the SPL to |
Simon Glass | b45b163 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 230 | also load device-tree overlays from the FIT image an apply them |
| 231 | over the device tree. |
| 232 | |
| 233 | config SPL_LOAD_FIT_APPLY_OVERLAY_BUF_SZ |
| 234 | depends on SPL_LOAD_FIT_APPLY_OVERLAY |
| 235 | default 0x10000 |
| 236 | hex "size of temporary buffer used to load the overlays" |
| 237 | help |
| 238 | The size of the area where the overlays will be loaded and |
| 239 | uncompress. Must be at least as large as biggest overlay |
| 240 | (uncompressed) |
| 241 | |
| 242 | config SPL_LOAD_FIT_FULL |
| 243 | bool "Enable SPL loading U-Boot as a FIT (full fitImage features)" |
| 244 | select SPL_FIT |
| 245 | help |
| 246 | Normally with the SPL framework a legacy image is generated as part |
| 247 | of the build. This contains U-Boot along with information as to |
| 248 | where it should be loaded. This option instead enables generation |
| 249 | of a FIT (Flat Image Tree) which provides more flexibility. In |
| 250 | particular it can handle selecting from multiple device tree |
| 251 | and passing the correct one to U-Boot. |
| 252 | |
| 253 | config SPL_FIT_IMAGE_POST_PROCESS |
| 254 | bool "Enable post-processing of FIT artifacts after loading by the SPL" |
| 255 | depends on SPL_LOAD_FIT |
Andrew Davis | 4ba9e6e | 2022-05-04 15:52:28 -0500 | [diff] [blame] | 256 | default y if TI_SECURE_DEVICE |
Simon Glass | b45b163 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 257 | help |
| 258 | Allows doing any sort of manipulation to blobs after they got extracted |
| 259 | from the U-Boot FIT image like stripping off headers or modifying the |
| 260 | size of the blob, verification, authentication, decryption etc. in a |
| 261 | platform or board specific way. In order to use this feature a platform |
| 262 | or board-specific implementation of board_fit_image_post_process() must |
| 263 | be provided. Also, anything done during this post-processing step would |
| 264 | need to be comprehended in how the images were prepared before being |
| 265 | injected into the FIT creation (i.e. the blobs would have been pre- |
| 266 | processed before being added to the FIT image). |
| 267 | |
| 268 | config SPL_FIT_SOURCE |
| 269 | string ".its source file for U-Boot FIT image" |
| 270 | depends on SPL_FIT |
| 271 | help |
| 272 | Specifies a (platform specific) FIT source file to generate the |
| 273 | U-Boot FIT image. This could specify further image to load and/or |
| 274 | execute. |
| 275 | |
| 276 | config USE_SPL_FIT_GENERATOR |
| 277 | bool "Use a script to generate the .its script" |
Tom Rini | 0f3d1de | 2022-12-04 10:14:20 -0500 | [diff] [blame] | 278 | depends on SPL_FIT |
Simon Glass | bd7694f | 2023-01-07 14:07:19 -0700 | [diff] [blame] | 279 | default y if SPL_FIT && ARCH_ZYNQMP |
Simon Glass | b45b163 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 280 | |
| 281 | config SPL_FIT_GENERATOR |
| 282 | string ".its file generator script for U-Boot FIT image" |
| 283 | depends on USE_SPL_FIT_GENERATOR |
Simon Glass | b45b163 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 284 | default "arch/arm/mach-zynqmp/mkimage_fit_atf.sh" if SPL_LOAD_FIT && ARCH_ZYNQMP |
Simon Glass | b45b163 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 285 | help |
| 286 | Specifies a (platform specific) script file to generate the FIT |
| 287 | source file used to build the U-Boot FIT image file. This gets |
| 288 | passed a list of supported device tree file stub names to |
| 289 | include in the generated image. |
| 290 | |
Simon Glass | bc993e5 | 2022-10-20 18:23:13 -0600 | [diff] [blame] | 291 | if VPL |
| 292 | |
| 293 | config VPL_FIT |
| 294 | bool "Support Flattened Image Tree within VPL" |
| 295 | depends on VPL |
| 296 | default y |
| 297 | select VPL_HASH |
| 298 | select VPL_OF_LIBFDT |
| 299 | |
| 300 | config VPL_FIT_PRINT |
| 301 | bool "Support FIT printing within VPL" |
| 302 | depends on VPL_FIT |
| 303 | default y |
| 304 | help |
| 305 | Support printing the content of the fitImage in a verbose manner in VPL. |
| 306 | |
| 307 | config VPL_FIT_FULL_CHECK |
| 308 | bool "Do a full check of the FIT before using it" |
| 309 | default y |
| 310 | help |
| 311 | Enable this do a full check of the FIT to make sure it is valid. This |
| 312 | helps to protect against carefully crafted FITs which take advantage |
| 313 | of bugs or omissions in the code. This includes a bad structure, |
| 314 | multiple root nodes and the like. |
| 315 | |
| 316 | config VPL_FIT_SIGNATURE |
| 317 | bool "Enable signature verification of FIT firmware within VPL" |
| 318 | depends on VPL_DM |
Simon Glass | bc993e5 | 2022-10-20 18:23:13 -0600 | [diff] [blame] | 319 | default y |
| 320 | select FIT_SIGNATURE |
| 321 | select VPL_FIT |
| 322 | select VPL_CRYPTO |
| 323 | select VPL_HASH |
| 324 | imply VPL_RSA |
| 325 | imply VPL_RSA_VERIFY |
| 326 | select VPL_IMAGE_SIGN_INFO |
| 327 | select VPL_FIT_FULL_CHECK |
| 328 | |
| 329 | config VPL_FIT_SIGNATURE_MAX_SIZE |
| 330 | hex "Max size of signed FIT structures in VPL" |
| 331 | depends on VPL_FIT_SIGNATURE |
| 332 | default 0x10000000 |
| 333 | help |
| 334 | This option sets a max size in bytes for verified FIT uImages. |
| 335 | A sane value of 256MB protects corrupted DTB structures from overlapping |
| 336 | device memory. Assure this size does not extend past expected storage |
| 337 | space. |
| 338 | |
| 339 | endif # VPL |
| 340 | |
Simon Glass | 2289ca9 | 2023-09-14 10:55:52 -0600 | [diff] [blame^] | 341 | endif # FIT |
| 342 | |
John Keeping | 9b60a17 | 2022-07-28 11:19:15 +0100 | [diff] [blame] | 343 | config PXE_UTILS |
| 344 | bool |
| 345 | select MENU |
| 346 | help |
| 347 | Utilities for parsing PXE file formats. |
| 348 | |
Simon Glass | 054d018 | 2023-03-24 16:58:13 -0400 | [diff] [blame] | 349 | config BOOT_DEFAULTS |
| 350 | bool # Common defaults for standard boot and distroboot |
| 351 | imply USE_BOOTCOMMAND |
| 352 | select CMD_ENV_EXISTS |
| 353 | select CMD_EXT2 |
| 354 | select CMD_EXT4 |
| 355 | select CMD_FAT |
| 356 | select CMD_FS_GENERIC |
| 357 | select CMD_PART if PARTITIONS |
| 358 | select CMD_DHCP if CMD_NET |
| 359 | select CMD_PING if CMD_NET |
| 360 | select CMD_PXE if CMD_NET |
| 361 | select SUPPORT_RAW_INITRD |
| 362 | select ENV_VARS_UBOOT_CONFIG |
| 363 | select CMD_BOOTI if ARM64 |
| 364 | select CMD_BOOTZ if ARM && !ARM64 |
| 365 | imply CMD_MII if NET |
| 366 | imply USB_STORAGE |
| 367 | imply EFI_PARTITION |
| 368 | imply ISO_PARTITION |
| 369 | help |
| 370 | These are not required but are commonly needed to support a good |
| 371 | selection of booting methods. Enable this to improve the capability |
| 372 | of U-Boot to boot various images. Currently much functionality is |
| 373 | tied to enabling the command that exercises it. |
| 374 | |
Simon Glass | 08ad13e | 2022-04-24 23:31:06 -0600 | [diff] [blame] | 375 | config BOOTSTD |
| 376 | bool "Standard boot support" |
| 377 | default y |
| 378 | depends on DM && OF_CONTROL && BLK |
| 379 | help |
| 380 | U-Boot supports a standard way of locating something to boot, |
| 381 | typically an Operating System such as Linux, provided by a distro such |
| 382 | as Arch Linux or Debian. Enable this to support iterating through |
| 383 | available bootdevs and using bootmeths to find bootflows suitable for |
| 384 | booting. |
| 385 | |
| 386 | Standard boot is not a standard way of booting, just a framework |
| 387 | within U-Boot for supporting all the different ways that exist. |
| 388 | |
| 389 | Terminology: |
| 390 | |
| 391 | - bootdev - a device which can hold a distro (e.g. MMC) |
| 392 | - bootmeth - a method to scan a bootdev to find bootflows (owned by |
| 393 | U-Boot) |
| 394 | - bootflow - a description of how to boot (owned by the distro) |
| 395 | |
Simon Glass | bc993e5 | 2022-10-20 18:23:13 -0600 | [diff] [blame] | 396 | config SPL_BOOTSTD |
Simon Glass | 4aa874f | 2023-02-22 09:33:58 -0700 | [diff] [blame] | 397 | bool "Standard boot support in SPL" |
Simon Glass | bc993e5 | 2022-10-20 18:23:13 -0600 | [diff] [blame] | 398 | depends on SPL && SPL_DM && SPL_OF_CONTROL && SPL_BLK |
| 399 | default y if VPL |
| 400 | help |
| 401 | This enables standard boot in SPL. This is neeeded so that VBE |
| 402 | (Verified Boot for Embedded) can be used, since it depends on standard |
| 403 | boot. It is enabled by default since the main purpose of VPL is to |
| 404 | handle the firmware part of VBE. |
| 405 | |
| 406 | config VPL_BOOTSTD |
| 407 | bool "Standard boot support in VPL" |
| 408 | depends on VPL && VPL_DM && VPL_OF_CONTROL && VPL_BLK |
| 409 | default y |
| 410 | help |
| 411 | This enables standard boot in SPL. This is neeeded so that VBE |
| 412 | (Verified Boot for Embedded) can be used, since it depends on standard |
| 413 | boot. It is enabled by default since the main purpose of VPL is to |
| 414 | handle the firmware part of VBE. |
| 415 | |
Simon Glass | ad8ec37 | 2022-04-24 23:31:13 -0600 | [diff] [blame] | 416 | if BOOTSTD |
| 417 | |
Simon Glass | 78c79dd | 2023-02-22 14:06:23 -0700 | [diff] [blame] | 418 | config BOOTSTD_FULL |
| 419 | bool "Enhanced features for standard boot" |
| 420 | default y if SANDBOX |
| 421 | help |
| 422 | This enables various useful features for standard boot, which are not |
| 423 | essential for operation: |
| 424 | |
| 425 | - bootdev, bootmeth commands |
| 426 | - extra features in the bootflow command |
| 427 | - support for selecting the ordering of bootmeths ("bootmeth order") |
| 428 | - support for selecting the ordering of bootdevs using the devicetree |
| 429 | as well as the "boot_targets" environment variable |
| 430 | |
Simon Glass | 2e5161eb | 2023-01-28 15:00:21 -0700 | [diff] [blame] | 431 | config BOOTSTD_DEFAULTS |
| 432 | bool "Select some common defaults for standard boot" |
| 433 | depends on BOOTSTD |
| 434 | imply USE_BOOTCOMMAND |
Simon Glass | 054d018 | 2023-03-24 16:58:13 -0400 | [diff] [blame] | 435 | select BOOT_DEFAULTS |
Simon Glass | db92e78 | 2023-05-10 16:34:47 -0600 | [diff] [blame] | 436 | select BOOTMETH_DISTRO |
Simon Glass | 2e5161eb | 2023-01-28 15:00:21 -0700 | [diff] [blame] | 437 | help |
| 438 | These are not required but are commonly needed to support a good |
| 439 | selection of booting methods. Enable this to improve the capability |
| 440 | of U-Boot to boot various images. |
| 441 | |
Simon Glass | be661cb | 2022-04-24 23:31:27 -0600 | [diff] [blame] | 442 | config BOOTSTD_BOOTCOMMAND |
| 443 | bool "Use bootstd to boot" |
| 444 | default y if !DISTRO_DEFAULTS |
| 445 | help |
| 446 | Enable this to select a default boot-command suitable for booting |
| 447 | with standard boot. This can be overridden by the board if needed, |
| 448 | but the default command should be enough for most boards which use |
| 449 | standard boot. |
| 450 | |
| 451 | For now this is only selected if distro boot is NOT used, since |
| 452 | standard boot does not support all of the features of distro boot |
| 453 | yet. |
| 454 | |
Simon Glass | 4f8633d | 2022-07-30 15:52:21 -0600 | [diff] [blame] | 455 | config BOOTMETH_GLOBAL |
| 456 | bool |
| 457 | help |
| 458 | Add support for global bootmeths. This feature is used by VBE and |
| 459 | EFI bootmgr, since they take full control over which bootdevs are |
| 460 | selected to boot. |
| 461 | |
Simon Glass | d74e62a | 2023-07-12 09:04:45 -0600 | [diff] [blame] | 462 | config BOOTMETH_CROS |
| 463 | bool "Bootdev support for Chromium OS" |
Simon Glass | 1870026 | 2023-07-30 11:17:02 -0600 | [diff] [blame] | 464 | depends on X86 || ARM || SANDBOX |
| 465 | default y if !ARM |
Simon Glass | d7d3a97 | 2023-08-24 13:55:45 -0600 | [diff] [blame] | 466 | select EFI_PARTITION |
| 467 | select PARTITION_TYPE_GUID |
| 468 | select PARTITION_UUIDS |
Simon Glass | d74e62a | 2023-07-12 09:04:45 -0600 | [diff] [blame] | 469 | help |
| 470 | Enables support for booting Chromium OS using bootdevs. This uses the |
| 471 | kernel A slot and obtains the kernel command line from the parameters |
| 472 | provided there. |
| 473 | |
| 474 | Note that only x86 devices are supported at present. |
| 475 | |
Simon Glass | b71d7f7 | 2023-05-10 16:34:46 -0600 | [diff] [blame] | 476 | config BOOTMETH_EXTLINUX |
| 477 | bool "Bootdev support for extlinux boot" |
John Keeping | 9b60a17 | 2022-07-28 11:19:15 +0100 | [diff] [blame] | 478 | select PXE_UTILS |
Simon Glass | ad8ec37 | 2022-04-24 23:31:13 -0600 | [diff] [blame] | 479 | default y |
| 480 | help |
Simon Glass | b71d7f7 | 2023-05-10 16:34:46 -0600 | [diff] [blame] | 481 | Enables support for extlinux boot using bootdevs. This makes the |
Simon Glass | ad8ec37 | 2022-04-24 23:31:13 -0600 | [diff] [blame] | 482 | bootdevs look for a 'extlinux/extlinux.conf' on each filesystem |
| 483 | they scan. |
| 484 | |
Simon Glass | b71d7f7 | 2023-05-10 16:34:46 -0600 | [diff] [blame] | 485 | The specification for this filed is here: |
| 486 | |
| 487 | https://uapi-group.org/specifications/specs/boot_loader_specification/ |
| 488 | |
Simon Glass | ad8ec37 | 2022-04-24 23:31:13 -0600 | [diff] [blame] | 489 | This provides a way to try out standard boot on an existing boot flow. |
| 490 | |
Simon Glass | b71d7f7 | 2023-05-10 16:34:46 -0600 | [diff] [blame] | 491 | config BOOTMETH_EXTLINUX_PXE |
| 492 | bool "Bootdev support for extlinux boot over network" |
Simon Glass | 8314461 | 2022-04-24 23:31:16 -0600 | [diff] [blame] | 493 | depends on CMD_PXE && CMD_NET && DM_ETH |
| 494 | default y |
| 495 | help |
Simon Glass | b71d7f7 | 2023-05-10 16:34:46 -0600 | [diff] [blame] | 496 | Enables support for extlinux boot using bootdevs. This makes the |
Simon Glass | 8314461 | 2022-04-24 23:31:16 -0600 | [diff] [blame] | 497 | bootdevs look for a 'extlinux/extlinux.conf' on the tftp server. |
| 498 | |
Simon Glass | b71d7f7 | 2023-05-10 16:34:46 -0600 | [diff] [blame] | 499 | The specification for this file is here: |
| 500 | |
| 501 | https://uapi-group.org/specifications/specs/boot_loader_specification/ |
| 502 | |
Simon Glass | 8314461 | 2022-04-24 23:31:16 -0600 | [diff] [blame] | 503 | This provides a way to try out standard boot on an existing boot flow. |
| 504 | |
Simon Glass | 66f6255 | 2022-04-24 23:31:17 -0600 | [diff] [blame] | 505 | config BOOTMETH_EFILOADER |
| 506 | bool "Bootdev support for EFI boot" |
Simon Glass | db92e78 | 2023-05-10 16:34:47 -0600 | [diff] [blame] | 507 | depends on EFI_LOADER |
Simon Glass | 66f6255 | 2022-04-24 23:31:17 -0600 | [diff] [blame] | 508 | default y |
| 509 | help |
| 510 | Enables support for EFI boot using bootdevs. This makes the |
| 511 | bootdevs look for a 'boot<arch>.efi' on each filesystem |
| 512 | they scan. The resulting file is booted after enabling U-Boot's |
| 513 | EFI loader support. |
| 514 | |
| 515 | The <arch> depends on the architecture of the board: |
| 516 | |
| 517 | aa64 - aarch64 (ARM 64-bit) |
| 518 | arm - ARM 32-bit |
| 519 | ia32 - x86 32-bit |
| 520 | x64 - x86 64-bit |
| 521 | riscv32 - RISC-V 32-bit |
| 522 | riscv64 - RISC-V 64-bit |
| 523 | |
| 524 | This provides a way to try out standard boot on an existing boot flow. |
| 525 | |
Simon Glass | 0a9f426 | 2022-07-30 15:52:32 -0600 | [diff] [blame] | 526 | config BOOTMETH_VBE |
| 527 | bool "Bootdev support for Verified Boot for Embedded" |
| 528 | depends on FIT |
| 529 | default y |
| 530 | select BOOTMETH_GLOBAL |
Tom Rini | 7d3684a | 2023-01-16 15:46:49 -0500 | [diff] [blame] | 531 | select EVENT |
Simon Glass | 0a9f426 | 2022-07-30 15:52:32 -0600 | [diff] [blame] | 532 | help |
| 533 | Enables support for VBE boot. This is a standard boot method which |
| 534 | supports selection of various firmware components, seleciton of an OS to |
| 535 | boot as well as updating these using fwupd. |
| 536 | |
Simon Glass | db92e78 | 2023-05-10 16:34:47 -0600 | [diff] [blame] | 537 | config BOOTMETH_DISTRO |
| 538 | bool # Options needed to boot any distro |
| 539 | select BOOTMETH_SCRIPT # E.g. Armbian uses scripts |
| 540 | select BOOTMETH_EXTLINUX # E.g. Debian uses these |
| 541 | select BOOTMETH_EXTLINUX_PXE if CMD_PXE && CMD_NET && DM_ETH |
| 542 | select BOOTMETH_EFILOADER if EFI_LOADER # E.g. Ubuntu uses this |
| 543 | |
Simon Glass | bc993e5 | 2022-10-20 18:23:13 -0600 | [diff] [blame] | 544 | config SPL_BOOTMETH_VBE |
| 545 | bool "Bootdev support for Verified Boot for Embedded (SPL)" |
| 546 | depends on SPL && FIT |
Tom Rini | 7d3684a | 2023-01-16 15:46:49 -0500 | [diff] [blame] | 547 | select EVENT |
Simon Glass | bc993e5 | 2022-10-20 18:23:13 -0600 | [diff] [blame] | 548 | default y if VPL |
| 549 | help |
| 550 | Enables support for VBE boot. This is a standard boot method which |
| 551 | supports selection of various firmware components, seleciton of an OS to |
| 552 | boot as well as updating these using fwupd. |
| 553 | |
| 554 | config VPL_BOOTMETH_VBE |
| 555 | bool "Bootdev support for Verified Boot for Embedded (VPL)" |
| 556 | depends on VPL && FIT |
Tom Rini | 7d3684a | 2023-01-16 15:46:49 -0500 | [diff] [blame] | 557 | select EVENT |
Simon Glass | bc993e5 | 2022-10-20 18:23:13 -0600 | [diff] [blame] | 558 | default y |
| 559 | help |
| 560 | Enables support for VBE boot. This is a standard boot method which |
| 561 | supports selection of various firmware components, seleciton of an OS to |
| 562 | boot as well as updating these using fwupd. |
| 563 | |
Simon Glass | d0af04c | 2022-07-30 15:52:33 -0600 | [diff] [blame] | 564 | if BOOTMETH_VBE |
| 565 | |
Simon Glass | 513eeed | 2023-02-22 09:33:52 -0700 | [diff] [blame] | 566 | config BOOTMETH_VBE_REQUEST |
| 567 | bool "Support for serving VBE OS requests" |
| 568 | default y |
| 569 | help |
| 570 | Enables support for looking that the requests made by the |
| 571 | Operating System being booted. These requests result in additions to |
| 572 | the device tree /chosen node, added during the device tree fixup |
| 573 | phase. |
| 574 | |
| 575 | config SPL_BOOTMETH_VBE_REQUEST |
| 576 | bool "Support for serving VBE OS requests (SPL)" |
| 577 | depends on SPL |
| 578 | help |
| 579 | Enables support for looking that the requests made by the |
| 580 | Operating System being booted. These requests result in additions to |
| 581 | the device tree /chosen node, added during the device tree fixup |
| 582 | phase. |
| 583 | |
| 584 | This is only useful if you are booting an OS direct from SPL. |
| 585 | |
Simon Glass | d0af04c | 2022-07-30 15:52:33 -0600 | [diff] [blame] | 586 | config BOOTMETH_VBE_SIMPLE |
| 587 | bool "Bootdev support for VBE 'simple' method" |
| 588 | default y |
| 589 | help |
| 590 | Enables support for VBE 'simple' boot. This allows updating a single |
| 591 | firmware image in boot media such as MMC. It does not support any sort |
| 592 | of rollback, recovery or A/B boot. |
| 593 | |
Simon Glass | bc993e5 | 2022-10-20 18:23:13 -0600 | [diff] [blame] | 594 | config BOOTMETH_VBE_SIMPLE_OS |
| 595 | bool "Bootdev support for VBE 'simple' method OS phase" |
| 596 | default y |
| 597 | help |
| 598 | Enables support for the OS parts of VBE 'simple' boot. This includes |
| 599 | fixing up the device tree with the required VBE information, ready |
| 600 | for booting into the OS. This option is only enabled for U-Boot |
| 601 | proper, since it is the phase where device tree fixups happen. |
| 602 | |
| 603 | config SPL_BOOTMETH_VBE_SIMPLE |
| 604 | bool "Bootdev support for VBE 'simple' method (SPL)" |
| 605 | depends on SPL |
| 606 | default y if VPL |
| 607 | help |
| 608 | Enables support for VBE 'simple' boot. This allows updating a single |
| 609 | firmware image in boot media such as MMC. It does not support any sort |
| 610 | of rollback, recovery or A/B boot. |
| 611 | |
| 612 | config VPL_BOOTMETH_VBE_SIMPLE |
| 613 | bool "Bootdev support for VBE 'simple' method (VPL)" |
| 614 | depends on VPL |
| 615 | default y |
| 616 | help |
| 617 | Enables support for VBE 'simple' boot. This allows updating a single |
| 618 | firmware image in boot media such as MMC. It does not support any sort |
| 619 | of rollback, recovery or A/B boot. |
| 620 | |
| 621 | config SPL_BOOTMETH_VBE_SIMPLE_FW |
| 622 | bool "Bootdev support for VBE 'simple' method firmware phase (SPL)" |
| 623 | depends on VPL |
| 624 | default y |
| 625 | help |
| 626 | Enables support for the firmware parts of VBE 'simple' boot. This |
| 627 | includes an SPL loader which locates the correct U-Boot to boot into. |
| 628 | This option should really only be enabled for VPL, since it is the |
| 629 | phase where the SPL + U-Boot decision should be made. But for now, |
| 630 | SPL does its own FIT-configuration selection. |
| 631 | |
| 632 | config VPL_BOOTMETH_VBE_SIMPLE_FW |
| 633 | bool "Bootdev support for VBE 'simple' method firmware phase (VPL)" |
| 634 | depends on VPL |
| 635 | default y |
| 636 | help |
| 637 | Enables support for the firmware parts of VBE 'simple' boot. This |
| 638 | includes an SPL loader which locates the correct SPL to boot into. |
| 639 | This option enabled for VPL, since it is the phase where the SPL |
| 640 | decision is made. |
| 641 | |
Simon Glass | d0af04c | 2022-07-30 15:52:33 -0600 | [diff] [blame] | 642 | endif # BOOTMETH_VBE |
| 643 | |
Simon Glass | d8adbe9 | 2023-01-06 08:52:36 -0600 | [diff] [blame] | 644 | config EXPO |
| 645 | bool "Support for expos - groups of scenes displaying a UI" |
Simon Glass | 389a458 | 2023-01-28 15:00:18 -0700 | [diff] [blame] | 646 | depends on VIDEO |
Simon Glass | d8adbe9 | 2023-01-06 08:52:36 -0600 | [diff] [blame] | 647 | default y if BOOTMETH_VBE |
| 648 | help |
| 649 | An expo is a way of presenting and collecting information from the |
| 650 | user. It consists of a collection of 'scenes' of which only one is |
| 651 | presented at a time. An expo is typically used to show a boot menu |
| 652 | and allow settings to be changed. |
| 653 | |
| 654 | The expo can be presented in graphics form using a vidconsole, or in |
| 655 | text form on a serial console. |
| 656 | |
Simon Glass | 423994e | 2022-04-24 23:31:20 -0600 | [diff] [blame] | 657 | config BOOTMETH_SANDBOX |
| 658 | def_bool y |
| 659 | depends on SANDBOX |
| 660 | help |
| 661 | This is a sandbox bootmeth driver used for testing. It always returns |
| 662 | -ENOTSUPP when attempting to boot. |
| 663 | |
Simon Glass | 7e03e74 | 2022-04-24 23:31:22 -0600 | [diff] [blame] | 664 | config BOOTMETH_SCRIPT |
| 665 | bool "Bootdev support for U-Boot scripts" |
| 666 | default y if BOOTSTD_FULL |
Simon Glass | b4b7ebe | 2023-05-05 20:03:05 -0600 | [diff] [blame] | 667 | select HUSH_PARSER |
Simon Glass | 7e03e74 | 2022-04-24 23:31:22 -0600 | [diff] [blame] | 668 | help |
| 669 | Enables support for booting a distro via a U-Boot script. This makes |
| 670 | the bootdevs look for a 'boot/boot.scr' file which can be used to |
| 671 | boot the distro. |
| 672 | |
| 673 | This provides a way to try out standard boot on an existing boot flow. |
| 674 | It is not enabled by default to save space. |
| 675 | |
Simon Glass | ad8ec37 | 2022-04-24 23:31:13 -0600 | [diff] [blame] | 676 | endif |
| 677 | |
Simon Glass | b45b163 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 678 | config LEGACY_IMAGE_FORMAT |
| 679 | bool "Enable support for the legacy image format" |
Andrew Davis | 98a22d0 | 2022-05-04 15:52:27 -0500 | [diff] [blame] | 680 | default y if !FIT_SIGNATURE && !TI_SECURE_DEVICE |
Simon Glass | b45b163 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 681 | help |
| 682 | This option enables the legacy image format. It is enabled by |
| 683 | default for backward compatibility, unless FIT_SIGNATURE is |
| 684 | set where it is disabled so that unsigned images cannot be |
| 685 | loaded. If a board needs the legacy image format support in this |
| 686 | case, enable it here. |
| 687 | |
Simon Glass | f11d613 | 2020-09-10 20:21:19 -0600 | [diff] [blame] | 688 | config SUPPORT_RAW_INITRD |
| 689 | bool "Enable raw initrd images" |
| 690 | help |
| 691 | Note, defining the SUPPORT_RAW_INITRD allows user to supply |
| 692 | kernel with raw initrd images. The syntax is slightly different, the |
| 693 | address of the initrd must be augmented by it's size, in the following |
| 694 | format: "<initrd address>:<initrd size>". |
| 695 | |
Simon Glass | 72cc538 | 2022-10-20 18:22:39 -0600 | [diff] [blame] | 696 | config HAVE_TEXT_BASE |
Simon Glass | b45b163 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 697 | bool |
| 698 | depends on !NIOS2 && !XTENSA |
| 699 | depends on !EFI_APP |
| 700 | default y |
| 701 | |
Simon Glass | 72cc538 | 2022-10-20 18:22:39 -0600 | [diff] [blame] | 702 | config TEXT_BASE |
| 703 | depends on HAVE_TEXT_BASE |
Tom Rini | 63471d5 | 2021-07-09 10:39:21 -0400 | [diff] [blame] | 704 | default 0x0 if POSITION_INDEPENDENT |
Simon Glass | b45b163 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 705 | default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3 |
Icenowy Zheng | 711fab3 | 2022-01-29 10:23:09 -0500 | [diff] [blame] | 706 | default 0x81700000 if MACH_SUNIV |
| 707 | default 0x2a000000 if MACH_SUN9I |
Andre Przywara | a2860fb | 2022-07-03 00:47:20 +0100 | [diff] [blame] | 708 | default 0x4a000000 if SUNXI_MINIMUM_DRAM_MB >= 256 |
| 709 | default 0x42e00000 if SUNXI_MINIMUM_DRAM_MB >= 64 |
Simon Glass | b45b163 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 710 | hex "Text Base" |
| 711 | help |
| 712 | The address in memory that U-Boot will be running from, initially. |
| 713 | |
Tom Rini | 03becca | 2022-03-24 17:18:05 -0400 | [diff] [blame] | 714 | config HAVE_SYS_MONITOR_BASE |
| 715 | bool |
| 716 | depends on ARC || MIPS || M68K || NIOS2 || PPC || XTENSA || X86 \ |
Tom Rini | 57f2c29 | 2022-07-23 13:05:01 -0400 | [diff] [blame] | 717 | || ENV_IS_IN_FLASH || MTD_NOR_FLASH |
Tom Rini | 03becca | 2022-03-24 17:18:05 -0400 | [diff] [blame] | 718 | depends on !EFI_APP |
| 719 | default y |
| 720 | |
| 721 | config SYS_MONITOR_BASE |
| 722 | depends on HAVE_SYS_MONITOR_BASE |
| 723 | hex "Physical start address of boot monitor code" |
Simon Glass | 72cc538 | 2022-10-20 18:22:39 -0600 | [diff] [blame] | 724 | default TEXT_BASE |
Tom Rini | 03becca | 2022-03-24 17:18:05 -0400 | [diff] [blame] | 725 | help |
| 726 | The physical start address of boot monitor code (which is the same as |
Tom Rini | 6a5dccc | 2022-11-16 13:10:41 -0500 | [diff] [blame] | 727 | CONFIG_TEXT_BASE when linking) and the same as CFG_SYS_FLASH_BASE |
Tom Rini | 03becca | 2022-03-24 17:18:05 -0400 | [diff] [blame] | 728 | when booting from flash. |
| 729 | |
| 730 | config SPL_SYS_MONITOR_BASE |
| 731 | depends on MPC85xx && SPL && HAVE_SYS_MONITOR_BASE |
| 732 | hex "Physical start address of SPL monitor code" |
| 733 | default SPL_TEXT_BASE |
| 734 | |
| 735 | config TPL_SYS_MONITOR_BASE |
| 736 | depends on MPC85xx && TPL && HAVE_SYS_MONITOR_BASE |
| 737 | hex "Physical start address of TPL monitor code" |
| 738 | |
Tom Rini | 8c70baa | 2021-12-14 13:36:40 -0500 | [diff] [blame] | 739 | config DYNAMIC_SYS_CLK_FREQ |
| 740 | bool "Determine CPU clock frequency at run-time" |
| 741 | help |
| 742 | Implement a get_board_sys_clk function that will determine the CPU |
| 743 | clock frequency at run time, rather than define it statically. |
| 744 | |
Simon Glass | b45b163 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 745 | config SYS_CLK_FREQ |
Tom Rini | 8c70baa | 2021-12-14 13:36:40 -0500 | [diff] [blame] | 746 | depends on !DYNAMIC_SYS_CLK_FREQ |
Simon Glass | b45b163 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 747 | int "CPU clock frequency" |
Tom Rini | 8c70baa | 2021-12-14 13:36:40 -0500 | [diff] [blame] | 748 | default 125000000 if ARCH_LS1012A |
| 749 | default 100000000 if ARCH_P2020 || ARCH_T1024 || ARCH_T1042 || \ |
| 750 | ARCH_LS1021A || FSL_LSCH2 || FSL_LSCH3 |
| 751 | default 66666666 if ARCH_P1010 || ARCH_P1020 || ARCH_T4240 |
| 752 | default 66660000 if ARCH_T2080 |
| 753 | default 33333333 if RCAR_GEN3 |
| 754 | default 24000000 if ARCH_EXYNOS |
| 755 | default 20000000 if RCAR_GEN2 |
| 756 | default 0 |
Simon Glass | b45b163 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 757 | help |
Tom Rini | 8c70baa | 2021-12-14 13:36:40 -0500 | [diff] [blame] | 758 | A static value for the CPU frequency. Note that if not required |
| 759 | for a given SoC, this can be left at 0. |
Simon Glass | b45b163 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 760 | |
| 761 | config ARCH_FIXUP_FDT_MEMORY |
| 762 | bool "Enable arch_fixup_memory_banks() call" |
| 763 | default y |
| 764 | help |
| 765 | Enable FDT memory map syncup before OS boot. This feature can be |
| 766 | used for booting OS with different memory setup where the part of |
| 767 | the memory location should be used for different purpose. |
| 768 | |
Simon Glass | d81f07f | 2020-11-04 09:57:35 -0700 | [diff] [blame] | 769 | config CHROMEOS |
| 770 | bool "Support booting Chrome OS" |
| 771 | help |
| 772 | Chrome OS requires U-Boot to set up a table indicating the boot mode |
| 773 | (e.g. Developer mode) and a few other things. Enable this if you are |
| 774 | booting on a Chromebook to avoid getting an error about an invalid |
| 775 | firmware ID. |
| 776 | |
| 777 | config CHROMEOS_VBOOT |
| 778 | bool "Support Chrome OS verified boot" |
| 779 | help |
| 780 | This is intended to enable the full Chrome OS verified boot support |
| 781 | in U-Boot. It is not actually implemented in the U-Boot source code |
| 782 | at present, so this option is always set to 'n'. It allows |
| 783 | distinguishing between booting Chrome OS in a basic way (developer |
| 784 | mode) and a full boot. |
| 785 | |
Tom Rini | eb4f2de | 2022-06-25 11:02:44 -0400 | [diff] [blame] | 786 | config SYS_RAMBOOT |
| 787 | bool |
| 788 | |
Tom Rini | 9ff815a | 2021-08-24 23:11:49 -0400 | [diff] [blame] | 789 | config RAMBOOT_PBL |
| 790 | bool "Freescale PBL(pre-boot loader) image format support" |
Tom Rini | eb4f2de | 2022-06-25 11:02:44 -0400 | [diff] [blame] | 791 | select SYS_RAMBOOT if PPC |
Tom Rini | 9ff815a | 2021-08-24 23:11:49 -0400 | [diff] [blame] | 792 | help |
| 793 | Some SoCs use PBL to load RCW and/or pre-initialization instructions. |
| 794 | For more details refer to doc/README.pblimage |
| 795 | |
Tom Rini | 886e6e3 | 2022-03-23 17:20:03 -0400 | [diff] [blame] | 796 | choice |
Tom Rini | 489f402 | 2022-12-28 10:52:51 -0500 | [diff] [blame] | 797 | prompt "Freescale PBL (or predecessor) load location" |
Tom Rini | 886e6e3 | 2022-03-23 17:20:03 -0400 | [diff] [blame] | 798 | depends on RAMBOOT_PBL || ((TARGET_P1010RDB_PA || TARGET_P1010RDB_PB \ |
| 799 | || TARGET_P1020RDB_PC || TARGET_P1020RDB_PD || TARGET_P2020RDB) \ |
| 800 | && !CMD_NAND) |
| 801 | |
| 802 | config SDCARD |
Tom Rini | 489f402 | 2022-12-28 10:52:51 -0500 | [diff] [blame] | 803 | bool "Freescale PBL (or similar) is found on SD card" |
Tom Rini | 886e6e3 | 2022-03-23 17:20:03 -0400 | [diff] [blame] | 804 | |
| 805 | config SPIFLASH |
Tom Rini | 489f402 | 2022-12-28 10:52:51 -0500 | [diff] [blame] | 806 | bool "Freescale PBL (or similar) is found on SPI flash" |
| 807 | |
| 808 | config NO_PBL |
| 809 | bool "Freescale PBL (or similar) is not used in this case" |
Tom Rini | 886e6e3 | 2022-03-23 17:20:03 -0400 | [diff] [blame] | 810 | |
| 811 | endchoice |
| 812 | |
Tom Rini | 5989fd4 | 2022-06-20 08:07:42 -0400 | [diff] [blame] | 813 | config FSL_FIXED_MMC_LOCATION |
| 814 | bool "PBL MMC is at a fixed location" |
| 815 | depends on SDCARD && !RAMBOOT_PBL |
| 816 | |
| 817 | config ESDHC_HC_BLK_ADDR |
| 818 | def_bool y |
| 819 | depends on FSL_FIXED_MMC_LOCATION && (ARCH_BSC9131 || ARCH_BSC9132 || ARCH_P1010) |
| 820 | help |
| 821 | In High Capacity SD Cards (> 2 GBytes), the 32-bit source address and |
| 822 | code length of these soc specify the memory address in block address |
| 823 | format. Block length is fixed to 512 bytes as per the SD High |
| 824 | Capacity specification. |
| 825 | |
Tom Rini | 9ff815a | 2021-08-24 23:11:49 -0400 | [diff] [blame] | 826 | config SYS_FSL_PBL_PBI |
| 827 | string "PBI(pre-boot instructions) commands for the PBL image" |
| 828 | depends on RAMBOOT_PBL |
| 829 | help |
| 830 | PBI commands can be used to configure SoC before it starts the execution. |
| 831 | Please refer doc/README.pblimage for more details. |
| 832 | |
| 833 | config SYS_FSL_PBL_RCW |
| 834 | string "Aadditional RCW (Power on reset configuration) for the PBL image" |
| 835 | depends on RAMBOOT_PBL |
| 836 | help |
| 837 | Enables addition of RCW (Power on reset configuration) in built image. |
| 838 | Please refer doc/README.pblimage for more details. |
| 839 | |
Tom Rini | 94b4fec | 2022-06-25 11:02:46 -0400 | [diff] [blame] | 840 | config SYS_BOOT_RAMDISK_HIGH |
| 841 | depends on CMD_BOOTM || CMD_BOOTI || CMD_BOOTZ |
| 842 | depends on !(NIOS2 || SANDBOX || SH || XTENSA) |
| 843 | def_bool y |
Simon Glass | 65edcd3 | 2023-03-24 16:58:12 -0400 | [diff] [blame] | 844 | select LMB |
Tom Rini | 94b4fec | 2022-06-25 11:02:46 -0400 | [diff] [blame] | 845 | help |
| 846 | Enable initrd_high functionality. If defined then the initrd_high |
| 847 | feature is enabled and the boot* ramdisk subcommand is enabled. |
| 848 | |
Simon Glass | b45b163 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 849 | endmenu # Boot images |
| 850 | |
Simon Glass | f111bf7 | 2023-03-24 16:58:11 -0400 | [diff] [blame] | 851 | config DISTRO_DEFAULTS |
| 852 | bool "Select defaults suitable for booting general purpose Linux distributions" |
Simon Glass | 054d018 | 2023-03-24 16:58:13 -0400 | [diff] [blame] | 853 | select BOOT_DEFAULTS |
Simon Glass | f111bf7 | 2023-03-24 16:58:11 -0400 | [diff] [blame] | 854 | select AUTO_COMPLETE |
| 855 | select CMDLINE_EDITING |
Simon Glass | f111bf7 | 2023-03-24 16:58:11 -0400 | [diff] [blame] | 856 | select CMD_SYSBOOT |
Simon Glass | f111bf7 | 2023-03-24 16:58:11 -0400 | [diff] [blame] | 857 | select HUSH_PARSER |
Simon Glass | f111bf7 | 2023-03-24 16:58:11 -0400 | [diff] [blame] | 858 | select SYS_LONGHELP |
Simon Glass | f111bf7 | 2023-03-24 16:58:11 -0400 | [diff] [blame] | 859 | help |
| 860 | Select this to enable various options and commands which are suitable |
| 861 | for building u-boot for booting general purpose Linux distributions. |
| 862 | |
Simon Glass | d02ddcf | 2020-09-10 20:21:14 -0600 | [diff] [blame] | 863 | menu "Boot timing" |
| 864 | |
| 865 | config BOOTSTAGE |
| 866 | bool "Boot timing and reporting" |
| 867 | help |
| 868 | Enable recording of boot time while booting. To use it, insert |
| 869 | calls to bootstage_mark() with a suitable BOOTSTAGE_ID from |
| 870 | bootstage.h. Only a single entry is recorded for each ID. You can |
| 871 | give the entry a name with bootstage_mark_name(). You can also |
| 872 | record elapsed time in a particular stage using bootstage_start() |
| 873 | before starting and bootstage_accum() when finished. Bootstage will |
| 874 | add up all the accumulated time and report it. |
| 875 | |
| 876 | Normally, IDs are defined in bootstage.h but a small number of |
| 877 | additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC |
| 878 | as the ID. |
| 879 | |
| 880 | Calls to show_boot_progress() will also result in log entries but |
| 881 | these will not have names. |
| 882 | |
| 883 | config SPL_BOOTSTAGE |
| 884 | bool "Boot timing and reported in SPL" |
Tom Rini | 0a83cc2 | 2022-06-10 23:03:09 -0400 | [diff] [blame] | 885 | depends on BOOTSTAGE && SPL |
Simon Glass | d02ddcf | 2020-09-10 20:21:14 -0600 | [diff] [blame] | 886 | help |
| 887 | Enable recording of boot time in SPL. To make this visible to U-Boot |
| 888 | proper, enable BOOTSTAGE_STASH as well. This will stash the timing |
| 889 | information when SPL finishes and load it when U-Boot proper starts |
| 890 | up. |
| 891 | |
| 892 | config TPL_BOOTSTAGE |
| 893 | bool "Boot timing and reported in TPL" |
Tom Rini | 36a4ca0 | 2022-06-08 08:24:39 -0400 | [diff] [blame] | 894 | depends on BOOTSTAGE && TPL |
Simon Glass | d02ddcf | 2020-09-10 20:21:14 -0600 | [diff] [blame] | 895 | help |
| 896 | Enable recording of boot time in SPL. To make this visible to U-Boot |
| 897 | proper, enable BOOTSTAGE_STASH as well. This will stash the timing |
| 898 | information when TPL finishes and load it when U-Boot proper starts |
| 899 | up. |
| 900 | |
| 901 | config BOOTSTAGE_REPORT |
| 902 | bool "Display a detailed boot timing report before booting the OS" |
| 903 | depends on BOOTSTAGE |
| 904 | help |
| 905 | Enable output of a boot time report just before the OS is booted. |
| 906 | This shows how long it took U-Boot to go through each stage of the |
| 907 | boot process. The report looks something like this: |
| 908 | |
| 909 | Timer summary in microseconds: |
| 910 | Mark Elapsed Stage |
| 911 | 0 0 reset |
| 912 | 3,575,678 3,575,678 board_init_f start |
| 913 | 3,575,695 17 arch_cpu_init A9 |
| 914 | 3,575,777 82 arch_cpu_init done |
| 915 | 3,659,598 83,821 board_init_r start |
| 916 | 3,910,375 250,777 main_loop |
| 917 | 29,916,167 26,005,792 bootm_start |
| 918 | 30,361,327 445,160 start_kernel |
| 919 | |
| 920 | config BOOTSTAGE_RECORD_COUNT |
| 921 | int "Number of boot stage records to store" |
Simon Glass | 051ddfb | 2021-02-03 06:00:49 -0700 | [diff] [blame] | 922 | depends on BOOTSTAGE |
Simon Glass | d02ddcf | 2020-09-10 20:21:14 -0600 | [diff] [blame] | 923 | default 30 |
| 924 | help |
| 925 | This is the size of the bootstage record list and is the maximum |
| 926 | number of bootstage records that can be recorded. |
| 927 | |
| 928 | config SPL_BOOTSTAGE_RECORD_COUNT |
| 929 | int "Number of boot stage records to store for SPL" |
Simon Glass | 051ddfb | 2021-02-03 06:00:49 -0700 | [diff] [blame] | 930 | depends on SPL_BOOTSTAGE |
Simon Glass | d02ddcf | 2020-09-10 20:21:14 -0600 | [diff] [blame] | 931 | default 5 |
| 932 | help |
| 933 | This is the size of the bootstage record list and is the maximum |
| 934 | number of bootstage records that can be recorded. |
| 935 | |
| 936 | config TPL_BOOTSTAGE_RECORD_COUNT |
| 937 | int "Number of boot stage records to store for TPL" |
Simon Glass | 051ddfb | 2021-02-03 06:00:49 -0700 | [diff] [blame] | 938 | depends on TPL_BOOTSTAGE |
Simon Glass | d02ddcf | 2020-09-10 20:21:14 -0600 | [diff] [blame] | 939 | default 5 |
| 940 | help |
| 941 | This is the size of the bootstage record list and is the maximum |
| 942 | number of bootstage records that can be recorded. |
| 943 | |
| 944 | config BOOTSTAGE_FDT |
| 945 | bool "Store boot timing information in the OS device tree" |
| 946 | depends on BOOTSTAGE |
| 947 | help |
| 948 | Stash the bootstage information in the FDT. A root 'bootstage' |
| 949 | node is created with each bootstage id as a child. Each child |
| 950 | has a 'name' property and either 'mark' containing the |
| 951 | mark time in microseconds, or 'accum' containing the |
| 952 | accumulated time for that bootstage id in microseconds. |
| 953 | For example: |
| 954 | |
| 955 | bootstage { |
| 956 | 154 { |
| 957 | name = "board_init_f"; |
| 958 | mark = <3575678>; |
| 959 | }; |
| 960 | 170 { |
| 961 | name = "lcd"; |
| 962 | accum = <33482>; |
| 963 | }; |
| 964 | }; |
| 965 | |
| 966 | Code in the Linux kernel can find this in /proc/devicetree. |
| 967 | |
| 968 | config BOOTSTAGE_STASH |
| 969 | bool "Stash the boot timing information in memory before booting OS" |
| 970 | depends on BOOTSTAGE |
| 971 | help |
| 972 | Some OSes do not support device tree. Bootstage can instead write |
| 973 | the boot timing information in a binary format at a given address. |
| 974 | This happens through a call to bootstage_stash(), typically in |
| 975 | the CPU's cleanup_before_linux() function. You can use the |
| 976 | 'bootstage stash' and 'bootstage unstash' commands to do this on |
| 977 | the command line. |
| 978 | |
| 979 | config BOOTSTAGE_STASH_ADDR |
| 980 | hex "Address to stash boot timing information" |
Tom Rini | f18679c | 2023-08-02 11:09:43 -0400 | [diff] [blame] | 981 | default 0x0 |
Simon Glass | d02ddcf | 2020-09-10 20:21:14 -0600 | [diff] [blame] | 982 | help |
| 983 | Provide an address which will not be overwritten by the OS when it |
| 984 | starts, so that it can read this information when ready. |
| 985 | |
| 986 | config BOOTSTAGE_STASH_SIZE |
| 987 | hex "Size of boot timing stash region" |
| 988 | default 0x1000 |
| 989 | help |
| 990 | This should be large enough to hold the bootstage stash. A value of |
| 991 | 4096 (4KiB) is normally plenty. |
| 992 | |
| 993 | config SHOW_BOOT_PROGRESS |
| 994 | bool "Show boot progress in a board-specific manner" |
| 995 | help |
| 996 | Defining this option allows to add some board-specific code (calling |
| 997 | a user-provided function show_boot_progress(int) that enables you to |
| 998 | show the system's boot progress on some display (for example, some |
| 999 | LEDs) on your board. At the moment, the following checkpoints are |
| 1000 | implemented: |
| 1001 | |
| 1002 | Legacy uImage format: |
| 1003 | |
| 1004 | Arg Where When |
| 1005 | 1 common/cmd_bootm.c before attempting to boot an image |
| 1006 | -1 common/cmd_bootm.c Image header has bad magic number |
| 1007 | 2 common/cmd_bootm.c Image header has correct magic number |
| 1008 | -2 common/cmd_bootm.c Image header has bad checksum |
| 1009 | 3 common/cmd_bootm.c Image header has correct checksum |
| 1010 | -3 common/cmd_bootm.c Image data has bad checksum |
| 1011 | 4 common/cmd_bootm.c Image data has correct checksum |
| 1012 | -4 common/cmd_bootm.c Image is for unsupported architecture |
| 1013 | 5 common/cmd_bootm.c Architecture check OK |
| 1014 | -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi) |
| 1015 | 6 common/cmd_bootm.c Image Type check OK |
| 1016 | -6 common/cmd_bootm.c gunzip uncompression error |
| 1017 | -7 common/cmd_bootm.c Unimplemented compression type |
| 1018 | 7 common/cmd_bootm.c Uncompression OK |
| 1019 | 8 common/cmd_bootm.c No uncompress/copy overwrite error |
| 1020 | -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX) |
| 1021 | |
| 1022 | 9 common/image.c Start initial ramdisk verification |
| 1023 | -10 common/image.c Ramdisk header has bad magic number |
| 1024 | -11 common/image.c Ramdisk header has bad checksum |
| 1025 | 10 common/image.c Ramdisk header is OK |
| 1026 | -12 common/image.c Ramdisk data has bad checksum |
| 1027 | 11 common/image.c Ramdisk data has correct checksum |
| 1028 | 12 common/image.c Ramdisk verification complete, start loading |
| 1029 | -13 common/image.c Wrong Image Type (not PPC Linux ramdisk) |
| 1030 | 13 common/image.c Start multifile image verification |
| 1031 | 14 common/image.c No initial ramdisk, no multifile, continue. |
| 1032 | |
| 1033 | 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS |
| 1034 | |
| 1035 | -30 arch/powerpc/lib/board.c Fatal error, hang the system |
| 1036 | -31 post/post.c POST test failed, detected by post_output_backlog() |
| 1037 | -32 post/post.c POST test failed, detected by post_run_single() |
| 1038 | |
| 1039 | 34 common/cmd_doc.c before loading a Image from a DOC device |
| 1040 | -35 common/cmd_doc.c Bad usage of "doc" command |
| 1041 | 35 common/cmd_doc.c correct usage of "doc" command |
| 1042 | -36 common/cmd_doc.c No boot device |
| 1043 | 36 common/cmd_doc.c correct boot device |
| 1044 | -37 common/cmd_doc.c Unknown Chip ID on boot device |
| 1045 | 37 common/cmd_doc.c correct chip ID found, device available |
| 1046 | -38 common/cmd_doc.c Read Error on boot device |
| 1047 | 38 common/cmd_doc.c reading Image header from DOC device OK |
| 1048 | -39 common/cmd_doc.c Image header has bad magic number |
| 1049 | 39 common/cmd_doc.c Image header has correct magic number |
| 1050 | -40 common/cmd_doc.c Error reading Image from DOC device |
| 1051 | 40 common/cmd_doc.c Image header has correct magic number |
| 1052 | 41 common/cmd_ide.c before loading a Image from a IDE device |
| 1053 | -42 common/cmd_ide.c Bad usage of "ide" command |
| 1054 | 42 common/cmd_ide.c correct usage of "ide" command |
| 1055 | -43 common/cmd_ide.c No boot device |
| 1056 | 43 common/cmd_ide.c boot device found |
| 1057 | -44 common/cmd_ide.c Device not available |
| 1058 | 44 common/cmd_ide.c Device available |
| 1059 | -45 common/cmd_ide.c wrong partition selected |
| 1060 | 45 common/cmd_ide.c partition selected |
| 1061 | -46 common/cmd_ide.c Unknown partition table |
| 1062 | 46 common/cmd_ide.c valid partition table found |
| 1063 | -47 common/cmd_ide.c Invalid partition type |
| 1064 | 47 common/cmd_ide.c correct partition type |
| 1065 | -48 common/cmd_ide.c Error reading Image Header on boot device |
| 1066 | 48 common/cmd_ide.c reading Image Header from IDE device OK |
| 1067 | -49 common/cmd_ide.c Image header has bad magic number |
| 1068 | 49 common/cmd_ide.c Image header has correct magic number |
| 1069 | -50 common/cmd_ide.c Image header has bad checksum |
| 1070 | 50 common/cmd_ide.c Image header has correct checksum |
| 1071 | -51 common/cmd_ide.c Error reading Image from IDE device |
| 1072 | 51 common/cmd_ide.c reading Image from IDE device OK |
| 1073 | 52 common/cmd_nand.c before loading a Image from a NAND device |
| 1074 | -53 common/cmd_nand.c Bad usage of "nand" command |
| 1075 | 53 common/cmd_nand.c correct usage of "nand" command |
| 1076 | -54 common/cmd_nand.c No boot device |
| 1077 | 54 common/cmd_nand.c boot device found |
| 1078 | -55 common/cmd_nand.c Unknown Chip ID on boot device |
| 1079 | 55 common/cmd_nand.c correct chip ID found, device available |
| 1080 | -56 common/cmd_nand.c Error reading Image Header on boot device |
| 1081 | 56 common/cmd_nand.c reading Image Header from NAND device OK |
| 1082 | -57 common/cmd_nand.c Image header has bad magic number |
| 1083 | 57 common/cmd_nand.c Image header has correct magic number |
| 1084 | -58 common/cmd_nand.c Error reading Image from NAND device |
| 1085 | 58 common/cmd_nand.c reading Image from NAND device OK |
| 1086 | |
| 1087 | -60 common/env_common.c Environment has a bad CRC, using default |
| 1088 | |
| 1089 | 64 net/eth.c starting with Ethernet configuration. |
| 1090 | -64 net/eth.c no Ethernet found. |
| 1091 | 65 net/eth.c Ethernet found. |
| 1092 | |
| 1093 | -80 common/cmd_net.c usage wrong |
| 1094 | 80 common/cmd_net.c before calling net_loop() |
| 1095 | -81 common/cmd_net.c some error in net_loop() occurred |
| 1096 | 81 common/cmd_net.c net_loop() back without error |
| 1097 | -82 common/cmd_net.c size == 0 (File with size 0 loaded) |
| 1098 | 82 common/cmd_net.c trying automatic boot |
| 1099 | 83 common/cmd_net.c running "source" command |
| 1100 | -83 common/cmd_net.c some error in automatic boot or "source" command |
| 1101 | 84 common/cmd_net.c end without errors |
| 1102 | |
| 1103 | FIT uImage format: |
| 1104 | |
| 1105 | Arg Where When |
| 1106 | 100 common/cmd_bootm.c Kernel FIT Image has correct format |
| 1107 | -100 common/cmd_bootm.c Kernel FIT Image has incorrect format |
| 1108 | 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration |
| 1109 | -101 common/cmd_bootm.c Can't get configuration for kernel subimage |
| 1110 | 102 common/cmd_bootm.c Kernel unit name specified |
| 1111 | -103 common/cmd_bootm.c Can't get kernel subimage node offset |
| 1112 | 103 common/cmd_bootm.c Found configuration node |
| 1113 | 104 common/cmd_bootm.c Got kernel subimage node offset |
| 1114 | -104 common/cmd_bootm.c Kernel subimage hash verification failed |
| 1115 | 105 common/cmd_bootm.c Kernel subimage hash verification OK |
| 1116 | -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture |
| 1117 | 106 common/cmd_bootm.c Architecture check OK |
| 1118 | -106 common/cmd_bootm.c Kernel subimage has wrong type |
| 1119 | 107 common/cmd_bootm.c Kernel subimage type OK |
| 1120 | -107 common/cmd_bootm.c Can't get kernel subimage data/size |
| 1121 | 108 common/cmd_bootm.c Got kernel subimage data/size |
| 1122 | -108 common/cmd_bootm.c Wrong image type (not legacy, FIT) |
| 1123 | -109 common/cmd_bootm.c Can't get kernel subimage type |
| 1124 | -110 common/cmd_bootm.c Can't get kernel subimage comp |
| 1125 | -111 common/cmd_bootm.c Can't get kernel subimage os |
| 1126 | -112 common/cmd_bootm.c Can't get kernel subimage load address |
| 1127 | -113 common/cmd_bootm.c Image uncompress/copy overwrite error |
| 1128 | |
| 1129 | 120 common/image.c Start initial ramdisk verification |
| 1130 | -120 common/image.c Ramdisk FIT image has incorrect format |
| 1131 | 121 common/image.c Ramdisk FIT image has correct format |
| 1132 | 122 common/image.c No ramdisk subimage unit name, using configuration |
| 1133 | -122 common/image.c Can't get configuration for ramdisk subimage |
| 1134 | 123 common/image.c Ramdisk unit name specified |
| 1135 | -124 common/image.c Can't get ramdisk subimage node offset |
| 1136 | 125 common/image.c Got ramdisk subimage node offset |
| 1137 | -125 common/image.c Ramdisk subimage hash verification failed |
| 1138 | 126 common/image.c Ramdisk subimage hash verification OK |
| 1139 | -126 common/image.c Ramdisk subimage for unsupported architecture |
| 1140 | 127 common/image.c Architecture check OK |
| 1141 | -127 common/image.c Can't get ramdisk subimage data/size |
| 1142 | 128 common/image.c Got ramdisk subimage data/size |
| 1143 | 129 common/image.c Can't get ramdisk load address |
| 1144 | -129 common/image.c Got ramdisk load address |
| 1145 | |
| 1146 | -130 common/cmd_doc.c Incorrect FIT image format |
| 1147 | 131 common/cmd_doc.c FIT image format OK |
| 1148 | |
| 1149 | -140 common/cmd_ide.c Incorrect FIT image format |
| 1150 | 141 common/cmd_ide.c FIT image format OK |
| 1151 | |
| 1152 | -150 common/cmd_nand.c Incorrect FIT image format |
| 1153 | 151 common/cmd_nand.c FIT image format OK |
| 1154 | |
Marek Vasut | 9815434 | 2021-10-23 03:06:03 +0200 | [diff] [blame] | 1155 | config SPL_SHOW_BOOT_PROGRESS |
Jan Kiszka | 5780edb | 2021-11-03 15:09:36 +0100 | [diff] [blame] | 1156 | bool "Show boot progress in a board-specific manner in SPL" |
Marek Vasut | 9815434 | 2021-10-23 03:06:03 +0200 | [diff] [blame] | 1157 | depends on SPL |
| 1158 | help |
| 1159 | Defining this option allows to add some board-specific code (calling |
| 1160 | a user-provided function show_boot_progress(int) that enables you to |
| 1161 | show the system's boot progress on some display (for example, some |
| 1162 | LEDs) on your board. For details see SHOW_BOOT_PROGRESS. |
| 1163 | |
Simon Glass | d02ddcf | 2020-09-10 20:21:14 -0600 | [diff] [blame] | 1164 | endmenu |
| 1165 | |
Simon Glass | eebed78 | 2020-09-10 20:21:15 -0600 | [diff] [blame] | 1166 | menu "Boot media" |
| 1167 | |
| 1168 | config NOR_BOOT |
| 1169 | bool "Support for booting from NOR flash" |
| 1170 | depends on NOR |
| 1171 | help |
| 1172 | Enabling this will make a U-Boot binary that is capable of being |
| 1173 | booted via NOR. In this case we will enable certain pinmux early |
| 1174 | as the ROM only partially sets up pinmux. We also default to using |
| 1175 | NOR for environment. |
| 1176 | |
| 1177 | config NAND_BOOT |
| 1178 | bool "Support for booting from NAND flash" |
Simon Glass | eebed78 | 2020-09-10 20:21:15 -0600 | [diff] [blame] | 1179 | imply MTD_RAW_NAND |
| 1180 | help |
| 1181 | Enabling this will make a U-Boot binary that is capable of being |
| 1182 | booted via NAND flash. This is not a must, some SoCs need this, |
| 1183 | some not. |
| 1184 | |
| 1185 | config ONENAND_BOOT |
| 1186 | bool "Support for booting from ONENAND" |
Simon Glass | eebed78 | 2020-09-10 20:21:15 -0600 | [diff] [blame] | 1187 | imply MTD_RAW_NAND |
| 1188 | help |
| 1189 | Enabling this will make a U-Boot binary that is capable of being |
| 1190 | booted via ONENAND. This is not a must, some SoCs need this, |
| 1191 | some not. |
| 1192 | |
| 1193 | config QSPI_BOOT |
| 1194 | bool "Support for booting from QSPI flash" |
Simon Glass | eebed78 | 2020-09-10 20:21:15 -0600 | [diff] [blame] | 1195 | help |
| 1196 | Enabling this will make a U-Boot binary that is capable of being |
| 1197 | booted via QSPI flash. This is not a must, some SoCs need this, |
| 1198 | some not. |
| 1199 | |
| 1200 | config SATA_BOOT |
| 1201 | bool "Support for booting from SATA" |
Simon Glass | eebed78 | 2020-09-10 20:21:15 -0600 | [diff] [blame] | 1202 | help |
| 1203 | Enabling this will make a U-Boot binary that is capable of being |
| 1204 | booted via SATA. This is not a must, some SoCs need this, |
| 1205 | some not. |
| 1206 | |
| 1207 | config SD_BOOT |
| 1208 | bool "Support for booting from SD/EMMC" |
Simon Glass | eebed78 | 2020-09-10 20:21:15 -0600 | [diff] [blame] | 1209 | help |
| 1210 | Enabling this will make a U-Boot binary that is capable of being |
| 1211 | booted via SD/EMMC. This is not a must, some SoCs need this, |
| 1212 | some not. |
| 1213 | |
Tom Rini | a43bf4e | 2021-12-11 14:55:50 -0500 | [diff] [blame] | 1214 | config SD_BOOT_QSPI |
| 1215 | bool "Support for booting from SD/EMMC and enable QSPI" |
| 1216 | help |
| 1217 | Enabling this will make a U-Boot binary that is capable of being |
| 1218 | booted via SD/EMMC while enabling QSPI on the platform as well. This |
| 1219 | is not a must, some SoCs need this, some not. |
| 1220 | |
Simon Glass | eebed78 | 2020-09-10 20:21:15 -0600 | [diff] [blame] | 1221 | config SPI_BOOT |
| 1222 | bool "Support for booting from SPI flash" |
Simon Glass | eebed78 | 2020-09-10 20:21:15 -0600 | [diff] [blame] | 1223 | help |
| 1224 | Enabling this will make a U-Boot binary that is capable of being |
| 1225 | booted via SPI flash. This is not a must, some SoCs need this, |
| 1226 | some not. |
| 1227 | |
| 1228 | endmenu |
| 1229 | |
Simon Glass | e9d54d7 | 2020-09-10 20:21:16 -0600 | [diff] [blame] | 1230 | menu "Autoboot options" |
| 1231 | |
| 1232 | config AUTOBOOT |
| 1233 | bool "Autoboot" |
| 1234 | default y |
| 1235 | help |
| 1236 | This enables the autoboot. See doc/README.autoboot for detail. |
| 1237 | |
Simon Glass | 1b6cbaa | 2020-09-10 20:21:17 -0600 | [diff] [blame] | 1238 | config BOOTDELAY |
| 1239 | int "delay in seconds before automatically booting" |
| 1240 | default 2 |
| 1241 | depends on AUTOBOOT |
| 1242 | help |
| 1243 | Delay before automatically running bootcmd; |
| 1244 | set to 0 to autoboot with no delay, but you can stop it by key input. |
| 1245 | set to -1 to disable autoboot. |
| 1246 | set to -2 to autoboot with no delay and not check for abort |
| 1247 | |
| 1248 | If this value is >= 0 then it is also used for the default delay |
| 1249 | before starting the default entry in bootmenu. If it is < 0 then |
| 1250 | a default value of 10s is used. |
| 1251 | |
| 1252 | See doc/README.autoboot for details. |
| 1253 | |
Simon Glass | e9d54d7 | 2020-09-10 20:21:16 -0600 | [diff] [blame] | 1254 | config AUTOBOOT_KEYED |
| 1255 | bool "Stop autobooting via specific input key / string" |
Simon Glass | e9d54d7 | 2020-09-10 20:21:16 -0600 | [diff] [blame] | 1256 | help |
| 1257 | This option enables stopping (aborting) of the automatic |
| 1258 | boot feature only by issuing a specific input key or |
| 1259 | string. If not enabled, any input key will abort the |
| 1260 | U-Boot automatic booting process and bring the device |
| 1261 | to the U-Boot prompt for user input. |
| 1262 | |
Steffen Jaeckel | dfc9732 | 2021-07-08 15:57:38 +0200 | [diff] [blame] | 1263 | config AUTOBOOT_FLUSH_STDIN |
| 1264 | bool "Enable flushing stdin before starting to read the password" |
| 1265 | depends on AUTOBOOT_KEYED && !SANDBOX |
| 1266 | help |
| 1267 | When this option is enabled stdin buffer will be flushed before |
| 1268 | starting to read the password. |
| 1269 | This can't be enabled for the sandbox as flushing stdin would |
| 1270 | break the autoboot unit tests. |
| 1271 | |
Simon Glass | e9d54d7 | 2020-09-10 20:21:16 -0600 | [diff] [blame] | 1272 | config AUTOBOOT_PROMPT |
| 1273 | string "Autoboot stop prompt" |
| 1274 | depends on AUTOBOOT_KEYED |
| 1275 | default "Autoboot in %d seconds\\n" |
| 1276 | help |
| 1277 | This string is displayed before the boot delay selected by |
| 1278 | CONFIG_BOOTDELAY starts. If it is not defined there is no |
| 1279 | output indicating that autoboot is in progress. |
| 1280 | |
| 1281 | Note that this define is used as the (only) argument to a |
| 1282 | printf() call, so it may contain '%' format specifications, |
| 1283 | provided that it also includes, sepearated by commas exactly |
| 1284 | like in a printf statement, the required arguments. It is |
| 1285 | the responsibility of the user to select only such arguments |
| 1286 | that are valid in the given context. |
| 1287 | |
| 1288 | config AUTOBOOT_ENCRYPTION |
| 1289 | bool "Enable encryption in autoboot stopping" |
| 1290 | depends on AUTOBOOT_KEYED |
| 1291 | help |
| 1292 | This option allows a string to be entered into U-Boot to stop the |
Steffen Jaeckel | 6aa6bfb | 2021-07-08 15:57:35 +0200 | [diff] [blame] | 1293 | autoboot. |
| 1294 | The behavior depends whether CONFIG_CRYPT_PW from lib is enabled |
| 1295 | or not. |
| 1296 | In case CONFIG_CRYPT_PW is enabled, the string will be forwarded |
| 1297 | to the crypt-based functionality and be compared against the |
| 1298 | string in the environment variable 'bootstopkeycrypt'. |
| 1299 | In case CONFIG_CRYPT_PW is disabled the string itself is hashed |
| 1300 | and compared against the hash in the environment variable |
| 1301 | 'bootstopkeysha256'. |
| 1302 | If it matches in either case then boot stops and |
| 1303 | a command-line prompt is presented. |
Simon Glass | e9d54d7 | 2020-09-10 20:21:16 -0600 | [diff] [blame] | 1304 | This provides a way to ship a secure production device which can also |
| 1305 | be accessed at the U-Boot command line. |
| 1306 | |
Steffen Jaeckel | 28be70d | 2021-07-08 15:57:39 +0200 | [diff] [blame] | 1307 | config AUTOBOOT_SHA256_FALLBACK |
| 1308 | bool "Allow fallback from crypt-hashed password to sha256" |
| 1309 | depends on AUTOBOOT_ENCRYPTION && CRYPT_PW |
| 1310 | help |
| 1311 | This option adds support to fall back from crypt-hashed |
| 1312 | passwords to checking a SHA256 hashed password in case the |
| 1313 | 'bootstopusesha256' environment variable is set to 'true'. |
| 1314 | |
Simon Glass | e9d54d7 | 2020-09-10 20:21:16 -0600 | [diff] [blame] | 1315 | config AUTOBOOT_DELAY_STR |
| 1316 | string "Delay autobooting via specific input key / string" |
| 1317 | depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION |
| 1318 | help |
| 1319 | This option delays the automatic boot feature by issuing |
| 1320 | a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR |
| 1321 | or the environment variable "bootdelaykey" is specified |
| 1322 | and this string is received from console input before |
| 1323 | autoboot starts booting, U-Boot gives a command prompt. The |
| 1324 | U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is |
| 1325 | used, otherwise it never times out. |
| 1326 | |
| 1327 | config AUTOBOOT_STOP_STR |
| 1328 | string "Stop autobooting via specific input key / string" |
| 1329 | depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION |
| 1330 | help |
| 1331 | This option enables stopping (aborting) of the automatic |
| 1332 | boot feature only by issuing a specific input key or |
| 1333 | string. If CONFIG_AUTOBOOT_STOP_STR or the environment |
| 1334 | variable "bootstopkey" is specified and this string is |
| 1335 | received from console input before autoboot starts booting, |
| 1336 | U-Boot gives a command prompt. The U-Boot prompt never |
| 1337 | times out, even if CONFIG_BOOT_RETRY_TIME is used. |
| 1338 | |
| 1339 | config AUTOBOOT_KEYED_CTRLC |
| 1340 | bool "Enable Ctrl-C autoboot interruption" |
| 1341 | depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION |
Simon Glass | e9d54d7 | 2020-09-10 20:21:16 -0600 | [diff] [blame] | 1342 | help |
| 1343 | This option allows for the boot sequence to be interrupted |
| 1344 | by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey". |
| 1345 | Setting this variable provides an escape sequence from the |
| 1346 | limited "password" strings. |
| 1347 | |
Steffen Jaeckel | 792a13f | 2021-07-08 15:57:37 +0200 | [diff] [blame] | 1348 | config AUTOBOOT_NEVER_TIMEOUT |
| 1349 | bool "Make the password entry never time-out" |
| 1350 | depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION && CRYPT_PW |
| 1351 | help |
| 1352 | This option removes the timeout from the password entry |
| 1353 | when the user first presses the <Enter> key before entering |
| 1354 | any other character. |
| 1355 | |
Steffen Jaeckel | 6aa6bfb | 2021-07-08 15:57:35 +0200 | [diff] [blame] | 1356 | config AUTOBOOT_STOP_STR_ENABLE |
| 1357 | bool "Enable fixed string to stop autobooting" |
| 1358 | depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION |
| 1359 | help |
| 1360 | This option enables the feature to add a fixed stop |
| 1361 | string that is defined at compile time. |
| 1362 | In every case it will be tried to load the stop |
| 1363 | string from the environment. |
| 1364 | In case this is enabled and there is no stop string |
| 1365 | in the environment, this will be used as default value. |
| 1366 | |
| 1367 | config AUTOBOOT_STOP_STR_CRYPT |
| 1368 | string "Stop autobooting via crypt-hashed password" |
| 1369 | depends on AUTOBOOT_STOP_STR_ENABLE && CRYPT_PW |
| 1370 | help |
| 1371 | This option adds the feature to only stop the autobooting, |
| 1372 | and therefore boot into the U-Boot prompt, when the input |
| 1373 | string / password matches a values that is hashed via |
| 1374 | one of the supported crypt-style password hashing options |
| 1375 | and saved in the environment variable "bootstopkeycrypt". |
| 1376 | |
Simon Glass | e9d54d7 | 2020-09-10 20:21:16 -0600 | [diff] [blame] | 1377 | config AUTOBOOT_STOP_STR_SHA256 |
Steffen Jaeckel | e1788f9 | 2021-07-08 15:57:40 +0200 | [diff] [blame] | 1378 | string "Stop autobooting via SHA256 hashed password" |
Steffen Jaeckel | 6aa6bfb | 2021-07-08 15:57:35 +0200 | [diff] [blame] | 1379 | depends on AUTOBOOT_STOP_STR_ENABLE |
Simon Glass | e9d54d7 | 2020-09-10 20:21:16 -0600 | [diff] [blame] | 1380 | help |
| 1381 | This option adds the feature to only stop the autobooting, |
| 1382 | and therefore boot into the U-Boot prompt, when the input |
| 1383 | string / password matches a values that is encypted via |
Joel Peshkin | 8b7bf53 | 2020-11-21 17:18:59 -0800 | [diff] [blame] | 1384 | a SHA256 hash and saved in the environment variable |
| 1385 | "bootstopkeysha256". If the value in that variable |
| 1386 | includes a ":", the portion prior to the ":" will be treated |
| 1387 | as a salt value. |
Simon Glass | e9d54d7 | 2020-09-10 20:21:16 -0600 | [diff] [blame] | 1388 | |
| 1389 | config AUTOBOOT_USE_MENUKEY |
| 1390 | bool "Allow a specify key to run a menu from the environment" |
| 1391 | depends on !AUTOBOOT_KEYED |
| 1392 | help |
| 1393 | If a specific key is pressed to stop autoboot, then the commands in |
| 1394 | the environment variable 'menucmd' are executed before boot starts. |
| 1395 | |
| 1396 | config AUTOBOOT_MENUKEY |
| 1397 | int "ASCII value of boot key to show a menu" |
| 1398 | default 0 |
| 1399 | depends on AUTOBOOT_USE_MENUKEY |
| 1400 | help |
| 1401 | If this key is pressed to stop autoboot, then the commands in the |
| 1402 | environment variable 'menucmd' will be executed before boot starts. |
| 1403 | For example, 33 means "!" in ASCII, so pressing ! at boot would take |
| 1404 | this action. |
| 1405 | |
| 1406 | config AUTOBOOT_MENU_SHOW |
| 1407 | bool "Show a menu on boot" |
| 1408 | depends on CMD_BOOTMENU |
| 1409 | help |
| 1410 | This enables the boot menu, controlled by environment variables |
| 1411 | defined by the board. The menu starts after running the 'preboot' |
| 1412 | environmnent variable (if enabled) and before handling the boot delay. |
Peter Robinson | 16e0b8f | 2023-08-18 15:54:10 +0100 | [diff] [blame] | 1413 | See doc/usage/cmd/bootmenu.rst for more details. |
Simon Glass | e9d54d7 | 2020-09-10 20:21:16 -0600 | [diff] [blame] | 1414 | |
Masahisa Kojima | 97cbcc4 | 2022-05-26 19:09:38 +0900 | [diff] [blame] | 1415 | config BOOTMENU_DISABLE_UBOOT_CONSOLE |
| 1416 | bool "Disallow bootmenu to enter the U-Boot console" |
| 1417 | depends on AUTOBOOT_MENU_SHOW |
| 1418 | help |
| 1419 | If this option is enabled, user can not enter the U-Boot console from |
| 1420 | bootmenu. It increases the system security. |
| 1421 | |
Tom Rini | a45a3ef | 2022-03-11 09:12:04 -0500 | [diff] [blame] | 1422 | config BOOT_RETRY |
| 1423 | bool "Boot retry feature" |
| 1424 | help |
| 1425 | Allow for having the U-Boot command prompt time out and attempt |
| 1426 | to boot again. If the environment variable "bootretry" is found then |
| 1427 | its value is used, otherwise the retry timeout is |
| 1428 | CONFIG_BOOT_RETRY_TIME. CONFIG_BOOT_RETRY_MIN is optional and |
| 1429 | defaults to CONFIG_BOOT_RETRY_TIME. All times are in seconds. |
| 1430 | |
| 1431 | config BOOT_RETRY_TIME |
| 1432 | int "Timeout in seconds before attempting to boot again" |
| 1433 | depends on BOOT_RETRY |
| 1434 | help |
| 1435 | Time in seconds before the U-Boot prompt will timeout and boot will |
| 1436 | be attempted again. |
| 1437 | |
| 1438 | config BOOT_RETRY_MIN |
| 1439 | int "Minimum timeout in seconds for 'bootretry'" |
| 1440 | depends on BOOT_RETRY |
| 1441 | default BOOT_RETRY_TIME |
| 1442 | help |
| 1443 | The minimum time in seconds that "bootretry" can be set to. |
| 1444 | |
| 1445 | config RESET_TO_RETRY |
| 1446 | bool "Reset the board to retry autoboot" |
| 1447 | depends on BOOT_RETRY |
| 1448 | help |
| 1449 | After the countdown timed out, the board will be reset to restart |
| 1450 | again. |
| 1451 | |
Simon Glass | e9d54d7 | 2020-09-10 20:21:16 -0600 | [diff] [blame] | 1452 | endmenu |
| 1453 | |
Philippe Reynes | d28484e | 2022-03-28 22:56:59 +0200 | [diff] [blame] | 1454 | menu "Image support" |
| 1455 | |
| 1456 | config IMAGE_PRE_LOAD |
| 1457 | bool "Image pre-load support" |
| 1458 | help |
| 1459 | Enable an image pre-load stage in the SPL. |
| 1460 | This pre-load stage allows to do some manipulation |
| 1461 | or check (for example signature check) on an image |
| 1462 | before launching it. |
| 1463 | |
| 1464 | config SPL_IMAGE_PRE_LOAD |
| 1465 | bool "Image pre-load support within SPL" |
| 1466 | depends on SPL && IMAGE_PRE_LOAD |
| 1467 | help |
| 1468 | Enable an image pre-load stage in the SPL. |
| 1469 | This pre-load stage allows to do some manipulation |
| 1470 | or check (for example signature check) on an image |
| 1471 | before launching it. |
| 1472 | |
| 1473 | config IMAGE_PRE_LOAD_SIG |
| 1474 | bool "Image pre-load signature support" |
| 1475 | depends on IMAGE_PRE_LOAD |
| 1476 | select FIT_SIGNATURE |
| 1477 | select RSA |
| 1478 | select RSA_VERIFY_WITH_PKEY |
| 1479 | help |
| 1480 | Enable signature check support in the pre-load stage. |
| 1481 | For this feature a very simple header is added before |
| 1482 | the image with few fields: |
| 1483 | - a magic |
| 1484 | - the image size |
| 1485 | - the signature |
| 1486 | All other information (header size, type of signature, |
| 1487 | ...) are provided in the node /image/pre-load/sig of |
| 1488 | u-boot. |
| 1489 | |
| 1490 | config SPL_IMAGE_PRE_LOAD_SIG |
| 1491 | bool "Image pre-load signature support witin SPL" |
| 1492 | depends on SPL_IMAGE_PRE_LOAD && IMAGE_PRE_LOAD_SIG |
| 1493 | select SPL_FIT_SIGNATURE |
| 1494 | select SPL_RSA |
| 1495 | select SPL_RSA_VERIFY_WITH_PKEY |
| 1496 | help |
| 1497 | Enable signature check support in the pre-load stage in the SPL. |
| 1498 | For this feature a very simple header is added before |
| 1499 | the image with few fields: |
| 1500 | - a magic |
| 1501 | - the image size |
| 1502 | - the signature |
| 1503 | All other information (header size, type of signature, |
| 1504 | ...) are provided in the node /image/pre-load/sig of |
| 1505 | u-boot. |
| 1506 | |
| 1507 | endmenu |
| 1508 | |
Simon Glass | 2736719 | 2023-09-14 10:55:46 -0600 | [diff] [blame] | 1509 | if OF_LIBFDT |
| 1510 | |
| 1511 | menu "Devicetree fixup" |
| 1512 | |
Simon Glass | 48e6d3d | 2023-09-14 10:55:47 -0600 | [diff] [blame] | 1513 | config OF_BOARD_SETUP |
| 1514 | bool "Set up board-specific details in device tree before boot" |
| 1515 | help |
| 1516 | This causes U-Boot to call ft_board_setup() before booting into |
| 1517 | the Operating System. This function can set up various |
| 1518 | board-specific information in the device tree for use by the OS. |
| 1519 | The device tree is then passed to the OS. |
| 1520 | |
| 1521 | config OF_SYSTEM_SETUP |
| 1522 | bool "Set up system-specific details in device tree before boot" |
| 1523 | help |
| 1524 | This causes U-Boot to call ft_system_setup() before booting into |
| 1525 | the Operating System. This function can set up various |
| 1526 | system-specific information in the device tree for use by the OS. |
| 1527 | The device tree is then passed to the OS. |
| 1528 | |
| 1529 | config OF_STDOUT_VIA_ALIAS |
| 1530 | bool "Update the device-tree stdout alias from U-Boot" |
| 1531 | help |
| 1532 | This uses U-Boot's serial alias from the aliases node to update |
| 1533 | the device tree passed to the OS. The "linux,stdout-path" property |
| 1534 | in the chosen node is set to point to the correct serial node. |
| 1535 | This option currently references CONFIG_CONS_INDEX, which is |
| 1536 | incorrect when used with device tree as this option does not |
| 1537 | exist / should not be used. |
| 1538 | |
Simon Glass | 2736719 | 2023-09-14 10:55:46 -0600 | [diff] [blame] | 1539 | config FDT_SIMPLEFB |
| 1540 | bool "FDT tools for simplefb support" |
| 1541 | help |
| 1542 | Enable the fdt tools to manage the simple fb nodes in device tree. |
| 1543 | These functions can be used by board to indicate to the OS |
| 1544 | the presence of the simple frame buffer with associated reserved |
| 1545 | memory |
| 1546 | |
| 1547 | endmenu |
| 1548 | |
| 1549 | endif # OF_LIBFDT |
| 1550 | |
Simon Glass | 5e95864 | 2020-09-10 20:21:18 -0600 | [diff] [blame] | 1551 | config USE_BOOTARGS |
| 1552 | bool "Enable boot arguments" |
| 1553 | help |
| 1554 | Provide boot arguments to bootm command. Boot arguments are specified |
| 1555 | in CONFIG_BOOTARGS option. Enable this option to be able to specify |
| 1556 | CONFIG_BOOTARGS string. If this option is disabled, CONFIG_BOOTARGS |
| 1557 | will be undefined and won't take any space in U-Boot image. |
| 1558 | |
| 1559 | config BOOTARGS |
| 1560 | string "Boot arguments" |
| 1561 | depends on USE_BOOTARGS && !USE_DEFAULT_ENV_FILE |
| 1562 | help |
| 1563 | This can be used to pass arguments to the bootm command. The value of |
| 1564 | CONFIG_BOOTARGS goes into the environment value "bootargs". Note that |
| 1565 | this value will also override the "chosen" node in FDT blob. |
| 1566 | |
Simon Glass | 529e208 | 2020-11-05 10:33:48 -0700 | [diff] [blame] | 1567 | config BOOTARGS_SUBST |
| 1568 | bool "Support substituting strings in boot arguments" |
| 1569 | help |
| 1570 | This allows substituting string values in the boot arguments. These |
| 1571 | are applied after the commandline has been built. |
| 1572 | |
| 1573 | One use for this is to insert the root-disk UUID into the command |
| 1574 | line where bootargs contains "root=${uuid}" |
| 1575 | |
| 1576 | setenv bootargs "console= root=${uuid}" |
| 1577 | # Set the 'uuid' environment variable |
| 1578 | part uuid mmc 2:2 uuid |
| 1579 | |
| 1580 | # Command-line substitution will put the real uuid into the |
| 1581 | # kernel command line |
| 1582 | bootm |
| 1583 | |
Simon Glass | 5e95864 | 2020-09-10 20:21:18 -0600 | [diff] [blame] | 1584 | config USE_BOOTCOMMAND |
| 1585 | bool "Enable a default value for bootcmd" |
| 1586 | help |
| 1587 | Provide a default value for the bootcmd entry in the environment. If |
| 1588 | autoboot is enabled this is what will be run automatically. Enable |
| 1589 | this option to be able to specify CONFIG_BOOTCOMMAND as a string. If |
| 1590 | this option is disabled, CONFIG_BOOTCOMMAND will be undefined and |
| 1591 | won't take any space in U-Boot image. |
| 1592 | |
| 1593 | config BOOTCOMMAND |
| 1594 | string "bootcmd value" |
| 1595 | depends on USE_BOOTCOMMAND && !USE_DEFAULT_ENV_FILE |
Simon Glass | 2d5a8e1 | 2023-05-06 08:27:09 -0600 | [diff] [blame] | 1596 | default "bootflow scan -lb" if BOOTSTD_DEFAULTS && CMD_BOOTFLOW_FULL |
| 1597 | default "bootflow scan" if BOOTSTD_DEFAULTS && !CMD_BOOTFLOW_FULL |
Simon Glass | be661cb | 2022-04-24 23:31:27 -0600 | [diff] [blame] | 1598 | default "run distro_bootcmd" if !BOOTSTD_BOOTCOMMAND && DISTRO_DEFAULTS |
Simon Glass | 5e95864 | 2020-09-10 20:21:18 -0600 | [diff] [blame] | 1599 | help |
| 1600 | This is the string of commands that will be used as bootcmd and if |
| 1601 | AUTOBOOT is set, automatically run. |
| 1602 | |
| 1603 | config USE_PREBOOT |
| 1604 | bool "Enable preboot" |
| 1605 | help |
| 1606 | When this option is enabled, the existence of the environment |
| 1607 | variable "preboot" will be checked immediately before starting the |
| 1608 | CONFIG_BOOTDELAY countdown and/or running the auto-boot command resp. |
| 1609 | entering interactive mode. |
| 1610 | |
| 1611 | This feature is especially useful when "preboot" is automatically |
| 1612 | generated or modified. For example, the boot code can modify the |
| 1613 | "preboot" when a user holds down a certain combination of keys. |
| 1614 | |
| 1615 | config PREBOOT |
| 1616 | string "preboot default value" |
| 1617 | depends on USE_PREBOOT && !USE_DEFAULT_ENV_FILE |
Patrick Delaunay | bb15d40 | 2020-10-12 09:47:50 +0200 | [diff] [blame] | 1618 | default "usb start" if USB_KEYBOARD |
Simon Glass | 5e95864 | 2020-09-10 20:21:18 -0600 | [diff] [blame] | 1619 | default "" |
| 1620 | help |
| 1621 | This is the default of "preboot" environment variable. |
| 1622 | |
Pali Rohár | 39c43c3 | 2022-07-10 13:42:55 +0200 | [diff] [blame] | 1623 | config PREBOOT_DEFINED |
| 1624 | bool |
| 1625 | default y if PREBOOT != "" |
| 1626 | |
Simon Glass | c10ddfd | 2020-09-10 20:21:20 -0600 | [diff] [blame] | 1627 | config DEFAULT_FDT_FILE |
| 1628 | string "Default fdt file" |
| 1629 | help |
| 1630 | This option is used to set the default fdt file to boot OS. |
| 1631 | |
Dzmitry Sankouski | a346306 | 2022-02-22 21:49:52 +0300 | [diff] [blame] | 1632 | config SAVE_PREV_BL_FDT_ADDR |
| 1633 | depends on ARM |
| 1634 | bool "Saves fdt address, passed by the previous bootloader, to env var" |
| 1635 | help |
| 1636 | When u-boot is used as a chain-loaded bootloader (replacing OS kernel), |
| 1637 | enable this option to save fdt address, passed by the |
| 1638 | previous bootloader for future use. |
| 1639 | Address is saved to `prevbl_fdt_addr` environment variable. |
| 1640 | |
| 1641 | If no fdt was provided by previous bootloader, no env variables |
| 1642 | will be created. |
| 1643 | |
| 1644 | config SAVE_PREV_BL_INITRAMFS_START_ADDR |
| 1645 | depends on ARM |
| 1646 | bool "Saves initramfs address, passed by the previous bootloader, to env var" |
| 1647 | help |
| 1648 | When u-boot is used as a chain-loaded bootloader(replacing OS kernel), |
| 1649 | enable this option to save initramfs address, passed by the |
| 1650 | previous bootloader for future use. |
| 1651 | Address is saved to `prevbl_initrd_start_addr` environment variable. |
| 1652 | |
| 1653 | If no initramfs was provided by previous bootloader, no env variables |
| 1654 | will be created. |
| 1655 | |
Simon Glass | c892511 | 2023-06-01 10:23:02 -0600 | [diff] [blame] | 1656 | menu "Configuration editor" |
| 1657 | |
| 1658 | config CEDIT |
| 1659 | bool "Configuration editor" |
| 1660 | depends on BOOTSTD |
| 1661 | help |
| 1662 | Provides a way to deal with board configuration and present it to |
| 1663 | the user for adjustment. |
| 1664 | |
| 1665 | This is intended to provide both graphical and text-based user |
| 1666 | interfaces, but only graphical is support at present. |
| 1667 | |
| 1668 | endmenu # Configuration editor |
| 1669 | |
Simon Glass | b45b163 | 2020-09-10 20:21:13 -0600 | [diff] [blame] | 1670 | endmenu # Booting |