Kconfig.boot 36 KB

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