Kconfig.boot 35 KB

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