blob: 26f93c21a769d0ccfd4dff6ba0a63a5a8b8dec2a [file] [log] [blame]
wdenkc6097192002-11-03 00:24:07 +00001#
wdenk151ab832005-02-24 22:44:16 +00002# (C) Copyright 2000 - 2005
wdenkc6097192002-11-03 00:24:07 +00003# Wolfgang Denk, DENX Software Engineering, wd@denx.de.
4#
5# See file CREDITS for list of people who contributed to this
6# project.
7#
8# This program is free software; you can redistribute it and/or
9# modify it under the terms of the GNU General Public License as
10# published by the Free Software Foundation; either version 2 of
11# the License, or (at your option) any later version.
12#
13# This program is distributed in the hope that it will be useful,
14# but WITHOUT ANY WARRANTY; without even the implied warranty of
15# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
16# GNU General Public License for more details.
17#
18# You should have received a copy of the GNU General Public License
19# along with this program; if not, write to the Free Software
20# Foundation, Inc., 59 Temple Place, Suite 330, Boston,
21# MA 02111-1307 USA
22#
23
24Summary:
25========
26
wdenk24ee89b2002-11-03 17:56:27 +000027This directory contains the source code for U-Boot, a boot loader for
wdenke86e5a02004-10-17 21:12:06 +000028Embedded boards based on PowerPC, ARM, MIPS and several other
29processors, which can be installed in a boot ROM and used to
30initialize and test the hardware or to download and run application
31code.
wdenkc6097192002-11-03 00:24:07 +000032
33The development of U-Boot is closely related to Linux: some parts of
wdenk24ee89b2002-11-03 17:56:27 +000034the source code originate in the Linux source tree, we have some
35header files in common, and special provision has been made to
wdenkc6097192002-11-03 00:24:07 +000036support booting of Linux images.
37
38Some attention has been paid to make this software easily
39configurable and extendable. For instance, all monitor commands are
40implemented with the same call interface, so that it's very easy to
41add new commands. Also, instead of permanently adding rarely used
42code (for instance hardware test utilities) to the monitor, you can
43load and run it dynamically.
44
45
46Status:
47=======
48
49In general, all boards for which a configuration option exists in the
wdenk24ee89b2002-11-03 17:56:27 +000050Makefile have been tested to some extent and can be considered
wdenkc6097192002-11-03 00:24:07 +000051"working". In fact, many of them are used in production systems.
52
wdenk24ee89b2002-11-03 17:56:27 +000053In case of problems see the CHANGELOG and CREDITS files to find out
wdenkc6097192002-11-03 00:24:07 +000054who contributed the specific port.
55
wdenkc6097192002-11-03 00:24:07 +000056
57Where to get help:
58==================
59
wdenk24ee89b2002-11-03 17:56:27 +000060In case you have questions about, problems with or contributions for
61U-Boot you should send a message to the U-Boot mailing list at
62<u-boot-users@lists.sourceforge.net>. There is also an archive of
63previous traffic on the mailing list - please search the archive
wdenkc6097192002-11-03 00:24:07 +000064before asking FAQ's. Please see
65http://lists.sourceforge.net/lists/listinfo/u-boot-users/
66
67
68Where we come from:
69===================
70
71- start from 8xxrom sources
wdenk24ee89b2002-11-03 17:56:27 +000072- create PPCBoot project (http://sourceforge.net/projects/ppcboot)
wdenkc6097192002-11-03 00:24:07 +000073- clean up code
74- make it easier to add custom boards
75- make it possible to add other [PowerPC] CPUs
76- extend functions, especially:
77 * Provide extended interface to Linux boot loader
78 * S-Record download
79 * network boot
80 * PCMCIA / CompactFLash / ATA disk / SCSI ... boot
wdenk24ee89b2002-11-03 17:56:27 +000081- create ARMBoot project (http://sourceforge.net/projects/armboot)
wdenkc6097192002-11-03 00:24:07 +000082- add other CPU families (starting with ARM)
wdenk24ee89b2002-11-03 17:56:27 +000083- create U-Boot project (http://sourceforge.net/projects/u-boot)
84
85
86Names and Spelling:
87===================
88
89The "official" name of this project is "Das U-Boot". The spelling
90"U-Boot" shall be used in all written text (documentation, comments
91in source files etc.). Example:
92
93 This is the README file for the U-Boot project.
94
95File names etc. shall be based on the string "u-boot". Examples:
96
97 include/asm-ppc/u-boot.h
98
99 #include <asm/u-boot.h>
100
101Variable names, preprocessor constants etc. shall be either based on
102the string "u_boot" or on "U_BOOT". Example:
103
104 U_BOOT_VERSION u_boot_logo
105 IH_OS_U_BOOT u_boot_hush_start
wdenkc6097192002-11-03 00:24:07 +0000106
107
wdenk93f19cc2002-12-17 17:55:09 +0000108Versioning:
109===========
110
111U-Boot uses a 3 level version number containing a version, a
112sub-version, and a patchlevel: "U-Boot-2.34.5" means version "2",
113sub-version "34", and patchlevel "4".
114
115The patchlevel is used to indicate certain stages of development
116between released versions, i. e. officially released versions of
117U-Boot will always have a patchlevel of "0".
118
119
wdenkc6097192002-11-03 00:24:07 +0000120Directory Hierarchy:
121====================
122
wdenk7152b1d2003-09-05 23:19:14 +0000123- board Board dependent files
124- common Misc architecture independent functions
wdenkc6097192002-11-03 00:24:07 +0000125- cpu CPU specific files
wdenk983fda82004-10-28 00:09:35 +0000126 - 74xx_7xx Files specific to Freescale MPC74xx and 7xx CPUs
wdenk11dadd52004-02-27 00:07:27 +0000127 - arm720t Files specific to ARM 720 CPUs
128 - arm920t Files specific to ARM 920 CPUs
wdenka85f9f22005-04-06 13:52:31 +0000129 - at91rm9200 Files specific to Atmel AT91RM9200 CPU
wdenk983fda82004-10-28 00:09:35 +0000130 - imx Files specific to Freescale MC9328 i.MX CPUs
wdenk1d9f4102004-10-09 22:21:29 +0000131 - s3c24x0 Files specific to Samsung S3C24X0 CPUs
wdenk11dadd52004-02-27 00:07:27 +0000132 - arm925t Files specific to ARM 925 CPUs
133 - arm926ejs Files specific to ARM 926 CPUs
wdenk8ed96042005-01-09 23:16:25 +0000134 - arm1136 Files specific to ARM 1136 CPUs
Wolfgang Denk72a087e2006-10-24 14:27:35 +0200135 - at32ap Files specific to Atmel AVR32 AP CPUs
wdenk11dadd52004-02-27 00:07:27 +0000136 - i386 Files specific to i386 CPUs
137 - ixp Files specific to Intel XScale IXP CPUs
wdenk983fda82004-10-28 00:09:35 +0000138 - mcf52x2 Files specific to Freescale ColdFire MCF52x2 CPUs
TsiChung Liew8e585f02007-06-18 13:50:13 -0500139 - mcf532x Files specific to Freescale ColdFire MCF5329 CPUs
TsiChungLiew8ae158c2007-08-16 15:05:11 -0500140 - mcf5445x Files specific to Freescale ColdFire MCF5445x CPUs
wdenk11dadd52004-02-27 00:07:27 +0000141 - mips Files specific to MIPS CPUs
wdenk983fda82004-10-28 00:09:35 +0000142 - mpc5xx Files specific to Freescale MPC5xx CPUs
143 - mpc5xxx Files specific to Freescale MPC5xxx CPUs
144 - mpc8xx Files specific to Freescale MPC8xx CPUs
145 - mpc8220 Files specific to Freescale MPC8220 CPUs
146 - mpc824x Files specific to Freescale MPC824x CPUs
147 - mpc8260 Files specific to Freescale MPC8260 CPUs
148 - mpc85xx Files specific to Freescale MPC85xx CPUs
wdenk11dadd52004-02-27 00:07:27 +0000149 - nios Files specific to Altera NIOS CPUs
wdenk5c952cf2004-10-10 21:27:30 +0000150 - nios2 Files specific to Altera Nios-II CPUs
Wolfgang Denk0c8721a2005-09-23 11:05:55 +0200151 - ppc4xx Files specific to AMCC PowerPC 4xx CPUs
wdenk11dadd52004-02-27 00:07:27 +0000152 - pxa Files specific to Intel XScale PXA CPUs
153 - s3c44b0 Files specific to Samsung S3C44B0 CPUs
154 - sa1100 Files specific to Intel StrongARM SA1100 CPUs
wdenkc6097192002-11-03 00:24:07 +0000155- disk Code for disk drive partition handling
156- doc Documentation (don't expect too much)
wdenk7152b1d2003-09-05 23:19:14 +0000157- drivers Commonly used device drivers
wdenkc6097192002-11-03 00:24:07 +0000158- dtt Digital Thermometer and Thermostat drivers
159- examples Example code for standalone applications, etc.
160- include Header Files
wdenk11dadd52004-02-27 00:07:27 +0000161- lib_arm Files generic to ARM architecture
Wolfgang Denk7b64fef2006-10-24 14:21:16 +0200162- lib_avr32 Files generic to AVR32 architecture
wdenk11dadd52004-02-27 00:07:27 +0000163- lib_generic Files generic to all architectures
164- lib_i386 Files generic to i386 architecture
165- lib_m68k Files generic to m68k architecture
166- lib_mips Files generic to MIPS architecture
167- lib_nios Files generic to NIOS architecture
168- lib_ppc Files generic to PowerPC architecture
Gerald Van Baren213bf8c2007-03-31 12:23:51 -0400169- libfdt Library files to support flattened device trees
wdenkc6097192002-11-03 00:24:07 +0000170- net Networking code
wdenkc6097192002-11-03 00:24:07 +0000171- post Power On Self Test
wdenkc6097192002-11-03 00:24:07 +0000172- rtc Real Time Clock drivers
173- tools Tools to build S-Record or U-Boot images, etc.
174
wdenkc6097192002-11-03 00:24:07 +0000175Software Configuration:
176=======================
177
178Configuration is usually done using C preprocessor defines; the
179rationale behind that is to avoid dead code whenever possible.
180
181There are two classes of configuration variables:
182
183* Configuration _OPTIONS_:
184 These are selectable by the user and have names beginning with
185 "CONFIG_".
186
187* Configuration _SETTINGS_:
188 These depend on the hardware etc. and should not be meddled with if
189 you don't know what you're doing; they have names beginning with
190 "CFG_".
191
192Later we will add a configuration tool - probably similar to or even
193identical to what's used for the Linux kernel. Right now, we have to
194do the configuration by hand, which means creating some symbolic
195links and editing some configuration files. We use the TQM8xxL boards
196as an example here.
197
198
199Selection of Processor Architecture and Board Type:
200---------------------------------------------------
201
202For all supported boards there are ready-to-use default
203configurations available; just type "make <board_name>_config".
204
205Example: For a TQM823L module type:
206
207 cd u-boot
208 make TQM823L_config
209
210For the Cogent platform, you need to specify the cpu type as well;
211e.g. "make cogent_mpc8xx_config". And also configure the cogent
212directory according to the instructions in cogent/README.
213
214
215Configuration Options:
216----------------------
217
218Configuration depends on the combination of board and CPU type; all
219such information is kept in a configuration file
220"include/configs/<board_name>.h".
221
222Example: For a TQM823L module, all configuration settings are in
223"include/configs/TQM823L.h".
224
225
wdenk7f6c2cb2002-11-10 22:06:23 +0000226Many of the options are named exactly as the corresponding Linux
227kernel configuration options. The intention is to make it easier to
228build a config tool - later.
229
230
wdenkc6097192002-11-03 00:24:07 +0000231The following options need to be configured:
232
Kim Phillips26281142007-08-10 13:28:25 -0500233- CPU Type: Define exactly one, e.g. CONFIG_MPC85XX.
wdenkc6097192002-11-03 00:24:07 +0000234
Kim Phillips26281142007-08-10 13:28:25 -0500235- Board Type: Define exactly one, e.g. CONFIG_MPC8540ADS.
Wolfgang Denk6ccec442006-10-24 14:42:37 +0200236
237- CPU Daughterboard Type: (if CONFIG_ATSTK1000 is defined)
Haavard Skinnemoen09ea0de2007-11-01 12:44:20 +0100238 Define exactly one, e.g. CONFIG_ATSTK1002
wdenkc6097192002-11-03 00:24:07 +0000239
240- CPU Module Type: (if CONFIG_COGENT is defined)
241 Define exactly one of
242 CONFIG_CMA286_60_OLD
243--- FIXME --- not tested yet:
244 CONFIG_CMA286_60, CONFIG_CMA286_21, CONFIG_CMA286_60P,
245 CONFIG_CMA287_23, CONFIG_CMA287_50
246
247- Motherboard Type: (if CONFIG_COGENT is defined)
248 Define exactly one of
249 CONFIG_CMA101, CONFIG_CMA102
250
251- Motherboard I/O Modules: (if CONFIG_COGENT is defined)
252 Define one or more of
253 CONFIG_CMA302
254
255- Motherboard Options: (if CONFIG_CMA101 or CONFIG_CMA102 are defined)
256 Define one or more of
257 CONFIG_LCD_HEARTBEAT - update a character position on
258 the lcd display every second with
259 a "rotator" |\-/|\-/
260
wdenk2535d602003-07-17 23:16:40 +0000261- Board flavour: (if CONFIG_MPC8260ADS is defined)
262 CONFIG_ADSTYPE
263 Possible values are:
264 CFG_8260ADS - original MPC8260ADS
wdenk180d3f72004-01-04 16:28:35 +0000265 CFG_8266ADS - MPC8266ADS
wdenk54387ac2003-10-08 22:45:44 +0000266 CFG_PQ2FADS - PQ2FADS-ZU or PQ2FADS-VR
wdenk04a85b32004-04-15 18:22:41 +0000267 CFG_8272ADS - MPC8272ADS
wdenk2535d602003-07-17 23:16:40 +0000268
wdenkc6097192002-11-03 00:24:07 +0000269- MPC824X Family Member (if CONFIG_MPC824X is defined)
wdenk5da627a2003-10-09 20:09:04 +0000270 Define exactly one of
271 CONFIG_MPC8240, CONFIG_MPC8245
wdenkc6097192002-11-03 00:24:07 +0000272
wdenk75d1ea72004-01-31 20:06:54 +0000273- 8xx CPU Options: (if using an MPC8xx cpu)
wdenk66ca92a2004-09-28 17:59:53 +0000274 CONFIG_8xx_GCLK_FREQ - deprecated: CPU clock if
275 get_gclk_freq() cannot work
wdenk5da627a2003-10-09 20:09:04 +0000276 e.g. if there is no 32KHz
277 reference PIT/RTC clock
wdenk66ca92a2004-09-28 17:59:53 +0000278 CONFIG_8xx_OSCLK - PLL input clock (either EXTCLK
279 or XTAL/EXTAL)
wdenkc6097192002-11-03 00:24:07 +0000280
wdenk66ca92a2004-09-28 17:59:53 +0000281- 859/866/885 CPU options: (if using a MPC859 or MPC866 or MPC885 CPU):
282 CFG_8xx_CPUCLK_MIN
283 CFG_8xx_CPUCLK_MAX
284 CONFIG_8xx_CPUCLK_DEFAULT
wdenk75d1ea72004-01-31 20:06:54 +0000285 See doc/README.MPC866
286
287 CFG_MEASURE_CPUCLK
288
wdenkba56f622004-02-06 23:19:44 +0000289 Define this to measure the actual CPU clock instead
290 of relying on the correctness of the configured
291 values. Mostly useful for board bringup to make sure
292 the PLL is locked at the intended frequency. Note
293 that this requires a (stable) reference clock (32 kHz
wdenk66ca92a2004-09-28 17:59:53 +0000294 RTC clock or CFG_8XX_XIN)
wdenk75d1ea72004-01-31 20:06:54 +0000295
Markus Klotzbuecher0b953ff2006-03-24 15:28:02 +0100296- Intel Monahans options:
297 CFG_MONAHANS_RUN_MODE_OSC_RATIO
298
299 Defines the Monahans run mode to oscillator
300 ratio. Valid values are 8, 16, 24, 31. The core
301 frequency is this value multiplied by 13 MHz.
302
303 CFG_MONAHANS_TURBO_RUN_MODE_RATIO
Wolfgang Denkcf48eb92006-04-16 10:51:58 +0200304
Markus Klotzbuecher0b953ff2006-03-24 15:28:02 +0100305 Defines the Monahans turbo mode to oscillator
306 ratio. Valid values are 1 (default if undefined) and
Wolfgang Denkcf48eb92006-04-16 10:51:58 +0200307 2. The core frequency as calculated above is multiplied
Markus Klotzbuecher0b953ff2006-03-24 15:28:02 +0100308 by this value.
Wolfgang Denkcf48eb92006-04-16 10:51:58 +0200309
wdenk5da627a2003-10-09 20:09:04 +0000310- Linux Kernel Interface:
wdenkc6097192002-11-03 00:24:07 +0000311 CONFIG_CLOCKS_IN_MHZ
312
313 U-Boot stores all clock information in Hz
314 internally. For binary compatibility with older Linux
315 kernels (which expect the clocks passed in the
316 bd_info data to be in MHz) the environment variable
317 "clocks_in_mhz" can be defined so that U-Boot
318 converts clock data to MHZ before passing it to the
319 Linux kernel.
wdenkc6097192002-11-03 00:24:07 +0000320 When CONFIG_CLOCKS_IN_MHZ is defined, a definition of
321 "clocks_in_mhz=1" is automatically included in the
322 default environment.
323
wdenk5da627a2003-10-09 20:09:04 +0000324 CONFIG_MEMSIZE_IN_BYTES [relevant for MIPS only]
325
326 When transfering memsize parameter to linux, some versions
327 expect it to be in bytes, others in MB.
328 Define CONFIG_MEMSIZE_IN_BYTES to make it in bytes.
329
Gerald Van Baren213bf8c2007-03-31 12:23:51 -0400330 CONFIG_OF_LIBFDT / CONFIG_OF_FLAT_TREE
Wolfgang Denkf57f70a2005-10-13 01:45:54 +0200331
332 New kernel versions are expecting firmware settings to be
Gerald Van Baren213bf8c2007-03-31 12:23:51 -0400333 passed using flattened device trees (based on open firmware
334 concepts).
335
336 CONFIG_OF_LIBFDT
337 * New libfdt-based support
338 * Adds the "fdt" command
Kim Phillips3bb342f2007-08-10 14:34:14 -0500339 * The bootm command automatically updates the fdt
Gerald Van Baren213bf8c2007-03-31 12:23:51 -0400340
341 CONFIG_OF_FLAT_TREE
342 * Deprecated, see CONFIG_OF_LIBFDT
343 * Original ft_build.c-based support
344 * Automatically modifies the dft as part of the bootm command
345 * The environment variable "disable_of", when set,
346 disables this functionality.
Wolfgang Denkf57f70a2005-10-13 01:45:54 +0200347
Wolfgang Denkf57f70a2005-10-13 01:45:54 +0200348 OF_CPU - The proper name of the cpus node.
Kumar Galac2871f02006-01-11 13:59:02 -0600349 OF_SOC - The proper name of the soc node.
Wolfgang Denkf57f70a2005-10-13 01:45:54 +0200350 OF_TBCLK - The timebase frequency.
Kumar Galac2871f02006-01-11 13:59:02 -0600351 OF_STDOUT_PATH - The path to the console device
Wolfgang Denkf57f70a2005-10-13 01:45:54 +0200352
Kim Phillips3bb342f2007-08-10 14:34:14 -0500353 boards with QUICC Engines require OF_QE to set UCC mac addresses
354
Kumar Galae4f880e2006-01-11 13:49:31 -0600355 CONFIG_OF_HAS_BD_T
356
Gerald Van Baren213bf8c2007-03-31 12:23:51 -0400357 * CONFIG_OF_LIBFDT - enables the "fdt bd_t" command
358 * CONFIG_OF_FLAT_TREE - The resulting flat device tree
359 will have a copy of the bd_t. Space should be
360 pre-allocated in the dts for the bd_t.
Kumar Galae4f880e2006-01-11 13:49:31 -0600361
362 CONFIG_OF_HAS_UBOOT_ENV
Stefan Roese15940c92006-03-13 11:16:36 +0100363
Kim Phillips3bb342f2007-08-10 14:34:14 -0500364 * CONFIG_OF_LIBFDT - enables the "fdt env" command
Gerald Van Baren213bf8c2007-03-31 12:23:51 -0400365 * CONFIG_OF_FLAT_TREE - The resulting flat device tree
366 will have a copy of u-boot's environment variables
Kumar Galae4f880e2006-01-11 13:49:31 -0600367
Kumar Gala4e253132006-01-11 13:54:17 -0600368 CONFIG_OF_BOARD_SETUP
369
370 Board code has addition modification that it wants to make
371 to the flat device tree before handing it off to the kernel
wdenk6705d812004-08-02 23:22:59 +0000372
Matthew McClintock02677682006-06-28 10:41:37 -0500373 CONFIG_OF_BOOT_CPU
374
375 This define fills in the correct boot cpu in the boot
376 param header, the default value is zero if undefined.
377
wdenk6705d812004-08-02 23:22:59 +0000378- Serial Ports:
379 CFG_PL010_SERIAL
380
381 Define this if you want support for Amba PrimeCell PL010 UARTs.
382
383 CFG_PL011_SERIAL
384
385 Define this if you want support for Amba PrimeCell PL011 UARTs.
386
387 CONFIG_PL011_CLOCK
388
389 If you have Amba PrimeCell PL011 UARTs, set this variable to
390 the clock speed of the UARTs.
391
392 CONFIG_PL01x_PORTS
393
394 If you have Amba PrimeCell PL010 or PL011 UARTs on your board,
395 define this to a list of base addresses for each (supported)
396 port. See e.g. include/configs/versatile.h
397
398
wdenkc6097192002-11-03 00:24:07 +0000399- Console Interface:
wdenk43d96162003-03-06 00:02:04 +0000400 Depending on board, define exactly one serial port
401 (like CONFIG_8xx_CONS_SMC1, CONFIG_8xx_CONS_SMC2,
402 CONFIG_8xx_CONS_SCC1, ...), or switch off the serial
403 console by defining CONFIG_8xx_CONS_NONE
wdenkc6097192002-11-03 00:24:07 +0000404
405 Note: if CONFIG_8xx_CONS_NONE is defined, the serial
406 port routines must be defined elsewhere
407 (i.e. serial_init(), serial_getc(), ...)
408
409 CONFIG_CFB_CONSOLE
410 Enables console device for a color framebuffer. Needs following
411 defines (cf. smiLynxEM, i8042, board/eltec/bab7xx)
412 VIDEO_FB_LITTLE_ENDIAN graphic memory organisation
413 (default big endian)
414 VIDEO_HW_RECTFILL graphic chip supports
415 rectangle fill
416 (cf. smiLynxEM)
417 VIDEO_HW_BITBLT graphic chip supports
418 bit-blit (cf. smiLynxEM)
419 VIDEO_VISIBLE_COLS visible pixel columns
420 (cols=pitch)
wdenkba56f622004-02-06 23:19:44 +0000421 VIDEO_VISIBLE_ROWS visible pixel rows
422 VIDEO_PIXEL_SIZE bytes per pixel
wdenkc6097192002-11-03 00:24:07 +0000423 VIDEO_DATA_FORMAT graphic data format
424 (0-5, cf. cfb_console.c)
wdenkba56f622004-02-06 23:19:44 +0000425 VIDEO_FB_ADRS framebuffer address
wdenkc6097192002-11-03 00:24:07 +0000426 VIDEO_KBD_INIT_FCT keyboard int fct
427 (i.e. i8042_kbd_init())
428 VIDEO_TSTC_FCT test char fct
429 (i.e. i8042_tstc)
430 VIDEO_GETC_FCT get char fct
431 (i.e. i8042_getc)
432 CONFIG_CONSOLE_CURSOR cursor drawing on/off
433 (requires blink timer
434 cf. i8042.c)
435 CFG_CONSOLE_BLINK_COUNT blink interval (cf. i8042.c)
436 CONFIG_CONSOLE_TIME display time/date info in
437 upper right corner
Jon Loeliger602ad3b2007-06-11 19:03:39 -0500438 (requires CONFIG_CMD_DATE)
wdenkc6097192002-11-03 00:24:07 +0000439 CONFIG_VIDEO_LOGO display Linux logo in
440 upper left corner
wdenka6c7ad22002-12-03 21:28:10 +0000441 CONFIG_VIDEO_BMP_LOGO use bmp_logo.h instead of
442 linux_logo.h for logo.
443 Requires CONFIG_VIDEO_LOGO
wdenkc6097192002-11-03 00:24:07 +0000444 CONFIG_CONSOLE_EXTRA_INFO
445 addional board info beside
446 the logo
447
wdenk43d96162003-03-06 00:02:04 +0000448 When CONFIG_CFB_CONSOLE is defined, video console is
449 default i/o. Serial console can be forced with
450 environment 'console=serial'.
wdenkc6097192002-11-03 00:24:07 +0000451
wdenkd4ca31c2004-01-02 14:00:00 +0000452 When CONFIG_SILENT_CONSOLE is defined, all console
453 messages (by U-Boot and Linux!) can be silenced with
454 the "silent" environment variable. See
455 doc/README.silent for more information.
wdenka3ad8e22003-10-19 23:22:11 +0000456
wdenkc6097192002-11-03 00:24:07 +0000457- Console Baudrate:
458 CONFIG_BAUDRATE - in bps
459 Select one of the baudrates listed in
460 CFG_BAUDRATE_TABLE, see below.
wdenk3bbc8992003-12-07 22:27:15 +0000461 CFG_BRGCLK_PRESCALE, baudrate prescale
wdenkc6097192002-11-03 00:24:07 +0000462
463- Interrupt driven serial port input:
464 CONFIG_SERIAL_SOFTWARE_FIFO
465
466 PPC405GP only.
467 Use an interrupt handler for receiving data on the
468 serial port. It also enables using hardware handshake
469 (RTS/CTS) and UART's built-in FIFO. Set the number of
470 bytes the interrupt driven input buffer should have.
471
wdenk109c0e32004-03-23 21:43:07 +0000472 Leave undefined to disable this feature, including
473 disable the buffer and hardware handshake.
wdenkc6097192002-11-03 00:24:07 +0000474
stroese1d49b1f2003-05-23 11:39:05 +0000475- Console UART Number:
476 CONFIG_UART1_CONSOLE
477
Wolfgang Denk0c8721a2005-09-23 11:05:55 +0200478 AMCC PPC4xx only.
stroese1d49b1f2003-05-23 11:39:05 +0000479 If defined internal UART1 (and not UART0) is used
480 as default U-Boot console.
481
wdenkc6097192002-11-03 00:24:07 +0000482- Boot Delay: CONFIG_BOOTDELAY - in seconds
483 Delay before automatically booting the default image;
484 set to -1 to disable autoboot.
485
486 See doc/README.autoboot for these options that
487 work with CONFIG_BOOTDELAY. None are required.
488 CONFIG_BOOT_RETRY_TIME
489 CONFIG_BOOT_RETRY_MIN
490 CONFIG_AUTOBOOT_KEYED
491 CONFIG_AUTOBOOT_PROMPT
492 CONFIG_AUTOBOOT_DELAY_STR
493 CONFIG_AUTOBOOT_STOP_STR
494 CONFIG_AUTOBOOT_DELAY_STR2
495 CONFIG_AUTOBOOT_STOP_STR2
496 CONFIG_ZERO_BOOTDELAY_CHECK
497 CONFIG_RESET_TO_RETRY
498
499- Autoboot Command:
500 CONFIG_BOOTCOMMAND
501 Only needed when CONFIG_BOOTDELAY is enabled;
502 define a command string that is automatically executed
503 when no character is read on the console interface
504 within "Boot Delay" after reset.
505
506 CONFIG_BOOTARGS
wdenk43d96162003-03-06 00:02:04 +0000507 This can be used to pass arguments to the bootm
508 command. The value of CONFIG_BOOTARGS goes into the
509 environment value "bootargs".
wdenkc6097192002-11-03 00:24:07 +0000510
511 CONFIG_RAMBOOT and CONFIG_NFSBOOT
wdenk43d96162003-03-06 00:02:04 +0000512 The value of these goes into the environment as
513 "ramboot" and "nfsboot" respectively, and can be used
514 as a convenience, when switching between booting from
515 ram and nfs.
wdenkc6097192002-11-03 00:24:07 +0000516
517- Pre-Boot Commands:
518 CONFIG_PREBOOT
519
520 When this option is #defined, the existence of the
521 environment variable "preboot" will be checked
522 immediately before starting the CONFIG_BOOTDELAY
523 countdown and/or running the auto-boot command resp.
524 entering interactive mode.
525
526 This feature is especially useful when "preboot" is
527 automatically generated or modified. For an example
528 see the LWMON board specific code: here "preboot" is
529 modified when the user holds down a certain
530 combination of keys on the (special) keyboard when
531 booting the systems
532
533- Serial Download Echo Mode:
534 CONFIG_LOADS_ECHO
535 If defined to 1, all characters received during a
536 serial download (using the "loads" command) are
537 echoed back. This might be needed by some terminal
538 emulations (like "cu"), but may as well just take
539 time on others. This setting #define's the initial
540 value of the "loads_echo" environment variable.
541
Jon Loeliger602ad3b2007-06-11 19:03:39 -0500542- Kgdb Serial Baudrate: (if CONFIG_CMD_KGDB is defined)
wdenkc6097192002-11-03 00:24:07 +0000543 CONFIG_KGDB_BAUDRATE
544 Select one of the baudrates listed in
545 CFG_BAUDRATE_TABLE, see below.
546
547- Monitor Functions:
Jon Loeliger602ad3b2007-06-11 19:03:39 -0500548 Monitor commands can be included or excluded
549 from the build by using the #include files
550 "config_cmd_all.h" and #undef'ing unwanted
551 commands, or using "config_cmd_default.h"
552 and augmenting with additional #define's
553 for wanted commands.
wdenkc6097192002-11-03 00:24:07 +0000554
Jon Loeliger602ad3b2007-06-11 19:03:39 -0500555 The default command configuration includes all commands
556 except those marked below with a "*".
wdenkc6097192002-11-03 00:24:07 +0000557
Jon Loeliger602ad3b2007-06-11 19:03:39 -0500558 CONFIG_CMD_ASKENV * ask for env variable
559 CONFIG_CMD_AUTOSCRIPT Autoscript Support
560 CONFIG_CMD_BDI bdinfo
561 CONFIG_CMD_BEDBUG * Include BedBug Debugger
562 CONFIG_CMD_BMP * BMP support
563 CONFIG_CMD_BSP * Board specific commands
564 CONFIG_CMD_BOOTD bootd
565 CONFIG_CMD_CACHE * icache, dcache
566 CONFIG_CMD_CONSOLE coninfo
567 CONFIG_CMD_DATE * support for RTC, date/time...
568 CONFIG_CMD_DHCP * DHCP support
569 CONFIG_CMD_DIAG * Diagnostics
570 CONFIG_CMD_DOC * Disk-On-Chip Support
571 CONFIG_CMD_DTT * Digital Therm and Thermostat
572 CONFIG_CMD_ECHO echo arguments
573 CONFIG_CMD_EEPROM * EEPROM read/write support
574 CONFIG_CMD_ELF * bootelf, bootvx
575 CONFIG_CMD_ENV saveenv
576 CONFIG_CMD_FDC * Floppy Disk Support
577 CONFIG_CMD_FAT * FAT partition support
578 CONFIG_CMD_FDOS * Dos diskette Support
579 CONFIG_CMD_FLASH flinfo, erase, protect
580 CONFIG_CMD_FPGA FPGA device initialization support
581 CONFIG_CMD_HWFLOW * RTS/CTS hw flow control
582 CONFIG_CMD_I2C * I2C serial bus support
583 CONFIG_CMD_IDE * IDE harddisk support
584 CONFIG_CMD_IMI iminfo
585 CONFIG_CMD_IMLS List all found images
586 CONFIG_CMD_IMMAP * IMMR dump support
587 CONFIG_CMD_IRQ * irqinfo
588 CONFIG_CMD_ITEST Integer/string test of 2 values
589 CONFIG_CMD_JFFS2 * JFFS2 Support
590 CONFIG_CMD_KGDB * kgdb
591 CONFIG_CMD_LOADB loadb
592 CONFIG_CMD_LOADS loads
593 CONFIG_CMD_MEMORY md, mm, nm, mw, cp, cmp, crc, base,
594 loop, loopw, mtest
595 CONFIG_CMD_MISC Misc functions like sleep etc
596 CONFIG_CMD_MMC * MMC memory mapped support
597 CONFIG_CMD_MII * MII utility commands
598 CONFIG_CMD_NAND * NAND support
599 CONFIG_CMD_NET bootp, tftpboot, rarpboot
600 CONFIG_CMD_PCI * pciinfo
601 CONFIG_CMD_PCMCIA * PCMCIA support
602 CONFIG_CMD_PING * send ICMP ECHO_REQUEST to network
603 host
604 CONFIG_CMD_PORTIO * Port I/O
605 CONFIG_CMD_REGINFO * Register dump
606 CONFIG_CMD_RUN run command in env variable
607 CONFIG_CMD_SAVES * save S record dump
608 CONFIG_CMD_SCSI * SCSI Support
609 CONFIG_CMD_SDRAM * print SDRAM configuration information
610 (requires CONFIG_CMD_I2C)
611 CONFIG_CMD_SETGETDCR Support for DCR Register access
612 (4xx only)
613 CONFIG_CMD_SPI * SPI serial bus support
614 CONFIG_CMD_USB * USB support
615 CONFIG_CMD_VFD * VFD support (TRAB)
616 CONFIG_CMD_BSP * Board SPecific functions
617 CONFIG_CMD_CDP * Cisco Discover Protocol support
618 CONFIG_CMD_FSL * Microblaze FSL support
wdenkc6097192002-11-03 00:24:07 +0000619
wdenkc6097192002-11-03 00:24:07 +0000620
621 EXAMPLE: If you want all functions except of network
622 support you can write:
623
Jon Loeliger602ad3b2007-06-11 19:03:39 -0500624 #include "config_cmd_all.h"
625 #undef CONFIG_CMD_NET
wdenkc6097192002-11-03 00:24:07 +0000626
Gerald Van Baren213bf8c2007-03-31 12:23:51 -0400627 Other Commands:
628 fdt (flattened device tree) command: CONFIG_OF_LIBFDT
wdenkc6097192002-11-03 00:24:07 +0000629
630 Note: Don't enable the "icache" and "dcache" commands
Jon Loeliger602ad3b2007-06-11 19:03:39 -0500631 (configuration option CONFIG_CMD_CACHE) unless you know
wdenk43d96162003-03-06 00:02:04 +0000632 what you (and your U-Boot users) are doing. Data
633 cache cannot be enabled on systems like the 8xx or
634 8260 (where accesses to the IMMR region must be
635 uncached), and it cannot be disabled on all other
636 systems where we (mis-) use the data cache to hold an
637 initial stack and some data.
wdenkc6097192002-11-03 00:24:07 +0000638
639
640 XXX - this list needs to get updated!
641
642- Watchdog:
643 CONFIG_WATCHDOG
644 If this variable is defined, it enables watchdog
wdenk7152b1d2003-09-05 23:19:14 +0000645 support. There must be support in the platform specific
wdenkc6097192002-11-03 00:24:07 +0000646 code for a watchdog. For the 8xx and 8260 CPUs, the
647 SIU Watchdog feature is enabled in the SYPCR
648 register.
649
stroesec1551ea2003-04-04 15:53:41 +0000650- U-Boot Version:
651 CONFIG_VERSION_VARIABLE
652 If this variable is defined, an environment variable
653 named "ver" is created by U-Boot showing the U-Boot
654 version as printed by the "version" command.
655 This variable is readonly.
656
wdenkc6097192002-11-03 00:24:07 +0000657- Real-Time Clock:
658
Jon Loeliger602ad3b2007-06-11 19:03:39 -0500659 When CONFIG_CMD_DATE is selected, the type of the RTC
wdenkc6097192002-11-03 00:24:07 +0000660 has to be selected, too. Define exactly one of the
661 following options:
662
663 CONFIG_RTC_MPC8xx - use internal RTC of MPC8xx
664 CONFIG_RTC_PCF8563 - use Philips PCF8563 RTC
665 CONFIG_RTC_MC146818 - use MC146818 RTC
wdenk1cb8e982003-03-06 21:55:29 +0000666 CONFIG_RTC_DS1307 - use Maxim, Inc. DS1307 RTC
wdenkc6097192002-11-03 00:24:07 +0000667 CONFIG_RTC_DS1337 - use Maxim, Inc. DS1337 RTC
wdenk7f70e852003-05-20 14:25:27 +0000668 CONFIG_RTC_DS1338 - use Maxim, Inc. DS1338 RTC
wdenk3bac3512003-03-12 10:41:04 +0000669 CONFIG_RTC_DS164x - use Dallas DS164x RTC
wdenk4c0d4c32004-06-09 17:34:58 +0000670 CONFIG_RTC_MAX6900 - use Maxim, Inc. MAX6900 RTC
wdenkc6097192002-11-03 00:24:07 +0000671
wdenkb37c7e52003-06-30 16:24:52 +0000672 Note that if the RTC uses I2C, then the I2C interface
673 must also be configured. See I2C Support, below.
674
wdenkc6097192002-11-03 00:24:07 +0000675- Timestamp Support:
676
wdenk43d96162003-03-06 00:02:04 +0000677 When CONFIG_TIMESTAMP is selected, the timestamp
678 (date and time) of an image is printed by image
679 commands like bootm or iminfo. This option is
Jon Loeliger602ad3b2007-06-11 19:03:39 -0500680 automatically enabled when you select CONFIG_CMD_DATE .
wdenkc6097192002-11-03 00:24:07 +0000681
682- Partition Support:
683 CONFIG_MAC_PARTITION and/or CONFIG_DOS_PARTITION
684 and/or CONFIG_ISO_PARTITION
685
Jon Loeliger602ad3b2007-06-11 19:03:39 -0500686 If IDE or SCSI support is enabled (CONFIG_CMD_IDE or
687 CONFIG_CMD_SCSI) you must configure support for at least
wdenkc6097192002-11-03 00:24:07 +0000688 one partition type as well.
689
690- IDE Reset method:
wdenk4d13cba2004-03-14 14:09:05 +0000691 CONFIG_IDE_RESET_ROUTINE - this is defined in several
692 board configurations files but used nowhere!
wdenkc6097192002-11-03 00:24:07 +0000693
wdenk4d13cba2004-03-14 14:09:05 +0000694 CONFIG_IDE_RESET - is this is defined, IDE Reset will
695 be performed by calling the function
696 ide_set_reset(int reset)
697 which has to be defined in a board specific file
wdenkc6097192002-11-03 00:24:07 +0000698
699- ATAPI Support:
700 CONFIG_ATAPI
701
702 Set this to enable ATAPI support.
703
wdenkc40b2952004-03-13 23:29:43 +0000704- LBA48 Support
705 CONFIG_LBA48
706
707 Set this to enable support for disks larger than 137GB
708 Also look at CFG_64BIT_LBA ,CFG_64BIT_VSPRINTF and CFG_64BIT_STRTOUL
709 Whithout these , LBA48 support uses 32bit variables and will 'only'
710 support disks up to 2.1TB.
711
712 CFG_64BIT_LBA:
713 When enabled, makes the IDE subsystem use 64bit sector addresses.
714 Default is 32bit.
715
wdenkc6097192002-11-03 00:24:07 +0000716- SCSI Support:
717 At the moment only there is only support for the
718 SYM53C8XX SCSI controller; define
719 CONFIG_SCSI_SYM53C8XX to enable it.
720
721 CFG_SCSI_MAX_LUN [8], CFG_SCSI_MAX_SCSI_ID [7] and
722 CFG_SCSI_MAX_DEVICE [CFG_SCSI_MAX_SCSI_ID *
723 CFG_SCSI_MAX_LUN] can be adjusted to define the
724 maximum numbers of LUNs, SCSI ID's and target
725 devices.
726 CFG_SCSI_SYM53C8XX_CCF to fix clock timing (80Mhz)
727
728- NETWORK Support (PCI):
wdenk682011f2003-06-03 23:54:09 +0000729 CONFIG_E1000
730 Support for Intel 8254x gigabit chips.
stroese53cf9432003-06-05 15:39:44 +0000731
wdenkc6097192002-11-03 00:24:07 +0000732 CONFIG_EEPRO100
733 Support for Intel 82557/82559/82559ER chips.
734 Optional CONFIG_EEPRO100_SROM_WRITE enables eeprom
735 write routine for first time initialisation.
736
737 CONFIG_TULIP
738 Support for Digital 2114x chips.
739 Optional CONFIG_TULIP_SELECT_MEDIA for board specific
740 modem chip initialisation (KS8761/QS6611).
741
742 CONFIG_NATSEMI
743 Support for National dp83815 chips.
744
745 CONFIG_NS8382X
746 Support for National dp8382[01] gigabit chips.
747
wdenk45219c42003-05-12 21:50:16 +0000748- NETWORK Support (other):
749
750 CONFIG_DRIVER_LAN91C96
751 Support for SMSC's LAN91C96 chips.
752
753 CONFIG_LAN91C96_BASE
754 Define this to hold the physical address
755 of the LAN91C96's I/O space
756
757 CONFIG_LAN91C96_USE_32_BIT
758 Define this to enable 32 bit addressing
759
wdenkf39748a2004-06-09 13:37:52 +0000760 CONFIG_DRIVER_SMC91111
761 Support for SMSC's LAN91C111 chip
762
763 CONFIG_SMC91111_BASE
764 Define this to hold the physical address
765 of the device (I/O space)
766
767 CONFIG_SMC_USE_32_BIT
768 Define this if data bus is 32 bits
769
770 CONFIG_SMC_USE_IOFUNCS
771 Define this to use i/o functions instead of macros
772 (some hardware wont work with macros)
773
wdenkc6097192002-11-03 00:24:07 +0000774- USB Support:
775 At the moment only the UHCI host controller is
wdenk4d13cba2004-03-14 14:09:05 +0000776 supported (PIP405, MIP405, MPC5200); define
wdenkc6097192002-11-03 00:24:07 +0000777 CONFIG_USB_UHCI to enable it.
778 define CONFIG_USB_KEYBOARD to enable the USB Keyboard
wdenk30d56fa2004-10-09 22:44:59 +0000779 and define CONFIG_USB_STORAGE to enable the USB
wdenkc6097192002-11-03 00:24:07 +0000780 storage devices.
781 Note:
782 Supported are USB Keyboards and USB Floppy drives
783 (TEAC FD-05PUB).
wdenk4d13cba2004-03-14 14:09:05 +0000784 MPC5200 USB requires additional defines:
785 CONFIG_USB_CLOCK
786 for 528 MHz Clock: 0x0001bbbb
787 CONFIG_USB_CONFIG
788 for differential drivers: 0x00001000
789 for single ended drivers: 0x00005000
Zhang Weifdcfaa12007-06-06 10:08:13 +0200790 CFG_USB_EVENT_POLL
791 May be defined to allow interrupt polling
792 instead of using asynchronous interrupts
wdenk4d13cba2004-03-14 14:09:05 +0000793
Wolfgang Denk16c8d5e2006-06-14 17:45:53 +0200794- USB Device:
795 Define the below if you wish to use the USB console.
796 Once firmware is rebuilt from a serial console issue the
797 command "setenv stdin usbtty; setenv stdout usbtty" and
798 attach your usb cable. The Unix command "dmesg" should print
799 it has found a new device. The environment variable usbtty
800 can be set to gserial or cdc_acm to enable your device to
Wolfgang Denk386eda02006-06-14 18:14:56 +0200801 appear to a USB host as a Linux gserial device or a
Wolfgang Denk16c8d5e2006-06-14 17:45:53 +0200802 Common Device Class Abstract Control Model serial device.
803 If you select usbtty = gserial you should be able to enumerate
804 a Linux host by
805 # modprobe usbserial vendor=0xVendorID product=0xProductID
806 else if using cdc_acm, simply setting the environment
807 variable usbtty to be cdc_acm should suffice. The following
808 might be defined in YourBoardName.h
Wolfgang Denk386eda02006-06-14 18:14:56 +0200809
Wolfgang Denk16c8d5e2006-06-14 17:45:53 +0200810 CONFIG_USB_DEVICE
811 Define this to build a UDC device
wdenkc6097192002-11-03 00:24:07 +0000812
Wolfgang Denk16c8d5e2006-06-14 17:45:53 +0200813 CONFIG_USB_TTY
814 Define this to have a tty type of device available to
815 talk to the UDC device
Wolfgang Denk386eda02006-06-14 18:14:56 +0200816
Wolfgang Denk16c8d5e2006-06-14 17:45:53 +0200817 CFG_CONSOLE_IS_IN_ENV
818 Define this if you want stdin, stdout &/or stderr to
819 be set to usbtty.
820
821 mpc8xx:
822 CFG_USB_EXTC_CLK 0xBLAH
823 Derive USB clock from external clock "blah"
Wolfgang Denk386eda02006-06-14 18:14:56 +0200824 - CFG_USB_EXTC_CLK 0x02
825
Wolfgang Denk16c8d5e2006-06-14 17:45:53 +0200826 CFG_USB_BRG_CLK 0xBLAH
827 Derive USB clock from brgclk
828 - CFG_USB_BRG_CLK 0x04
829
Wolfgang Denk386eda02006-06-14 18:14:56 +0200830 If you have a USB-IF assigned VendorID then you may wish to
Wolfgang Denk16c8d5e2006-06-14 17:45:53 +0200831 define your own vendor specific values either in BoardName.h
Wolfgang Denk386eda02006-06-14 18:14:56 +0200832 or directly in usbd_vendor_info.h. If you don't define
Wolfgang Denk16c8d5e2006-06-14 17:45:53 +0200833 CONFIG_USBD_MANUFACTURER, CONFIG_USBD_PRODUCT_NAME,
834 CONFIG_USBD_VENDORID and CONFIG_USBD_PRODUCTID, then U-Boot
835 should pretend to be a Linux device to it's target host.
836
837 CONFIG_USBD_MANUFACTURER
838 Define this string as the name of your company for
839 - CONFIG_USBD_MANUFACTURER "my company"
Wolfgang Denk386eda02006-06-14 18:14:56 +0200840
Wolfgang Denk16c8d5e2006-06-14 17:45:53 +0200841 CONFIG_USBD_PRODUCT_NAME
842 Define this string as the name of your product
843 - CONFIG_USBD_PRODUCT_NAME "acme usb device"
844
845 CONFIG_USBD_VENDORID
846 Define this as your assigned Vendor ID from the USB
847 Implementors Forum. This *must* be a genuine Vendor ID
848 to avoid polluting the USB namespace.
849 - CONFIG_USBD_VENDORID 0xFFFF
Wolfgang Denk386eda02006-06-14 18:14:56 +0200850
Wolfgang Denk16c8d5e2006-06-14 17:45:53 +0200851 CONFIG_USBD_PRODUCTID
852 Define this as the unique Product ID
853 for your device
854 - CONFIG_USBD_PRODUCTID 0xFFFF
wdenkc6097192002-11-03 00:24:07 +0000855
856
857- MMC Support:
858 The MMC controller on the Intel PXA is supported. To
859 enable this define CONFIG_MMC. The MMC can be
860 accessed from the boot prompt by mapping the device
861 to physical memory similar to flash. Command line is
Jon Loeliger602ad3b2007-06-11 19:03:39 -0500862 enabled with CONFIG_CMD_MMC. The MMC driver also works with
863 the FAT fs. This is enabled with CONFIG_CMD_FAT.
wdenkc6097192002-11-03 00:24:07 +0000864
wdenk6705d812004-08-02 23:22:59 +0000865- Journaling Flash filesystem support:
866 CONFIG_JFFS2_NAND, CONFIG_JFFS2_NAND_OFF, CONFIG_JFFS2_NAND_SIZE,
867 CONFIG_JFFS2_NAND_DEV
868 Define these for a default partition on a NAND device
869
870 CFG_JFFS2_FIRST_SECTOR,
871 CFG_JFFS2_FIRST_BANK, CFG_JFFS2_NUM_BANKS
872 Define these for a default partition on a NOR device
873
874 CFG_JFFS_CUSTOM_PART
875 Define this to create an own partition. You have to provide a
876 function struct part_info* jffs2_part_info(int part_num)
877
878 If you define only one JFFS2 partition you may also want to
wdenkefe2a4d2004-12-16 21:44:03 +0000879 #define CFG_JFFS_SINGLE_PART 1
wdenk6705d812004-08-02 23:22:59 +0000880 to disable the command chpart. This is the default when you
881 have not defined a custom partition
882
wdenkc6097192002-11-03 00:24:07 +0000883- Keyboard Support:
884 CONFIG_ISA_KEYBOARD
885
886 Define this to enable standard (PC-Style) keyboard
887 support
888
889 CONFIG_I8042_KBD
890 Standard PC keyboard driver with US (is default) and
891 GERMAN key layout (switch via environment 'keymap=de') support.
892 Export function i8042_kbd_init, i8042_tstc and i8042_getc
893 for cfb_console. Supports cursor blinking.
894
895- Video support:
896 CONFIG_VIDEO
897
898 Define this to enable video support (for output to
899 video).
900
901 CONFIG_VIDEO_CT69000
902
903 Enable Chips & Technologies 69000 Video chip
904
905 CONFIG_VIDEO_SMI_LYNXEM
wdenkb79a11c2004-03-25 15:14:43 +0000906 Enable Silicon Motion SMI 712/710/810 Video chip. The
wdenkeeb1b772004-03-23 22:53:55 +0000907 video output is selected via environment 'videoout'
908 (1 = LCD and 2 = CRT). If videoout is undefined, CRT is
909 assumed.
wdenkc6097192002-11-03 00:24:07 +0000910
wdenkb79a11c2004-03-25 15:14:43 +0000911 For the CT69000 and SMI_LYNXEM drivers, videomode is
912 selected via environment 'videomode'. Two diferent ways
wdenkeeb1b772004-03-23 22:53:55 +0000913 are possible:
914 - "videomode=num" 'num' is a standard LiLo mode numbers.
wdenk6e592382004-04-18 17:39:38 +0000915 Following standard modes are supported (* is default):
wdenkeeb1b772004-03-23 22:53:55 +0000916
917 Colors 640x480 800x600 1024x768 1152x864 1280x1024
918 -------------+---------------------------------------------
919 8 bits | 0x301* 0x303 0x305 0x161 0x307
920 15 bits | 0x310 0x313 0x316 0x162 0x319
921 16 bits | 0x311 0x314 0x317 0x163 0x31A
922 24 bits | 0x312 0x315 0x318 ? 0x31B
923 -------------+---------------------------------------------
wdenkc6097192002-11-03 00:24:07 +0000924 (i.e. setenv videomode 317; saveenv; reset;)
925
wdenkb79a11c2004-03-25 15:14:43 +0000926 - "videomode=bootargs" all the video parameters are parsed
wdenkeeb1b772004-03-23 22:53:55 +0000927 from the bootargs. (See drivers/videomodes.c)
928
929
stroesec1551ea2003-04-04 15:53:41 +0000930 CONFIG_VIDEO_SED13806
wdenk43d96162003-03-06 00:02:04 +0000931 Enable Epson SED13806 driver. This driver supports 8bpp
wdenka6c7ad22002-12-03 21:28:10 +0000932 and 16bpp modes defined by CONFIG_VIDEO_SED13806_8BPP
933 or CONFIG_VIDEO_SED13806_16BPP
934
wdenk682011f2003-06-03 23:54:09 +0000935- Keyboard Support:
wdenk8bde7f72003-06-27 21:31:46 +0000936 CONFIG_KEYBOARD
wdenk682011f2003-06-03 23:54:09 +0000937
wdenk8bde7f72003-06-27 21:31:46 +0000938 Define this to enable a custom keyboard support.
939 This simply calls drv_keyboard_init() which must be
940 defined in your board-specific files.
941 The only board using this so far is RBC823.
wdenka6c7ad22002-12-03 21:28:10 +0000942
wdenkc6097192002-11-03 00:24:07 +0000943- LCD Support: CONFIG_LCD
944
945 Define this to enable LCD support (for output to LCD
946 display); also select one of the supported displays
947 by defining one of these:
948
wdenkfd3103b2003-11-25 16:55:19 +0000949 CONFIG_NEC_NL6448AC33:
wdenkc6097192002-11-03 00:24:07 +0000950
wdenkfd3103b2003-11-25 16:55:19 +0000951 NEC NL6448AC33-18. Active, color, single scan.
wdenkc6097192002-11-03 00:24:07 +0000952
wdenkfd3103b2003-11-25 16:55:19 +0000953 CONFIG_NEC_NL6448BC20
wdenkc6097192002-11-03 00:24:07 +0000954
wdenkfd3103b2003-11-25 16:55:19 +0000955 NEC NL6448BC20-08. 6.5", 640x480.
956 Active, color, single scan.
957
958 CONFIG_NEC_NL6448BC33_54
959
960 NEC NL6448BC33-54. 10.4", 640x480.
wdenkc6097192002-11-03 00:24:07 +0000961 Active, color, single scan.
962
963 CONFIG_SHARP_16x9
964
965 Sharp 320x240. Active, color, single scan.
966 It isn't 16x9, and I am not sure what it is.
967
968 CONFIG_SHARP_LQ64D341
969
970 Sharp LQ64D341 display, 640x480.
971 Active, color, single scan.
972
973 CONFIG_HLD1045
974
975 HLD1045 display, 640x480.
976 Active, color, single scan.
977
978 CONFIG_OPTREX_BW
979
980 Optrex CBL50840-2 NF-FW 99 22 M5
981 or
982 Hitachi LMG6912RPFC-00T
983 or
984 Hitachi SP14Q002
985
986 320x240. Black & white.
987
988 Normally display is black on white background; define
989 CFG_WHITE_ON_BLACK to get it inverted.
990
wdenk7152b1d2003-09-05 23:19:14 +0000991- Splash Screen Support: CONFIG_SPLASH_SCREEN
wdenkd791b1d2003-04-20 14:04:18 +0000992
wdenk8bde7f72003-06-27 21:31:46 +0000993 If this option is set, the environment is checked for
994 a variable "splashimage". If found, the usual display
995 of logo, copyright and system information on the LCD
wdenke94d2cd2004-06-30 22:59:18 +0000996 is suppressed and the BMP image at the address
wdenk8bde7f72003-06-27 21:31:46 +0000997 specified in "splashimage" is loaded instead. The
998 console is redirected to the "nulldev", too. This
999 allows for a "silent" boot where a splash screen is
1000 loaded very quickly after power-on.
wdenkd791b1d2003-04-20 14:04:18 +00001001
Stefan Roese98f4a3d2005-09-22 09:04:17 +02001002- Gzip compressed BMP image support: CONFIG_VIDEO_BMP_GZIP
1003
1004 If this option is set, additionally to standard BMP
1005 images, gzipped BMP images can be displayed via the
1006 splashscreen support or the bmp command.
1007
wdenkc29fdfc2003-08-29 20:57:53 +00001008- Compression support:
1009 CONFIG_BZIP2
1010
1011 If this option is set, support for bzip2 compressed
1012 images is included. If not, only uncompressed and gzip
1013 compressed images are supported.
1014
wdenk42d1f032003-10-15 23:53:47 +00001015 NOTE: the bzip2 algorithm requires a lot of RAM, so
1016 the malloc area (as defined by CFG_MALLOC_LEN) should
1017 be at least 4MB.
wdenkd791b1d2003-04-20 14:04:18 +00001018
wdenk17ea1172004-06-06 21:51:03 +00001019- MII/PHY support:
1020 CONFIG_PHY_ADDR
1021
1022 The address of PHY on MII bus.
1023
1024 CONFIG_PHY_CLOCK_FREQ (ppc4xx)
1025
1026 The clock frequency of the MII bus
1027
1028 CONFIG_PHY_GIGE
1029
1030 If this option is set, support for speed/duplex
1031 detection of Gigabit PHY is included.
1032
1033 CONFIG_PHY_RESET_DELAY
1034
1035 Some PHY like Intel LXT971A need extra delay after
1036 reset before any MII register access is possible.
1037 For such PHY, set this option to the usec delay
1038 required. (minimum 300usec for LXT971A)
1039
1040 CONFIG_PHY_CMD_DELAY (ppc4xx)
1041
1042 Some PHY like Intel LXT971A need extra delay after
1043 command issued before MII status register can be read
1044
wdenkc6097192002-11-03 00:24:07 +00001045- Ethernet address:
1046 CONFIG_ETHADDR
1047 CONFIG_ETH2ADDR
1048 CONFIG_ETH3ADDR
1049
1050 Define a default value for ethernet address to use
1051 for the respective ethernet interface, in case this
1052 is not determined automatically.
1053
1054- IP address:
1055 CONFIG_IPADDR
1056
1057 Define a default value for the IP address to use for
1058 the default ethernet interface, in case this is not
1059 determined through e.g. bootp.
1060
1061- Server IP address:
1062 CONFIG_SERVERIP
1063
1064 Defines a default value for theIP address of a TFTP
1065 server to contact when using the "tftboot" command.
1066
David Updegraff53a5c422007-06-11 10:41:07 -05001067- Multicast TFTP Mode:
1068 CONFIG_MCAST_TFTP
1069
1070 Defines whether you want to support multicast TFTP as per
1071 rfc-2090; for example to work with atftp. Lets lots of targets
1072 tftp down the same boot image concurrently. Note: the ethernet
1073 driver in use must provide a function: mcast() to join/leave a
1074 multicast group.
1075
1076 CONFIG_BOOTP_RANDOM_DELAY
wdenkc6097192002-11-03 00:24:07 +00001077- BOOTP Recovery Mode:
1078 CONFIG_BOOTP_RANDOM_DELAY
1079
1080 If you have many targets in a network that try to
1081 boot using BOOTP, you may want to avoid that all
1082 systems send out BOOTP requests at precisely the same
1083 moment (which would happen for instance at recovery
1084 from a power failure, when all systems will try to
1085 boot, thus flooding the BOOTP server. Defining
1086 CONFIG_BOOTP_RANDOM_DELAY causes a random delay to be
1087 inserted before sending out BOOTP requests. The
Wolfgang Denk6c33c782007-08-06 23:21:05 +02001088 following delays are inserted then:
wdenkc6097192002-11-03 00:24:07 +00001089
1090 1st BOOTP request: delay 0 ... 1 sec
1091 2nd BOOTP request: delay 0 ... 2 sec
1092 3rd BOOTP request: delay 0 ... 4 sec
1093 4th and following
1094 BOOTP requests: delay 0 ... 8 sec
1095
stroesefe389a82003-08-28 14:17:32 +00001096- DHCP Advanced Options:
Jon Loeliger1fe80d72007-07-09 22:08:34 -05001097 You can fine tune the DHCP functionality by defining
1098 CONFIG_BOOTP_* symbols:
stroesefe389a82003-08-28 14:17:32 +00001099
Jon Loeliger1fe80d72007-07-09 22:08:34 -05001100 CONFIG_BOOTP_SUBNETMASK
1101 CONFIG_BOOTP_GATEWAY
1102 CONFIG_BOOTP_HOSTNAME
1103 CONFIG_BOOTP_NISDOMAIN
1104 CONFIG_BOOTP_BOOTPATH
1105 CONFIG_BOOTP_BOOTFILESIZE
1106 CONFIG_BOOTP_DNS
1107 CONFIG_BOOTP_DNS2
1108 CONFIG_BOOTP_SEND_HOSTNAME
1109 CONFIG_BOOTP_NTPSERVER
1110 CONFIG_BOOTP_TIMEOFFSET
1111 CONFIG_BOOTP_VENDOREX
stroesefe389a82003-08-28 14:17:32 +00001112
Wilson Callan5d110f02007-07-28 10:56:13 -04001113 CONFIG_BOOTP_SERVERIP - TFTP server will be the serverip
1114 environment variable, not the BOOTP server.
stroesefe389a82003-08-28 14:17:32 +00001115
1116 CONFIG_BOOTP_DNS2 - If a DHCP client requests the DNS
1117 serverip from a DHCP server, it is possible that more
1118 than one DNS serverip is offered to the client.
1119 If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1120 serverip will be stored in the additional environment
1121 variable "dnsip2". The first DNS serverip is always
1122 stored in the variable "dnsip", when CONFIG_BOOTP_DNS
Jon Loeliger1fe80d72007-07-09 22:08:34 -05001123 is defined.
stroesefe389a82003-08-28 14:17:32 +00001124
1125 CONFIG_BOOTP_SEND_HOSTNAME - Some DHCP servers are capable
1126 to do a dynamic update of a DNS server. To do this, they
1127 need the hostname of the DHCP requester.
Wilson Callan5d110f02007-07-28 10:56:13 -04001128 If CONFIG_BOOTP_SEND_HOSTNAME is defined, the content
Jon Loeliger1fe80d72007-07-09 22:08:34 -05001129 of the "hostname" environment variable is passed as
1130 option 12 to the DHCP server.
stroesefe389a82003-08-28 14:17:32 +00001131
wdenka3d991b2004-04-15 21:48:45 +00001132 - CDP Options:
wdenk6e592382004-04-18 17:39:38 +00001133 CONFIG_CDP_DEVICE_ID
wdenka3d991b2004-04-15 21:48:45 +00001134
1135 The device id used in CDP trigger frames.
1136
1137 CONFIG_CDP_DEVICE_ID_PREFIX
1138
1139 A two character string which is prefixed to the MAC address
1140 of the device.
1141
1142 CONFIG_CDP_PORT_ID
1143
1144 A printf format string which contains the ascii name of
1145 the port. Normally is set to "eth%d" which sets
1146 eth0 for the first ethernet, eth1 for the second etc.
1147
1148 CONFIG_CDP_CAPABILITIES
1149
1150 A 32bit integer which indicates the device capabilities;
1151 0x00000010 for a normal host which does not forwards.
1152
1153 CONFIG_CDP_VERSION
1154
1155 An ascii string containing the version of the software.
1156
1157 CONFIG_CDP_PLATFORM
1158
1159 An ascii string containing the name of the platform.
1160
1161 CONFIG_CDP_TRIGGER
1162
1163 A 32bit integer sent on the trigger.
1164
1165 CONFIG_CDP_POWER_CONSUMPTION
1166
1167 A 16bit integer containing the power consumption of the
1168 device in .1 of milliwatts.
1169
1170 CONFIG_CDP_APPLIANCE_VLAN_TYPE
1171
1172 A byte containing the id of the VLAN.
1173
wdenkc6097192002-11-03 00:24:07 +00001174- Status LED: CONFIG_STATUS_LED
1175
1176 Several configurations allow to display the current
1177 status using a LED. For instance, the LED will blink
1178 fast while running U-Boot code, stop blinking as
1179 soon as a reply to a BOOTP request was received, and
1180 start blinking slow once the Linux kernel is running
1181 (supported by a status LED driver in the Linux
1182 kernel). Defining CONFIG_STATUS_LED enables this
1183 feature in U-Boot.
1184
1185- CAN Support: CONFIG_CAN_DRIVER
1186
1187 Defining CONFIG_CAN_DRIVER enables CAN driver support
1188 on those systems that support this (optional)
1189 feature, like the TQM8xxL modules.
1190
1191- I2C Support: CONFIG_HARD_I2C | CONFIG_SOFT_I2C
1192
wdenkb37c7e52003-06-30 16:24:52 +00001193 These enable I2C serial bus commands. Defining either of
wdenk945af8d2003-07-16 21:53:01 +00001194 (but not both of) CONFIG_HARD_I2C or CONFIG_SOFT_I2C will
1195 include the appropriate I2C driver for the selected cpu.
wdenkc6097192002-11-03 00:24:07 +00001196
wdenk945af8d2003-07-16 21:53:01 +00001197 This will allow you to use i2c commands at the u-boot
Jon Loeliger602ad3b2007-06-11 19:03:39 -05001198 command line (as long as you set CONFIG_CMD_I2C in
wdenkb37c7e52003-06-30 16:24:52 +00001199 CONFIG_COMMANDS) and communicate with i2c based realtime
1200 clock chips. See common/cmd_i2c.c for a description of the
wdenk43d96162003-03-06 00:02:04 +00001201 command line interface.
wdenkc6097192002-11-03 00:24:07 +00001202
Ben Warrenbb99ad62006-09-07 16:50:54 -04001203 CONFIG_I2C_CMD_TREE is a recommended option that places
1204 all I2C commands under a single 'i2c' root command. The
1205 older 'imm', 'imd', 'iprobe' etc. commands are considered
1206 deprecated and may disappear in the future.
1207
1208 CONFIG_HARD_I2C selects a hardware I2C controller.
wdenkc6097192002-11-03 00:24:07 +00001209
wdenk945af8d2003-07-16 21:53:01 +00001210 CONFIG_SOFT_I2C configures u-boot to use a software (aka
wdenkb37c7e52003-06-30 16:24:52 +00001211 bit-banging) driver instead of CPM or similar hardware
1212 support for I2C.
wdenkc6097192002-11-03 00:24:07 +00001213
wdenk945af8d2003-07-16 21:53:01 +00001214 There are several other quantities that must also be
wdenkb37c7e52003-06-30 16:24:52 +00001215 defined when you define CONFIG_HARD_I2C or CONFIG_SOFT_I2C.
wdenkc6097192002-11-03 00:24:07 +00001216
wdenkb37c7e52003-06-30 16:24:52 +00001217 In both cases you will need to define CFG_I2C_SPEED
wdenk945af8d2003-07-16 21:53:01 +00001218 to be the frequency (in Hz) at which you wish your i2c bus
1219 to run and CFG_I2C_SLAVE to be the address of this node (ie
1220 the cpu's i2c node address).
1221
wdenkb37c7e52003-06-30 16:24:52 +00001222 Now, the u-boot i2c code for the mpc8xx (cpu/mpc8xx/i2c.c)
1223 sets the cpu up as a master node and so its address should
1224 therefore be cleared to 0 (See, eg, MPC823e User's Manual
wdenk945af8d2003-07-16 21:53:01 +00001225 p.16-473). So, set CFG_I2C_SLAVE to 0.
wdenkc6097192002-11-03 00:24:07 +00001226
wdenk945af8d2003-07-16 21:53:01 +00001227 That's all that's required for CONFIG_HARD_I2C.
wdenkb37c7e52003-06-30 16:24:52 +00001228
1229 If you use the software i2c interface (CONFIG_SOFT_I2C)
1230 then the following macros need to be defined (examples are
1231 from include/configs/lwmon.h):
wdenkc6097192002-11-03 00:24:07 +00001232
1233 I2C_INIT
1234
wdenkb37c7e52003-06-30 16:24:52 +00001235 (Optional). Any commands necessary to enable the I2C
wdenk43d96162003-03-06 00:02:04 +00001236 controller or configure ports.
wdenkc6097192002-11-03 00:24:07 +00001237
wdenkba56f622004-02-06 23:19:44 +00001238 eg: #define I2C_INIT (immr->im_cpm.cp_pbdir |= PB_SCL)
wdenkb37c7e52003-06-30 16:24:52 +00001239
wdenkc6097192002-11-03 00:24:07 +00001240 I2C_PORT
1241
wdenk43d96162003-03-06 00:02:04 +00001242 (Only for MPC8260 CPU). The I/O port to use (the code
1243 assumes both bits are on the same port). Valid values
1244 are 0..3 for ports A..D.
wdenkc6097192002-11-03 00:24:07 +00001245
1246 I2C_ACTIVE
1247
1248 The code necessary to make the I2C data line active
1249 (driven). If the data line is open collector, this
1250 define can be null.
1251
wdenkb37c7e52003-06-30 16:24:52 +00001252 eg: #define I2C_ACTIVE (immr->im_cpm.cp_pbdir |= PB_SDA)
1253
wdenkc6097192002-11-03 00:24:07 +00001254 I2C_TRISTATE
1255
1256 The code necessary to make the I2C data line tri-stated
1257 (inactive). If the data line is open collector, this
1258 define can be null.
1259
wdenkb37c7e52003-06-30 16:24:52 +00001260 eg: #define I2C_TRISTATE (immr->im_cpm.cp_pbdir &= ~PB_SDA)
1261
wdenkc6097192002-11-03 00:24:07 +00001262 I2C_READ
1263
1264 Code that returns TRUE if the I2C data line is high,
1265 FALSE if it is low.
1266
wdenkb37c7e52003-06-30 16:24:52 +00001267 eg: #define I2C_READ ((immr->im_cpm.cp_pbdat & PB_SDA) != 0)
1268
wdenkc6097192002-11-03 00:24:07 +00001269 I2C_SDA(bit)
1270
1271 If <bit> is TRUE, sets the I2C data line high. If it
1272 is FALSE, it clears it (low).
1273
wdenkb37c7e52003-06-30 16:24:52 +00001274 eg: #define I2C_SDA(bit) \
wdenk2535d602003-07-17 23:16:40 +00001275 if(bit) immr->im_cpm.cp_pbdat |= PB_SDA; \
wdenkba56f622004-02-06 23:19:44 +00001276 else immr->im_cpm.cp_pbdat &= ~PB_SDA
wdenkb37c7e52003-06-30 16:24:52 +00001277
wdenkc6097192002-11-03 00:24:07 +00001278 I2C_SCL(bit)
1279
1280 If <bit> is TRUE, sets the I2C clock line high. If it
1281 is FALSE, it clears it (low).
1282
wdenkb37c7e52003-06-30 16:24:52 +00001283 eg: #define I2C_SCL(bit) \
wdenk2535d602003-07-17 23:16:40 +00001284 if(bit) immr->im_cpm.cp_pbdat |= PB_SCL; \
wdenkba56f622004-02-06 23:19:44 +00001285 else immr->im_cpm.cp_pbdat &= ~PB_SCL
wdenkb37c7e52003-06-30 16:24:52 +00001286
wdenkc6097192002-11-03 00:24:07 +00001287 I2C_DELAY
1288
1289 This delay is invoked four times per clock cycle so this
1290 controls the rate of data transfer. The data rate thus
wdenkb37c7e52003-06-30 16:24:52 +00001291 is 1 / (I2C_DELAY * 4). Often defined to be something
wdenk945af8d2003-07-16 21:53:01 +00001292 like:
1293
wdenkb37c7e52003-06-30 16:24:52 +00001294 #define I2C_DELAY udelay(2)
wdenkc6097192002-11-03 00:24:07 +00001295
wdenk47cd00f2003-03-06 13:39:27 +00001296 CFG_I2C_INIT_BOARD
1297
wdenk8bde7f72003-06-27 21:31:46 +00001298 When a board is reset during an i2c bus transfer
1299 chips might think that the current transfer is still
1300 in progress. On some boards it is possible to access
1301 the i2c SCLK line directly, either by using the
1302 processor pin as a GPIO or by having a second pin
1303 connected to the bus. If this option is defined a
1304 custom i2c_init_board() routine in boards/xxx/board.c
1305 is run early in the boot sequence.
wdenk47cd00f2003-03-06 13:39:27 +00001306
wdenk17ea1172004-06-06 21:51:03 +00001307 CONFIG_I2CFAST (PPC405GP|PPC405EP only)
1308
1309 This option enables configuration of bi_iic_fast[] flags
1310 in u-boot bd_info structure based on u-boot environment
1311 variable "i2cfast". (see also i2cfast)
1312
Ben Warrenbb99ad62006-09-07 16:50:54 -04001313 CONFIG_I2C_MULTI_BUS
1314
1315 This option allows the use of multiple I2C buses, each of which
1316 must have a controller. At any point in time, only one bus is
1317 active. To switch to a different bus, use the 'i2c dev' command.
1318 Note that bus numbering is zero-based.
1319
1320 CFG_I2C_NOPROBES
1321
1322 This option specifies a list of I2C devices that will be skipped
1323 when the 'i2c probe' command is issued (or 'iprobe' using the legacy
1324 command). If CONFIG_I2C_MULTI_BUS is set, specify a list of bus-device
1325 pairs. Otherwise, specify a 1D array of device addresses
1326
1327 e.g.
1328 #undef CONFIG_I2C_MULTI_BUS
1329 #define CFG_I2C_NOPROBES {0x50,0x68}
1330
1331 will skip addresses 0x50 and 0x68 on a board with one I2C bus
1332
1333 #define CONFIG_I2C_MULTI_BUS
1334 #define CFG_I2C_MULTI_NOPROBES {{0,0x50},{0,0x68},{1,0x54}}
1335
1336 will skip addresses 0x50 and 0x68 on bus 0 and address 0x54 on bus 1
1337
Timur Tabibe5e6182006-11-03 19:15:00 -06001338 CFG_SPD_BUS_NUM
1339
1340 If defined, then this indicates the I2C bus number for DDR SPD.
1341 If not defined, then U-Boot assumes that SPD is on I2C bus 0.
1342
Stefan Roese0dc018e2007-02-20 10:51:26 +01001343 CFG_RTC_BUS_NUM
1344
1345 If defined, then this indicates the I2C bus number for the RTC.
1346 If not defined, then U-Boot assumes that RTC is on I2C bus 0.
1347
1348 CFG_DTT_BUS_NUM
1349
1350 If defined, then this indicates the I2C bus number for the DTT.
1351 If not defined, then U-Boot assumes that DTT is on I2C bus 0.
1352
Timur Tabibe5e6182006-11-03 19:15:00 -06001353 CONFIG_FSL_I2C
1354
1355 Define this option if you want to use Freescale's I2C driver in
1356 drivers/fsl_i2c.c.
1357
1358
wdenkc6097192002-11-03 00:24:07 +00001359- SPI Support: CONFIG_SPI
1360
1361 Enables SPI driver (so far only tested with
1362 SPI EEPROM, also an instance works with Crystal A/D and
1363 D/As on the SACSng board)
1364
1365 CONFIG_SPI_X
1366
1367 Enables extended (16-bit) SPI EEPROM addressing.
1368 (symmetrical to CONFIG_I2C_X)
1369
1370 CONFIG_SOFT_SPI
1371
wdenk43d96162003-03-06 00:02:04 +00001372 Enables a software (bit-bang) SPI driver rather than
1373 using hardware support. This is a general purpose
1374 driver that only requires three general I/O port pins
1375 (two outputs, one input) to function. If this is
1376 defined, the board configuration must define several
1377 SPI configuration items (port pins to use, etc). For
1378 an example, see include/configs/sacsng.h.
wdenkc6097192002-11-03 00:24:07 +00001379
1380- FPGA Support: CONFIG_FPGA_COUNT
1381
wdenk43d96162003-03-06 00:02:04 +00001382 Specify the number of FPGA devices to support.
wdenkc6097192002-11-03 00:24:07 +00001383
wdenk43d96162003-03-06 00:02:04 +00001384 CONFIG_FPGA
wdenkc6097192002-11-03 00:24:07 +00001385
wdenk8bde7f72003-06-27 21:31:46 +00001386 Used to specify the types of FPGA devices. For example,
1387 #define CONFIG_FPGA CFG_XILINX_VIRTEX2
wdenkc6097192002-11-03 00:24:07 +00001388
wdenk8bde7f72003-06-27 21:31:46 +00001389 CFG_FPGA_PROG_FEEDBACK
wdenkc6097192002-11-03 00:24:07 +00001390
wdenk8bde7f72003-06-27 21:31:46 +00001391 Enable printing of hash marks during FPGA configuration.
wdenkc6097192002-11-03 00:24:07 +00001392
1393 CFG_FPGA_CHECK_BUSY
1394
wdenk43d96162003-03-06 00:02:04 +00001395 Enable checks on FPGA configuration interface busy
1396 status by the configuration function. This option
1397 will require a board or device specific function to
1398 be written.
wdenkc6097192002-11-03 00:24:07 +00001399
1400 CONFIG_FPGA_DELAY
1401
1402 If defined, a function that provides delays in the FPGA
1403 configuration driver.
1404
1405 CFG_FPGA_CHECK_CTRLC
1406 Allow Control-C to interrupt FPGA configuration
1407
1408 CFG_FPGA_CHECK_ERROR
1409
wdenk43d96162003-03-06 00:02:04 +00001410 Check for configuration errors during FPGA bitfile
1411 loading. For example, abort during Virtex II
1412 configuration if the INIT_B line goes low (which
1413 indicated a CRC error).
wdenkc6097192002-11-03 00:24:07 +00001414
1415 CFG_FPGA_WAIT_INIT
1416
wdenk43d96162003-03-06 00:02:04 +00001417 Maximum time to wait for the INIT_B line to deassert
1418 after PROB_B has been deasserted during a Virtex II
1419 FPGA configuration sequence. The default time is 500
1420 mS.
wdenkc6097192002-11-03 00:24:07 +00001421
1422 CFG_FPGA_WAIT_BUSY
1423
wdenk43d96162003-03-06 00:02:04 +00001424 Maximum time to wait for BUSY to deassert during
1425 Virtex II FPGA configuration. The default is 5 mS.
wdenkc6097192002-11-03 00:24:07 +00001426
1427 CFG_FPGA_WAIT_CONFIG
1428
wdenk43d96162003-03-06 00:02:04 +00001429 Time to wait after FPGA configuration. The default is
1430 200 mS.
wdenkc6097192002-11-03 00:24:07 +00001431
1432- Configuration Management:
1433 CONFIG_IDENT_STRING
1434
wdenk43d96162003-03-06 00:02:04 +00001435 If defined, this string will be added to the U-Boot
1436 version information (U_BOOT_VERSION)
wdenkc6097192002-11-03 00:24:07 +00001437
1438- Vendor Parameter Protection:
1439
wdenk43d96162003-03-06 00:02:04 +00001440 U-Boot considers the values of the environment
1441 variables "serial#" (Board Serial Number) and
wdenk7152b1d2003-09-05 23:19:14 +00001442 "ethaddr" (Ethernet Address) to be parameters that
wdenk43d96162003-03-06 00:02:04 +00001443 are set once by the board vendor / manufacturer, and
1444 protects these variables from casual modification by
1445 the user. Once set, these variables are read-only,
1446 and write or delete attempts are rejected. You can
1447 change this behviour:
wdenkc6097192002-11-03 00:24:07 +00001448
1449 If CONFIG_ENV_OVERWRITE is #defined in your config
1450 file, the write protection for vendor parameters is
wdenk47cd00f2003-03-06 13:39:27 +00001451 completely disabled. Anybody can change or delete
wdenkc6097192002-11-03 00:24:07 +00001452 these parameters.
1453
1454 Alternatively, if you #define _both_ CONFIG_ETHADDR
1455 _and_ CONFIG_OVERWRITE_ETHADDR_ONCE, a default
1456 ethernet address is installed in the environment,
1457 which can be changed exactly ONCE by the user. [The
1458 serial# is unaffected by this, i. e. it remains
1459 read-only.]
1460
1461- Protected RAM:
1462 CONFIG_PRAM
1463
1464 Define this variable to enable the reservation of
1465 "protected RAM", i. e. RAM which is not overwritten
1466 by U-Boot. Define CONFIG_PRAM to hold the number of
1467 kB you want to reserve for pRAM. You can overwrite
1468 this default value by defining an environment
1469 variable "pram" to the number of kB you want to
1470 reserve. Note that the board info structure will
1471 still show the full amount of RAM. If pRAM is
1472 reserved, a new environment variable "mem" will
1473 automatically be defined to hold the amount of
1474 remaining RAM in a form that can be passed as boot
1475 argument to Linux, for instance like that:
1476
Wolfgang Denkfe126d82005-11-20 21:40:11 +01001477 setenv bootargs ... mem=\${mem}
wdenkc6097192002-11-03 00:24:07 +00001478 saveenv
1479
1480 This way you can tell Linux not to use this memory,
1481 either, which results in a memory region that will
1482 not be affected by reboots.
1483
1484 *WARNING* If your board configuration uses automatic
1485 detection of the RAM size, you must make sure that
1486 this memory test is non-destructive. So far, the
1487 following board configurations are known to be
1488 "pRAM-clean":
1489
1490 ETX094, IVMS8, IVML24, SPD8xx, TQM8xxL,
1491 HERMES, IP860, RPXlite, LWMON, LANTEC,
1492 PCU_E, FLAGADM, TQM8260
1493
1494- Error Recovery:
1495 CONFIG_PANIC_HANG
1496
1497 Define this variable to stop the system in case of a
1498 fatal error, so that you have to reset it manually.
1499 This is probably NOT a good idea for an embedded
1500 system where you want to system to reboot
1501 automatically as fast as possible, but it may be
1502 useful during development since you can try to debug
1503 the conditions that lead to the situation.
1504
1505 CONFIG_NET_RETRY_COUNT
1506
wdenk43d96162003-03-06 00:02:04 +00001507 This variable defines the number of retries for
1508 network operations like ARP, RARP, TFTP, or BOOTP
1509 before giving up the operation. If not defined, a
1510 default value of 5 is used.
wdenkc6097192002-11-03 00:24:07 +00001511
1512- Command Interpreter:
Wolfgang Denk8078f1a2006-10-28 02:28:02 +02001513 CONFIG_AUTO_COMPLETE
wdenk04a85b32004-04-15 18:22:41 +00001514
1515 Enable auto completion of commands using TAB.
1516
Wolfgang Denka9398e02006-11-27 15:32:42 +01001517 Note that this feature has NOT been implemented yet
1518 for the "hush" shell.
Wolfgang Denk8078f1a2006-10-28 02:28:02 +02001519
1520
wdenkc6097192002-11-03 00:24:07 +00001521 CFG_HUSH_PARSER
1522
1523 Define this variable to enable the "hush" shell (from
1524 Busybox) as command line interpreter, thus enabling
1525 powerful command line syntax like
1526 if...then...else...fi conditionals or `&&' and '||'
1527 constructs ("shell scripts").
1528
1529 If undefined, you get the old, much simpler behaviour
1530 with a somewhat smaller memory footprint.
1531
1532
1533 CFG_PROMPT_HUSH_PS2
1534
1535 This defines the secondary prompt string, which is
1536 printed when the command interpreter needs more input
1537 to complete a command. Usually "> ".
1538
1539 Note:
1540
wdenk8bde7f72003-06-27 21:31:46 +00001541 In the current implementation, the local variables
1542 space and global environment variables space are
1543 separated. Local variables are those you define by
1544 simply typing `name=value'. To access a local
1545 variable later on, you have write `$name' or
1546 `${name}'; to execute the contents of a variable
1547 directly type `$name' at the command prompt.
wdenkc6097192002-11-03 00:24:07 +00001548
wdenk43d96162003-03-06 00:02:04 +00001549 Global environment variables are those you use
1550 setenv/printenv to work with. To run a command stored
1551 in such a variable, you need to use the run command,
1552 and you must not use the '$' sign to access them.
wdenkc6097192002-11-03 00:24:07 +00001553
1554 To store commands and special characters in a
1555 variable, please use double quotation marks
1556 surrounding the whole text of the variable, instead
1557 of the backslashes before semicolons and special
1558 symbols.
1559
Wolfgang Denkaa0c71a2006-07-21 11:35:21 +02001560- Commandline Editing and History:
1561 CONFIG_CMDLINE_EDITING
1562
Wolfgang Denkb9365a22006-07-21 11:56:05 +02001563 Enable editiong and History functions for interactive
1564 commandline input operations
Wolfgang Denkaa0c71a2006-07-21 11:35:21 +02001565
wdenka8c7c702003-12-06 19:49:23 +00001566- Default Environment:
wdenkc6097192002-11-03 00:24:07 +00001567 CONFIG_EXTRA_ENV_SETTINGS
1568
wdenk43d96162003-03-06 00:02:04 +00001569 Define this to contain any number of null terminated
1570 strings (variable = value pairs) that will be part of
wdenk7152b1d2003-09-05 23:19:14 +00001571 the default environment compiled into the boot image.
wdenk2262cfe2002-11-18 00:14:45 +00001572
wdenk43d96162003-03-06 00:02:04 +00001573 For example, place something like this in your
1574 board's config file:
wdenkc6097192002-11-03 00:24:07 +00001575
1576 #define CONFIG_EXTRA_ENV_SETTINGS \
1577 "myvar1=value1\0" \
1578 "myvar2=value2\0"
1579
wdenk43d96162003-03-06 00:02:04 +00001580 Warning: This method is based on knowledge about the
1581 internal format how the environment is stored by the
1582 U-Boot code. This is NOT an official, exported
1583 interface! Although it is unlikely that this format
wdenk7152b1d2003-09-05 23:19:14 +00001584 will change soon, there is no guarantee either.
wdenkc6097192002-11-03 00:24:07 +00001585 You better know what you are doing here.
1586
wdenk43d96162003-03-06 00:02:04 +00001587 Note: overly (ab)use of the default environment is
1588 discouraged. Make sure to check other ways to preset
1589 the environment like the autoscript function or the
1590 boot command first.
wdenkc6097192002-11-03 00:24:07 +00001591
wdenka8c7c702003-12-06 19:49:23 +00001592- DataFlash Support:
wdenk2abbe072003-06-16 23:50:08 +00001593 CONFIG_HAS_DATAFLASH
1594
wdenk8bde7f72003-06-27 21:31:46 +00001595 Defining this option enables DataFlash features and
1596 allows to read/write in Dataflash via the standard
1597 commands cp, md...
wdenk2abbe072003-06-16 23:50:08 +00001598
wdenk3f85ce22004-02-23 16:11:30 +00001599- SystemACE Support:
1600 CONFIG_SYSTEMACE
1601
1602 Adding this option adds support for Xilinx SystemACE
1603 chips attached via some sort of local bus. The address
1604 of the chip must alsh be defined in the
1605 CFG_SYSTEMACE_BASE macro. For example:
1606
1607 #define CONFIG_SYSTEMACE
1608 #define CFG_SYSTEMACE_BASE 0xf0000000
1609
1610 When SystemACE support is added, the "ace" device type
1611 becomes available to the fat commands, i.e. fatls.
1612
Wolfgang Denkecb0ccd2005-09-24 22:37:32 +02001613- TFTP Fixed UDP Port:
1614 CONFIG_TFTP_PORT
1615
Wolfgang Denk28cb9372005-09-24 23:25:46 +02001616 If this is defined, the environment variable tftpsrcp
Wolfgang Denkecb0ccd2005-09-24 22:37:32 +02001617 is used to supply the TFTP UDP source port value.
Wolfgang Denk28cb9372005-09-24 23:25:46 +02001618 If tftpsrcp isn't defined, the normal pseudo-random port
Wolfgang Denkecb0ccd2005-09-24 22:37:32 +02001619 number generator is used.
1620
Wolfgang Denk28cb9372005-09-24 23:25:46 +02001621 Also, the environment variable tftpdstp is used to supply
1622 the TFTP UDP destination port value. If tftpdstp isn't
1623 defined, the normal port 69 is used.
1624
1625 The purpose for tftpsrcp is to allow a TFTP server to
Wolfgang Denkecb0ccd2005-09-24 22:37:32 +02001626 blindly start the TFTP transfer using the pre-configured
1627 target IP address and UDP port. This has the effect of
1628 "punching through" the (Windows XP) firewall, allowing
1629 the remainder of the TFTP transfer to proceed normally.
1630 A better solution is to properly configure the firewall,
1631 but sometimes that is not allowed.
1632
wdenka8c7c702003-12-06 19:49:23 +00001633- Show boot progress:
wdenkc6097192002-11-03 00:24:07 +00001634 CONFIG_SHOW_BOOT_PROGRESS
1635
wdenk43d96162003-03-06 00:02:04 +00001636 Defining this option allows to add some board-
1637 specific code (calling a user-provided function
1638 "show_boot_progress(int)") that enables you to show
1639 the system's boot progress on some display (for
1640 example, some LED's) on your board. At the moment,
1641 the following checkpoints are implemented:
wdenkc6097192002-11-03 00:24:07 +00001642
1643 Arg Where When
1644 1 common/cmd_bootm.c before attempting to boot an image
wdenkba56f622004-02-06 23:19:44 +00001645 -1 common/cmd_bootm.c Image header has bad magic number
wdenkc6097192002-11-03 00:24:07 +00001646 2 common/cmd_bootm.c Image header has correct magic number
wdenkba56f622004-02-06 23:19:44 +00001647 -2 common/cmd_bootm.c Image header has bad checksum
wdenkc6097192002-11-03 00:24:07 +00001648 3 common/cmd_bootm.c Image header has correct checksum
wdenkba56f622004-02-06 23:19:44 +00001649 -3 common/cmd_bootm.c Image data has bad checksum
wdenkc6097192002-11-03 00:24:07 +00001650 4 common/cmd_bootm.c Image data has correct checksum
1651 -4 common/cmd_bootm.c Image is for unsupported architecture
1652 5 common/cmd_bootm.c Architecture check OK
1653 -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi, standalone)
1654 6 common/cmd_bootm.c Image Type check OK
1655 -6 common/cmd_bootm.c gunzip uncompression error
1656 -7 common/cmd_bootm.c Unimplemented compression type
1657 7 common/cmd_bootm.c Uncompression OK
1658 -8 common/cmd_bootm.c Wrong Image Type (not kernel, multi, standalone)
1659 8 common/cmd_bootm.c Image Type check OK
1660 -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
1661 9 common/cmd_bootm.c Start initial ramdisk verification
wdenkba56f622004-02-06 23:19:44 +00001662 -10 common/cmd_bootm.c Ramdisk header has bad magic number
1663 -11 common/cmd_bootm.c Ramdisk header has bad checksum
wdenkc6097192002-11-03 00:24:07 +00001664 10 common/cmd_bootm.c Ramdisk header is OK
wdenkba56f622004-02-06 23:19:44 +00001665 -12 common/cmd_bootm.c Ramdisk data has bad checksum
wdenkc6097192002-11-03 00:24:07 +00001666 11 common/cmd_bootm.c Ramdisk data has correct checksum
1667 12 common/cmd_bootm.c Ramdisk verification complete, start loading
1668 -13 common/cmd_bootm.c Wrong Image Type (not PPC Linux Ramdisk)
1669 13 common/cmd_bootm.c Start multifile image verification
1670 14 common/cmd_bootm.c No initial ramdisk, no multifile, continue.
1671 15 common/cmd_bootm.c All preparation done, transferring control to OS
1672
wdenk11dadd52004-02-27 00:07:27 +00001673 -30 lib_ppc/board.c Fatal error, hang the system
1674 -31 post/post.c POST test failed, detected by post_output_backlog()
1675 -32 post/post.c POST test failed, detected by post_run_single()
wdenk63e73c92004-02-23 22:22:28 +00001676
Heiko Schocher566a4942007-06-22 19:11:54 +02001677 34 common/cmd_doc.c before loading a Image from a DOC device
1678 -35 common/cmd_doc.c Bad usage of "doc" command
1679 35 common/cmd_doc.c correct usage of "doc" command
1680 -36 common/cmd_doc.c No boot device
1681 36 common/cmd_doc.c correct boot device
1682 -37 common/cmd_doc.c Unknown Chip ID on boot device
1683 37 common/cmd_doc.c correct chip ID found, device available
1684 -38 common/cmd_doc.c Read Error on boot device
1685 38 common/cmd_doc.c reading Image header from DOC device OK
1686 -39 common/cmd_doc.c Image header has bad magic number
1687 39 common/cmd_doc.c Image header has correct magic number
1688 -40 common/cmd_doc.c Error reading Image from DOC device
1689 40 common/cmd_doc.c Image header has correct magic number
1690 41 common/cmd_ide.c before loading a Image from a IDE device
1691 -42 common/cmd_ide.c Bad usage of "ide" command
1692 42 common/cmd_ide.c correct usage of "ide" command
1693 -43 common/cmd_ide.c No boot device
1694 43 common/cmd_ide.c boot device found
1695 -44 common/cmd_ide.c Device not available
1696 44 common/cmd_ide.c Device available
1697 -45 common/cmd_ide.c wrong partition selected
1698 45 common/cmd_ide.c partition selected
1699 -46 common/cmd_ide.c Unknown partition table
1700 46 common/cmd_ide.c valid partition table found
1701 -47 common/cmd_ide.c Invalid partition type
1702 47 common/cmd_ide.c correct partition type
1703 -48 common/cmd_ide.c Error reading Image Header on boot device
1704 48 common/cmd_ide.c reading Image Header from IDE device OK
1705 -49 common/cmd_ide.c Image header has bad magic number
1706 49 common/cmd_ide.c Image header has correct magic number
1707 -50 common/cmd_ide.c Image header has bad checksum
1708 50 common/cmd_ide.c Image header has correct checksum
1709 -51 common/cmd_ide.c Error reading Image from IDE device
1710 51 common/cmd_ide.c reading Image from IDE device OK
1711 52 common/cmd_nand.c before loading a Image from a NAND device
1712 -53 common/cmd_nand.c Bad usage of "nand" command
1713 53 common/cmd_nand.c correct usage of "nand" command
1714 -54 common/cmd_nand.c No boot device
1715 54 common/cmd_nand.c boot device found
1716 -55 common/cmd_nand.c Unknown Chip ID on boot device
1717 55 common/cmd_nand.c correct chip ID found, device available
1718 -56 common/cmd_nand.c Error reading Image Header on boot device
1719 56 common/cmd_nand.c reading Image Header from NAND device OK
1720 -57 common/cmd_nand.c Image header has bad magic number
1721 57 common/cmd_nand.c Image header has correct magic number
1722 -58 common/cmd_nand.c Error reading Image from NAND device
1723 58 common/cmd_nand.c reading Image from NAND device OK
wdenkc6097192002-11-03 00:24:07 +00001724
Heiko Schocher566a4942007-06-22 19:11:54 +02001725 -60 common/env_common.c Environment has a bad CRC, using default
wdenkc6097192002-11-03 00:24:07 +00001726
Heiko Schocher566a4942007-06-22 19:11:54 +02001727 64 net/eth.c starting with Ethernetconfiguration.
1728 -64 net/eth.c no Ethernet found.
1729 65 net/eth.c Ethernet found.
wdenk206c60c2003-09-18 10:02:25 +00001730
Heiko Schocher566a4942007-06-22 19:11:54 +02001731 -80 common/cmd_net.c usage wrong
1732 80 common/cmd_net.c before calling NetLoop()
1733 -81 common/cmd_net.c some error in NetLoop() occured
1734 81 common/cmd_net.c NetLoop() back without error
1735 -82 common/cmd_net.c size == 0 (File with size 0 loaded)
1736 82 common/cmd_net.c trying automatic boot
1737 83 common/cmd_net.c running autoscript
1738 -83 common/cmd_net.c some error in automatic boot or autoscript
1739 84 common/cmd_net.c end without errors
wdenkc6097192002-11-03 00:24:07 +00001740
1741Modem Support:
1742--------------
1743
wdenk85ec0bc2003-03-31 16:34:49 +00001744[so far only for SMDK2400 and TRAB boards]
wdenkc6097192002-11-03 00:24:07 +00001745
1746- Modem support endable:
1747 CONFIG_MODEM_SUPPORT
1748
1749- RTS/CTS Flow control enable:
1750 CONFIG_HWFLOW
1751
1752- Modem debug support:
1753 CONFIG_MODEM_SUPPORT_DEBUG
1754
wdenk43d96162003-03-06 00:02:04 +00001755 Enables debugging stuff (char screen[1024], dbg())
1756 for modem support. Useful only with BDI2000.
wdenkc6097192002-11-03 00:24:07 +00001757
wdenka8c7c702003-12-06 19:49:23 +00001758- Interrupt support (PPC):
1759
wdenkd4ca31c2004-01-02 14:00:00 +00001760 There are common interrupt_init() and timer_interrupt()
1761 for all PPC archs. interrupt_init() calls interrupt_init_cpu()
1762 for cpu specific initialization. interrupt_init_cpu()
1763 should set decrementer_count to appropriate value. If
1764 cpu resets decrementer automatically after interrupt
1765 (ppc4xx) it should set decrementer_count to zero.
1766 timer_interrupt() calls timer_interrupt_cpu() for cpu
1767 specific handling. If board has watchdog / status_led
1768 / other_activity_monitor it works automatically from
1769 general timer_interrupt().
wdenka8c7c702003-12-06 19:49:23 +00001770
wdenkc6097192002-11-03 00:24:07 +00001771- General:
1772
wdenk43d96162003-03-06 00:02:04 +00001773 In the target system modem support is enabled when a
1774 specific key (key combination) is pressed during
1775 power-on. Otherwise U-Boot will boot normally
1776 (autoboot). The key_pressed() fuction is called from
1777 board_init(). Currently key_pressed() is a dummy
1778 function, returning 1 and thus enabling modem
1779 initialization.
wdenkc6097192002-11-03 00:24:07 +00001780
wdenk43d96162003-03-06 00:02:04 +00001781 If there are no modem init strings in the
1782 environment, U-Boot proceed to autoboot; the
1783 previous output (banner, info printfs) will be
1784 supressed, though.
wdenkc6097192002-11-03 00:24:07 +00001785
1786 See also: doc/README.Modem
1787
1788
wdenkc6097192002-11-03 00:24:07 +00001789Configuration Settings:
1790-----------------------
1791
1792- CFG_LONGHELP: Defined when you want long help messages included;
1793 undefine this when you're short of memory.
1794
1795- CFG_PROMPT: This is what U-Boot prints on the console to
1796 prompt for user input.
1797
1798- CFG_CBSIZE: Buffer size for input from the Console
1799
1800- CFG_PBSIZE: Buffer size for Console output
1801
1802- CFG_MAXARGS: max. Number of arguments accepted for monitor commands
1803
1804- CFG_BARGSIZE: Buffer size for Boot Arguments which are passed to
1805 the application (usually a Linux kernel) when it is
1806 booted
1807
1808- CFG_BAUDRATE_TABLE:
1809 List of legal baudrate settings for this board.
1810
1811- CFG_CONSOLE_INFO_QUIET
wdenk8bde7f72003-06-27 21:31:46 +00001812 Suppress display of console information at boot.
wdenkc6097192002-11-03 00:24:07 +00001813
1814- CFG_CONSOLE_IS_IN_ENV
wdenk8bde7f72003-06-27 21:31:46 +00001815 If the board specific function
1816 extern int overwrite_console (void);
1817 returns 1, the stdin, stderr and stdout are switched to the
wdenkc6097192002-11-03 00:24:07 +00001818 serial port, else the settings in the environment are used.
1819
1820- CFG_CONSOLE_OVERWRITE_ROUTINE
wdenk8bde7f72003-06-27 21:31:46 +00001821 Enable the call to overwrite_console().
wdenkc6097192002-11-03 00:24:07 +00001822
1823- CFG_CONSOLE_ENV_OVERWRITE
1824 Enable overwrite of previous console environment settings.
1825
1826- CFG_MEMTEST_START, CFG_MEMTEST_END:
1827 Begin and End addresses of the area used by the
1828 simple memory test.
1829
1830- CFG_ALT_MEMTEST:
wdenk8bde7f72003-06-27 21:31:46 +00001831 Enable an alternate, more extensive memory test.
wdenkc6097192002-11-03 00:24:07 +00001832
wdenk5f535fe2003-09-18 09:21:33 +00001833- CFG_MEMTEST_SCRATCH:
1834 Scratch address used by the alternate memory test
1835 You only need to set this if address zero isn't writeable
1836
wdenkc6097192002-11-03 00:24:07 +00001837- CFG_TFTP_LOADADDR:
1838 Default load address for network file downloads
1839
1840- CFG_LOADS_BAUD_CHANGE:
1841 Enable temporary baudrate change while serial download
1842
1843- CFG_SDRAM_BASE:
1844 Physical start address of SDRAM. _Must_ be 0 here.
1845
1846- CFG_MBIO_BASE:
1847 Physical start address of Motherboard I/O (if using a
1848 Cogent motherboard)
1849
1850- CFG_FLASH_BASE:
1851 Physical start address of Flash memory.
1852
1853- CFG_MONITOR_BASE:
1854 Physical start address of boot monitor code (set by
1855 make config files to be same as the text base address
1856 (TEXT_BASE) used when linking) - same as
1857 CFG_FLASH_BASE when booting from flash.
1858
1859- CFG_MONITOR_LEN:
wdenk8bde7f72003-06-27 21:31:46 +00001860 Size of memory reserved for monitor code, used to
1861 determine _at_compile_time_ (!) if the environment is
1862 embedded within the U-Boot image, or in a separate
1863 flash sector.
wdenkc6097192002-11-03 00:24:07 +00001864
1865- CFG_MALLOC_LEN:
1866 Size of DRAM reserved for malloc() use.
1867
Stefan Roese15940c92006-03-13 11:16:36 +01001868- CFG_BOOTM_LEN:
1869 Normally compressed uImages are limited to an
1870 uncompressed size of 8 MBytes. If this is not enough,
1871 you can define CFG_BOOTM_LEN in your board config file
1872 to adjust this setting to your needs.
1873
wdenkc6097192002-11-03 00:24:07 +00001874- CFG_BOOTMAPSZ:
1875 Maximum size of memory mapped by the startup code of
1876 the Linux kernel; all data that must be processed by
1877 the Linux kernel (bd_info, boot arguments, eventually
1878 initrd image) must be put below this limit.
1879
1880- CFG_MAX_FLASH_BANKS:
1881 Max number of Flash memory banks
1882
1883- CFG_MAX_FLASH_SECT:
1884 Max number of sectors on a Flash chip
1885
1886- CFG_FLASH_ERASE_TOUT:
1887 Timeout for Flash erase operations (in ms)
1888
1889- CFG_FLASH_WRITE_TOUT:
1890 Timeout for Flash write operations (in ms)
1891
wdenk8564acf2003-07-14 22:13:32 +00001892- CFG_FLASH_LOCK_TOUT
1893 Timeout for Flash set sector lock bit operation (in ms)
1894
1895- CFG_FLASH_UNLOCK_TOUT
1896 Timeout for Flash clear lock bits operation (in ms)
1897
1898- CFG_FLASH_PROTECTION
1899 If defined, hardware flash sectors protection is used
1900 instead of U-Boot software protection.
1901
wdenkc6097192002-11-03 00:24:07 +00001902- CFG_DIRECT_FLASH_TFTP:
1903
1904 Enable TFTP transfers directly to flash memory;
1905 without this option such a download has to be
1906 performed in two steps: (1) download to RAM, and (2)
1907 copy from RAM to flash.
1908
1909 The two-step approach is usually more reliable, since
1910 you can check if the download worked before you erase
1911 the flash, but in some situations (when sytem RAM is
1912 too limited to allow for a tempory copy of the
1913 downloaded image) this option may be very useful.
1914
1915- CFG_FLASH_CFI:
wdenk43d96162003-03-06 00:02:04 +00001916 Define if the flash driver uses extra elements in the
wdenk5653fc32004-02-08 22:55:38 +00001917 common flash structure for storing flash geometry.
1918
1919- CFG_FLASH_CFI_DRIVER
1920 This option also enables the building of the cfi_flash driver
1921 in the drivers directory
wdenkc6097192002-11-03 00:24:07 +00001922
Stefan Roese5568e612005-11-22 13:20:42 +01001923- CFG_FLASH_QUIET_TEST
1924 If this option is defined, the common CFI flash doesn't
1925 print it's warning upon not recognized FLASH banks. This
1926 is useful, if some of the configured banks are only
1927 optionally available.
1928
stroese53cf9432003-06-05 15:39:44 +00001929- CFG_RX_ETH_BUFFER:
1930 Defines the number of ethernet receive buffers. On some
1931 ethernet controllers it is recommended to set this value
1932 to 8 or even higher (EEPRO100 or 405 EMAC), since all
1933 buffers can be full shortly after enabling the interface
1934 on high ethernet traffic.
1935 Defaults to 4 if not defined.
1936
wdenkc6097192002-11-03 00:24:07 +00001937The following definitions that deal with the placement and management
1938of environment data (variable area); in general, we support the
1939following configurations:
1940
1941- CFG_ENV_IS_IN_FLASH:
1942
1943 Define this if the environment is in flash memory.
1944
1945 a) The environment occupies one whole flash sector, which is
1946 "embedded" in the text segment with the U-Boot code. This
1947 happens usually with "bottom boot sector" or "top boot
1948 sector" type flash chips, which have several smaller
1949 sectors at the start or the end. For instance, such a
1950 layout can have sector sizes of 8, 2x4, 16, Nx32 kB. In
1951 such a case you would place the environment in one of the
1952 4 kB sectors - with U-Boot code before and after it. With
1953 "top boot sector" type flash chips, you would put the
1954 environment in one of the last sectors, leaving a gap
1955 between U-Boot and the environment.
1956
1957 - CFG_ENV_OFFSET:
1958
1959 Offset of environment data (variable area) to the
1960 beginning of flash memory; for instance, with bottom boot
1961 type flash chips the second sector can be used: the offset
1962 for this sector is given here.
1963
1964 CFG_ENV_OFFSET is used relative to CFG_FLASH_BASE.
1965
1966 - CFG_ENV_ADDR:
1967
1968 This is just another way to specify the start address of
1969 the flash sector containing the environment (instead of
1970 CFG_ENV_OFFSET).
1971
1972 - CFG_ENV_SECT_SIZE:
1973
1974 Size of the sector containing the environment.
1975
1976
1977 b) Sometimes flash chips have few, equal sized, BIG sectors.
1978 In such a case you don't want to spend a whole sector for
1979 the environment.
1980
1981 - CFG_ENV_SIZE:
1982
1983 If you use this in combination with CFG_ENV_IS_IN_FLASH
1984 and CFG_ENV_SECT_SIZE, you can specify to use only a part
1985 of this flash sector for the environment. This saves
1986 memory for the RAM copy of the environment.
1987
1988 It may also save flash memory if you decide to use this
1989 when your environment is "embedded" within U-Boot code,
1990 since then the remainder of the flash sector could be used
1991 for U-Boot code. It should be pointed out that this is
1992 STRONGLY DISCOURAGED from a robustness point of view:
1993 updating the environment in flash makes it always
1994 necessary to erase the WHOLE sector. If something goes
1995 wrong before the contents has been restored from a copy in
1996 RAM, your target system will be dead.
1997
1998 - CFG_ENV_ADDR_REDUND
1999 CFG_ENV_SIZE_REDUND
2000
wdenk43d96162003-03-06 00:02:04 +00002001 These settings describe a second storage area used to hold
2002 a redundand copy of the environment data, so that there is
wdenk3e386912003-04-05 00:53:31 +00002003 a valid backup copy in case there is a power failure during
wdenk43d96162003-03-06 00:02:04 +00002004 a "saveenv" operation.
wdenkc6097192002-11-03 00:24:07 +00002005
2006BE CAREFUL! Any changes to the flash layout, and some changes to the
2007source code will make it necessary to adapt <board>/u-boot.lds*
2008accordingly!
2009
2010
2011- CFG_ENV_IS_IN_NVRAM:
2012
2013 Define this if you have some non-volatile memory device
2014 (NVRAM, battery buffered SRAM) which you want to use for the
2015 environment.
2016
2017 - CFG_ENV_ADDR:
2018 - CFG_ENV_SIZE:
2019
2020 These two #defines are used to determin the memory area you
2021 want to use for environment. It is assumed that this memory
2022 can just be read and written to, without any special
2023 provision.
2024
2025BE CAREFUL! The first access to the environment happens quite early
2026in U-Boot initalization (when we try to get the setting of for the
2027console baudrate). You *MUST* have mappend your NVRAM area then, or
2028U-Boot will hang.
2029
2030Please note that even with NVRAM we still use a copy of the
2031environment in RAM: we could work on NVRAM directly, but we want to
2032keep settings there always unmodified except somebody uses "saveenv"
2033to save the current settings.
2034
2035
2036- CFG_ENV_IS_IN_EEPROM:
2037
2038 Use this if you have an EEPROM or similar serial access
2039 device and a driver for it.
2040
2041 - CFG_ENV_OFFSET:
2042 - CFG_ENV_SIZE:
2043
2044 These two #defines specify the offset and size of the
2045 environment area within the total memory of your EEPROM.
2046
2047 - CFG_I2C_EEPROM_ADDR:
2048 If defined, specified the chip address of the EEPROM device.
2049 The default address is zero.
2050
2051 - CFG_EEPROM_PAGE_WRITE_BITS:
2052 If defined, the number of bits used to address bytes in a
2053 single page in the EEPROM device. A 64 byte page, for example
2054 would require six bits.
2055
2056 - CFG_EEPROM_PAGE_WRITE_DELAY_MS:
2057 If defined, the number of milliseconds to delay between
wdenkba56f622004-02-06 23:19:44 +00002058 page writes. The default is zero milliseconds.
wdenkc6097192002-11-03 00:24:07 +00002059
2060 - CFG_I2C_EEPROM_ADDR_LEN:
2061 The length in bytes of the EEPROM memory array address. Note
2062 that this is NOT the chip address length!
2063
wdenk5cf91d62004-04-23 20:32:05 +00002064 - CFG_I2C_EEPROM_ADDR_OVERFLOW:
2065 EEPROM chips that implement "address overflow" are ones
2066 like Catalyst 24WC04/08/16 which has 9/10/11 bits of
2067 address and the extra bits end up in the "chip address" bit
2068 slots. This makes a 24WC08 (1Kbyte) chip look like four 256
2069 byte chips.
2070
2071 Note that we consider the length of the address field to
2072 still be one byte because the extra address bits are hidden
2073 in the chip address.
2074
wdenkc6097192002-11-03 00:24:07 +00002075 - CFG_EEPROM_SIZE:
2076 The size in bytes of the EEPROM device.
2077
wdenkc6097192002-11-03 00:24:07 +00002078
wdenk5779d8d2003-12-06 23:55:10 +00002079- CFG_ENV_IS_IN_DATAFLASH:
2080
wdenkd4ca31c2004-01-02 14:00:00 +00002081 Define this if you have a DataFlash memory device which you
wdenk5779d8d2003-12-06 23:55:10 +00002082 want to use for the environment.
2083
2084 - CFG_ENV_OFFSET:
2085 - CFG_ENV_ADDR:
2086 - CFG_ENV_SIZE:
2087
2088 These three #defines specify the offset and size of the
2089 environment area within the total memory of your DataFlash placed
2090 at the specified address.
2091
wdenk13a56952004-06-09 14:58:14 +00002092- CFG_ENV_IS_IN_NAND:
2093
2094 Define this if you have a NAND device which you want to use
2095 for the environment.
2096
2097 - CFG_ENV_OFFSET:
2098 - CFG_ENV_SIZE:
2099
2100 These two #defines specify the offset and size of the environment
2101 area within the first NAND device.
wdenk5779d8d2003-12-06 23:55:10 +00002102
Markus Klotzbuechere443c942006-03-20 18:02:44 +01002103 - CFG_ENV_OFFSET_REDUND
2104
2105 This setting describes a second storage area of CFG_ENV_SIZE
2106 size used to hold a redundant copy of the environment data,
2107 so that there is a valid backup copy in case there is a
2108 power failure during a "saveenv" operation.
2109
2110 Note: CFG_ENV_OFFSET and CFG_ENV_OFFSET_REDUND must be aligned
2111 to a block boundary, and CFG_ENV_SIZE must be a multiple of
2112 the NAND devices block size.
2113
wdenkc6097192002-11-03 00:24:07 +00002114- CFG_SPI_INIT_OFFSET
2115
2116 Defines offset to the initial SPI buffer area in DPRAM. The
2117 area is used at an early stage (ROM part) if the environment
2118 is configured to reside in the SPI EEPROM: We need a 520 byte
2119 scratch DPRAM area. It is used between the two initialization
2120 calls (spi_init_f() and spi_init_r()). A value of 0xB00 seems
2121 to be a good choice since it makes it far enough from the
2122 start of the data area as well as from the stack pointer.
2123
Bruce Adlere881cb52007-11-02 13:15:42 -07002124Please note that the environment is read-only until the monitor
wdenkc6097192002-11-03 00:24:07 +00002125has been relocated to RAM and a RAM copy of the environment has been
2126created; also, when using EEPROM you will have to use getenv_r()
2127until then to read environment variables.
2128
wdenk85ec0bc2003-03-31 16:34:49 +00002129The environment is protected by a CRC32 checksum. Before the monitor
2130is relocated into RAM, as a result of a bad CRC you will be working
2131with the compiled-in default environment - *silently*!!! [This is
2132necessary, because the first environment variable we need is the
2133"baudrate" setting for the console - if we have a bad CRC, we don't
2134have any device yet where we could complain.]
wdenkc6097192002-11-03 00:24:07 +00002135
2136Note: once the monitor has been relocated, then it will complain if
2137the default environment is used; a new CRC is computed as soon as you
wdenk85ec0bc2003-03-31 16:34:49 +00002138use the "saveenv" command to store a valid environment.
wdenkc6097192002-11-03 00:24:07 +00002139
wdenkfc3e2162003-10-08 22:33:00 +00002140- CFG_FAULT_ECHO_LINK_DOWN:
wdenk42d1f032003-10-15 23:53:47 +00002141 Echo the inverted Ethernet link state to the fault LED.
wdenkfc3e2162003-10-08 22:33:00 +00002142
2143 Note: If this option is active, then CFG_FAULT_MII_ADDR
2144 also needs to be defined.
2145
2146- CFG_FAULT_MII_ADDR:
wdenk42d1f032003-10-15 23:53:47 +00002147 MII address of the PHY to check for the Ethernet link state.
wdenkc6097192002-11-03 00:24:07 +00002148
wdenkc40b2952004-03-13 23:29:43 +00002149- CFG_64BIT_VSPRINTF:
2150 Makes vsprintf (and all *printf functions) support printing
2151 of 64bit values by using the L quantifier
2152
2153- CFG_64BIT_STRTOUL:
2154 Adds simple_strtoull that returns a 64bit value
2155
wdenkc6097192002-11-03 00:24:07 +00002156Low Level (hardware related) configuration options:
wdenkdc7c9a12003-03-26 06:55:25 +00002157---------------------------------------------------
wdenkc6097192002-11-03 00:24:07 +00002158
2159- CFG_CACHELINE_SIZE:
2160 Cache Line Size of the CPU.
2161
2162- CFG_DEFAULT_IMMR:
2163 Default address of the IMMR after system reset.
wdenk2535d602003-07-17 23:16:40 +00002164
wdenk42d1f032003-10-15 23:53:47 +00002165 Needed on some 8260 systems (MPC8260ADS, PQ2FADS-ZU,
2166 and RPXsuper) to be able to adjust the position of
2167 the IMMR register after a reset.
wdenkc6097192002-11-03 00:24:07 +00002168
wdenk7f6c2cb2002-11-10 22:06:23 +00002169- Floppy Disk Support:
2170 CFG_FDC_DRIVE_NUMBER
2171
2172 the default drive number (default value 0)
2173
2174 CFG_ISA_IO_STRIDE
2175
2176 defines the spacing between fdc chipset registers
2177 (default value 1)
2178
2179 CFG_ISA_IO_OFFSET
2180
wdenk43d96162003-03-06 00:02:04 +00002181 defines the offset of register from address. It
2182 depends on which part of the data bus is connected to
2183 the fdc chipset. (default value 0)
wdenk7f6c2cb2002-11-10 22:06:23 +00002184
wdenk43d96162003-03-06 00:02:04 +00002185 If CFG_ISA_IO_STRIDE CFG_ISA_IO_OFFSET and
2186 CFG_FDC_DRIVE_NUMBER are undefined, they take their
2187 default value.
wdenk7f6c2cb2002-11-10 22:06:23 +00002188
wdenk43d96162003-03-06 00:02:04 +00002189 if CFG_FDC_HW_INIT is defined, then the function
2190 fdc_hw_init() is called at the beginning of the FDC
2191 setup. fdc_hw_init() must be provided by the board
2192 source code. It is used to make hardware dependant
2193 initializations.
wdenk7f6c2cb2002-11-10 22:06:23 +00002194
wdenk25d67122004-12-10 11:40:40 +00002195- CFG_IMMR: Physical address of the Internal Memory.
wdenkefe2a4d2004-12-16 21:44:03 +00002196 DO NOT CHANGE unless you know exactly what you're
wdenk25d67122004-12-10 11:40:40 +00002197 doing! (11-4) [MPC8xx/82xx systems only]
wdenkc6097192002-11-03 00:24:07 +00002198
2199- CFG_INIT_RAM_ADDR:
2200
wdenk7152b1d2003-09-05 23:19:14 +00002201 Start address of memory area that can be used for
wdenkc6097192002-11-03 00:24:07 +00002202 initial data and stack; please note that this must be
2203 writable memory that is working WITHOUT special
2204 initialization, i. e. you CANNOT use normal RAM which
2205 will become available only after programming the
2206 memory controller and running certain initialization
2207 sequences.
2208
2209 U-Boot uses the following memory types:
2210 - MPC8xx and MPC8260: IMMR (internal memory of the CPU)
2211 - MPC824X: data cache
2212 - PPC4xx: data cache
2213
wdenk85ec0bc2003-03-31 16:34:49 +00002214- CFG_GBL_DATA_OFFSET:
wdenkc6097192002-11-03 00:24:07 +00002215
2216 Offset of the initial data structure in the memory
2217 area defined by CFG_INIT_RAM_ADDR. Usually
wdenk85ec0bc2003-03-31 16:34:49 +00002218 CFG_GBL_DATA_OFFSET is chosen such that the initial
wdenkc6097192002-11-03 00:24:07 +00002219 data is located at the end of the available space
2220 (sometimes written as (CFG_INIT_RAM_END -
2221 CFG_INIT_DATA_SIZE), and the initial stack is just
2222 below that area (growing from (CFG_INIT_RAM_ADDR +
wdenk85ec0bc2003-03-31 16:34:49 +00002223 CFG_GBL_DATA_OFFSET) downward.
wdenkc6097192002-11-03 00:24:07 +00002224
2225 Note:
2226 On the MPC824X (or other systems that use the data
2227 cache for initial memory) the address chosen for
2228 CFG_INIT_RAM_ADDR is basically arbitrary - it must
2229 point to an otherwise UNUSED address space between
2230 the top of RAM and the start of the PCI space.
2231
2232- CFG_SIUMCR: SIU Module Configuration (11-6)
2233
2234- CFG_SYPCR: System Protection Control (11-9)
2235
2236- CFG_TBSCR: Time Base Status and Control (11-26)
2237
2238- CFG_PISCR: Periodic Interrupt Status and Control (11-31)
2239
2240- CFG_PLPRCR: PLL, Low-Power, and Reset Control Register (15-30)
2241
2242- CFG_SCCR: System Clock and reset Control Register (15-27)
2243
2244- CFG_OR_TIMING_SDRAM:
2245 SDRAM timing
2246
2247- CFG_MAMR_PTA:
2248 periodic timer for refresh
2249
2250- CFG_DER: Debug Event Register (37-47)
2251
2252- FLASH_BASE0_PRELIM, FLASH_BASE1_PRELIM, CFG_REMAP_OR_AM,
2253 CFG_PRELIM_OR_AM, CFG_OR_TIMING_FLASH, CFG_OR0_REMAP,
2254 CFG_OR0_PRELIM, CFG_BR0_PRELIM, CFG_OR1_REMAP, CFG_OR1_PRELIM,
2255 CFG_BR1_PRELIM:
2256 Memory Controller Definitions: BR0/1 and OR0/1 (FLASH)
2257
2258- SDRAM_BASE2_PRELIM, SDRAM_BASE3_PRELIM, SDRAM_MAX_SIZE,
2259 CFG_OR_TIMING_SDRAM, CFG_OR2_PRELIM, CFG_BR2_PRELIM,
2260 CFG_OR3_PRELIM, CFG_BR3_PRELIM:
2261 Memory Controller Definitions: BR2/3 and OR2/3 (SDRAM)
2262
2263- CFG_MAMR_PTA, CFG_MPTPR_2BK_4K, CFG_MPTPR_1BK_4K, CFG_MPTPR_2BK_8K,
2264 CFG_MPTPR_1BK_8K, CFG_MAMR_8COL, CFG_MAMR_9COL:
2265 Machine Mode Register and Memory Periodic Timer
2266 Prescaler definitions (SDRAM timing)
2267
2268- CFG_I2C_UCODE_PATCH, CFG_I2C_DPMEM_OFFSET [0x1FC0]:
2269 enable I2C microcode relocation patch (MPC8xx);
2270 define relocation offset in DPRAM [DSP2]
2271
2272- CFG_SPI_UCODE_PATCH, CFG_SPI_DPMEM_OFFSET [0x1FC0]:
2273 enable SPI microcode relocation patch (MPC8xx);
2274 define relocation offset in DPRAM [SCC4]
2275
2276- CFG_USE_OSCCLK:
2277 Use OSCM clock mode on MBX8xx board. Be careful,
2278 wrong setting might damage your board. Read
2279 doc/README.MBX before setting this variable!
2280
wdenkea909b72002-11-21 23:11:29 +00002281- CFG_CPM_POST_WORD_ADDR: (MPC8xx, MPC8260 only)
wdenk43d96162003-03-06 00:02:04 +00002282 Offset of the bootmode word in DPRAM used by post
2283 (Power On Self Tests). This definition overrides
2284 #define'd default value in commproc.h resp.
2285 cpm_8260.h.
wdenkea909b72002-11-21 23:11:29 +00002286
stroese1d49b1f2003-05-23 11:39:05 +00002287- CFG_PCI_SLV_MEM_LOCAL, CFG_PCI_SLV_MEM_BUS, CFG_PICMR0_MASK_ATTRIB,
2288 CFG_PCI_MSTR0_LOCAL, CFG_PCIMSK0_MASK, CFG_PCI_MSTR1_LOCAL,
2289 CFG_PCIMSK1_MASK, CFG_PCI_MSTR_MEM_LOCAL, CFG_PCI_MSTR_MEM_BUS,
2290 CFG_CPU_PCI_MEM_START, CFG_PCI_MSTR_MEM_SIZE, CFG_POCMR0_MASK_ATTRIB,
2291 CFG_PCI_MSTR_MEMIO_LOCAL, CFG_PCI_MSTR_MEMIO_BUS, CPU_PCI_MEMIO_START,
2292 CFG_PCI_MSTR_MEMIO_SIZE, CFG_POCMR1_MASK_ATTRIB, CFG_PCI_MSTR_IO_LOCAL,
2293 CFG_PCI_MSTR_IO_BUS, CFG_CPU_PCI_IO_START, CFG_PCI_MSTR_IO_SIZE,
wdenk5d232d02003-05-22 22:52:13 +00002294 CFG_POCMR2_MASK_ATTRIB: (MPC826x only)
2295 Overrides the default PCI memory map in cpu/mpc8260/pci.c if set.
2296
Ben Warrenbb99ad62006-09-07 16:50:54 -04002297- CONFIG_SPD_EEPROM
2298 Get DDR timing information from an I2C EEPROM. Common with pluggable
2299 memory modules such as SODIMMs
2300 SPD_EEPROM_ADDRESS
2301 I2C address of the SPD EEPROM
2302
2303- CFG_SPD_BUS_NUM
2304 If SPD EEPROM is on an I2C bus other than the first one, specify here.
2305 Note that the value must resolve to something your driver can deal with.
2306
Timur Tabi2ad6b512006-10-31 18:44:42 -06002307- CFG_83XX_DDR_USES_CS0
2308 Only for 83xx systems. If specified, then DDR should be configured
2309 using CS0 and CS1 instead of CS2 and CS3.
2310
2311- CFG_83XX_DDR_USES_CS0
2312 Only for 83xx systems. If specified, then DDR should be configured
2313 using CS0 and CS1 instead of CS2 and CS3.
2314
wdenkc26e4542004-04-18 10:13:26 +00002315- CONFIG_ETHER_ON_FEC[12]
2316 Define to enable FEC[12] on a 8xx series processor.
2317
2318- CONFIG_FEC[12]_PHY
2319 Define to the hardcoded PHY address which corresponds
wdenk6e592382004-04-18 17:39:38 +00002320 to the given FEC; i. e.
2321 #define CONFIG_FEC1_PHY 4
wdenkc26e4542004-04-18 10:13:26 +00002322 means that the PHY with address 4 is connected to FEC1
2323
2324 When set to -1, means to probe for first available.
2325
2326- CONFIG_FEC[12]_PHY_NORXERR
2327 The PHY does not have a RXERR line (RMII only).
2328 (so program the FEC to ignore it).
2329
2330- CONFIG_RMII
2331 Enable RMII mode for all FECs.
2332 Note that this is a global option, we can't
2333 have one FEC in standard MII mode and another in RMII mode.
2334
wdenk5cf91d62004-04-23 20:32:05 +00002335- CONFIG_CRC32_VERIFY
2336 Add a verify option to the crc32 command.
2337 The syntax is:
2338
2339 => crc32 -v <address> <count> <crc32>
2340
2341 Where address/count indicate a memory area
2342 and crc32 is the correct crc32 which the
2343 area should have.
2344
wdenk56523f12004-07-11 17:40:54 +00002345- CONFIG_LOOPW
2346 Add the "loopw" memory command. This only takes effect if
Jon Loeliger602ad3b2007-06-11 19:03:39 -05002347 the memory commands are activated globally (CONFIG_CMD_MEM).
wdenk56523f12004-07-11 17:40:54 +00002348
stroese7b466642004-12-16 18:46:55 +00002349- CONFIG_MX_CYCLIC
2350 Add the "mdc" and "mwc" memory commands. These are cyclic
2351 "md/mw" commands.
2352 Examples:
2353
wdenkefe2a4d2004-12-16 21:44:03 +00002354 => mdc.b 10 4 500
stroese7b466642004-12-16 18:46:55 +00002355 This command will print 4 bytes (10,11,12,13) each 500 ms.
2356
wdenkefe2a4d2004-12-16 21:44:03 +00002357 => mwc.l 100 12345678 10
stroese7b466642004-12-16 18:46:55 +00002358 This command will write 12345678 to address 100 all 10 ms.
2359
wdenkefe2a4d2004-12-16 21:44:03 +00002360 This only takes effect if the memory commands are activated
Jon Loeliger602ad3b2007-06-11 19:03:39 -05002361 globally (CONFIG_CMD_MEM).
stroese7b466642004-12-16 18:46:55 +00002362
wdenk8aa1a2d2005-04-04 12:44:11 +00002363- CONFIG_SKIP_LOWLEVEL_INIT
2364- CONFIG_SKIP_RELOCATE_UBOOT
2365
wdenk3c2b3d42005-04-05 23:32:21 +00002366 [ARM only] If these variables are defined, then
2367 certain low level initializations (like setting up
2368 the memory controller) are omitted and/or U-Boot does
2369 not relocate itself into RAM.
2370 Normally these variables MUST NOT be defined. The
2371 only exception is when U-Boot is loaded (to RAM) by
2372 some other boot loader or by a debugger which
2373 performs these intializations itself.
wdenk8aa1a2d2005-04-04 12:44:11 +00002374
wdenk400558b2005-04-02 23:52:25 +00002375
wdenkc6097192002-11-03 00:24:07 +00002376Building the Software:
2377======================
2378
2379Building U-Boot has been tested in native PPC environments (on a
2380PowerBook G3 running LinuxPPC 2000) and in cross environments
2381(running RedHat 6.x and 7.x Linux on x86, Solaris 2.6 on a SPARC, and
2382NetBSD 1.5 on x86).
2383
2384If you are not using a native PPC environment, it is assumed that you
2385have the GNU cross compiling tools available in your path and named
2386with a prefix of "powerpc-linux-". If this is not the case, (e.g. if
2387you are using Monta Vista's Hard Hat Linux CDK 1.2) you must change
2388the definition of CROSS_COMPILE in Makefile. For HHL on a 4xx CPU,
2389change it to:
2390
2391 CROSS_COMPILE = ppc_4xx-
2392
2393
wdenkba56f622004-02-06 23:19:44 +00002394U-Boot is intended to be simple to build. After installing the
wdenkc6097192002-11-03 00:24:07 +00002395sources you must configure U-Boot for one specific board type. This
2396is done by typing:
2397
2398 make NAME_config
2399
2400where "NAME_config" is the name of one of the existing
Kim Phillips26281142007-08-10 13:28:25 -05002401configurations; see the main Makefile for supported names.
wdenk54387ac2003-10-08 22:45:44 +00002402
wdenk2729af92004-05-03 20:45:30 +00002403Note: for some board special configuration names may exist; check if
2404 additional information is available from the board vendor; for
2405 instance, the TQM823L systems are available without (standard)
2406 or with LCD support. You can select such additional "features"
2407 when chosing the configuration, i. e.
wdenkc6097192002-11-03 00:24:07 +00002408
wdenk2729af92004-05-03 20:45:30 +00002409 make TQM823L_config
2410 - will configure for a plain TQM823L, i. e. no LCD support
wdenkc6097192002-11-03 00:24:07 +00002411
wdenk2729af92004-05-03 20:45:30 +00002412 make TQM823L_LCD_config
2413 - will configure for a TQM823L with U-Boot console on LCD
wdenkc6097192002-11-03 00:24:07 +00002414
wdenk2729af92004-05-03 20:45:30 +00002415 etc.
wdenkc6097192002-11-03 00:24:07 +00002416
wdenkc6097192002-11-03 00:24:07 +00002417
wdenk2729af92004-05-03 20:45:30 +00002418Finally, type "make all", and you should get some working U-Boot
2419images ready for download to / installation on your system:
wdenkc6097192002-11-03 00:24:07 +00002420
wdenk2729af92004-05-03 20:45:30 +00002421- "u-boot.bin" is a raw binary image
2422- "u-boot" is an image in ELF binary format
2423- "u-boot.srec" is in Motorola S-Record format
wdenkc6097192002-11-03 00:24:07 +00002424
Marian Balakowiczbaf31242006-09-07 17:25:40 +02002425By default the build is performed locally and the objects are saved
2426in the source directory. One of the two methods can be used to change
2427this behavior and build U-Boot to some external directory:
2428
24291. Add O= to the make command line invocations:
2430
2431 make O=/tmp/build distclean
2432 make O=/tmp/build NAME_config
2433 make O=/tmp/build all
2434
24352. Set environment variable BUILD_DIR to point to the desired location:
2436
2437 export BUILD_DIR=/tmp/build
2438 make distclean
2439 make NAME_config
2440 make all
2441
2442Note that the command line "O=" setting overrides the BUILD_DIR environment
2443variable.
2444
wdenkc6097192002-11-03 00:24:07 +00002445
wdenk2729af92004-05-03 20:45:30 +00002446Please be aware that the Makefiles assume you are using GNU make, so
2447for instance on NetBSD you might need to use "gmake" instead of
2448native "make".
wdenkc6097192002-11-03 00:24:07 +00002449
wdenkc6097192002-11-03 00:24:07 +00002450
wdenk2729af92004-05-03 20:45:30 +00002451If the system board that you have is not listed, then you will need
2452to port U-Boot to your hardware platform. To do this, follow these
2453steps:
wdenkc6097192002-11-03 00:24:07 +00002454
wdenk2729af92004-05-03 20:45:30 +000024551. Add a new configuration option for your board to the toplevel
2456 "Makefile" and to the "MAKEALL" script, using the existing
2457 entries as examples. Note that here and at many other places
2458 boards and other names are listed in alphabetical sort order. Please
2459 keep this order.
24602. Create a new directory to hold your board specific code. Add any
2461 files you need. In your board directory, you will need at least
2462 the "Makefile", a "<board>.c", "flash.c" and "u-boot.lds".
24633. Create a new configuration file "include/configs/<board>.h" for
2464 your board
24653. If you're porting U-Boot to a new CPU, then also create a new
2466 directory to hold your CPU specific code. Add any files you need.
24674. Run "make <board>_config" with your new name.
24685. Type "make", and you should get a working "u-boot.srec" file
2469 to be installed on your target system.
24706. Debug and solve any problems that might arise.
2471 [Of course, this last step is much harder than it sounds.]
wdenkc6097192002-11-03 00:24:07 +00002472
wdenkc6097192002-11-03 00:24:07 +00002473
wdenk2729af92004-05-03 20:45:30 +00002474Testing of U-Boot Modifications, Ports to New Hardware, etc.:
2475==============================================================
wdenkc6097192002-11-03 00:24:07 +00002476
wdenk2729af92004-05-03 20:45:30 +00002477If you have modified U-Boot sources (for instance added a new board
2478or support for new devices, a new CPU, etc.) you are expected to
2479provide feedback to the other developers. The feedback normally takes
2480the form of a "patch", i. e. a context diff against a certain (latest
2481official or latest in CVS) version of U-Boot sources.
wdenkc6097192002-11-03 00:24:07 +00002482
wdenk2729af92004-05-03 20:45:30 +00002483But before you submit such a patch, please verify that your modifi-
2484cation did not break existing code. At least make sure that *ALL* of
2485the supported boards compile WITHOUT ANY compiler warnings. To do so,
2486just run the "MAKEALL" script, which will configure and build U-Boot
2487for ALL supported system. Be warned, this will take a while. You can
2488select which (cross) compiler to use by passing a `CROSS_COMPILE'
2489environment variable to the script, i. e. to use the cross tools from
2490MontaVista's Hard Hat Linux you can type
wdenkc6097192002-11-03 00:24:07 +00002491
wdenk2729af92004-05-03 20:45:30 +00002492 CROSS_COMPILE=ppc_8xx- MAKEALL
wdenkc6097192002-11-03 00:24:07 +00002493
wdenk2729af92004-05-03 20:45:30 +00002494or to build on a native PowerPC system you can type
wdenkc6097192002-11-03 00:24:07 +00002495
wdenk2729af92004-05-03 20:45:30 +00002496 CROSS_COMPILE=' ' MAKEALL
wdenkc6097192002-11-03 00:24:07 +00002497
Marian Balakowiczbaf31242006-09-07 17:25:40 +02002498When using the MAKEALL script, the default behaviour is to build U-Boot
2499in the source directory. This location can be changed by setting the
2500BUILD_DIR environment variable. Also, for each target built, the MAKEALL
2501script saves two log files (<target>.ERR and <target>.MAKEALL) in the
2502<source dir>/LOG directory. This default location can be changed by
2503setting the MAKEALL_LOGDIR environment variable. For example:
2504
2505 export BUILD_DIR=/tmp/build
2506 export MAKEALL_LOGDIR=/tmp/log
2507 CROSS_COMPILE=ppc_8xx- MAKEALL
2508
2509With the above settings build objects are saved in the /tmp/build, log
2510files are saved in the /tmp/log and the source tree remains clean during
2511the whole build process.
2512
2513
wdenk2729af92004-05-03 20:45:30 +00002514See also "U-Boot Porting Guide" below.
wdenkc6097192002-11-03 00:24:07 +00002515
wdenkc6097192002-11-03 00:24:07 +00002516
wdenk2729af92004-05-03 20:45:30 +00002517Monitor Commands - Overview:
2518============================
wdenkc6097192002-11-03 00:24:07 +00002519
wdenk2729af92004-05-03 20:45:30 +00002520go - start application at address 'addr'
2521run - run commands in an environment variable
2522bootm - boot application image from memory
2523bootp - boot image via network using BootP/TFTP protocol
2524tftpboot- boot image via network using TFTP protocol
2525 and env variables "ipaddr" and "serverip"
2526 (and eventually "gatewayip")
2527rarpboot- boot image via network using RARP/TFTP protocol
2528diskboot- boot from IDE devicebootd - boot default, i.e., run 'bootcmd'
2529loads - load S-Record file over serial line
2530loadb - load binary file over serial line (kermit mode)
2531md - memory display
2532mm - memory modify (auto-incrementing)
2533nm - memory modify (constant address)
2534mw - memory write (fill)
2535cp - memory copy
2536cmp - memory compare
2537crc32 - checksum calculation
2538imd - i2c memory display
2539imm - i2c memory modify (auto-incrementing)
2540inm - i2c memory modify (constant address)
2541imw - i2c memory write (fill)
2542icrc32 - i2c checksum calculation
2543iprobe - probe to discover valid I2C chip addresses
2544iloop - infinite loop on address range
2545isdram - print SDRAM configuration information
2546sspi - SPI utility commands
2547base - print or set address offset
2548printenv- print environment variables
2549setenv - set environment variables
2550saveenv - save environment variables to persistent storage
2551protect - enable or disable FLASH write protection
2552erase - erase FLASH memory
2553flinfo - print FLASH memory information
2554bdinfo - print Board Info structure
2555iminfo - print header information for application image
2556coninfo - print console devices and informations
2557ide - IDE sub-system
2558loop - infinite loop on address range
wdenk56523f12004-07-11 17:40:54 +00002559loopw - infinite write loop on address range
wdenk2729af92004-05-03 20:45:30 +00002560mtest - simple RAM test
2561icache - enable or disable instruction cache
2562dcache - enable or disable data cache
2563reset - Perform RESET of the CPU
2564echo - echo args to console
2565version - print monitor version
2566help - print online help
2567? - alias for 'help'
wdenkc6097192002-11-03 00:24:07 +00002568
wdenkc6097192002-11-03 00:24:07 +00002569
wdenk2729af92004-05-03 20:45:30 +00002570Monitor Commands - Detailed Description:
2571========================================
wdenkc6097192002-11-03 00:24:07 +00002572
wdenk2729af92004-05-03 20:45:30 +00002573TODO.
wdenkc6097192002-11-03 00:24:07 +00002574
wdenk2729af92004-05-03 20:45:30 +00002575For now: just type "help <command>".
wdenkc6097192002-11-03 00:24:07 +00002576
2577
wdenk2729af92004-05-03 20:45:30 +00002578Environment Variables:
2579======================
wdenkc6097192002-11-03 00:24:07 +00002580
wdenk2729af92004-05-03 20:45:30 +00002581U-Boot supports user configuration using Environment Variables which
2582can be made persistent by saving to Flash memory.
wdenkc6097192002-11-03 00:24:07 +00002583
wdenk2729af92004-05-03 20:45:30 +00002584Environment Variables are set using "setenv", printed using
2585"printenv", and saved to Flash using "saveenv". Using "setenv"
2586without a value can be used to delete a variable from the
2587environment. As long as you don't save the environment you are
2588working with an in-memory copy. In case the Flash area containing the
2589environment is erased by accident, a default environment is provided.
wdenkc6097192002-11-03 00:24:07 +00002590
wdenk2729af92004-05-03 20:45:30 +00002591Some configuration options can be set using Environment Variables:
wdenkc6097192002-11-03 00:24:07 +00002592
wdenk2729af92004-05-03 20:45:30 +00002593 baudrate - see CONFIG_BAUDRATE
wdenkc6097192002-11-03 00:24:07 +00002594
wdenk2729af92004-05-03 20:45:30 +00002595 bootdelay - see CONFIG_BOOTDELAY
wdenkc6097192002-11-03 00:24:07 +00002596
wdenk2729af92004-05-03 20:45:30 +00002597 bootcmd - see CONFIG_BOOTCOMMAND
wdenkc6097192002-11-03 00:24:07 +00002598
wdenk2729af92004-05-03 20:45:30 +00002599 bootargs - Boot arguments when booting an RTOS image
wdenkc6097192002-11-03 00:24:07 +00002600
wdenk2729af92004-05-03 20:45:30 +00002601 bootfile - Name of the image to load with TFTP
wdenkc6097192002-11-03 00:24:07 +00002602
wdenk2729af92004-05-03 20:45:30 +00002603 autoload - if set to "no" (any string beginning with 'n'),
2604 "bootp" will just load perform a lookup of the
2605 configuration from the BOOTP server, but not try to
2606 load any image using TFTP
wdenkc6097192002-11-03 00:24:07 +00002607
wdenk2729af92004-05-03 20:45:30 +00002608 autostart - if set to "yes", an image loaded using the "bootp",
2609 "rarpboot", "tftpboot" or "diskboot" commands will
2610 be automatically started (by internally calling
2611 "bootm")
wdenkc6097192002-11-03 00:24:07 +00002612
wdenk2729af92004-05-03 20:45:30 +00002613 If set to "no", a standalone image passed to the
2614 "bootm" command will be copied to the load address
2615 (and eventually uncompressed), but NOT be started.
2616 This can be used to load and uncompress arbitrary
2617 data.
wdenkc6097192002-11-03 00:24:07 +00002618
wdenk17ea1172004-06-06 21:51:03 +00002619 i2cfast - (PPC405GP|PPC405EP only)
2620 if set to 'y' configures Linux I2C driver for fast
2621 mode (400kHZ). This environment variable is used in
2622 initialization code. So, for changes to be effective
2623 it must be saved and board must be reset.
2624
wdenk2729af92004-05-03 20:45:30 +00002625 initrd_high - restrict positioning of initrd images:
2626 If this variable is not set, initrd images will be
2627 copied to the highest possible address in RAM; this
2628 is usually what you want since it allows for
2629 maximum initrd size. If for some reason you want to
2630 make sure that the initrd image is loaded below the
2631 CFG_BOOTMAPSZ limit, you can set this environment
2632 variable to a value of "no" or "off" or "0".
2633 Alternatively, you can set it to a maximum upper
2634 address to use (U-Boot will still check that it
2635 does not overwrite the U-Boot stack and data).
wdenkc6097192002-11-03 00:24:07 +00002636
wdenk2729af92004-05-03 20:45:30 +00002637 For instance, when you have a system with 16 MB
2638 RAM, and want to reserve 4 MB from use by Linux,
2639 you can do this by adding "mem=12M" to the value of
2640 the "bootargs" variable. However, now you must make
2641 sure that the initrd image is placed in the first
2642 12 MB as well - this can be done with
wdenkc6097192002-11-03 00:24:07 +00002643
wdenk2729af92004-05-03 20:45:30 +00002644 setenv initrd_high 00c00000
wdenkc6097192002-11-03 00:24:07 +00002645
wdenk2729af92004-05-03 20:45:30 +00002646 If you set initrd_high to 0xFFFFFFFF, this is an
2647 indication to U-Boot that all addresses are legal
2648 for the Linux kernel, including addresses in flash
2649 memory. In this case U-Boot will NOT COPY the
2650 ramdisk at all. This may be useful to reduce the
2651 boot time on your system, but requires that this
2652 feature is supported by your Linux kernel.
wdenk4a6fd342003-04-12 23:38:12 +00002653
wdenk2729af92004-05-03 20:45:30 +00002654 ipaddr - IP address; needed for tftpboot command
wdenkc6097192002-11-03 00:24:07 +00002655
wdenk2729af92004-05-03 20:45:30 +00002656 loadaddr - Default load address for commands like "bootp",
2657 "rarpboot", "tftpboot", "loadb" or "diskboot"
wdenkc6097192002-11-03 00:24:07 +00002658
wdenk2729af92004-05-03 20:45:30 +00002659 loads_echo - see CONFIG_LOADS_ECHO
wdenkc6097192002-11-03 00:24:07 +00002660
wdenk2729af92004-05-03 20:45:30 +00002661 serverip - TFTP server IP address; needed for tftpboot command
wdenk38b99262003-05-23 23:18:21 +00002662
wdenk2729af92004-05-03 20:45:30 +00002663 bootretry - see CONFIG_BOOT_RETRY_TIME
wdenkc6097192002-11-03 00:24:07 +00002664
wdenk2729af92004-05-03 20:45:30 +00002665 bootdelaykey - see CONFIG_AUTOBOOT_DELAY_STR
wdenkc6097192002-11-03 00:24:07 +00002666
wdenk2729af92004-05-03 20:45:30 +00002667 bootstopkey - see CONFIG_AUTOBOOT_STOP_STR
wdenkc6097192002-11-03 00:24:07 +00002668
wdenk2729af92004-05-03 20:45:30 +00002669 ethprime - When CONFIG_NET_MULTI is enabled controls which
2670 interface is used first.
wdenkc6097192002-11-03 00:24:07 +00002671
wdenk2729af92004-05-03 20:45:30 +00002672 ethact - When CONFIG_NET_MULTI is enabled controls which
2673 interface is currently active. For example you
2674 can do the following
wdenkc6097192002-11-03 00:24:07 +00002675
wdenk2729af92004-05-03 20:45:30 +00002676 => setenv ethact FEC ETHERNET
2677 => ping 192.168.0.1 # traffic sent on FEC ETHERNET
2678 => setenv ethact SCC ETHERNET
2679 => ping 10.0.0.1 # traffic sent on SCC ETHERNET
wdenkc6097192002-11-03 00:24:07 +00002680
wdenk2729af92004-05-03 20:45:30 +00002681 netretry - When set to "no" each network operation will
2682 either succeed or fail without retrying.
2683 When set to "once" the network operation will
2684 fail when all the available network interfaces
2685 are tried once without success.
2686 Useful on scripts which control the retry operation
2687 themselves.
wdenkc6097192002-11-03 00:24:07 +00002688
Wolfgang Denk28cb9372005-09-24 23:25:46 +02002689 tftpsrcport - If this is set, the value is used for TFTP's
Wolfgang Denkecb0ccd2005-09-24 22:37:32 +02002690 UDP source port.
2691
Wolfgang Denk28cb9372005-09-24 23:25:46 +02002692 tftpdstport - If this is set, the value is used for TFTP's UDP
2693 destination port instead of the Well Know Port 69.
2694
wdenk2729af92004-05-03 20:45:30 +00002695 vlan - When set to a value < 4095 the traffic over
2696 ethernet is encapsulated/received over 802.1q
2697 VLAN tagged frames.
wdenka3d991b2004-04-15 21:48:45 +00002698
wdenk2729af92004-05-03 20:45:30 +00002699The following environment variables may be used and automatically
2700updated by the network boot commands ("bootp" and "rarpboot"),
2701depending the information provided by your boot server:
wdenka3d991b2004-04-15 21:48:45 +00002702
wdenk2729af92004-05-03 20:45:30 +00002703 bootfile - see above
2704 dnsip - IP address of your Domain Name Server
2705 dnsip2 - IP address of your secondary Domain Name Server
2706 gatewayip - IP address of the Gateway (Router) to use
2707 hostname - Target hostname
2708 ipaddr - see above
2709 netmask - Subnet Mask
2710 rootpath - Pathname of the root filesystem on the NFS server
2711 serverip - see above
wdenka3d991b2004-04-15 21:48:45 +00002712
wdenka3d991b2004-04-15 21:48:45 +00002713
wdenk2729af92004-05-03 20:45:30 +00002714There are two special Environment Variables:
wdenkc6097192002-11-03 00:24:07 +00002715
wdenk2729af92004-05-03 20:45:30 +00002716 serial# - contains hardware identification information such
2717 as type string and/or serial number
2718 ethaddr - Ethernet address
wdenkc6097192002-11-03 00:24:07 +00002719
wdenk2729af92004-05-03 20:45:30 +00002720These variables can be set only once (usually during manufacturing of
2721the board). U-Boot refuses to delete or overwrite these variables
2722once they have been set once.
wdenkc6097192002-11-03 00:24:07 +00002723
2724
wdenk2729af92004-05-03 20:45:30 +00002725Further special Environment Variables:
wdenkc6097192002-11-03 00:24:07 +00002726
wdenk2729af92004-05-03 20:45:30 +00002727 ver - Contains the U-Boot version string as printed
2728 with the "version" command. This variable is
2729 readonly (see CONFIG_VERSION_VARIABLE).
wdenkc6097192002-11-03 00:24:07 +00002730
wdenkc6097192002-11-03 00:24:07 +00002731
wdenk2729af92004-05-03 20:45:30 +00002732Please note that changes to some configuration parameters may take
2733only effect after the next boot (yes, that's just like Windoze :-).
wdenkc6097192002-11-03 00:24:07 +00002734
stroesec1551ea2003-04-04 15:53:41 +00002735
wdenk2729af92004-05-03 20:45:30 +00002736Command Line Parsing:
2737=====================
stroesec1551ea2003-04-04 15:53:41 +00002738
wdenk2729af92004-05-03 20:45:30 +00002739There are two different command line parsers available with U-Boot:
2740the old "simple" one, and the much more powerful "hush" shell:
stroesec1551ea2003-04-04 15:53:41 +00002741
wdenk2729af92004-05-03 20:45:30 +00002742Old, simple command line parser:
2743--------------------------------
wdenkc6097192002-11-03 00:24:07 +00002744
wdenk2729af92004-05-03 20:45:30 +00002745- supports environment variables (through setenv / saveenv commands)
2746- several commands on one line, separated by ';'
Wolfgang Denkfe126d82005-11-20 21:40:11 +01002747- variable substitution using "... ${name} ..." syntax
wdenk2729af92004-05-03 20:45:30 +00002748- special characters ('$', ';') can be escaped by prefixing with '\',
2749 for example:
Wolfgang Denkfe126d82005-11-20 21:40:11 +01002750 setenv bootcmd bootm \${address}
wdenk2729af92004-05-03 20:45:30 +00002751- You can also escape text by enclosing in single apostrophes, for example:
2752 setenv addip 'setenv bootargs $bootargs ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname::off'
wdenkc6097192002-11-03 00:24:07 +00002753
wdenk2729af92004-05-03 20:45:30 +00002754Hush shell:
2755-----------
wdenkf07771c2003-05-28 08:06:31 +00002756
wdenk2729af92004-05-03 20:45:30 +00002757- similar to Bourne shell, with control structures like
2758 if...then...else...fi, for...do...done; while...do...done,
2759 until...do...done, ...
2760- supports environment ("global") variables (through setenv / saveenv
2761 commands) and local shell variables (through standard shell syntax
2762 "name=value"); only environment variables can be used with "run"
2763 command
wdenkf07771c2003-05-28 08:06:31 +00002764
wdenk2729af92004-05-03 20:45:30 +00002765General rules:
2766--------------
wdenkf07771c2003-05-28 08:06:31 +00002767
wdenk2729af92004-05-03 20:45:30 +00002768(1) If a command line (or an environment variable executed by a "run"
2769 command) contains several commands separated by semicolon, and
2770 one of these commands fails, then the remaining commands will be
2771 executed anyway.
wdenkf07771c2003-05-28 08:06:31 +00002772
wdenk2729af92004-05-03 20:45:30 +00002773(2) If you execute several variables with one call to run (i. e.
2774 calling run with a list af variables as arguments), any failing
2775 command will cause "run" to terminate, i. e. the remaining
2776 variables are not executed.
wdenkf07771c2003-05-28 08:06:31 +00002777
wdenk2729af92004-05-03 20:45:30 +00002778Note for Redundant Ethernet Interfaces:
2779=======================================
wdenkf07771c2003-05-28 08:06:31 +00002780
wdenk2729af92004-05-03 20:45:30 +00002781Some boards come with redundant ethernet interfaces; U-Boot supports
2782such configurations and is capable of automatic selection of a
2783"working" interface when needed. MAC assignment works as follows:
wdenkf07771c2003-05-28 08:06:31 +00002784
wdenk2729af92004-05-03 20:45:30 +00002785Network interfaces are numbered eth0, eth1, eth2, ... Corresponding
2786MAC addresses can be stored in the environment as "ethaddr" (=>eth0),
2787"eth1addr" (=>eth1), "eth2addr", ...
wdenkf07771c2003-05-28 08:06:31 +00002788
wdenk2729af92004-05-03 20:45:30 +00002789If the network interface stores some valid MAC address (for instance
2790in SROM), this is used as default address if there is NO correspon-
2791ding setting in the environment; if the corresponding environment
2792variable is set, this overrides the settings in the card; that means:
wdenkf07771c2003-05-28 08:06:31 +00002793
wdenk2729af92004-05-03 20:45:30 +00002794o If the SROM has a valid MAC address, and there is no address in the
2795 environment, the SROM's address is used.
wdenkc6097192002-11-03 00:24:07 +00002796
wdenk2729af92004-05-03 20:45:30 +00002797o If there is no valid address in the SROM, and a definition in the
2798 environment exists, then the value from the environment variable is
2799 used.
wdenkc6097192002-11-03 00:24:07 +00002800
wdenk2729af92004-05-03 20:45:30 +00002801o If both the SROM and the environment contain a MAC address, and
2802 both addresses are the same, this MAC address is used.
wdenkc6097192002-11-03 00:24:07 +00002803
wdenk2729af92004-05-03 20:45:30 +00002804o If both the SROM and the environment contain a MAC address, and the
2805 addresses differ, the value from the environment is used and a
2806 warning is printed.
wdenkc6097192002-11-03 00:24:07 +00002807
wdenk2729af92004-05-03 20:45:30 +00002808o If neither SROM nor the environment contain a MAC address, an error
2809 is raised.
wdenkc6097192002-11-03 00:24:07 +00002810
wdenkc6097192002-11-03 00:24:07 +00002811
wdenk2729af92004-05-03 20:45:30 +00002812Image Formats:
2813==============
wdenkc6097192002-11-03 00:24:07 +00002814
wdenk2729af92004-05-03 20:45:30 +00002815The "boot" commands of this monitor operate on "image" files which
2816can be basicly anything, preceeded by a special header; see the
2817definitions in include/image.h for details; basicly, the header
2818defines the following image properties:
wdenkc6097192002-11-03 00:24:07 +00002819
wdenk2729af92004-05-03 20:45:30 +00002820* Target Operating System (Provisions for OpenBSD, NetBSD, FreeBSD,
2821 4.4BSD, Linux, SVR4, Esix, Solaris, Irix, SCO, Dell, NCR, VxWorks,
2822 LynxOS, pSOS, QNX, RTEMS, ARTOS;
2823 Currently supported: Linux, NetBSD, VxWorks, QNX, RTEMS, ARTOS, LynxOS).
Wolfgang Denk7b64fef2006-10-24 14:21:16 +02002824* Target CPU Architecture (Provisions for Alpha, ARM, AVR32, Intel x86,
wdenk2729af92004-05-03 20:45:30 +00002825 IA64, MIPS, NIOS, PowerPC, IBM S390, SuperH, Sparc, Sparc 64 Bit;
Wolfgang Denk7b64fef2006-10-24 14:21:16 +02002826 Currently supported: ARM, AVR32, Intel x86, MIPS, NIOS, PowerPC).
wdenk2729af92004-05-03 20:45:30 +00002827* Compression Type (uncompressed, gzip, bzip2)
2828* Load Address
2829* Entry Point
2830* Image Name
2831* Image Timestamp
wdenkc6097192002-11-03 00:24:07 +00002832
wdenk2729af92004-05-03 20:45:30 +00002833The header is marked by a special Magic Number, and both the header
2834and the data portions of the image are secured against corruption by
2835CRC32 checksums.
wdenkc6097192002-11-03 00:24:07 +00002836
wdenkc6097192002-11-03 00:24:07 +00002837
wdenk2729af92004-05-03 20:45:30 +00002838Linux Support:
2839==============
wdenkc6097192002-11-03 00:24:07 +00002840
wdenk2729af92004-05-03 20:45:30 +00002841Although U-Boot should support any OS or standalone application
2842easily, the main focus has always been on Linux during the design of
2843U-Boot.
wdenkc6097192002-11-03 00:24:07 +00002844
wdenk2729af92004-05-03 20:45:30 +00002845U-Boot includes many features that so far have been part of some
2846special "boot loader" code within the Linux kernel. Also, any
2847"initrd" images to be used are no longer part of one big Linux image;
2848instead, kernel and "initrd" are separate images. This implementation
2849serves several purposes:
wdenkc6097192002-11-03 00:24:07 +00002850
wdenk2729af92004-05-03 20:45:30 +00002851- the same features can be used for other OS or standalone
2852 applications (for instance: using compressed images to reduce the
2853 Flash memory footprint)
wdenkc6097192002-11-03 00:24:07 +00002854
wdenk2729af92004-05-03 20:45:30 +00002855- it becomes much easier to port new Linux kernel versions because
2856 lots of low-level, hardware dependent stuff are done by U-Boot
wdenkc6097192002-11-03 00:24:07 +00002857
wdenk2729af92004-05-03 20:45:30 +00002858- the same Linux kernel image can now be used with different "initrd"
2859 images; of course this also means that different kernel images can
2860 be run with the same "initrd". This makes testing easier (you don't
2861 have to build a new "zImage.initrd" Linux image when you just
2862 change a file in your "initrd"). Also, a field-upgrade of the
2863 software is easier now.
wdenkc6097192002-11-03 00:24:07 +00002864
wdenkc6097192002-11-03 00:24:07 +00002865
wdenk2729af92004-05-03 20:45:30 +00002866Linux HOWTO:
2867============
wdenkc6097192002-11-03 00:24:07 +00002868
wdenk2729af92004-05-03 20:45:30 +00002869Porting Linux to U-Boot based systems:
2870---------------------------------------
wdenkc6097192002-11-03 00:24:07 +00002871
wdenk2729af92004-05-03 20:45:30 +00002872U-Boot cannot save you from doing all the necessary modifications to
2873configure the Linux device drivers for use with your target hardware
2874(no, we don't intend to provide a full virtual machine interface to
2875Linux :-).
wdenkc6097192002-11-03 00:24:07 +00002876
wdenk2729af92004-05-03 20:45:30 +00002877But now you can ignore ALL boot loader code (in arch/ppc/mbxboot).
wdenkc6097192002-11-03 00:24:07 +00002878
wdenk2729af92004-05-03 20:45:30 +00002879Just make sure your machine specific header file (for instance
2880include/asm-ppc/tqm8xx.h) includes the same definition of the Board
2881Information structure as we define in include/u-boot.h, and make
2882sure that your definition of IMAP_ADDR uses the same value as your
2883U-Boot configuration in CFG_IMMR.
wdenkc6097192002-11-03 00:24:07 +00002884
wdenkc6097192002-11-03 00:24:07 +00002885
wdenk2729af92004-05-03 20:45:30 +00002886Configuring the Linux kernel:
2887-----------------------------
wdenkc6097192002-11-03 00:24:07 +00002888
wdenk2729af92004-05-03 20:45:30 +00002889No specific requirements for U-Boot. Make sure you have some root
2890device (initial ramdisk, NFS) for your target system.
wdenkc6097192002-11-03 00:24:07 +00002891
wdenkc6097192002-11-03 00:24:07 +00002892
wdenk2729af92004-05-03 20:45:30 +00002893Building a Linux Image:
2894-----------------------
wdenkc6097192002-11-03 00:24:07 +00002895
wdenk2729af92004-05-03 20:45:30 +00002896With U-Boot, "normal" build targets like "zImage" or "bzImage" are
2897not used. If you use recent kernel source, a new build target
2898"uImage" will exist which automatically builds an image usable by
2899U-Boot. Most older kernels also have support for a "pImage" target,
2900which was introduced for our predecessor project PPCBoot and uses a
2901100% compatible format.
wdenkc6097192002-11-03 00:24:07 +00002902
wdenk2729af92004-05-03 20:45:30 +00002903Example:
wdenkc6097192002-11-03 00:24:07 +00002904
wdenk2729af92004-05-03 20:45:30 +00002905 make TQM850L_config
2906 make oldconfig
2907 make dep
2908 make uImage
wdenkc6097192002-11-03 00:24:07 +00002909
wdenk2729af92004-05-03 20:45:30 +00002910The "uImage" build target uses a special tool (in 'tools/mkimage') to
2911encapsulate a compressed Linux kernel image with header information,
2912CRC32 checksum etc. for use with U-Boot. This is what we are doing:
wdenkc6097192002-11-03 00:24:07 +00002913
wdenk2729af92004-05-03 20:45:30 +00002914* build a standard "vmlinux" kernel image (in ELF binary format):
wdenkc6097192002-11-03 00:24:07 +00002915
wdenk2729af92004-05-03 20:45:30 +00002916* convert the kernel into a raw binary image:
wdenkc6097192002-11-03 00:24:07 +00002917
wdenk2729af92004-05-03 20:45:30 +00002918 ${CROSS_COMPILE}-objcopy -O binary \
2919 -R .note -R .comment \
2920 -S vmlinux linux.bin
wdenkc6097192002-11-03 00:24:07 +00002921
wdenk2729af92004-05-03 20:45:30 +00002922* compress the binary image:
wdenkc6097192002-11-03 00:24:07 +00002923
wdenk2729af92004-05-03 20:45:30 +00002924 gzip -9 linux.bin
wdenkc6097192002-11-03 00:24:07 +00002925
wdenk2729af92004-05-03 20:45:30 +00002926* package compressed binary image for U-Boot:
wdenk24ee89b2002-11-03 17:56:27 +00002927
wdenk2729af92004-05-03 20:45:30 +00002928 mkimage -A ppc -O linux -T kernel -C gzip \
2929 -a 0 -e 0 -n "Linux Kernel Image" \
2930 -d linux.bin.gz uImage
wdenk24ee89b2002-11-03 17:56:27 +00002931
wdenk24ee89b2002-11-03 17:56:27 +00002932
wdenk2729af92004-05-03 20:45:30 +00002933The "mkimage" tool can also be used to create ramdisk images for use
2934with U-Boot, either separated from the Linux kernel image, or
2935combined into one file. "mkimage" encapsulates the images with a 64
2936byte header containing information about target architecture,
2937operating system, image type, compression method, entry points, time
2938stamp, CRC32 checksums, etc.
wdenk24ee89b2002-11-03 17:56:27 +00002939
wdenk2729af92004-05-03 20:45:30 +00002940"mkimage" can be called in two ways: to verify existing images and
2941print the header information, or to build new images.
wdenk24ee89b2002-11-03 17:56:27 +00002942
wdenk2729af92004-05-03 20:45:30 +00002943In the first form (with "-l" option) mkimage lists the information
2944contained in the header of an existing U-Boot image; this includes
2945checksum verification:
wdenk24ee89b2002-11-03 17:56:27 +00002946
wdenk2729af92004-05-03 20:45:30 +00002947 tools/mkimage -l image
2948 -l ==> list image header information
wdenk24ee89b2002-11-03 17:56:27 +00002949
wdenk2729af92004-05-03 20:45:30 +00002950The second form (with "-d" option) is used to build a U-Boot image
2951from a "data file" which is used as image payload:
wdenk24ee89b2002-11-03 17:56:27 +00002952
wdenk2729af92004-05-03 20:45:30 +00002953 tools/mkimage -A arch -O os -T type -C comp -a addr -e ep \
2954 -n name -d data_file image
2955 -A ==> set architecture to 'arch'
2956 -O ==> set operating system to 'os'
2957 -T ==> set image type to 'type'
2958 -C ==> set compression type 'comp'
2959 -a ==> set load address to 'addr' (hex)
2960 -e ==> set entry point to 'ep' (hex)
2961 -n ==> set image name to 'name'
2962 -d ==> use image data from 'datafile'
wdenk24ee89b2002-11-03 17:56:27 +00002963
wdenk69459792004-05-29 16:53:29 +00002964Right now, all Linux kernels for PowerPC systems use the same load
2965address (0x00000000), but the entry point address depends on the
2966kernel version:
wdenkc6097192002-11-03 00:24:07 +00002967
wdenk2729af92004-05-03 20:45:30 +00002968- 2.2.x kernels have the entry point at 0x0000000C,
2969- 2.3.x and later kernels have the entry point at 0x00000000.
wdenkc6097192002-11-03 00:24:07 +00002970
wdenk2729af92004-05-03 20:45:30 +00002971So a typical call to build a U-Boot image would read:
wdenkc6097192002-11-03 00:24:07 +00002972
wdenk2729af92004-05-03 20:45:30 +00002973 -> tools/mkimage -n '2.4.4 kernel for TQM850L' \
2974 > -A ppc -O linux -T kernel -C gzip -a 0 -e 0 \
2975 > -d /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/ppc/coffboot/vmlinux.gz \
2976 > examples/uImage.TQM850L
2977 Image Name: 2.4.4 kernel for TQM850L
2978 Created: Wed Jul 19 02:34:59 2000
2979 Image Type: PowerPC Linux Kernel Image (gzip compressed)
2980 Data Size: 335725 Bytes = 327.86 kB = 0.32 MB
2981 Load Address: 0x00000000
2982 Entry Point: 0x00000000
wdenkc6097192002-11-03 00:24:07 +00002983
wdenk2729af92004-05-03 20:45:30 +00002984To verify the contents of the image (or check for corruption):
wdenkc6097192002-11-03 00:24:07 +00002985
wdenk2729af92004-05-03 20:45:30 +00002986 -> tools/mkimage -l examples/uImage.TQM850L
2987 Image Name: 2.4.4 kernel for TQM850L
2988 Created: Wed Jul 19 02:34:59 2000
2989 Image Type: PowerPC Linux Kernel Image (gzip compressed)
2990 Data Size: 335725 Bytes = 327.86 kB = 0.32 MB
2991 Load Address: 0x00000000
2992 Entry Point: 0x00000000
wdenkc6097192002-11-03 00:24:07 +00002993
wdenk2729af92004-05-03 20:45:30 +00002994NOTE: for embedded systems where boot time is critical you can trade
2995speed for memory and install an UNCOMPRESSED image instead: this
2996needs more space in Flash, but boots much faster since it does not
2997need to be uncompressed:
wdenkc6097192002-11-03 00:24:07 +00002998
wdenk2729af92004-05-03 20:45:30 +00002999 -> gunzip /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/ppc/coffboot/vmlinux.gz
3000 -> tools/mkimage -n '2.4.4 kernel for TQM850L' \
3001 > -A ppc -O linux -T kernel -C none -a 0 -e 0 \
3002 > -d /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/ppc/coffboot/vmlinux \
3003 > examples/uImage.TQM850L-uncompressed
3004 Image Name: 2.4.4 kernel for TQM850L
3005 Created: Wed Jul 19 02:34:59 2000
3006 Image Type: PowerPC Linux Kernel Image (uncompressed)
3007 Data Size: 792160 Bytes = 773.59 kB = 0.76 MB
3008 Load Address: 0x00000000
3009 Entry Point: 0x00000000
wdenkc6097192002-11-03 00:24:07 +00003010
wdenkc6097192002-11-03 00:24:07 +00003011
wdenk2729af92004-05-03 20:45:30 +00003012Similar you can build U-Boot images from a 'ramdisk.image.gz' file
3013when your kernel is intended to use an initial ramdisk:
wdenkdb01a2e2004-04-15 23:14:49 +00003014
wdenk2729af92004-05-03 20:45:30 +00003015 -> tools/mkimage -n 'Simple Ramdisk Image' \
3016 > -A ppc -O linux -T ramdisk -C gzip \
3017 > -d /LinuxPPC/images/SIMPLE-ramdisk.image.gz examples/simple-initrd
3018 Image Name: Simple Ramdisk Image
3019 Created: Wed Jan 12 14:01:50 2000
3020 Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
3021 Data Size: 566530 Bytes = 553.25 kB = 0.54 MB
3022 Load Address: 0x00000000
3023 Entry Point: 0x00000000
wdenkdb01a2e2004-04-15 23:14:49 +00003024
wdenkdb01a2e2004-04-15 23:14:49 +00003025
wdenk2729af92004-05-03 20:45:30 +00003026Installing a Linux Image:
3027-------------------------
wdenkdb01a2e2004-04-15 23:14:49 +00003028
wdenk2729af92004-05-03 20:45:30 +00003029To downloading a U-Boot image over the serial (console) interface,
3030you must convert the image to S-Record format:
wdenkdb01a2e2004-04-15 23:14:49 +00003031
wdenk2729af92004-05-03 20:45:30 +00003032 objcopy -I binary -O srec examples/image examples/image.srec
wdenkdb01a2e2004-04-15 23:14:49 +00003033
wdenk2729af92004-05-03 20:45:30 +00003034The 'objcopy' does not understand the information in the U-Boot
3035image header, so the resulting S-Record file will be relative to
3036address 0x00000000. To load it to a given address, you need to
3037specify the target address as 'offset' parameter with the 'loads'
3038command.
wdenkc6097192002-11-03 00:24:07 +00003039
wdenk2729af92004-05-03 20:45:30 +00003040Example: install the image to address 0x40100000 (which on the
3041TQM8xxL is in the first Flash bank):
wdenkc6097192002-11-03 00:24:07 +00003042
wdenk2729af92004-05-03 20:45:30 +00003043 => erase 40100000 401FFFFF
wdenkc6097192002-11-03 00:24:07 +00003044
wdenk2729af92004-05-03 20:45:30 +00003045 .......... done
3046 Erased 8 sectors
wdenkc6097192002-11-03 00:24:07 +00003047
wdenk2729af92004-05-03 20:45:30 +00003048 => loads 40100000
3049 ## Ready for S-Record download ...
3050 ~>examples/image.srec
3051 1 2 3 4 5 6 7 8 9 10 11 12 13 ...
3052 ...
3053 15989 15990 15991 15992
3054 [file transfer complete]
3055 [connected]
3056 ## Start Addr = 0x00000000
wdenkc6097192002-11-03 00:24:07 +00003057
3058
wdenk2729af92004-05-03 20:45:30 +00003059You can check the success of the download using the 'iminfo' command;
3060this includes a checksum verification so you can be sure no data
3061corruption happened:
wdenkc6097192002-11-03 00:24:07 +00003062
wdenk2729af92004-05-03 20:45:30 +00003063 => imi 40100000
wdenkc6097192002-11-03 00:24:07 +00003064
wdenk2729af92004-05-03 20:45:30 +00003065 ## Checking Image at 40100000 ...
3066 Image Name: 2.2.13 for initrd on TQM850L
3067 Image Type: PowerPC Linux Kernel Image (gzip compressed)
3068 Data Size: 335725 Bytes = 327 kB = 0 MB
3069 Load Address: 00000000
3070 Entry Point: 0000000c
3071 Verifying Checksum ... OK
wdenkc6097192002-11-03 00:24:07 +00003072
3073
wdenk2729af92004-05-03 20:45:30 +00003074Boot Linux:
3075-----------
wdenkc6097192002-11-03 00:24:07 +00003076
wdenk2729af92004-05-03 20:45:30 +00003077The "bootm" command is used to boot an application that is stored in
3078memory (RAM or Flash). In case of a Linux kernel image, the contents
3079of the "bootargs" environment variable is passed to the kernel as
3080parameters. You can check and modify this variable using the
3081"printenv" and "setenv" commands:
wdenkc6097192002-11-03 00:24:07 +00003082
3083
wdenk2729af92004-05-03 20:45:30 +00003084 => printenv bootargs
3085 bootargs=root=/dev/ram
wdenkc6097192002-11-03 00:24:07 +00003086
wdenk2729af92004-05-03 20:45:30 +00003087 => 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 +00003088
wdenk2729af92004-05-03 20:45:30 +00003089 => printenv bootargs
3090 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 +00003091
wdenk2729af92004-05-03 20:45:30 +00003092 => bootm 40020000
3093 ## Booting Linux kernel at 40020000 ...
3094 Image Name: 2.2.13 for NFS on TQM850L
3095 Image Type: PowerPC Linux Kernel Image (gzip compressed)
3096 Data Size: 381681 Bytes = 372 kB = 0 MB
3097 Load Address: 00000000
3098 Entry Point: 0000000c
3099 Verifying Checksum ... OK
3100 Uncompressing Kernel Image ... OK
3101 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
3102 Boot arguments: root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2
3103 time_init: decrementer frequency = 187500000/60
3104 Calibrating delay loop... 49.77 BogoMIPS
3105 Memory: 15208k available (700k kernel code, 444k data, 32k init) [c0000000,c1000000]
3106 ...
wdenkc6097192002-11-03 00:24:07 +00003107
wdenk2729af92004-05-03 20:45:30 +00003108If you want to boot a Linux kernel with initial ram disk, you pass
3109the memory addresses of both the kernel and the initrd image (PPBCOOT
3110format!) to the "bootm" command:
wdenkc6097192002-11-03 00:24:07 +00003111
wdenk2729af92004-05-03 20:45:30 +00003112 => imi 40100000 40200000
wdenkc6097192002-11-03 00:24:07 +00003113
wdenk2729af92004-05-03 20:45:30 +00003114 ## Checking Image at 40100000 ...
3115 Image Name: 2.2.13 for initrd on TQM850L
3116 Image Type: PowerPC Linux Kernel Image (gzip compressed)
3117 Data Size: 335725 Bytes = 327 kB = 0 MB
3118 Load Address: 00000000
3119 Entry Point: 0000000c
3120 Verifying Checksum ... OK
wdenkc6097192002-11-03 00:24:07 +00003121
wdenk2729af92004-05-03 20:45:30 +00003122 ## Checking Image at 40200000 ...
3123 Image Name: Simple Ramdisk Image
3124 Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
3125 Data Size: 566530 Bytes = 553 kB = 0 MB
3126 Load Address: 00000000
3127 Entry Point: 00000000
3128 Verifying Checksum ... OK
wdenkc6097192002-11-03 00:24:07 +00003129
wdenk2729af92004-05-03 20:45:30 +00003130 => bootm 40100000 40200000
3131 ## Booting Linux kernel at 40100000 ...
3132 Image Name: 2.2.13 for initrd on TQM850L
3133 Image Type: PowerPC Linux Kernel Image (gzip compressed)
3134 Data Size: 335725 Bytes = 327 kB = 0 MB
3135 Load Address: 00000000
3136 Entry Point: 0000000c
3137 Verifying Checksum ... OK
3138 Uncompressing Kernel Image ... OK
3139 ## Loading RAMDisk Image at 40200000 ...
3140 Image Name: Simple Ramdisk Image
3141 Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
3142 Data Size: 566530 Bytes = 553 kB = 0 MB
3143 Load Address: 00000000
3144 Entry Point: 00000000
3145 Verifying Checksum ... OK
3146 Loading Ramdisk ... OK
3147 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
3148 Boot arguments: root=/dev/ram
3149 time_init: decrementer frequency = 187500000/60
3150 Calibrating delay loop... 49.77 BogoMIPS
3151 ...
3152 RAMDISK: Compressed image found at block 0
3153 VFS: Mounted root (ext2 filesystem).
wdenkc6097192002-11-03 00:24:07 +00003154
wdenk2729af92004-05-03 20:45:30 +00003155 bash#
wdenkc6097192002-11-03 00:24:07 +00003156
Matthew McClintock02677682006-06-28 10:41:37 -05003157Boot Linux and pass a flat device tree:
3158-----------
3159
3160First, U-Boot must be compiled with the appropriate defines. See the section
3161titled "Linux Kernel Interface" above for a more in depth explanation. The
3162following is an example of how to start a kernel and pass an updated
3163flat device tree:
3164
3165=> print oftaddr
3166oftaddr=0x300000
3167=> print oft
3168oft=oftrees/mpc8540ads.dtb
3169=> tftp $oftaddr $oft
3170Speed: 1000, full duplex
3171Using TSEC0 device
3172TFTP from server 192.168.1.1; our IP address is 192.168.1.101
3173Filename 'oftrees/mpc8540ads.dtb'.
3174Load address: 0x300000
3175Loading: #
3176done
3177Bytes transferred = 4106 (100a hex)
3178=> tftp $loadaddr $bootfile
3179Speed: 1000, full duplex
3180Using TSEC0 device
3181TFTP from server 192.168.1.1; our IP address is 192.168.1.2
3182Filename 'uImage'.
3183Load address: 0x200000
3184Loading:############
3185done
3186Bytes transferred = 1029407 (fb51f hex)
3187=> print loadaddr
3188loadaddr=200000
3189=> print oftaddr
3190oftaddr=0x300000
3191=> bootm $loadaddr - $oftaddr
3192## Booting image at 00200000 ...
Wolfgang Denka9398e02006-11-27 15:32:42 +01003193 Image Name: Linux-2.6.17-dirty
3194 Image Type: PowerPC Linux Kernel Image (gzip compressed)
3195 Data Size: 1029343 Bytes = 1005.2 kB
Matthew McClintock02677682006-06-28 10:41:37 -05003196 Load Address: 00000000
Wolfgang Denka9398e02006-11-27 15:32:42 +01003197 Entry Point: 00000000
Matthew McClintock02677682006-06-28 10:41:37 -05003198 Verifying Checksum ... OK
3199 Uncompressing Kernel Image ... OK
3200Booting using flat device tree at 0x300000
3201Using MPC85xx ADS machine description
3202Memory CAM mapping: CAM0=256Mb, CAM1=256Mb, CAM2=0Mb residual: 0Mb
3203[snip]
3204
3205
wdenk2729af92004-05-03 20:45:30 +00003206More About U-Boot Image Types:
3207------------------------------
wdenk6069ff22003-02-28 00:49:47 +00003208
wdenk2729af92004-05-03 20:45:30 +00003209U-Boot supports the following image types:
wdenk6069ff22003-02-28 00:49:47 +00003210
wdenk2729af92004-05-03 20:45:30 +00003211 "Standalone Programs" are directly runnable in the environment
3212 provided by U-Boot; it is expected that (if they behave
3213 well) you can continue to work in U-Boot after return from
3214 the Standalone Program.
3215 "OS Kernel Images" are usually images of some Embedded OS which
3216 will take over control completely. Usually these programs
3217 will install their own set of exception handlers, device
3218 drivers, set up the MMU, etc. - this means, that you cannot
3219 expect to re-enter U-Boot except by resetting the CPU.
3220 "RAMDisk Images" are more or less just data blocks, and their
3221 parameters (address, size) are passed to an OS kernel that is
3222 being started.
3223 "Multi-File Images" contain several images, typically an OS
3224 (Linux) kernel image and one or more data images like
3225 RAMDisks. This construct is useful for instance when you want
3226 to boot over the network using BOOTP etc., where the boot
3227 server provides just a single image file, but you want to get
3228 for instance an OS kernel and a RAMDisk image.
stroesec1551ea2003-04-04 15:53:41 +00003229
wdenk2729af92004-05-03 20:45:30 +00003230 "Multi-File Images" start with a list of image sizes, each
3231 image size (in bytes) specified by an "uint32_t" in network
3232 byte order. This list is terminated by an "(uint32_t)0".
3233 Immediately after the terminating 0 follow the images, one by
3234 one, all aligned on "uint32_t" boundaries (size rounded up to
3235 a multiple of 4 bytes).
stroesec1551ea2003-04-04 15:53:41 +00003236
wdenk2729af92004-05-03 20:45:30 +00003237 "Firmware Images" are binary images containing firmware (like
3238 U-Boot or FPGA images) which usually will be programmed to
3239 flash memory.
stroesec1551ea2003-04-04 15:53:41 +00003240
wdenk2729af92004-05-03 20:45:30 +00003241 "Script files" are command sequences that will be executed by
3242 U-Boot's command interpreter; this feature is especially
3243 useful when you configure U-Boot to use a real shell (hush)
3244 as command interpreter.
wdenk6069ff22003-02-28 00:49:47 +00003245
wdenkc6097192002-11-03 00:24:07 +00003246
wdenk2729af92004-05-03 20:45:30 +00003247Standalone HOWTO:
3248=================
wdenkc6097192002-11-03 00:24:07 +00003249
wdenk2729af92004-05-03 20:45:30 +00003250One of the features of U-Boot is that you can dynamically load and
3251run "standalone" applications, which can use some resources of
3252U-Boot like console I/O functions or interrupt services.
wdenkc6097192002-11-03 00:24:07 +00003253
wdenk2729af92004-05-03 20:45:30 +00003254Two simple examples are included with the sources:
wdenkc6097192002-11-03 00:24:07 +00003255
wdenk2729af92004-05-03 20:45:30 +00003256"Hello World" Demo:
3257-------------------
wdenkc6097192002-11-03 00:24:07 +00003258
wdenk2729af92004-05-03 20:45:30 +00003259'examples/hello_world.c' contains a small "Hello World" Demo
3260application; it is automatically compiled when you build U-Boot.
3261It's configured to run at address 0x00040004, so you can play with it
3262like that:
wdenkc6097192002-11-03 00:24:07 +00003263
wdenk2729af92004-05-03 20:45:30 +00003264 => loads
3265 ## Ready for S-Record download ...
3266 ~>examples/hello_world.srec
3267 1 2 3 4 5 6 7 8 9 10 11 ...
3268 [file transfer complete]
3269 [connected]
3270 ## Start Addr = 0x00040004
wdenkc6097192002-11-03 00:24:07 +00003271
wdenk2729af92004-05-03 20:45:30 +00003272 => go 40004 Hello World! This is a test.
3273 ## Starting application at 0x00040004 ...
3274 Hello World
3275 argc = 7
3276 argv[0] = "40004"
3277 argv[1] = "Hello"
3278 argv[2] = "World!"
3279 argv[3] = "This"
3280 argv[4] = "is"
3281 argv[5] = "a"
3282 argv[6] = "test."
3283 argv[7] = "<NULL>"
3284 Hit any key to exit ...
wdenkc6097192002-11-03 00:24:07 +00003285
wdenk2729af92004-05-03 20:45:30 +00003286 ## Application terminated, rc = 0x0
wdenkc6097192002-11-03 00:24:07 +00003287
wdenk2729af92004-05-03 20:45:30 +00003288Another example, which demonstrates how to register a CPM interrupt
3289handler with the U-Boot code, can be found in 'examples/timer.c'.
3290Here, a CPM timer is set up to generate an interrupt every second.
3291The interrupt service routine is trivial, just printing a '.'
3292character, but this is just a demo program. The application can be
3293controlled by the following keys:
wdenkc6097192002-11-03 00:24:07 +00003294
wdenk2729af92004-05-03 20:45:30 +00003295 ? - print current values og the CPM Timer registers
3296 b - enable interrupts and start timer
3297 e - stop timer and disable interrupts
3298 q - quit application
wdenkc6097192002-11-03 00:24:07 +00003299
wdenk2729af92004-05-03 20:45:30 +00003300 => loads
3301 ## Ready for S-Record download ...
3302 ~>examples/timer.srec
3303 1 2 3 4 5 6 7 8 9 10 11 ...
3304 [file transfer complete]
3305 [connected]
3306 ## Start Addr = 0x00040004
wdenkc6097192002-11-03 00:24:07 +00003307
wdenk2729af92004-05-03 20:45:30 +00003308 => go 40004
3309 ## Starting application at 0x00040004 ...
3310 TIMERS=0xfff00980
3311 Using timer 1
3312 tgcr @ 0xfff00980, tmr @ 0xfff00990, trr @ 0xfff00994, tcr @ 0xfff00998, tcn @ 0xfff0099c, ter @ 0xfff009b0
wdenkc6097192002-11-03 00:24:07 +00003313
wdenk2729af92004-05-03 20:45:30 +00003314Hit 'b':
3315 [q, b, e, ?] Set interval 1000000 us
3316 Enabling timer
3317Hit '?':
3318 [q, b, e, ?] ........
3319 tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0xef6, ter=0x0
3320Hit '?':
3321 [q, b, e, ?] .
3322 tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x2ad4, ter=0x0
3323Hit '?':
3324 [q, b, e, ?] .
3325 tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x1efc, ter=0x0
3326Hit '?':
3327 [q, b, e, ?] .
3328 tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x169d, ter=0x0
3329Hit 'e':
3330 [q, b, e, ?] ...Stopping timer
3331Hit 'q':
3332 [q, b, e, ?] ## Application terminated, rc = 0x0
wdenkc6097192002-11-03 00:24:07 +00003333
3334
wdenk2729af92004-05-03 20:45:30 +00003335Minicom warning:
3336================
wdenk85ec0bc2003-03-31 16:34:49 +00003337
wdenk2729af92004-05-03 20:45:30 +00003338Over time, many people have reported problems when trying to use the
3339"minicom" terminal emulation program for serial download. I (wd)
3340consider minicom to be broken, and recommend not to use it. Under
3341Unix, I recommend to use C-Kermit for general purpose use (and
3342especially for kermit binary protocol download ("loadb" command), and
3343use "cu" for S-Record download ("loads" command).
wdenk85ec0bc2003-03-31 16:34:49 +00003344
wdenk2729af92004-05-03 20:45:30 +00003345Nevertheless, if you absolutely want to use it try adding this
3346configuration to your "File transfer protocols" section:
wdenk52f52c12003-06-19 23:04:19 +00003347
wdenk2729af92004-05-03 20:45:30 +00003348 Name Program Name U/D FullScr IO-Red. Multi
3349 X kermit /usr/bin/kermit -i -l %l -s Y U Y N N
3350 Y kermit /usr/bin/kermit -i -l %l -r N D Y N N
wdenk52f52c12003-06-19 23:04:19 +00003351
3352
wdenk2729af92004-05-03 20:45:30 +00003353NetBSD Notes:
3354=============
wdenkc6097192002-11-03 00:24:07 +00003355
wdenk2729af92004-05-03 20:45:30 +00003356Starting at version 0.9.2, U-Boot supports NetBSD both as host
3357(build U-Boot) and target system (boots NetBSD/mpc8xx).
wdenkc6097192002-11-03 00:24:07 +00003358
wdenk2729af92004-05-03 20:45:30 +00003359Building requires a cross environment; it is known to work on
3360NetBSD/i386 with the cross-powerpc-netbsd-1.3 package (you will also
3361need gmake since the Makefiles are not compatible with BSD make).
3362Note that the cross-powerpc package does not install include files;
3363attempting to build U-Boot will fail because <machine/ansi.h> is
3364missing. This file has to be installed and patched manually:
wdenkc6097192002-11-03 00:24:07 +00003365
wdenk2729af92004-05-03 20:45:30 +00003366 # cd /usr/pkg/cross/powerpc-netbsd/include
3367 # mkdir powerpc
3368 # ln -s powerpc machine
3369 # cp /usr/src/sys/arch/powerpc/include/ansi.h powerpc/ansi.h
3370 # ${EDIT} powerpc/ansi.h ## must remove __va_list, _BSD_VA_LIST
wdenkc6097192002-11-03 00:24:07 +00003371
wdenk2729af92004-05-03 20:45:30 +00003372Native builds *don't* work due to incompatibilities between native
3373and U-Boot include files.
wdenkc6097192002-11-03 00:24:07 +00003374
wdenk2729af92004-05-03 20:45:30 +00003375Booting assumes that (the first part of) the image booted is a
3376stage-2 loader which in turn loads and then invokes the kernel
3377proper. Loader sources will eventually appear in the NetBSD source
3378tree (probably in sys/arc/mpc8xx/stand/u-boot_stage2/); in the
wdenk2a8af182005-04-13 10:02:42 +00003379meantime, see ftp://ftp.denx.de/pub/u-boot/ppcboot_stage2.tar.gz
wdenkc6097192002-11-03 00:24:07 +00003380
3381
wdenk2729af92004-05-03 20:45:30 +00003382Implementation Internals:
3383=========================
wdenkc6097192002-11-03 00:24:07 +00003384
wdenk2729af92004-05-03 20:45:30 +00003385The following is not intended to be a complete description of every
3386implementation detail. However, it should help to understand the
3387inner workings of U-Boot and make it easier to port it to custom
3388hardware.
wdenkc6097192002-11-03 00:24:07 +00003389
3390
wdenk2729af92004-05-03 20:45:30 +00003391Initial Stack, Global Data:
3392---------------------------
wdenkc6097192002-11-03 00:24:07 +00003393
wdenk2729af92004-05-03 20:45:30 +00003394The implementation of U-Boot is complicated by the fact that U-Boot
3395starts running out of ROM (flash memory), usually without access to
3396system RAM (because the memory controller is not initialized yet).
3397This means that we don't have writable Data or BSS segments, and BSS
3398is not initialized as zero. To be able to get a C environment working
3399at all, we have to allocate at least a minimal stack. Implementation
3400options for this are defined and restricted by the CPU used: Some CPU
3401models provide on-chip memory (like the IMMR area on MPC8xx and
3402MPC826x processors), on others (parts of) the data cache can be
3403locked as (mis-) used as memory, etc.
wdenkc6097192002-11-03 00:24:07 +00003404
wdenk2729af92004-05-03 20:45:30 +00003405 Chris Hallinan posted a good summary of these issues to the
3406 u-boot-users mailing list:
wdenk43d96162003-03-06 00:02:04 +00003407
wdenk2729af92004-05-03 20:45:30 +00003408 Subject: RE: [U-Boot-Users] RE: More On Memory Bank x (nothingness)?
3409 From: "Chris Hallinan" <clh@net1plus.com>
3410 Date: Mon, 10 Feb 2003 16:43:46 -0500 (22:43 MET)
3411 ...
wdenk43d96162003-03-06 00:02:04 +00003412
wdenk2729af92004-05-03 20:45:30 +00003413 Correct me if I'm wrong, folks, but the way I understand it
3414 is this: Using DCACHE as initial RAM for Stack, etc, does not
3415 require any physical RAM backing up the cache. The cleverness
3416 is that the cache is being used as a temporary supply of
3417 necessary storage before the SDRAM controller is setup. It's
3418 beyond the scope of this list to expain the details, but you
3419 can see how this works by studying the cache architecture and
3420 operation in the architecture and processor-specific manuals.
wdenk43d96162003-03-06 00:02:04 +00003421
wdenk2729af92004-05-03 20:45:30 +00003422 OCM is On Chip Memory, which I believe the 405GP has 4K. It
3423 is another option for the system designer to use as an
3424 initial stack/ram area prior to SDRAM being available. Either
3425 option should work for you. Using CS 4 should be fine if your
3426 board designers haven't used it for something that would
3427 cause you grief during the initial boot! It is frequently not
3428 used.
wdenk43d96162003-03-06 00:02:04 +00003429
wdenk2729af92004-05-03 20:45:30 +00003430 CFG_INIT_RAM_ADDR should be somewhere that won't interfere
3431 with your processor/board/system design. The default value
3432 you will find in any recent u-boot distribution in
Stefan Roese8a316c92005-08-01 16:49:12 +02003433 walnut.h should work for you. I'd set it to a value larger
wdenk2729af92004-05-03 20:45:30 +00003434 than your SDRAM module. If you have a 64MB SDRAM module, set
3435 it above 400_0000. Just make sure your board has no resources
3436 that are supposed to respond to that address! That code in
3437 start.S has been around a while and should work as is when
3438 you get the config right.
wdenk43d96162003-03-06 00:02:04 +00003439
wdenk2729af92004-05-03 20:45:30 +00003440 -Chris Hallinan
3441 DS4.COM, Inc.
wdenk43d96162003-03-06 00:02:04 +00003442
wdenk2729af92004-05-03 20:45:30 +00003443It is essential to remember this, since it has some impact on the C
3444code for the initialization procedures:
wdenkc6097192002-11-03 00:24:07 +00003445
wdenk2729af92004-05-03 20:45:30 +00003446* Initialized global data (data segment) is read-only. Do not attempt
3447 to write it.
wdenkc6097192002-11-03 00:24:07 +00003448
wdenk2729af92004-05-03 20:45:30 +00003449* Do not use any unitialized global data (or implicitely initialized
3450 as zero data - BSS segment) at all - this is undefined, initiali-
3451 zation is performed later (when relocating to RAM).
wdenkc6097192002-11-03 00:24:07 +00003452
wdenk2729af92004-05-03 20:45:30 +00003453* Stack space is very limited. Avoid big data buffers or things like
3454 that.
wdenkc6097192002-11-03 00:24:07 +00003455
wdenk2729af92004-05-03 20:45:30 +00003456Having only the stack as writable memory limits means we cannot use
3457normal global data to share information beween the code. But it
3458turned out that the implementation of U-Boot can be greatly
3459simplified by making a global data structure (gd_t) available to all
3460functions. We could pass a pointer to this data as argument to _all_
3461functions, but this would bloat the code. Instead we use a feature of
3462the GCC compiler (Global Register Variables) to share the data: we
3463place a pointer (gd) to the global data into a register which we
3464reserve for this purpose.
wdenkc6097192002-11-03 00:24:07 +00003465
wdenk2729af92004-05-03 20:45:30 +00003466When choosing a register for such a purpose we are restricted by the
3467relevant (E)ABI specifications for the current architecture, and by
3468GCC's implementation.
wdenkc6097192002-11-03 00:24:07 +00003469
wdenk2729af92004-05-03 20:45:30 +00003470For PowerPC, the following registers have specific use:
3471 R1: stack pointer
3472 R2: TOC pointer
3473 R3-R4: parameter passing and return values
3474 R5-R10: parameter passing
3475 R13: small data area pointer
3476 R30: GOT pointer
3477 R31: frame pointer
wdenkc6097192002-11-03 00:24:07 +00003478
wdenk2729af92004-05-03 20:45:30 +00003479 (U-Boot also uses R14 as internal GOT pointer.)
wdenkc6097192002-11-03 00:24:07 +00003480
wdenk2729af92004-05-03 20:45:30 +00003481 ==> U-Boot will use R29 to hold a pointer to the global data
wdenkc6097192002-11-03 00:24:07 +00003482
wdenk2729af92004-05-03 20:45:30 +00003483 Note: on PPC, we could use a static initializer (since the
3484 address of the global data structure is known at compile time),
3485 but it turned out that reserving a register results in somewhat
3486 smaller code - although the code savings are not that big (on
3487 average for all boards 752 bytes for the whole U-Boot image,
3488 624 text + 127 data).
wdenkc6097192002-11-03 00:24:07 +00003489
wdenk2729af92004-05-03 20:45:30 +00003490On ARM, the following registers are used:
wdenkc6097192002-11-03 00:24:07 +00003491
wdenk2729af92004-05-03 20:45:30 +00003492 R0: function argument word/integer result
3493 R1-R3: function argument word
3494 R9: GOT pointer
3495 R10: stack limit (used only if stack checking if enabled)
3496 R11: argument (frame) pointer
3497 R12: temporary workspace
3498 R13: stack pointer
3499 R14: link register
3500 R15: program counter
wdenkc6097192002-11-03 00:24:07 +00003501
wdenk2729af92004-05-03 20:45:30 +00003502 ==> U-Boot will use R8 to hold a pointer to the global data
wdenkc6097192002-11-03 00:24:07 +00003503
Wolfgang Denkd87080b2006-03-31 18:32:53 +02003504NOTE: DECLARE_GLOBAL_DATA_PTR must be used with file-global scope,
3505or current versions of GCC may "optimize" the code too much.
wdenkc6097192002-11-03 00:24:07 +00003506
wdenk2729af92004-05-03 20:45:30 +00003507Memory Management:
3508------------------
wdenkc6097192002-11-03 00:24:07 +00003509
wdenk2729af92004-05-03 20:45:30 +00003510U-Boot runs in system state and uses physical addresses, i.e. the
3511MMU is not used either for address mapping nor for memory protection.
wdenkc6097192002-11-03 00:24:07 +00003512
wdenk2729af92004-05-03 20:45:30 +00003513The available memory is mapped to fixed addresses using the memory
3514controller. In this process, a contiguous block is formed for each
3515memory type (Flash, SDRAM, SRAM), even when it consists of several
3516physical memory banks.
wdenkc6097192002-11-03 00:24:07 +00003517
wdenk2729af92004-05-03 20:45:30 +00003518U-Boot is installed in the first 128 kB of the first Flash bank (on
3519TQM8xxL modules this is the range 0x40000000 ... 0x4001FFFF). After
3520booting and sizing and initializing DRAM, the code relocates itself
3521to the upper end of DRAM. Immediately below the U-Boot code some
3522memory is reserved for use by malloc() [see CFG_MALLOC_LEN
3523configuration setting]. Below that, a structure with global Board
3524Info data is placed, followed by the stack (growing downward).
wdenkc6097192002-11-03 00:24:07 +00003525
wdenk2729af92004-05-03 20:45:30 +00003526Additionally, some exception handler code is copied to the low 8 kB
3527of DRAM (0x00000000 ... 0x00001FFF).
wdenkc6097192002-11-03 00:24:07 +00003528
wdenk2729af92004-05-03 20:45:30 +00003529So a typical memory configuration with 16 MB of DRAM could look like
3530this:
wdenkc6097192002-11-03 00:24:07 +00003531
wdenk2729af92004-05-03 20:45:30 +00003532 0x0000 0000 Exception Vector code
3533 :
3534 0x0000 1FFF
3535 0x0000 2000 Free for Application Use
3536 :
3537 :
wdenkc6097192002-11-03 00:24:07 +00003538
wdenk2729af92004-05-03 20:45:30 +00003539 :
3540 :
3541 0x00FB FF20 Monitor Stack (Growing downward)
3542 0x00FB FFAC Board Info Data and permanent copy of global data
3543 0x00FC 0000 Malloc Arena
3544 :
3545 0x00FD FFFF
3546 0x00FE 0000 RAM Copy of Monitor Code
3547 ... eventually: LCD or video framebuffer
3548 ... eventually: pRAM (Protected RAM - unchanged by reset)
3549 0x00FF FFFF [End of RAM]
wdenkc6097192002-11-03 00:24:07 +00003550
3551
wdenk2729af92004-05-03 20:45:30 +00003552System Initialization:
3553----------------------
wdenkc6097192002-11-03 00:24:07 +00003554
wdenk2729af92004-05-03 20:45:30 +00003555In the reset configuration, U-Boot starts at the reset entry point
3556(on most PowerPC systens at address 0x00000100). Because of the reset
3557configuration for CS0# this is a mirror of the onboard Flash memory.
3558To be able to re-map memory U-Boot then jumps to its link address.
3559To be able to implement the initialization code in C, a (small!)
3560initial stack is set up in the internal Dual Ported RAM (in case CPUs
3561which provide such a feature like MPC8xx or MPC8260), or in a locked
3562part of the data cache. After that, U-Boot initializes the CPU core,
3563the caches and the SIU.
wdenkc6097192002-11-03 00:24:07 +00003564
wdenk2729af92004-05-03 20:45:30 +00003565Next, all (potentially) available memory banks are mapped using a
3566preliminary mapping. For example, we put them on 512 MB boundaries
3567(multiples of 0x20000000: SDRAM on 0x00000000 and 0x20000000, Flash
3568on 0x40000000 and 0x60000000, SRAM on 0x80000000). Then UPM A is
3569programmed for SDRAM access. Using the temporary configuration, a
3570simple memory test is run that determines the size of the SDRAM
3571banks.
wdenkc6097192002-11-03 00:24:07 +00003572
wdenk2729af92004-05-03 20:45:30 +00003573When there is more than one SDRAM bank, and the banks are of
3574different size, the largest is mapped first. For equal size, the first
3575bank (CS2#) is mapped first. The first mapping is always for address
35760x00000000, with any additional banks following immediately to create
3577contiguous memory starting from 0.
wdenkc6097192002-11-03 00:24:07 +00003578
wdenk2729af92004-05-03 20:45:30 +00003579Then, the monitor installs itself at the upper end of the SDRAM area
3580and allocates memory for use by malloc() and for the global Board
3581Info data; also, the exception vector code is copied to the low RAM
3582pages, and the final stack is set up.
wdenkc6097192002-11-03 00:24:07 +00003583
wdenk2729af92004-05-03 20:45:30 +00003584Only after this relocation will you have a "normal" C environment;
3585until that you are restricted in several ways, mostly because you are
3586running from ROM, and because the code will have to be relocated to a
3587new address in RAM.
wdenkc6097192002-11-03 00:24:07 +00003588
3589
wdenk2729af92004-05-03 20:45:30 +00003590U-Boot Porting Guide:
3591----------------------
wdenkc6097192002-11-03 00:24:07 +00003592
wdenk2729af92004-05-03 20:45:30 +00003593[Based on messages by Jerry Van Baren in the U-Boot-Users mailing
3594list, October 2002]
wdenkc6097192002-11-03 00:24:07 +00003595
3596
wdenk2729af92004-05-03 20:45:30 +00003597int main (int argc, char *argv[])
3598{
3599 sighandler_t no_more_time;
wdenkc6097192002-11-03 00:24:07 +00003600
wdenk2729af92004-05-03 20:45:30 +00003601 signal (SIGALRM, no_more_time);
3602 alarm (PROJECT_DEADLINE - toSec (3 * WEEK));
wdenkc6097192002-11-03 00:24:07 +00003603
wdenk2729af92004-05-03 20:45:30 +00003604 if (available_money > available_manpower) {
3605 pay consultant to port U-Boot;
wdenkc6097192002-11-03 00:24:07 +00003606 return 0;
3607 }
3608
wdenk2729af92004-05-03 20:45:30 +00003609 Download latest U-Boot source;
3610
3611 Subscribe to u-boot-users mailing list;
3612
3613 if (clueless) {
3614 email ("Hi, I am new to U-Boot, how do I get started?");
wdenkc6097192002-11-03 00:24:07 +00003615 }
3616
wdenk2729af92004-05-03 20:45:30 +00003617 while (learning) {
3618 Read the README file in the top level directory;
3619 Read http://www.denx.de/twiki/bin/view/DULG/Manual ;
3620 Read the source, Luke;
3621 }
wdenkc6097192002-11-03 00:24:07 +00003622
wdenk2729af92004-05-03 20:45:30 +00003623 if (available_money > toLocalCurrency ($2500)) {
3624 Buy a BDI2000;
3625 } else {
3626 Add a lot of aggravation and time;
3627 }
wdenkc6097192002-11-03 00:24:07 +00003628
wdenk2729af92004-05-03 20:45:30 +00003629 Create your own board support subdirectory;
wdenkc6097192002-11-03 00:24:07 +00003630
wdenk2729af92004-05-03 20:45:30 +00003631 Create your own board config file;
wdenk6aff3112002-12-17 01:51:00 +00003632
wdenk2729af92004-05-03 20:45:30 +00003633 while (!running) {
3634 do {
3635 Add / modify source code;
3636 } until (compiles);
3637 Debug;
3638 if (clueless)
3639 email ("Hi, I am having problems...");
3640 }
3641 Send patch file to Wolfgang;
wdenkc6097192002-11-03 00:24:07 +00003642
wdenk2729af92004-05-03 20:45:30 +00003643 return 0;
3644}
3645
3646void no_more_time (int sig)
3647{
3648 hire_a_guru();
3649}
wdenkc6097192002-11-03 00:24:07 +00003650
3651
wdenk2729af92004-05-03 20:45:30 +00003652Coding Standards:
3653-----------------
wdenkc6097192002-11-03 00:24:07 +00003654
wdenk2729af92004-05-03 20:45:30 +00003655All contributions to U-Boot should conform to the Linux kernel
Detlev Zundel2c051652006-09-01 15:39:02 +02003656coding style; see the file "Documentation/CodingStyle" and the script
3657"scripts/Lindent" in your Linux kernel source directory. In sources
3658originating from U-Boot a style corresponding to "Lindent -pcs" (adding
3659spaces before parameters to function calls) is actually used.
wdenk2729af92004-05-03 20:45:30 +00003660
Detlev Zundel2c051652006-09-01 15:39:02 +02003661Source files originating from a different project (for example the
3662MTD subsystem) are generally exempt from these guidelines and are not
3663reformated to ease subsequent migration to newer versions of those
3664sources.
3665
3666Please note that U-Boot is implemented in C (and to some small parts in
3667Assembler); no C++ is used, so please do not use C++ style comments (//)
3668in your code.
wdenk2729af92004-05-03 20:45:30 +00003669
3670Please also stick to the following formatting rules:
3671- remove any trailing white space
3672- use TAB characters for indentation, not spaces
3673- make sure NOT to use DOS '\r\n' line feeds
3674- do not add more than 2 empty lines to source files
3675- do not add trailing empty lines to source files
3676
3677Submissions which do not conform to the standards may be returned
3678with a request to reformat the changes.
wdenkc6097192002-11-03 00:24:07 +00003679
3680
wdenk2729af92004-05-03 20:45:30 +00003681Submitting Patches:
3682-------------------
wdenkc6097192002-11-03 00:24:07 +00003683
wdenk2729af92004-05-03 20:45:30 +00003684Since the number of patches for U-Boot is growing, we need to
3685establish some rules. Submissions which do not conform to these rules
3686may be rejected, even when they contain important and valuable stuff.
wdenkc6097192002-11-03 00:24:07 +00003687
wdenk90dc6702005-05-03 14:12:25 +00003688Patches shall be sent to the u-boot-users mailing list.
wdenkc6097192002-11-03 00:24:07 +00003689
wdenk2729af92004-05-03 20:45:30 +00003690When you send a patch, please include the following information with
3691it:
wdenkc6097192002-11-03 00:24:07 +00003692
wdenk2729af92004-05-03 20:45:30 +00003693* For bug fixes: a description of the bug and how your patch fixes
3694 this bug. Please try to include a way of demonstrating that the
3695 patch actually fixes something.
wdenkc6097192002-11-03 00:24:07 +00003696
wdenk2729af92004-05-03 20:45:30 +00003697* For new features: a description of the feature and your
3698 implementation.
wdenkc6097192002-11-03 00:24:07 +00003699
wdenk2729af92004-05-03 20:45:30 +00003700* A CHANGELOG entry as plaintext (separate from the patch)
3701
3702* For major contributions, your entry to the CREDITS file
3703
3704* When you add support for a new board, don't forget to add this
3705 board to the MAKEALL script, too.
3706
3707* If your patch adds new configuration options, don't forget to
3708 document these in the README file.
3709
3710* The patch itself. If you are accessing the CVS repository use "cvs
3711 update; cvs diff -puRN"; else, use "diff -purN OLD NEW". If your
3712 version of diff does not support these options, then get the latest
3713 version of GNU diff.
3714
3715 The current directory when running this command shall be the top
3716 level directory of the U-Boot source tree, or it's parent directory
3717 (i. e. please make sure that your patch includes sufficient
3718 directory information for the affected files).
3719
3720 We accept patches as plain text, MIME attachments or as uuencoded
3721 gzipped text.
3722
3723* If one logical set of modifications affects or creates several
3724 files, all these changes shall be submitted in a SINGLE patch file.
3725
3726* Changesets that contain different, unrelated modifications shall be
3727 submitted as SEPARATE patches, one patch per changeset.
3728
3729
3730Notes:
3731
3732* Before sending the patch, run the MAKEALL script on your patched
3733 source tree and make sure that no errors or warnings are reported
3734 for any of the boards.
3735
3736* Keep your modifications to the necessary minimum: A patch
3737 containing several unrelated changes or arbitrary reformats will be
3738 returned with a request to re-formatting / split it.
3739
3740* If you modify existing code, make sure that your new code does not
3741 add to the memory footprint of the code ;-) Small is beautiful!
3742 When adding new features, these should compile conditionally only
3743 (using #ifdef), and the resulting code with the new feature
3744 disabled must not need more memory than the old code without your
3745 modification.
wdenk90dc6702005-05-03 14:12:25 +00003746
3747* Remember that there is a size limit of 40 kB per message on the
3748 u-boot-users mailing list. Compression may help.