Kconfig.boot 37 KB

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