blob: 2384966a39fbde5116006755f5599ecb8dc36bb5 [file] [log] [blame]
Tom Rini83d290c2018-05-06 17:58:06 -04001# SPDX-License-Identifier: GPL-2.0+
wdenkc6097192002-11-03 00:24:07 +00002#
Wolfgang Denkeca3aeb2013-06-21 10:22:36 +02003# (C) Copyright 2000 - 2013
wdenkc6097192002-11-03 00:24:07 +00004# Wolfgang Denk, DENX Software Engineering, wd@denx.de.
wdenkc6097192002-11-03 00:24:07 +00005
6Summary:
7========
8
wdenk24ee89b2002-11-03 17:56:27 +00009This directory contains the source code for U-Boot, a boot loader for
wdenke86e5a02004-10-17 21:12:06 +000010Embedded boards based on PowerPC, ARM, MIPS and several other
11processors, which can be installed in a boot ROM and used to
12initialize and test the hardware or to download and run application
13code.
wdenkc6097192002-11-03 00:24:07 +000014
15The development of U-Boot is closely related to Linux: some parts of
wdenk24ee89b2002-11-03 17:56:27 +000016the source code originate in the Linux source tree, we have some
17header files in common, and special provision has been made to
wdenkc6097192002-11-03 00:24:07 +000018support booting of Linux images.
19
20Some attention has been paid to make this software easily
21configurable and extendable. For instance, all monitor commands are
22implemented with the same call interface, so that it's very easy to
23add new commands. Also, instead of permanently adding rarely used
24code (for instance hardware test utilities) to the monitor, you can
25load and run it dynamically.
26
27
28Status:
29=======
30
31In general, all boards for which a configuration option exists in the
wdenk24ee89b2002-11-03 17:56:27 +000032Makefile have been tested to some extent and can be considered
wdenkc6097192002-11-03 00:24:07 +000033"working". In fact, many of them are used in production systems.
34
Robert P. J. Day7207b362015-12-19 07:16:10 -050035In case of problems see the CHANGELOG file to find out who contributed
36the specific port. In addition, there are various MAINTAINERS files
37scattered throughout the U-Boot source identifying the people or
38companies responsible for various boards and subsystems.
wdenkc6097192002-11-03 00:24:07 +000039
Robert P. J. Day7207b362015-12-19 07:16:10 -050040Note: As of August, 2010, there is no longer a CHANGELOG file in the
41actual U-Boot source tree; however, it can be created dynamically
42from the Git log using:
Robert P. J. Dayadb9d852012-11-14 02:03:20 +000043
44 make CHANGELOG
45
wdenkc6097192002-11-03 00:24:07 +000046
47Where to get help:
48==================
49
wdenk24ee89b2002-11-03 17:56:27 +000050In case you have questions about, problems with or contributions for
Robert P. J. Day7207b362015-12-19 07:16:10 -050051U-Boot, you should send a message to the U-Boot mailing list at
Peter Tyser0c325652008-09-10 09:18:34 -050052<u-boot@lists.denx.de>. There is also an archive of previous traffic
53on the mailing list - please search the archive before asking FAQ's.
54Please see http://lists.denx.de/pipermail/u-boot and
55http://dir.gmane.org/gmane.comp.boot-loaders.u-boot
wdenkc6097192002-11-03 00:24:07 +000056
57
Wolfgang Denk218ca722008-03-26 10:40:12 +010058Where to get source code:
59=========================
60
Robert P. J. Day7207b362015-12-19 07:16:10 -050061The U-Boot source code is maintained in the Git repository at
Wolfgang Denk218ca722008-03-26 10:40:12 +010062git://www.denx.de/git/u-boot.git ; you can browse it online at
63http://www.denx.de/cgi-bin/gitweb.cgi?p=u-boot.git;a=summary
64
65The "snapshot" links on this page allow you to download tarballs of
Marcel Ziswiler11ccc332008-07-09 08:17:15 +020066any version you might be interested in. Official releases are also
Wolfgang Denk218ca722008-03-26 10:40:12 +010067available for FTP download from the ftp://ftp.denx.de/pub/u-boot/
68directory.
69
Anatolij Gustschind4ee7112008-03-26 18:13:33 +010070Pre-built (and tested) images are available from
Wolfgang Denk218ca722008-03-26 10:40:12 +010071ftp://ftp.denx.de/pub/u-boot/images/
72
73
wdenkc6097192002-11-03 00:24:07 +000074Where we come from:
75===================
76
77- start from 8xxrom sources
wdenk24ee89b2002-11-03 17:56:27 +000078- create PPCBoot project (http://sourceforge.net/projects/ppcboot)
wdenkc6097192002-11-03 00:24:07 +000079- clean up code
80- make it easier to add custom boards
81- make it possible to add other [PowerPC] CPUs
82- extend functions, especially:
83 * Provide extended interface to Linux boot loader
84 * S-Record download
85 * network boot
Simon Glass9e5616d2019-08-01 09:47:14 -060086 * ATA disk / SCSI ... boot
wdenk24ee89b2002-11-03 17:56:27 +000087- create ARMBoot project (http://sourceforge.net/projects/armboot)
wdenkc6097192002-11-03 00:24:07 +000088- add other CPU families (starting with ARM)
wdenk24ee89b2002-11-03 17:56:27 +000089- create U-Boot project (http://sourceforge.net/projects/u-boot)
Magnus Lilja0d28f342008-08-06 19:32:33 +020090- current project page: see http://www.denx.de/wiki/U-Boot
wdenk24ee89b2002-11-03 17:56:27 +000091
92
93Names and Spelling:
94===================
95
96The "official" name of this project is "Das U-Boot". The spelling
97"U-Boot" shall be used in all written text (documentation, comments
98in source files etc.). Example:
99
100 This is the README file for the U-Boot project.
101
102File names etc. shall be based on the string "u-boot". Examples:
103
104 include/asm-ppc/u-boot.h
105
106 #include <asm/u-boot.h>
107
108Variable names, preprocessor constants etc. shall be either based on
109the string "u_boot" or on "U_BOOT". Example:
110
111 U_BOOT_VERSION u_boot_logo
112 IH_OS_U_BOOT u_boot_hush_start
wdenkc6097192002-11-03 00:24:07 +0000113
114
wdenk93f19cc2002-12-17 17:55:09 +0000115Versioning:
116===========
117
Thomas Weber360d8832010-09-28 08:06:25 +0200118Starting with the release in October 2008, the names of the releases
119were changed from numerical release numbers without deeper meaning
120into a time stamp based numbering. Regular releases are identified by
121names consisting of the calendar year and month of the release date.
122Additional fields (if present) indicate release candidates or bug fix
123releases in "stable" maintenance trees.
wdenk93f19cc2002-12-17 17:55:09 +0000124
Thomas Weber360d8832010-09-28 08:06:25 +0200125Examples:
Wolfgang Denkc0f40852011-10-26 10:21:21 +0000126 U-Boot v2009.11 - Release November 2009
Thomas Weber360d8832010-09-28 08:06:25 +0200127 U-Boot v2009.11.1 - Release 1 in version November 2009 stable tree
Jelle van der Waa0de21ec2016-10-30 17:30:30 +0100128 U-Boot v2010.09-rc1 - Release candidate 1 for September 2010 release
wdenk93f19cc2002-12-17 17:55:09 +0000129
130
wdenkc6097192002-11-03 00:24:07 +0000131Directory Hierarchy:
132====================
133
Peter Tyser8d321b82010-04-12 22:28:21 -0500134/arch Architecture specific files
Masahiro Yamada6eae68e2014-03-07 18:02:02 +0900135 /arc Files generic to ARC architecture
Peter Tyser8d321b82010-04-12 22:28:21 -0500136 /arm Files generic to ARM architecture
Peter Tyser8d321b82010-04-12 22:28:21 -0500137 /m68k Files generic to m68k architecture
Peter Tyser8d321b82010-04-12 22:28:21 -0500138 /microblaze Files generic to microblaze architecture
Peter Tyser8d321b82010-04-12 22:28:21 -0500139 /mips Files generic to MIPS architecture
Macpaul Linafc1ce82011-10-19 20:41:11 +0000140 /nds32 Files generic to NDS32 architecture
Peter Tyser8d321b82010-04-12 22:28:21 -0500141 /nios2 Files generic to Altera NIOS2 architecture
Robert P. J. Day33c77312013-09-15 18:34:15 -0400142 /openrisc Files generic to OpenRISC architecture
Stefan Roesea47a12b2010-04-15 16:07:28 +0200143 /powerpc Files generic to PowerPC architecture
Rick Chen3fafced2017-12-26 13:55:59 +0800144 /riscv Files generic to RISC-V architecture
Robert P. J. Day7207b362015-12-19 07:16:10 -0500145 /sandbox Files generic to HW-independent "sandbox"
Peter Tyser8d321b82010-04-12 22:28:21 -0500146 /sh Files generic to SH architecture
Robert P. J. Day33c77312013-09-15 18:34:15 -0400147 /x86 Files generic to x86 architecture
Peter Tyser8d321b82010-04-12 22:28:21 -0500148/api Machine/arch independent API for external apps
149/board Board dependent files
Xu Ziyuan740f7e52016-08-26 19:54:49 +0800150/cmd U-Boot commands functions
Peter Tyser8d321b82010-04-12 22:28:21 -0500151/common Misc architecture independent functions
Robert P. J. Day7207b362015-12-19 07:16:10 -0500152/configs Board default configuration files
Peter Tyser8d321b82010-04-12 22:28:21 -0500153/disk Code for disk drive partition handling
154/doc Documentation (don't expect too much)
155/drivers Commonly used device drivers
Robert P. J. Day33c77312013-09-15 18:34:15 -0400156/dts Contains Makefile for building internal U-Boot fdt.
Peter Tyser8d321b82010-04-12 22:28:21 -0500157/examples Example code for standalone applications, etc.
158/fs Filesystem code (cramfs, ext2, jffs2, etc.)
159/include Header Files
Robert P. J. Day7207b362015-12-19 07:16:10 -0500160/lib Library routines generic to all architectures
161/Licenses Various license files
Peter Tyser8d321b82010-04-12 22:28:21 -0500162/net Networking code
163/post Power On Self Test
Robert P. J. Day7207b362015-12-19 07:16:10 -0500164/scripts Various build scripts and Makefiles
165/test Various unit test files
Peter Tyser8d321b82010-04-12 22:28:21 -0500166/tools Tools to build S-Record or U-Boot images, etc.
wdenkc6097192002-11-03 00:24:07 +0000167
wdenkc6097192002-11-03 00:24:07 +0000168Software Configuration:
169=======================
170
171Configuration is usually done using C preprocessor defines; the
172rationale behind that is to avoid dead code whenever possible.
173
174There are two classes of configuration variables:
175
176* Configuration _OPTIONS_:
177 These are selectable by the user and have names beginning with
178 "CONFIG_".
179
180* Configuration _SETTINGS_:
181 These depend on the hardware etc. and should not be meddled with if
182 you don't know what you're doing; they have names beginning with
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +0200183 "CONFIG_SYS_".
wdenkc6097192002-11-03 00:24:07 +0000184
Robert P. J. Day7207b362015-12-19 07:16:10 -0500185Previously, all configuration was done by hand, which involved creating
186symbolic links and editing configuration files manually. More recently,
187U-Boot has added the Kbuild infrastructure used by the Linux kernel,
188allowing you to use the "make menuconfig" command to configure your
189build.
wdenkc6097192002-11-03 00:24:07 +0000190
191
192Selection of Processor Architecture and Board Type:
193---------------------------------------------------
194
195For all supported boards there are ready-to-use default
Holger Freytherab584d62014-08-04 09:26:05 +0200196configurations available; just type "make <board_name>_defconfig".
wdenkc6097192002-11-03 00:24:07 +0000197
198Example: For a TQM823L module type:
199
200 cd u-boot
Holger Freytherab584d62014-08-04 09:26:05 +0200201 make TQM823L_defconfig
wdenkc6097192002-11-03 00:24:07 +0000202
Robert P. J. Day7207b362015-12-19 07:16:10 -0500203Note: If you're looking for the default configuration file for a board
204you're sure used to be there but is now missing, check the file
205doc/README.scrapyard for a list of no longer supported boards.
wdenkc6097192002-11-03 00:24:07 +0000206
Simon Glass75b3c3a2014-03-22 17:12:59 -0600207Sandbox Environment:
208--------------------
209
210U-Boot can be built natively to run on a Linux host using the 'sandbox'
211board. This allows feature development which is not board- or architecture-
212specific to be undertaken on a native platform. The sandbox is also used to
213run some of U-Boot's tests.
214
Keerthy5917d0b2019-07-29 13:52:04 +0530215See doc/arch/index.rst for more details.
Simon Glass75b3c3a2014-03-22 17:12:59 -0600216
217
Simon Glassdb910352015-03-03 08:03:00 -0700218Board Initialisation Flow:
219--------------------------
220
221This is the intended start-up flow for boards. This should apply for both
Robert P. J. Day7207b362015-12-19 07:16:10 -0500222SPL and U-Boot proper (i.e. they both follow the same rules).
Simon Glassdb910352015-03-03 08:03:00 -0700223
Robert P. J. Day7207b362015-12-19 07:16:10 -0500224Note: "SPL" stands for "Secondary Program Loader," which is explained in
225more detail later in this file.
226
227At present, SPL mostly uses a separate code path, but the function names
228and roles of each function are the same. Some boards or architectures
229may not conform to this. At least most ARM boards which use
230CONFIG_SPL_FRAMEWORK conform to this.
231
232Execution typically starts with an architecture-specific (and possibly
233CPU-specific) start.S file, such as:
234
235 - arch/arm/cpu/armv7/start.S
236 - arch/powerpc/cpu/mpc83xx/start.S
237 - arch/mips/cpu/start.S
238
239and so on. From there, three functions are called; the purpose and
240limitations of each of these functions are described below.
Simon Glassdb910352015-03-03 08:03:00 -0700241
242lowlevel_init():
243 - purpose: essential init to permit execution to reach board_init_f()
244 - no global_data or BSS
245 - there is no stack (ARMv7 may have one but it will soon be removed)
246 - must not set up SDRAM or use console
247 - must only do the bare minimum to allow execution to continue to
248 board_init_f()
249 - this is almost never needed
250 - return normally from this function
251
252board_init_f():
253 - purpose: set up the machine ready for running board_init_r():
254 i.e. SDRAM and serial UART
255 - global_data is available
256 - stack is in SRAM
257 - BSS is not available, so you cannot use global/static variables,
258 only stack variables and global_data
259
260 Non-SPL-specific notes:
261 - dram_init() is called to set up DRAM. If already done in SPL this
262 can do nothing
263
264 SPL-specific notes:
265 - you can override the entire board_init_f() function with your own
266 version as needed.
267 - preloader_console_init() can be called here in extremis
268 - should set up SDRAM, and anything needed to make the UART work
269 - these is no need to clear BSS, it will be done by crt0.S
Andreas Dannenberg14254652019-08-08 12:54:49 -0500270 - for specific scenarios on certain architectures an early BSS *can*
271 be made available (via CONFIG_SPL_EARLY_BSS by moving the clearing
272 of BSS prior to entering board_init_f()) but doing so is discouraged.
273 Instead it is strongly recommended to architect any code changes
274 or additions such to not depend on the availability of BSS during
275 board_init_f() as indicated in other sections of this README to
276 maintain compatibility and consistency across the entire code base.
Simon Glassdb910352015-03-03 08:03:00 -0700277 - must return normally from this function (don't call board_init_r()
278 directly)
279
280Here the BSS is cleared. For SPL, if CONFIG_SPL_STACK_R is defined, then at
281this point the stack and global_data are relocated to below
282CONFIG_SPL_STACK_R_ADDR. For non-SPL, U-Boot is relocated to run at the top of
283memory.
284
285board_init_r():
286 - purpose: main execution, common code
287 - global_data is available
288 - SDRAM is available
289 - BSS is available, all static/global variables can be used
290 - execution eventually continues to main_loop()
291
292 Non-SPL-specific notes:
293 - U-Boot is relocated to the top of memory and is now running from
294 there.
295
296 SPL-specific notes:
297 - stack is optionally in SDRAM, if CONFIG_SPL_STACK_R is defined and
298 CONFIG_SPL_STACK_R_ADDR points into SDRAM
299 - preloader_console_init() can be called here - typically this is
Ley Foon Tan0680f1b2017-05-03 17:13:32 +0800300 done by selecting CONFIG_SPL_BOARD_INIT and then supplying a
Simon Glassdb910352015-03-03 08:03:00 -0700301 spl_board_init() function containing this call
302 - loads U-Boot or (in falcon mode) Linux
303
304
305
wdenkc6097192002-11-03 00:24:07 +0000306Configuration Options:
307----------------------
308
309Configuration depends on the combination of board and CPU type; all
310such information is kept in a configuration file
311"include/configs/<board_name>.h".
312
313Example: For a TQM823L module, all configuration settings are in
314"include/configs/TQM823L.h".
315
316
wdenk7f6c2cb2002-11-10 22:06:23 +0000317Many of the options are named exactly as the corresponding Linux
318kernel configuration options. The intention is to make it easier to
319build a config tool - later.
320
Ashish Kumar63b23162017-08-11 11:09:14 +0530321- ARM Platform Bus Type(CCI):
322 CoreLink Cache Coherent Interconnect (CCI) is ARM BUS which
323 provides full cache coherency between two clusters of multi-core
324 CPUs and I/O coherency for devices and I/O masters
325
326 CONFIG_SYS_FSL_HAS_CCI400
327
328 Defined For SoC that has cache coherent interconnect
329 CCN-400
wdenk7f6c2cb2002-11-10 22:06:23 +0000330
Ashish Kumarc055cee2017-08-18 10:54:36 +0530331 CONFIG_SYS_FSL_HAS_CCN504
332
333 Defined for SoC that has cache coherent interconnect CCN-504
334
wdenkc6097192002-11-03 00:24:07 +0000335The following options need to be configured:
336
Kim Phillips26281142007-08-10 13:28:25 -0500337- CPU Type: Define exactly one, e.g. CONFIG_MPC85XX.
wdenkc6097192002-11-03 00:24:07 +0000338
Kim Phillips26281142007-08-10 13:28:25 -0500339- Board Type: Define exactly one, e.g. CONFIG_MPC8540ADS.
Wolfgang Denk6ccec442006-10-24 14:42:37 +0200340
Kumar Gala66412c62011-02-18 05:40:54 -0600341- 85xx CPU Options:
York Sunffd06e02012-10-08 07:44:30 +0000342 CONFIG_SYS_PPC64
343
344 Specifies that the core is a 64-bit PowerPC implementation (implements
345 the "64" category of the Power ISA). This is necessary for ePAPR
346 compliance, among other possible reasons.
347
Kumar Gala66412c62011-02-18 05:40:54 -0600348 CONFIG_SYS_FSL_TBCLK_DIV
349
350 Defines the core time base clock divider ratio compared to the
351 system clock. On most PQ3 devices this is 8, on newer QorIQ
352 devices it can be 16 or 32. The ratio varies from SoC to Soc.
353
Kumar Gala8f290842011-05-20 00:39:21 -0500354 CONFIG_SYS_FSL_PCIE_COMPAT
355
356 Defines the string to utilize when trying to match PCIe device
357 tree nodes for the given platform.
358
Scott Wood33eee332012-08-14 10:14:53 +0000359 CONFIG_SYS_FSL_ERRATUM_A004510
360
361 Enables a workaround for erratum A004510. If set,
362 then CONFIG_SYS_FSL_ERRATUM_A004510_SVR_REV and
363 CONFIG_SYS_FSL_CORENET_SNOOPVEC_COREONLY must be set.
364
365 CONFIG_SYS_FSL_ERRATUM_A004510_SVR_REV
366 CONFIG_SYS_FSL_ERRATUM_A004510_SVR_REV2 (optional)
367
368 Defines one or two SoC revisions (low 8 bits of SVR)
369 for which the A004510 workaround should be applied.
370
371 The rest of SVR is either not relevant to the decision
372 of whether the erratum is present (e.g. p2040 versus
373 p2041) or is implied by the build target, which controls
374 whether CONFIG_SYS_FSL_ERRATUM_A004510 is set.
375
376 See Freescale App Note 4493 for more information about
377 this erratum.
378
Prabhakar Kushwaha74fa22e2013-04-16 13:27:44 +0530379 CONFIG_A003399_NOR_WORKAROUND
380 Enables a workaround for IFC erratum A003399. It is only
Jeremiah Mahlerb445bbb2015-01-04 18:56:50 -0800381 required during NOR boot.
Prabhakar Kushwaha74fa22e2013-04-16 13:27:44 +0530382
Prabhakar Kushwaha9f074e62014-10-29 22:33:09 +0530383 CONFIG_A008044_WORKAROUND
384 Enables a workaround for T1040/T1042 erratum A008044. It is only
Jeremiah Mahlerb445bbb2015-01-04 18:56:50 -0800385 required during NAND boot and valid for Rev 1.0 SoC revision
Prabhakar Kushwaha9f074e62014-10-29 22:33:09 +0530386
Scott Wood33eee332012-08-14 10:14:53 +0000387 CONFIG_SYS_FSL_CORENET_SNOOPVEC_COREONLY
388
389 This is the value to write into CCSR offset 0x18600
390 according to the A004510 workaround.
391
Priyanka Jain64501c62013-07-02 09:21:04 +0530392 CONFIG_SYS_FSL_DSP_DDR_ADDR
393 This value denotes start offset of DDR memory which is
394 connected exclusively to the DSP cores.
395
Priyanka Jain765b0bd2013-04-04 09:31:54 +0530396 CONFIG_SYS_FSL_DSP_M2_RAM_ADDR
397 This value denotes start offset of M2 memory
398 which is directly connected to the DSP core.
399
Priyanka Jain64501c62013-07-02 09:21:04 +0530400 CONFIG_SYS_FSL_DSP_M3_RAM_ADDR
401 This value denotes start offset of M3 memory which is directly
402 connected to the DSP core.
403
Priyanka Jain765b0bd2013-04-04 09:31:54 +0530404 CONFIG_SYS_FSL_DSP_CCSRBAR_DEFAULT
405 This value denotes start offset of DSP CCSR space.
406
Priyanka Jainb1359912013-12-17 14:25:52 +0530407 CONFIG_SYS_FSL_SINGLE_SOURCE_CLK
408 Single Source Clock is clocking mode present in some of FSL SoC's.
409 In this mode, a single differential clock is used to supply
410 clocks to the sysclock, ddrclock and usbclock.
411
Aneesh Bansalfb4a2402014-03-18 23:40:26 +0530412 CONFIG_SYS_CPC_REINIT_F
413 This CONFIG is defined when the CPC is configured as SRAM at the
Bin Menga1875592016-02-05 19:30:11 -0800414 time of U-Boot entry and is required to be re-initialized.
Aneesh Bansalfb4a2402014-03-18 23:40:26 +0530415
Tang Yuantianaade2002014-04-17 15:33:46 +0800416 CONFIG_DEEP_SLEEP
Jeremiah Mahlerb445bbb2015-01-04 18:56:50 -0800417 Indicates this SoC supports deep sleep feature. If deep sleep is
Tang Yuantianaade2002014-04-17 15:33:46 +0800418 supported, core will start to execute uboot when wakes up.
419
Daniel Schwierzeck6cb461b2012-04-02 02:57:56 +0000420- Generic CPU options:
421 CONFIG_SYS_BIG_ENDIAN, CONFIG_SYS_LITTLE_ENDIAN
422
423 Defines the endianess of the CPU. Implementation of those
424 values is arch specific.
425
York Sun5614e712013-09-30 09:22:09 -0700426 CONFIG_SYS_FSL_DDR
427 Freescale DDR driver in use. This type of DDR controller is
428 found in mpc83xx, mpc85xx, mpc86xx as well as some ARM core
429 SoCs.
430
431 CONFIG_SYS_FSL_DDR_ADDR
432 Freescale DDR memory-mapped register base.
433
434 CONFIG_SYS_FSL_DDR_EMU
435 Specify emulator support for DDR. Some DDR features such as
436 deskew training are not available.
437
438 CONFIG_SYS_FSL_DDRC_GEN1
439 Freescale DDR1 controller.
440
441 CONFIG_SYS_FSL_DDRC_GEN2
442 Freescale DDR2 controller.
443
444 CONFIG_SYS_FSL_DDRC_GEN3
445 Freescale DDR3 controller.
446
York Sun34e026f2014-03-27 17:54:47 -0700447 CONFIG_SYS_FSL_DDRC_GEN4
448 Freescale DDR4 controller.
449
York Sun9ac4ffb2013-09-30 14:20:51 -0700450 CONFIG_SYS_FSL_DDRC_ARM_GEN3
451 Freescale DDR3 controller for ARM-based SoCs.
452
York Sun5614e712013-09-30 09:22:09 -0700453 CONFIG_SYS_FSL_DDR1
454 Board config to use DDR1. It can be enabled for SoCs with
455 Freescale DDR1 or DDR2 controllers, depending on the board
456 implemetation.
457
458 CONFIG_SYS_FSL_DDR2
Robert P. J. Day62a3b7d2016-07-15 13:44:45 -0400459 Board config to use DDR2. It can be enabled for SoCs with
York Sun5614e712013-09-30 09:22:09 -0700460 Freescale DDR2 or DDR3 controllers, depending on the board
461 implementation.
462
463 CONFIG_SYS_FSL_DDR3
464 Board config to use DDR3. It can be enabled for SoCs with
York Sun34e026f2014-03-27 17:54:47 -0700465 Freescale DDR3 or DDR3L controllers.
466
467 CONFIG_SYS_FSL_DDR3L
468 Board config to use DDR3L. It can be enabled for SoCs with
469 DDR3L controllers.
470
471 CONFIG_SYS_FSL_DDR4
472 Board config to use DDR4. It can be enabled for SoCs with
473 DDR4 controllers.
York Sun5614e712013-09-30 09:22:09 -0700474
Prabhakar Kushwaha1b4175d2014-01-18 12:28:30 +0530475 CONFIG_SYS_FSL_IFC_BE
476 Defines the IFC controller register space as Big Endian
477
478 CONFIG_SYS_FSL_IFC_LE
479 Defines the IFC controller register space as Little Endian
480
Prabhakar Kushwaha1c407072017-02-02 15:01:26 +0530481 CONFIG_SYS_FSL_IFC_CLK_DIV
482 Defines divider of platform clock(clock input to IFC controller).
483
Prabhakar Kushwahaadd63f92017-02-02 15:02:00 +0530484 CONFIG_SYS_FSL_LBC_CLK_DIV
485 Defines divider of platform clock(clock input to eLBC controller).
486
Prabhakar Kushwaha690e4252014-01-13 11:28:04 +0530487 CONFIG_SYS_FSL_PBL_PBI
488 It enables addition of RCW (Power on reset configuration) in built image.
489 Please refer doc/README.pblimage for more details
490
491 CONFIG_SYS_FSL_PBL_RCW
492 It adds PBI(pre-boot instructions) commands in u-boot build image.
493 PBI commands can be used to configure SoC before it starts the execution.
494 Please refer doc/README.pblimage for more details
495
York Sun4e5b1bd2014-02-10 13:59:42 -0800496 CONFIG_SYS_FSL_DDR_BE
497 Defines the DDR controller register space as Big Endian
498
499 CONFIG_SYS_FSL_DDR_LE
500 Defines the DDR controller register space as Little Endian
501
York Sun6b9e3092014-02-10 13:59:43 -0800502 CONFIG_SYS_FSL_DDR_SDRAM_BASE_PHY
503 Physical address from the view of DDR controllers. It is the
504 same as CONFIG_SYS_DDR_SDRAM_BASE for all Power SoCs. But
505 it could be different for ARM SoCs.
506
York Sun6b1e1252014-02-10 13:59:44 -0800507 CONFIG_SYS_FSL_DDR_INTLV_256B
508 DDR controller interleaving on 256-byte. This is a special
509 interleaving mode, handled by Dickens for Freescale layerscape
510 SoCs with ARM core.
511
York Sun1d71efb2014-08-01 15:51:00 -0700512 CONFIG_SYS_FSL_DDR_MAIN_NUM_CTRLS
513 Number of controllers used as main memory.
514
515 CONFIG_SYS_FSL_OTHER_DDR_NUM_CTRLS
516 Number of controllers used for other than main memory.
517
Prabhakar Kushwaha44937212015-11-09 16:42:07 +0530518 CONFIG_SYS_FSL_HAS_DP_DDR
519 Defines the SoC has DP-DDR used for DPAA.
520
Ruchika Gupta028dbb82014-09-09 11:50:31 +0530521 CONFIG_SYS_FSL_SEC_BE
522 Defines the SEC controller register space as Big Endian
523
524 CONFIG_SYS_FSL_SEC_LE
525 Defines the SEC controller register space as Little Endian
526
Daniel Schwierzeck92bbd642011-07-27 13:22:39 +0200527- MIPS CPU options:
528 CONFIG_SYS_INIT_SP_OFFSET
529
530 Offset relative to CONFIG_SYS_SDRAM_BASE for initial stack
531 pointer. This is needed for the temporary stack before
532 relocation.
533
Daniel Schwierzeck92bbd642011-07-27 13:22:39 +0200534 CONFIG_XWAY_SWAP_BYTES
535
536 Enable compilation of tools/xway-swap-bytes needed for Lantiq
537 XWAY SoCs for booting from NOR flash. The U-Boot image needs to
538 be swapped if a flash programmer is used.
539
Christian Rieschb67d8812012-02-02 00:44:39 +0000540- ARM options:
541 CONFIG_SYS_EXCEPTION_VECTORS_HIGH
542
543 Select high exception vectors of the ARM core, e.g., do not
544 clear the V bit of the c1 register of CP15.
545
York Sun207774b2015-03-20 19:28:08 -0700546 COUNTER_FREQUENCY
547 Generic timer clock source frequency.
548
549 COUNTER_FREQUENCY_REAL
550 Generic timer clock source frequency if the real clock is
551 different from COUNTER_FREQUENCY, and can only be determined
552 at run time.
553
Stephen Warren73c38932015-01-19 16:25:52 -0700554- Tegra SoC options:
555 CONFIG_TEGRA_SUPPORT_NON_SECURE
556
557 Support executing U-Boot in non-secure (NS) mode. Certain
558 impossible actions will be skipped if the CPU is in NS mode,
559 such as ARM architectural timer initialization.
560
wdenk5da627a2003-10-09 20:09:04 +0000561- Linux Kernel Interface:
wdenk5da627a2003-10-09 20:09:04 +0000562 CONFIG_MEMSIZE_IN_BYTES [relevant for MIPS only]
563
Jeremiah Mahlerb445bbb2015-01-04 18:56:50 -0800564 When transferring memsize parameter to Linux, some versions
wdenk5da627a2003-10-09 20:09:04 +0000565 expect it to be in bytes, others in MB.
566 Define CONFIG_MEMSIZE_IN_BYTES to make it in bytes.
567
Gerald Van Barenfec6d9e2008-06-03 20:34:45 -0400568 CONFIG_OF_LIBFDT
Wolfgang Denkf57f70a2005-10-13 01:45:54 +0200569
570 New kernel versions are expecting firmware settings to be
Gerald Van Baren213bf8c2007-03-31 12:23:51 -0400571 passed using flattened device trees (based on open firmware
572 concepts).
573
574 CONFIG_OF_LIBFDT
575 * New libfdt-based support
576 * Adds the "fdt" command
Kim Phillips3bb342f2007-08-10 14:34:14 -0500577 * The bootm command automatically updates the fdt
Gerald Van Baren213bf8c2007-03-31 12:23:51 -0400578
Wolfgang Denkf57f70a2005-10-13 01:45:54 +0200579 OF_TBCLK - The timebase frequency.
Kumar Galac2871f02006-01-11 13:59:02 -0600580 OF_STDOUT_PATH - The path to the console device
Wolfgang Denkf57f70a2005-10-13 01:45:54 +0200581
Marcel Ziswiler11ccc332008-07-09 08:17:15 +0200582 boards with QUICC Engines require OF_QE to set UCC MAC
583 addresses
Kim Phillips3bb342f2007-08-10 14:34:14 -0500584
Kumar Gala4e253132006-01-11 13:54:17 -0600585 CONFIG_OF_BOARD_SETUP
586
587 Board code has addition modification that it wants to make
588 to the flat device tree before handing it off to the kernel
wdenk6705d812004-08-02 23:22:59 +0000589
Simon Glassc654b512014-10-23 18:58:54 -0600590 CONFIG_OF_SYSTEM_SETUP
591
592 Other code has addition modification that it wants to make
593 to the flat device tree before handing it off to the kernel.
594 This causes ft_system_setup() to be called before booting
595 the kernel.
596
Heiko Schocher3887c3f2009-09-23 07:56:08 +0200597 CONFIG_OF_IDE_FIXUP
598
599 U-Boot can detect if an IDE device is present or not.
600 If not, and this new config option is activated, U-Boot
601 removes the ATA node from the DTS before booting Linux,
602 so the Linux IDE driver does not probe the device and
603 crash. This is needed for buggy hardware (uc101) where
604 no pull down resistor is connected to the signal IDE5V_DD7.
605
Igor Grinberg7eb29392011-07-14 05:45:07 +0000606 CONFIG_MACH_TYPE [relevant for ARM only][mandatory]
607
608 This setting is mandatory for all boards that have only one
609 machine type and must be used to specify the machine type
610 number as it appears in the ARM machine registry
611 (see http://www.arm.linux.org.uk/developer/machines/).
612 Only boards that have multiple machine types supported
613 in a single configuration file and the machine type is
614 runtime discoverable, do not have to use this setting.
615
Niklaus Giger0b2f4ec2008-11-03 22:13:47 +0100616- vxWorks boot parameters:
617
618 bootvx constructs a valid bootline using the following
Bin Meng9e98b7e2015-10-07 20:19:17 -0700619 environments variables: bootdev, bootfile, ipaddr, netmask,
620 serverip, gatewayip, hostname, othbootargs.
Niklaus Giger0b2f4ec2008-11-03 22:13:47 +0100621 It loads the vxWorks image pointed bootfile.
622
Niklaus Giger0b2f4ec2008-11-03 22:13:47 +0100623 Note: If a "bootargs" environment is defined, it will overwride
624 the defaults discussed just above.
625
Aneesh V2c451f72011-06-16 23:30:47 +0000626- Cache Configuration:
Aneesh V2c451f72011-06-16 23:30:47 +0000627 CONFIG_SYS_L2CACHE_OFF- Do not enable L2 cache in U-Boot
628
Aneesh V93bc2192011-06-16 23:30:51 +0000629- Cache Configuration for ARM:
630 CONFIG_SYS_L2_PL310 - Enable support for ARM PL310 L2 cache
631 controller
632 CONFIG_SYS_PL310_BASE - Physical base address of PL310
633 controller register space
634
wdenk6705d812004-08-02 23:22:59 +0000635- Serial Ports:
Andreas Engel48d01922008-09-08 14:30:53 +0200636 CONFIG_PL010_SERIAL
wdenk6705d812004-08-02 23:22:59 +0000637
638 Define this if you want support for Amba PrimeCell PL010 UARTs.
639
Andreas Engel48d01922008-09-08 14:30:53 +0200640 CONFIG_PL011_SERIAL
wdenk6705d812004-08-02 23:22:59 +0000641
642 Define this if you want support for Amba PrimeCell PL011 UARTs.
643
644 CONFIG_PL011_CLOCK
645
646 If you have Amba PrimeCell PL011 UARTs, set this variable to
647 the clock speed of the UARTs.
648
649 CONFIG_PL01x_PORTS
650
651 If you have Amba PrimeCell PL010 or PL011 UARTs on your board,
652 define this to a list of base addresses for each (supported)
653 port. See e.g. include/configs/versatile.h
654
Karicheri, Muralidharand57dee52014-04-09 15:38:46 -0400655 CONFIG_SERIAL_HW_FLOW_CONTROL
656
657 Define this variable to enable hw flow control in serial driver.
658 Current user of this option is drivers/serial/nsl16550.c driver
wdenk6705d812004-08-02 23:22:59 +0000659
wdenkc6097192002-11-03 00:24:07 +0000660- Autoboot Command:
661 CONFIG_BOOTCOMMAND
662 Only needed when CONFIG_BOOTDELAY is enabled;
663 define a command string that is automatically executed
664 when no character is read on the console interface
665 within "Boot Delay" after reset.
666
wdenkc6097192002-11-03 00:24:07 +0000667 CONFIG_RAMBOOT and CONFIG_NFSBOOT
wdenk43d96162003-03-06 00:02:04 +0000668 The value of these goes into the environment as
669 "ramboot" and "nfsboot" respectively, and can be used
670 as a convenience, when switching between booting from
Marcel Ziswiler11ccc332008-07-09 08:17:15 +0200671 RAM and NFS.
wdenkc6097192002-11-03 00:24:07 +0000672
wdenkc6097192002-11-03 00:24:07 +0000673- Serial Download Echo Mode:
674 CONFIG_LOADS_ECHO
675 If defined to 1, all characters received during a
676 serial download (using the "loads" command) are
677 echoed back. This might be needed by some terminal
678 emulations (like "cu"), but may as well just take
679 time on others. This setting #define's the initial
680 value of the "loads_echo" environment variable.
681
Jon Loeliger602ad3b2007-06-11 19:03:39 -0500682- Kgdb Serial Baudrate: (if CONFIG_CMD_KGDB is defined)
wdenkc6097192002-11-03 00:24:07 +0000683 CONFIG_KGDB_BAUDRATE
684 Select one of the baudrates listed in
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +0200685 CONFIG_SYS_BAUDRATE_TABLE, see below.
wdenkc6097192002-11-03 00:24:07 +0000686
Simon Glass302a6482016-03-13 19:07:28 -0600687- Removal of commands
688 If no commands are needed to boot, you can disable
689 CONFIG_CMDLINE to remove them. In this case, the command line
690 will not be available, and when U-Boot wants to execute the
691 boot command (on start-up) it will call board_run_command()
692 instead. This can reduce image size significantly for very
693 simple boot procedures.
694
Wolfgang Denka5ecbe62013-03-23 23:50:31 +0000695- Regular expression support:
696 CONFIG_REGEX
Wolfgang Denk93e14592013-10-04 17:43:24 +0200697 If this variable is defined, U-Boot is linked against
698 the SLRE (Super Light Regular Expression) library,
699 which adds regex support to some commands, as for
700 example "env grep" and "setexpr".
Wolfgang Denka5ecbe62013-03-23 23:50:31 +0000701
Simon Glass45ba8072011-10-15 05:48:20 +0000702- Device tree:
703 CONFIG_OF_CONTROL
704 If this variable is defined, U-Boot will use a device tree
705 to configure its devices, instead of relying on statically
706 compiled #defines in the board file. This option is
707 experimental and only available on a few boards. The device
708 tree is available in the global data as gd->fdt_blob.
709
Simon Glass2c0f79e2011-10-24 19:15:31 +0000710 U-Boot needs to get its device tree from somewhere. This can
Alex Deymo82f766d2017-04-02 01:25:20 -0700711 be done using one of the three options below:
Simon Glassbbb0b122011-10-15 05:48:21 +0000712
713 CONFIG_OF_EMBED
714 If this variable is defined, U-Boot will embed a device tree
715 binary in its image. This device tree file should be in the
716 board directory and called <soc>-<board>.dts. The binary file
717 is then picked up in board_init_f() and made available through
Nobuhiro Iwamatsueb3eb602017-08-26 07:34:14 +0900718 the global data structure as gd->fdt_blob.
Simon Glass45ba8072011-10-15 05:48:20 +0000719
Simon Glass2c0f79e2011-10-24 19:15:31 +0000720 CONFIG_OF_SEPARATE
721 If this variable is defined, U-Boot will build a device tree
722 binary. It will be called u-boot.dtb. Architecture-specific
723 code will locate it at run-time. Generally this works by:
724
725 cat u-boot.bin u-boot.dtb >image.bin
726
727 and in fact, U-Boot does this for you, creating a file called
728 u-boot-dtb.bin which is useful in the common case. You can
729 still use the individual files if you need something more
730 exotic.
731
Alex Deymo82f766d2017-04-02 01:25:20 -0700732 CONFIG_OF_BOARD
733 If this variable is defined, U-Boot will use the device tree
734 provided by the board at runtime instead of embedding one with
735 the image. Only boards defining board_fdt_blob_setup() support
736 this option (see include/fdtdec.h file).
737
wdenkc6097192002-11-03 00:24:07 +0000738- Watchdog:
739 CONFIG_WATCHDOG
740 If this variable is defined, it enables watchdog
Detlev Zundel6abe6fb2011-04-27 05:25:59 +0000741 support for the SoC. There must be support in the SoC
Christophe Leroy907208c2017-07-06 10:23:22 +0200742 specific code for a watchdog. For the 8xx
743 CPUs, the SIU Watchdog feature is enabled in the SYPCR
744 register. When supported for a specific SoC is
745 available, then no further board specific code should
746 be needed to use it.
Detlev Zundel6abe6fb2011-04-27 05:25:59 +0000747
748 CONFIG_HW_WATCHDOG
749 When using a watchdog circuitry external to the used
750 SoC, then define this variable and provide board
751 specific code for the "hw_watchdog_reset" function.
wdenkc6097192002-11-03 00:24:07 +0000752
753- Real-Time Clock:
754
Jon Loeliger602ad3b2007-06-11 19:03:39 -0500755 When CONFIG_CMD_DATE is selected, the type of the RTC
wdenkc6097192002-11-03 00:24:07 +0000756 has to be selected, too. Define exactly one of the
757 following options:
758
wdenkc6097192002-11-03 00:24:07 +0000759 CONFIG_RTC_PCF8563 - use Philips PCF8563 RTC
Fabio Estevam4e8b7542011-10-24 06:44:15 +0000760 CONFIG_RTC_MC13XXX - use MC13783 or MC13892 RTC
wdenkc6097192002-11-03 00:24:07 +0000761 CONFIG_RTC_MC146818 - use MC146818 RTC
wdenk1cb8e982003-03-06 21:55:29 +0000762 CONFIG_RTC_DS1307 - use Maxim, Inc. DS1307 RTC
wdenkc6097192002-11-03 00:24:07 +0000763 CONFIG_RTC_DS1337 - use Maxim, Inc. DS1337 RTC
wdenk7f70e852003-05-20 14:25:27 +0000764 CONFIG_RTC_DS1338 - use Maxim, Inc. DS1338 RTC
Markus Niebel412921d2014-07-21 11:06:16 +0200765 CONFIG_RTC_DS1339 - use Maxim, Inc. DS1339 RTC
wdenk3bac3512003-03-12 10:41:04 +0000766 CONFIG_RTC_DS164x - use Dallas DS164x RTC
Tor Krill9536dfc2008-03-15 15:40:26 +0100767 CONFIG_RTC_ISL1208 - use Intersil ISL1208 RTC
wdenk4c0d4c32004-06-09 17:34:58 +0000768 CONFIG_RTC_MAX6900 - use Maxim, Inc. MAX6900 RTC
Chris Packham2bd3cab2017-05-30 12:03:33 +1200769 CONFIG_RTC_DS1337_NOOSC - Turn off the OSC output for DS1337
Heiko Schocher71d19f32011-03-28 09:24:22 +0200770 CONFIG_SYS_RV3029_TCR - enable trickle charger on
771 RV3029 RTC.
wdenkc6097192002-11-03 00:24:07 +0000772
wdenkb37c7e52003-06-30 16:24:52 +0000773 Note that if the RTC uses I2C, then the I2C interface
774 must also be configured. See I2C Support, below.
775
Peter Tysere92739d2008-12-17 16:36:21 -0600776- GPIO Support:
777 CONFIG_PCA953X - use NXP's PCA953X series I2C GPIO
Peter Tysere92739d2008-12-17 16:36:21 -0600778
Chris Packham5dec49c2010-12-19 10:12:13 +0000779 The CONFIG_SYS_I2C_PCA953X_WIDTH option specifies a list of
780 chip-ngpio pairs that tell the PCA953X driver the number of
781 pins supported by a particular chip.
782
Peter Tysere92739d2008-12-17 16:36:21 -0600783 Note that if the GPIO device uses I2C, then the I2C interface
784 must also be configured. See I2C Support, below.
785
Simon Glassaa532332014-06-11 23:29:41 -0600786- I/O tracing:
787 When CONFIG_IO_TRACE is selected, U-Boot intercepts all I/O
788 accesses and can checksum them or write a list of them out
789 to memory. See the 'iotrace' command for details. This is
790 useful for testing device drivers since it can confirm that
791 the driver behaves the same way before and after a code
792 change. Currently this is supported on sandbox and arm. To
793 add support for your architecture, add '#include <iotrace.h>'
794 to the bottom of arch/<arch>/include/asm/io.h and test.
795
796 Example output from the 'iotrace stats' command is below.
797 Note that if the trace buffer is exhausted, the checksum will
798 still continue to operate.
799
800 iotrace is enabled
801 Start: 10000000 (buffer start address)
802 Size: 00010000 (buffer size)
803 Offset: 00000120 (current buffer offset)
804 Output: 10000120 (start + offset)
805 Count: 00000018 (number of trace records)
806 CRC32: 9526fb66 (CRC32 of all trace records)
807
wdenkc6097192002-11-03 00:24:07 +0000808- Timestamp Support:
809
wdenk43d96162003-03-06 00:02:04 +0000810 When CONFIG_TIMESTAMP is selected, the timestamp
811 (date and time) of an image is printed by image
812 commands like bootm or iminfo. This option is
Jon Loeliger602ad3b2007-06-11 19:03:39 -0500813 automatically enabled when you select CONFIG_CMD_DATE .
wdenkc6097192002-11-03 00:24:07 +0000814
Karl O. Pinc923c46f2012-08-16 06:20:15 +0000815- Partition Labels (disklabels) Supported:
816 Zero or more of the following:
817 CONFIG_MAC_PARTITION Apple's MacOS partition table.
Karl O. Pinc923c46f2012-08-16 06:20:15 +0000818 CONFIG_ISO_PARTITION ISO partition table, used on CDROM etc.
819 CONFIG_EFI_PARTITION GPT partition table, common when EFI is the
820 bootloader. Note 2TB partition limit; see
821 disk/part_efi.c
Simon Glassc649e3c2016-05-01 11:36:02 -0600822 CONFIG_SCSI) you must configure support for at
Karl O. Pinc923c46f2012-08-16 06:20:15 +0000823 least one non-MTD partition type as well.
wdenkc6097192002-11-03 00:24:07 +0000824
825- IDE Reset method:
wdenk4d13cba2004-03-14 14:09:05 +0000826 CONFIG_IDE_RESET_ROUTINE - this is defined in several
827 board configurations files but used nowhere!
wdenkc6097192002-11-03 00:24:07 +0000828
wdenk4d13cba2004-03-14 14:09:05 +0000829 CONFIG_IDE_RESET - is this is defined, IDE Reset will
830 be performed by calling the function
831 ide_set_reset(int reset)
832 which has to be defined in a board specific file
wdenkc6097192002-11-03 00:24:07 +0000833
834- ATAPI Support:
835 CONFIG_ATAPI
836
837 Set this to enable ATAPI support.
838
wdenkc40b2952004-03-13 23:29:43 +0000839- LBA48 Support
840 CONFIG_LBA48
841
842 Set this to enable support for disks larger than 137GB
Heiko Schocher4b142fe2009-12-03 11:21:21 +0100843 Also look at CONFIG_SYS_64BIT_LBA.
wdenkc40b2952004-03-13 23:29:43 +0000844 Whithout these , LBA48 support uses 32bit variables and will 'only'
845 support disks up to 2.1TB.
846
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +0200847 CONFIG_SYS_64BIT_LBA:
wdenkc40b2952004-03-13 23:29:43 +0000848 When enabled, makes the IDE subsystem use 64bit sector addresses.
849 Default is 32bit.
850
wdenkc6097192002-11-03 00:24:07 +0000851- SCSI Support:
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +0200852 CONFIG_SYS_SCSI_MAX_LUN [8], CONFIG_SYS_SCSI_MAX_SCSI_ID [7] and
853 CONFIG_SYS_SCSI_MAX_DEVICE [CONFIG_SYS_SCSI_MAX_SCSI_ID *
854 CONFIG_SYS_SCSI_MAX_LUN] can be adjusted to define the
wdenkc6097192002-11-03 00:24:07 +0000855 maximum numbers of LUNs, SCSI ID's and target
856 devices.
wdenkc6097192002-11-03 00:24:07 +0000857
Wolfgang Denk93e14592013-10-04 17:43:24 +0200858 The environment variable 'scsidevs' is set to the number of
859 SCSI devices found during the last scan.
Stefan Reinauer447c0312012-10-29 05:23:48 +0000860
wdenkc6097192002-11-03 00:24:07 +0000861- NETWORK Support (PCI):
wdenk682011f2003-06-03 23:54:09 +0000862 CONFIG_E1000
Kyle Moffettce5207e2011-10-18 11:05:29 +0000863 Support for Intel 8254x/8257x gigabit chips.
864
865 CONFIG_E1000_SPI
866 Utility code for direct access to the SPI bus on Intel 8257x.
867 This does not do anything useful unless you set at least one
868 of CONFIG_CMD_E1000 or CONFIG_E1000_SPI_GENERIC.
869
870 CONFIG_E1000_SPI_GENERIC
871 Allow generic access to the SPI bus on the Intel 8257x, for
872 example with the "sspi" command.
873
wdenkc6097192002-11-03 00:24:07 +0000874 CONFIG_TULIP
875 Support for Digital 2114x chips.
wdenkc6097192002-11-03 00:24:07 +0000876
877 CONFIG_NATSEMI
878 Support for National dp83815 chips.
879
880 CONFIG_NS8382X
881 Support for National dp8382[01] gigabit chips.
882
wdenk45219c42003-05-12 21:50:16 +0000883- NETWORK Support (other):
884
Jens Scharsigc041e9d2010-01-23 12:03:45 +0100885 CONFIG_DRIVER_AT91EMAC
886 Support for AT91RM9200 EMAC.
887
888 CONFIG_RMII
889 Define this to use reduced MII inteface
890
891 CONFIG_DRIVER_AT91EMAC_QUIET
892 If this defined, the driver is quiet.
893 The driver doen't show link status messages.
894
Rob Herringefdd7312011-12-15 11:15:49 +0000895 CONFIG_CALXEDA_XGMAC
896 Support for the Calxeda XGMAC device
897
Ashok3bb46d22012-10-15 06:20:47 +0000898 CONFIG_LAN91C96
wdenk45219c42003-05-12 21:50:16 +0000899 Support for SMSC's LAN91C96 chips.
900
wdenk45219c42003-05-12 21:50:16 +0000901 CONFIG_LAN91C96_USE_32_BIT
902 Define this to enable 32 bit addressing
903
Ashok3bb46d22012-10-15 06:20:47 +0000904 CONFIG_SMC91111
wdenkf39748a2004-06-09 13:37:52 +0000905 Support for SMSC's LAN91C111 chip
906
907 CONFIG_SMC91111_BASE
908 Define this to hold the physical address
909 of the device (I/O space)
910
911 CONFIG_SMC_USE_32_BIT
912 Define this if data bus is 32 bits
913
914 CONFIG_SMC_USE_IOFUNCS
915 Define this to use i/o functions instead of macros
916 (some hardware wont work with macros)
917
Heiko Schocherdc02bad2011-11-15 10:00:04 -0500918 CONFIG_SYS_DAVINCI_EMAC_PHY_COUNT
919 Define this if you have more then 3 PHYs.
920
Macpaul Linb3dbf4a52010-12-21 16:59:46 +0800921 CONFIG_FTGMAC100
922 Support for Faraday's FTGMAC100 Gigabit SoC Ethernet
923
924 CONFIG_FTGMAC100_EGIGA
925 Define this to use GE link update with gigabit PHY.
926 Define this if FTGMAC100 is connected to gigabit PHY.
927 If your system has 10/100 PHY only, it might not occur
928 wrong behavior. Because PHY usually return timeout or
929 useless data when polling gigabit status and gigabit
930 control registers. This behavior won't affect the
931 correctnessof 10/100 link speed update.
932
Yoshihiro Shimoda3d0075f2011-01-27 10:06:03 +0900933 CONFIG_SH_ETHER
934 Support for Renesas on-chip Ethernet controller
935
936 CONFIG_SH_ETHER_USE_PORT
937 Define the number of ports to be used
938
939 CONFIG_SH_ETHER_PHY_ADDR
940 Define the ETH PHY's address
941
Yoshihiro Shimoda68260aa2011-01-27 10:06:08 +0900942 CONFIG_SH_ETHER_CACHE_WRITEBACK
943 If this option is set, the driver enables cache flush.
944
Vadim Bendebury5e124722011-10-17 08:36:14 +0000945- TPM Support:
Che-liang Chiou90899cc2013-04-12 11:04:34 +0000946 CONFIG_TPM
947 Support TPM devices.
948
Christophe Ricard0766ad22015-10-06 22:54:41 +0200949 CONFIG_TPM_TIS_INFINEON
950 Support for Infineon i2c bus TPM devices. Only one device
Tom Wai-Hong Tam1b393db2013-04-12 11:04:37 +0000951 per system is supported at this time.
952
Tom Wai-Hong Tam1b393db2013-04-12 11:04:37 +0000953 CONFIG_TPM_TIS_I2C_BURST_LIMITATION
954 Define the burst count bytes upper limit
955
Christophe Ricard3aa74082016-01-21 23:27:13 +0100956 CONFIG_TPM_ST33ZP24
957 Support for STMicroelectronics TPM devices. Requires DM_TPM support.
958
959 CONFIG_TPM_ST33ZP24_I2C
960 Support for STMicroelectronics ST33ZP24 I2C devices.
961 Requires TPM_ST33ZP24 and I2C.
962
Christophe Ricardb75fdc12016-01-21 23:27:14 +0100963 CONFIG_TPM_ST33ZP24_SPI
964 Support for STMicroelectronics ST33ZP24 SPI devices.
965 Requires TPM_ST33ZP24 and SPI.
966
Dirk Eibachc01939c2013-06-26 15:55:15 +0200967 CONFIG_TPM_ATMEL_TWI
968 Support for Atmel TWI TPM device. Requires I2C support.
969
Che-liang Chiou90899cc2013-04-12 11:04:34 +0000970 CONFIG_TPM_TIS_LPC
Vadim Bendebury5e124722011-10-17 08:36:14 +0000971 Support for generic parallel port TPM devices. Only one device
972 per system is supported at this time.
973
974 CONFIG_TPM_TIS_BASE_ADDRESS
975 Base address where the generic TPM device is mapped
976 to. Contemporary x86 systems usually map it at
977 0xfed40000.
978
Reinhard Pfaube6c1522013-06-26 15:55:13 +0200979 CONFIG_TPM
980 Define this to enable the TPM support library which provides
981 functional interfaces to some TPM commands.
982 Requires support for a TPM device.
983
984 CONFIG_TPM_AUTH_SESSIONS
985 Define this to enable authorized functions in the TPM library.
986 Requires CONFIG_TPM and CONFIG_SHA1.
987
wdenkc6097192002-11-03 00:24:07 +0000988- USB Support:
989 At the moment only the UHCI host controller is
Heiko Schocher064b55c2017-06-14 05:49:40 +0200990 supported (PIP405, MIP405); define
wdenkc6097192002-11-03 00:24:07 +0000991 CONFIG_USB_UHCI to enable it.
992 define CONFIG_USB_KEYBOARD to enable the USB Keyboard
wdenk30d56fa2004-10-09 22:44:59 +0000993 and define CONFIG_USB_STORAGE to enable the USB
wdenkc6097192002-11-03 00:24:07 +0000994 storage devices.
995 Note:
996 Supported are USB Keyboards and USB Floppy drives
997 (TEAC FD-05PUB).
wdenk4d13cba2004-03-14 14:09:05 +0000998
Simon Glass9ab4ce22012-02-27 10:52:47 +0000999 CONFIG_USB_EHCI_TXFIFO_THRESH enables setting of the
1000 txfilltuning field in the EHCI controller on reset.
1001
Oleksandr Tymoshenko6e9e0622014-02-01 21:51:25 -07001002 CONFIG_USB_DWC2_REG_ADDR the physical CPU address of the DWC2
1003 HW module registers.
1004
Wolfgang Denk16c8d5e2006-06-14 17:45:53 +02001005- USB Device:
1006 Define the below if you wish to use the USB console.
1007 Once firmware is rebuilt from a serial console issue the
1008 command "setenv stdin usbtty; setenv stdout usbtty" and
Marcel Ziswiler11ccc332008-07-09 08:17:15 +02001009 attach your USB cable. The Unix command "dmesg" should print
Wolfgang Denk16c8d5e2006-06-14 17:45:53 +02001010 it has found a new device. The environment variable usbtty
1011 can be set to gserial or cdc_acm to enable your device to
Wolfgang Denk386eda02006-06-14 18:14:56 +02001012 appear to a USB host as a Linux gserial device or a
Wolfgang Denk16c8d5e2006-06-14 17:45:53 +02001013 Common Device Class Abstract Control Model serial device.
1014 If you select usbtty = gserial you should be able to enumerate
1015 a Linux host by
1016 # modprobe usbserial vendor=0xVendorID product=0xProductID
1017 else if using cdc_acm, simply setting the environment
1018 variable usbtty to be cdc_acm should suffice. The following
1019 might be defined in YourBoardName.h
Wolfgang Denk386eda02006-06-14 18:14:56 +02001020
Wolfgang Denk16c8d5e2006-06-14 17:45:53 +02001021 CONFIG_USB_DEVICE
1022 Define this to build a UDC device
wdenkc6097192002-11-03 00:24:07 +00001023
Wolfgang Denk16c8d5e2006-06-14 17:45:53 +02001024 CONFIG_USB_TTY
1025 Define this to have a tty type of device available to
1026 talk to the UDC device
Wolfgang Denk386eda02006-06-14 18:14:56 +02001027
Vipin KUMARf9da0f82012-03-26 15:38:06 +05301028 CONFIG_USBD_HS
1029 Define this to enable the high speed support for usb
1030 device and usbtty. If this feature is enabled, a routine
1031 int is_usbd_high_speed(void)
1032 also needs to be defined by the driver to dynamically poll
1033 whether the enumeration has succeded at high speed or full
1034 speed.
1035
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02001036 CONFIG_SYS_CONSOLE_IS_IN_ENV
Wolfgang Denk16c8d5e2006-06-14 17:45:53 +02001037 Define this if you want stdin, stdout &/or stderr to
1038 be set to usbtty.
1039
Wolfgang Denk386eda02006-06-14 18:14:56 +02001040 If you have a USB-IF assigned VendorID then you may wish to
Wolfgang Denk16c8d5e2006-06-14 17:45:53 +02001041 define your own vendor specific values either in BoardName.h
Wolfgang Denk386eda02006-06-14 18:14:56 +02001042 or directly in usbd_vendor_info.h. If you don't define
Wolfgang Denk16c8d5e2006-06-14 17:45:53 +02001043 CONFIG_USBD_MANUFACTURER, CONFIG_USBD_PRODUCT_NAME,
1044 CONFIG_USBD_VENDORID and CONFIG_USBD_PRODUCTID, then U-Boot
1045 should pretend to be a Linux device to it's target host.
1046
1047 CONFIG_USBD_MANUFACTURER
1048 Define this string as the name of your company for
1049 - CONFIG_USBD_MANUFACTURER "my company"
Wolfgang Denk386eda02006-06-14 18:14:56 +02001050
Wolfgang Denk16c8d5e2006-06-14 17:45:53 +02001051 CONFIG_USBD_PRODUCT_NAME
1052 Define this string as the name of your product
1053 - CONFIG_USBD_PRODUCT_NAME "acme usb device"
1054
1055 CONFIG_USBD_VENDORID
1056 Define this as your assigned Vendor ID from the USB
1057 Implementors Forum. This *must* be a genuine Vendor ID
1058 to avoid polluting the USB namespace.
1059 - CONFIG_USBD_VENDORID 0xFFFF
Wolfgang Denk386eda02006-06-14 18:14:56 +02001060
Wolfgang Denk16c8d5e2006-06-14 17:45:53 +02001061 CONFIG_USBD_PRODUCTID
1062 Define this as the unique Product ID
1063 for your device
1064 - CONFIG_USBD_PRODUCTID 0xFFFF
wdenkc6097192002-11-03 00:24:07 +00001065
Igor Grinbergd70a5602011-12-12 12:08:35 +02001066- ULPI Layer Support:
1067 The ULPI (UTMI Low Pin (count) Interface) PHYs are supported via
1068 the generic ULPI layer. The generic layer accesses the ULPI PHY
1069 via the platform viewport, so you need both the genric layer and
1070 the viewport enabled. Currently only Chipidea/ARC based
1071 viewport is supported.
1072 To enable the ULPI layer support, define CONFIG_USB_ULPI and
1073 CONFIG_USB_ULPI_VIEWPORT in your board configuration file.
Lucas Stach6d365ea2012-10-01 00:44:35 +02001074 If your ULPI phy needs a different reference clock than the
1075 standard 24 MHz then you have to define CONFIG_ULPI_REF_CLK to
1076 the appropriate value in Hz.
wdenkc6097192002-11-03 00:24:07 +00001077
1078- MMC Support:
1079 The MMC controller on the Intel PXA is supported. To
1080 enable this define CONFIG_MMC. The MMC can be
1081 accessed from the boot prompt by mapping the device
1082 to physical memory similar to flash. Command line is
Jon Loeliger602ad3b2007-06-11 19:03:39 -05001083 enabled with CONFIG_CMD_MMC. The MMC driver also works with
1084 the FAT fs. This is enabled with CONFIG_CMD_FAT.
wdenkc6097192002-11-03 00:24:07 +00001085
Yoshihiro Shimodaafb35662011-07-04 22:21:22 +00001086 CONFIG_SH_MMCIF
1087 Support for Renesas on-chip MMCIF controller
1088
1089 CONFIG_SH_MMCIF_ADDR
1090 Define the base address of MMCIF registers
1091
1092 CONFIG_SH_MMCIF_CLK
1093 Define the clock frequency for MMCIF
1094
Tom Rinib3ba6e92013-03-14 05:32:47 +00001095- USB Device Firmware Update (DFU) class support:
Marek Vasutbb4059a2018-02-16 16:41:18 +01001096 CONFIG_DFU_OVER_USB
Tom Rinib3ba6e92013-03-14 05:32:47 +00001097 This enables the USB portion of the DFU USB class
1098
Pantelis Antoniouc6631762013-03-14 05:32:52 +00001099 CONFIG_DFU_NAND
1100 This enables support for exposing NAND devices via DFU.
1101
Afzal Mohammeda9479f02013-09-18 01:15:24 +05301102 CONFIG_DFU_RAM
1103 This enables support for exposing RAM via DFU.
1104 Note: DFU spec refer to non-volatile memory usage, but
1105 allow usages beyond the scope of spec - here RAM usage,
1106 one that would help mostly the developer.
1107
Heiko Schochere7e75c72013-06-12 06:05:51 +02001108 CONFIG_SYS_DFU_DATA_BUF_SIZE
1109 Dfu transfer uses a buffer before writing data to the
1110 raw storage device. Make the size (in bytes) of this buffer
1111 configurable. The size of this buffer is also configurable
1112 through the "dfu_bufsiz" environment variable.
1113
Pantelis Antoniouea2453d2013-03-14 05:32:48 +00001114 CONFIG_SYS_DFU_MAX_FILE_SIZE
1115 When updating files rather than the raw storage device,
1116 we use a static buffer to copy the file into and then write
1117 the buffer once we've been given the whole file. Define
1118 this to the maximum filesize (in bytes) for the buffer.
1119 Default is 4 MiB if undefined.
1120
Heiko Schocher001a8312014-03-18 08:09:56 +01001121 DFU_DEFAULT_POLL_TIMEOUT
1122 Poll timeout [ms], is the timeout a device can send to the
1123 host. The host must wait for this timeout before sending
1124 a subsequent DFU_GET_STATUS request to the device.
1125
1126 DFU_MANIFEST_POLL_TIMEOUT
1127 Poll timeout [ms], which the device sends to the host when
1128 entering dfuMANIFEST state. Host waits this timeout, before
1129 sending again an USB request to the device.
1130
wdenk6705d812004-08-02 23:22:59 +00001131- Journaling Flash filesystem support:
Simon Glassb2482df2016-10-02 18:00:59 -06001132 CONFIG_JFFS2_NAND
wdenk6705d812004-08-02 23:22:59 +00001133 Define these for a default partition on a NAND device
1134
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02001135 CONFIG_SYS_JFFS2_FIRST_SECTOR,
1136 CONFIG_SYS_JFFS2_FIRST_BANK, CONFIG_SYS_JFFS2_NUM_BANKS
wdenk6705d812004-08-02 23:22:59 +00001137 Define these for a default partition on a NOR device
1138
wdenkc6097192002-11-03 00:24:07 +00001139- Keyboard Support:
Simon Glass39f615e2015-11-11 10:05:47 -07001140 See Kconfig help for available keyboard drivers.
1141
1142 CONFIG_KEYBOARD
1143
1144 Define this to enable a custom keyboard support.
1145 This simply calls drv_keyboard_init() which must be
1146 defined in your board-specific files. This option is deprecated
1147 and is only used by novena. For new boards, use driver model
1148 instead.
wdenkc6097192002-11-03 00:24:07 +00001149
1150- Video support:
Timur Tabi7d3053f2011-02-15 17:09:19 -06001151 CONFIG_FSL_DIU_FB
Wolfgang Denk04e5ae72011-09-11 21:24:09 +02001152 Enable the Freescale DIU video driver. Reference boards for
Timur Tabi7d3053f2011-02-15 17:09:19 -06001153 SOCs that have a DIU should define this macro to enable DIU
1154 support, and should also define these other macros:
1155
1156 CONFIG_SYS_DIU_ADDR
1157 CONFIG_VIDEO
Timur Tabi7d3053f2011-02-15 17:09:19 -06001158 CONFIG_CFB_CONSOLE
1159 CONFIG_VIDEO_SW_CURSOR
1160 CONFIG_VGA_AS_SINGLE_DEVICE
1161 CONFIG_VIDEO_LOGO
1162 CONFIG_VIDEO_BMP_LOGO
1163
Timur Tabiba8e76b2011-04-11 14:18:22 -05001164 The DIU driver will look for the 'video-mode' environment
1165 variable, and if defined, enable the DIU as a console during
Fabio Estevam8eca9432016-04-02 11:53:18 -03001166 boot. See the documentation file doc/README.video for a
Timur Tabiba8e76b2011-04-11 14:18:22 -05001167 description of this variable.
Timur Tabi7d3053f2011-02-15 17:09:19 -06001168
wdenkc6097192002-11-03 00:24:07 +00001169- LCD Support: CONFIG_LCD
1170
1171 Define this to enable LCD support (for output to LCD
1172 display); also select one of the supported displays
1173 by defining one of these:
1174
Stelian Pop39cf4802008-05-09 21:57:18 +02001175 CONFIG_ATMEL_LCD:
1176
1177 HITACHI TX09D70VM1CCA, 3.5", 240x320.
1178
wdenkfd3103b2003-11-25 16:55:19 +00001179 CONFIG_NEC_NL6448AC33:
wdenkc6097192002-11-03 00:24:07 +00001180
wdenkfd3103b2003-11-25 16:55:19 +00001181 NEC NL6448AC33-18. Active, color, single scan.
wdenkc6097192002-11-03 00:24:07 +00001182
wdenkfd3103b2003-11-25 16:55:19 +00001183 CONFIG_NEC_NL6448BC20
wdenkc6097192002-11-03 00:24:07 +00001184
wdenkfd3103b2003-11-25 16:55:19 +00001185 NEC NL6448BC20-08. 6.5", 640x480.
1186 Active, color, single scan.
1187
1188 CONFIG_NEC_NL6448BC33_54
1189
1190 NEC NL6448BC33-54. 10.4", 640x480.
wdenkc6097192002-11-03 00:24:07 +00001191 Active, color, single scan.
1192
1193 CONFIG_SHARP_16x9
1194
1195 Sharp 320x240. Active, color, single scan.
1196 It isn't 16x9, and I am not sure what it is.
1197
1198 CONFIG_SHARP_LQ64D341
1199
1200 Sharp LQ64D341 display, 640x480.
1201 Active, color, single scan.
1202
1203 CONFIG_HLD1045
1204
1205 HLD1045 display, 640x480.
1206 Active, color, single scan.
1207
1208 CONFIG_OPTREX_BW
1209
1210 Optrex CBL50840-2 NF-FW 99 22 M5
1211 or
1212 Hitachi LMG6912RPFC-00T
1213 or
1214 Hitachi SP14Q002
1215
1216 320x240. Black & white.
1217
Simon Glass676d3192012-10-17 13:24:54 +00001218 CONFIG_LCD_ALIGNMENT
1219
Jeremiah Mahlerb445bbb2015-01-04 18:56:50 -08001220 Normally the LCD is page-aligned (typically 4KB). If this is
Simon Glass676d3192012-10-17 13:24:54 +00001221 defined then the LCD will be aligned to this value instead.
1222 For ARM it is sometimes useful to use MMU_SECTION_SIZE
1223 here, since it is cheaper to change data cache settings on
1224 a per-section basis.
1225
1226
Hannes Petermaier604c7d42015-03-27 08:01:38 +01001227 CONFIG_LCD_ROTATION
1228
1229 Sometimes, for example if the display is mounted in portrait
1230 mode or even if it's mounted landscape but rotated by 180degree,
1231 we need to rotate our content of the display relative to the
1232 framebuffer, so that user can read the messages which are
1233 printed out.
1234 Once CONFIG_LCD_ROTATION is defined, the lcd_console will be
1235 initialized with a given rotation from "vl_rot" out of
1236 "vidinfo_t" which is provided by the board specific code.
1237 The value for vl_rot is coded as following (matching to
1238 fbcon=rotate:<n> linux-kernel commandline):
1239 0 = no rotation respectively 0 degree
1240 1 = 90 degree rotation
1241 2 = 180 degree rotation
1242 3 = 270 degree rotation
1243
1244 If CONFIG_LCD_ROTATION is not defined, the console will be
1245 initialized with 0degree rotation.
1246
Tom Wai-Hong Tam45d7f522012-09-28 15:11:16 +00001247 CONFIG_LCD_BMP_RLE8
1248
1249 Support drawing of RLE8-compressed bitmaps on the LCD.
1250
Tom Wai-Hong Tam735987c2012-12-05 14:46:40 +00001251 CONFIG_I2C_EDID
1252
1253 Enables an 'i2c edid' command which can read EDID
1254 information over I2C from an attached LCD display.
1255
wdenk7152b1d2003-09-05 23:19:14 +00001256- Splash Screen Support: CONFIG_SPLASH_SCREEN
wdenkd791b1d2003-04-20 14:04:18 +00001257
wdenk8bde7f72003-06-27 21:31:46 +00001258 If this option is set, the environment is checked for
1259 a variable "splashimage". If found, the usual display
1260 of logo, copyright and system information on the LCD
wdenke94d2cd2004-06-30 22:59:18 +00001261 is suppressed and the BMP image at the address
wdenk8bde7f72003-06-27 21:31:46 +00001262 specified in "splashimage" is loaded instead. The
1263 console is redirected to the "nulldev", too. This
1264 allows for a "silent" boot where a splash screen is
1265 loaded very quickly after power-on.
wdenkd791b1d2003-04-20 14:04:18 +00001266
Nikita Kiryanovc0880482013-02-24 21:28:43 +00001267 CONFIG_SPLASHIMAGE_GUARD
1268
1269 If this option is set, then U-Boot will prevent the environment
1270 variable "splashimage" from being set to a problematic address
Fabio Estevamab5645f2016-03-23 12:46:12 -03001271 (see doc/README.displaying-bmps).
Nikita Kiryanovc0880482013-02-24 21:28:43 +00001272 This option is useful for targets where, due to alignment
1273 restrictions, an improperly aligned BMP image will cause a data
1274 abort. If you think you will not have problems with unaligned
1275 accesses (for example because your toolchain prevents them)
1276 there is no need to set this option.
1277
Matthias Weisser1ca298c2009-07-09 16:07:30 +02001278 CONFIG_SPLASH_SCREEN_ALIGN
1279
1280 If this option is set the splash image can be freely positioned
1281 on the screen. Environment variable "splashpos" specifies the
1282 position as "x,y". If a positive number is given it is used as
1283 number of pixel from left/top. If a negative number is given it
1284 is used as number of pixel from right/bottom. You can also
1285 specify 'm' for centering the image.
1286
1287 Example:
1288 setenv splashpos m,m
1289 => image at center of screen
1290
1291 setenv splashpos 30,20
1292 => image at x = 30 and y = 20
1293
1294 setenv splashpos -10,m
1295 => vertically centered image
1296 at x = dspWidth - bmpWidth - 9
1297
Stefan Roese98f4a3d2005-09-22 09:04:17 +02001298- Gzip compressed BMP image support: CONFIG_VIDEO_BMP_GZIP
1299
1300 If this option is set, additionally to standard BMP
1301 images, gzipped BMP images can be displayed via the
1302 splashscreen support or the bmp command.
1303
Anatolij Gustschind5011762010-03-15 14:50:25 +01001304- Run length encoded BMP image (RLE8) support: CONFIG_VIDEO_BMP_RLE8
1305
1306 If this option is set, 8-bit RLE compressed BMP images
1307 can be displayed via the splashscreen support or the
1308 bmp command.
1309
wdenk17ea1172004-06-06 21:51:03 +00001310- MII/PHY support:
wdenk17ea1172004-06-06 21:51:03 +00001311 CONFIG_PHY_CLOCK_FREQ (ppc4xx)
1312
1313 The clock frequency of the MII bus
1314
wdenk17ea1172004-06-06 21:51:03 +00001315 CONFIG_PHY_RESET_DELAY
1316
1317 Some PHY like Intel LXT971A need extra delay after
1318 reset before any MII register access is possible.
1319 For such PHY, set this option to the usec delay
1320 required. (minimum 300usec for LXT971A)
1321
1322 CONFIG_PHY_CMD_DELAY (ppc4xx)
1323
1324 Some PHY like Intel LXT971A need extra delay after
1325 command issued before MII status register can be read
1326
wdenkc6097192002-11-03 00:24:07 +00001327- IP address:
1328 CONFIG_IPADDR
1329
1330 Define a default value for the IP address to use for
Marcel Ziswiler11ccc332008-07-09 08:17:15 +02001331 the default Ethernet interface, in case this is not
wdenkc6097192002-11-03 00:24:07 +00001332 determined through e.g. bootp.
Wolfgang Denk1ebcd652011-10-26 10:21:22 +00001333 (Environment variable "ipaddr")
wdenkc6097192002-11-03 00:24:07 +00001334
1335- Server IP address:
1336 CONFIG_SERVERIP
1337
Marcel Ziswiler11ccc332008-07-09 08:17:15 +02001338 Defines a default value for the IP address of a TFTP
wdenkc6097192002-11-03 00:24:07 +00001339 server to contact when using the "tftboot" command.
Wolfgang Denk1ebcd652011-10-26 10:21:22 +00001340 (Environment variable "serverip")
wdenkc6097192002-11-03 00:24:07 +00001341
Robin Getz97cfe862009-07-21 12:15:28 -04001342 CONFIG_KEEP_SERVERADDR
1343
1344 Keeps the server's MAC address, in the env 'serveraddr'
1345 for passing to bootargs (like Linux's netconsole option)
1346
Wolfgang Denk1ebcd652011-10-26 10:21:22 +00001347- Gateway IP address:
1348 CONFIG_GATEWAYIP
1349
1350 Defines a default value for the IP address of the
1351 default router where packets to other networks are
1352 sent to.
1353 (Environment variable "gatewayip")
1354
1355- Subnet mask:
1356 CONFIG_NETMASK
1357
1358 Defines a default value for the subnet mask (or
1359 routing prefix) which is used to determine if an IP
1360 address belongs to the local subnet or needs to be
1361 forwarded through a router.
1362 (Environment variable "netmask")
1363
wdenkc6097192002-11-03 00:24:07 +00001364- BOOTP Recovery Mode:
1365 CONFIG_BOOTP_RANDOM_DELAY
1366
1367 If you have many targets in a network that try to
1368 boot using BOOTP, you may want to avoid that all
1369 systems send out BOOTP requests at precisely the same
1370 moment (which would happen for instance at recovery
1371 from a power failure, when all systems will try to
1372 boot, thus flooding the BOOTP server. Defining
1373 CONFIG_BOOTP_RANDOM_DELAY causes a random delay to be
1374 inserted before sending out BOOTP requests. The
Wolfgang Denk6c33c782007-08-06 23:21:05 +02001375 following delays are inserted then:
wdenkc6097192002-11-03 00:24:07 +00001376
1377 1st BOOTP request: delay 0 ... 1 sec
1378 2nd BOOTP request: delay 0 ... 2 sec
1379 3rd BOOTP request: delay 0 ... 4 sec
1380 4th and following
1381 BOOTP requests: delay 0 ... 8 sec
1382
Thierry Reding92ac8ac2014-08-19 10:21:24 +02001383 CONFIG_BOOTP_ID_CACHE_SIZE
1384
1385 BOOTP packets are uniquely identified using a 32-bit ID. The
1386 server will copy the ID from client requests to responses and
1387 U-Boot will use this to determine if it is the destination of
1388 an incoming response. Some servers will check that addresses
1389 aren't in use before handing them out (usually using an ARP
1390 ping) and therefore take up to a few hundred milliseconds to
1391 respond. Network congestion may also influence the time it
1392 takes for a response to make it back to the client. If that
1393 time is too long, U-Boot will retransmit requests. In order
1394 to allow earlier responses to still be accepted after these
1395 retransmissions, U-Boot's BOOTP client keeps a small cache of
1396 IDs. The CONFIG_BOOTP_ID_CACHE_SIZE controls the size of this
1397 cache. The default is to keep IDs for up to four outstanding
1398 requests. Increasing this will allow U-Boot to accept offers
1399 from a BOOTP client in networks with unusually high latency.
1400
stroesefe389a82003-08-28 14:17:32 +00001401- DHCP Advanced Options:
Jon Loeliger1fe80d72007-07-09 22:08:34 -05001402 You can fine tune the DHCP functionality by defining
1403 CONFIG_BOOTP_* symbols:
stroesefe389a82003-08-28 14:17:32 +00001404
Jon Loeliger1fe80d72007-07-09 22:08:34 -05001405 CONFIG_BOOTP_NISDOMAIN
Jon Loeliger1fe80d72007-07-09 22:08:34 -05001406 CONFIG_BOOTP_BOOTFILESIZE
Jon Loeliger1fe80d72007-07-09 22:08:34 -05001407 CONFIG_BOOTP_SEND_HOSTNAME
1408 CONFIG_BOOTP_NTPSERVER
1409 CONFIG_BOOTP_TIMEOFFSET
1410 CONFIG_BOOTP_VENDOREX
Joe Hershberger2c00e092012-05-23 07:59:19 +00001411 CONFIG_BOOTP_MAY_FAIL
stroesefe389a82003-08-28 14:17:32 +00001412
Wilson Callan5d110f02007-07-28 10:56:13 -04001413 CONFIG_BOOTP_SERVERIP - TFTP server will be the serverip
1414 environment variable, not the BOOTP server.
stroesefe389a82003-08-28 14:17:32 +00001415
Joe Hershberger2c00e092012-05-23 07:59:19 +00001416 CONFIG_BOOTP_MAY_FAIL - If the DHCP server is not found
1417 after the configured retry count, the call will fail
1418 instead of starting over. This can be used to fail over
1419 to Link-local IP address configuration if the DHCP server
1420 is not available.
1421
stroesefe389a82003-08-28 14:17:32 +00001422 CONFIG_BOOTP_SEND_HOSTNAME - Some DHCP servers are capable
1423 to do a dynamic update of a DNS server. To do this, they
1424 need the hostname of the DHCP requester.
Wilson Callan5d110f02007-07-28 10:56:13 -04001425 If CONFIG_BOOTP_SEND_HOSTNAME is defined, the content
Jon Loeliger1fe80d72007-07-09 22:08:34 -05001426 of the "hostname" environment variable is passed as
1427 option 12 to the DHCP server.
stroesefe389a82003-08-28 14:17:32 +00001428
Aras Vaichasd9a2f412008-03-26 09:43:57 +11001429 CONFIG_BOOTP_DHCP_REQUEST_DELAY
1430
1431 A 32bit value in microseconds for a delay between
1432 receiving a "DHCP Offer" and sending the "DHCP Request".
1433 This fixes a problem with certain DHCP servers that don't
1434 respond 100% of the time to a "DHCP request". E.g. On an
1435 AT91RM9200 processor running at 180MHz, this delay needed
1436 to be *at least* 15,000 usec before a Windows Server 2003
1437 DHCP server would reply 100% of the time. I recommend at
1438 least 50,000 usec to be safe. The alternative is to hope
1439 that one of the retries will be successful but note that
1440 the DHCP timeout and retry process takes a longer than
1441 this delay.
1442
Joe Hershbergerd22c3382012-05-23 08:00:12 +00001443 - Link-local IP address negotiation:
1444 Negotiate with other link-local clients on the local network
1445 for an address that doesn't require explicit configuration.
1446 This is especially useful if a DHCP server cannot be guaranteed
1447 to exist in all environments that the device must operate.
1448
1449 See doc/README.link-local for more information.
1450
Prabhakar Kushwaha24acb832017-11-23 16:51:32 +05301451 - MAC address from environment variables
1452
1453 FDT_SEQ_MACADDR_FROM_ENV
1454
1455 Fix-up device tree with MAC addresses fetched sequentially from
1456 environment variables. This config work on assumption that
1457 non-usable ethernet node of device-tree are either not present
1458 or their status has been marked as "disabled".
1459
wdenka3d991b2004-04-15 21:48:45 +00001460 - CDP Options:
wdenk6e592382004-04-18 17:39:38 +00001461 CONFIG_CDP_DEVICE_ID
wdenka3d991b2004-04-15 21:48:45 +00001462
1463 The device id used in CDP trigger frames.
1464
1465 CONFIG_CDP_DEVICE_ID_PREFIX
1466
1467 A two character string which is prefixed to the MAC address
1468 of the device.
1469
1470 CONFIG_CDP_PORT_ID
1471
1472 A printf format string which contains the ascii name of
1473 the port. Normally is set to "eth%d" which sets
Marcel Ziswiler11ccc332008-07-09 08:17:15 +02001474 eth0 for the first Ethernet, eth1 for the second etc.
wdenka3d991b2004-04-15 21:48:45 +00001475
1476 CONFIG_CDP_CAPABILITIES
1477
1478 A 32bit integer which indicates the device capabilities;
1479 0x00000010 for a normal host which does not forwards.
1480
1481 CONFIG_CDP_VERSION
1482
1483 An ascii string containing the version of the software.
1484
1485 CONFIG_CDP_PLATFORM
1486
1487 An ascii string containing the name of the platform.
1488
1489 CONFIG_CDP_TRIGGER
1490
1491 A 32bit integer sent on the trigger.
1492
1493 CONFIG_CDP_POWER_CONSUMPTION
1494
1495 A 16bit integer containing the power consumption of the
1496 device in .1 of milliwatts.
1497
1498 CONFIG_CDP_APPLIANCE_VLAN_TYPE
1499
1500 A byte containing the id of the VLAN.
1501
Uri Mashiach79267ed2017-01-19 10:51:05 +02001502- Status LED: CONFIG_LED_STATUS
wdenkc6097192002-11-03 00:24:07 +00001503
1504 Several configurations allow to display the current
1505 status using a LED. For instance, the LED will blink
1506 fast while running U-Boot code, stop blinking as
1507 soon as a reply to a BOOTP request was received, and
1508 start blinking slow once the Linux kernel is running
1509 (supported by a status LED driver in the Linux
Uri Mashiach79267ed2017-01-19 10:51:05 +02001510 kernel). Defining CONFIG_LED_STATUS enables this
wdenkc6097192002-11-03 00:24:07 +00001511 feature in U-Boot.
1512
Igor Grinberg1df7bbb2013-11-08 01:03:50 +02001513 Additional options:
1514
Uri Mashiach79267ed2017-01-19 10:51:05 +02001515 CONFIG_LED_STATUS_GPIO
Igor Grinberg1df7bbb2013-11-08 01:03:50 +02001516 The status LED can be connected to a GPIO pin.
1517 In such cases, the gpio_led driver can be used as a
Uri Mashiach79267ed2017-01-19 10:51:05 +02001518 status LED backend implementation. Define CONFIG_LED_STATUS_GPIO
Igor Grinberg1df7bbb2013-11-08 01:03:50 +02001519 to include the gpio_led driver in the U-Boot binary.
1520
Igor Grinberg9dfdcdf2013-11-08 01:03:52 +02001521 CONFIG_GPIO_LED_INVERTED_TABLE
1522 Some GPIO connected LEDs may have inverted polarity in which
1523 case the GPIO high value corresponds to LED off state and
1524 GPIO low value corresponds to LED on state.
1525 In such cases CONFIG_GPIO_LED_INVERTED_TABLE may be defined
1526 with a list of GPIO LEDs that have inverted polarity.
1527
Heiko Schocher3f4978c2012-01-16 21:12:24 +00001528- I2C Support: CONFIG_SYS_I2C
wdenkc6097192002-11-03 00:24:07 +00001529
Heiko Schocher3f4978c2012-01-16 21:12:24 +00001530 This enable the NEW i2c subsystem, and will allow you to use
1531 i2c commands at the u-boot command line (as long as you set
Heiko Schocherea818db2013-01-29 08:53:15 +01001532 CONFIG_SYS_I2C_SOFT_SPEED and CONFIG_SYS_I2C_SOFT_SLAVE
1533 for defining speed and slave address
1534 - activate second bus with I2C_SOFT_DECLARATIONS2 define
1535 CONFIG_SYS_I2C_SOFT_SPEED_2 and CONFIG_SYS_I2C_SOFT_SLAVE_2
1536 for defining speed and slave address
1537 - activate third bus with I2C_SOFT_DECLARATIONS3 define
1538 CONFIG_SYS_I2C_SOFT_SPEED_3 and CONFIG_SYS_I2C_SOFT_SLAVE_3
1539 for defining speed and slave address
1540 - activate fourth bus with I2C_SOFT_DECLARATIONS4 define
1541 CONFIG_SYS_I2C_SOFT_SPEED_4 and CONFIG_SYS_I2C_SOFT_SLAVE_4
1542 for defining speed and slave address
Heiko Schocher3f4978c2012-01-16 21:12:24 +00001543
Heiko Schocher00f792e2012-10-24 13:48:22 +02001544 - drivers/i2c/fsl_i2c.c:
1545 - activate i2c driver with CONFIG_SYS_I2C_FSL
1546 define CONFIG_SYS_FSL_I2C_OFFSET for setting the register
1547 offset CONFIG_SYS_FSL_I2C_SPEED for the i2c speed and
1548 CONFIG_SYS_FSL_I2C_SLAVE for the slave addr of the first
1549 bus.
Wolfgang Denk93e14592013-10-04 17:43:24 +02001550 - If your board supports a second fsl i2c bus, define
Heiko Schocher00f792e2012-10-24 13:48:22 +02001551 CONFIG_SYS_FSL_I2C2_OFFSET for the register offset
1552 CONFIG_SYS_FSL_I2C2_SPEED for the speed and
1553 CONFIG_SYS_FSL_I2C2_SLAVE for the slave address of the
1554 second bus.
1555
Simon Glass1f2ba722012-10-30 07:28:53 +00001556 - drivers/i2c/tegra_i2c.c:
Nobuhiro Iwamatsu10cee512013-10-11 16:23:53 +09001557 - activate this driver with CONFIG_SYS_I2C_TEGRA
1558 - This driver adds 4 i2c buses with a fix speed from
1559 100000 and the slave addr 0!
Simon Glass1f2ba722012-10-30 07:28:53 +00001560
Dirk Eibach880540d2013-04-25 02:40:01 +00001561 - drivers/i2c/ppc4xx_i2c.c
1562 - activate this driver with CONFIG_SYS_I2C_PPC4XX
1563 - CONFIG_SYS_I2C_PPC4XX_CH0 activate hardware channel 0
1564 - CONFIG_SYS_I2C_PPC4XX_CH1 activate hardware channel 1
1565
tremfac96402013-09-21 18:13:35 +02001566 - drivers/i2c/i2c_mxc.c
1567 - activate this driver with CONFIG_SYS_I2C_MXC
Albert ARIBAUD \\(3ADEV\\)03544c62015-09-21 22:43:38 +02001568 - enable bus 1 with CONFIG_SYS_I2C_MXC_I2C1
1569 - enable bus 2 with CONFIG_SYS_I2C_MXC_I2C2
1570 - enable bus 3 with CONFIG_SYS_I2C_MXC_I2C3
1571 - enable bus 4 with CONFIG_SYS_I2C_MXC_I2C4
tremfac96402013-09-21 18:13:35 +02001572 - define speed for bus 1 with CONFIG_SYS_MXC_I2C1_SPEED
1573 - define slave for bus 1 with CONFIG_SYS_MXC_I2C1_SLAVE
1574 - define speed for bus 2 with CONFIG_SYS_MXC_I2C2_SPEED
1575 - define slave for bus 2 with CONFIG_SYS_MXC_I2C2_SLAVE
1576 - define speed for bus 3 with CONFIG_SYS_MXC_I2C3_SPEED
1577 - define slave for bus 3 with CONFIG_SYS_MXC_I2C3_SLAVE
Albert ARIBAUD \\(3ADEV\\)03544c62015-09-21 22:43:38 +02001578 - define speed for bus 4 with CONFIG_SYS_MXC_I2C4_SPEED
1579 - define slave for bus 4 with CONFIG_SYS_MXC_I2C4_SLAVE
Jeremiah Mahlerb445bbb2015-01-04 18:56:50 -08001580 If those defines are not set, default value is 100000
tremfac96402013-09-21 18:13:35 +02001581 for speed, and 0 for slave.
1582
Nobuhiro Iwamatsu1086bfa2013-09-27 16:58:30 +09001583 - drivers/i2c/rcar_i2c.c:
1584 - activate this driver with CONFIG_SYS_I2C_RCAR
1585 - This driver adds 4 i2c buses
1586
Nobuhiro Iwamatsu2035d772013-10-29 13:33:51 +09001587 - drivers/i2c/sh_i2c.c:
1588 - activate this driver with CONFIG_SYS_I2C_SH
1589 - This driver adds from 2 to 5 i2c buses
1590
1591 - CONFIG_SYS_I2C_SH_BASE0 for setting the register channel 0
1592 - CONFIG_SYS_I2C_SH_SPEED0 for for the speed channel 0
1593 - CONFIG_SYS_I2C_SH_BASE1 for setting the register channel 1
1594 - CONFIG_SYS_I2C_SH_SPEED1 for for the speed channel 1
1595 - CONFIG_SYS_I2C_SH_BASE2 for setting the register channel 2
1596 - CONFIG_SYS_I2C_SH_SPEED2 for for the speed channel 2
1597 - CONFIG_SYS_I2C_SH_BASE3 for setting the register channel 3
1598 - CONFIG_SYS_I2C_SH_SPEED3 for for the speed channel 3
1599 - CONFIG_SYS_I2C_SH_BASE4 for setting the register channel 4
1600 - CONFIG_SYS_I2C_SH_SPEED4 for for the speed channel 4
Jeremiah Mahlerb445bbb2015-01-04 18:56:50 -08001601 - CONFIG_SYS_I2C_SH_NUM_CONTROLLERS for number of i2c buses
Nobuhiro Iwamatsu2035d772013-10-29 13:33:51 +09001602
Heiko Schocher6789e842013-10-22 11:03:18 +02001603 - drivers/i2c/omap24xx_i2c.c
1604 - activate this driver with CONFIG_SYS_I2C_OMAP24XX
1605 - CONFIG_SYS_OMAP24_I2C_SPEED speed channel 0
1606 - CONFIG_SYS_OMAP24_I2C_SLAVE slave addr channel 0
1607 - CONFIG_SYS_OMAP24_I2C_SPEED1 speed channel 1
1608 - CONFIG_SYS_OMAP24_I2C_SLAVE1 slave addr channel 1
1609 - CONFIG_SYS_OMAP24_I2C_SPEED2 speed channel 2
1610 - CONFIG_SYS_OMAP24_I2C_SLAVE2 slave addr channel 2
1611 - CONFIG_SYS_OMAP24_I2C_SPEED3 speed channel 3
1612 - CONFIG_SYS_OMAP24_I2C_SLAVE3 slave addr channel 3
1613 - CONFIG_SYS_OMAP24_I2C_SPEED4 speed channel 4
1614 - CONFIG_SYS_OMAP24_I2C_SLAVE4 slave addr channel 4
1615
Naveen Krishna Che717fc62013-12-06 12:12:38 +05301616 - drivers/i2c/s3c24x0_i2c.c:
1617 - activate this driver with CONFIG_SYS_I2C_S3C24X0
1618 - This driver adds i2c buses (11 for Exynos5250, Exynos5420
1619 9 i2c buses for Exynos4 and 1 for S3C24X0 SoCs from Samsung)
1620 with a fix speed from 100000 and the slave addr 0!
1621
Dirk Eibachb46226b2014-07-03 09:28:18 +02001622 - drivers/i2c/ihs_i2c.c
1623 - activate this driver with CONFIG_SYS_I2C_IHS
1624 - CONFIG_SYS_I2C_IHS_CH0 activate hardware channel 0
1625 - CONFIG_SYS_I2C_IHS_SPEED_0 speed channel 0
1626 - CONFIG_SYS_I2C_IHS_SLAVE_0 slave addr channel 0
1627 - CONFIG_SYS_I2C_IHS_CH1 activate hardware channel 1
1628 - CONFIG_SYS_I2C_IHS_SPEED_1 speed channel 1
1629 - CONFIG_SYS_I2C_IHS_SLAVE_1 slave addr channel 1
1630 - CONFIG_SYS_I2C_IHS_CH2 activate hardware channel 2
1631 - CONFIG_SYS_I2C_IHS_SPEED_2 speed channel 2
1632 - CONFIG_SYS_I2C_IHS_SLAVE_2 slave addr channel 2
1633 - CONFIG_SYS_I2C_IHS_CH3 activate hardware channel 3
1634 - CONFIG_SYS_I2C_IHS_SPEED_3 speed channel 3
1635 - CONFIG_SYS_I2C_IHS_SLAVE_3 slave addr channel 3
Dirk Eibach071be892015-10-28 11:46:22 +01001636 - activate dual channel with CONFIG_SYS_I2C_IHS_DUAL
1637 - CONFIG_SYS_I2C_IHS_SPEED_0_1 speed channel 0_1
1638 - CONFIG_SYS_I2C_IHS_SLAVE_0_1 slave addr channel 0_1
1639 - CONFIG_SYS_I2C_IHS_SPEED_1_1 speed channel 1_1
1640 - CONFIG_SYS_I2C_IHS_SLAVE_1_1 slave addr channel 1_1
1641 - CONFIG_SYS_I2C_IHS_SPEED_2_1 speed channel 2_1
1642 - CONFIG_SYS_I2C_IHS_SLAVE_2_1 slave addr channel 2_1
1643 - CONFIG_SYS_I2C_IHS_SPEED_3_1 speed channel 3_1
1644 - CONFIG_SYS_I2C_IHS_SLAVE_3_1 slave addr channel 3_1
Dirk Eibachb46226b2014-07-03 09:28:18 +02001645
Heiko Schocher3f4978c2012-01-16 21:12:24 +00001646 additional defines:
1647
1648 CONFIG_SYS_NUM_I2C_BUSES
Simon Glass945a18e2016-10-02 18:01:05 -06001649 Hold the number of i2c buses you want to use.
Heiko Schocher3f4978c2012-01-16 21:12:24 +00001650
1651 CONFIG_SYS_I2C_DIRECT_BUS
1652 define this, if you don't use i2c muxes on your hardware.
1653 if CONFIG_SYS_I2C_MAX_HOPS is not defined or == 0 you can
1654 omit this define.
1655
1656 CONFIG_SYS_I2C_MAX_HOPS
1657 define how many muxes are maximal consecutively connected
1658 on one i2c bus. If you not use i2c muxes, omit this
1659 define.
1660
1661 CONFIG_SYS_I2C_BUSES
Jeremiah Mahlerb445bbb2015-01-04 18:56:50 -08001662 hold a list of buses you want to use, only used if
Heiko Schocher3f4978c2012-01-16 21:12:24 +00001663 CONFIG_SYS_I2C_DIRECT_BUS is not defined, for example
1664 a board with CONFIG_SYS_I2C_MAX_HOPS = 1 and
1665 CONFIG_SYS_NUM_I2C_BUSES = 9:
1666
1667 CONFIG_SYS_I2C_BUSES {{0, {I2C_NULL_HOP}}, \
1668 {0, {{I2C_MUX_PCA9547, 0x70, 1}}}, \
1669 {0, {{I2C_MUX_PCA9547, 0x70, 2}}}, \
1670 {0, {{I2C_MUX_PCA9547, 0x70, 3}}}, \
1671 {0, {{I2C_MUX_PCA9547, 0x70, 4}}}, \
1672 {0, {{I2C_MUX_PCA9547, 0x70, 5}}}, \
1673 {1, {I2C_NULL_HOP}}, \
1674 {1, {{I2C_MUX_PCA9544, 0x72, 1}}}, \
1675 {1, {{I2C_MUX_PCA9544, 0x72, 2}}}, \
1676 }
1677
1678 which defines
1679 bus 0 on adapter 0 without a mux
Heiko Schocherea818db2013-01-29 08:53:15 +01001680 bus 1 on adapter 0 with a PCA9547 on address 0x70 port 1
1681 bus 2 on adapter 0 with a PCA9547 on address 0x70 port 2
1682 bus 3 on adapter 0 with a PCA9547 on address 0x70 port 3
1683 bus 4 on adapter 0 with a PCA9547 on address 0x70 port 4
1684 bus 5 on adapter 0 with a PCA9547 on address 0x70 port 5
Heiko Schocher3f4978c2012-01-16 21:12:24 +00001685 bus 6 on adapter 1 without a mux
Heiko Schocherea818db2013-01-29 08:53:15 +01001686 bus 7 on adapter 1 with a PCA9544 on address 0x72 port 1
1687 bus 8 on adapter 1 with a PCA9544 on address 0x72 port 2
Heiko Schocher3f4978c2012-01-16 21:12:24 +00001688
1689 If you do not have i2c muxes on your board, omit this define.
1690
Simon Glassce3b5d62017-05-12 21:10:00 -06001691- Legacy I2C Support:
Heiko Schocherea818db2013-01-29 08:53:15 +01001692 If you use the software i2c interface (CONFIG_SYS_I2C_SOFT)
wdenkb37c7e52003-06-30 16:24:52 +00001693 then the following macros need to be defined (examples are
1694 from include/configs/lwmon.h):
wdenkc6097192002-11-03 00:24:07 +00001695
1696 I2C_INIT
1697
wdenkb37c7e52003-06-30 16:24:52 +00001698 (Optional). Any commands necessary to enable the I2C
wdenk43d96162003-03-06 00:02:04 +00001699 controller or configure ports.
wdenkc6097192002-11-03 00:24:07 +00001700
wdenkba56f622004-02-06 23:19:44 +00001701 eg: #define I2C_INIT (immr->im_cpm.cp_pbdir |= PB_SCL)
wdenkb37c7e52003-06-30 16:24:52 +00001702
wdenkc6097192002-11-03 00:24:07 +00001703 I2C_ACTIVE
1704
1705 The code necessary to make the I2C data line active
1706 (driven). If the data line is open collector, this
1707 define can be null.
1708
wdenkb37c7e52003-06-30 16:24:52 +00001709 eg: #define I2C_ACTIVE (immr->im_cpm.cp_pbdir |= PB_SDA)
1710
wdenkc6097192002-11-03 00:24:07 +00001711 I2C_TRISTATE
1712
1713 The code necessary to make the I2C data line tri-stated
1714 (inactive). If the data line is open collector, this
1715 define can be null.
1716
wdenkb37c7e52003-06-30 16:24:52 +00001717 eg: #define I2C_TRISTATE (immr->im_cpm.cp_pbdir &= ~PB_SDA)
1718
wdenkc6097192002-11-03 00:24:07 +00001719 I2C_READ
1720
York Sun472d5462013-04-01 11:29:11 -07001721 Code that returns true if the I2C data line is high,
1722 false if it is low.
wdenkc6097192002-11-03 00:24:07 +00001723
wdenkb37c7e52003-06-30 16:24:52 +00001724 eg: #define I2C_READ ((immr->im_cpm.cp_pbdat & PB_SDA) != 0)
1725
wdenkc6097192002-11-03 00:24:07 +00001726 I2C_SDA(bit)
1727
York Sun472d5462013-04-01 11:29:11 -07001728 If <bit> is true, sets the I2C data line high. If it
1729 is false, it clears it (low).
wdenkc6097192002-11-03 00:24:07 +00001730
wdenkb37c7e52003-06-30 16:24:52 +00001731 eg: #define I2C_SDA(bit) \
wdenk2535d602003-07-17 23:16:40 +00001732 if(bit) immr->im_cpm.cp_pbdat |= PB_SDA; \
wdenkba56f622004-02-06 23:19:44 +00001733 else immr->im_cpm.cp_pbdat &= ~PB_SDA
wdenkb37c7e52003-06-30 16:24:52 +00001734
wdenkc6097192002-11-03 00:24:07 +00001735 I2C_SCL(bit)
1736
York Sun472d5462013-04-01 11:29:11 -07001737 If <bit> is true, sets the I2C clock line high. If it
1738 is false, it clears it (low).
wdenkc6097192002-11-03 00:24:07 +00001739
wdenkb37c7e52003-06-30 16:24:52 +00001740 eg: #define I2C_SCL(bit) \
wdenk2535d602003-07-17 23:16:40 +00001741 if(bit) immr->im_cpm.cp_pbdat |= PB_SCL; \
wdenkba56f622004-02-06 23:19:44 +00001742 else immr->im_cpm.cp_pbdat &= ~PB_SCL
wdenkb37c7e52003-06-30 16:24:52 +00001743
wdenkc6097192002-11-03 00:24:07 +00001744 I2C_DELAY
1745
1746 This delay is invoked four times per clock cycle so this
1747 controls the rate of data transfer. The data rate thus
wdenkb37c7e52003-06-30 16:24:52 +00001748 is 1 / (I2C_DELAY * 4). Often defined to be something
wdenk945af8d2003-07-16 21:53:01 +00001749 like:
1750
wdenkb37c7e52003-06-30 16:24:52 +00001751 #define I2C_DELAY udelay(2)
wdenkc6097192002-11-03 00:24:07 +00001752
Mike Frysinger793b5722010-07-21 13:38:02 -04001753 CONFIG_SOFT_I2C_GPIO_SCL / CONFIG_SOFT_I2C_GPIO_SDA
1754
1755 If your arch supports the generic GPIO framework (asm/gpio.h),
1756 then you may alternatively define the two GPIOs that are to be
1757 used as SCL / SDA. Any of the previous I2C_xxx macros will
1758 have GPIO-based defaults assigned to them as appropriate.
1759
1760 You should define these to the GPIO value as given directly to
1761 the generic GPIO functions.
1762
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02001763 CONFIG_SYS_I2C_INIT_BOARD
wdenk47cd00f2003-03-06 13:39:27 +00001764
wdenk8bde7f72003-06-27 21:31:46 +00001765 When a board is reset during an i2c bus transfer
1766 chips might think that the current transfer is still
1767 in progress. On some boards it is possible to access
1768 the i2c SCLK line directly, either by using the
1769 processor pin as a GPIO or by having a second pin
1770 connected to the bus. If this option is defined a
1771 custom i2c_init_board() routine in boards/xxx/board.c
1772 is run early in the boot sequence.
wdenk47cd00f2003-03-06 13:39:27 +00001773
Ben Warrenbb99ad62006-09-07 16:50:54 -04001774 CONFIG_I2C_MULTI_BUS
1775
1776 This option allows the use of multiple I2C buses, each of which
Wolfgang Denkc0f40852011-10-26 10:21:21 +00001777 must have a controller. At any point in time, only one bus is
1778 active. To switch to a different bus, use the 'i2c dev' command.
Ben Warrenbb99ad62006-09-07 16:50:54 -04001779 Note that bus numbering is zero-based.
1780
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02001781 CONFIG_SYS_I2C_NOPROBES
Ben Warrenbb99ad62006-09-07 16:50:54 -04001782
1783 This option specifies a list of I2C devices that will be skipped
Wolfgang Denkc0f40852011-10-26 10:21:21 +00001784 when the 'i2c probe' command is issued. If CONFIG_I2C_MULTI_BUS
Peter Tyser0f89c542009-04-18 22:34:03 -05001785 is set, specify a list of bus-device pairs. Otherwise, specify
1786 a 1D array of device addresses
Ben Warrenbb99ad62006-09-07 16:50:54 -04001787
1788 e.g.
1789 #undef CONFIG_I2C_MULTI_BUS
Wolfgang Denkc0f40852011-10-26 10:21:21 +00001790 #define CONFIG_SYS_I2C_NOPROBES {0x50,0x68}
Ben Warrenbb99ad62006-09-07 16:50:54 -04001791
1792 will skip addresses 0x50 and 0x68 on a board with one I2C bus
1793
Wolfgang Denkc0f40852011-10-26 10:21:21 +00001794 #define CONFIG_I2C_MULTI_BUS
Simon Glass945a18e2016-10-02 18:01:05 -06001795 #define CONFIG_SYS_I2C_NOPROBES {{0,0x50},{0,0x68},{1,0x54}}
Ben Warrenbb99ad62006-09-07 16:50:54 -04001796
1797 will skip addresses 0x50 and 0x68 on bus 0 and address 0x54 on bus 1
1798
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02001799 CONFIG_SYS_SPD_BUS_NUM
Timur Tabibe5e6182006-11-03 19:15:00 -06001800
1801 If defined, then this indicates the I2C bus number for DDR SPD.
1802 If not defined, then U-Boot assumes that SPD is on I2C bus 0.
1803
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02001804 CONFIG_SYS_RTC_BUS_NUM
Stefan Roese0dc018e2007-02-20 10:51:26 +01001805
1806 If defined, then this indicates the I2C bus number for the RTC.
1807 If not defined, then U-Boot assumes that RTC is on I2C bus 0.
1808
Andrew Dyer2ac69852008-12-29 17:36:01 -06001809 CONFIG_SOFT_I2C_READ_REPEATED_START
1810
1811 defining this will force the i2c_read() function in
1812 the soft_i2c driver to perform an I2C repeated start
1813 between writing the address pointer and reading the
1814 data. If this define is omitted the default behaviour
1815 of doing a stop-start sequence will be used. Most I2C
1816 devices can use either method, but some require one or
1817 the other.
Timur Tabibe5e6182006-11-03 19:15:00 -06001818
wdenkc6097192002-11-03 00:24:07 +00001819- SPI Support: CONFIG_SPI
1820
1821 Enables SPI driver (so far only tested with
1822 SPI EEPROM, also an instance works with Crystal A/D and
1823 D/As on the SACSng board)
1824
wdenkc6097192002-11-03 00:24:07 +00001825 CONFIG_SOFT_SPI
1826
wdenk43d96162003-03-06 00:02:04 +00001827 Enables a software (bit-bang) SPI driver rather than
1828 using hardware support. This is a general purpose
1829 driver that only requires three general I/O port pins
1830 (two outputs, one input) to function. If this is
1831 defined, the board configuration must define several
1832 SPI configuration items (port pins to use, etc). For
1833 an example, see include/configs/sacsng.h.
wdenkc6097192002-11-03 00:24:07 +00001834
Heiko Schocherf659b572014-07-14 10:22:11 +02001835 CONFIG_SYS_SPI_MXC_WAIT
1836 Timeout for waiting until spi transfer completed.
1837 default: (CONFIG_SYS_HZ/100) /* 10 ms */
1838
Matthias Fuchs01335022007-12-27 17:12:34 +01001839- FPGA Support: CONFIG_FPGA
1840
1841 Enables FPGA subsystem.
1842
1843 CONFIG_FPGA_<vendor>
1844
1845 Enables support for specific chip vendors.
1846 (ALTERA, XILINX)
1847
1848 CONFIG_FPGA_<family>
1849
1850 Enables support for FPGA family.
1851 (SPARTAN2, SPARTAN3, VIRTEX2, CYCLONE2, ACEX1K, ACEX)
1852
1853 CONFIG_FPGA_COUNT
wdenkc6097192002-11-03 00:24:07 +00001854
wdenk43d96162003-03-06 00:02:04 +00001855 Specify the number of FPGA devices to support.
wdenkc6097192002-11-03 00:24:07 +00001856
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02001857 CONFIG_SYS_FPGA_PROG_FEEDBACK
wdenkc6097192002-11-03 00:24:07 +00001858
wdenk8bde7f72003-06-27 21:31:46 +00001859 Enable printing of hash marks during FPGA configuration.
wdenkc6097192002-11-03 00:24:07 +00001860
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02001861 CONFIG_SYS_FPGA_CHECK_BUSY
wdenkc6097192002-11-03 00:24:07 +00001862
wdenk43d96162003-03-06 00:02:04 +00001863 Enable checks on FPGA configuration interface busy
1864 status by the configuration function. This option
1865 will require a board or device specific function to
1866 be written.
wdenkc6097192002-11-03 00:24:07 +00001867
1868 CONFIG_FPGA_DELAY
1869
1870 If defined, a function that provides delays in the FPGA
1871 configuration driver.
1872
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02001873 CONFIG_SYS_FPGA_CHECK_CTRLC
wdenkc6097192002-11-03 00:24:07 +00001874 Allow Control-C to interrupt FPGA configuration
1875
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02001876 CONFIG_SYS_FPGA_CHECK_ERROR
wdenkc6097192002-11-03 00:24:07 +00001877
wdenk43d96162003-03-06 00:02:04 +00001878 Check for configuration errors during FPGA bitfile
1879 loading. For example, abort during Virtex II
1880 configuration if the INIT_B line goes low (which
1881 indicated a CRC error).
wdenkc6097192002-11-03 00:24:07 +00001882
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02001883 CONFIG_SYS_FPGA_WAIT_INIT
wdenkc6097192002-11-03 00:24:07 +00001884
Jeremiah Mahlerb445bbb2015-01-04 18:56:50 -08001885 Maximum time to wait for the INIT_B line to de-assert
1886 after PROB_B has been de-asserted during a Virtex II
wdenk43d96162003-03-06 00:02:04 +00001887 FPGA configuration sequence. The default time is 500
Marcel Ziswiler11ccc332008-07-09 08:17:15 +02001888 ms.
wdenkc6097192002-11-03 00:24:07 +00001889
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02001890 CONFIG_SYS_FPGA_WAIT_BUSY
wdenkc6097192002-11-03 00:24:07 +00001891
Jeremiah Mahlerb445bbb2015-01-04 18:56:50 -08001892 Maximum time to wait for BUSY to de-assert during
Marcel Ziswiler11ccc332008-07-09 08:17:15 +02001893 Virtex II FPGA configuration. The default is 5 ms.
wdenkc6097192002-11-03 00:24:07 +00001894
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02001895 CONFIG_SYS_FPGA_WAIT_CONFIG
wdenkc6097192002-11-03 00:24:07 +00001896
wdenk43d96162003-03-06 00:02:04 +00001897 Time to wait after FPGA configuration. The default is
Marcel Ziswiler11ccc332008-07-09 08:17:15 +02001898 200 ms.
wdenkc6097192002-11-03 00:24:07 +00001899
1900- Configuration Management:
Stefan Roeseb2b8a692014-10-22 12:13:24 +02001901
wdenkc6097192002-11-03 00:24:07 +00001902 CONFIG_IDENT_STRING
1903
wdenk43d96162003-03-06 00:02:04 +00001904 If defined, this string will be added to the U-Boot
1905 version information (U_BOOT_VERSION)
wdenkc6097192002-11-03 00:24:07 +00001906
1907- Vendor Parameter Protection:
1908
wdenk43d96162003-03-06 00:02:04 +00001909 U-Boot considers the values of the environment
1910 variables "serial#" (Board Serial Number) and
wdenk7152b1d2003-09-05 23:19:14 +00001911 "ethaddr" (Ethernet Address) to be parameters that
wdenk43d96162003-03-06 00:02:04 +00001912 are set once by the board vendor / manufacturer, and
1913 protects these variables from casual modification by
1914 the user. Once set, these variables are read-only,
1915 and write or delete attempts are rejected. You can
Marcel Ziswiler11ccc332008-07-09 08:17:15 +02001916 change this behaviour:
wdenkc6097192002-11-03 00:24:07 +00001917
1918 If CONFIG_ENV_OVERWRITE is #defined in your config
1919 file, the write protection for vendor parameters is
wdenk47cd00f2003-03-06 13:39:27 +00001920 completely disabled. Anybody can change or delete
wdenkc6097192002-11-03 00:24:07 +00001921 these parameters.
1922
Joe Hershberger92ac5202015-05-04 14:55:14 -05001923 Alternatively, if you define _both_ an ethaddr in the
1924 default env _and_ CONFIG_OVERWRITE_ETHADDR_ONCE, a default
Marcel Ziswiler11ccc332008-07-09 08:17:15 +02001925 Ethernet address is installed in the environment,
wdenkc6097192002-11-03 00:24:07 +00001926 which can be changed exactly ONCE by the user. [The
1927 serial# is unaffected by this, i. e. it remains
1928 read-only.]
1929
Joe Hershberger25980902012-12-11 22:16:31 -06001930 The same can be accomplished in a more flexible way
1931 for any variable by configuring the type of access
1932 to allow for those variables in the ".flags" variable
1933 or define CONFIG_ENV_FLAGS_LIST_STATIC.
1934
wdenkc6097192002-11-03 00:24:07 +00001935- Protected RAM:
1936 CONFIG_PRAM
1937
1938 Define this variable to enable the reservation of
1939 "protected RAM", i. e. RAM which is not overwritten
1940 by U-Boot. Define CONFIG_PRAM to hold the number of
1941 kB you want to reserve for pRAM. You can overwrite
1942 this default value by defining an environment
1943 variable "pram" to the number of kB you want to
1944 reserve. Note that the board info structure will
1945 still show the full amount of RAM. If pRAM is
1946 reserved, a new environment variable "mem" will
1947 automatically be defined to hold the amount of
1948 remaining RAM in a form that can be passed as boot
1949 argument to Linux, for instance like that:
1950
Wolfgang Denkfe126d82005-11-20 21:40:11 +01001951 setenv bootargs ... mem=\${mem}
wdenkc6097192002-11-03 00:24:07 +00001952 saveenv
1953
1954 This way you can tell Linux not to use this memory,
1955 either, which results in a memory region that will
1956 not be affected by reboots.
1957
1958 *WARNING* If your board configuration uses automatic
1959 detection of the RAM size, you must make sure that
1960 this memory test is non-destructive. So far, the
1961 following board configurations are known to be
1962 "pRAM-clean":
1963
Heiko Schocher5b8e76c2017-06-07 17:33:09 +02001964 IVMS8, IVML24, SPD8xx,
Wolfgang Denk1b0757e2012-10-24 02:36:15 +00001965 HERMES, IP860, RPXlite, LWMON,
Heiko Schocher2eb48ff2017-06-07 17:33:10 +02001966 FLAGADM
wdenkc6097192002-11-03 00:24:07 +00001967
Gabe Black40fef042012-12-02 04:55:18 +00001968- Access to physical memory region (> 4GB)
1969 Some basic support is provided for operations on memory not
1970 normally accessible to U-Boot - e.g. some architectures
1971 support access to more than 4GB of memory on 32-bit
1972 machines using physical address extension or similar.
1973 Define CONFIG_PHYSMEM to access this basic support, which
1974 currently only supports clearing the memory.
1975
wdenkc6097192002-11-03 00:24:07 +00001976- Error Recovery:
wdenkc6097192002-11-03 00:24:07 +00001977 CONFIG_NET_RETRY_COUNT
1978
wdenk43d96162003-03-06 00:02:04 +00001979 This variable defines the number of retries for
1980 network operations like ARP, RARP, TFTP, or BOOTP
1981 before giving up the operation. If not defined, a
1982 default value of 5 is used.
wdenkc6097192002-11-03 00:24:07 +00001983
Guennadi Liakhovetski40cb90e2008-04-03 17:04:19 +02001984 CONFIG_ARP_TIMEOUT
1985
1986 Timeout waiting for an ARP reply in milliseconds.
1987
Tetsuyuki Kobayashi48a3e992012-07-03 22:25:21 +00001988 CONFIG_NFS_TIMEOUT
1989
1990 Timeout in milliseconds used in NFS protocol.
1991 If you encounter "ERROR: Cannot umount" in nfs command,
1992 try longer timeout such as
1993 #define CONFIG_NFS_TIMEOUT 10000UL
1994
wdenkc6097192002-11-03 00:24:07 +00001995- Command Interpreter:
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02001996 CONFIG_SYS_PROMPT_HUSH_PS2
wdenkc6097192002-11-03 00:24:07 +00001997
1998 This defines the secondary prompt string, which is
1999 printed when the command interpreter needs more input
2000 to complete a command. Usually "> ".
2001
2002 Note:
2003
wdenk8bde7f72003-06-27 21:31:46 +00002004 In the current implementation, the local variables
2005 space and global environment variables space are
2006 separated. Local variables are those you define by
2007 simply typing `name=value'. To access a local
2008 variable later on, you have write `$name' or
2009 `${name}'; to execute the contents of a variable
2010 directly type `$name' at the command prompt.
wdenkc6097192002-11-03 00:24:07 +00002011
wdenk43d96162003-03-06 00:02:04 +00002012 Global environment variables are those you use
2013 setenv/printenv to work with. To run a command stored
2014 in such a variable, you need to use the run command,
2015 and you must not use the '$' sign to access them.
wdenkc6097192002-11-03 00:24:07 +00002016
2017 To store commands and special characters in a
2018 variable, please use double quotation marks
2019 surrounding the whole text of the variable, instead
2020 of the backslashes before semicolons and special
2021 symbols.
2022
Jeremiah Mahlerb445bbb2015-01-04 18:56:50 -08002023- Command Line Editing and History:
Marek Vasutf3b267b2016-01-27 04:47:55 +01002024 CONFIG_CMDLINE_PS_SUPPORT
2025
2026 Enable support for changing the command prompt string
2027 at run-time. Only static string is supported so far.
2028 The string is obtained from environment variables PS1
2029 and PS2.
2030
wdenka8c7c702003-12-06 19:49:23 +00002031- Default Environment:
wdenkc6097192002-11-03 00:24:07 +00002032 CONFIG_EXTRA_ENV_SETTINGS
2033
wdenk43d96162003-03-06 00:02:04 +00002034 Define this to contain any number of null terminated
2035 strings (variable = value pairs) that will be part of
wdenk7152b1d2003-09-05 23:19:14 +00002036 the default environment compiled into the boot image.
wdenk2262cfe2002-11-18 00:14:45 +00002037
wdenk43d96162003-03-06 00:02:04 +00002038 For example, place something like this in your
2039 board's config file:
wdenkc6097192002-11-03 00:24:07 +00002040
2041 #define CONFIG_EXTRA_ENV_SETTINGS \
2042 "myvar1=value1\0" \
2043 "myvar2=value2\0"
2044
wdenk43d96162003-03-06 00:02:04 +00002045 Warning: This method is based on knowledge about the
2046 internal format how the environment is stored by the
2047 U-Boot code. This is NOT an official, exported
2048 interface! Although it is unlikely that this format
wdenk7152b1d2003-09-05 23:19:14 +00002049 will change soon, there is no guarantee either.
wdenkc6097192002-11-03 00:24:07 +00002050 You better know what you are doing here.
2051
wdenk43d96162003-03-06 00:02:04 +00002052 Note: overly (ab)use of the default environment is
2053 discouraged. Make sure to check other ways to preset
Wolfgang Denk74de7ae2009-04-01 23:34:12 +02002054 the environment like the "source" command or the
wdenk43d96162003-03-06 00:02:04 +00002055 boot command first.
wdenkc6097192002-11-03 00:24:07 +00002056
Simon Glass06fd8532012-11-30 13:01:17 +00002057 CONFIG_DELAY_ENVIRONMENT
2058
2059 Normally the environment is loaded when the board is
Jeremiah Mahlerb445bbb2015-01-04 18:56:50 -08002060 initialised so that it is available to U-Boot. This inhibits
Simon Glass06fd8532012-11-30 13:01:17 +00002061 that so that the environment is not available until
2062 explicitly loaded later by U-Boot code. With CONFIG_OF_CONTROL
2063 this is instead controlled by the value of
2064 /config/load-environment.
2065
Wolfgang Denkecb0ccd2005-09-24 22:37:32 +02002066- TFTP Fixed UDP Port:
2067 CONFIG_TFTP_PORT
2068
Wolfgang Denk28cb9372005-09-24 23:25:46 +02002069 If this is defined, the environment variable tftpsrcp
Wolfgang Denkecb0ccd2005-09-24 22:37:32 +02002070 is used to supply the TFTP UDP source port value.
Wolfgang Denk28cb9372005-09-24 23:25:46 +02002071 If tftpsrcp isn't defined, the normal pseudo-random port
Wolfgang Denkecb0ccd2005-09-24 22:37:32 +02002072 number generator is used.
2073
Wolfgang Denk28cb9372005-09-24 23:25:46 +02002074 Also, the environment variable tftpdstp is used to supply
2075 the TFTP UDP destination port value. If tftpdstp isn't
2076 defined, the normal port 69 is used.
2077
2078 The purpose for tftpsrcp is to allow a TFTP server to
Wolfgang Denkecb0ccd2005-09-24 22:37:32 +02002079 blindly start the TFTP transfer using the pre-configured
2080 target IP address and UDP port. This has the effect of
2081 "punching through" the (Windows XP) firewall, allowing
2082 the remainder of the TFTP transfer to proceed normally.
2083 A better solution is to properly configure the firewall,
2084 but sometimes that is not allowed.
2085
Wolfgang Denk4cf26092011-10-07 09:58:21 +02002086 CONFIG_STANDALONE_LOAD_ADDR
2087
Wolfgang Denk6feff892011-10-09 21:06:34 +02002088 This option defines a board specific value for the
2089 address where standalone program gets loaded, thus
2090 overwriting the architecture dependent default
Wolfgang Denk4cf26092011-10-07 09:58:21 +02002091 settings.
2092
2093- Frame Buffer Address:
2094 CONFIG_FB_ADDR
2095
2096 Define CONFIG_FB_ADDR if you want to use specific
Wolfgang Denk44a53b52013-01-03 00:43:59 +00002097 address for frame buffer. This is typically the case
2098 when using a graphics controller has separate video
2099 memory. U-Boot will then place the frame buffer at
2100 the given address instead of dynamically reserving it
2101 in system RAM by calling lcd_setmem(), which grabs
2102 the memory for the frame buffer depending on the
2103 configured panel size.
Wolfgang Denk4cf26092011-10-07 09:58:21 +02002104
2105 Please see board_init_f function.
2106
Detlev Zundelcccfc2a2009-12-01 17:16:19 +01002107- Automatic software updates via TFTP server
2108 CONFIG_UPDATE_TFTP
2109 CONFIG_UPDATE_TFTP_CNT_MAX
2110 CONFIG_UPDATE_TFTP_MSEC_MAX
2111
2112 These options enable and control the auto-update feature;
2113 for a more detailed description refer to doc/README.update.
2114
2115- MTD Support (mtdparts command, UBI support)
Heiko Schocherff94bc42014-06-24 10:10:04 +02002116 CONFIG_MTD_UBI_WL_THRESHOLD
2117 This parameter defines the maximum difference between the highest
2118 erase counter value and the lowest erase counter value of eraseblocks
2119 of UBI devices. When this threshold is exceeded, UBI starts performing
2120 wear leveling by means of moving data from eraseblock with low erase
2121 counter to eraseblocks with high erase counter.
2122
2123 The default value should be OK for SLC NAND flashes, NOR flashes and
2124 other flashes which have eraseblock life-cycle 100000 or more.
2125 However, in case of MLC NAND flashes which typically have eraseblock
2126 life-cycle less than 10000, the threshold should be lessened (e.g.,
2127 to 128 or 256, although it does not have to be power of 2).
2128
2129 default: 4096
Simon Glassc654b512014-10-23 18:58:54 -06002130
Heiko Schocherff94bc42014-06-24 10:10:04 +02002131 CONFIG_MTD_UBI_BEB_LIMIT
2132 This option specifies the maximum bad physical eraseblocks UBI
2133 expects on the MTD device (per 1024 eraseblocks). If the
2134 underlying flash does not admit of bad eraseblocks (e.g. NOR
2135 flash), this value is ignored.
2136
2137 NAND datasheets often specify the minimum and maximum NVM
2138 (Number of Valid Blocks) for the flashes' endurance lifetime.
2139 The maximum expected bad eraseblocks per 1024 eraseblocks
2140 then can be calculated as "1024 * (1 - MinNVB / MaxNVB)",
2141 which gives 20 for most NANDs (MaxNVB is basically the total
2142 count of eraseblocks on the chip).
2143
2144 To put it differently, if this value is 20, UBI will try to
2145 reserve about 1.9% of physical eraseblocks for bad blocks
2146 handling. And that will be 1.9% of eraseblocks on the entire
2147 NAND chip, not just the MTD partition UBI attaches. This means
2148 that if you have, say, a NAND flash chip admits maximum 40 bad
2149 eraseblocks, and it is split on two MTD partitions of the same
2150 size, UBI will reserve 40 eraseblocks when attaching a
2151 partition.
2152
2153 default: 20
2154
2155 CONFIG_MTD_UBI_FASTMAP
2156 Fastmap is a mechanism which allows attaching an UBI device
2157 in nearly constant time. Instead of scanning the whole MTD device it
2158 only has to locate a checkpoint (called fastmap) on the device.
2159 The on-flash fastmap contains all information needed to attach
2160 the device. Using fastmap makes only sense on large devices where
2161 attaching by scanning takes long. UBI will not automatically install
2162 a fastmap on old images, but you can set the UBI parameter
2163 CONFIG_MTD_UBI_FASTMAP_AUTOCONVERT to 1 if you want so. Please note
2164 that fastmap-enabled images are still usable with UBI implementations
2165 without fastmap support. On typical flash devices the whole fastmap
2166 fits into one PEB. UBI will reserve PEBs to hold two fastmaps.
2167
2168 CONFIG_MTD_UBI_FASTMAP_AUTOCONVERT
2169 Set this parameter to enable fastmap automatically on images
2170 without a fastmap.
2171 default: 0
2172
Heiko Schocher0195a7b2015-10-22 06:19:21 +02002173 CONFIG_MTD_UBI_FM_DEBUG
2174 Enable UBI fastmap debug
2175 default: 0
2176
Daniel Schwierzeck6a11cf42011-07-18 07:48:07 +00002177- SPL framework
Wolfgang Denk04e5ae72011-09-11 21:24:09 +02002178 CONFIG_SPL
2179 Enable building of SPL globally.
Daniel Schwierzeck6a11cf42011-07-18 07:48:07 +00002180
Tom Rini95579792012-02-14 07:29:40 +00002181 CONFIG_SPL_LDSCRIPT
2182 LDSCRIPT for linking the SPL binary.
2183
Albert ARIBAUD6ebc3462013-04-12 05:14:30 +00002184 CONFIG_SPL_MAX_FOOTPRINT
2185 Maximum size in memory allocated to the SPL, BSS included.
2186 When defined, the linker checks that the actual memory
2187 used by SPL from _start to __bss_end does not exceed it.
Albert ARIBAUD8960af82013-04-14 04:48:38 +00002188 CONFIG_SPL_MAX_FOOTPRINT and CONFIG_SPL_BSS_MAX_SIZE
Albert ARIBAUD6ebc3462013-04-12 05:14:30 +00002189 must not be both defined at the same time.
2190
Tom Rini95579792012-02-14 07:29:40 +00002191 CONFIG_SPL_MAX_SIZE
Albert ARIBAUD6ebc3462013-04-12 05:14:30 +00002192 Maximum size of the SPL image (text, data, rodata, and
2193 linker lists sections), BSS excluded.
2194 When defined, the linker checks that the actual size does
2195 not exceed it.
Tom Rini95579792012-02-14 07:29:40 +00002196
Scott Wood94a45bb2012-09-20 19:05:12 -05002197 CONFIG_SPL_RELOC_TEXT_BASE
2198 Address to relocate to. If unspecified, this is equal to
2199 CONFIG_SPL_TEXT_BASE (i.e. no relocation is done).
2200
Tom Rini95579792012-02-14 07:29:40 +00002201 CONFIG_SPL_BSS_START_ADDR
2202 Link address for the BSS within the SPL binary.
2203
2204 CONFIG_SPL_BSS_MAX_SIZE
Albert ARIBAUD6ebc3462013-04-12 05:14:30 +00002205 Maximum size in memory allocated to the SPL BSS.
2206 When defined, the linker checks that the actual memory used
2207 by SPL from __bss_start to __bss_end does not exceed it.
Albert ARIBAUD8960af82013-04-14 04:48:38 +00002208 CONFIG_SPL_MAX_FOOTPRINT and CONFIG_SPL_BSS_MAX_SIZE
Albert ARIBAUD6ebc3462013-04-12 05:14:30 +00002209 must not be both defined at the same time.
Tom Rini95579792012-02-14 07:29:40 +00002210
2211 CONFIG_SPL_STACK
2212 Adress of the start of the stack SPL will use
2213
Albert ARIBAUD \(3ADEV\)8c80eb32015-03-31 11:40:50 +02002214 CONFIG_SPL_PANIC_ON_RAW_IMAGE
2215 When defined, SPL will panic() if the image it has
2216 loaded does not have a signature.
2217 Defining this is useful when code which loads images
2218 in SPL cannot guarantee that absolutely all read errors
2219 will be caught.
2220 An example is the LPC32XX MLC NAND driver, which will
2221 consider that a completely unreadable NAND block is bad,
2222 and thus should be skipped silently.
2223
Scott Wood94a45bb2012-09-20 19:05:12 -05002224 CONFIG_SPL_RELOC_STACK
2225 Adress of the start of the stack SPL will use after
2226 relocation. If unspecified, this is equal to
2227 CONFIG_SPL_STACK.
2228
Tom Rini95579792012-02-14 07:29:40 +00002229 CONFIG_SYS_SPL_MALLOC_START
2230 Starting address of the malloc pool used in SPL.
Fabio Estevam9ac4fc82015-11-12 12:30:19 -02002231 When this option is set the full malloc is used in SPL and
2232 it is set up by spl_init() and before that, the simple malloc()
2233 can be used if CONFIG_SYS_MALLOC_F is defined.
Tom Rini95579792012-02-14 07:29:40 +00002234
2235 CONFIG_SYS_SPL_MALLOC_SIZE
2236 The size of the malloc pool used in SPL.
Daniel Schwierzeck6a11cf42011-07-18 07:48:07 +00002237
Tom Rini9607faf2014-03-28 12:03:39 -04002238 CONFIG_SPL_OS_BOOT
2239 Enable booting directly to an OS from SPL.
2240 See also: doc/README.falcon
2241
Tom Rini861a86f2012-08-13 11:37:56 -07002242 CONFIG_SPL_DISPLAY_PRINT
2243 For ARM, enable an optional function to print more information
2244 about the running system.
2245
Scott Wood4b919722012-09-20 16:35:21 -05002246 CONFIG_SPL_INIT_MINIMAL
2247 Arch init code should be built for a very small image
2248
Paul Kocialkowskib97300b2014-11-08 23:14:56 +01002249 CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_PARTITION
2250 Partition on the MMC to load U-Boot from when the MMC is being
2251 used in raw mode
2252
Peter Korsgaard2b75b0a2013-05-13 08:36:29 +00002253 CONFIG_SYS_MMCSD_RAW_MODE_KERNEL_SECTOR
2254 Sector to load kernel uImage from when MMC is being
2255 used in raw mode (for Falcon mode)
2256
2257 CONFIG_SYS_MMCSD_RAW_MODE_ARGS_SECTOR,
2258 CONFIG_SYS_MMCSD_RAW_MODE_ARGS_SECTORS
2259 Sector and number of sectors to load kernel argument
2260 parameters from when MMC is being used in raw mode
2261 (for falcon mode)
2262
Paul Kocialkowskie2ccdf82014-11-08 23:14:55 +01002263 CONFIG_SYS_MMCSD_FS_BOOT_PARTITION
2264 Partition on the MMC to load U-Boot from when the MMC is being
2265 used in fs mode
2266
Guillaume GARDETfae81c72014-10-15 17:53:13 +02002267 CONFIG_SPL_FS_LOAD_PAYLOAD_NAME
2268 Filename to read to load U-Boot when reading from filesystem
2269
2270 CONFIG_SPL_FS_LOAD_KERNEL_NAME
Peter Korsgaard7ad2cc72013-05-13 08:36:27 +00002271 Filename to read to load kernel uImage when reading
Guillaume GARDETfae81c72014-10-15 17:53:13 +02002272 from filesystem (for Falcon mode)
Peter Korsgaard7ad2cc72013-05-13 08:36:27 +00002273
Guillaume GARDETfae81c72014-10-15 17:53:13 +02002274 CONFIG_SPL_FS_LOAD_ARGS_NAME
Peter Korsgaard7ad2cc72013-05-13 08:36:27 +00002275 Filename to read to load kernel argument parameters
Guillaume GARDETfae81c72014-10-15 17:53:13 +02002276 when reading from filesystem (for Falcon mode)
Peter Korsgaard7ad2cc72013-05-13 08:36:27 +00002277
Scott Wood06f60ae2012-12-06 13:33:17 +00002278 CONFIG_SPL_MPC83XX_WAIT_FOR_NAND
2279 Set this for NAND SPL on PPC mpc83xx targets, so that
2280 start.S waits for the rest of the SPL to load before
2281 continuing (the hardware starts execution after just
2282 loading the first page rather than the full 4K).
2283
Prabhakar Kushwaha651fcf62014-04-08 19:12:31 +05302284 CONFIG_SPL_SKIP_RELOCATE
2285 Avoid SPL relocation
2286
Scott Wood6f2f01b2012-09-20 19:09:07 -05002287 CONFIG_SPL_NAND_BASE
2288 Include nand_base.c in the SPL. Requires
2289 CONFIG_SPL_NAND_DRIVERS.
2290
2291 CONFIG_SPL_NAND_DRIVERS
2292 SPL uses normal NAND drivers, not minimal drivers.
2293
Jörg Krause15e207f2018-01-14 19:26:38 +01002294 CONFIG_SPL_NAND_IDENT
2295 SPL uses the chip ID list to identify the NAND flash.
2296 Requires CONFIG_SPL_NAND_BASE.
2297
Scott Wood6f2f01b2012-09-20 19:09:07 -05002298 CONFIG_SPL_NAND_ECC
2299 Include standard software ECC in the SPL
2300
Tom Rini95579792012-02-14 07:29:40 +00002301 CONFIG_SPL_NAND_SIMPLE
Scott Wood7d4b7952012-09-21 18:35:27 -05002302 Support for NAND boot using simple NAND drivers that
2303 expose the cmd_ctrl() interface.
Tom Rini95579792012-02-14 07:29:40 +00002304
Thomas Gleixner6f4e7d32016-07-12 20:28:12 +02002305 CONFIG_SPL_UBI
2306 Support for a lightweight UBI (fastmap) scanner and
2307 loader
2308
Heiko Schocher0c3117b2014-10-31 08:31:00 +01002309 CONFIG_SPL_NAND_RAW_ONLY
2310 Support to boot only raw u-boot.bin images. Use this only
2311 if you need to save space.
2312
Ying Zhang7c8eea52013-08-16 15:16:12 +08002313 CONFIG_SPL_COMMON_INIT_DDR
2314 Set for common ddr init with serial presence detect in
2315 SPL binary.
2316
Tom Rini95579792012-02-14 07:29:40 +00002317 CONFIG_SYS_NAND_5_ADDR_CYCLE, CONFIG_SYS_NAND_PAGE_COUNT,
2318 CONFIG_SYS_NAND_PAGE_SIZE, CONFIG_SYS_NAND_OOBSIZE,
2319 CONFIG_SYS_NAND_BLOCK_SIZE, CONFIG_SYS_NAND_BAD_BLOCK_POS,
2320 CONFIG_SYS_NAND_ECCPOS, CONFIG_SYS_NAND_ECCSIZE,
2321 CONFIG_SYS_NAND_ECCBYTES
2322 Defines the size and behavior of the NAND that SPL uses
Scott Wood7d4b7952012-09-21 18:35:27 -05002323 to read U-Boot
Tom Rini95579792012-02-14 07:29:40 +00002324
2325 CONFIG_SYS_NAND_U_BOOT_OFFS
Scott Wood7d4b7952012-09-21 18:35:27 -05002326 Location in NAND to read U-Boot from
2327
2328 CONFIG_SYS_NAND_U_BOOT_DST
2329 Location in memory to load U-Boot to
2330
2331 CONFIG_SYS_NAND_U_BOOT_SIZE
2332 Size of image to load
Tom Rini95579792012-02-14 07:29:40 +00002333
2334 CONFIG_SYS_NAND_U_BOOT_START
Scott Wood7d4b7952012-09-21 18:35:27 -05002335 Entry point in loaded image to jump to
Tom Rini95579792012-02-14 07:29:40 +00002336
2337 CONFIG_SYS_NAND_HW_ECC_OOBFIRST
2338 Define this if you need to first read the OOB and then the
Jeremiah Mahlerb445bbb2015-01-04 18:56:50 -08002339 data. This is used, for example, on davinci platforms.
Tom Rini95579792012-02-14 07:29:40 +00002340
Pavel Machekc57b9532012-08-30 22:42:11 +02002341 CONFIG_SPL_RAM_DEVICE
2342 Support for running image already present in ram, in SPL binary
2343
Scott Wood74752ba2012-12-06 13:33:16 +00002344 CONFIG_SPL_PAD_TO
Benoît Thébaudeau6113d3f2013-04-11 09:35:49 +00002345 Image offset to which the SPL should be padded before appending
2346 the SPL payload. By default, this is defined as
2347 CONFIG_SPL_MAX_SIZE, or 0 if CONFIG_SPL_MAX_SIZE is undefined.
2348 CONFIG_SPL_PAD_TO must be either 0, meaning to append the SPL
2349 payload without any padding, or >= CONFIG_SPL_MAX_SIZE.
Scott Wood74752ba2012-12-06 13:33:16 +00002350
Scott Woodca2fca22012-09-21 16:27:32 -05002351 CONFIG_SPL_TARGET
2352 Final target image containing SPL and payload. Some SPLs
2353 use an arch-specific makefile fragment instead, for
2354 example if more than one image needs to be produced.
2355
Marek Vasutb527b9c2018-05-13 00:22:52 +02002356 CONFIG_SPL_FIT_PRINT
Simon Glass87ebee32013-05-08 08:05:59 +00002357 Printing information about a FIT image adds quite a bit of
2358 code to SPL. So this is normally disabled in SPL. Use this
2359 option to re-enable it. This will affect the output of the
2360 bootm command when booting a FIT image.
2361
Ying Zhang3aa29de2013-08-16 15:16:15 +08002362- TPL framework
2363 CONFIG_TPL
2364 Enable building of TPL globally.
2365
2366 CONFIG_TPL_PAD_TO
2367 Image offset to which the TPL should be padded before appending
2368 the TPL payload. By default, this is defined as
Wolfgang Denk93e14592013-10-04 17:43:24 +02002369 CONFIG_SPL_MAX_SIZE, or 0 if CONFIG_SPL_MAX_SIZE is undefined.
2370 CONFIG_SPL_PAD_TO must be either 0, meaning to append the SPL
2371 payload without any padding, or >= CONFIG_SPL_MAX_SIZE.
Ying Zhang3aa29de2013-08-16 15:16:15 +08002372
wdenka8c7c702003-12-06 19:49:23 +00002373- Interrupt support (PPC):
2374
wdenkd4ca31c2004-01-02 14:00:00 +00002375 There are common interrupt_init() and timer_interrupt()
2376 for all PPC archs. interrupt_init() calls interrupt_init_cpu()
Marcel Ziswiler11ccc332008-07-09 08:17:15 +02002377 for CPU specific initialization. interrupt_init_cpu()
wdenkd4ca31c2004-01-02 14:00:00 +00002378 should set decrementer_count to appropriate value. If
Marcel Ziswiler11ccc332008-07-09 08:17:15 +02002379 CPU resets decrementer automatically after interrupt
wdenkd4ca31c2004-01-02 14:00:00 +00002380 (ppc4xx) it should set decrementer_count to zero.
Marcel Ziswiler11ccc332008-07-09 08:17:15 +02002381 timer_interrupt() calls timer_interrupt_cpu() for CPU
wdenkd4ca31c2004-01-02 14:00:00 +00002382 specific handling. If board has watchdog / status_led
2383 / other_activity_monitor it works automatically from
2384 general timer_interrupt().
wdenka8c7c702003-12-06 19:49:23 +00002385
wdenkc6097192002-11-03 00:24:07 +00002386
Helmut Raiger9660e442011-10-20 04:19:47 +00002387Board initialization settings:
2388------------------------------
2389
2390During Initialization u-boot calls a number of board specific functions
2391to allow the preparation of board specific prerequisites, e.g. pin setup
2392before drivers are initialized. To enable these callbacks the
2393following configuration macros have to be defined. Currently this is
2394architecture specific, so please check arch/your_architecture/lib/board.c
2395typically in board_init_f() and board_init_r().
2396
2397- CONFIG_BOARD_EARLY_INIT_F: Call board_early_init_f()
2398- CONFIG_BOARD_EARLY_INIT_R: Call board_early_init_r()
2399- CONFIG_BOARD_LATE_INIT: Call board_late_init()
2400- CONFIG_BOARD_POSTCLK_INIT: Call board_postclk_init()
wdenkc6097192002-11-03 00:24:07 +00002401
wdenkc6097192002-11-03 00:24:07 +00002402Configuration Settings:
2403-----------------------
2404
Simon Glass4d979bf2019-12-28 10:45:10 -07002405- MEM_SUPPORT_64BIT_DATA: Defined automatically if compiled as 64-bit.
York Sun4d1fd7f2014-02-26 17:03:19 -08002406 Optionally it can be defined to support 64-bit memory commands.
2407
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002408- CONFIG_SYS_LONGHELP: Defined when you want long help messages included;
wdenkc6097192002-11-03 00:24:07 +00002409 undefine this when you're short of memory.
2410
Peter Tyser2fb26042009-01-27 18:03:12 -06002411- CONFIG_SYS_HELP_CMD_WIDTH: Defined when you want to override the default
2412 width of the commands listed in the 'help' command output.
2413
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002414- CONFIG_SYS_PROMPT: This is what U-Boot prints on the console to
wdenkc6097192002-11-03 00:24:07 +00002415 prompt for user input.
2416
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002417- CONFIG_SYS_CBSIZE: Buffer size for input from the Console
wdenkc6097192002-11-03 00:24:07 +00002418
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002419- CONFIG_SYS_PBSIZE: Buffer size for Console output
wdenkc6097192002-11-03 00:24:07 +00002420
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002421- CONFIG_SYS_MAXARGS: max. Number of arguments accepted for monitor commands
wdenkc6097192002-11-03 00:24:07 +00002422
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002423- CONFIG_SYS_BARGSIZE: Buffer size for Boot Arguments which are passed to
wdenkc6097192002-11-03 00:24:07 +00002424 the application (usually a Linux kernel) when it is
2425 booted
2426
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002427- CONFIG_SYS_BAUDRATE_TABLE:
wdenkc6097192002-11-03 00:24:07 +00002428 List of legal baudrate settings for this board.
2429
York Sune8149522015-12-04 11:57:07 -08002430- CONFIG_SYS_MEM_RESERVE_SECURE
York Sune61a7532016-06-24 16:46:18 -07002431 Only implemented for ARMv8 for now.
York Sune8149522015-12-04 11:57:07 -08002432 If defined, the size of CONFIG_SYS_MEM_RESERVE_SECURE memory
2433 is substracted from total RAM and won't be reported to OS.
2434 This memory can be used as secure memory. A variable
York Sune61a7532016-06-24 16:46:18 -07002435 gd->arch.secure_ram is used to track the location. In systems
York Sune8149522015-12-04 11:57:07 -08002436 the RAM base is not zero, or RAM is divided into banks,
2437 this variable needs to be recalcuated to get the address.
2438
York Sunaabd7dd2015-12-07 11:05:29 -08002439- CONFIG_SYS_MEM_TOP_HIDE:
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002440 If CONFIG_SYS_MEM_TOP_HIDE is defined in the board config header,
Stefan Roese14f73ca2008-03-26 10:14:11 +01002441 this specified memory area will get subtracted from the top
Marcel Ziswiler11ccc332008-07-09 08:17:15 +02002442 (end) of RAM and won't get "touched" at all by U-Boot. By
Stefan Roese14f73ca2008-03-26 10:14:11 +01002443 fixing up gd->ram_size the Linux kernel should gets passed
2444 the now "corrected" memory size and won't touch it either.
2445 This should work for arch/ppc and arch/powerpc. Only Linux
Stefan Roese5e12e752008-03-28 11:02:53 +01002446 board ports in arch/powerpc with bootwrapper support that
Stefan Roese14f73ca2008-03-26 10:14:11 +01002447 recalculate the memory size from the SDRAM controller setup
Stefan Roese5e12e752008-03-28 11:02:53 +01002448 will have to get fixed in Linux additionally.
Stefan Roese14f73ca2008-03-26 10:14:11 +01002449
2450 This option can be used as a workaround for the 440EPx/GRx
2451 CHIP 11 errata where the last 256 bytes in SDRAM shouldn't
2452 be touched.
2453
2454 WARNING: Please make sure that this value is a multiple of
2455 the Linux page size (normally 4k). If this is not the case,
2456 then the end address of the Linux memory will be located at a
2457 non page size aligned address and this could cause major
2458 problems.
2459
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002460- CONFIG_SYS_LOADS_BAUD_CHANGE:
wdenkc6097192002-11-03 00:24:07 +00002461 Enable temporary baudrate change while serial download
2462
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002463- CONFIG_SYS_SDRAM_BASE:
wdenkc6097192002-11-03 00:24:07 +00002464 Physical start address of SDRAM. _Must_ be 0 here.
2465
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002466- CONFIG_SYS_FLASH_BASE:
wdenkc6097192002-11-03 00:24:07 +00002467 Physical start address of Flash memory.
2468
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002469- CONFIG_SYS_MONITOR_BASE:
wdenkc6097192002-11-03 00:24:07 +00002470 Physical start address of boot monitor code (set by
2471 make config files to be same as the text base address
Wolfgang Denk14d0a022010-10-07 21:51:12 +02002472 (CONFIG_SYS_TEXT_BASE) used when linking) - same as
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002473 CONFIG_SYS_FLASH_BASE when booting from flash.
wdenkc6097192002-11-03 00:24:07 +00002474
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002475- CONFIG_SYS_MONITOR_LEN:
wdenk8bde7f72003-06-27 21:31:46 +00002476 Size of memory reserved for monitor code, used to
2477 determine _at_compile_time_ (!) if the environment is
2478 embedded within the U-Boot image, or in a separate
2479 flash sector.
wdenkc6097192002-11-03 00:24:07 +00002480
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002481- CONFIG_SYS_MALLOC_LEN:
wdenkc6097192002-11-03 00:24:07 +00002482 Size of DRAM reserved for malloc() use.
2483
Simon Glassd59476b2014-07-10 22:23:28 -06002484- CONFIG_SYS_MALLOC_F_LEN
2485 Size of the malloc() pool for use before relocation. If
2486 this is defined, then a very simple malloc() implementation
2487 will become available before relocation. The address is just
2488 below the global data, and the stack is moved down to make
2489 space.
2490
2491 This feature allocates regions with increasing addresses
2492 within the region. calloc() is supported, but realloc()
2493 is not available. free() is supported but does nothing.
Jeremiah Mahlerb445bbb2015-01-04 18:56:50 -08002494 The memory will be freed (or in fact just forgotten) when
Simon Glassd59476b2014-07-10 22:23:28 -06002495 U-Boot relocates itself.
2496
Simon Glass38687ae2014-11-10 17:16:54 -07002497- CONFIG_SYS_MALLOC_SIMPLE
2498 Provides a simple and small malloc() and calloc() for those
2499 boards which do not use the full malloc in SPL (which is
2500 enabled with CONFIG_SYS_SPL_MALLOC_START).
2501
Thierry Reding1dfdd9b2014-12-09 22:25:22 -07002502- CONFIG_SYS_NONCACHED_MEMORY:
2503 Size of non-cached memory area. This area of memory will be
2504 typically located right below the malloc() area and mapped
2505 uncached in the MMU. This is useful for drivers that would
2506 otherwise require a lot of explicit cache maintenance. For
2507 some drivers it's also impossible to properly maintain the
2508 cache. For example if the regions that need to be flushed
2509 are not a multiple of the cache-line size, *and* padding
2510 cannot be allocated between the regions to align them (i.e.
2511 if the HW requires a contiguous array of regions, and the
2512 size of each region is not cache-aligned), then a flush of
2513 one region may result in overwriting data that hardware has
2514 written to another region in the same cache-line. This can
2515 happen for example in network drivers where descriptors for
2516 buffers are typically smaller than the CPU cache-line (e.g.
2517 16 bytes vs. 32 or 64 bytes).
2518
2519 Non-cached memory is only supported on 32-bit ARM at present.
2520
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002521- CONFIG_SYS_BOOTM_LEN:
Stefan Roese15940c92006-03-13 11:16:36 +01002522 Normally compressed uImages are limited to an
2523 uncompressed size of 8 MBytes. If this is not enough,
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002524 you can define CONFIG_SYS_BOOTM_LEN in your board config file
Stefan Roese15940c92006-03-13 11:16:36 +01002525 to adjust this setting to your needs.
2526
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002527- CONFIG_SYS_BOOTMAPSZ:
wdenkc6097192002-11-03 00:24:07 +00002528 Maximum size of memory mapped by the startup code of
2529 the Linux kernel; all data that must be processed by
Bartlomiej Sieka7d721e32008-04-14 15:44:16 +02002530 the Linux kernel (bd_info, boot arguments, FDT blob if
2531 used) must be put below this limit, unless "bootm_low"
Robert P. J. Day1bce2ae2013-09-16 07:15:45 -04002532 environment variable is defined and non-zero. In such case
Bartlomiej Sieka7d721e32008-04-14 15:44:16 +02002533 all data for the Linux kernel must be between "bootm_low"
Wolfgang Denkc0f40852011-10-26 10:21:21 +00002534 and "bootm_low" + CONFIG_SYS_BOOTMAPSZ. The environment
Grant Likelyc3624e62011-03-28 09:58:43 +00002535 variable "bootm_mapsize" will override the value of
2536 CONFIG_SYS_BOOTMAPSZ. If CONFIG_SYS_BOOTMAPSZ is undefined,
2537 then the value in "bootm_size" will be used instead.
wdenkc6097192002-11-03 00:24:07 +00002538
John Rigbyfca43cc2010-10-13 13:57:35 -06002539- CONFIG_SYS_BOOT_RAMDISK_HIGH:
2540 Enable initrd_high functionality. If defined then the
2541 initrd_high feature is enabled and the bootm ramdisk subcommand
2542 is enabled.
2543
2544- CONFIG_SYS_BOOT_GET_CMDLINE:
2545 Enables allocating and saving kernel cmdline in space between
2546 "bootm_low" and "bootm_low" + BOOTMAPSZ.
2547
2548- CONFIG_SYS_BOOT_GET_KBD:
2549 Enables allocating and saving a kernel copy of the bd_info in
2550 space between "bootm_low" and "bootm_low" + BOOTMAPSZ.
2551
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002552- CONFIG_SYS_MAX_FLASH_BANKS:
wdenkc6097192002-11-03 00:24:07 +00002553 Max number of Flash memory banks
2554
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002555- CONFIG_SYS_MAX_FLASH_SECT:
wdenkc6097192002-11-03 00:24:07 +00002556 Max number of sectors on a Flash chip
2557
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002558- CONFIG_SYS_FLASH_ERASE_TOUT:
wdenkc6097192002-11-03 00:24:07 +00002559 Timeout for Flash erase operations (in ms)
2560
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002561- CONFIG_SYS_FLASH_WRITE_TOUT:
wdenkc6097192002-11-03 00:24:07 +00002562 Timeout for Flash write operations (in ms)
2563
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002564- CONFIG_SYS_FLASH_LOCK_TOUT
wdenk8564acf2003-07-14 22:13:32 +00002565 Timeout for Flash set sector lock bit operation (in ms)
2566
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002567- CONFIG_SYS_FLASH_UNLOCK_TOUT
wdenk8564acf2003-07-14 22:13:32 +00002568 Timeout for Flash clear lock bits operation (in ms)
2569
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002570- CONFIG_SYS_FLASH_PROTECTION
wdenk8564acf2003-07-14 22:13:32 +00002571 If defined, hardware flash sectors protection is used
2572 instead of U-Boot software protection.
2573
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002574- CONFIG_SYS_DIRECT_FLASH_TFTP:
wdenkc6097192002-11-03 00:24:07 +00002575
2576 Enable TFTP transfers directly to flash memory;
2577 without this option such a download has to be
2578 performed in two steps: (1) download to RAM, and (2)
2579 copy from RAM to flash.
2580
2581 The two-step approach is usually more reliable, since
2582 you can check if the download worked before you erase
Marcel Ziswiler11ccc332008-07-09 08:17:15 +02002583 the flash, but in some situations (when system RAM is
2584 too limited to allow for a temporary copy of the
wdenkc6097192002-11-03 00:24:07 +00002585 downloaded image) this option may be very useful.
2586
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002587- CONFIG_SYS_FLASH_CFI:
wdenk43d96162003-03-06 00:02:04 +00002588 Define if the flash driver uses extra elements in the
wdenk5653fc32004-02-08 22:55:38 +00002589 common flash structure for storing flash geometry.
2590
Jean-Christophe PLAGNIOL-VILLARD00b18832008-08-13 01:40:42 +02002591- CONFIG_FLASH_CFI_DRIVER
wdenk5653fc32004-02-08 22:55:38 +00002592 This option also enables the building of the cfi_flash driver
2593 in the drivers directory
wdenkc6097192002-11-03 00:24:07 +00002594
Piotr Ziecik91809ed2008-11-17 15:57:58 +01002595- CONFIG_FLASH_CFI_MTD
2596 This option enables the building of the cfi_mtd driver
2597 in the drivers directory. The driver exports CFI flash
2598 to the MTD layer.
2599
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002600- CONFIG_SYS_FLASH_USE_BUFFER_WRITE
Guennadi Liakhovetski96ef8312008-04-03 13:36:02 +02002601 Use buffered writes to flash.
2602
2603- CONFIG_FLASH_SPANSION_S29WS_N
2604 s29ws-n MirrorBit flash has non-standard addresses for buffered
2605 write commands.
2606
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002607- CONFIG_SYS_FLASH_QUIET_TEST
Stefan Roese5568e612005-11-22 13:20:42 +01002608 If this option is defined, the common CFI flash doesn't
2609 print it's warning upon not recognized FLASH banks. This
2610 is useful, if some of the configured banks are only
2611 optionally available.
2612
Jerry Van Baren9a042e92008-03-08 13:48:01 -05002613- CONFIG_FLASH_SHOW_PROGRESS
2614 If defined (must be an integer), print out countdown
2615 digits and dots. Recommended value: 45 (9..1) for 80
2616 column displays, 15 (3..1) for 40 column displays.
2617
Stefan Roese352ef3f2013-04-04 15:53:14 +02002618- CONFIG_FLASH_VERIFY
2619 If defined, the content of the flash (destination) is compared
2620 against the source after the write operation. An error message
2621 will be printed when the contents are not identical.
2622 Please note that this option is useless in nearly all cases,
2623 since such flash programming errors usually are detected earlier
2624 while unprotecting/erasing/programming. Please only enable
2625 this option if you really know what you are doing.
2626
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002627- CONFIG_SYS_RX_ETH_BUFFER:
Marcel Ziswiler11ccc332008-07-09 08:17:15 +02002628 Defines the number of Ethernet receive buffers. On some
2629 Ethernet controllers it is recommended to set this value
stroese53cf9432003-06-05 15:39:44 +00002630 to 8 or even higher (EEPRO100 or 405 EMAC), since all
2631 buffers can be full shortly after enabling the interface
Marcel Ziswiler11ccc332008-07-09 08:17:15 +02002632 on high Ethernet traffic.
stroese53cf9432003-06-05 15:39:44 +00002633 Defaults to 4 if not defined.
2634
Wolfgang Denkea882ba2010-06-20 23:33:59 +02002635- CONFIG_ENV_MAX_ENTRIES
2636
Wolfgang Denk071bc922010-10-27 22:48:30 +02002637 Maximum number of entries in the hash table that is used
2638 internally to store the environment settings. The default
2639 setting is supposed to be generous and should work in most
2640 cases. This setting can be used to tune behaviour; see
2641 lib/hashtable.c for details.
Wolfgang Denkea882ba2010-06-20 23:33:59 +02002642
Joe Hershberger25980902012-12-11 22:16:31 -06002643- CONFIG_ENV_FLAGS_LIST_DEFAULT
2644- CONFIG_ENV_FLAGS_LIST_STATIC
Robert P. J. Day1bce2ae2013-09-16 07:15:45 -04002645 Enable validation of the values given to environment variables when
Joe Hershberger25980902012-12-11 22:16:31 -06002646 calling env set. Variables can be restricted to only decimal,
2647 hexadecimal, or boolean. If CONFIG_CMD_NET is also defined,
2648 the variables can also be restricted to IP address or MAC address.
2649
2650 The format of the list is:
2651 type_attribute = [s|d|x|b|i|m]
Jeremiah Mahlerb445bbb2015-01-04 18:56:50 -08002652 access_attribute = [a|r|o|c]
2653 attributes = type_attribute[access_attribute]
Joe Hershberger25980902012-12-11 22:16:31 -06002654 entry = variable_name[:attributes]
2655 list = entry[,list]
2656
2657 The type attributes are:
2658 s - String (default)
2659 d - Decimal
2660 x - Hexadecimal
2661 b - Boolean ([1yYtT|0nNfF])
2662 i - IP address
2663 m - MAC address
2664
Joe Hershberger267541f2012-12-11 22:16:34 -06002665 The access attributes are:
2666 a - Any (default)
2667 r - Read-only
2668 o - Write-once
2669 c - Change-default
2670
Joe Hershberger25980902012-12-11 22:16:31 -06002671 - CONFIG_ENV_FLAGS_LIST_DEFAULT
2672 Define this to a list (string) to define the ".flags"
Jeremiah Mahlerb445bbb2015-01-04 18:56:50 -08002673 environment variable in the default or embedded environment.
Joe Hershberger25980902012-12-11 22:16:31 -06002674
2675 - CONFIG_ENV_FLAGS_LIST_STATIC
2676 Define this to a list (string) to define validation that
2677 should be done if an entry is not found in the ".flags"
2678 environment variable. To override a setting in the static
2679 list, simply add an entry for the same variable name to the
2680 ".flags" variable.
2681
Joe Hershbergerbdf1fe42015-05-20 14:27:20 -05002682 If CONFIG_REGEX is defined, the variable_name above is evaluated as a
2683 regular expression. This allows multiple variables to define the same
2684 flags without explicitly listing them for each variable.
2685
wdenkc6097192002-11-03 00:24:07 +00002686The following definitions that deal with the placement and management
2687of environment data (variable area); in general, we support the
2688following configurations:
2689
Mike Frysingerc3eb3fe2011-07-08 10:44:25 +00002690- CONFIG_BUILD_ENVCRC:
2691
2692 Builds up envcrc with the target environment so that external utils
2693 may easily extract it and embed it in final U-Boot images.
2694
wdenkc6097192002-11-03 00:24:07 +00002695BE CAREFUL! The first access to the environment happens quite early
Jeremiah Mahlerb445bbb2015-01-04 18:56:50 -08002696in U-Boot initialization (when we try to get the setting of for the
Marcel Ziswiler11ccc332008-07-09 08:17:15 +02002697console baudrate). You *MUST* have mapped your NVRAM area then, or
wdenkc6097192002-11-03 00:24:07 +00002698U-Boot will hang.
2699
2700Please note that even with NVRAM we still use a copy of the
2701environment in RAM: we could work on NVRAM directly, but we want to
2702keep settings there always unmodified except somebody uses "saveenv"
2703to save the current settings.
2704
Liu Gang0a85a9e2012-03-08 00:33:20 +00002705BE CAREFUL! For some special cases, the local device can not use
2706"saveenv" command. For example, the local device will get the
Liu Gangfc54c7f2012-08-09 05:10:01 +00002707environment stored in a remote NOR flash by SRIO or PCIE link,
2708but it can not erase, write this NOR flash by SRIO or PCIE interface.
Liu Gang0a85a9e2012-03-08 00:33:20 +00002709
Guennadi Liakhovetskib74ab732009-05-18 16:07:22 +02002710- CONFIG_NAND_ENV_DST
2711
2712 Defines address in RAM to which the nand_spl code should copy the
2713 environment. If redundant environment is used, it will be copied to
2714 CONFIG_NAND_ENV_DST + CONFIG_ENV_SIZE.
2715
Bruce Adlere881cb52007-11-02 13:15:42 -07002716Please note that the environment is read-only until the monitor
wdenkc6097192002-11-03 00:24:07 +00002717has been relocated to RAM and a RAM copy of the environment has been
Simon Glass00caae62017-08-03 12:22:12 -06002718created; also, when using EEPROM you will have to use env_get_f()
wdenkc6097192002-11-03 00:24:07 +00002719until then to read environment variables.
2720
wdenk85ec0bc2003-03-31 16:34:49 +00002721The environment is protected by a CRC32 checksum. Before the monitor
2722is relocated into RAM, as a result of a bad CRC you will be working
2723with the compiled-in default environment - *silently*!!! [This is
2724necessary, because the first environment variable we need is the
2725"baudrate" setting for the console - if we have a bad CRC, we don't
2726have any device yet where we could complain.]
wdenkc6097192002-11-03 00:24:07 +00002727
2728Note: once the monitor has been relocated, then it will complain if
2729the default environment is used; a new CRC is computed as soon as you
wdenk85ec0bc2003-03-31 16:34:49 +00002730use the "saveenv" command to store a valid environment.
wdenkc6097192002-11-03 00:24:07 +00002731
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002732- CONFIG_SYS_FAULT_ECHO_LINK_DOWN:
wdenk42d1f032003-10-15 23:53:47 +00002733 Echo the inverted Ethernet link state to the fault LED.
wdenkfc3e2162003-10-08 22:33:00 +00002734
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002735 Note: If this option is active, then CONFIG_SYS_FAULT_MII_ADDR
wdenkfc3e2162003-10-08 22:33:00 +00002736 also needs to be defined.
2737
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002738- CONFIG_SYS_FAULT_MII_ADDR:
wdenk42d1f032003-10-15 23:53:47 +00002739 MII address of the PHY to check for the Ethernet link state.
wdenkc6097192002-11-03 00:24:07 +00002740
Ron Madridf5675aa2009-02-18 14:30:44 -08002741- CONFIG_NS16550_MIN_FUNCTIONS:
2742 Define this if you desire to only have use of the NS16550_init
2743 and NS16550_putc functions for the serial driver located at
2744 drivers/serial/ns16550.c. This option is useful for saving
2745 space for already greatly restricted images, including but not
2746 limited to NAND_SPL configurations.
2747
Simon Glassb2b92f52012-11-30 13:01:18 +00002748- CONFIG_DISPLAY_BOARDINFO
2749 Display information about the board that U-Boot is running on
2750 when U-Boot starts up. The board function checkboard() is called
2751 to do this.
2752
Simon Glasse2e3e2b2012-11-30 13:01:19 +00002753- CONFIG_DISPLAY_BOARDINFO_LATE
2754 Similar to the previous option, but display this information
2755 later, once stdio is running and output goes to the LCD, if
2756 present.
2757
Sascha Silbefeb85802013-08-11 16:40:43 +02002758- CONFIG_BOARD_SIZE_LIMIT:
2759 Maximum size of the U-Boot image. When defined, the
2760 build system checks that the actual size does not
2761 exceed it.
2762
wdenkc6097192002-11-03 00:24:07 +00002763Low Level (hardware related) configuration options:
wdenkdc7c9a12003-03-26 06:55:25 +00002764---------------------------------------------------
wdenkc6097192002-11-03 00:24:07 +00002765
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002766- CONFIG_SYS_CACHELINE_SIZE:
wdenkc6097192002-11-03 00:24:07 +00002767 Cache Line Size of the CPU.
2768
Timur Tabie46fedf2011-08-04 18:03:41 -05002769- CONFIG_SYS_CCSRBAR_DEFAULT:
2770 Default (power-on reset) physical address of CCSR on Freescale
2771 PowerPC SOCs.
2772
2773- CONFIG_SYS_CCSRBAR:
2774 Virtual address of CCSR. On a 32-bit build, this is typically
2775 the same value as CONFIG_SYS_CCSRBAR_DEFAULT.
2776
Timur Tabie46fedf2011-08-04 18:03:41 -05002777- CONFIG_SYS_CCSRBAR_PHYS:
2778 Physical address of CCSR. CCSR can be relocated to a new
2779 physical address, if desired. In this case, this macro should
Wolfgang Denkc0f40852011-10-26 10:21:21 +00002780 be set to that address. Otherwise, it should be set to the
Timur Tabie46fedf2011-08-04 18:03:41 -05002781 same value as CONFIG_SYS_CCSRBAR_DEFAULT. For example, CCSR
2782 is typically relocated on 36-bit builds. It is recommended
2783 that this macro be defined via the _HIGH and _LOW macros:
2784
2785 #define CONFIG_SYS_CCSRBAR_PHYS ((CONFIG_SYS_CCSRBAR_PHYS_HIGH
2786 * 1ull) << 32 | CONFIG_SYS_CCSRBAR_PHYS_LOW)
2787
2788- CONFIG_SYS_CCSRBAR_PHYS_HIGH:
Wolfgang Denk4cf26092011-10-07 09:58:21 +02002789 Bits 33-36 of CONFIG_SYS_CCSRBAR_PHYS. This value is typically
2790 either 0 (32-bit build) or 0xF (36-bit build). This macro is
Timur Tabie46fedf2011-08-04 18:03:41 -05002791 used in assembly code, so it must not contain typecasts or
2792 integer size suffixes (e.g. "ULL").
2793
2794- CONFIG_SYS_CCSRBAR_PHYS_LOW:
2795 Lower 32-bits of CONFIG_SYS_CCSRBAR_PHYS. This macro is
2796 used in assembly code, so it must not contain typecasts or
2797 integer size suffixes (e.g. "ULL").
2798
2799- CONFIG_SYS_CCSR_DO_NOT_RELOCATE:
2800 If this macro is defined, then CONFIG_SYS_CCSRBAR_PHYS will be
2801 forced to a value that ensures that CCSR is not relocated.
2802
Macpaul Lin0abddf82011-04-11 20:45:32 +00002803- CONFIG_IDE_AHB:
2804 Most IDE controllers were designed to be connected with PCI
2805 interface. Only few of them were designed for AHB interface.
2806 When software is doing ATA command and data transfer to
2807 IDE devices through IDE-AHB controller, some additional
2808 registers accessing to these kind of IDE-AHB controller
Jeremiah Mahlerb445bbb2015-01-04 18:56:50 -08002809 is required.
Macpaul Lin0abddf82011-04-11 20:45:32 +00002810
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002811- CONFIG_SYS_IMMR: Physical address of the Internal Memory.
wdenkefe2a4d2004-12-16 21:44:03 +00002812 DO NOT CHANGE unless you know exactly what you're
Christophe Leroy907208c2017-07-06 10:23:22 +02002813 doing! (11-4) [MPC8xx systems only]
wdenkc6097192002-11-03 00:24:07 +00002814
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002815- CONFIG_SYS_INIT_RAM_ADDR:
wdenkc6097192002-11-03 00:24:07 +00002816
wdenk7152b1d2003-09-05 23:19:14 +00002817 Start address of memory area that can be used for
wdenkc6097192002-11-03 00:24:07 +00002818 initial data and stack; please note that this must be
2819 writable memory that is working WITHOUT special
2820 initialization, i. e. you CANNOT use normal RAM which
2821 will become available only after programming the
2822 memory controller and running certain initialization
2823 sequences.
2824
2825 U-Boot uses the following memory types:
Christophe Leroy907208c2017-07-06 10:23:22 +02002826 - MPC8xx: IMMR (internal memory of the CPU)
wdenkc6097192002-11-03 00:24:07 +00002827
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002828- CONFIG_SYS_GBL_DATA_OFFSET:
wdenkc6097192002-11-03 00:24:07 +00002829
2830 Offset of the initial data structure in the memory
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002831 area defined by CONFIG_SYS_INIT_RAM_ADDR. Usually
2832 CONFIG_SYS_GBL_DATA_OFFSET is chosen such that the initial
wdenkc6097192002-11-03 00:24:07 +00002833 data is located at the end of the available space
Wolfgang Denk553f0982010-10-26 13:32:32 +02002834 (sometimes written as (CONFIG_SYS_INIT_RAM_SIZE -
Simon Glassacd51f92016-10-02 18:01:06 -06002835 GENERATED_GBL_DATA_SIZE), and the initial stack is just
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002836 below that area (growing from (CONFIG_SYS_INIT_RAM_ADDR +
2837 CONFIG_SYS_GBL_DATA_OFFSET) downward.
wdenkc6097192002-11-03 00:24:07 +00002838
2839 Note:
2840 On the MPC824X (or other systems that use the data
2841 cache for initial memory) the address chosen for
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002842 CONFIG_SYS_INIT_RAM_ADDR is basically arbitrary - it must
wdenkc6097192002-11-03 00:24:07 +00002843 point to an otherwise UNUSED address space between
2844 the top of RAM and the start of the PCI space.
2845
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002846- CONFIG_SYS_SCCR: System Clock and reset Control Register (15-27)
wdenkc6097192002-11-03 00:24:07 +00002847
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002848- CONFIG_SYS_OR_TIMING_SDRAM:
wdenkc6097192002-11-03 00:24:07 +00002849 SDRAM timing
2850
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002851- CONFIG_SYS_MAMR_PTA:
wdenkc6097192002-11-03 00:24:07 +00002852 periodic timer for refresh
2853
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002854- FLASH_BASE0_PRELIM, FLASH_BASE1_PRELIM, CONFIG_SYS_REMAP_OR_AM,
2855 CONFIG_SYS_PRELIM_OR_AM, CONFIG_SYS_OR_TIMING_FLASH, CONFIG_SYS_OR0_REMAP,
2856 CONFIG_SYS_OR0_PRELIM, CONFIG_SYS_BR0_PRELIM, CONFIG_SYS_OR1_REMAP, CONFIG_SYS_OR1_PRELIM,
2857 CONFIG_SYS_BR1_PRELIM:
wdenkc6097192002-11-03 00:24:07 +00002858 Memory Controller Definitions: BR0/1 and OR0/1 (FLASH)
2859
2860- SDRAM_BASE2_PRELIM, SDRAM_BASE3_PRELIM, SDRAM_MAX_SIZE,
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002861 CONFIG_SYS_OR_TIMING_SDRAM, CONFIG_SYS_OR2_PRELIM, CONFIG_SYS_BR2_PRELIM,
2862 CONFIG_SYS_OR3_PRELIM, CONFIG_SYS_BR3_PRELIM:
wdenkc6097192002-11-03 00:24:07 +00002863 Memory Controller Definitions: BR2/3 and OR2/3 (SDRAM)
2864
Andrew Sharp69fd2d32012-08-29 14:16:32 +00002865- CONFIG_PCI_ENUM_ONLY
Jeremiah Mahlerb445bbb2015-01-04 18:56:50 -08002866 Only scan through and get the devices on the buses.
Andrew Sharp69fd2d32012-08-29 14:16:32 +00002867 Don't do any setup work, presumably because someone or
2868 something has already done it, and we don't need to do it
2869 a second time. Useful for platforms that are pre-booted
2870 by coreboot or similar.
2871
Gabor Juhos842033e2013-05-30 07:06:12 +00002872- CONFIG_PCI_INDIRECT_BRIDGE:
2873 Enable support for indirect PCI bridges.
2874
Kumar Galaa09b9b62010-12-30 12:09:53 -06002875- CONFIG_SYS_SRIO:
2876 Chip has SRIO or not
2877
2878- CONFIG_SRIO1:
2879 Board has SRIO 1 port available
2880
2881- CONFIG_SRIO2:
2882 Board has SRIO 2 port available
2883
Liu Gangc8b28152013-05-07 16:30:46 +08002884- CONFIG_SRIO_PCIE_BOOT_MASTER
2885 Board can support master function for Boot from SRIO and PCIE
2886
Kumar Galaa09b9b62010-12-30 12:09:53 -06002887- CONFIG_SYS_SRIOn_MEM_VIRT:
2888 Virtual Address of SRIO port 'n' memory region
2889
Simon Glass62f9b652019-11-14 12:57:09 -07002890- CONFIG_SYS_SRIOn_MEM_PHYxS:
Kumar Galaa09b9b62010-12-30 12:09:53 -06002891 Physical Address of SRIO port 'n' memory region
2892
2893- CONFIG_SYS_SRIOn_MEM_SIZE:
2894 Size of SRIO port 'n' memory region
2895
Fabio Estevam66bd1842013-04-11 09:35:34 +00002896- CONFIG_SYS_NAND_BUSWIDTH_16BIT
2897 Defined to tell the NAND controller that the NAND chip is using
2898 a 16 bit bus.
2899 Not all NAND drivers use this symbol.
Fabio Estevama430e912013-04-11 09:35:35 +00002900 Example of drivers that use it:
Miquel Raynala430fa02018-08-16 17:30:07 +02002901 - drivers/mtd/nand/raw/ndfc.c
2902 - drivers/mtd/nand/raw/mxc_nand.c
Alex Watermaneced4622011-05-19 15:08:36 -04002903
2904- CONFIG_SYS_NDFC_EBC0_CFG
2905 Sets the EBC0_CFG register for the NDFC. If not defined
2906 a default value will be used.
2907
Ben Warrenbb99ad62006-09-07 16:50:54 -04002908- CONFIG_SPD_EEPROM
Wolfgang Denk218ca722008-03-26 10:40:12 +01002909 Get DDR timing information from an I2C EEPROM. Common
2910 with pluggable memory modules such as SODIMMs
2911
Ben Warrenbb99ad62006-09-07 16:50:54 -04002912 SPD_EEPROM_ADDRESS
2913 I2C address of the SPD EEPROM
2914
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002915- CONFIG_SYS_SPD_BUS_NUM
Wolfgang Denk218ca722008-03-26 10:40:12 +01002916 If SPD EEPROM is on an I2C bus other than the first
2917 one, specify here. Note that the value must resolve
2918 to something your driver can deal with.
Ben Warrenbb99ad62006-09-07 16:50:54 -04002919
York Sun1b3e3c42011-06-07 09:42:16 +08002920- CONFIG_SYS_DDR_RAW_TIMING
2921 Get DDR timing information from other than SPD. Common with
2922 soldered DDR chips onboard without SPD. DDR raw timing
2923 parameters are extracted from datasheet and hard-coded into
2924 header files or board specific files.
2925
York Sun6f5e1dc2011-09-16 13:21:35 -07002926- CONFIG_FSL_DDR_INTERACTIVE
2927 Enable interactive DDR debugging. See doc/README.fsl-ddr.
2928
York Sune32d59a2015-01-06 13:18:55 -08002929- CONFIG_FSL_DDR_SYNC_REFRESH
2930 Enable sync of refresh for multiple controllers.
2931
York Sun4516ff82015-03-19 09:30:28 -07002932- CONFIG_FSL_DDR_BIST
2933 Enable built-in memory test for Freescale DDR controllers.
2934
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02002935- CONFIG_SYS_83XX_DDR_USES_CS0
Wolfgang Denk218ca722008-03-26 10:40:12 +01002936 Only for 83xx systems. If specified, then DDR should
2937 be configured using CS0 and CS1 instead of CS2 and CS3.
Timur Tabi2ad6b512006-10-31 18:44:42 -06002938
wdenkc26e4542004-04-18 10:13:26 +00002939- CONFIG_RMII
2940 Enable RMII mode for all FECs.
2941 Note that this is a global option, we can't
2942 have one FEC in standard MII mode and another in RMII mode.
2943
wdenk5cf91d62004-04-23 20:32:05 +00002944- CONFIG_CRC32_VERIFY
2945 Add a verify option to the crc32 command.
2946 The syntax is:
2947
2948 => crc32 -v <address> <count> <crc32>
2949
2950 Where address/count indicate a memory area
2951 and crc32 is the correct crc32 which the
2952 area should have.
2953
wdenk56523f12004-07-11 17:40:54 +00002954- CONFIG_LOOPW
2955 Add the "loopw" memory command. This only takes effect if
Simon Glass493f4202017-08-04 16:34:27 -06002956 the memory commands are activated globally (CONFIG_CMD_MEMORY).
wdenk56523f12004-07-11 17:40:54 +00002957
Joel Johnson72732312020-01-29 09:17:18 -07002958- CONFIG_CMD_MX_CYCLIC
stroese7b466642004-12-16 18:46:55 +00002959 Add the "mdc" and "mwc" memory commands. These are cyclic
2960 "md/mw" commands.
2961 Examples:
2962
wdenkefe2a4d2004-12-16 21:44:03 +00002963 => mdc.b 10 4 500
stroese7b466642004-12-16 18:46:55 +00002964 This command will print 4 bytes (10,11,12,13) each 500 ms.
2965
wdenkefe2a4d2004-12-16 21:44:03 +00002966 => mwc.l 100 12345678 10
stroese7b466642004-12-16 18:46:55 +00002967 This command will write 12345678 to address 100 all 10 ms.
2968
wdenkefe2a4d2004-12-16 21:44:03 +00002969 This only takes effect if the memory commands are activated
Simon Glass493f4202017-08-04 16:34:27 -06002970 globally (CONFIG_CMD_MEMORY).
stroese7b466642004-12-16 18:46:55 +00002971
wdenk8aa1a2d2005-04-04 12:44:11 +00002972- CONFIG_SKIP_LOWLEVEL_INIT
Rick Chen3fafced2017-12-26 13:55:59 +08002973 [ARM, NDS32, MIPS, RISC-V only] If this variable is defined, then certain
Wolfgang Denk844f07d2010-11-27 23:30:56 +01002974 low level initializations (like setting up the memory
2975 controller) are omitted and/or U-Boot does not
2976 relocate itself into RAM.
wdenk8aa1a2d2005-04-04 12:44:11 +00002977
Wolfgang Denk844f07d2010-11-27 23:30:56 +01002978 Normally this variable MUST NOT be defined. The only
2979 exception is when U-Boot is loaded (to RAM) by some
2980 other boot loader or by a debugger which performs
2981 these initializations itself.
wdenk8aa1a2d2005-04-04 12:44:11 +00002982
Simon Glassb5bd0982016-05-05 07:28:06 -06002983- CONFIG_SKIP_LOWLEVEL_INIT_ONLY
2984 [ARM926EJ-S only] This allows just the call to lowlevel_init()
yeongjun Kim90211f72016-07-20 22:56:12 +09002985 to be skipped. The normal CP15 init (such as enabling the
Simon Glassb5bd0982016-05-05 07:28:06 -06002986 instruction cache) is still performed.
2987
Aneesh V401bb302011-07-13 05:11:07 +00002988- CONFIG_SPL_BUILD
Thomas Hebb32f2ca22019-11-13 18:18:03 -08002989 Set when the currently-running compilation is for an artifact
2990 that will end up in the SPL (as opposed to the TPL or U-Boot
2991 proper). Code that needs stage-specific behavior should check
2992 this.
wdenk400558b2005-04-02 23:52:25 +00002993
Ying Zhang3aa29de2013-08-16 15:16:15 +08002994- CONFIG_TPL_BUILD
Thomas Hebb32f2ca22019-11-13 18:18:03 -08002995 Set when the currently-running compilation is for an artifact
2996 that will end up in the TPL (as opposed to the SPL or U-Boot
2997 proper). Code that needs stage-specific behavior should check
2998 this.
Ying Zhang3aa29de2013-08-16 15:16:15 +08002999
Ying Zhang5df572f2013-05-20 14:07:23 +08003000- CONFIG_SYS_MPC85XX_NO_RESETVEC
3001 Only for 85xx systems. If this variable is specified, the section
3002 .resetvec is not kept and the section .bootpg is placed in the
3003 previous 4k of the .text section.
3004
Simon Glass4213fc22013-02-24 17:33:14 +00003005- CONFIG_ARCH_MAP_SYSMEM
3006 Generally U-Boot (and in particular the md command) uses
3007 effective address. It is therefore not necessary to regard
3008 U-Boot address as virtual addresses that need to be translated
3009 to physical addresses. However, sandbox requires this, since
3010 it maintains its own little RAM buffer which contains all
3011 addressable memory. This option causes some memory accesses
3012 to be mapped through map_sysmem() / unmap_sysmem().
3013
Simon Glass588a13f2013-02-14 04:18:54 +00003014- CONFIG_X86_RESET_VECTOR
3015 If defined, the x86 reset vector code is included. This is not
3016 needed when U-Boot is running from Coreboot.
Gabe Blackb16f5212012-11-27 21:08:06 +00003017
Karicheri, Muralidharan999d7d32014-04-04 13:16:50 -04003018- CONFIG_SYS_NAND_NO_SUBPAGE_WRITE
3019 Option to disable subpage write in NAND driver
3020 driver that uses this:
Miquel Raynala430fa02018-08-16 17:30:07 +02003021 drivers/mtd/nand/raw/davinci_nand.c
Karicheri, Muralidharan999d7d32014-04-04 13:16:50 -04003022
Timur Tabif2717b42011-11-22 09:21:25 -06003023Freescale QE/FMAN Firmware Support:
3024-----------------------------------
3025
3026The Freescale QUICCEngine (QE) and Frame Manager (FMAN) both support the
3027loading of "firmware", which is encoded in the QE firmware binary format.
3028This firmware often needs to be loaded during U-Boot booting, so macros
3029are used to identify the storage device (NOR flash, SPI, etc) and the address
3030within that device.
3031
Zhao Qiangdcf1d772014-03-21 16:21:44 +08003032- CONFIG_SYS_FMAN_FW_ADDR
3033 The address in the storage device where the FMAN microcode is located. The
Tom Rinicc1e98b2019-05-12 07:59:12 -04003034 meaning of this address depends on which CONFIG_SYS_QE_FMAN_FW_IN_xxx macro
Zhao Qiangdcf1d772014-03-21 16:21:44 +08003035 is also specified.
3036
3037- CONFIG_SYS_QE_FW_ADDR
3038 The address in the storage device where the QE microcode is located. The
Tom Rinicc1e98b2019-05-12 07:59:12 -04003039 meaning of this address depends on which CONFIG_SYS_QE_FMAN_FW_IN_xxx macro
Timur Tabif2717b42011-11-22 09:21:25 -06003040 is also specified.
3041
3042- CONFIG_SYS_QE_FMAN_FW_LENGTH
3043 The maximum possible size of the firmware. The firmware binary format
3044 has a field that specifies the actual size of the firmware, but it
3045 might not be possible to read any part of the firmware unless some
3046 local storage is allocated to hold the entire firmware first.
3047
3048- CONFIG_SYS_QE_FMAN_FW_IN_NOR
3049 Specifies that QE/FMAN firmware is located in NOR flash, mapped as
3050 normal addressable memory via the LBC. CONFIG_SYS_FMAN_FW_ADDR is the
3051 virtual address in NOR flash.
3052
3053- CONFIG_SYS_QE_FMAN_FW_IN_NAND
3054 Specifies that QE/FMAN firmware is located in NAND flash.
3055 CONFIG_SYS_FMAN_FW_ADDR is the offset within NAND flash.
3056
3057- CONFIG_SYS_QE_FMAN_FW_IN_MMC
3058 Specifies that QE/FMAN firmware is located on the primary SD/MMC
3059 device. CONFIG_SYS_FMAN_FW_ADDR is the byte offset on that device.
3060
Liu Gang292dc6c2012-03-08 00:33:18 +00003061- CONFIG_SYS_QE_FMAN_FW_IN_REMOTE
3062 Specifies that QE/FMAN firmware is located in the remote (master)
3063 memory space. CONFIG_SYS_FMAN_FW_ADDR is a virtual address which
Liu Gangfc54c7f2012-08-09 05:10:01 +00003064 can be mapped from slave TLB->slave LAW->slave SRIO or PCIE outbound
3065 window->master inbound window->master LAW->the ucode address in
3066 master's memory space.
Timur Tabif2717b42011-11-22 09:21:25 -06003067
J. German Riverab940ca62014-06-23 15:15:55 -07003068Freescale Layerscape Management Complex Firmware Support:
3069---------------------------------------------------------
3070The Freescale Layerscape Management Complex (MC) supports the loading of
3071"firmware".
3072This firmware often needs to be loaded during U-Boot booting, so macros
3073are used to identify the storage device (NOR flash, SPI, etc) and the address
3074within that device.
3075
3076- CONFIG_FSL_MC_ENET
3077 Enable the MC driver for Layerscape SoCs.
3078
Prabhakar Kushwaha5c055082015-06-02 10:55:52 +05303079Freescale Layerscape Debug Server Support:
3080-------------------------------------------
3081The Freescale Layerscape Debug Server Support supports the loading of
3082"Debug Server firmware" and triggering SP boot-rom.
3083This firmware often needs to be loaded during U-Boot booting.
3084
York Sunc0492142015-12-07 11:08:58 -08003085- CONFIG_SYS_MC_RSV_MEM_ALIGN
3086 Define alignment of reserved memory MC requires
Prabhakar Kushwaha5c055082015-06-02 10:55:52 +05303087
Paul Kocialkowskif3f431a2015-07-26 18:48:15 +02003088Reproducible builds
3089-------------------
3090
3091In order to achieve reproducible builds, timestamps used in the U-Boot build
3092process have to be set to a fixed value.
3093
3094This is done using the SOURCE_DATE_EPOCH environment variable.
3095SOURCE_DATE_EPOCH is to be set on the build host's shell, not as a configuration
3096option for U-Boot or an environment variable in U-Boot.
3097
3098SOURCE_DATE_EPOCH should be set to a number of seconds since the epoch, in UTC.
3099
wdenkc6097192002-11-03 00:24:07 +00003100Building the Software:
3101======================
3102
Wolfgang Denk218ca722008-03-26 10:40:12 +01003103Building U-Boot has been tested in several native build environments
3104and in many different cross environments. Of course we cannot support
3105all possibly existing versions of cross development tools in all
3106(potentially obsolete) versions. In case of tool chain problems we
3107recommend to use the ELDK (see http://www.denx.de/wiki/DULG/ELDK)
3108which is extensively used to build and test U-Boot.
wdenkc6097192002-11-03 00:24:07 +00003109
Wolfgang Denk218ca722008-03-26 10:40:12 +01003110If you are not using a native environment, it is assumed that you
3111have GNU cross compiling tools available in your path. In this case,
3112you must set the environment variable CROSS_COMPILE in your shell.
3113Note that no changes to the Makefile or any other source files are
3114necessary. For example using the ELDK on a 4xx CPU, please enter:
wdenkc6097192002-11-03 00:24:07 +00003115
Wolfgang Denk218ca722008-03-26 10:40:12 +01003116 $ CROSS_COMPILE=ppc_4xx-
3117 $ export CROSS_COMPILE
wdenkc6097192002-11-03 00:24:07 +00003118
Wolfgang Denk218ca722008-03-26 10:40:12 +01003119U-Boot is intended to be simple to build. After installing the
3120sources you must configure U-Boot for one specific board type. This
wdenkc6097192002-11-03 00:24:07 +00003121is done by typing:
3122
Holger Freytherab584d62014-08-04 09:26:05 +02003123 make NAME_defconfig
wdenkc6097192002-11-03 00:24:07 +00003124
Holger Freytherab584d62014-08-04 09:26:05 +02003125where "NAME_defconfig" is the name of one of the existing configu-
Heinrich Schuchardtecb3a0a2020-02-24 18:36:30 +01003126rations; see configs/*_defconfig for supported names.
wdenk54387ac2003-10-08 22:45:44 +00003127
Heinrich Schuchardtecb3a0a2020-02-24 18:36:30 +01003128Note: for some boards special configuration names may exist; check if
wdenk2729af92004-05-03 20:45:30 +00003129 additional information is available from the board vendor; for
3130 instance, the TQM823L systems are available without (standard)
3131 or with LCD support. You can select such additional "features"
Marcel Ziswiler11ccc332008-07-09 08:17:15 +02003132 when choosing the configuration, i. e.
wdenkc6097192002-11-03 00:24:07 +00003133
Holger Freytherab584d62014-08-04 09:26:05 +02003134 make TQM823L_defconfig
wdenk2729af92004-05-03 20:45:30 +00003135 - will configure for a plain TQM823L, i. e. no LCD support
wdenkc6097192002-11-03 00:24:07 +00003136
Holger Freytherab584d62014-08-04 09:26:05 +02003137 make TQM823L_LCD_defconfig
wdenk2729af92004-05-03 20:45:30 +00003138 - will configure for a TQM823L with U-Boot console on LCD
wdenkc6097192002-11-03 00:24:07 +00003139
wdenk2729af92004-05-03 20:45:30 +00003140 etc.
wdenkc6097192002-11-03 00:24:07 +00003141
wdenkc6097192002-11-03 00:24:07 +00003142
wdenk2729af92004-05-03 20:45:30 +00003143Finally, type "make all", and you should get some working U-Boot
3144images ready for download to / installation on your system:
wdenkc6097192002-11-03 00:24:07 +00003145
wdenk2729af92004-05-03 20:45:30 +00003146- "u-boot.bin" is a raw binary image
3147- "u-boot" is an image in ELF binary format
3148- "u-boot.srec" is in Motorola S-Record format
wdenkc6097192002-11-03 00:24:07 +00003149
Marian Balakowiczbaf31242006-09-07 17:25:40 +02003150By default the build is performed locally and the objects are saved
3151in the source directory. One of the two methods can be used to change
3152this behavior and build U-Boot to some external directory:
3153
31541. Add O= to the make command line invocations:
3155
3156 make O=/tmp/build distclean
Holger Freytherab584d62014-08-04 09:26:05 +02003157 make O=/tmp/build NAME_defconfig
Marian Balakowiczbaf31242006-09-07 17:25:40 +02003158 make O=/tmp/build all
3159
Timo Ketolaadbba992014-11-06 14:39:05 +020031602. Set environment variable KBUILD_OUTPUT to point to the desired location:
Marian Balakowiczbaf31242006-09-07 17:25:40 +02003161
Timo Ketolaadbba992014-11-06 14:39:05 +02003162 export KBUILD_OUTPUT=/tmp/build
Marian Balakowiczbaf31242006-09-07 17:25:40 +02003163 make distclean
Holger Freytherab584d62014-08-04 09:26:05 +02003164 make NAME_defconfig
Marian Balakowiczbaf31242006-09-07 17:25:40 +02003165 make all
3166
Timo Ketolaadbba992014-11-06 14:39:05 +02003167Note that the command line "O=" setting overrides the KBUILD_OUTPUT environment
Marian Balakowiczbaf31242006-09-07 17:25:40 +02003168variable.
3169
Daniel Schwierzeck215bb1c2018-01-26 16:31:04 +01003170User specific CPPFLAGS, AFLAGS and CFLAGS can be passed to the compiler by
3171setting the according environment variables KCPPFLAGS, KAFLAGS and KCFLAGS.
3172For example to treat all compiler warnings as errors:
3173
3174 make KCFLAGS=-Werror
wdenkc6097192002-11-03 00:24:07 +00003175
wdenk2729af92004-05-03 20:45:30 +00003176Please be aware that the Makefiles assume you are using GNU make, so
3177for instance on NetBSD you might need to use "gmake" instead of
3178native "make".
wdenkc6097192002-11-03 00:24:07 +00003179
wdenkc6097192002-11-03 00:24:07 +00003180
wdenk2729af92004-05-03 20:45:30 +00003181If the system board that you have is not listed, then you will need
3182to port U-Boot to your hardware platform. To do this, follow these
3183steps:
wdenkc6097192002-11-03 00:24:07 +00003184
Phil Sutter3c1496c2015-12-25 14:41:18 +010031851. Create a new directory to hold your board specific code. Add any
wdenk2729af92004-05-03 20:45:30 +00003186 files you need. In your board directory, you will need at least
Phil Sutter3c1496c2015-12-25 14:41:18 +01003187 the "Makefile" and a "<board>.c".
31882. Create a new configuration file "include/configs/<board>.h" for
3189 your board.
wdenk2729af92004-05-03 20:45:30 +000031903. If you're porting U-Boot to a new CPU, then also create a new
3191 directory to hold your CPU specific code. Add any files you need.
Holger Freytherab584d62014-08-04 09:26:05 +020031924. Run "make <board>_defconfig" with your new name.
wdenk2729af92004-05-03 20:45:30 +000031935. Type "make", and you should get a working "u-boot.srec" file
3194 to be installed on your target system.
31956. Debug and solve any problems that might arise.
3196 [Of course, this last step is much harder than it sounds.]
wdenkc6097192002-11-03 00:24:07 +00003197
wdenkc6097192002-11-03 00:24:07 +00003198
wdenk2729af92004-05-03 20:45:30 +00003199Testing of U-Boot Modifications, Ports to New Hardware, etc.:
3200==============================================================
wdenkc6097192002-11-03 00:24:07 +00003201
Wolfgang Denk218ca722008-03-26 10:40:12 +01003202If you have modified U-Boot sources (for instance added a new board
3203or support for new devices, a new CPU, etc.) you are expected to
wdenk2729af92004-05-03 20:45:30 +00003204provide feedback to the other developers. The feedback normally takes
Thomas Hebb32f2ca22019-11-13 18:18:03 -08003205the form of a "patch", i.e. a context diff against a certain (latest
Wolfgang Denk218ca722008-03-26 10:40:12 +01003206official or latest in the git repository) version of U-Boot sources.
wdenkc6097192002-11-03 00:24:07 +00003207
Wolfgang Denk218ca722008-03-26 10:40:12 +01003208But before you submit such a patch, please verify that your modifi-
3209cation did not break existing code. At least make sure that *ALL* of
wdenk2729af92004-05-03 20:45:30 +00003210the supported boards compile WITHOUT ANY compiler warnings. To do so,
Simon Glass6de80f22016-07-27 20:33:08 -06003211just run the buildman script (tools/buildman/buildman), which will
3212configure and build U-Boot for ALL supported system. Be warned, this
3213will take a while. Please see the buildman README, or run 'buildman -H'
3214for documentation.
Marian Balakowiczbaf31242006-09-07 17:25:40 +02003215
3216
wdenk2729af92004-05-03 20:45:30 +00003217See also "U-Boot Porting Guide" below.
wdenkc6097192002-11-03 00:24:07 +00003218
wdenkc6097192002-11-03 00:24:07 +00003219
wdenk2729af92004-05-03 20:45:30 +00003220Monitor Commands - Overview:
3221============================
wdenkc6097192002-11-03 00:24:07 +00003222
wdenk2729af92004-05-03 20:45:30 +00003223go - start application at address 'addr'
3224run - run commands in an environment variable
3225bootm - boot application image from memory
3226bootp - boot image via network using BootP/TFTP protocol
Marek Vasut44f074c2012-03-14 21:52:45 +00003227bootz - boot zImage from memory
wdenk2729af92004-05-03 20:45:30 +00003228tftpboot- boot image via network using TFTP protocol
3229 and env variables "ipaddr" and "serverip"
3230 (and eventually "gatewayip")
Simon Glass1fb7cd42011-10-24 18:00:07 +00003231tftpput - upload a file via network using TFTP protocol
wdenk2729af92004-05-03 20:45:30 +00003232rarpboot- boot image via network using RARP/TFTP protocol
3233diskboot- boot from IDE devicebootd - boot default, i.e., run 'bootcmd'
3234loads - load S-Record file over serial line
3235loadb - load binary file over serial line (kermit mode)
3236md - memory display
3237mm - memory modify (auto-incrementing)
3238nm - memory modify (constant address)
3239mw - memory write (fill)
Simon Glassbdded202020-06-02 19:26:49 -06003240ms - memory search
wdenk2729af92004-05-03 20:45:30 +00003241cp - memory copy
3242cmp - memory compare
3243crc32 - checksum calculation
Peter Tyser0f89c542009-04-18 22:34:03 -05003244i2c - I2C sub-system
wdenk2729af92004-05-03 20:45:30 +00003245sspi - SPI utility commands
3246base - print or set address offset
3247printenv- print environment variables
3248setenv - set environment variables
3249saveenv - save environment variables to persistent storage
3250protect - enable or disable FLASH write protection
3251erase - erase FLASH memory
3252flinfo - print FLASH memory information
Karl O. Pinc10635af2012-08-03 05:57:21 +00003253nand - NAND memory operations (see doc/README.nand)
wdenk2729af92004-05-03 20:45:30 +00003254bdinfo - print Board Info structure
3255iminfo - print header information for application image
3256coninfo - print console devices and informations
3257ide - IDE sub-system
3258loop - infinite loop on address range
wdenk56523f12004-07-11 17:40:54 +00003259loopw - infinite write loop on address range
wdenk2729af92004-05-03 20:45:30 +00003260mtest - simple RAM test
3261icache - enable or disable instruction cache
3262dcache - enable or disable data cache
3263reset - Perform RESET of the CPU
3264echo - echo args to console
3265version - print monitor version
3266help - print online help
3267? - alias for 'help'
wdenkc6097192002-11-03 00:24:07 +00003268
wdenkc6097192002-11-03 00:24:07 +00003269
wdenk2729af92004-05-03 20:45:30 +00003270Monitor Commands - Detailed Description:
3271========================================
wdenkc6097192002-11-03 00:24:07 +00003272
wdenk2729af92004-05-03 20:45:30 +00003273TODO.
wdenkc6097192002-11-03 00:24:07 +00003274
wdenk2729af92004-05-03 20:45:30 +00003275For now: just type "help <command>".
wdenkc6097192002-11-03 00:24:07 +00003276
3277
wdenk2729af92004-05-03 20:45:30 +00003278Environment Variables:
3279======================
wdenkc6097192002-11-03 00:24:07 +00003280
wdenk2729af92004-05-03 20:45:30 +00003281U-Boot supports user configuration using Environment Variables which
3282can be made persistent by saving to Flash memory.
wdenkc6097192002-11-03 00:24:07 +00003283
wdenk2729af92004-05-03 20:45:30 +00003284Environment Variables are set using "setenv", printed using
3285"printenv", and saved to Flash using "saveenv". Using "setenv"
3286without a value can be used to delete a variable from the
3287environment. As long as you don't save the environment you are
3288working with an in-memory copy. In case the Flash area containing the
3289environment is erased by accident, a default environment is provided.
wdenkc6097192002-11-03 00:24:07 +00003290
Wolfgang Denkc96f86e2010-01-17 23:55:53 +01003291Some configuration options can be set using Environment Variables.
3292
3293List of environment variables (most likely not complete):
wdenkc6097192002-11-03 00:24:07 +00003294
wdenk2729af92004-05-03 20:45:30 +00003295 baudrate - see CONFIG_BAUDRATE
wdenkc6097192002-11-03 00:24:07 +00003296
wdenk2729af92004-05-03 20:45:30 +00003297 bootdelay - see CONFIG_BOOTDELAY
wdenkc6097192002-11-03 00:24:07 +00003298
wdenk2729af92004-05-03 20:45:30 +00003299 bootcmd - see CONFIG_BOOTCOMMAND
wdenkc6097192002-11-03 00:24:07 +00003300
wdenk2729af92004-05-03 20:45:30 +00003301 bootargs - Boot arguments when booting an RTOS image
wdenkc6097192002-11-03 00:24:07 +00003302
wdenk2729af92004-05-03 20:45:30 +00003303 bootfile - Name of the image to load with TFTP
wdenkc6097192002-11-03 00:24:07 +00003304
Bartlomiej Sieka7d721e32008-04-14 15:44:16 +02003305 bootm_low - Memory range available for image processing in the bootm
3306 command can be restricted. This variable is given as
3307 a hexadecimal number and defines lowest address allowed
3308 for use by the bootm command. See also "bootm_size"
3309 environment variable. Address defined by "bootm_low" is
3310 also the base of the initial memory mapping for the Linux
Grant Likelyc3624e62011-03-28 09:58:43 +00003311 kernel -- see the description of CONFIG_SYS_BOOTMAPSZ and
3312 bootm_mapsize.
3313
Wolfgang Denkc0f40852011-10-26 10:21:21 +00003314 bootm_mapsize - Size of the initial memory mapping for the Linux kernel.
Grant Likelyc3624e62011-03-28 09:58:43 +00003315 This variable is given as a hexadecimal number and it
3316 defines the size of the memory region starting at base
3317 address bootm_low that is accessible by the Linux kernel
3318 during early boot. If unset, CONFIG_SYS_BOOTMAPSZ is used
3319 as the default value if it is defined, and bootm_size is
3320 used otherwise.
Bartlomiej Sieka7d721e32008-04-14 15:44:16 +02003321
3322 bootm_size - Memory range available for image processing in the bootm
3323 command can be restricted. This variable is given as
3324 a hexadecimal number and defines the size of the region
3325 allowed for use by the bootm command. See also "bootm_low"
3326 environment variable.
3327
Simon Glass88fa4be2019-07-20 20:51:17 -06003328 bootstopkeysha256, bootdelaykey, bootstopkey - See README.autoboot
3329
Bartlomiej Sieka4bae9092008-10-01 15:26:31 +02003330 updatefile - Location of the software update file on a TFTP server, used
3331 by the automatic software update feature. Please refer to
3332 documentation in doc/README.update for more details.
3333
wdenk2729af92004-05-03 20:45:30 +00003334 autoload - if set to "no" (any string beginning with 'n'),
3335 "bootp" will just load perform a lookup of the
3336 configuration from the BOOTP server, but not try to
3337 load any image using TFTP
wdenkc6097192002-11-03 00:24:07 +00003338
wdenk2729af92004-05-03 20:45:30 +00003339 autostart - if set to "yes", an image loaded using the "bootp",
3340 "rarpboot", "tftpboot" or "diskboot" commands will
3341 be automatically started (by internally calling
3342 "bootm")
wdenkc6097192002-11-03 00:24:07 +00003343
wdenk2729af92004-05-03 20:45:30 +00003344 If set to "no", a standalone image passed to the
3345 "bootm" command will be copied to the load address
3346 (and eventually uncompressed), but NOT be started.
3347 This can be used to load and uncompress arbitrary
3348 data.
wdenkc6097192002-11-03 00:24:07 +00003349
David A. Longa28afca2011-07-09 16:40:19 -04003350 fdt_high - if set this restricts the maximum address that the
3351 flattened device tree will be copied into upon boot.
Shawn Guofa34f6b2012-01-09 21:54:08 +00003352 For example, if you have a system with 1 GB memory
3353 at physical address 0x10000000, while Linux kernel
3354 only recognizes the first 704 MB as low memory, you
3355 may need to set fdt_high as 0x3C000000 to have the
3356 device tree blob be copied to the maximum address
3357 of the 704 MB low memory, so that Linux kernel can
3358 access it during the boot procedure.
3359
David A. Longa28afca2011-07-09 16:40:19 -04003360 If this is set to the special value 0xFFFFFFFF then
3361 the fdt will not be copied at all on boot. For this
3362 to work it must reside in writable memory, have
3363 sufficient padding on the end of it for u-boot to
3364 add the information it needs into it, and the memory
3365 must be accessible by the kernel.
3366
Simon Glasseea63e02011-10-24 19:15:34 +00003367 fdtcontroladdr- if set this is the address of the control flattened
3368 device tree used by U-Boot when CONFIG_OF_CONTROL is
3369 defined.
3370
wdenk17ea1172004-06-06 21:51:03 +00003371 i2cfast - (PPC405GP|PPC405EP only)
3372 if set to 'y' configures Linux I2C driver for fast
3373 mode (400kHZ). This environment variable is used in
3374 initialization code. So, for changes to be effective
3375 it must be saved and board must be reset.
3376
wdenk2729af92004-05-03 20:45:30 +00003377 initrd_high - restrict positioning of initrd images:
3378 If this variable is not set, initrd images will be
3379 copied to the highest possible address in RAM; this
3380 is usually what you want since it allows for
3381 maximum initrd size. If for some reason you want to
3382 make sure that the initrd image is loaded below the
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02003383 CONFIG_SYS_BOOTMAPSZ limit, you can set this environment
wdenk2729af92004-05-03 20:45:30 +00003384 variable to a value of "no" or "off" or "0".
3385 Alternatively, you can set it to a maximum upper
3386 address to use (U-Boot will still check that it
3387 does not overwrite the U-Boot stack and data).
wdenkc6097192002-11-03 00:24:07 +00003388
wdenk2729af92004-05-03 20:45:30 +00003389 For instance, when you have a system with 16 MB
3390 RAM, and want to reserve 4 MB from use by Linux,
3391 you can do this by adding "mem=12M" to the value of
3392 the "bootargs" variable. However, now you must make
3393 sure that the initrd image is placed in the first
3394 12 MB as well - this can be done with
wdenkc6097192002-11-03 00:24:07 +00003395
wdenk2729af92004-05-03 20:45:30 +00003396 setenv initrd_high 00c00000
wdenkc6097192002-11-03 00:24:07 +00003397
wdenk2729af92004-05-03 20:45:30 +00003398 If you set initrd_high to 0xFFFFFFFF, this is an
3399 indication to U-Boot that all addresses are legal
3400 for the Linux kernel, including addresses in flash
3401 memory. In this case U-Boot will NOT COPY the
3402 ramdisk at all. This may be useful to reduce the
3403 boot time on your system, but requires that this
3404 feature is supported by your Linux kernel.
wdenk4a6fd342003-04-12 23:38:12 +00003405
wdenk2729af92004-05-03 20:45:30 +00003406 ipaddr - IP address; needed for tftpboot command
wdenkc6097192002-11-03 00:24:07 +00003407
wdenk2729af92004-05-03 20:45:30 +00003408 loadaddr - Default load address for commands like "bootp",
3409 "rarpboot", "tftpboot", "loadb" or "diskboot"
wdenkc6097192002-11-03 00:24:07 +00003410
wdenk2729af92004-05-03 20:45:30 +00003411 loads_echo - see CONFIG_LOADS_ECHO
wdenkc6097192002-11-03 00:24:07 +00003412
wdenk2729af92004-05-03 20:45:30 +00003413 serverip - TFTP server IP address; needed for tftpboot command
wdenk38b99262003-05-23 23:18:21 +00003414
wdenk2729af92004-05-03 20:45:30 +00003415 bootretry - see CONFIG_BOOT_RETRY_TIME
wdenkc6097192002-11-03 00:24:07 +00003416
wdenk2729af92004-05-03 20:45:30 +00003417 bootdelaykey - see CONFIG_AUTOBOOT_DELAY_STR
wdenkc6097192002-11-03 00:24:07 +00003418
wdenk2729af92004-05-03 20:45:30 +00003419 bootstopkey - see CONFIG_AUTOBOOT_STOP_STR
wdenkc6097192002-11-03 00:24:07 +00003420
Mike Frysingere2a53452011-10-02 10:01:27 +00003421 ethprime - controls which interface is used first.
wdenkc6097192002-11-03 00:24:07 +00003422
Mike Frysingere2a53452011-10-02 10:01:27 +00003423 ethact - controls which interface is currently active.
3424 For example you can do the following
wdenkc6097192002-11-03 00:24:07 +00003425
Heiko Schocher48690d82010-07-20 17:45:02 +02003426 => setenv ethact FEC
3427 => ping 192.168.0.1 # traffic sent on FEC
3428 => setenv ethact SCC
3429 => ping 10.0.0.1 # traffic sent on SCC
wdenkc6097192002-11-03 00:24:07 +00003430
Matthias Fuchse1692572008-01-17 07:45:05 +01003431 ethrotate - When set to "no" U-Boot does not go through all
3432 available network interfaces.
3433 It just stays at the currently selected interface.
3434
Wolfgang Denkc96f86e2010-01-17 23:55:53 +01003435 netretry - When set to "no" each network operation will
wdenk2729af92004-05-03 20:45:30 +00003436 either succeed or fail without retrying.
3437 When set to "once" the network operation will
3438 fail when all the available network interfaces
3439 are tried once without success.
3440 Useful on scripts which control the retry operation
3441 themselves.
wdenkc6097192002-11-03 00:24:07 +00003442
Jean-Christophe PLAGNIOL-VILLARDb4e2f892009-01-31 09:53:39 +01003443 npe_ucode - set load address for the NPE microcode
Jean-Christophe PLAGNIOL-VILLARDa1cf0272008-01-07 08:41:34 +01003444
Jeremiah Mahlerb445bbb2015-01-04 18:56:50 -08003445 silent_linux - If set then Linux will be told to boot silently, by
Simon Glass8d51aac2013-07-16 20:10:00 -07003446 changing the console to be empty. If "yes" it will be
3447 made silent. If "no" it will not be made silent. If
3448 unset, then it will be made silent if the U-Boot console
3449 is silent.
3450
Albert ARIBAUD \(3ADEV\)f5fb7342015-10-12 00:02:57 +02003451 tftpsrcp - If this is set, the value is used for TFTP's
Wolfgang Denkecb0ccd2005-09-24 22:37:32 +02003452 UDP source port.
3453
Albert ARIBAUD \(3ADEV\)f5fb7342015-10-12 00:02:57 +02003454 tftpdstp - If this is set, the value is used for TFTP's UDP
Wolfgang Denk28cb9372005-09-24 23:25:46 +02003455 destination port instead of the Well Know Port 69.
3456
Wolfgang Denkc96f86e2010-01-17 23:55:53 +01003457 tftpblocksize - Block size to use for TFTP transfers; if not set,
3458 we use the TFTP server's default block size
3459
3460 tftptimeout - Retransmission timeout for TFTP packets (in milli-
3461 seconds, minimum value is 1000 = 1 second). Defines
3462 when a packet is considered to be lost so it has to
3463 be retransmitted. The default is 5000 = 5 seconds.
3464 Lowering this value may make downloads succeed
3465 faster in networks with high packet loss rates or
3466 with unreliable TFTP servers.
3467
Albert ARIBAUD \(3ADEV\)f5fb7342015-10-12 00:02:57 +02003468 tftptimeoutcountmax - maximum count of TFTP timeouts (no
3469 unit, minimum value = 0). Defines how many timeouts
3470 can happen during a single file transfer before that
3471 transfer is aborted. The default is 10, and 0 means
3472 'no timeouts allowed'. Increasing this value may help
3473 downloads succeed with high packet loss rates, or with
3474 unreliable TFTP servers or client hardware.
3475
Wolfgang Denkc96f86e2010-01-17 23:55:53 +01003476 vlan - When set to a value < 4095 the traffic over
Marcel Ziswiler11ccc332008-07-09 08:17:15 +02003477 Ethernet is encapsulated/received over 802.1q
wdenk2729af92004-05-03 20:45:30 +00003478 VLAN tagged frames.
wdenka3d991b2004-04-15 21:48:45 +00003479
Alexandre Messier50768f52016-02-01 17:08:57 -05003480 bootpretryperiod - Period during which BOOTP/DHCP sends retries.
3481 Unsigned value, in milliseconds. If not set, the period will
3482 be either the default (28000), or a value based on
3483 CONFIG_NET_RETRY_COUNT, if defined. This value has
3484 precedence over the valu based on CONFIG_NET_RETRY_COUNT.
3485
Simon Glassbdded202020-06-02 19:26:49 -06003486 memmatches - Number of matches found by the last 'ms' command, in hex
3487
3488 memaddr - Address of the last match found by the 'ms' command, in hex,
3489 or 0 if none
3490
3491 mempos - Index position of the last match found by the 'ms' command,
3492 in units of the size (.b, .w, .l) of the search
3493
3494
Jason Hobbsdc0b7b02011-08-31 05:37:28 +00003495The following image location variables contain the location of images
3496used in booting. The "Image" column gives the role of the image and is
3497not an environment variable name. The other columns are environment
3498variable names. "File Name" gives the name of the file on a TFTP
3499server, "RAM Address" gives the location in RAM the image will be
3500loaded to, and "Flash Location" gives the image's address in NOR
3501flash or offset in NAND flash.
3502
3503*Note* - these variables don't have to be defined for all boards, some
Fabio Estevamaed9fed2015-04-25 18:53:10 -03003504boards currently use other variables for these purposes, and some
Jason Hobbsdc0b7b02011-08-31 05:37:28 +00003505boards use these variables for other purposes.
3506
Wolfgang Denkc0f40852011-10-26 10:21:21 +00003507Image File Name RAM Address Flash Location
3508----- --------- ----------- --------------
3509u-boot u-boot u-boot_addr_r u-boot_addr
3510Linux kernel bootfile kernel_addr_r kernel_addr
3511device tree blob fdtfile fdt_addr_r fdt_addr
3512ramdisk ramdiskfile ramdisk_addr_r ramdisk_addr
Jason Hobbsdc0b7b02011-08-31 05:37:28 +00003513
wdenk2729af92004-05-03 20:45:30 +00003514The following environment variables may be used and automatically
3515updated by the network boot commands ("bootp" and "rarpboot"),
3516depending the information provided by your boot server:
wdenka3d991b2004-04-15 21:48:45 +00003517
wdenk2729af92004-05-03 20:45:30 +00003518 bootfile - see above
3519 dnsip - IP address of your Domain Name Server
3520 dnsip2 - IP address of your secondary Domain Name Server
3521 gatewayip - IP address of the Gateway (Router) to use
3522 hostname - Target hostname
3523 ipaddr - see above
3524 netmask - Subnet Mask
3525 rootpath - Pathname of the root filesystem on the NFS server
3526 serverip - see above
wdenka3d991b2004-04-15 21:48:45 +00003527
wdenka3d991b2004-04-15 21:48:45 +00003528
wdenk2729af92004-05-03 20:45:30 +00003529There are two special Environment Variables:
wdenkc6097192002-11-03 00:24:07 +00003530
wdenk2729af92004-05-03 20:45:30 +00003531 serial# - contains hardware identification information such
3532 as type string and/or serial number
3533 ethaddr - Ethernet address
wdenkc6097192002-11-03 00:24:07 +00003534
wdenk2729af92004-05-03 20:45:30 +00003535These variables can be set only once (usually during manufacturing of
3536the board). U-Boot refuses to delete or overwrite these variables
3537once they have been set once.
wdenkc6097192002-11-03 00:24:07 +00003538
3539
wdenk2729af92004-05-03 20:45:30 +00003540Further special Environment Variables:
wdenkc6097192002-11-03 00:24:07 +00003541
wdenk2729af92004-05-03 20:45:30 +00003542 ver - Contains the U-Boot version string as printed
3543 with the "version" command. This variable is
3544 readonly (see CONFIG_VERSION_VARIABLE).
wdenkc6097192002-11-03 00:24:07 +00003545
wdenkc6097192002-11-03 00:24:07 +00003546
wdenk2729af92004-05-03 20:45:30 +00003547Please note that changes to some configuration parameters may take
3548only effect after the next boot (yes, that's just like Windoze :-).
wdenkc6097192002-11-03 00:24:07 +00003549
stroesec1551ea2003-04-04 15:53:41 +00003550
Joe Hershberger170ab112012-12-11 22:16:24 -06003551Callback functions for environment variables:
3552---------------------------------------------
3553
3554For some environment variables, the behavior of u-boot needs to change
Jeremiah Mahlerb445bbb2015-01-04 18:56:50 -08003555when their values are changed. This functionality allows functions to
Joe Hershberger170ab112012-12-11 22:16:24 -06003556be associated with arbitrary variables. On creation, overwrite, or
3557deletion, the callback will provide the opportunity for some side
3558effect to happen or for the change to be rejected.
3559
3560The callbacks are named and associated with a function using the
3561U_BOOT_ENV_CALLBACK macro in your board or driver code.
3562
3563These callbacks are associated with variables in one of two ways. The
3564static list can be added to by defining CONFIG_ENV_CALLBACK_LIST_STATIC
3565in the board configuration to a string that defines a list of
3566associations. The list must be in the following format:
3567
3568 entry = variable_name[:callback_name]
3569 list = entry[,list]
3570
3571If the callback name is not specified, then the callback is deleted.
3572Spaces are also allowed anywhere in the list.
3573
3574Callbacks can also be associated by defining the ".callbacks" variable
3575with the same list format above. Any association in ".callbacks" will
3576override any association in the static list. You can define
3577CONFIG_ENV_CALLBACK_LIST_DEFAULT to a list (string) to define the
Jeremiah Mahlerb445bbb2015-01-04 18:56:50 -08003578".callbacks" environment variable in the default or embedded environment.
Joe Hershberger170ab112012-12-11 22:16:24 -06003579
Joe Hershbergerbdf1fe42015-05-20 14:27:20 -05003580If CONFIG_REGEX is defined, the variable_name above is evaluated as a
3581regular expression. This allows multiple variables to be connected to
3582the same callback without explicitly listing them all out.
3583
Heinrich Schuchardt1b040472018-07-29 11:08:14 +02003584The signature of the callback functions is:
3585
3586 int callback(const char *name, const char *value, enum env_op op, int flags)
3587
3588* name - changed environment variable
3589* value - new value of the environment variable
3590* op - operation (create, overwrite, or delete)
3591* flags - attributes of the environment variable change, see flags H_* in
3592 include/search.h
3593
3594The return value is 0 if the variable change is accepted and 1 otherwise.
Joe Hershberger170ab112012-12-11 22:16:24 -06003595
wdenk2729af92004-05-03 20:45:30 +00003596Command Line Parsing:
3597=====================
stroesec1551ea2003-04-04 15:53:41 +00003598
wdenk2729af92004-05-03 20:45:30 +00003599There are two different command line parsers available with U-Boot:
3600the old "simple" one, and the much more powerful "hush" shell:
stroesec1551ea2003-04-04 15:53:41 +00003601
wdenk2729af92004-05-03 20:45:30 +00003602Old, simple command line parser:
3603--------------------------------
wdenkc6097192002-11-03 00:24:07 +00003604
wdenk2729af92004-05-03 20:45:30 +00003605- supports environment variables (through setenv / saveenv commands)
3606- several commands on one line, separated by ';'
Wolfgang Denkfe126d82005-11-20 21:40:11 +01003607- variable substitution using "... ${name} ..." syntax
wdenk2729af92004-05-03 20:45:30 +00003608- special characters ('$', ';') can be escaped by prefixing with '\',
3609 for example:
Wolfgang Denkfe126d82005-11-20 21:40:11 +01003610 setenv bootcmd bootm \${address}
wdenk2729af92004-05-03 20:45:30 +00003611- You can also escape text by enclosing in single apostrophes, for example:
3612 setenv addip 'setenv bootargs $bootargs ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname::off'
wdenkc6097192002-11-03 00:24:07 +00003613
wdenk2729af92004-05-03 20:45:30 +00003614Hush shell:
3615-----------
wdenkf07771c2003-05-28 08:06:31 +00003616
wdenk2729af92004-05-03 20:45:30 +00003617- similar to Bourne shell, with control structures like
3618 if...then...else...fi, for...do...done; while...do...done,
3619 until...do...done, ...
3620- supports environment ("global") variables (through setenv / saveenv
3621 commands) and local shell variables (through standard shell syntax
3622 "name=value"); only environment variables can be used with "run"
3623 command
wdenkf07771c2003-05-28 08:06:31 +00003624
wdenk2729af92004-05-03 20:45:30 +00003625General rules:
3626--------------
wdenkf07771c2003-05-28 08:06:31 +00003627
wdenk2729af92004-05-03 20:45:30 +00003628(1) If a command line (or an environment variable executed by a "run"
3629 command) contains several commands separated by semicolon, and
3630 one of these commands fails, then the remaining commands will be
3631 executed anyway.
wdenkf07771c2003-05-28 08:06:31 +00003632
wdenk2729af92004-05-03 20:45:30 +00003633(2) If you execute several variables with one call to run (i. e.
Marcel Ziswiler11ccc332008-07-09 08:17:15 +02003634 calling run with a list of variables as arguments), any failing
wdenk2729af92004-05-03 20:45:30 +00003635 command will cause "run" to terminate, i. e. the remaining
3636 variables are not executed.
wdenkf07771c2003-05-28 08:06:31 +00003637
wdenk2729af92004-05-03 20:45:30 +00003638Note for Redundant Ethernet Interfaces:
3639=======================================
wdenkf07771c2003-05-28 08:06:31 +00003640
Marcel Ziswiler11ccc332008-07-09 08:17:15 +02003641Some boards come with redundant Ethernet interfaces; U-Boot supports
wdenk2729af92004-05-03 20:45:30 +00003642such configurations and is capable of automatic selection of a
3643"working" interface when needed. MAC assignment works as follows:
wdenkf07771c2003-05-28 08:06:31 +00003644
wdenk2729af92004-05-03 20:45:30 +00003645Network interfaces are numbered eth0, eth1, eth2, ... Corresponding
3646MAC addresses can be stored in the environment as "ethaddr" (=>eth0),
3647"eth1addr" (=>eth1), "eth2addr", ...
wdenkf07771c2003-05-28 08:06:31 +00003648
wdenk2729af92004-05-03 20:45:30 +00003649If the network interface stores some valid MAC address (for instance
3650in SROM), this is used as default address if there is NO correspon-
3651ding setting in the environment; if the corresponding environment
3652variable is set, this overrides the settings in the card; that means:
wdenkf07771c2003-05-28 08:06:31 +00003653
wdenk2729af92004-05-03 20:45:30 +00003654o If the SROM has a valid MAC address, and there is no address in the
3655 environment, the SROM's address is used.
wdenkc6097192002-11-03 00:24:07 +00003656
wdenk2729af92004-05-03 20:45:30 +00003657o If there is no valid address in the SROM, and a definition in the
3658 environment exists, then the value from the environment variable is
3659 used.
wdenkc6097192002-11-03 00:24:07 +00003660
wdenk2729af92004-05-03 20:45:30 +00003661o If both the SROM and the environment contain a MAC address, and
3662 both addresses are the same, this MAC address is used.
wdenkc6097192002-11-03 00:24:07 +00003663
wdenk2729af92004-05-03 20:45:30 +00003664o If both the SROM and the environment contain a MAC address, and the
3665 addresses differ, the value from the environment is used and a
3666 warning is printed.
wdenkc6097192002-11-03 00:24:07 +00003667
wdenk2729af92004-05-03 20:45:30 +00003668o If neither SROM nor the environment contain a MAC address, an error
Joe Hershbergerbef10142015-05-04 14:55:13 -05003669 is raised. If CONFIG_NET_RANDOM_ETHADDR is defined, then in this case
3670 a random, locally-assigned MAC is used.
wdenkc6097192002-11-03 00:24:07 +00003671
Ben Warrenecee9322010-04-26 11:11:46 -07003672If Ethernet drivers implement the 'write_hwaddr' function, valid MAC addresses
Wolfgang Denkc0f40852011-10-26 10:21:21 +00003673will be programmed into hardware as part of the initialization process. This
Ben Warrenecee9322010-04-26 11:11:46 -07003674may be skipped by setting the appropriate 'ethmacskip' environment variable.
3675The naming convention is as follows:
3676"ethmacskip" (=>eth0), "eth1macskip" (=>eth1) etc.
wdenkc6097192002-11-03 00:24:07 +00003677
wdenk2729af92004-05-03 20:45:30 +00003678Image Formats:
3679==============
wdenkc6097192002-11-03 00:24:07 +00003680
Marian Balakowicz3310c542008-03-12 12:13:13 +01003681U-Boot is capable of booting (and performing other auxiliary operations on)
3682images in two formats:
3683
3684New uImage format (FIT)
3685-----------------------
3686
3687Flexible and powerful format based on Flattened Image Tree -- FIT (similar
3688to Flattened Device Tree). It allows the use of images with multiple
3689components (several kernels, ramdisks, etc.), with contents protected by
3690SHA1, MD5 or CRC32. More details are found in the doc/uImage.FIT directory.
3691
3692
3693Old uImage format
3694-----------------
3695
3696Old image format is based on binary files which can be basically anything,
3697preceded by a special header; see the definitions in include/image.h for
3698details; basically, the header defines the following image properties:
wdenkc6097192002-11-03 00:24:07 +00003699
wdenk2729af92004-05-03 20:45:30 +00003700* Target Operating System (Provisions for OpenBSD, NetBSD, FreeBSD,
3701 4.4BSD, Linux, SVR4, Esix, Solaris, Irix, SCO, Dell, NCR, VxWorks,
Peter Tyserf5ed9e32008-09-08 14:56:49 -05003702 LynxOS, pSOS, QNX, RTEMS, INTEGRITY;
3703 Currently supported: Linux, NetBSD, VxWorks, QNX, RTEMS, LynxOS,
3704 INTEGRITY).
Andy Shevchenkodaab59a2017-07-05 16:25:22 +03003705* Target CPU Architecture (Provisions for Alpha, ARM, Intel x86,
Macpaul Linafc1ce82011-10-19 20:41:11 +00003706 IA64, MIPS, NDS32, Nios II, PowerPC, IBM S390, SuperH, Sparc, Sparc 64 Bit;
Andy Shevchenkodaab59a2017-07-05 16:25:22 +03003707 Currently supported: ARM, Intel x86, MIPS, NDS32, Nios II, PowerPC).
wdenk2729af92004-05-03 20:45:30 +00003708* Compression Type (uncompressed, gzip, bzip2)
3709* Load Address
3710* Entry Point
3711* Image Name
3712* Image Timestamp
wdenkc6097192002-11-03 00:24:07 +00003713
wdenk2729af92004-05-03 20:45:30 +00003714The header is marked by a special Magic Number, and both the header
3715and the data portions of the image are secured against corruption by
3716CRC32 checksums.
wdenkc6097192002-11-03 00:24:07 +00003717
wdenkc6097192002-11-03 00:24:07 +00003718
wdenk2729af92004-05-03 20:45:30 +00003719Linux Support:
3720==============
wdenkc6097192002-11-03 00:24:07 +00003721
wdenk2729af92004-05-03 20:45:30 +00003722Although U-Boot should support any OS or standalone application
3723easily, the main focus has always been on Linux during the design of
3724U-Boot.
wdenkc6097192002-11-03 00:24:07 +00003725
wdenk2729af92004-05-03 20:45:30 +00003726U-Boot includes many features that so far have been part of some
3727special "boot loader" code within the Linux kernel. Also, any
3728"initrd" images to be used are no longer part of one big Linux image;
3729instead, kernel and "initrd" are separate images. This implementation
3730serves several purposes:
wdenkc6097192002-11-03 00:24:07 +00003731
wdenk2729af92004-05-03 20:45:30 +00003732- the same features can be used for other OS or standalone
3733 applications (for instance: using compressed images to reduce the
3734 Flash memory footprint)
wdenkc6097192002-11-03 00:24:07 +00003735
wdenk2729af92004-05-03 20:45:30 +00003736- it becomes much easier to port new Linux kernel versions because
3737 lots of low-level, hardware dependent stuff are done by U-Boot
wdenkc6097192002-11-03 00:24:07 +00003738
wdenk2729af92004-05-03 20:45:30 +00003739- the same Linux kernel image can now be used with different "initrd"
3740 images; of course this also means that different kernel images can
3741 be run with the same "initrd". This makes testing easier (you don't
3742 have to build a new "zImage.initrd" Linux image when you just
3743 change a file in your "initrd"). Also, a field-upgrade of the
3744 software is easier now.
wdenkc6097192002-11-03 00:24:07 +00003745
wdenkc6097192002-11-03 00:24:07 +00003746
wdenk2729af92004-05-03 20:45:30 +00003747Linux HOWTO:
3748============
wdenkc6097192002-11-03 00:24:07 +00003749
wdenk2729af92004-05-03 20:45:30 +00003750Porting Linux to U-Boot based systems:
3751---------------------------------------
wdenkc6097192002-11-03 00:24:07 +00003752
wdenk2729af92004-05-03 20:45:30 +00003753U-Boot cannot save you from doing all the necessary modifications to
3754configure the Linux device drivers for use with your target hardware
3755(no, we don't intend to provide a full virtual machine interface to
3756Linux :-).
wdenkc6097192002-11-03 00:24:07 +00003757
Stefan Roesea47a12b2010-04-15 16:07:28 +02003758But now you can ignore ALL boot loader code (in arch/powerpc/mbxboot).
wdenkc6097192002-11-03 00:24:07 +00003759
wdenk2729af92004-05-03 20:45:30 +00003760Just make sure your machine specific header file (for instance
3761include/asm-ppc/tqm8xx.h) includes the same definition of the Board
Markus Heidelberg1dc30692008-09-07 20:18:27 +02003762Information structure as we define in include/asm-<arch>/u-boot.h,
3763and make sure that your definition of IMAP_ADDR uses the same value
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02003764as your U-Boot configuration in CONFIG_SYS_IMMR.
wdenkc6097192002-11-03 00:24:07 +00003765
Simon Glass2eb31b12014-06-11 23:29:46 -06003766Note that U-Boot now has a driver model, a unified model for drivers.
3767If you are adding a new driver, plumb it into driver model. If there
3768is no uclass available, you are encouraged to create one. See
3769doc/driver-model.
3770
wdenkc6097192002-11-03 00:24:07 +00003771
wdenk2729af92004-05-03 20:45:30 +00003772Configuring the Linux kernel:
3773-----------------------------
wdenkc6097192002-11-03 00:24:07 +00003774
wdenk2729af92004-05-03 20:45:30 +00003775No specific requirements for U-Boot. Make sure you have some root
3776device (initial ramdisk, NFS) for your target system.
wdenkc6097192002-11-03 00:24:07 +00003777
wdenkc6097192002-11-03 00:24:07 +00003778
wdenk2729af92004-05-03 20:45:30 +00003779Building a Linux Image:
3780-----------------------
wdenkc6097192002-11-03 00:24:07 +00003781
wdenk2729af92004-05-03 20:45:30 +00003782With U-Boot, "normal" build targets like "zImage" or "bzImage" are
3783not used. If you use recent kernel source, a new build target
3784"uImage" will exist which automatically builds an image usable by
3785U-Boot. Most older kernels also have support for a "pImage" target,
3786which was introduced for our predecessor project PPCBoot and uses a
3787100% compatible format.
wdenkc6097192002-11-03 00:24:07 +00003788
wdenk2729af92004-05-03 20:45:30 +00003789Example:
wdenkc6097192002-11-03 00:24:07 +00003790
Holger Freytherab584d62014-08-04 09:26:05 +02003791 make TQM850L_defconfig
wdenk2729af92004-05-03 20:45:30 +00003792 make oldconfig
3793 make dep
3794 make uImage
wdenkc6097192002-11-03 00:24:07 +00003795
wdenk2729af92004-05-03 20:45:30 +00003796The "uImage" build target uses a special tool (in 'tools/mkimage') to
3797encapsulate a compressed Linux kernel image with header information,
3798CRC32 checksum etc. for use with U-Boot. This is what we are doing:
wdenkc6097192002-11-03 00:24:07 +00003799
wdenk2729af92004-05-03 20:45:30 +00003800* build a standard "vmlinux" kernel image (in ELF binary format):
wdenkc6097192002-11-03 00:24:07 +00003801
wdenk2729af92004-05-03 20:45:30 +00003802* convert the kernel into a raw binary image:
wdenkc6097192002-11-03 00:24:07 +00003803
wdenk2729af92004-05-03 20:45:30 +00003804 ${CROSS_COMPILE}-objcopy -O binary \
3805 -R .note -R .comment \
3806 -S vmlinux linux.bin
wdenkc6097192002-11-03 00:24:07 +00003807
wdenk2729af92004-05-03 20:45:30 +00003808* compress the binary image:
wdenkc6097192002-11-03 00:24:07 +00003809
wdenk2729af92004-05-03 20:45:30 +00003810 gzip -9 linux.bin
wdenkc6097192002-11-03 00:24:07 +00003811
wdenk2729af92004-05-03 20:45:30 +00003812* package compressed binary image for U-Boot:
wdenk24ee89b2002-11-03 17:56:27 +00003813
wdenk2729af92004-05-03 20:45:30 +00003814 mkimage -A ppc -O linux -T kernel -C gzip \
3815 -a 0 -e 0 -n "Linux Kernel Image" \
3816 -d linux.bin.gz uImage
wdenk24ee89b2002-11-03 17:56:27 +00003817
wdenk24ee89b2002-11-03 17:56:27 +00003818
wdenk2729af92004-05-03 20:45:30 +00003819The "mkimage" tool can also be used to create ramdisk images for use
3820with U-Boot, either separated from the Linux kernel image, or
3821combined into one file. "mkimage" encapsulates the images with a 64
3822byte header containing information about target architecture,
3823operating system, image type, compression method, entry points, time
3824stamp, CRC32 checksums, etc.
wdenk24ee89b2002-11-03 17:56:27 +00003825
wdenk2729af92004-05-03 20:45:30 +00003826"mkimage" can be called in two ways: to verify existing images and
3827print the header information, or to build new images.
wdenk24ee89b2002-11-03 17:56:27 +00003828
wdenk2729af92004-05-03 20:45:30 +00003829In the first form (with "-l" option) mkimage lists the information
3830contained in the header of an existing U-Boot image; this includes
3831checksum verification:
wdenk24ee89b2002-11-03 17:56:27 +00003832
wdenk2729af92004-05-03 20:45:30 +00003833 tools/mkimage -l image
3834 -l ==> list image header information
wdenk24ee89b2002-11-03 17:56:27 +00003835
wdenk2729af92004-05-03 20:45:30 +00003836The second form (with "-d" option) is used to build a U-Boot image
3837from a "data file" which is used as image payload:
wdenk24ee89b2002-11-03 17:56:27 +00003838
wdenk2729af92004-05-03 20:45:30 +00003839 tools/mkimage -A arch -O os -T type -C comp -a addr -e ep \
3840 -n name -d data_file image
3841 -A ==> set architecture to 'arch'
3842 -O ==> set operating system to 'os'
3843 -T ==> set image type to 'type'
3844 -C ==> set compression type 'comp'
3845 -a ==> set load address to 'addr' (hex)
3846 -e ==> set entry point to 'ep' (hex)
3847 -n ==> set image name to 'name'
3848 -d ==> use image data from 'datafile'
wdenk24ee89b2002-11-03 17:56:27 +00003849
wdenk69459792004-05-29 16:53:29 +00003850Right now, all Linux kernels for PowerPC systems use the same load
3851address (0x00000000), but the entry point address depends on the
3852kernel version:
wdenkc6097192002-11-03 00:24:07 +00003853
wdenk2729af92004-05-03 20:45:30 +00003854- 2.2.x kernels have the entry point at 0x0000000C,
3855- 2.3.x and later kernels have the entry point at 0x00000000.
wdenkc6097192002-11-03 00:24:07 +00003856
wdenk2729af92004-05-03 20:45:30 +00003857So a typical call to build a U-Boot image would read:
wdenkc6097192002-11-03 00:24:07 +00003858
wdenk2729af92004-05-03 20:45:30 +00003859 -> tools/mkimage -n '2.4.4 kernel for TQM850L' \
3860 > -A ppc -O linux -T kernel -C gzip -a 0 -e 0 \
Stefan Roesea47a12b2010-04-15 16:07:28 +02003861 > -d /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/powerpc/coffboot/vmlinux.gz \
wdenk2729af92004-05-03 20:45:30 +00003862 > examples/uImage.TQM850L
3863 Image Name: 2.4.4 kernel for TQM850L
3864 Created: Wed Jul 19 02:34:59 2000
3865 Image Type: PowerPC Linux Kernel Image (gzip compressed)
3866 Data Size: 335725 Bytes = 327.86 kB = 0.32 MB
3867 Load Address: 0x00000000
3868 Entry Point: 0x00000000
wdenkc6097192002-11-03 00:24:07 +00003869
wdenk2729af92004-05-03 20:45:30 +00003870To verify the contents of the image (or check for corruption):
wdenkc6097192002-11-03 00:24:07 +00003871
wdenk2729af92004-05-03 20:45:30 +00003872 -> tools/mkimage -l examples/uImage.TQM850L
3873 Image Name: 2.4.4 kernel for TQM850L
3874 Created: Wed Jul 19 02:34:59 2000
3875 Image Type: PowerPC Linux Kernel Image (gzip compressed)
3876 Data Size: 335725 Bytes = 327.86 kB = 0.32 MB
3877 Load Address: 0x00000000
3878 Entry Point: 0x00000000
wdenkc6097192002-11-03 00:24:07 +00003879
wdenk2729af92004-05-03 20:45:30 +00003880NOTE: for embedded systems where boot time is critical you can trade
3881speed for memory and install an UNCOMPRESSED image instead: this
3882needs more space in Flash, but boots much faster since it does not
3883need to be uncompressed:
wdenkc6097192002-11-03 00:24:07 +00003884
Stefan Roesea47a12b2010-04-15 16:07:28 +02003885 -> gunzip /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/powerpc/coffboot/vmlinux.gz
wdenk2729af92004-05-03 20:45:30 +00003886 -> tools/mkimage -n '2.4.4 kernel for TQM850L' \
3887 > -A ppc -O linux -T kernel -C none -a 0 -e 0 \
Stefan Roesea47a12b2010-04-15 16:07:28 +02003888 > -d /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/powerpc/coffboot/vmlinux \
wdenk2729af92004-05-03 20:45:30 +00003889 > examples/uImage.TQM850L-uncompressed
3890 Image Name: 2.4.4 kernel for TQM850L
3891 Created: Wed Jul 19 02:34:59 2000
3892 Image Type: PowerPC Linux Kernel Image (uncompressed)
3893 Data Size: 792160 Bytes = 773.59 kB = 0.76 MB
3894 Load Address: 0x00000000
3895 Entry Point: 0x00000000
wdenkc6097192002-11-03 00:24:07 +00003896
wdenkc6097192002-11-03 00:24:07 +00003897
wdenk2729af92004-05-03 20:45:30 +00003898Similar you can build U-Boot images from a 'ramdisk.image.gz' file
3899when your kernel is intended to use an initial ramdisk:
wdenkdb01a2e2004-04-15 23:14:49 +00003900
wdenk2729af92004-05-03 20:45:30 +00003901 -> tools/mkimage -n 'Simple Ramdisk Image' \
3902 > -A ppc -O linux -T ramdisk -C gzip \
3903 > -d /LinuxPPC/images/SIMPLE-ramdisk.image.gz examples/simple-initrd
3904 Image Name: Simple Ramdisk Image
3905 Created: Wed Jan 12 14:01:50 2000
3906 Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
3907 Data Size: 566530 Bytes = 553.25 kB = 0.54 MB
3908 Load Address: 0x00000000
3909 Entry Point: 0x00000000
wdenkdb01a2e2004-04-15 23:14:49 +00003910
Guilherme Maciel Ferreiraa804b5c2013-12-01 12:43:11 -07003911The "dumpimage" is a tool to disassemble images built by mkimage. Its "-i"
3912option performs the converse operation of the mkimage's second form (the "-d"
3913option). Given an image built by mkimage, the dumpimage extracts a "data file"
3914from the image:
3915
Guilherme Maciel Ferreiraf41f5b72015-01-15 02:54:40 -02003916 tools/dumpimage -i image -T type -p position data_file
3917 -i ==> extract from the 'image' a specific 'data_file'
3918 -T ==> set image type to 'type'
3919 -p ==> 'position' (starting at 0) of the 'data_file' inside the 'image'
Guilherme Maciel Ferreiraa804b5c2013-12-01 12:43:11 -07003920
wdenkdb01a2e2004-04-15 23:14:49 +00003921
wdenk2729af92004-05-03 20:45:30 +00003922Installing a Linux Image:
3923-------------------------
wdenkdb01a2e2004-04-15 23:14:49 +00003924
wdenk2729af92004-05-03 20:45:30 +00003925To downloading a U-Boot image over the serial (console) interface,
3926you must convert the image to S-Record format:
wdenkdb01a2e2004-04-15 23:14:49 +00003927
wdenk2729af92004-05-03 20:45:30 +00003928 objcopy -I binary -O srec examples/image examples/image.srec
wdenkdb01a2e2004-04-15 23:14:49 +00003929
wdenk2729af92004-05-03 20:45:30 +00003930The 'objcopy' does not understand the information in the U-Boot
3931image header, so the resulting S-Record file will be relative to
3932address 0x00000000. To load it to a given address, you need to
3933specify the target address as 'offset' parameter with the 'loads'
3934command.
wdenkc6097192002-11-03 00:24:07 +00003935
wdenk2729af92004-05-03 20:45:30 +00003936Example: install the image to address 0x40100000 (which on the
3937TQM8xxL is in the first Flash bank):
wdenkc6097192002-11-03 00:24:07 +00003938
wdenk2729af92004-05-03 20:45:30 +00003939 => erase 40100000 401FFFFF
wdenkc6097192002-11-03 00:24:07 +00003940
wdenk2729af92004-05-03 20:45:30 +00003941 .......... done
3942 Erased 8 sectors
wdenkc6097192002-11-03 00:24:07 +00003943
wdenk2729af92004-05-03 20:45:30 +00003944 => loads 40100000
3945 ## Ready for S-Record download ...
3946 ~>examples/image.srec
3947 1 2 3 4 5 6 7 8 9 10 11 12 13 ...
3948 ...
3949 15989 15990 15991 15992
3950 [file transfer complete]
3951 [connected]
3952 ## Start Addr = 0x00000000
wdenkc6097192002-11-03 00:24:07 +00003953
3954
wdenk2729af92004-05-03 20:45:30 +00003955You can check the success of the download using the 'iminfo' command;
Wolfgang Denk218ca722008-03-26 10:40:12 +01003956this includes a checksum verification so you can be sure no data
wdenk2729af92004-05-03 20:45:30 +00003957corruption happened:
wdenkc6097192002-11-03 00:24:07 +00003958
wdenk2729af92004-05-03 20:45:30 +00003959 => imi 40100000
wdenkc6097192002-11-03 00:24:07 +00003960
wdenk2729af92004-05-03 20:45:30 +00003961 ## Checking Image at 40100000 ...
3962 Image Name: 2.2.13 for initrd on TQM850L
3963 Image Type: PowerPC Linux Kernel Image (gzip compressed)
3964 Data Size: 335725 Bytes = 327 kB = 0 MB
3965 Load Address: 00000000
3966 Entry Point: 0000000c
3967 Verifying Checksum ... OK
wdenkc6097192002-11-03 00:24:07 +00003968
3969
wdenk2729af92004-05-03 20:45:30 +00003970Boot Linux:
3971-----------
wdenkc6097192002-11-03 00:24:07 +00003972
wdenk2729af92004-05-03 20:45:30 +00003973The "bootm" command is used to boot an application that is stored in
3974memory (RAM or Flash). In case of a Linux kernel image, the contents
3975of the "bootargs" environment variable is passed to the kernel as
3976parameters. You can check and modify this variable using the
3977"printenv" and "setenv" commands:
wdenkc6097192002-11-03 00:24:07 +00003978
3979
wdenk2729af92004-05-03 20:45:30 +00003980 => printenv bootargs
3981 bootargs=root=/dev/ram
wdenkc6097192002-11-03 00:24:07 +00003982
wdenk2729af92004-05-03 20:45:30 +00003983 => setenv bootargs root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2
wdenkc6097192002-11-03 00:24:07 +00003984
wdenk2729af92004-05-03 20:45:30 +00003985 => printenv bootargs
3986 bootargs=root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2
wdenkc6097192002-11-03 00:24:07 +00003987
wdenk2729af92004-05-03 20:45:30 +00003988 => bootm 40020000
3989 ## Booting Linux kernel at 40020000 ...
3990 Image Name: 2.2.13 for NFS on TQM850L
3991 Image Type: PowerPC Linux Kernel Image (gzip compressed)
3992 Data Size: 381681 Bytes = 372 kB = 0 MB
3993 Load Address: 00000000
3994 Entry Point: 0000000c
3995 Verifying Checksum ... OK
3996 Uncompressing Kernel Image ... OK
3997 Linux version 2.2.13 (wd@denx.local.net) (gcc version 2.95.2 19991024 (release)) #1 Wed Jul 19 02:35:17 MEST 2000
3998 Boot arguments: root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2
3999 time_init: decrementer frequency = 187500000/60
4000 Calibrating delay loop... 49.77 BogoMIPS
4001 Memory: 15208k available (700k kernel code, 444k data, 32k init) [c0000000,c1000000]
4002 ...
wdenkc6097192002-11-03 00:24:07 +00004003
Marcel Ziswiler11ccc332008-07-09 08:17:15 +02004004If you want to boot a Linux kernel with initial RAM disk, you pass
wdenk2729af92004-05-03 20:45:30 +00004005the memory addresses of both the kernel and the initrd image (PPBCOOT
4006format!) to the "bootm" command:
wdenkc6097192002-11-03 00:24:07 +00004007
wdenk2729af92004-05-03 20:45:30 +00004008 => imi 40100000 40200000
wdenkc6097192002-11-03 00:24:07 +00004009
wdenk2729af92004-05-03 20:45:30 +00004010 ## Checking Image at 40100000 ...
4011 Image Name: 2.2.13 for initrd on TQM850L
4012 Image Type: PowerPC Linux Kernel Image (gzip compressed)
4013 Data Size: 335725 Bytes = 327 kB = 0 MB
4014 Load Address: 00000000
4015 Entry Point: 0000000c
4016 Verifying Checksum ... OK
wdenkc6097192002-11-03 00:24:07 +00004017
wdenk2729af92004-05-03 20:45:30 +00004018 ## Checking Image at 40200000 ...
4019 Image Name: Simple Ramdisk Image
4020 Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
4021 Data Size: 566530 Bytes = 553 kB = 0 MB
4022 Load Address: 00000000
4023 Entry Point: 00000000
4024 Verifying Checksum ... OK
wdenkc6097192002-11-03 00:24:07 +00004025
wdenk2729af92004-05-03 20:45:30 +00004026 => bootm 40100000 40200000
4027 ## Booting Linux kernel at 40100000 ...
4028 Image Name: 2.2.13 for initrd on TQM850L
4029 Image Type: PowerPC Linux Kernel Image (gzip compressed)
4030 Data Size: 335725 Bytes = 327 kB = 0 MB
4031 Load Address: 00000000
4032 Entry Point: 0000000c
4033 Verifying Checksum ... OK
4034 Uncompressing Kernel Image ... OK
4035 ## Loading RAMDisk Image at 40200000 ...
4036 Image Name: Simple Ramdisk Image
4037 Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
4038 Data Size: 566530 Bytes = 553 kB = 0 MB
4039 Load Address: 00000000
4040 Entry Point: 00000000
4041 Verifying Checksum ... OK
4042 Loading Ramdisk ... OK
4043 Linux version 2.2.13 (wd@denx.local.net) (gcc version 2.95.2 19991024 (release)) #1 Wed Jul 19 02:32:08 MEST 2000
4044 Boot arguments: root=/dev/ram
4045 time_init: decrementer frequency = 187500000/60
4046 Calibrating delay loop... 49.77 BogoMIPS
4047 ...
4048 RAMDISK: Compressed image found at block 0
4049 VFS: Mounted root (ext2 filesystem).
wdenkc6097192002-11-03 00:24:07 +00004050
wdenk2729af92004-05-03 20:45:30 +00004051 bash#
wdenkc6097192002-11-03 00:24:07 +00004052
Matthew McClintock02677682006-06-28 10:41:37 -05004053Boot Linux and pass a flat device tree:
4054-----------
4055
4056First, U-Boot must be compiled with the appropriate defines. See the section
4057titled "Linux Kernel Interface" above for a more in depth explanation. The
4058following is an example of how to start a kernel and pass an updated
4059flat device tree:
4060
4061=> print oftaddr
4062oftaddr=0x300000
4063=> print oft
4064oft=oftrees/mpc8540ads.dtb
4065=> tftp $oftaddr $oft
4066Speed: 1000, full duplex
4067Using TSEC0 device
4068TFTP from server 192.168.1.1; our IP address is 192.168.1.101
4069Filename 'oftrees/mpc8540ads.dtb'.
4070Load address: 0x300000
4071Loading: #
4072done
4073Bytes transferred = 4106 (100a hex)
4074=> tftp $loadaddr $bootfile
4075Speed: 1000, full duplex
4076Using TSEC0 device
4077TFTP from server 192.168.1.1; our IP address is 192.168.1.2
4078Filename 'uImage'.
4079Load address: 0x200000
4080Loading:############
4081done
4082Bytes transferred = 1029407 (fb51f hex)
4083=> print loadaddr
4084loadaddr=200000
4085=> print oftaddr
4086oftaddr=0x300000
4087=> bootm $loadaddr - $oftaddr
4088## Booting image at 00200000 ...
Wolfgang Denka9398e02006-11-27 15:32:42 +01004089 Image Name: Linux-2.6.17-dirty
4090 Image Type: PowerPC Linux Kernel Image (gzip compressed)
4091 Data Size: 1029343 Bytes = 1005.2 kB
Matthew McClintock02677682006-06-28 10:41:37 -05004092 Load Address: 00000000
Wolfgang Denka9398e02006-11-27 15:32:42 +01004093 Entry Point: 00000000
Matthew McClintock02677682006-06-28 10:41:37 -05004094 Verifying Checksum ... OK
4095 Uncompressing Kernel Image ... OK
4096Booting using flat device tree at 0x300000
4097Using MPC85xx ADS machine description
4098Memory CAM mapping: CAM0=256Mb, CAM1=256Mb, CAM2=0Mb residual: 0Mb
4099[snip]
4100
4101
wdenk2729af92004-05-03 20:45:30 +00004102More About U-Boot Image Types:
4103------------------------------
wdenk6069ff22003-02-28 00:49:47 +00004104
wdenk2729af92004-05-03 20:45:30 +00004105U-Boot supports the following image types:
wdenk6069ff22003-02-28 00:49:47 +00004106
wdenk2729af92004-05-03 20:45:30 +00004107 "Standalone Programs" are directly runnable in the environment
4108 provided by U-Boot; it is expected that (if they behave
4109 well) you can continue to work in U-Boot after return from
4110 the Standalone Program.
4111 "OS Kernel Images" are usually images of some Embedded OS which
4112 will take over control completely. Usually these programs
4113 will install their own set of exception handlers, device
4114 drivers, set up the MMU, etc. - this means, that you cannot
4115 expect to re-enter U-Boot except by resetting the CPU.
4116 "RAMDisk Images" are more or less just data blocks, and their
4117 parameters (address, size) are passed to an OS kernel that is
4118 being started.
4119 "Multi-File Images" contain several images, typically an OS
4120 (Linux) kernel image and one or more data images like
4121 RAMDisks. This construct is useful for instance when you want
4122 to boot over the network using BOOTP etc., where the boot
4123 server provides just a single image file, but you want to get
4124 for instance an OS kernel and a RAMDisk image.
stroesec1551ea2003-04-04 15:53:41 +00004125
wdenk2729af92004-05-03 20:45:30 +00004126 "Multi-File Images" start with a list of image sizes, each
4127 image size (in bytes) specified by an "uint32_t" in network
4128 byte order. This list is terminated by an "(uint32_t)0".
4129 Immediately after the terminating 0 follow the images, one by
4130 one, all aligned on "uint32_t" boundaries (size rounded up to
4131 a multiple of 4 bytes).
stroesec1551ea2003-04-04 15:53:41 +00004132
wdenk2729af92004-05-03 20:45:30 +00004133 "Firmware Images" are binary images containing firmware (like
4134 U-Boot or FPGA images) which usually will be programmed to
4135 flash memory.
stroesec1551ea2003-04-04 15:53:41 +00004136
wdenk2729af92004-05-03 20:45:30 +00004137 "Script files" are command sequences that will be executed by
4138 U-Boot's command interpreter; this feature is especially
4139 useful when you configure U-Boot to use a real shell (hush)
4140 as command interpreter.
wdenk6069ff22003-02-28 00:49:47 +00004141
Marek Vasut44f074c2012-03-14 21:52:45 +00004142Booting the Linux zImage:
4143-------------------------
4144
4145On some platforms, it's possible to boot Linux zImage. This is done
4146using the "bootz" command. The syntax of "bootz" command is the same
4147as the syntax of "bootm" command.
4148
Tom Rini8ac28562013-05-16 11:40:11 -04004149Note, defining the CONFIG_SUPPORT_RAW_INITRD allows user to supply
Marek Vasut017e1f32012-03-18 11:47:58 +00004150kernel with raw initrd images. The syntax is slightly different, the
4151address of the initrd must be augmented by it's size, in the following
4152format: "<initrd addres>:<initrd size>".
4153
wdenkc6097192002-11-03 00:24:07 +00004154
wdenk2729af92004-05-03 20:45:30 +00004155Standalone HOWTO:
4156=================
wdenkc6097192002-11-03 00:24:07 +00004157
wdenk2729af92004-05-03 20:45:30 +00004158One of the features of U-Boot is that you can dynamically load and
4159run "standalone" applications, which can use some resources of
4160U-Boot like console I/O functions or interrupt services.
wdenkc6097192002-11-03 00:24:07 +00004161
wdenk2729af92004-05-03 20:45:30 +00004162Two simple examples are included with the sources:
wdenkc6097192002-11-03 00:24:07 +00004163
wdenk2729af92004-05-03 20:45:30 +00004164"Hello World" Demo:
4165-------------------
wdenkc6097192002-11-03 00:24:07 +00004166
wdenk2729af92004-05-03 20:45:30 +00004167'examples/hello_world.c' contains a small "Hello World" Demo
4168application; it is automatically compiled when you build U-Boot.
4169It's configured to run at address 0x00040004, so you can play with it
4170like that:
wdenkc6097192002-11-03 00:24:07 +00004171
wdenk2729af92004-05-03 20:45:30 +00004172 => loads
4173 ## Ready for S-Record download ...
4174 ~>examples/hello_world.srec
4175 1 2 3 4 5 6 7 8 9 10 11 ...
4176 [file transfer complete]
4177 [connected]
4178 ## Start Addr = 0x00040004
wdenkc6097192002-11-03 00:24:07 +00004179
wdenk2729af92004-05-03 20:45:30 +00004180 => go 40004 Hello World! This is a test.
4181 ## Starting application at 0x00040004 ...
4182 Hello World
4183 argc = 7
4184 argv[0] = "40004"
4185 argv[1] = "Hello"
4186 argv[2] = "World!"
4187 argv[3] = "This"
4188 argv[4] = "is"
4189 argv[5] = "a"
4190 argv[6] = "test."
4191 argv[7] = "<NULL>"
4192 Hit any key to exit ...
wdenkc6097192002-11-03 00:24:07 +00004193
wdenk2729af92004-05-03 20:45:30 +00004194 ## Application terminated, rc = 0x0
wdenkc6097192002-11-03 00:24:07 +00004195
wdenk2729af92004-05-03 20:45:30 +00004196Another example, which demonstrates how to register a CPM interrupt
4197handler with the U-Boot code, can be found in 'examples/timer.c'.
4198Here, a CPM timer is set up to generate an interrupt every second.
4199The interrupt service routine is trivial, just printing a '.'
4200character, but this is just a demo program. The application can be
4201controlled by the following keys:
wdenkc6097192002-11-03 00:24:07 +00004202
wdenk2729af92004-05-03 20:45:30 +00004203 ? - print current values og the CPM Timer registers
4204 b - enable interrupts and start timer
4205 e - stop timer and disable interrupts
4206 q - quit application
wdenkc6097192002-11-03 00:24:07 +00004207
wdenk2729af92004-05-03 20:45:30 +00004208 => loads
4209 ## Ready for S-Record download ...
4210 ~>examples/timer.srec
4211 1 2 3 4 5 6 7 8 9 10 11 ...
4212 [file transfer complete]
4213 [connected]
4214 ## Start Addr = 0x00040004
wdenkc6097192002-11-03 00:24:07 +00004215
wdenk2729af92004-05-03 20:45:30 +00004216 => go 40004
4217 ## Starting application at 0x00040004 ...
4218 TIMERS=0xfff00980
4219 Using timer 1
4220 tgcr @ 0xfff00980, tmr @ 0xfff00990, trr @ 0xfff00994, tcr @ 0xfff00998, tcn @ 0xfff0099c, ter @ 0xfff009b0
wdenkc6097192002-11-03 00:24:07 +00004221
wdenk2729af92004-05-03 20:45:30 +00004222Hit 'b':
4223 [q, b, e, ?] Set interval 1000000 us
4224 Enabling timer
4225Hit '?':
4226 [q, b, e, ?] ........
4227 tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0xef6, ter=0x0
4228Hit '?':
4229 [q, b, e, ?] .
4230 tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x2ad4, ter=0x0
4231Hit '?':
4232 [q, b, e, ?] .
4233 tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x1efc, ter=0x0
4234Hit '?':
4235 [q, b, e, ?] .
4236 tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x169d, ter=0x0
4237Hit 'e':
4238 [q, b, e, ?] ...Stopping timer
4239Hit 'q':
4240 [q, b, e, ?] ## Application terminated, rc = 0x0
wdenkc6097192002-11-03 00:24:07 +00004241
4242
wdenk2729af92004-05-03 20:45:30 +00004243Minicom warning:
4244================
wdenk85ec0bc2003-03-31 16:34:49 +00004245
wdenk2729af92004-05-03 20:45:30 +00004246Over time, many people have reported problems when trying to use the
4247"minicom" terminal emulation program for serial download. I (wd)
4248consider minicom to be broken, and recommend not to use it. Under
4249Unix, I recommend to use C-Kermit for general purpose use (and
4250especially for kermit binary protocol download ("loadb" command), and
Karl O. Pince53515a2012-10-01 05:11:56 +00004251use "cu" for S-Record download ("loads" command). See
4252http://www.denx.de/wiki/view/DULG/SystemSetup#Section_4.3.
4253for help with kermit.
4254
wdenk85ec0bc2003-03-31 16:34:49 +00004255
wdenk2729af92004-05-03 20:45:30 +00004256Nevertheless, if you absolutely want to use it try adding this
4257configuration to your "File transfer protocols" section:
wdenk52f52c12003-06-19 23:04:19 +00004258
wdenk2729af92004-05-03 20:45:30 +00004259 Name Program Name U/D FullScr IO-Red. Multi
4260 X kermit /usr/bin/kermit -i -l %l -s Y U Y N N
4261 Y kermit /usr/bin/kermit -i -l %l -r N D Y N N
wdenk52f52c12003-06-19 23:04:19 +00004262
4263
wdenk2729af92004-05-03 20:45:30 +00004264NetBSD Notes:
4265=============
wdenkc6097192002-11-03 00:24:07 +00004266
wdenk2729af92004-05-03 20:45:30 +00004267Starting at version 0.9.2, U-Boot supports NetBSD both as host
4268(build U-Boot) and target system (boots NetBSD/mpc8xx).
wdenkc6097192002-11-03 00:24:07 +00004269
wdenk2729af92004-05-03 20:45:30 +00004270Building requires a cross environment; it is known to work on
4271NetBSD/i386 with the cross-powerpc-netbsd-1.3 package (you will also
4272need gmake since the Makefiles are not compatible with BSD make).
4273Note that the cross-powerpc package does not install include files;
4274attempting to build U-Boot will fail because <machine/ansi.h> is
4275missing. This file has to be installed and patched manually:
wdenkc6097192002-11-03 00:24:07 +00004276
wdenk2729af92004-05-03 20:45:30 +00004277 # cd /usr/pkg/cross/powerpc-netbsd/include
4278 # mkdir powerpc
4279 # ln -s powerpc machine
4280 # cp /usr/src/sys/arch/powerpc/include/ansi.h powerpc/ansi.h
4281 # ${EDIT} powerpc/ansi.h ## must remove __va_list, _BSD_VA_LIST
wdenkc6097192002-11-03 00:24:07 +00004282
wdenk2729af92004-05-03 20:45:30 +00004283Native builds *don't* work due to incompatibilities between native
4284and U-Boot include files.
wdenkc6097192002-11-03 00:24:07 +00004285
wdenk2729af92004-05-03 20:45:30 +00004286Booting assumes that (the first part of) the image booted is a
4287stage-2 loader which in turn loads and then invokes the kernel
4288proper. Loader sources will eventually appear in the NetBSD source
4289tree (probably in sys/arc/mpc8xx/stand/u-boot_stage2/); in the
wdenk2a8af182005-04-13 10:02:42 +00004290meantime, see ftp://ftp.denx.de/pub/u-boot/ppcboot_stage2.tar.gz
wdenkc6097192002-11-03 00:24:07 +00004291
4292
wdenk2729af92004-05-03 20:45:30 +00004293Implementation Internals:
4294=========================
wdenkc6097192002-11-03 00:24:07 +00004295
wdenk2729af92004-05-03 20:45:30 +00004296The following is not intended to be a complete description of every
4297implementation detail. However, it should help to understand the
4298inner workings of U-Boot and make it easier to port it to custom
4299hardware.
wdenkc6097192002-11-03 00:24:07 +00004300
4301
wdenk2729af92004-05-03 20:45:30 +00004302Initial Stack, Global Data:
4303---------------------------
wdenkc6097192002-11-03 00:24:07 +00004304
wdenk2729af92004-05-03 20:45:30 +00004305The implementation of U-Boot is complicated by the fact that U-Boot
4306starts running out of ROM (flash memory), usually without access to
4307system RAM (because the memory controller is not initialized yet).
4308This means that we don't have writable Data or BSS segments, and BSS
4309is not initialized as zero. To be able to get a C environment working
4310at all, we have to allocate at least a minimal stack. Implementation
4311options for this are defined and restricted by the CPU used: Some CPU
4312models provide on-chip memory (like the IMMR area on MPC8xx and
4313MPC826x processors), on others (parts of) the data cache can be
4314locked as (mis-) used as memory, etc.
wdenkc6097192002-11-03 00:24:07 +00004315
Wolfgang Denk218ca722008-03-26 10:40:12 +01004316 Chris Hallinan posted a good summary of these issues to the
Wolfgang Denk06682362008-12-30 22:56:11 +01004317 U-Boot mailing list:
wdenk43d96162003-03-06 00:02:04 +00004318
wdenk2729af92004-05-03 20:45:30 +00004319 Subject: RE: [U-Boot-Users] RE: More On Memory Bank x (nothingness)?
4320 From: "Chris Hallinan" <clh@net1plus.com>
4321 Date: Mon, 10 Feb 2003 16:43:46 -0500 (22:43 MET)
4322 ...
wdenk43d96162003-03-06 00:02:04 +00004323
wdenk2729af92004-05-03 20:45:30 +00004324 Correct me if I'm wrong, folks, but the way I understand it
4325 is this: Using DCACHE as initial RAM for Stack, etc, does not
4326 require any physical RAM backing up the cache. The cleverness
4327 is that the cache is being used as a temporary supply of
4328 necessary storage before the SDRAM controller is setup. It's
Marcel Ziswiler11ccc332008-07-09 08:17:15 +02004329 beyond the scope of this list to explain the details, but you
wdenk2729af92004-05-03 20:45:30 +00004330 can see how this works by studying the cache architecture and
4331 operation in the architecture and processor-specific manuals.
wdenk43d96162003-03-06 00:02:04 +00004332
wdenk2729af92004-05-03 20:45:30 +00004333 OCM is On Chip Memory, which I believe the 405GP has 4K. It
4334 is another option for the system designer to use as an
Marcel Ziswiler11ccc332008-07-09 08:17:15 +02004335 initial stack/RAM area prior to SDRAM being available. Either
wdenk2729af92004-05-03 20:45:30 +00004336 option should work for you. Using CS 4 should be fine if your
4337 board designers haven't used it for something that would
4338 cause you grief during the initial boot! It is frequently not
4339 used.
wdenk43d96162003-03-06 00:02:04 +00004340
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02004341 CONFIG_SYS_INIT_RAM_ADDR should be somewhere that won't interfere
wdenk2729af92004-05-03 20:45:30 +00004342 with your processor/board/system design. The default value
4343 you will find in any recent u-boot distribution in
Stefan Roese8a316c92005-08-01 16:49:12 +02004344 walnut.h should work for you. I'd set it to a value larger
wdenk2729af92004-05-03 20:45:30 +00004345 than your SDRAM module. If you have a 64MB SDRAM module, set
4346 it above 400_0000. Just make sure your board has no resources
4347 that are supposed to respond to that address! That code in
4348 start.S has been around a while and should work as is when
4349 you get the config right.
wdenk43d96162003-03-06 00:02:04 +00004350
wdenk2729af92004-05-03 20:45:30 +00004351 -Chris Hallinan
4352 DS4.COM, Inc.
wdenk43d96162003-03-06 00:02:04 +00004353
wdenk2729af92004-05-03 20:45:30 +00004354It is essential to remember this, since it has some impact on the C
4355code for the initialization procedures:
wdenkc6097192002-11-03 00:24:07 +00004356
wdenk2729af92004-05-03 20:45:30 +00004357* Initialized global data (data segment) is read-only. Do not attempt
4358 to write it.
wdenkc6097192002-11-03 00:24:07 +00004359
Jeremiah Mahlerb445bbb2015-01-04 18:56:50 -08004360* Do not use any uninitialized global data (or implicitly initialized
wdenk2729af92004-05-03 20:45:30 +00004361 as zero data - BSS segment) at all - this is undefined, initiali-
4362 zation is performed later (when relocating to RAM).
wdenkc6097192002-11-03 00:24:07 +00004363
wdenk2729af92004-05-03 20:45:30 +00004364* Stack space is very limited. Avoid big data buffers or things like
4365 that.
wdenkc6097192002-11-03 00:24:07 +00004366
wdenk2729af92004-05-03 20:45:30 +00004367Having only the stack as writable memory limits means we cannot use
Jeremiah Mahlerb445bbb2015-01-04 18:56:50 -08004368normal global data to share information between the code. But it
wdenk2729af92004-05-03 20:45:30 +00004369turned out that the implementation of U-Boot can be greatly
4370simplified by making a global data structure (gd_t) available to all
4371functions. We could pass a pointer to this data as argument to _all_
4372functions, but this would bloat the code. Instead we use a feature of
4373the GCC compiler (Global Register Variables) to share the data: we
4374place a pointer (gd) to the global data into a register which we
4375reserve for this purpose.
wdenkc6097192002-11-03 00:24:07 +00004376
wdenk2729af92004-05-03 20:45:30 +00004377When choosing a register for such a purpose we are restricted by the
4378relevant (E)ABI specifications for the current architecture, and by
4379GCC's implementation.
wdenkc6097192002-11-03 00:24:07 +00004380
wdenk2729af92004-05-03 20:45:30 +00004381For PowerPC, the following registers have specific use:
4382 R1: stack pointer
Wolfgang Denke7670f62008-02-14 22:43:22 +01004383 R2: reserved for system use
wdenk2729af92004-05-03 20:45:30 +00004384 R3-R4: parameter passing and return values
4385 R5-R10: parameter passing
4386 R13: small data area pointer
4387 R30: GOT pointer
4388 R31: frame pointer
wdenkc6097192002-11-03 00:24:07 +00004389
Joakim Tjernlunde6bee802010-01-19 14:41:58 +01004390 (U-Boot also uses R12 as internal GOT pointer. r12
4391 is a volatile register so r12 needs to be reset when
4392 going back and forth between asm and C)
wdenkc6097192002-11-03 00:24:07 +00004393
Wolfgang Denke7670f62008-02-14 22:43:22 +01004394 ==> U-Boot will use R2 to hold a pointer to the global data
wdenkc6097192002-11-03 00:24:07 +00004395
wdenk2729af92004-05-03 20:45:30 +00004396 Note: on PPC, we could use a static initializer (since the
4397 address of the global data structure is known at compile time),
4398 but it turned out that reserving a register results in somewhat
4399 smaller code - although the code savings are not that big (on
4400 average for all boards 752 bytes for the whole U-Boot image,
4401 624 text + 127 data).
wdenkc6097192002-11-03 00:24:07 +00004402
wdenk2729af92004-05-03 20:45:30 +00004403On ARM, the following registers are used:
wdenkc6097192002-11-03 00:24:07 +00004404
wdenk2729af92004-05-03 20:45:30 +00004405 R0: function argument word/integer result
4406 R1-R3: function argument word
Jeroen Hofstee12eba1b2013-09-21 14:04:42 +02004407 R9: platform specific
4408 R10: stack limit (used only if stack checking is enabled)
wdenk2729af92004-05-03 20:45:30 +00004409 R11: argument (frame) pointer
4410 R12: temporary workspace
4411 R13: stack pointer
4412 R14: link register
4413 R15: program counter
wdenkc6097192002-11-03 00:24:07 +00004414
Jeroen Hofstee12eba1b2013-09-21 14:04:42 +02004415 ==> U-Boot will use R9 to hold a pointer to the global data
4416
4417 Note: on ARM, only R_ARM_RELATIVE relocations are supported.
wdenkc6097192002-11-03 00:24:07 +00004418
Thomas Chou0df01fd32010-05-21 11:08:03 +08004419On Nios II, the ABI is documented here:
4420 http://www.altera.com/literature/hb/nios2/n2cpu_nii51016.pdf
4421
4422 ==> U-Boot will use gp to hold a pointer to the global data
4423
4424 Note: on Nios II, we give "-G0" option to gcc and don't use gp
4425 to access small data sections, so gp is free.
4426
Macpaul Linafc1ce82011-10-19 20:41:11 +00004427On NDS32, the following registers are used:
4428
4429 R0-R1: argument/return
4430 R2-R5: argument
4431 R15: temporary register for assembler
4432 R16: trampoline register
4433 R28: frame pointer (FP)
4434 R29: global pointer (GP)
4435 R30: link register (LP)
4436 R31: stack pointer (SP)
4437 PC: program counter (PC)
4438
4439 ==> U-Boot will use R10 to hold a pointer to the global data
4440
Wolfgang Denkd87080b2006-03-31 18:32:53 +02004441NOTE: DECLARE_GLOBAL_DATA_PTR must be used with file-global scope,
4442or current versions of GCC may "optimize" the code too much.
wdenkc6097192002-11-03 00:24:07 +00004443
Rick Chen3fafced2017-12-26 13:55:59 +08004444On RISC-V, the following registers are used:
4445
4446 x0: hard-wired zero (zero)
4447 x1: return address (ra)
4448 x2: stack pointer (sp)
4449 x3: global pointer (gp)
4450 x4: thread pointer (tp)
4451 x5: link register (t0)
4452 x8: frame pointer (fp)
4453 x10-x11: arguments/return values (a0-1)
4454 x12-x17: arguments (a2-7)
4455 x28-31: temporaries (t3-6)
4456 pc: program counter (pc)
4457
4458 ==> U-Boot will use gp to hold a pointer to the global data
4459
wdenk2729af92004-05-03 20:45:30 +00004460Memory Management:
4461------------------
wdenkc6097192002-11-03 00:24:07 +00004462
wdenk2729af92004-05-03 20:45:30 +00004463U-Boot runs in system state and uses physical addresses, i.e. the
4464MMU is not used either for address mapping nor for memory protection.
wdenkc6097192002-11-03 00:24:07 +00004465
wdenk2729af92004-05-03 20:45:30 +00004466The available memory is mapped to fixed addresses using the memory
4467controller. In this process, a contiguous block is formed for each
4468memory type (Flash, SDRAM, SRAM), even when it consists of several
4469physical memory banks.
wdenkc6097192002-11-03 00:24:07 +00004470
wdenk2729af92004-05-03 20:45:30 +00004471U-Boot is installed in the first 128 kB of the first Flash bank (on
4472TQM8xxL modules this is the range 0x40000000 ... 0x4001FFFF). After
4473booting and sizing and initializing DRAM, the code relocates itself
4474to the upper end of DRAM. Immediately below the U-Boot code some
Jean-Christophe PLAGNIOL-VILLARD6d0f6bc2008-10-16 15:01:15 +02004475memory is reserved for use by malloc() [see CONFIG_SYS_MALLOC_LEN
wdenk2729af92004-05-03 20:45:30 +00004476configuration setting]. Below that, a structure with global Board
4477Info data is placed, followed by the stack (growing downward).
wdenkc6097192002-11-03 00:24:07 +00004478
wdenk2729af92004-05-03 20:45:30 +00004479Additionally, some exception handler code is copied to the low 8 kB
4480of DRAM (0x00000000 ... 0x00001FFF).
wdenkc6097192002-11-03 00:24:07 +00004481
wdenk2729af92004-05-03 20:45:30 +00004482So a typical memory configuration with 16 MB of DRAM could look like
4483this:
wdenkc6097192002-11-03 00:24:07 +00004484
wdenk2729af92004-05-03 20:45:30 +00004485 0x0000 0000 Exception Vector code
4486 :
4487 0x0000 1FFF
4488 0x0000 2000 Free for Application Use
4489 :
4490 :
wdenkc6097192002-11-03 00:24:07 +00004491
wdenk2729af92004-05-03 20:45:30 +00004492 :
4493 :
4494 0x00FB FF20 Monitor Stack (Growing downward)
4495 0x00FB FFAC Board Info Data and permanent copy of global data
4496 0x00FC 0000 Malloc Arena
4497 :
4498 0x00FD FFFF
4499 0x00FE 0000 RAM Copy of Monitor Code
4500 ... eventually: LCD or video framebuffer
4501 ... eventually: pRAM (Protected RAM - unchanged by reset)
4502 0x00FF FFFF [End of RAM]
wdenkc6097192002-11-03 00:24:07 +00004503
4504
wdenk2729af92004-05-03 20:45:30 +00004505System Initialization:
4506----------------------
wdenkc6097192002-11-03 00:24:07 +00004507
wdenk2729af92004-05-03 20:45:30 +00004508In the reset configuration, U-Boot starts at the reset entry point
Marcel Ziswiler11ccc332008-07-09 08:17:15 +02004509(on most PowerPC systems at address 0x00000100). Because of the reset
Jeremiah Mahlerb445bbb2015-01-04 18:56:50 -08004510configuration for CS0# this is a mirror of the on board Flash memory.
wdenk2729af92004-05-03 20:45:30 +00004511To be able to re-map memory U-Boot then jumps to its link address.
4512To be able to implement the initialization code in C, a (small!)
4513initial stack is set up in the internal Dual Ported RAM (in case CPUs
Heiko Schocher2eb48ff2017-06-07 17:33:10 +02004514which provide such a feature like), or in a locked part of the data
4515cache. After that, U-Boot initializes the CPU core, the caches and
4516the SIU.
wdenkc6097192002-11-03 00:24:07 +00004517
wdenk2729af92004-05-03 20:45:30 +00004518Next, all (potentially) available memory banks are mapped using a
4519preliminary mapping. For example, we put them on 512 MB boundaries
4520(multiples of 0x20000000: SDRAM on 0x00000000 and 0x20000000, Flash
4521on 0x40000000 and 0x60000000, SRAM on 0x80000000). Then UPM A is
4522programmed for SDRAM access. Using the temporary configuration, a
4523simple memory test is run that determines the size of the SDRAM
4524banks.
wdenkc6097192002-11-03 00:24:07 +00004525
wdenk2729af92004-05-03 20:45:30 +00004526When there is more than one SDRAM bank, and the banks are of
4527different size, the largest is mapped first. For equal size, the first
4528bank (CS2#) is mapped first. The first mapping is always for address
45290x00000000, with any additional banks following immediately to create
4530contiguous memory starting from 0.
wdenkc6097192002-11-03 00:24:07 +00004531
wdenk2729af92004-05-03 20:45:30 +00004532Then, the monitor installs itself at the upper end of the SDRAM area
4533and allocates memory for use by malloc() and for the global Board
4534Info data; also, the exception vector code is copied to the low RAM
4535pages, and the final stack is set up.
wdenkc6097192002-11-03 00:24:07 +00004536
wdenk2729af92004-05-03 20:45:30 +00004537Only after this relocation will you have a "normal" C environment;
4538until that you are restricted in several ways, mostly because you are
4539running from ROM, and because the code will have to be relocated to a
4540new address in RAM.
wdenkc6097192002-11-03 00:24:07 +00004541
4542
wdenk2729af92004-05-03 20:45:30 +00004543U-Boot Porting Guide:
4544----------------------
wdenkc6097192002-11-03 00:24:07 +00004545
wdenk2729af92004-05-03 20:45:30 +00004546[Based on messages by Jerry Van Baren in the U-Boot-Users mailing
4547list, October 2002]
wdenkc6097192002-11-03 00:24:07 +00004548
4549
Jerry Van Baren6c3fef22009-07-15 20:42:59 -04004550int main(int argc, char *argv[])
wdenk2729af92004-05-03 20:45:30 +00004551{
4552 sighandler_t no_more_time;
wdenkc6097192002-11-03 00:24:07 +00004553
Jerry Van Baren6c3fef22009-07-15 20:42:59 -04004554 signal(SIGALRM, no_more_time);
4555 alarm(PROJECT_DEADLINE - toSec (3 * WEEK));
wdenkc6097192002-11-03 00:24:07 +00004556
wdenk2729af92004-05-03 20:45:30 +00004557 if (available_money > available_manpower) {
Jerry Van Baren6c3fef22009-07-15 20:42:59 -04004558 Pay consultant to port U-Boot;
wdenkc6097192002-11-03 00:24:07 +00004559 return 0;
4560 }
4561
wdenk2729af92004-05-03 20:45:30 +00004562 Download latest U-Boot source;
4563
Wolfgang Denk06682362008-12-30 22:56:11 +01004564 Subscribe to u-boot mailing list;
wdenk2729af92004-05-03 20:45:30 +00004565
Jerry Van Baren6c3fef22009-07-15 20:42:59 -04004566 if (clueless)
4567 email("Hi, I am new to U-Boot, how do I get started?");
wdenkc6097192002-11-03 00:24:07 +00004568
wdenk2729af92004-05-03 20:45:30 +00004569 while (learning) {
4570 Read the README file in the top level directory;
Jerry Van Baren6c3fef22009-07-15 20:42:59 -04004571 Read http://www.denx.de/twiki/bin/view/DULG/Manual;
Patrick Delaunay24bcaec2020-02-28 15:18:10 +01004572 Read applicable doc/README.*;
wdenk2729af92004-05-03 20:45:30 +00004573 Read the source, Luke;
Jerry Van Baren6c3fef22009-07-15 20:42:59 -04004574 /* find . -name "*.[chS]" | xargs grep -i <keyword> */
wdenk2729af92004-05-03 20:45:30 +00004575 }
wdenkc6097192002-11-03 00:24:07 +00004576
Jerry Van Baren6c3fef22009-07-15 20:42:59 -04004577 if (available_money > toLocalCurrency ($2500))
4578 Buy a BDI3000;
4579 else
wdenk2729af92004-05-03 20:45:30 +00004580 Add a lot of aggravation and time;
Jerry Van Baren6c3fef22009-07-15 20:42:59 -04004581
4582 if (a similar board exists) { /* hopefully... */
4583 cp -a board/<similar> board/<myboard>
4584 cp include/configs/<similar>.h include/configs/<myboard>.h
4585 } else {
4586 Create your own board support subdirectory;
4587 Create your own board include/configs/<myboard>.h file;
wdenk2729af92004-05-03 20:45:30 +00004588 }
Jerry Van Baren6c3fef22009-07-15 20:42:59 -04004589 Edit new board/<myboard> files
4590 Edit new include/configs/<myboard>.h
wdenkc6097192002-11-03 00:24:07 +00004591
Jerry Van Baren6c3fef22009-07-15 20:42:59 -04004592 while (!accepted) {
4593 while (!running) {
4594 do {
4595 Add / modify source code;
4596 } until (compiles);
4597 Debug;
4598 if (clueless)
4599 email("Hi, I am having problems...");
4600 }
4601 Send patch file to the U-Boot email list;
4602 if (reasonable critiques)
4603 Incorporate improvements from email list code review;
4604 else
4605 Defend code as written;
wdenk2729af92004-05-03 20:45:30 +00004606 }
wdenkc6097192002-11-03 00:24:07 +00004607
wdenk2729af92004-05-03 20:45:30 +00004608 return 0;
4609}
4610
4611void no_more_time (int sig)
4612{
4613 hire_a_guru();
4614}
wdenkc6097192002-11-03 00:24:07 +00004615
4616
wdenk2729af92004-05-03 20:45:30 +00004617Coding Standards:
4618-----------------
wdenkc6097192002-11-03 00:24:07 +00004619
wdenk2729af92004-05-03 20:45:30 +00004620All contributions to U-Boot should conform to the Linux kernel
Baruch Siach659208d2017-12-10 17:34:35 +02004621coding style; see the kernel coding style guide at
4622https://www.kernel.org/doc/html/latest/process/coding-style.html, and the
4623script "scripts/Lindent" in your Linux kernel source directory.
wdenk2729af92004-05-03 20:45:30 +00004624
Detlev Zundel2c051652006-09-01 15:39:02 +02004625Source files originating from a different project (for example the
4626MTD subsystem) are generally exempt from these guidelines and are not
Jeremiah Mahlerb445bbb2015-01-04 18:56:50 -08004627reformatted to ease subsequent migration to newer versions of those
Detlev Zundel2c051652006-09-01 15:39:02 +02004628sources.
4629
4630Please note that U-Boot is implemented in C (and to some small parts in
4631Assembler); no C++ is used, so please do not use C++ style comments (//)
4632in your code.
wdenk2729af92004-05-03 20:45:30 +00004633
4634Please also stick to the following formatting rules:
4635- remove any trailing white space
Wolfgang Denk7ca92962011-07-27 10:59:55 +00004636- use TAB characters for indentation and vertical alignment, not spaces
wdenk2729af92004-05-03 20:45:30 +00004637- make sure NOT to use DOS '\r\n' line feeds
Wolfgang Denk7ca92962011-07-27 10:59:55 +00004638- do not add more than 2 consecutive empty lines to source files
wdenk2729af92004-05-03 20:45:30 +00004639- do not add trailing empty lines to source files
4640
4641Submissions which do not conform to the standards may be returned
4642with a request to reformat the changes.
wdenkc6097192002-11-03 00:24:07 +00004643
4644
wdenk2729af92004-05-03 20:45:30 +00004645Submitting Patches:
4646-------------------
wdenkc6097192002-11-03 00:24:07 +00004647
wdenk2729af92004-05-03 20:45:30 +00004648Since the number of patches for U-Boot is growing, we need to
4649establish some rules. Submissions which do not conform to these rules
4650may be rejected, even when they contain important and valuable stuff.
wdenkc6097192002-11-03 00:24:07 +00004651
Magnus Lilja0d28f342008-08-06 19:32:33 +02004652Please see http://www.denx.de/wiki/U-Boot/Patches for details.
Wolfgang Denk218ca722008-03-26 10:40:12 +01004653
Wolfgang Denk06682362008-12-30 22:56:11 +01004654Patches shall be sent to the u-boot mailing list <u-boot@lists.denx.de>;
S. Lockwood-Childs1dade182017-11-14 22:56:42 -08004655see https://lists.denx.de/listinfo/u-boot
Wolfgang Denk06682362008-12-30 22:56:11 +01004656
wdenk2729af92004-05-03 20:45:30 +00004657When you send a patch, please include the following information with
4658it:
wdenkc6097192002-11-03 00:24:07 +00004659
wdenk2729af92004-05-03 20:45:30 +00004660* For bug fixes: a description of the bug and how your patch fixes
4661 this bug. Please try to include a way of demonstrating that the
4662 patch actually fixes something.
wdenkc6097192002-11-03 00:24:07 +00004663
wdenk2729af92004-05-03 20:45:30 +00004664* For new features: a description of the feature and your
4665 implementation.
wdenkc6097192002-11-03 00:24:07 +00004666
Robert P. J. Day7207b362015-12-19 07:16:10 -05004667* For major contributions, add a MAINTAINERS file with your
4668 information and associated file and directory references.
wdenk2729af92004-05-03 20:45:30 +00004669
Albert ARIBAUD27af9302013-09-11 15:52:51 +02004670* When you add support for a new board, don't forget to add a
4671 maintainer e-mail address to the boards.cfg file, too.
wdenk2729af92004-05-03 20:45:30 +00004672
4673* If your patch adds new configuration options, don't forget to
4674 document these in the README file.
4675
Wolfgang Denk218ca722008-03-26 10:40:12 +01004676* The patch itself. If you are using git (which is *strongly*
4677 recommended) you can easily generate the patch using the
Wolfgang Denk7ca92962011-07-27 10:59:55 +00004678 "git format-patch". If you then use "git send-email" to send it to
Wolfgang Denk218ca722008-03-26 10:40:12 +01004679 the U-Boot mailing list, you will avoid most of the common problems
4680 with some other mail clients.
wdenk2729af92004-05-03 20:45:30 +00004681
Wolfgang Denk218ca722008-03-26 10:40:12 +01004682 If you cannot use git, use "diff -purN OLD NEW". If your version of
4683 diff does not support these options, then get the latest version of
4684 GNU diff.
wdenk2729af92004-05-03 20:45:30 +00004685
Wolfgang Denk218ca722008-03-26 10:40:12 +01004686 The current directory when running this command shall be the parent
4687 directory of the U-Boot source tree (i. e. please make sure that
4688 your patch includes sufficient directory information for the
4689 affected files).
4690
4691 We prefer patches as plain text. MIME attachments are discouraged,
4692 and compressed attachments must not be used.
wdenk2729af92004-05-03 20:45:30 +00004693
4694* If one logical set of modifications affects or creates several
4695 files, all these changes shall be submitted in a SINGLE patch file.
4696
4697* Changesets that contain different, unrelated modifications shall be
4698 submitted as SEPARATE patches, one patch per changeset.
4699
4700
4701Notes:
4702
Simon Glass6de80f22016-07-27 20:33:08 -06004703* Before sending the patch, run the buildman script on your patched
wdenk2729af92004-05-03 20:45:30 +00004704 source tree and make sure that no errors or warnings are reported
4705 for any of the boards.
4706
4707* Keep your modifications to the necessary minimum: A patch
4708 containing several unrelated changes or arbitrary reformats will be
4709 returned with a request to re-formatting / split it.
4710
4711* If you modify existing code, make sure that your new code does not
4712 add to the memory footprint of the code ;-) Small is beautiful!
4713 When adding new features, these should compile conditionally only
4714 (using #ifdef), and the resulting code with the new feature
4715 disabled must not need more memory than the old code without your
4716 modification.
wdenk90dc6702005-05-03 14:12:25 +00004717
Wolfgang Denk06682362008-12-30 22:56:11 +01004718* Remember that there is a size limit of 100 kB per message on the
4719 u-boot mailing list. Bigger patches will be moderated. If they are
4720 reasonable and not too big, they will be acknowledged. But patches
4721 bigger than the size limit should be avoided.