Kconfig 40 KB

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