Kconfig.boot 38 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192939495969798991001011021031041051061071081091101111121131141151161171181191201211221231241251261271281291301311321331341351361371381391401411421431441451461471481491501511521531541551561571581591601611621631641651661671681691701711721731741751761771781791801811821831841851861871881891901911921931941951961971981992002012022032042052062072082092102112122132142152162172182192202212222232242252262272282292302312322332342352362372382392402412422432442452462472482492502512522532542552562572582592602612622632642652662672682692702712722732742752762772782792802812822832842852862872882892902912922932942952962972982993003013023033043053063073083093103113123133143153163173183193203213223233243253263273283293303313323333343353363373383393403413423433443453463473483493503513523533543553563573583593603613623633643653663673683693703713723733743753763773783793803813823833843853863873883893903913923933943953963973983994004014024034044054064074084094104114124134144154164174184194204214224234244254264274284294304314324334344354364374384394404414424434444454464474484494504514524534544554564574584594604614624634644654664674684694704714724734744754764774784794804814824834844854864874884894904914924934944954964974984995005015025035045055065075085095105115125135145155165175185195205215225235245255265275285295305315325335345355365375385395405415425435445455465475485495505515525535545555565575585595605615625635645655665675685695705715725735745755765775785795805815825835845855865875885895905915925935945955965975985996006016026036046056066076086096106116126136146156166176186196206216226236246256266276286296306316326336346356366376386396406416426436446456466476486496506516526536546556566576586596606616626636646656666676686696706716726736746756766776786796806816826836846856866876886896906916926936946956966976986997007017027037047057067077087097107117127137147157167177187197207217227237247257267277287297307317327337347357367377387397407417427437447457467477487497507517527537547557567577587597607617627637647657667677687697707717727737747757767777787797807817827837847857867877887897907917927937947957967977987998008018028038048058068078088098108118128138148158168178188198208218228238248258268278288298308318328338348358368378388398408418428438448458468478488498508518528538548558568578588598608618628638648658668678688698708718728738748758768778788798808818828838848858868878888898908918928938948958968978988999009019029039049059069079089099109119129139149159169179189199209219229239249259269279289299309319329339349359369379389399409419429439449459469479489499509519529539549559569579589599609619629639649659669679689699709719729739749759769779789799809819829839849859869879889899909919929939949959969979989991000100110021003100410051006100710081009101010111012101310141015101610171018101910201021102210231024
  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 MD5
  12. select SHA1
  13. help
  14. This option allows you to boot the new uImage structure,
  15. Flattened Image Tree. FIT is formally a FDT, which can include
  16. images of various types (kernel, FDT blob, ramdisk, etc.)
  17. in a single blob. To boot this new uImage structure,
  18. pass the address of the blob to the "bootm" command.
  19. FIT is very flexible, supporting compression, multiple images,
  20. multiple configurations, verification through hashing and also
  21. verified boot (secure boot using RSA).
  22. if FIT
  23. config FIT_EXTERNAL_OFFSET
  24. hex "FIT external data offset"
  25. default 0x0
  26. help
  27. This specifies a data offset in fit image.
  28. The offset is from data payload offset to the beginning of
  29. fit image header. When specifies a offset, specific data
  30. could be put in the hole between data payload and fit image
  31. header, such as CSF data on i.MX platform.
  32. config FIT_SHA256
  33. bool "Support SHA256 checksum of FIT image contents"
  34. default y
  35. select SHA256
  36. help
  37. Enable this to support SHA256 checksum of FIT image contents. A
  38. SHA256 checksum is a 256-bit (32-byte) hash value used to check that
  39. the image contents have not been corrupted.
  40. config FIT_SHA384
  41. bool "Support SHA384 checksum of FIT image contents"
  42. default n
  43. select SHA384
  44. help
  45. Enable this to support SHA384 checksum of FIT image contents. A
  46. SHA384 checksum is a 384-bit (48-byte) hash value used to check that
  47. the image contents have not been corrupted. Use this for the highest
  48. security.
  49. config FIT_SHA512
  50. bool "Support SHA512 checksum of FIT image contents"
  51. default n
  52. select SHA512
  53. help
  54. Enable this to support SHA512 checksum of FIT image contents. A
  55. SHA512 checksum is a 512-bit (64-byte) hash value used to check that
  56. the image contents have not been corrupted.
  57. config FIT_FULL_CHECK
  58. bool "Do a full check of the FIT before using it"
  59. default y
  60. help
  61. Enable this do a full check of the FIT to make sure it is valid. This
  62. helps to protect against carefully crafted FITs which take advantage
  63. of bugs or omissions in the code. This includes a bad structure,
  64. multiple root nodes and the like.
  65. config FIT_SIGNATURE
  66. bool "Enable signature verification of FIT uImages"
  67. depends on DM
  68. select HASH
  69. select RSA
  70. select RSA_VERIFY
  71. select IMAGE_SIGN_INFO
  72. select FIT_FULL_CHECK
  73. help
  74. This option enables signature verification of FIT uImages,
  75. using a hash signed and verified using RSA. If
  76. CONFIG_SHA_PROG_HW_ACCEL is defined, i.e support for progressive
  77. hashing is available using hardware, then the RSA library will use
  78. it. See doc/uImage.FIT/signature.txt for more details.
  79. WARNING: When relying on signed FIT images with a required signature
  80. check the legacy image format is disabled by default, so that
  81. unsigned images cannot be loaded. If a board needs the legacy image
  82. format support in this case, enable it using
  83. CONFIG_LEGACY_IMAGE_FORMAT.
  84. config FIT_SIGNATURE_MAX_SIZE
  85. hex "Max size of signed FIT structures"
  86. depends on FIT_SIGNATURE
  87. default 0x10000000
  88. help
  89. This option sets a max size in bytes for verified FIT uImages.
  90. A sane value of 256MB protects corrupted DTB structures from overlapping
  91. device memory. Assure this size does not extend past expected storage
  92. space.
  93. config FIT_RSASSA_PSS
  94. bool "Support rsassa-pss signature scheme of FIT image contents"
  95. depends on FIT_SIGNATURE
  96. default n
  97. help
  98. Enable this to support the pss padding algorithm as described
  99. in the rfc8017 (https://tools.ietf.org/html/rfc8017).
  100. config FIT_CIPHER
  101. bool "Enable ciphering data in a FIT uImages"
  102. depends on DM
  103. select AES
  104. help
  105. Enable the feature of data ciphering/unciphering in the tool mkimage
  106. and in the u-boot support of the FIT image.
  107. config FIT_VERBOSE
  108. bool "Show verbose messages when FIT images fail"
  109. help
  110. Generally a system will have valid FIT images so debug messages
  111. are a waste of code space. If you are debugging your images then
  112. you can enable this option to get more verbose information about
  113. failures.
  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. config FIT_IMAGE_POST_PROCESS
  123. bool "Enable post-processing of FIT artifacts after loading by U-Boot"
  124. depends on TI_SECURE_DEVICE || SOCFPGA_SECURE_VAB_AUTH
  125. help
  126. Allows doing any sort of manipulation to blobs after they got extracted
  127. from FIT images like stripping off headers or modifying the size of the
  128. blob, verification, authentication, decryption etc. in a platform or
  129. board specific way. In order to use this feature a platform or board-
  130. specific implementation of board_fit_image_post_process() must be
  131. provided. Also, anything done during this post-processing step would
  132. need to be comprehended in how the images were prepared before being
  133. injected into the FIT creation (i.e. the blobs would have been pre-
  134. processed before being added to the FIT image).
  135. config FIT_PRINT
  136. bool "Support FIT printing"
  137. default y
  138. help
  139. Support printing the content of the fitImage in a verbose manner.
  140. if SPL
  141. config SPL_FIT
  142. bool "Support Flattened Image Tree within SPL"
  143. depends on SPL
  144. select SPL_OF_LIBFDT
  145. config SPL_FIT_PRINT
  146. bool "Support FIT printing within SPL"
  147. depends on SPL_FIT
  148. help
  149. Support printing the content of the fitImage in a verbose manner in SPL.
  150. config SPL_FIT_FULL_CHECK
  151. bool "Do a full check of the FIT before using it"
  152. help
  153. Enable this do a full check of the FIT to make sure it is valid. This
  154. helps to protect against carefully crafted FITs which take advantage
  155. of bugs or omissions in the code. This includes a bad structure,
  156. multiple root nodes and the like.
  157. config SPL_FIT_SIGNATURE
  158. bool "Enable signature verification of FIT firmware within SPL"
  159. depends on SPL_DM
  160. depends on SPL_LOAD_FIT || SPL_LOAD_FIT_FULL
  161. select FIT_SIGNATURE
  162. select SPL_FIT
  163. select SPL_CRYPTO_SUPPORT
  164. select SPL_HASH_SUPPORT
  165. select SPL_RSA
  166. select SPL_RSA_VERIFY
  167. select SPL_IMAGE_SIGN_INFO
  168. select SPL_FIT_FULL_CHECK
  169. config SPL_LOAD_FIT
  170. bool "Enable SPL loading U-Boot as a FIT (basic fitImage features)"
  171. select SPL_FIT
  172. help
  173. Normally with the SPL framework a legacy image is generated as part
  174. of the build. This contains U-Boot along with information as to
  175. where it should be loaded. This option instead enables generation
  176. of a FIT (Flat Image Tree) which provides more flexibility. In
  177. particular it can handle selecting from multiple device tree
  178. and passing the correct one to U-Boot.
  179. This path has the following limitations:
  180. 1. "loadables" images, other than FDTs, which do not have a "load"
  181. property will not be loaded. This limitation also applies to FPGA
  182. images with the correct "compatible" string.
  183. 2. For FPGA images, only the "compatible" = "u-boot,fpga-legacy"
  184. loading method is supported.
  185. 3. FDTs are only loaded for images with an "os" property of "u-boot".
  186. "linux" images are also supported with Falcon boot mode.
  187. config SPL_LOAD_FIT_ADDRESS
  188. hex "load address of fit image"
  189. depends on SPL_LOAD_FIT
  190. default 0x0
  191. help
  192. Specify the load address of the fit image that will be loaded
  193. by SPL.
  194. config SPL_LOAD_FIT_APPLY_OVERLAY
  195. bool "Enable SPL applying DT overlays from FIT"
  196. depends on SPL_LOAD_FIT
  197. select OF_LIBFDT_OVERLAY
  198. help
  199. The device tree is loaded from the FIT image. Allow the SPL is to
  200. also load device-tree overlays from the FIT image an apply them
  201. over the device tree.
  202. config SPL_LOAD_FIT_APPLY_OVERLAY_BUF_SZ
  203. depends on SPL_LOAD_FIT_APPLY_OVERLAY
  204. default 0x10000
  205. hex "size of temporary buffer used to load the overlays"
  206. help
  207. The size of the area where the overlays will be loaded and
  208. uncompress. Must be at least as large as biggest overlay
  209. (uncompressed)
  210. config SPL_LOAD_FIT_FULL
  211. bool "Enable SPL loading U-Boot as a FIT (full fitImage features)"
  212. select SPL_FIT
  213. help
  214. Normally with the SPL framework a legacy image is generated as part
  215. of the build. This contains U-Boot along with information as to
  216. where it should be loaded. This option instead enables generation
  217. of a FIT (Flat Image Tree) which provides more flexibility. In
  218. particular it can handle selecting from multiple device tree
  219. and passing the correct one to U-Boot.
  220. config SPL_FIT_IMAGE_POST_PROCESS
  221. bool "Enable post-processing of FIT artifacts after loading by the SPL"
  222. depends on SPL_LOAD_FIT
  223. help
  224. Allows doing any sort of manipulation to blobs after they got extracted
  225. from the U-Boot FIT image like stripping off headers or modifying the
  226. size of the blob, verification, authentication, decryption etc. in a
  227. platform or board specific way. In order to use this feature a platform
  228. or board-specific implementation of board_fit_image_post_process() must
  229. be provided. Also, anything done during this post-processing step would
  230. need to be comprehended in how the images were prepared before being
  231. injected into the FIT creation (i.e. the blobs would have been pre-
  232. processed before being added to the FIT image).
  233. config SPL_FIT_SOURCE
  234. string ".its source file for U-Boot FIT image"
  235. depends on SPL_FIT
  236. help
  237. Specifies a (platform specific) FIT source file to generate the
  238. U-Boot FIT image. This could specify further image to load and/or
  239. execute.
  240. config USE_SPL_FIT_GENERATOR
  241. bool "Use a script to generate the .its script"
  242. default y if SPL_FIT && (!ARCH_SUNXI && !RISCV)
  243. config SPL_FIT_GENERATOR
  244. string ".its file generator script for U-Boot FIT image"
  245. depends on USE_SPL_FIT_GENERATOR
  246. default "arch/arm/mach-rockchip/make_fit_atf.py" if SPL_LOAD_FIT && ARCH_ROCKCHIP
  247. default "arch/arm/mach-zynqmp/mkimage_fit_atf.sh" if SPL_LOAD_FIT && ARCH_ZYNQMP
  248. help
  249. Specifies a (platform specific) script file to generate the FIT
  250. source file used to build the U-Boot FIT image file. This gets
  251. passed a list of supported device tree file stub names to
  252. include in the generated image.
  253. endif # SPL
  254. endif # FIT
  255. config LEGACY_IMAGE_FORMAT
  256. bool "Enable support for the legacy image format"
  257. default y if !FIT_SIGNATURE
  258. help
  259. This option enables the legacy image format. It is enabled by
  260. default for backward compatibility, unless FIT_SIGNATURE is
  261. set where it is disabled so that unsigned images cannot be
  262. loaded. If a board needs the legacy image format support in this
  263. case, enable it here.
  264. config SUPPORT_RAW_INITRD
  265. bool "Enable raw initrd images"
  266. help
  267. Note, defining the SUPPORT_RAW_INITRD allows user to supply
  268. kernel with raw initrd images. The syntax is slightly different, the
  269. address of the initrd must be augmented by it's size, in the following
  270. format: "<initrd address>:<initrd size>".
  271. config OF_BOARD_SETUP
  272. bool "Set up board-specific details in device tree before boot"
  273. depends on OF_LIBFDT
  274. help
  275. This causes U-Boot to call ft_board_setup() before booting into
  276. the Operating System. This function can set up various
  277. board-specific information in the device tree for use by the OS.
  278. The device tree is then passed to the OS.
  279. config OF_SYSTEM_SETUP
  280. bool "Set up system-specific details in device tree before boot"
  281. depends on OF_LIBFDT
  282. help
  283. This causes U-Boot to call ft_system_setup() before booting into
  284. the Operating System. This function can set up various
  285. system-specific information in the device tree for use by the OS.
  286. The device tree is then passed to the OS.
  287. config OF_STDOUT_VIA_ALIAS
  288. bool "Update the device-tree stdout alias from U-Boot"
  289. depends on OF_LIBFDT
  290. help
  291. This uses U-Boot's serial alias from the aliases node to update
  292. the device tree passed to the OS. The "linux,stdout-path" property
  293. in the chosen node is set to point to the correct serial node.
  294. This option currently references CONFIG_CONS_INDEX, which is
  295. incorrect when used with device tree as this option does not
  296. exist / should not be used.
  297. config SYS_EXTRA_OPTIONS
  298. string "Extra Options (DEPRECATED)"
  299. help
  300. The old configuration infrastructure (= mkconfig + boards.cfg)
  301. provided the extra options field. If you have something like
  302. "HAS_BAR,BAZ=64", the optional options
  303. #define CONFIG_HAS
  304. #define CONFIG_BAZ 64
  305. will be defined in include/config.h.
  306. This option was prepared for the smooth migration from the old
  307. configuration to Kconfig. Since this option will be removed sometime,
  308. new boards should not use this option.
  309. config HAVE_SYS_TEXT_BASE
  310. bool
  311. depends on !NIOS2 && !XTENSA
  312. depends on !EFI_APP
  313. default y
  314. config SYS_TEXT_BASE
  315. depends on HAVE_SYS_TEXT_BASE
  316. default 0x0 if POSITION_INDEPENDENT
  317. default 0x80800000 if ARCH_OMAP2PLUS || ARCH_K3
  318. default 0x4a000000 if ARCH_SUNXI && !MACH_SUN9I && !MACH_SUN8I_V3S
  319. default 0x2a000000 if ARCH_SUNXI && MACH_SUN9I
  320. default 0x42e00000 if ARCH_SUNXI && MACH_SUN8I_V3S
  321. hex "Text Base"
  322. help
  323. The address in memory that U-Boot will be running from, initially.
  324. config SYS_CLK_FREQ
  325. depends on ARC || ARCH_SUNXI || MPC83xx
  326. int "CPU clock frequency"
  327. help
  328. TODO: Move CONFIG_SYS_CLK_FREQ for all the architecture
  329. config ARCH_FIXUP_FDT_MEMORY
  330. bool "Enable arch_fixup_memory_banks() call"
  331. default y
  332. help
  333. Enable FDT memory map syncup before OS boot. This feature can be
  334. used for booting OS with different memory setup where the part of
  335. the memory location should be used for different purpose.
  336. config CHROMEOS
  337. bool "Support booting Chrome OS"
  338. help
  339. Chrome OS requires U-Boot to set up a table indicating the boot mode
  340. (e.g. Developer mode) and a few other things. Enable this if you are
  341. booting on a Chromebook to avoid getting an error about an invalid
  342. firmware ID.
  343. config CHROMEOS_VBOOT
  344. bool "Support Chrome OS verified boot"
  345. help
  346. This is intended to enable the full Chrome OS verified boot support
  347. in U-Boot. It is not actually implemented in the U-Boot source code
  348. at present, so this option is always set to 'n'. It allows
  349. distinguishing between booting Chrome OS in a basic way (developer
  350. mode) and a full boot.
  351. endmenu # Boot images
  352. menu "Boot timing"
  353. config BOOTSTAGE
  354. bool "Boot timing and reporting"
  355. help
  356. Enable recording of boot time while booting. To use it, insert
  357. calls to bootstage_mark() with a suitable BOOTSTAGE_ID from
  358. bootstage.h. Only a single entry is recorded for each ID. You can
  359. give the entry a name with bootstage_mark_name(). You can also
  360. record elapsed time in a particular stage using bootstage_start()
  361. before starting and bootstage_accum() when finished. Bootstage will
  362. add up all the accumulated time and report it.
  363. Normally, IDs are defined in bootstage.h but a small number of
  364. additional 'user' IDs can be used by passing BOOTSTAGE_ID_ALLOC
  365. as the ID.
  366. Calls to show_boot_progress() will also result in log entries but
  367. these will not have names.
  368. config SPL_BOOTSTAGE
  369. bool "Boot timing and reported in SPL"
  370. depends on BOOTSTAGE
  371. help
  372. Enable recording of boot time in SPL. To make this visible to U-Boot
  373. proper, enable BOOTSTAGE_STASH as well. This will stash the timing
  374. information when SPL finishes and load it when U-Boot proper starts
  375. up.
  376. config TPL_BOOTSTAGE
  377. bool "Boot timing and reported in TPL"
  378. depends on BOOTSTAGE
  379. help
  380. Enable recording of boot time in SPL. To make this visible to U-Boot
  381. proper, enable BOOTSTAGE_STASH as well. This will stash the timing
  382. information when TPL finishes and load it when U-Boot proper starts
  383. up.
  384. config BOOTSTAGE_REPORT
  385. bool "Display a detailed boot timing report before booting the OS"
  386. depends on BOOTSTAGE
  387. help
  388. Enable output of a boot time report just before the OS is booted.
  389. This shows how long it took U-Boot to go through each stage of the
  390. boot process. The report looks something like this:
  391. Timer summary in microseconds:
  392. Mark Elapsed Stage
  393. 0 0 reset
  394. 3,575,678 3,575,678 board_init_f start
  395. 3,575,695 17 arch_cpu_init A9
  396. 3,575,777 82 arch_cpu_init done
  397. 3,659,598 83,821 board_init_r start
  398. 3,910,375 250,777 main_loop
  399. 29,916,167 26,005,792 bootm_start
  400. 30,361,327 445,160 start_kernel
  401. config BOOTSTAGE_RECORD_COUNT
  402. int "Number of boot stage records to store"
  403. depends on BOOTSTAGE
  404. default 30
  405. help
  406. This is the size of the bootstage record list and is the maximum
  407. number of bootstage records that can be recorded.
  408. config SPL_BOOTSTAGE_RECORD_COUNT
  409. int "Number of boot stage records to store for SPL"
  410. depends on SPL_BOOTSTAGE
  411. default 5
  412. help
  413. This is the size of the bootstage record list and is the maximum
  414. number of bootstage records that can be recorded.
  415. config TPL_BOOTSTAGE_RECORD_COUNT
  416. int "Number of boot stage records to store for TPL"
  417. depends on TPL_BOOTSTAGE
  418. default 5
  419. help
  420. This is the size of the bootstage record list and is the maximum
  421. number of bootstage records that can be recorded.
  422. config BOOTSTAGE_FDT
  423. bool "Store boot timing information in the OS device tree"
  424. depends on BOOTSTAGE
  425. help
  426. Stash the bootstage information in the FDT. A root 'bootstage'
  427. node is created with each bootstage id as a child. Each child
  428. has a 'name' property and either 'mark' containing the
  429. mark time in microseconds, or 'accum' containing the
  430. accumulated time for that bootstage id in microseconds.
  431. For example:
  432. bootstage {
  433. 154 {
  434. name = "board_init_f";
  435. mark = <3575678>;
  436. };
  437. 170 {
  438. name = "lcd";
  439. accum = <33482>;
  440. };
  441. };
  442. Code in the Linux kernel can find this in /proc/devicetree.
  443. config BOOTSTAGE_STASH
  444. bool "Stash the boot timing information in memory before booting OS"
  445. depends on BOOTSTAGE
  446. help
  447. Some OSes do not support device tree. Bootstage can instead write
  448. the boot timing information in a binary format at a given address.
  449. This happens through a call to bootstage_stash(), typically in
  450. the CPU's cleanup_before_linux() function. You can use the
  451. 'bootstage stash' and 'bootstage unstash' commands to do this on
  452. the command line.
  453. config BOOTSTAGE_STASH_ADDR
  454. hex "Address to stash boot timing information"
  455. default 0
  456. help
  457. Provide an address which will not be overwritten by the OS when it
  458. starts, so that it can read this information when ready.
  459. config BOOTSTAGE_STASH_SIZE
  460. hex "Size of boot timing stash region"
  461. default 0x1000
  462. help
  463. This should be large enough to hold the bootstage stash. A value of
  464. 4096 (4KiB) is normally plenty.
  465. config SHOW_BOOT_PROGRESS
  466. bool "Show boot progress in a board-specific manner"
  467. help
  468. Defining this option allows to add some board-specific code (calling
  469. a user-provided function show_boot_progress(int) that enables you to
  470. show the system's boot progress on some display (for example, some
  471. LEDs) on your board. At the moment, the following checkpoints are
  472. implemented:
  473. Legacy uImage format:
  474. Arg Where When
  475. 1 common/cmd_bootm.c before attempting to boot an image
  476. -1 common/cmd_bootm.c Image header has bad magic number
  477. 2 common/cmd_bootm.c Image header has correct magic number
  478. -2 common/cmd_bootm.c Image header has bad checksum
  479. 3 common/cmd_bootm.c Image header has correct checksum
  480. -3 common/cmd_bootm.c Image data has bad checksum
  481. 4 common/cmd_bootm.c Image data has correct checksum
  482. -4 common/cmd_bootm.c Image is for unsupported architecture
  483. 5 common/cmd_bootm.c Architecture check OK
  484. -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi)
  485. 6 common/cmd_bootm.c Image Type check OK
  486. -6 common/cmd_bootm.c gunzip uncompression error
  487. -7 common/cmd_bootm.c Unimplemented compression type
  488. 7 common/cmd_bootm.c Uncompression OK
  489. 8 common/cmd_bootm.c No uncompress/copy overwrite error
  490. -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
  491. 9 common/image.c Start initial ramdisk verification
  492. -10 common/image.c Ramdisk header has bad magic number
  493. -11 common/image.c Ramdisk header has bad checksum
  494. 10 common/image.c Ramdisk header is OK
  495. -12 common/image.c Ramdisk data has bad checksum
  496. 11 common/image.c Ramdisk data has correct checksum
  497. 12 common/image.c Ramdisk verification complete, start loading
  498. -13 common/image.c Wrong Image Type (not PPC Linux ramdisk)
  499. 13 common/image.c Start multifile image verification
  500. 14 common/image.c No initial ramdisk, no multifile, continue.
  501. 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS
  502. -30 arch/powerpc/lib/board.c Fatal error, hang the system
  503. -31 post/post.c POST test failed, detected by post_output_backlog()
  504. -32 post/post.c POST test failed, detected by post_run_single()
  505. 34 common/cmd_doc.c before loading a Image from a DOC device
  506. -35 common/cmd_doc.c Bad usage of "doc" command
  507. 35 common/cmd_doc.c correct usage of "doc" command
  508. -36 common/cmd_doc.c No boot device
  509. 36 common/cmd_doc.c correct boot device
  510. -37 common/cmd_doc.c Unknown Chip ID on boot device
  511. 37 common/cmd_doc.c correct chip ID found, device available
  512. -38 common/cmd_doc.c Read Error on boot device
  513. 38 common/cmd_doc.c reading Image header from DOC device OK
  514. -39 common/cmd_doc.c Image header has bad magic number
  515. 39 common/cmd_doc.c Image header has correct magic number
  516. -40 common/cmd_doc.c Error reading Image from DOC device
  517. 40 common/cmd_doc.c Image header has correct magic number
  518. 41 common/cmd_ide.c before loading a Image from a IDE device
  519. -42 common/cmd_ide.c Bad usage of "ide" command
  520. 42 common/cmd_ide.c correct usage of "ide" command
  521. -43 common/cmd_ide.c No boot device
  522. 43 common/cmd_ide.c boot device found
  523. -44 common/cmd_ide.c Device not available
  524. 44 common/cmd_ide.c Device available
  525. -45 common/cmd_ide.c wrong partition selected
  526. 45 common/cmd_ide.c partition selected
  527. -46 common/cmd_ide.c Unknown partition table
  528. 46 common/cmd_ide.c valid partition table found
  529. -47 common/cmd_ide.c Invalid partition type
  530. 47 common/cmd_ide.c correct partition type
  531. -48 common/cmd_ide.c Error reading Image Header on boot device
  532. 48 common/cmd_ide.c reading Image Header from IDE device OK
  533. -49 common/cmd_ide.c Image header has bad magic number
  534. 49 common/cmd_ide.c Image header has correct magic number
  535. -50 common/cmd_ide.c Image header has bad checksum
  536. 50 common/cmd_ide.c Image header has correct checksum
  537. -51 common/cmd_ide.c Error reading Image from IDE device
  538. 51 common/cmd_ide.c reading Image from IDE device OK
  539. 52 common/cmd_nand.c before loading a Image from a NAND device
  540. -53 common/cmd_nand.c Bad usage of "nand" command
  541. 53 common/cmd_nand.c correct usage of "nand" command
  542. -54 common/cmd_nand.c No boot device
  543. 54 common/cmd_nand.c boot device found
  544. -55 common/cmd_nand.c Unknown Chip ID on boot device
  545. 55 common/cmd_nand.c correct chip ID found, device available
  546. -56 common/cmd_nand.c Error reading Image Header on boot device
  547. 56 common/cmd_nand.c reading Image Header from NAND device OK
  548. -57 common/cmd_nand.c Image header has bad magic number
  549. 57 common/cmd_nand.c Image header has correct magic number
  550. -58 common/cmd_nand.c Error reading Image from NAND device
  551. 58 common/cmd_nand.c reading Image from NAND device OK
  552. -60 common/env_common.c Environment has a bad CRC, using default
  553. 64 net/eth.c starting with Ethernet configuration.
  554. -64 net/eth.c no Ethernet found.
  555. 65 net/eth.c Ethernet found.
  556. -80 common/cmd_net.c usage wrong
  557. 80 common/cmd_net.c before calling net_loop()
  558. -81 common/cmd_net.c some error in net_loop() occurred
  559. 81 common/cmd_net.c net_loop() back without error
  560. -82 common/cmd_net.c size == 0 (File with size 0 loaded)
  561. 82 common/cmd_net.c trying automatic boot
  562. 83 common/cmd_net.c running "source" command
  563. -83 common/cmd_net.c some error in automatic boot or "source" command
  564. 84 common/cmd_net.c end without errors
  565. FIT uImage format:
  566. Arg Where When
  567. 100 common/cmd_bootm.c Kernel FIT Image has correct format
  568. -100 common/cmd_bootm.c Kernel FIT Image has incorrect format
  569. 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration
  570. -101 common/cmd_bootm.c Can't get configuration for kernel subimage
  571. 102 common/cmd_bootm.c Kernel unit name specified
  572. -103 common/cmd_bootm.c Can't get kernel subimage node offset
  573. 103 common/cmd_bootm.c Found configuration node
  574. 104 common/cmd_bootm.c Got kernel subimage node offset
  575. -104 common/cmd_bootm.c Kernel subimage hash verification failed
  576. 105 common/cmd_bootm.c Kernel subimage hash verification OK
  577. -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture
  578. 106 common/cmd_bootm.c Architecture check OK
  579. -106 common/cmd_bootm.c Kernel subimage has wrong type
  580. 107 common/cmd_bootm.c Kernel subimage type OK
  581. -107 common/cmd_bootm.c Can't get kernel subimage data/size
  582. 108 common/cmd_bootm.c Got kernel subimage data/size
  583. -108 common/cmd_bootm.c Wrong image type (not legacy, FIT)
  584. -109 common/cmd_bootm.c Can't get kernel subimage type
  585. -110 common/cmd_bootm.c Can't get kernel subimage comp
  586. -111 common/cmd_bootm.c Can't get kernel subimage os
  587. -112 common/cmd_bootm.c Can't get kernel subimage load address
  588. -113 common/cmd_bootm.c Image uncompress/copy overwrite error
  589. 120 common/image.c Start initial ramdisk verification
  590. -120 common/image.c Ramdisk FIT image has incorrect format
  591. 121 common/image.c Ramdisk FIT image has correct format
  592. 122 common/image.c No ramdisk subimage unit name, using configuration
  593. -122 common/image.c Can't get configuration for ramdisk subimage
  594. 123 common/image.c Ramdisk unit name specified
  595. -124 common/image.c Can't get ramdisk subimage node offset
  596. 125 common/image.c Got ramdisk subimage node offset
  597. -125 common/image.c Ramdisk subimage hash verification failed
  598. 126 common/image.c Ramdisk subimage hash verification OK
  599. -126 common/image.c Ramdisk subimage for unsupported architecture
  600. 127 common/image.c Architecture check OK
  601. -127 common/image.c Can't get ramdisk subimage data/size
  602. 128 common/image.c Got ramdisk subimage data/size
  603. 129 common/image.c Can't get ramdisk load address
  604. -129 common/image.c Got ramdisk load address
  605. -130 common/cmd_doc.c Incorrect FIT image format
  606. 131 common/cmd_doc.c FIT image format OK
  607. -140 common/cmd_ide.c Incorrect FIT image format
  608. 141 common/cmd_ide.c FIT image format OK
  609. -150 common/cmd_nand.c Incorrect FIT image format
  610. 151 common/cmd_nand.c FIT image format OK
  611. endmenu
  612. menu "Boot media"
  613. config NOR_BOOT
  614. bool "Support for booting from NOR flash"
  615. depends on NOR
  616. help
  617. Enabling this will make a U-Boot binary that is capable of being
  618. booted via NOR. In this case we will enable certain pinmux early
  619. as the ROM only partially sets up pinmux. We also default to using
  620. NOR for environment.
  621. config NAND_BOOT
  622. bool "Support for booting from NAND flash"
  623. default n
  624. imply MTD_RAW_NAND
  625. help
  626. Enabling this will make a U-Boot binary that is capable of being
  627. booted via NAND flash. This is not a must, some SoCs need this,
  628. some not.
  629. config ONENAND_BOOT
  630. bool "Support for booting from ONENAND"
  631. default n
  632. imply MTD_RAW_NAND
  633. help
  634. Enabling this will make a U-Boot binary that is capable of being
  635. booted via ONENAND. This is not a must, some SoCs need this,
  636. some not.
  637. config QSPI_BOOT
  638. bool "Support for booting from QSPI flash"
  639. default n
  640. help
  641. Enabling this will make a U-Boot binary that is capable of being
  642. booted via QSPI flash. This is not a must, some SoCs need this,
  643. some not.
  644. config SATA_BOOT
  645. bool "Support for booting from SATA"
  646. default n
  647. help
  648. Enabling this will make a U-Boot binary that is capable of being
  649. booted via SATA. This is not a must, some SoCs need this,
  650. some not.
  651. config SD_BOOT
  652. bool "Support for booting from SD/EMMC"
  653. default n
  654. help
  655. Enabling this will make a U-Boot binary that is capable of being
  656. booted via SD/EMMC. This is not a must, some SoCs need this,
  657. some not.
  658. config SPI_BOOT
  659. bool "Support for booting from SPI flash"
  660. default n
  661. help
  662. Enabling this will make a U-Boot binary that is capable of being
  663. booted via SPI flash. This is not a must, some SoCs need this,
  664. some not.
  665. endmenu
  666. menu "Autoboot options"
  667. config AUTOBOOT
  668. bool "Autoboot"
  669. default y
  670. help
  671. This enables the autoboot. See doc/README.autoboot for detail.
  672. config BOOTDELAY
  673. int "delay in seconds before automatically booting"
  674. default 2
  675. depends on AUTOBOOT
  676. help
  677. Delay before automatically running bootcmd;
  678. set to 0 to autoboot with no delay, but you can stop it by key input.
  679. set to -1 to disable autoboot.
  680. set to -2 to autoboot with no delay and not check for abort
  681. If this value is >= 0 then it is also used for the default delay
  682. before starting the default entry in bootmenu. If it is < 0 then
  683. a default value of 10s is used.
  684. See doc/README.autoboot for details.
  685. config AUTOBOOT_KEYED
  686. bool "Stop autobooting via specific input key / string"
  687. default n
  688. help
  689. This option enables stopping (aborting) of the automatic
  690. boot feature only by issuing a specific input key or
  691. string. If not enabled, any input key will abort the
  692. U-Boot automatic booting process and bring the device
  693. to the U-Boot prompt for user input.
  694. config AUTOBOOT_FLUSH_STDIN
  695. bool "Enable flushing stdin before starting to read the password"
  696. depends on AUTOBOOT_KEYED && !SANDBOX
  697. help
  698. When this option is enabled stdin buffer will be flushed before
  699. starting to read the password.
  700. This can't be enabled for the sandbox as flushing stdin would
  701. break the autoboot unit tests.
  702. config AUTOBOOT_PROMPT
  703. string "Autoboot stop prompt"
  704. depends on AUTOBOOT_KEYED
  705. default "Autoboot in %d seconds\\n"
  706. help
  707. This string is displayed before the boot delay selected by
  708. CONFIG_BOOTDELAY starts. If it is not defined there is no
  709. output indicating that autoboot is in progress.
  710. Note that this define is used as the (only) argument to a
  711. printf() call, so it may contain '%' format specifications,
  712. provided that it also includes, sepearated by commas exactly
  713. like in a printf statement, the required arguments. It is
  714. the responsibility of the user to select only such arguments
  715. that are valid in the given context.
  716. config AUTOBOOT_ENCRYPTION
  717. bool "Enable encryption in autoboot stopping"
  718. depends on AUTOBOOT_KEYED
  719. help
  720. This option allows a string to be entered into U-Boot to stop the
  721. autoboot.
  722. The behavior depends whether CONFIG_CRYPT_PW from lib is enabled
  723. or not.
  724. In case CONFIG_CRYPT_PW is enabled, the string will be forwarded
  725. to the crypt-based functionality and be compared against the
  726. string in the environment variable 'bootstopkeycrypt'.
  727. In case CONFIG_CRYPT_PW is disabled the string itself is hashed
  728. and compared against the hash in the environment variable
  729. 'bootstopkeysha256'.
  730. If it matches in either case then boot stops and
  731. a command-line prompt is presented.
  732. This provides a way to ship a secure production device which can also
  733. be accessed at the U-Boot command line.
  734. config AUTOBOOT_SHA256_FALLBACK
  735. bool "Allow fallback from crypt-hashed password to sha256"
  736. depends on AUTOBOOT_ENCRYPTION && CRYPT_PW
  737. help
  738. This option adds support to fall back from crypt-hashed
  739. passwords to checking a SHA256 hashed password in case the
  740. 'bootstopusesha256' environment variable is set to 'true'.
  741. config AUTOBOOT_DELAY_STR
  742. string "Delay autobooting via specific input key / string"
  743. depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
  744. help
  745. This option delays the automatic boot feature by issuing
  746. a specific input key or string. If CONFIG_AUTOBOOT_DELAY_STR
  747. or the environment variable "bootdelaykey" is specified
  748. and this string is received from console input before
  749. autoboot starts booting, U-Boot gives a command prompt. The
  750. U-Boot prompt will time out if CONFIG_BOOT_RETRY_TIME is
  751. used, otherwise it never times out.
  752. config AUTOBOOT_STOP_STR
  753. string "Stop autobooting via specific input key / string"
  754. depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
  755. help
  756. This option enables stopping (aborting) of the automatic
  757. boot feature only by issuing a specific input key or
  758. string. If CONFIG_AUTOBOOT_STOP_STR or the environment
  759. variable "bootstopkey" is specified and this string is
  760. received from console input before autoboot starts booting,
  761. U-Boot gives a command prompt. The U-Boot prompt never
  762. times out, even if CONFIG_BOOT_RETRY_TIME is used.
  763. config AUTOBOOT_KEYED_CTRLC
  764. bool "Enable Ctrl-C autoboot interruption"
  765. depends on AUTOBOOT_KEYED && !AUTOBOOT_ENCRYPTION
  766. default n
  767. help
  768. This option allows for the boot sequence to be interrupted
  769. by ctrl-c, in addition to the "bootdelaykey" and "bootstopkey".
  770. Setting this variable provides an escape sequence from the
  771. limited "password" strings.
  772. config AUTOBOOT_NEVER_TIMEOUT
  773. bool "Make the password entry never time-out"
  774. depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION && CRYPT_PW
  775. help
  776. This option removes the timeout from the password entry
  777. when the user first presses the <Enter> key before entering
  778. any other character.
  779. config AUTOBOOT_STOP_STR_ENABLE
  780. bool "Enable fixed string to stop autobooting"
  781. depends on AUTOBOOT_KEYED && AUTOBOOT_ENCRYPTION
  782. help
  783. This option enables the feature to add a fixed stop
  784. string that is defined at compile time.
  785. In every case it will be tried to load the stop
  786. string from the environment.
  787. In case this is enabled and there is no stop string
  788. in the environment, this will be used as default value.
  789. config AUTOBOOT_STOP_STR_CRYPT
  790. string "Stop autobooting via crypt-hashed password"
  791. depends on AUTOBOOT_STOP_STR_ENABLE && CRYPT_PW
  792. help
  793. This option adds the feature to only stop the autobooting,
  794. and therefore boot into the U-Boot prompt, when the input
  795. string / password matches a values that is hashed via
  796. one of the supported crypt-style password hashing options
  797. and saved in the environment variable "bootstopkeycrypt".
  798. config AUTOBOOT_STOP_STR_SHA256
  799. string "Stop autobooting via SHA256 hashed password"
  800. depends on AUTOBOOT_STOP_STR_ENABLE
  801. help
  802. This option adds the feature to only stop the autobooting,
  803. and therefore boot into the U-Boot prompt, when the input
  804. string / password matches a values that is encypted via
  805. a SHA256 hash and saved in the environment variable
  806. "bootstopkeysha256". If the value in that variable
  807. includes a ":", the portion prior to the ":" will be treated
  808. as a salt value.
  809. config AUTOBOOT_USE_MENUKEY
  810. bool "Allow a specify key to run a menu from the environment"
  811. depends on !AUTOBOOT_KEYED
  812. help
  813. If a specific key is pressed to stop autoboot, then the commands in
  814. the environment variable 'menucmd' are executed before boot starts.
  815. config AUTOBOOT_MENUKEY
  816. int "ASCII value of boot key to show a menu"
  817. default 0
  818. depends on AUTOBOOT_USE_MENUKEY
  819. help
  820. If this key is pressed to stop autoboot, then the commands in the
  821. environment variable 'menucmd' will be executed before boot starts.
  822. For example, 33 means "!" in ASCII, so pressing ! at boot would take
  823. this action.
  824. config AUTOBOOT_MENU_SHOW
  825. bool "Show a menu on boot"
  826. depends on CMD_BOOTMENU
  827. help
  828. This enables the boot menu, controlled by environment variables
  829. defined by the board. The menu starts after running the 'preboot'
  830. environmnent variable (if enabled) and before handling the boot delay.
  831. See README.bootmenu for more details.
  832. endmenu
  833. config USE_BOOTARGS
  834. bool "Enable boot arguments"
  835. help
  836. Provide boot arguments to bootm command. Boot arguments are specified
  837. in CONFIG_BOOTARGS option. Enable this option to be able to specify
  838. CONFIG_BOOTARGS string. If this option is disabled, CONFIG_BOOTARGS
  839. will be undefined and won't take any space in U-Boot image.
  840. config BOOTARGS
  841. string "Boot arguments"
  842. depends on USE_BOOTARGS && !USE_DEFAULT_ENV_FILE
  843. help
  844. This can be used to pass arguments to the bootm command. The value of
  845. CONFIG_BOOTARGS goes into the environment value "bootargs". Note that
  846. this value will also override the "chosen" node in FDT blob.
  847. config BOOTARGS_SUBST
  848. bool "Support substituting strings in boot arguments"
  849. help
  850. This allows substituting string values in the boot arguments. These
  851. are applied after the commandline has been built.
  852. One use for this is to insert the root-disk UUID into the command
  853. line where bootargs contains "root=${uuid}"
  854. setenv bootargs "console= root=${uuid}"
  855. # Set the 'uuid' environment variable
  856. part uuid mmc 2:2 uuid
  857. # Command-line substitution will put the real uuid into the
  858. # kernel command line
  859. bootm
  860. config USE_BOOTCOMMAND
  861. bool "Enable a default value for bootcmd"
  862. help
  863. Provide a default value for the bootcmd entry in the environment. If
  864. autoboot is enabled this is what will be run automatically. Enable
  865. this option to be able to specify CONFIG_BOOTCOMMAND as a string. If
  866. this option is disabled, CONFIG_BOOTCOMMAND will be undefined and
  867. won't take any space in U-Boot image.
  868. config BOOTCOMMAND
  869. string "bootcmd value"
  870. depends on USE_BOOTCOMMAND && !USE_DEFAULT_ENV_FILE
  871. default "run distro_bootcmd" if DISTRO_DEFAULTS
  872. help
  873. This is the string of commands that will be used as bootcmd and if
  874. AUTOBOOT is set, automatically run.
  875. config USE_PREBOOT
  876. bool "Enable preboot"
  877. help
  878. When this option is enabled, the existence of the environment
  879. variable "preboot" will be checked immediately before starting the
  880. CONFIG_BOOTDELAY countdown and/or running the auto-boot command resp.
  881. entering interactive mode.
  882. This feature is especially useful when "preboot" is automatically
  883. generated or modified. For example, the boot code can modify the
  884. "preboot" when a user holds down a certain combination of keys.
  885. config PREBOOT
  886. string "preboot default value"
  887. depends on USE_PREBOOT && !USE_DEFAULT_ENV_FILE
  888. default "usb start" if USB_KEYBOARD
  889. default ""
  890. help
  891. This is the default of "preboot" environment variable.
  892. config DEFAULT_FDT_FILE
  893. string "Default fdt file"
  894. help
  895. This option is used to set the default fdt file to boot OS.
  896. endmenu # Booting