Kconfig 58 KB

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