blob: cdf3f55590794c9f1ba1bd7394db04b877c3c95d [file] [log] [blame]
wdenkc6097192002-11-03 00:24:07 +00001#
2# (C) Copyright 2000 - 2002
3# 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
28Embedded boards based on PowerPC and ARM processors, which can be
29installed in a boot ROM and used to initialize and test the hardware
30or to download and run application code.
wdenkc6097192002-11-03 00:24:07 +000031
32The development of U-Boot is closely related to Linux: some parts of
wdenk24ee89b2002-11-03 17:56:27 +000033the source code originate in the Linux source tree, we have some
34header files in common, and special provision has been made to
wdenkc6097192002-11-03 00:24:07 +000035support booting of Linux images.
36
37Some attention has been paid to make this software easily
38configurable and extendable. For instance, all monitor commands are
39implemented with the same call interface, so that it's very easy to
40add new commands. Also, instead of permanently adding rarely used
41code (for instance hardware test utilities) to the monitor, you can
42load and run it dynamically.
43
44
45Status:
46=======
47
48In general, all boards for which a configuration option exists in the
wdenk24ee89b2002-11-03 17:56:27 +000049Makefile have been tested to some extent and can be considered
wdenkc6097192002-11-03 00:24:07 +000050"working". In fact, many of them are used in production systems.
51
wdenk24ee89b2002-11-03 17:56:27 +000052In case of problems see the CHANGELOG and CREDITS files to find out
wdenkc6097192002-11-03 00:24:07 +000053who contributed the specific port.
54
wdenkc6097192002-11-03 00:24:07 +000055
56Where to get help:
57==================
58
wdenk24ee89b2002-11-03 17:56:27 +000059In case you have questions about, problems with or contributions for
60U-Boot you should send a message to the U-Boot mailing list at
61<u-boot-users@lists.sourceforge.net>. There is also an archive of
62previous traffic on the mailing list - please search the archive
wdenkc6097192002-11-03 00:24:07 +000063before asking FAQ's. Please see
64http://lists.sourceforge.net/lists/listinfo/u-boot-users/
65
66
67Where we come from:
68===================
69
70- start from 8xxrom sources
wdenk24ee89b2002-11-03 17:56:27 +000071- create PPCBoot project (http://sourceforge.net/projects/ppcboot)
wdenkc6097192002-11-03 00:24:07 +000072- clean up code
73- make it easier to add custom boards
74- make it possible to add other [PowerPC] CPUs
75- extend functions, especially:
76 * Provide extended interface to Linux boot loader
77 * S-Record download
78 * network boot
79 * PCMCIA / CompactFLash / ATA disk / SCSI ... boot
wdenk24ee89b2002-11-03 17:56:27 +000080- create ARMBoot project (http://sourceforge.net/projects/armboot)
wdenkc6097192002-11-03 00:24:07 +000081- add other CPU families (starting with ARM)
wdenk24ee89b2002-11-03 17:56:27 +000082- create U-Boot project (http://sourceforge.net/projects/u-boot)
83
84
85Names and Spelling:
86===================
87
88The "official" name of this project is "Das U-Boot". The spelling
89"U-Boot" shall be used in all written text (documentation, comments
90in source files etc.). Example:
91
92 This is the README file for the U-Boot project.
93
94File names etc. shall be based on the string "u-boot". Examples:
95
96 include/asm-ppc/u-boot.h
97
98 #include <asm/u-boot.h>
99
100Variable names, preprocessor constants etc. shall be either based on
101the string "u_boot" or on "U_BOOT". Example:
102
103 U_BOOT_VERSION u_boot_logo
104 IH_OS_U_BOOT u_boot_hush_start
wdenkc6097192002-11-03 00:24:07 +0000105
106
wdenk93f19cc2002-12-17 17:55:09 +0000107Versioning:
108===========
109
110U-Boot uses a 3 level version number containing a version, a
111sub-version, and a patchlevel: "U-Boot-2.34.5" means version "2",
112sub-version "34", and patchlevel "4".
113
114The patchlevel is used to indicate certain stages of development
115between released versions, i. e. officially released versions of
116U-Boot will always have a patchlevel of "0".
117
118
wdenkc6097192002-11-03 00:24:07 +0000119Directory Hierarchy:
120====================
121
wdenk7152b1d2003-09-05 23:19:14 +0000122- board Board dependent files
123- common Misc architecture independent functions
wdenkc6097192002-11-03 00:24:07 +0000124- cpu CPU specific files
125- disk Code for disk drive partition handling
126- doc Documentation (don't expect too much)
wdenk7152b1d2003-09-05 23:19:14 +0000127- drivers Commonly used device drivers
wdenkc6097192002-11-03 00:24:07 +0000128- dtt Digital Thermometer and Thermostat drivers
129- examples Example code for standalone applications, etc.
130- include Header Files
131- disk Harddisk interface code
132- net Networking code
133- ppc Files generic to PowerPC architecture
134- post Power On Self Test
135- post/arch Symlink to architecture specific Power On Self Test
136- post/arch-ppc PowerPC architecture specific Power On Self Test
137- post/cpu/mpc8260 MPC8260 CPU specific Power On Self Test
138- post/cpu/mpc8xx MPC8xx CPU specific Power On Self Test
139- rtc Real Time Clock drivers
140- tools Tools to build S-Record or U-Boot images, etc.
141
142- cpu/74xx_7xx Files specific to Motorola MPC74xx and 7xx CPUs
wdenk2e5983d2003-07-15 20:04:06 +0000143- cpu/arm925t Files specific to ARM 925 CPUs
wdenk6f213472003-08-29 22:00:43 +0000144- cpu/arm926ejs Files specific to ARM 926 CPUs
wdenk0db5bca2003-03-31 17:27:09 +0000145- cpu/mpc5xx Files specific to Motorola MPC5xx CPUs
wdenkc6097192002-11-03 00:24:07 +0000146- cpu/mpc8xx Files specific to Motorola MPC8xx CPUs
147- cpu/mpc824x Files specific to Motorola MPC824x CPUs
148- cpu/mpc8260 Files specific to Motorola MPC8260 CPU
wdenk42d1f032003-10-15 23:53:47 +0000149- cpu/mpc85xx Files specific to Motorola MPC85xx CPUs
wdenkc6097192002-11-03 00:24:07 +0000150- cpu/ppc4xx Files specific to IBM 4xx CPUs
151
wdenk2e5983d2003-07-15 20:04:06 +0000152
wdenk3bac3512003-03-12 10:41:04 +0000153- board/LEOX/ Files specific to boards manufactured by The LEOX team
154- board/LEOX/elpt860 Files specific to ELPT860 boards
wdenkc6097192002-11-03 00:24:07 +0000155- board/RPXClassic
156 Files specific to RPXClassic boards
157- board/RPXlite Files specific to RPXlite boards
wdenk2abbe072003-06-16 23:50:08 +0000158- board/at91rm9200dk Files specific to AT91RM9200DK boards
wdenkc6097192002-11-03 00:24:07 +0000159- board/c2mon Files specific to c2mon boards
wdenk0db5bca2003-03-31 17:27:09 +0000160- board/cmi Files specific to cmi boards
wdenkc6097192002-11-03 00:24:07 +0000161- board/cogent Files specific to Cogent boards
162 (need further configuration)
163 Files specific to CPCIISER4 boards
164- board/cpu86 Files specific to CPU86 boards
165- board/cray/ Files specific to boards manufactured by Cray
166- board/cray/L1 Files specific to L1 boards
167- board/cu824 Files specific to CU824 boards
168- board/ebony Files specific to IBM Ebony board
169- board/eric Files specific to ERIC boards
170- board/esd/ Files specific to boards manufactured by ESD
171- board/esd/adciop Files specific to ADCIOP boards
172- board/esd/ar405 Files specific to AR405 boards
173- board/esd/canbt Files specific to CANBT boards
174- board/esd/cpci405 Files specific to CPCI405 boards
175- board/esd/cpciiser4 Files specific to CPCIISER4 boards
176- board/esd/common Common files for ESD boards
177- board/esd/dasa_sim Files specific to DASA_SIM boards
178- board/esd/du405 Files specific to DU405 boards
179- board/esd/ocrtc Files specific to OCRTC boards
180- board/esd/pci405 Files specific to PCI405 boards
181- board/esteem192e
182 Files specific to ESTEEM192E boards
183- board/etx094 Files specific to ETX_094 boards
184- board/evb64260
185 Files specific to EVB64260 boards
186- board/fads Files specific to FADS boards
187- board/flagadm Files specific to FLAGADM boards
wdenk7aa78612003-05-03 15:50:43 +0000188- board/gen860t Files specific to GEN860T and GEN860T_SC boards
wdenkc6097192002-11-03 00:24:07 +0000189- board/genietv Files specific to GENIETV boards
190- board/gth Files specific to GTH boards
191- board/hermes Files specific to HERMES boards
192- board/hymod Files specific to HYMOD boards
193- board/icu862 Files specific to ICU862 boards
194- board/ip860 Files specific to IP860 boards
195- board/iphase4539
196 Files specific to Interphase4539 boards
197- board/ivm Files specific to IVMS8/IVML24 boards
198- board/lantec Files specific to LANTEC boards
199- board/lwmon Files specific to LWMON boards
200- board/mbx8xx Files specific to MBX boards
201- board/mpc8260ads
wdenk2535d602003-07-17 23:16:40 +0000202 Files specific to MPC8260ADS and PQ2FADS-ZU boards
wdenk42d1f032003-10-15 23:53:47 +0000203- board/mpc8540ads
204 Files specific to MPC8540ADS boards
205- board/mpc8560ads
206 Files specific to MPC8560ADS boards
wdenkc6097192002-11-03 00:24:07 +0000207- board/mpl/ Files specific to boards manufactured by MPL
208- board/mpl/common Common files for MPL boards
209- board/mpl/pip405 Files specific to PIP405 boards
210- board/mpl/mip405 Files specific to MIP405 boards
wdenk531716e2003-09-13 19:01:12 +0000211- board/mpl/vcma9 Files specific to VCMA9 boards
wdenkc6097192002-11-03 00:24:07 +0000212- board/musenki Files specific to MUSEKNI boards
213- board/mvs1 Files specific to MVS1 boards
214- board/nx823 Files specific to NX823 boards
215- board/oxc Files specific to OXC boards
wdenk945af8d2003-07-16 21:53:01 +0000216- board/omap1510inn
wdenk2e5983d2003-07-15 20:04:06 +0000217 Files specific to OMAP 1510 Innovator boards
wdenk42d1f032003-10-15 23:53:47 +0000218- board/omap1610inn
wdenk6f213472003-08-29 22:00:43 +0000219 Files specific to OMAP 1610 Innovator boards
wdenkc6097192002-11-03 00:24:07 +0000220- board/pcippc2 Files specific to PCIPPC2/PCIPPC6 boards
221- board/pm826 Files specific to PM826 boards
222- board/ppmc8260
223 Files specific to PPMC8260 boards
224- board/rpxsuper
225 Files specific to RPXsuper boards
226- board/rsdproto
227 Files specific to RSDproto boards
228- board/sandpoint
229 Files specific to Sandpoint boards
230- board/sbc8260 Files specific to SBC8260 boards
231- board/sacsng Files specific to SACSng boards
232- board/siemens Files specific to boards manufactured by Siemens AG
233- board/siemens/CCM Files specific to CCM boards
234- board/siemens/IAD210 Files specific to IAD210 boards
235- board/siemens/SCM Files specific to SCM boards
236- board/siemens/pcu_e Files specific to PCU_E boards
237- board/sixnet Files specific to SIXNET boards
238- board/spd8xx Files specific to SPD8xxTS boards
239- board/tqm8260 Files specific to TQM8260 boards
240- board/tqm8xx Files specific to TQM8xxL boards
241- board/w7o Files specific to W7O boards
242- board/walnut405
243 Files specific to Walnut405 boards
244- board/westel/ Files specific to boards manufactured by Westel Wireless
245- board/westel/amx860 Files specific to AMX860 boards
246- board/utx8245 Files specific to UTX8245 boards
wdenk54387ac2003-10-08 22:45:44 +0000247- board/zpc1900 Files specific to Zephyr Engineering ZPC.1900 board
wdenkc6097192002-11-03 00:24:07 +0000248
249Software Configuration:
250=======================
251
252Configuration is usually done using C preprocessor defines; the
253rationale behind that is to avoid dead code whenever possible.
254
255There are two classes of configuration variables:
256
257* Configuration _OPTIONS_:
258 These are selectable by the user and have names beginning with
259 "CONFIG_".
260
261* Configuration _SETTINGS_:
262 These depend on the hardware etc. and should not be meddled with if
263 you don't know what you're doing; they have names beginning with
264 "CFG_".
265
266Later we will add a configuration tool - probably similar to or even
267identical to what's used for the Linux kernel. Right now, we have to
268do the configuration by hand, which means creating some symbolic
269links and editing some configuration files. We use the TQM8xxL boards
270as an example here.
271
272
273Selection of Processor Architecture and Board Type:
274---------------------------------------------------
275
276For all supported boards there are ready-to-use default
277configurations available; just type "make <board_name>_config".
278
279Example: For a TQM823L module type:
280
281 cd u-boot
282 make TQM823L_config
283
284For the Cogent platform, you need to specify the cpu type as well;
285e.g. "make cogent_mpc8xx_config". And also configure the cogent
286directory according to the instructions in cogent/README.
287
288
289Configuration Options:
290----------------------
291
292Configuration depends on the combination of board and CPU type; all
293such information is kept in a configuration file
294"include/configs/<board_name>.h".
295
296Example: For a TQM823L module, all configuration settings are in
297"include/configs/TQM823L.h".
298
299
wdenk7f6c2cb2002-11-10 22:06:23 +0000300Many of the options are named exactly as the corresponding Linux
301kernel configuration options. The intention is to make it easier to
302build a config tool - later.
303
304
wdenkc6097192002-11-03 00:24:07 +0000305The following options need to be configured:
306
307- CPU Type: Define exactly one of
308
309 PowerPC based CPUs:
310 -------------------
311 CONFIG_MPC823, CONFIG_MPC850, CONFIG_MPC855, CONFIG_MPC860
wdenk0db5bca2003-03-31 17:27:09 +0000312 or CONFIG_MPC5xx
wdenkc6097192002-11-03 00:24:07 +0000313 or CONFIG_MPC824X, CONFIG_MPC8260
wdenk42d1f032003-10-15 23:53:47 +0000314 or CONFIG_MPC85xx
wdenkc6097192002-11-03 00:24:07 +0000315 or CONFIG_IOP480
316 or CONFIG_405GP
wdenk12f34242003-09-02 22:48:03 +0000317 or CONFIG_405EP
wdenkc6097192002-11-03 00:24:07 +0000318 or CONFIG_440
319 or CONFIG_MPC74xx
wdenk72755c72003-06-20 23:10:58 +0000320 or CONFIG_750FX
wdenkc6097192002-11-03 00:24:07 +0000321
322 ARM based CPUs:
323 ---------------
324 CONFIG_SA1110
325 CONFIG_ARM7
326 CONFIG_PXA250
327
328
329- Board Type: Define exactly one of
330
331 PowerPC based boards:
332 ---------------------
333
334 CONFIG_ADCIOP, CONFIG_ICU862 CONFIG_RPXsuper,
335 CONFIG_ADS860, CONFIG_IP860, CONFIG_SM850,
336 CONFIG_AMX860, CONFIG_IPHASE4539, CONFIG_SPD823TS,
337 CONFIG_AR405, CONFIG_IVML24, CONFIG_SXNI855T,
338 CONFIG_BAB7xx, CONFIG_IVML24_128, CONFIG_Sandpoint8240,
339 CONFIG_CANBT, CONFIG_IVML24_256, CONFIG_Sandpoint8245,
340 CONFIG_CCM, CONFIG_IVMS8, CONFIG_TQM823L,
341 CONFIG_CPCI405, CONFIG_IVMS8_128, CONFIG_TQM850L,
342 CONFIG_CPCI4052, CONFIG_IVMS8_256, CONFIG_TQM855L,
343 CONFIG_CPCIISER4, CONFIG_LANTEC, CONFIG_TQM860L,
344 CONFIG_CPU86, CONFIG_MBX, CONFIG_TQM8260,
345 CONFIG_CRAYL1, CONFIG_MBX860T, CONFIG_TTTech,
346 CONFIG_CU824, CONFIG_MHPC, CONFIG_UTX8245,
347 CONFIG_DASA_SIM, CONFIG_MIP405, CONFIG_W7OLMC,
348 CONFIG_DU405, CONFIG_MOUSSE, CONFIG_W7OLMG,
349 CONFIG_ELPPC, CONFIG_MPC8260ADS, CONFIG_WALNUT405,
350 CONFIG_ERIC, CONFIG_MUSENKI, CONFIG_ZUMA,
351 CONFIG_ESTEEM192E, CONFIG_MVS1, CONFIG_c2mon,
352 CONFIG_ETX094, CONFIG_NX823, CONFIG_cogent_mpc8260,
353 CONFIG_EVB64260, CONFIG_OCRTC, CONFIG_cogent_mpc8xx,
354 CONFIG_FADS823, CONFIG_ORSG, CONFIG_ep8260,
355 CONFIG_FADS850SAR, CONFIG_OXC, CONFIG_gw8260,
356 CONFIG_FADS860T, CONFIG_PCI405, CONFIG_hermes,
357 CONFIG_FLAGADM, CONFIG_PCIPPC2, CONFIG_hymod,
358 CONFIG_FPS850L, CONFIG_PCIPPC6, CONFIG_lwmon,
359 CONFIG_GEN860T, CONFIG_PIP405, CONFIG_pcu_e,
360 CONFIG_GENIETV, CONFIG_PM826, CONFIG_ppmc8260,
361 CONFIG_GTH, CONFIG_RPXClassic, CONFIG_rsdproto,
362 CONFIG_IAD210, CONFIG_RPXlite, CONFIG_sbc8260,
wdenk608c9142003-01-13 23:54:46 +0000363 CONFIG_EBONY, CONFIG_sacsng, CONFIG_FPS860L,
wdenk7f70e852003-05-20 14:25:27 +0000364 CONFIG_V37, CONFIG_ELPT860, CONFIG_CMI,
wdenk42d1f032003-10-15 23:53:47 +0000365 CONFIG_NETVIA, CONFIG_RBC823, CONFIG_ZPC1900,
366 CONFIG_MPC8540ADS, CONFIG_MPC8560ADS
wdenkc6097192002-11-03 00:24:07 +0000367
368 ARM based boards:
369 -----------------
370
371 CONFIG_HHP_CRADLE, CONFIG_DNP1110, CONFIG_EP7312,
372 CONFIG_IMPA7, CONFIG_LART, CONFIG_LUBBOCK,
wdenk6f213472003-08-29 22:00:43 +0000373 CONFIG_INNOVATOROMAP1510, CONFIG_INNOVATOROMAP1610
wdenkc6097192002-11-03 00:24:07 +0000374 CONFIG_SHANNON, CONFIG_SMDK2400, CONFIG_SMDK2410,
wdenk531716e2003-09-13 19:01:12 +0000375 CONFIG_TRAB, CONFIG_VCMA9, CONFIG_AT91RM9200DK
wdenkc6097192002-11-03 00:24:07 +0000376
377
378- CPU Module Type: (if CONFIG_COGENT is defined)
379 Define exactly one of
380 CONFIG_CMA286_60_OLD
381--- FIXME --- not tested yet:
382 CONFIG_CMA286_60, CONFIG_CMA286_21, CONFIG_CMA286_60P,
383 CONFIG_CMA287_23, CONFIG_CMA287_50
384
385- Motherboard Type: (if CONFIG_COGENT is defined)
386 Define exactly one of
387 CONFIG_CMA101, CONFIG_CMA102
388
389- Motherboard I/O Modules: (if CONFIG_COGENT is defined)
390 Define one or more of
391 CONFIG_CMA302
392
393- Motherboard Options: (if CONFIG_CMA101 or CONFIG_CMA102 are defined)
394 Define one or more of
395 CONFIG_LCD_HEARTBEAT - update a character position on
396 the lcd display every second with
397 a "rotator" |\-/|\-/
398
wdenk2535d602003-07-17 23:16:40 +0000399- Board flavour: (if CONFIG_MPC8260ADS is defined)
400 CONFIG_ADSTYPE
401 Possible values are:
402 CFG_8260ADS - original MPC8260ADS
403 CFG_8266ADS - MPC8266ADS (untested)
wdenk54387ac2003-10-08 22:45:44 +0000404 CFG_PQ2FADS - PQ2FADS-ZU or PQ2FADS-VR
wdenk2535d602003-07-17 23:16:40 +0000405
406
wdenkc6097192002-11-03 00:24:07 +0000407- MPC824X Family Member (if CONFIG_MPC824X is defined)
wdenk5da627a2003-10-09 20:09:04 +0000408 Define exactly one of
409 CONFIG_MPC8240, CONFIG_MPC8245
wdenkc6097192002-11-03 00:24:07 +0000410
411- 8xx CPU Options: (if using an 8xx cpu)
412 Define one or more of
wdenk5da627a2003-10-09 20:09:04 +0000413 CONFIG_8xx_GCLK_FREQ - if get_gclk_freq() cannot work
414 e.g. if there is no 32KHz
415 reference PIT/RTC clock
wdenkc6097192002-11-03 00:24:07 +0000416
wdenk5da627a2003-10-09 20:09:04 +0000417- Linux Kernel Interface:
wdenkc6097192002-11-03 00:24:07 +0000418 CONFIG_CLOCKS_IN_MHZ
419
420 U-Boot stores all clock information in Hz
421 internally. For binary compatibility with older Linux
422 kernels (which expect the clocks passed in the
423 bd_info data to be in MHz) the environment variable
424 "clocks_in_mhz" can be defined so that U-Boot
425 converts clock data to MHZ before passing it to the
426 Linux kernel.
wdenkc6097192002-11-03 00:24:07 +0000427 When CONFIG_CLOCKS_IN_MHZ is defined, a definition of
428 "clocks_in_mhz=1" is automatically included in the
429 default environment.
430
wdenk5da627a2003-10-09 20:09:04 +0000431 CONFIG_MEMSIZE_IN_BYTES [relevant for MIPS only]
432
433 When transfering memsize parameter to linux, some versions
434 expect it to be in bytes, others in MB.
435 Define CONFIG_MEMSIZE_IN_BYTES to make it in bytes.
436
wdenkc6097192002-11-03 00:24:07 +0000437- Console Interface:
wdenk43d96162003-03-06 00:02:04 +0000438 Depending on board, define exactly one serial port
439 (like CONFIG_8xx_CONS_SMC1, CONFIG_8xx_CONS_SMC2,
440 CONFIG_8xx_CONS_SCC1, ...), or switch off the serial
441 console by defining CONFIG_8xx_CONS_NONE
wdenkc6097192002-11-03 00:24:07 +0000442
443 Note: if CONFIG_8xx_CONS_NONE is defined, the serial
444 port routines must be defined elsewhere
445 (i.e. serial_init(), serial_getc(), ...)
446
447 CONFIG_CFB_CONSOLE
448 Enables console device for a color framebuffer. Needs following
449 defines (cf. smiLynxEM, i8042, board/eltec/bab7xx)
450 VIDEO_FB_LITTLE_ENDIAN graphic memory organisation
451 (default big endian)
452 VIDEO_HW_RECTFILL graphic chip supports
453 rectangle fill
454 (cf. smiLynxEM)
455 VIDEO_HW_BITBLT graphic chip supports
456 bit-blit (cf. smiLynxEM)
457 VIDEO_VISIBLE_COLS visible pixel columns
458 (cols=pitch)
459 VIDEO_VISIBLE_ROWS visible pixel rows
460 VIDEO_PIXEL_SIZE bytes per pixel
461 VIDEO_DATA_FORMAT graphic data format
462 (0-5, cf. cfb_console.c)
463 VIDEO_FB_ADRS framebuffer address
464 VIDEO_KBD_INIT_FCT keyboard int fct
465 (i.e. i8042_kbd_init())
466 VIDEO_TSTC_FCT test char fct
467 (i.e. i8042_tstc)
468 VIDEO_GETC_FCT get char fct
469 (i.e. i8042_getc)
470 CONFIG_CONSOLE_CURSOR cursor drawing on/off
471 (requires blink timer
472 cf. i8042.c)
473 CFG_CONSOLE_BLINK_COUNT blink interval (cf. i8042.c)
474 CONFIG_CONSOLE_TIME display time/date info in
475 upper right corner
476 (requires CFG_CMD_DATE)
477 CONFIG_VIDEO_LOGO display Linux logo in
478 upper left corner
wdenka6c7ad22002-12-03 21:28:10 +0000479 CONFIG_VIDEO_BMP_LOGO use bmp_logo.h instead of
480 linux_logo.h for logo.
481 Requires CONFIG_VIDEO_LOGO
wdenkc6097192002-11-03 00:24:07 +0000482 CONFIG_CONSOLE_EXTRA_INFO
483 addional board info beside
484 the logo
485
wdenk43d96162003-03-06 00:02:04 +0000486 When CONFIG_CFB_CONSOLE is defined, video console is
487 default i/o. Serial console can be forced with
488 environment 'console=serial'.
wdenkc6097192002-11-03 00:24:07 +0000489
wdenka3ad8e22003-10-19 23:22:11 +0000490 When CONFIG_SILENT_CONSOLE is defined, all console
491 messages (by U-Boot and Linux!) can be silenced with
492 the "silent" environment variable. See
493 doc/README.silent for more information.
494
wdenkc6097192002-11-03 00:24:07 +0000495- Console Baudrate:
496 CONFIG_BAUDRATE - in bps
497 Select one of the baudrates listed in
498 CFG_BAUDRATE_TABLE, see below.
499
500- Interrupt driven serial port input:
501 CONFIG_SERIAL_SOFTWARE_FIFO
502
503 PPC405GP only.
504 Use an interrupt handler for receiving data on the
505 serial port. It also enables using hardware handshake
506 (RTS/CTS) and UART's built-in FIFO. Set the number of
507 bytes the interrupt driven input buffer should have.
508
509 Set to 0 to disable this feature (this is the default).
510 This will also disable hardware handshake.
511
stroese1d49b1f2003-05-23 11:39:05 +0000512- Console UART Number:
513 CONFIG_UART1_CONSOLE
514
515 IBM PPC4xx only.
516 If defined internal UART1 (and not UART0) is used
517 as default U-Boot console.
518
wdenkc6097192002-11-03 00:24:07 +0000519- Boot Delay: CONFIG_BOOTDELAY - in seconds
520 Delay before automatically booting the default image;
521 set to -1 to disable autoboot.
522
523 See doc/README.autoboot for these options that
524 work with CONFIG_BOOTDELAY. None are required.
525 CONFIG_BOOT_RETRY_TIME
526 CONFIG_BOOT_RETRY_MIN
527 CONFIG_AUTOBOOT_KEYED
528 CONFIG_AUTOBOOT_PROMPT
529 CONFIG_AUTOBOOT_DELAY_STR
530 CONFIG_AUTOBOOT_STOP_STR
531 CONFIG_AUTOBOOT_DELAY_STR2
532 CONFIG_AUTOBOOT_STOP_STR2
533 CONFIG_ZERO_BOOTDELAY_CHECK
534 CONFIG_RESET_TO_RETRY
535
536- Autoboot Command:
537 CONFIG_BOOTCOMMAND
538 Only needed when CONFIG_BOOTDELAY is enabled;
539 define a command string that is automatically executed
540 when no character is read on the console interface
541 within "Boot Delay" after reset.
542
543 CONFIG_BOOTARGS
wdenk43d96162003-03-06 00:02:04 +0000544 This can be used to pass arguments to the bootm
545 command. The value of CONFIG_BOOTARGS goes into the
546 environment value "bootargs".
wdenkc6097192002-11-03 00:24:07 +0000547
548 CONFIG_RAMBOOT and CONFIG_NFSBOOT
wdenk43d96162003-03-06 00:02:04 +0000549 The value of these goes into the environment as
550 "ramboot" and "nfsboot" respectively, and can be used
551 as a convenience, when switching between booting from
552 ram and nfs.
wdenkc6097192002-11-03 00:24:07 +0000553
554- Pre-Boot Commands:
555 CONFIG_PREBOOT
556
557 When this option is #defined, the existence of the
558 environment variable "preboot" will be checked
559 immediately before starting the CONFIG_BOOTDELAY
560 countdown and/or running the auto-boot command resp.
561 entering interactive mode.
562
563 This feature is especially useful when "preboot" is
564 automatically generated or modified. For an example
565 see the LWMON board specific code: here "preboot" is
566 modified when the user holds down a certain
567 combination of keys on the (special) keyboard when
568 booting the systems
569
570- Serial Download Echo Mode:
571 CONFIG_LOADS_ECHO
572 If defined to 1, all characters received during a
573 serial download (using the "loads" command) are
574 echoed back. This might be needed by some terminal
575 emulations (like "cu"), but may as well just take
576 time on others. This setting #define's the initial
577 value of the "loads_echo" environment variable.
578
579- Kgdb Serial Baudrate: (if CFG_CMD_KGDB is defined)
580 CONFIG_KGDB_BAUDRATE
581 Select one of the baudrates listed in
582 CFG_BAUDRATE_TABLE, see below.
583
584- Monitor Functions:
585 CONFIG_COMMANDS
586 Most monitor functions can be selected (or
587 de-selected) by adjusting the definition of
588 CONFIG_COMMANDS; to select individual functions,
589 #define CONFIG_COMMANDS by "OR"ing any of the
590 following values:
591
592 #define enables commands:
593 -------------------------
594 CFG_CMD_ASKENV * ask for env variable
wdenk78137c32003-09-15 18:00:00 +0000595 CFG_CMD_AUTOSCRIPT Autoscript Support
wdenkc6097192002-11-03 00:24:07 +0000596 CFG_CMD_BDI bdinfo
597 CFG_CMD_BEDBUG Include BedBug Debugger
wdenk78137c32003-09-15 18:00:00 +0000598 CFG_CMD_BMP * BMP support
wdenkc6097192002-11-03 00:24:07 +0000599 CFG_CMD_BOOTD bootd
600 CFG_CMD_CACHE icache, dcache
601 CFG_CMD_CONSOLE coninfo
602 CFG_CMD_DATE * support for RTC, date/time...
603 CFG_CMD_DHCP DHCP support
wdenk78137c32003-09-15 18:00:00 +0000604 CFG_CMD_DIAG * Diagnostics
605 CFG_CMD_DOC * Disk-On-Chip Support
wdenk42d1f032003-10-15 23:53:47 +0000606 CFG_CMD_DTT Digital Therm and Thermostat
wdenkc6097192002-11-03 00:24:07 +0000607 CFG_CMD_ECHO * echo arguments
608 CFG_CMD_EEPROM * EEPROM read/write support
609 CFG_CMD_ELF bootelf, bootvx
610 CFG_CMD_ENV saveenv
611 CFG_CMD_FDC * Floppy Disk Support
wdenk71f95112003-06-15 22:40:42 +0000612 CFG_CMD_FAT FAT partition support
wdenk2262cfe2002-11-18 00:14:45 +0000613 CFG_CMD_FDOS * Dos diskette Support
wdenkc6097192002-11-03 00:24:07 +0000614 CFG_CMD_FLASH flinfo, erase, protect
615 CFG_CMD_FPGA FPGA device initialization support
wdenk78137c32003-09-15 18:00:00 +0000616 CFG_CMD_HWFLOW * RTS/CTS hw flow control
wdenkc6097192002-11-03 00:24:07 +0000617 CFG_CMD_I2C * I2C serial bus support
618 CFG_CMD_IDE * IDE harddisk support
619 CFG_CMD_IMI iminfo
wdenk78137c32003-09-15 18:00:00 +0000620 CFG_CMD_IMLS List all found images
wdenkc6097192002-11-03 00:24:07 +0000621 CFG_CMD_IMMAP * IMMR dump support
622 CFG_CMD_IRQ * irqinfo
wdenk78137c32003-09-15 18:00:00 +0000623 CFG_CMD_JFFS2 * JFFS2 Support
wdenkc6097192002-11-03 00:24:07 +0000624 CFG_CMD_KGDB * kgdb
625 CFG_CMD_LOADB loadb
626 CFG_CMD_LOADS loads
627 CFG_CMD_MEMORY md, mm, nm, mw, cp, cmp, crc, base,
628 loop, mtest
wdenk78137c32003-09-15 18:00:00 +0000629 CFG_CMD_MISC Misc functions like sleep etc
wdenk71f95112003-06-15 22:40:42 +0000630 CFG_CMD_MMC MMC memory mapped support
wdenkc6097192002-11-03 00:24:07 +0000631 CFG_CMD_MII MII utility commands
wdenk78137c32003-09-15 18:00:00 +0000632 CFG_CMD_NAND * NAND support
wdenkc6097192002-11-03 00:24:07 +0000633 CFG_CMD_NET bootp, tftpboot, rarpboot
634 CFG_CMD_PCI * pciinfo
635 CFG_CMD_PCMCIA * PCMCIA support
wdenk78137c32003-09-15 18:00:00 +0000636 CFG_CMD_PING * send ICMP ECHO_REQUEST to network host
637 CFG_CMD_PORTIO Port I/O
wdenkc6097192002-11-03 00:24:07 +0000638 CFG_CMD_REGINFO * Register dump
639 CFG_CMD_RUN run command in env variable
wdenk78137c32003-09-15 18:00:00 +0000640 CFG_CMD_SAVES save S record dump
wdenkc6097192002-11-03 00:24:07 +0000641 CFG_CMD_SCSI * SCSI Support
wdenk78137c32003-09-15 18:00:00 +0000642 CFG_CMD_SDRAM * print SDRAM configuration information
wdenkc6097192002-11-03 00:24:07 +0000643 CFG_CMD_SETGETDCR Support for DCR Register access (4xx only)
644 CFG_CMD_SPI * SPI serial bus support
645 CFG_CMD_USB * USB support
wdenk78137c32003-09-15 18:00:00 +0000646 CFG_CMD_VFD * VFD support (TRAB)
wdenkc6097192002-11-03 00:24:07 +0000647 CFG_CMD_BSP * Board SPecific functions
648 -----------------------------------------------
649 CFG_CMD_ALL all
650
651 CFG_CMD_DFL Default configuration; at the moment
652 this is includes all commands, except
653 the ones marked with "*" in the list
654 above.
655
656 If you don't define CONFIG_COMMANDS it defaults to
657 CFG_CMD_DFL in include/cmd_confdefs.h. A board can
658 override the default settings in the respective
659 include file.
660
661 EXAMPLE: If you want all functions except of network
662 support you can write:
663
664 #define CONFIG_COMMANDS (CFG_CMD_ALL & ~CFG_CMD_NET)
665
666
667 Note: Don't enable the "icache" and "dcache" commands
wdenk43d96162003-03-06 00:02:04 +0000668 (configuration option CFG_CMD_CACHE) unless you know
669 what you (and your U-Boot users) are doing. Data
670 cache cannot be enabled on systems like the 8xx or
671 8260 (where accesses to the IMMR region must be
672 uncached), and it cannot be disabled on all other
673 systems where we (mis-) use the data cache to hold an
674 initial stack and some data.
wdenkc6097192002-11-03 00:24:07 +0000675
676
677 XXX - this list needs to get updated!
678
679- Watchdog:
680 CONFIG_WATCHDOG
681 If this variable is defined, it enables watchdog
wdenk7152b1d2003-09-05 23:19:14 +0000682 support. There must be support in the platform specific
wdenkc6097192002-11-03 00:24:07 +0000683 code for a watchdog. For the 8xx and 8260 CPUs, the
684 SIU Watchdog feature is enabled in the SYPCR
685 register.
686
stroesec1551ea2003-04-04 15:53:41 +0000687- U-Boot Version:
688 CONFIG_VERSION_VARIABLE
689 If this variable is defined, an environment variable
690 named "ver" is created by U-Boot showing the U-Boot
691 version as printed by the "version" command.
692 This variable is readonly.
693
wdenkc6097192002-11-03 00:24:07 +0000694- Real-Time Clock:
695
696 When CFG_CMD_DATE is selected, the type of the RTC
697 has to be selected, too. Define exactly one of the
698 following options:
699
700 CONFIG_RTC_MPC8xx - use internal RTC of MPC8xx
701 CONFIG_RTC_PCF8563 - use Philips PCF8563 RTC
702 CONFIG_RTC_MC146818 - use MC146818 RTC
wdenk1cb8e982003-03-06 21:55:29 +0000703 CONFIG_RTC_DS1307 - use Maxim, Inc. DS1307 RTC
wdenkc6097192002-11-03 00:24:07 +0000704 CONFIG_RTC_DS1337 - use Maxim, Inc. DS1337 RTC
wdenk7f70e852003-05-20 14:25:27 +0000705 CONFIG_RTC_DS1338 - use Maxim, Inc. DS1338 RTC
wdenk3bac3512003-03-12 10:41:04 +0000706 CONFIG_RTC_DS164x - use Dallas DS164x RTC
wdenkc6097192002-11-03 00:24:07 +0000707
wdenkb37c7e52003-06-30 16:24:52 +0000708 Note that if the RTC uses I2C, then the I2C interface
709 must also be configured. See I2C Support, below.
710
wdenkc6097192002-11-03 00:24:07 +0000711- Timestamp Support:
712
wdenk43d96162003-03-06 00:02:04 +0000713 When CONFIG_TIMESTAMP is selected, the timestamp
714 (date and time) of an image is printed by image
715 commands like bootm or iminfo. This option is
716 automatically enabled when you select CFG_CMD_DATE .
wdenkc6097192002-11-03 00:24:07 +0000717
718- Partition Support:
719 CONFIG_MAC_PARTITION and/or CONFIG_DOS_PARTITION
720 and/or CONFIG_ISO_PARTITION
721
722 If IDE or SCSI support is enabled (CFG_CMD_IDE or
723 CFG_CMD_SCSI) you must configure support for at least
724 one partition type as well.
725
726- IDE Reset method:
727 CONFIG_IDE_RESET_ROUTINE
728
729 Set this to define that instead of a reset Pin, the
730 routine ide_set_reset(int idereset) will be used.
731
732- ATAPI Support:
733 CONFIG_ATAPI
734
735 Set this to enable ATAPI support.
736
737- SCSI Support:
738 At the moment only there is only support for the
739 SYM53C8XX SCSI controller; define
740 CONFIG_SCSI_SYM53C8XX to enable it.
741
742 CFG_SCSI_MAX_LUN [8], CFG_SCSI_MAX_SCSI_ID [7] and
743 CFG_SCSI_MAX_DEVICE [CFG_SCSI_MAX_SCSI_ID *
744 CFG_SCSI_MAX_LUN] can be adjusted to define the
745 maximum numbers of LUNs, SCSI ID's and target
746 devices.
747 CFG_SCSI_SYM53C8XX_CCF to fix clock timing (80Mhz)
748
749- NETWORK Support (PCI):
wdenk682011f2003-06-03 23:54:09 +0000750 CONFIG_E1000
751 Support for Intel 8254x gigabit chips.
stroese53cf9432003-06-05 15:39:44 +0000752
wdenkc6097192002-11-03 00:24:07 +0000753 CONFIG_EEPRO100
754 Support for Intel 82557/82559/82559ER chips.
755 Optional CONFIG_EEPRO100_SROM_WRITE enables eeprom
756 write routine for first time initialisation.
757
758 CONFIG_TULIP
759 Support for Digital 2114x chips.
760 Optional CONFIG_TULIP_SELECT_MEDIA for board specific
761 modem chip initialisation (KS8761/QS6611).
762
763 CONFIG_NATSEMI
764 Support for National dp83815 chips.
765
766 CONFIG_NS8382X
767 Support for National dp8382[01] gigabit chips.
768
wdenk45219c42003-05-12 21:50:16 +0000769- NETWORK Support (other):
770
771 CONFIG_DRIVER_LAN91C96
772 Support for SMSC's LAN91C96 chips.
773
774 CONFIG_LAN91C96_BASE
775 Define this to hold the physical address
776 of the LAN91C96's I/O space
777
778 CONFIG_LAN91C96_USE_32_BIT
779 Define this to enable 32 bit addressing
780
wdenkc6097192002-11-03 00:24:07 +0000781- USB Support:
782 At the moment only the UHCI host controller is
783 supported (PIP405, MIP405); define
784 CONFIG_USB_UHCI to enable it.
785 define CONFIG_USB_KEYBOARD to enable the USB Keyboard
786 end define CONFIG_USB_STORAGE to enable the USB
787 storage devices.
788 Note:
789 Supported are USB Keyboards and USB Floppy drives
790 (TEAC FD-05PUB).
791
wdenk71f95112003-06-15 22:40:42 +0000792- MMC Support:
wdenk8bde7f72003-06-27 21:31:46 +0000793 The MMC controller on the Intel PXA is supported. To
794 enable this define CONFIG_MMC. The MMC can be
795 accessed from the boot prompt by mapping the device
wdenk71f95112003-06-15 22:40:42 +0000796 to physical memory similar to flash. Command line is
797 enabled with CFG_CMD_MMC. The MMC driver also works with
wdenk8bde7f72003-06-27 21:31:46 +0000798 the FAT fs. This is enabled with CFG_CMD_FAT.
wdenk71f95112003-06-15 22:40:42 +0000799
wdenkc6097192002-11-03 00:24:07 +0000800- Keyboard Support:
801 CONFIG_ISA_KEYBOARD
802
803 Define this to enable standard (PC-Style) keyboard
804 support
805
806 CONFIG_I8042_KBD
807 Standard PC keyboard driver with US (is default) and
808 GERMAN key layout (switch via environment 'keymap=de') support.
809 Export function i8042_kbd_init, i8042_tstc and i8042_getc
810 for cfb_console. Supports cursor blinking.
811
812- Video support:
813 CONFIG_VIDEO
814
815 Define this to enable video support (for output to
816 video).
817
818 CONFIG_VIDEO_CT69000
819
820 Enable Chips & Technologies 69000 Video chip
821
822 CONFIG_VIDEO_SMI_LYNXEM
823 Enable Silicon Motion SMI 712/710/810 Video chip
824 Videomode are selected via environment 'videomode' with
825 standard LiLo mode numbers.
826 Following modes are supported (* is default):
827
wdenk43d96162003-03-06 00:02:04 +0000828 800x600 1024x768 1280x1024
829 256 (8bit) 303* 305 307
830 65536 (16bit) 314 317 31a
831 16,7 Mill (24bit) 315 318 31b
wdenkc6097192002-11-03 00:24:07 +0000832 (i.e. setenv videomode 317; saveenv; reset;)
833
stroesec1551ea2003-04-04 15:53:41 +0000834 CONFIG_VIDEO_SED13806
wdenk43d96162003-03-06 00:02:04 +0000835 Enable Epson SED13806 driver. This driver supports 8bpp
wdenka6c7ad22002-12-03 21:28:10 +0000836 and 16bpp modes defined by CONFIG_VIDEO_SED13806_8BPP
837 or CONFIG_VIDEO_SED13806_16BPP
838
wdenk682011f2003-06-03 23:54:09 +0000839- Keyboard Support:
wdenk8bde7f72003-06-27 21:31:46 +0000840 CONFIG_KEYBOARD
wdenk682011f2003-06-03 23:54:09 +0000841
wdenk8bde7f72003-06-27 21:31:46 +0000842 Define this to enable a custom keyboard support.
843 This simply calls drv_keyboard_init() which must be
844 defined in your board-specific files.
845 The only board using this so far is RBC823.
wdenka6c7ad22002-12-03 21:28:10 +0000846
wdenkc6097192002-11-03 00:24:07 +0000847- LCD Support: CONFIG_LCD
848
849 Define this to enable LCD support (for output to LCD
850 display); also select one of the supported displays
851 by defining one of these:
852
wdenkfd3103b2003-11-25 16:55:19 +0000853 CONFIG_NEC_NL6448AC33:
wdenkc6097192002-11-03 00:24:07 +0000854
wdenkfd3103b2003-11-25 16:55:19 +0000855 NEC NL6448AC33-18. Active, color, single scan.
wdenkc6097192002-11-03 00:24:07 +0000856
wdenkfd3103b2003-11-25 16:55:19 +0000857 CONFIG_NEC_NL6448BC20
wdenkc6097192002-11-03 00:24:07 +0000858
wdenkfd3103b2003-11-25 16:55:19 +0000859 NEC NL6448BC20-08. 6.5", 640x480.
860 Active, color, single scan.
861
862 CONFIG_NEC_NL6448BC33_54
863
864 NEC NL6448BC33-54. 10.4", 640x480.
wdenkc6097192002-11-03 00:24:07 +0000865 Active, color, single scan.
866
867 CONFIG_SHARP_16x9
868
869 Sharp 320x240. Active, color, single scan.
870 It isn't 16x9, and I am not sure what it is.
871
872 CONFIG_SHARP_LQ64D341
873
874 Sharp LQ64D341 display, 640x480.
875 Active, color, single scan.
876
877 CONFIG_HLD1045
878
879 HLD1045 display, 640x480.
880 Active, color, single scan.
881
882 CONFIG_OPTREX_BW
883
884 Optrex CBL50840-2 NF-FW 99 22 M5
885 or
886 Hitachi LMG6912RPFC-00T
887 or
888 Hitachi SP14Q002
889
890 320x240. Black & white.
891
892 Normally display is black on white background; define
893 CFG_WHITE_ON_BLACK to get it inverted.
894
wdenk7152b1d2003-09-05 23:19:14 +0000895- Splash Screen Support: CONFIG_SPLASH_SCREEN
wdenkd791b1d2003-04-20 14:04:18 +0000896
wdenk8bde7f72003-06-27 21:31:46 +0000897 If this option is set, the environment is checked for
898 a variable "splashimage". If found, the usual display
899 of logo, copyright and system information on the LCD
900 is supressed and the BMP image at the address
901 specified in "splashimage" is loaded instead. The
902 console is redirected to the "nulldev", too. This
903 allows for a "silent" boot where a splash screen is
904 loaded very quickly after power-on.
wdenkd791b1d2003-04-20 14:04:18 +0000905
wdenkc29fdfc2003-08-29 20:57:53 +0000906- Compression support:
907 CONFIG_BZIP2
908
909 If this option is set, support for bzip2 compressed
910 images is included. If not, only uncompressed and gzip
911 compressed images are supported.
912
wdenk42d1f032003-10-15 23:53:47 +0000913 NOTE: the bzip2 algorithm requires a lot of RAM, so
914 the malloc area (as defined by CFG_MALLOC_LEN) should
915 be at least 4MB.
wdenkd791b1d2003-04-20 14:04:18 +0000916
wdenkc6097192002-11-03 00:24:07 +0000917- Ethernet address:
918 CONFIG_ETHADDR
919 CONFIG_ETH2ADDR
920 CONFIG_ETH3ADDR
921
922 Define a default value for ethernet address to use
923 for the respective ethernet interface, in case this
924 is not determined automatically.
925
926- IP address:
927 CONFIG_IPADDR
928
929 Define a default value for the IP address to use for
930 the default ethernet interface, in case this is not
931 determined through e.g. bootp.
932
933- Server IP address:
934 CONFIG_SERVERIP
935
936 Defines a default value for theIP address of a TFTP
937 server to contact when using the "tftboot" command.
938
939- BOOTP Recovery Mode:
940 CONFIG_BOOTP_RANDOM_DELAY
941
942 If you have many targets in a network that try to
943 boot using BOOTP, you may want to avoid that all
944 systems send out BOOTP requests at precisely the same
945 moment (which would happen for instance at recovery
946 from a power failure, when all systems will try to
947 boot, thus flooding the BOOTP server. Defining
948 CONFIG_BOOTP_RANDOM_DELAY causes a random delay to be
949 inserted before sending out BOOTP requests. The
950 following delays are insterted then:
951
952 1st BOOTP request: delay 0 ... 1 sec
953 2nd BOOTP request: delay 0 ... 2 sec
954 3rd BOOTP request: delay 0 ... 4 sec
955 4th and following
956 BOOTP requests: delay 0 ... 8 sec
957
stroesefe389a82003-08-28 14:17:32 +0000958- DHCP Advanced Options:
959 CONFIG_BOOTP_MASK
960
961 You can fine tune the DHCP functionality by adding
962 these flags to the CONFIG_BOOTP_MASK define:
963
964 CONFIG_BOOTP_DNS2 - If a DHCP client requests the DNS
965 serverip from a DHCP server, it is possible that more
966 than one DNS serverip is offered to the client.
967 If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
968 serverip will be stored in the additional environment
969 variable "dnsip2". The first DNS serverip is always
970 stored in the variable "dnsip", when CONFIG_BOOTP_DNS
971 is added to the CONFIG_BOOTP_MASK.
972
973 CONFIG_BOOTP_SEND_HOSTNAME - Some DHCP servers are capable
974 to do a dynamic update of a DNS server. To do this, they
975 need the hostname of the DHCP requester.
976 If CONFIG_BOOP_SEND_HOSTNAME is added to the
977 CONFIG_BOOTP_MASK, the content of the "hostname"
978 environment variable is passed as option 12 to
979 the DHCP server.
980
wdenkc6097192002-11-03 00:24:07 +0000981- Status LED: CONFIG_STATUS_LED
982
983 Several configurations allow to display the current
984 status using a LED. For instance, the LED will blink
985 fast while running U-Boot code, stop blinking as
986 soon as a reply to a BOOTP request was received, and
987 start blinking slow once the Linux kernel is running
988 (supported by a status LED driver in the Linux
989 kernel). Defining CONFIG_STATUS_LED enables this
990 feature in U-Boot.
991
992- CAN Support: CONFIG_CAN_DRIVER
993
994 Defining CONFIG_CAN_DRIVER enables CAN driver support
995 on those systems that support this (optional)
996 feature, like the TQM8xxL modules.
997
998- I2C Support: CONFIG_HARD_I2C | CONFIG_SOFT_I2C
999
wdenkb37c7e52003-06-30 16:24:52 +00001000 These enable I2C serial bus commands. Defining either of
wdenk945af8d2003-07-16 21:53:01 +00001001 (but not both of) CONFIG_HARD_I2C or CONFIG_SOFT_I2C will
1002 include the appropriate I2C driver for the selected cpu.
wdenkc6097192002-11-03 00:24:07 +00001003
wdenk945af8d2003-07-16 21:53:01 +00001004 This will allow you to use i2c commands at the u-boot
1005 command line (as long as you set CFG_CMD_I2C in
wdenkb37c7e52003-06-30 16:24:52 +00001006 CONFIG_COMMANDS) and communicate with i2c based realtime
1007 clock chips. See common/cmd_i2c.c for a description of the
wdenk43d96162003-03-06 00:02:04 +00001008 command line interface.
wdenkc6097192002-11-03 00:24:07 +00001009
wdenk945af8d2003-07-16 21:53:01 +00001010 CONFIG_HARD_I2C selects the CPM hardware driver for I2C.
wdenkc6097192002-11-03 00:24:07 +00001011
wdenk945af8d2003-07-16 21:53:01 +00001012 CONFIG_SOFT_I2C configures u-boot to use a software (aka
wdenkb37c7e52003-06-30 16:24:52 +00001013 bit-banging) driver instead of CPM or similar hardware
1014 support for I2C.
wdenkc6097192002-11-03 00:24:07 +00001015
wdenk945af8d2003-07-16 21:53:01 +00001016 There are several other quantities that must also be
wdenkb37c7e52003-06-30 16:24:52 +00001017 defined when you define CONFIG_HARD_I2C or CONFIG_SOFT_I2C.
wdenkc6097192002-11-03 00:24:07 +00001018
wdenkb37c7e52003-06-30 16:24:52 +00001019 In both cases you will need to define CFG_I2C_SPEED
wdenk945af8d2003-07-16 21:53:01 +00001020 to be the frequency (in Hz) at which you wish your i2c bus
1021 to run and CFG_I2C_SLAVE to be the address of this node (ie
1022 the cpu's i2c node address).
1023
wdenkb37c7e52003-06-30 16:24:52 +00001024 Now, the u-boot i2c code for the mpc8xx (cpu/mpc8xx/i2c.c)
1025 sets the cpu up as a master node and so its address should
1026 therefore be cleared to 0 (See, eg, MPC823e User's Manual
wdenk945af8d2003-07-16 21:53:01 +00001027 p.16-473). So, set CFG_I2C_SLAVE to 0.
wdenkc6097192002-11-03 00:24:07 +00001028
wdenk945af8d2003-07-16 21:53:01 +00001029 That's all that's required for CONFIG_HARD_I2C.
wdenkb37c7e52003-06-30 16:24:52 +00001030
1031 If you use the software i2c interface (CONFIG_SOFT_I2C)
1032 then the following macros need to be defined (examples are
1033 from include/configs/lwmon.h):
wdenkc6097192002-11-03 00:24:07 +00001034
1035 I2C_INIT
1036
wdenkb37c7e52003-06-30 16:24:52 +00001037 (Optional). Any commands necessary to enable the I2C
wdenk43d96162003-03-06 00:02:04 +00001038 controller or configure ports.
wdenkc6097192002-11-03 00:24:07 +00001039
wdenkb37c7e52003-06-30 16:24:52 +00001040 eg: #define I2C_INIT (immr->im_cpm.cp_pbdir |= PB_SCL)
1041
wdenkc6097192002-11-03 00:24:07 +00001042 I2C_PORT
1043
wdenk43d96162003-03-06 00:02:04 +00001044 (Only for MPC8260 CPU). The I/O port to use (the code
1045 assumes both bits are on the same port). Valid values
1046 are 0..3 for ports A..D.
wdenkc6097192002-11-03 00:24:07 +00001047
1048 I2C_ACTIVE
1049
1050 The code necessary to make the I2C data line active
1051 (driven). If the data line is open collector, this
1052 define can be null.
1053
wdenkb37c7e52003-06-30 16:24:52 +00001054 eg: #define I2C_ACTIVE (immr->im_cpm.cp_pbdir |= PB_SDA)
1055
wdenkc6097192002-11-03 00:24:07 +00001056 I2C_TRISTATE
1057
1058 The code necessary to make the I2C data line tri-stated
1059 (inactive). If the data line is open collector, this
1060 define can be null.
1061
wdenkb37c7e52003-06-30 16:24:52 +00001062 eg: #define I2C_TRISTATE (immr->im_cpm.cp_pbdir &= ~PB_SDA)
1063
wdenkc6097192002-11-03 00:24:07 +00001064 I2C_READ
1065
1066 Code that returns TRUE if the I2C data line is high,
1067 FALSE if it is low.
1068
wdenkb37c7e52003-06-30 16:24:52 +00001069 eg: #define I2C_READ ((immr->im_cpm.cp_pbdat & PB_SDA) != 0)
1070
wdenkc6097192002-11-03 00:24:07 +00001071 I2C_SDA(bit)
1072
1073 If <bit> is TRUE, sets the I2C data line high. If it
1074 is FALSE, it clears it (low).
1075
wdenkb37c7e52003-06-30 16:24:52 +00001076 eg: #define I2C_SDA(bit) \
wdenk2535d602003-07-17 23:16:40 +00001077 if(bit) immr->im_cpm.cp_pbdat |= PB_SDA; \
1078 else immr->im_cpm.cp_pbdat &= ~PB_SDA
wdenkb37c7e52003-06-30 16:24:52 +00001079
wdenkc6097192002-11-03 00:24:07 +00001080 I2C_SCL(bit)
1081
1082 If <bit> is TRUE, sets the I2C clock line high. If it
1083 is FALSE, it clears it (low).
1084
wdenkb37c7e52003-06-30 16:24:52 +00001085 eg: #define I2C_SCL(bit) \
wdenk2535d602003-07-17 23:16:40 +00001086 if(bit) immr->im_cpm.cp_pbdat |= PB_SCL; \
1087 else immr->im_cpm.cp_pbdat &= ~PB_SCL
wdenkb37c7e52003-06-30 16:24:52 +00001088
wdenkc6097192002-11-03 00:24:07 +00001089 I2C_DELAY
1090
1091 This delay is invoked four times per clock cycle so this
1092 controls the rate of data transfer. The data rate thus
wdenkb37c7e52003-06-30 16:24:52 +00001093 is 1 / (I2C_DELAY * 4). Often defined to be something
wdenk945af8d2003-07-16 21:53:01 +00001094 like:
1095
wdenkb37c7e52003-06-30 16:24:52 +00001096 #define I2C_DELAY udelay(2)
wdenkc6097192002-11-03 00:24:07 +00001097
wdenk47cd00f2003-03-06 13:39:27 +00001098 CFG_I2C_INIT_BOARD
1099
wdenk8bde7f72003-06-27 21:31:46 +00001100 When a board is reset during an i2c bus transfer
1101 chips might think that the current transfer is still
1102 in progress. On some boards it is possible to access
1103 the i2c SCLK line directly, either by using the
1104 processor pin as a GPIO or by having a second pin
1105 connected to the bus. If this option is defined a
1106 custom i2c_init_board() routine in boards/xxx/board.c
1107 is run early in the boot sequence.
wdenk47cd00f2003-03-06 13:39:27 +00001108
wdenkc6097192002-11-03 00:24:07 +00001109- SPI Support: CONFIG_SPI
1110
1111 Enables SPI driver (so far only tested with
1112 SPI EEPROM, also an instance works with Crystal A/D and
1113 D/As on the SACSng board)
1114
1115 CONFIG_SPI_X
1116
1117 Enables extended (16-bit) SPI EEPROM addressing.
1118 (symmetrical to CONFIG_I2C_X)
1119
1120 CONFIG_SOFT_SPI
1121
wdenk43d96162003-03-06 00:02:04 +00001122 Enables a software (bit-bang) SPI driver rather than
1123 using hardware support. This is a general purpose
1124 driver that only requires three general I/O port pins
1125 (two outputs, one input) to function. If this is
1126 defined, the board configuration must define several
1127 SPI configuration items (port pins to use, etc). For
1128 an example, see include/configs/sacsng.h.
wdenkc6097192002-11-03 00:24:07 +00001129
1130- FPGA Support: CONFIG_FPGA_COUNT
1131
wdenk43d96162003-03-06 00:02:04 +00001132 Specify the number of FPGA devices to support.
wdenkc6097192002-11-03 00:24:07 +00001133
wdenk43d96162003-03-06 00:02:04 +00001134 CONFIG_FPGA
wdenkc6097192002-11-03 00:24:07 +00001135
wdenk43d96162003-03-06 00:02:04 +00001136 Used to specify the types of FPGA devices. For
wdenkc6097192002-11-03 00:24:07 +00001137 example,
wdenk8bde7f72003-06-27 21:31:46 +00001138 #define CONFIG_FPGA CFG_XILINX_VIRTEX2
wdenkc6097192002-11-03 00:24:07 +00001139
wdenk8bde7f72003-06-27 21:31:46 +00001140 CFG_FPGA_PROG_FEEDBACK
wdenkc6097192002-11-03 00:24:07 +00001141
wdenk43d96162003-03-06 00:02:04 +00001142 Enable printing of hash marks during FPGA
wdenkc6097192002-11-03 00:24:07 +00001143 configuration.
1144
1145 CFG_FPGA_CHECK_BUSY
1146
wdenk43d96162003-03-06 00:02:04 +00001147 Enable checks on FPGA configuration interface busy
1148 status by the configuration function. This option
1149 will require a board or device specific function to
1150 be written.
wdenkc6097192002-11-03 00:24:07 +00001151
1152 CONFIG_FPGA_DELAY
1153
wdenk43d96162003-03-06 00:02:04 +00001154 If defined, a function that provides delays in the
1155 FPGA configuration driver.
wdenkc6097192002-11-03 00:24:07 +00001156
1157 CFG_FPGA_CHECK_CTRLC
1158
1159 Allow Control-C to interrupt FPGA configuration
1160
1161 CFG_FPGA_CHECK_ERROR
1162
wdenk43d96162003-03-06 00:02:04 +00001163 Check for configuration errors during FPGA bitfile
1164 loading. For example, abort during Virtex II
1165 configuration if the INIT_B line goes low (which
1166 indicated a CRC error).
wdenkc6097192002-11-03 00:24:07 +00001167
1168 CFG_FPGA_WAIT_INIT
1169
wdenk43d96162003-03-06 00:02:04 +00001170 Maximum time to wait for the INIT_B line to deassert
1171 after PROB_B has been deasserted during a Virtex II
1172 FPGA configuration sequence. The default time is 500 mS.
wdenkc6097192002-11-03 00:24:07 +00001173
1174 CFG_FPGA_WAIT_BUSY
1175
wdenk43d96162003-03-06 00:02:04 +00001176 Maximum time to wait for BUSY to deassert during
1177 Virtex II FPGA configuration. The default is 5 mS.
wdenkc6097192002-11-03 00:24:07 +00001178
1179 CFG_FPGA_WAIT_CONFIG
1180
wdenk43d96162003-03-06 00:02:04 +00001181 Time to wait after FPGA configuration. The default is
wdenkc6097192002-11-03 00:24:07 +00001182 200 mS.
1183
1184- FPGA Support: CONFIG_FPGA_COUNT
1185
wdenk8bde7f72003-06-27 21:31:46 +00001186 Specify the number of FPGA devices to support.
wdenkc6097192002-11-03 00:24:07 +00001187
wdenk8bde7f72003-06-27 21:31:46 +00001188 CONFIG_FPGA
wdenkc6097192002-11-03 00:24:07 +00001189
wdenk8bde7f72003-06-27 21:31:46 +00001190 Used to specify the types of FPGA devices. For example,
1191 #define CONFIG_FPGA CFG_XILINX_VIRTEX2
wdenkc6097192002-11-03 00:24:07 +00001192
wdenk8bde7f72003-06-27 21:31:46 +00001193 CFG_FPGA_PROG_FEEDBACK
wdenkc6097192002-11-03 00:24:07 +00001194
wdenk8bde7f72003-06-27 21:31:46 +00001195 Enable printing of hash marks during FPGA configuration.
wdenkc6097192002-11-03 00:24:07 +00001196
1197 CFG_FPGA_CHECK_BUSY
1198
wdenk43d96162003-03-06 00:02:04 +00001199 Enable checks on FPGA configuration interface busy
1200 status by the configuration function. This option
1201 will require a board or device specific function to
1202 be written.
wdenkc6097192002-11-03 00:24:07 +00001203
1204 CONFIG_FPGA_DELAY
1205
1206 If defined, a function that provides delays in the FPGA
1207 configuration driver.
1208
1209 CFG_FPGA_CHECK_CTRLC
1210 Allow Control-C to interrupt FPGA configuration
1211
1212 CFG_FPGA_CHECK_ERROR
1213
wdenk43d96162003-03-06 00:02:04 +00001214 Check for configuration errors during FPGA bitfile
1215 loading. For example, abort during Virtex II
1216 configuration if the INIT_B line goes low (which
1217 indicated a CRC error).
wdenkc6097192002-11-03 00:24:07 +00001218
1219 CFG_FPGA_WAIT_INIT
1220
wdenk43d96162003-03-06 00:02:04 +00001221 Maximum time to wait for the INIT_B line to deassert
1222 after PROB_B has been deasserted during a Virtex II
1223 FPGA configuration sequence. The default time is 500
1224 mS.
wdenkc6097192002-11-03 00:24:07 +00001225
1226 CFG_FPGA_WAIT_BUSY
1227
wdenk43d96162003-03-06 00:02:04 +00001228 Maximum time to wait for BUSY to deassert during
1229 Virtex II FPGA configuration. The default is 5 mS.
wdenkc6097192002-11-03 00:24:07 +00001230
1231 CFG_FPGA_WAIT_CONFIG
1232
wdenk43d96162003-03-06 00:02:04 +00001233 Time to wait after FPGA configuration. The default is
1234 200 mS.
wdenkc6097192002-11-03 00:24:07 +00001235
1236- Configuration Management:
1237 CONFIG_IDENT_STRING
1238
wdenk43d96162003-03-06 00:02:04 +00001239 If defined, this string will be added to the U-Boot
1240 version information (U_BOOT_VERSION)
wdenkc6097192002-11-03 00:24:07 +00001241
1242- Vendor Parameter Protection:
1243
wdenk43d96162003-03-06 00:02:04 +00001244 U-Boot considers the values of the environment
1245 variables "serial#" (Board Serial Number) and
wdenk7152b1d2003-09-05 23:19:14 +00001246 "ethaddr" (Ethernet Address) to be parameters that
wdenk43d96162003-03-06 00:02:04 +00001247 are set once by the board vendor / manufacturer, and
1248 protects these variables from casual modification by
1249 the user. Once set, these variables are read-only,
1250 and write or delete attempts are rejected. You can
1251 change this behviour:
wdenkc6097192002-11-03 00:24:07 +00001252
1253 If CONFIG_ENV_OVERWRITE is #defined in your config
1254 file, the write protection for vendor parameters is
wdenk47cd00f2003-03-06 13:39:27 +00001255 completely disabled. Anybody can change or delete
wdenkc6097192002-11-03 00:24:07 +00001256 these parameters.
1257
1258 Alternatively, if you #define _both_ CONFIG_ETHADDR
1259 _and_ CONFIG_OVERWRITE_ETHADDR_ONCE, a default
1260 ethernet address is installed in the environment,
1261 which can be changed exactly ONCE by the user. [The
1262 serial# is unaffected by this, i. e. it remains
1263 read-only.]
1264
1265- Protected RAM:
1266 CONFIG_PRAM
1267
1268 Define this variable to enable the reservation of
1269 "protected RAM", i. e. RAM which is not overwritten
1270 by U-Boot. Define CONFIG_PRAM to hold the number of
1271 kB you want to reserve for pRAM. You can overwrite
1272 this default value by defining an environment
1273 variable "pram" to the number of kB you want to
1274 reserve. Note that the board info structure will
1275 still show the full amount of RAM. If pRAM is
1276 reserved, a new environment variable "mem" will
1277 automatically be defined to hold the amount of
1278 remaining RAM in a form that can be passed as boot
1279 argument to Linux, for instance like that:
1280
1281 setenv bootargs ... mem=\$(mem)
1282 saveenv
1283
1284 This way you can tell Linux not to use this memory,
1285 either, which results in a memory region that will
1286 not be affected by reboots.
1287
1288 *WARNING* If your board configuration uses automatic
1289 detection of the RAM size, you must make sure that
1290 this memory test is non-destructive. So far, the
1291 following board configurations are known to be
1292 "pRAM-clean":
1293
1294 ETX094, IVMS8, IVML24, SPD8xx, TQM8xxL,
1295 HERMES, IP860, RPXlite, LWMON, LANTEC,
1296 PCU_E, FLAGADM, TQM8260
1297
1298- Error Recovery:
1299 CONFIG_PANIC_HANG
1300
1301 Define this variable to stop the system in case of a
1302 fatal error, so that you have to reset it manually.
1303 This is probably NOT a good idea for an embedded
1304 system where you want to system to reboot
1305 automatically as fast as possible, but it may be
1306 useful during development since you can try to debug
1307 the conditions that lead to the situation.
1308
1309 CONFIG_NET_RETRY_COUNT
1310
wdenk43d96162003-03-06 00:02:04 +00001311 This variable defines the number of retries for
1312 network operations like ARP, RARP, TFTP, or BOOTP
1313 before giving up the operation. If not defined, a
1314 default value of 5 is used.
wdenkc6097192002-11-03 00:24:07 +00001315
1316- Command Interpreter:
1317 CFG_HUSH_PARSER
1318
1319 Define this variable to enable the "hush" shell (from
1320 Busybox) as command line interpreter, thus enabling
1321 powerful command line syntax like
1322 if...then...else...fi conditionals or `&&' and '||'
1323 constructs ("shell scripts").
1324
1325 If undefined, you get the old, much simpler behaviour
1326 with a somewhat smaller memory footprint.
1327
1328
1329 CFG_PROMPT_HUSH_PS2
1330
1331 This defines the secondary prompt string, which is
1332 printed when the command interpreter needs more input
1333 to complete a command. Usually "> ".
1334
1335 Note:
1336
wdenk8bde7f72003-06-27 21:31:46 +00001337 In the current implementation, the local variables
1338 space and global environment variables space are
1339 separated. Local variables are those you define by
1340 simply typing `name=value'. To access a local
1341 variable later on, you have write `$name' or
1342 `${name}'; to execute the contents of a variable
1343 directly type `$name' at the command prompt.
wdenkc6097192002-11-03 00:24:07 +00001344
wdenk43d96162003-03-06 00:02:04 +00001345 Global environment variables are those you use
1346 setenv/printenv to work with. To run a command stored
1347 in such a variable, you need to use the run command,
1348 and you must not use the '$' sign to access them.
wdenkc6097192002-11-03 00:24:07 +00001349
1350 To store commands and special characters in a
1351 variable, please use double quotation marks
1352 surrounding the whole text of the variable, instead
1353 of the backslashes before semicolons and special
1354 symbols.
1355
wdenka8c7c702003-12-06 19:49:23 +00001356- Default Environment:
wdenkc6097192002-11-03 00:24:07 +00001357 CONFIG_EXTRA_ENV_SETTINGS
1358
wdenk43d96162003-03-06 00:02:04 +00001359 Define this to contain any number of null terminated
1360 strings (variable = value pairs) that will be part of
wdenk7152b1d2003-09-05 23:19:14 +00001361 the default environment compiled into the boot image.
wdenk2262cfe2002-11-18 00:14:45 +00001362
wdenk43d96162003-03-06 00:02:04 +00001363 For example, place something like this in your
1364 board's config file:
wdenkc6097192002-11-03 00:24:07 +00001365
1366 #define CONFIG_EXTRA_ENV_SETTINGS \
1367 "myvar1=value1\0" \
1368 "myvar2=value2\0"
1369
wdenk43d96162003-03-06 00:02:04 +00001370 Warning: This method is based on knowledge about the
1371 internal format how the environment is stored by the
1372 U-Boot code. This is NOT an official, exported
1373 interface! Although it is unlikely that this format
wdenk7152b1d2003-09-05 23:19:14 +00001374 will change soon, there is no guarantee either.
wdenkc6097192002-11-03 00:24:07 +00001375 You better know what you are doing here.
1376
wdenk43d96162003-03-06 00:02:04 +00001377 Note: overly (ab)use of the default environment is
1378 discouraged. Make sure to check other ways to preset
1379 the environment like the autoscript function or the
1380 boot command first.
wdenkc6097192002-11-03 00:24:07 +00001381
wdenka8c7c702003-12-06 19:49:23 +00001382- DataFlash Support:
wdenk2abbe072003-06-16 23:50:08 +00001383 CONFIG_HAS_DATAFLASH
1384
wdenk8bde7f72003-06-27 21:31:46 +00001385 Defining this option enables DataFlash features and
1386 allows to read/write in Dataflash via the standard
1387 commands cp, md...
wdenk2abbe072003-06-16 23:50:08 +00001388
wdenka8c7c702003-12-06 19:49:23 +00001389- Show boot progress:
wdenkc6097192002-11-03 00:24:07 +00001390 CONFIG_SHOW_BOOT_PROGRESS
1391
wdenk43d96162003-03-06 00:02:04 +00001392 Defining this option allows to add some board-
1393 specific code (calling a user-provided function
1394 "show_boot_progress(int)") that enables you to show
1395 the system's boot progress on some display (for
1396 example, some LED's) on your board. At the moment,
1397 the following checkpoints are implemented:
wdenkc6097192002-11-03 00:24:07 +00001398
1399 Arg Where When
1400 1 common/cmd_bootm.c before attempting to boot an image
1401 -1 common/cmd_bootm.c Image header has bad magic number
1402 2 common/cmd_bootm.c Image header has correct magic number
1403 -2 common/cmd_bootm.c Image header has bad checksum
1404 3 common/cmd_bootm.c Image header has correct checksum
1405 -3 common/cmd_bootm.c Image data has bad checksum
1406 4 common/cmd_bootm.c Image data has correct checksum
1407 -4 common/cmd_bootm.c Image is for unsupported architecture
1408 5 common/cmd_bootm.c Architecture check OK
1409 -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi, standalone)
1410 6 common/cmd_bootm.c Image Type check OK
1411 -6 common/cmd_bootm.c gunzip uncompression error
1412 -7 common/cmd_bootm.c Unimplemented compression type
1413 7 common/cmd_bootm.c Uncompression OK
1414 -8 common/cmd_bootm.c Wrong Image Type (not kernel, multi, standalone)
1415 8 common/cmd_bootm.c Image Type check OK
1416 -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
1417 9 common/cmd_bootm.c Start initial ramdisk verification
1418 -10 common/cmd_bootm.c Ramdisk header has bad magic number
1419 -11 common/cmd_bootm.c Ramdisk header has bad checksum
1420 10 common/cmd_bootm.c Ramdisk header is OK
1421 -12 common/cmd_bootm.c Ramdisk data has bad checksum
1422 11 common/cmd_bootm.c Ramdisk data has correct checksum
1423 12 common/cmd_bootm.c Ramdisk verification complete, start loading
1424 -13 common/cmd_bootm.c Wrong Image Type (not PPC Linux Ramdisk)
1425 13 common/cmd_bootm.c Start multifile image verification
1426 14 common/cmd_bootm.c No initial ramdisk, no multifile, continue.
1427 15 common/cmd_bootm.c All preparation done, transferring control to OS
1428
1429 -1 common/cmd_doc.c Bad usage of "doc" command
1430 -1 common/cmd_doc.c No boot device
1431 -1 common/cmd_doc.c Unknown Chip ID on boot device
1432 -1 common/cmd_doc.c Read Error on boot device
1433 -1 common/cmd_doc.c Image header has bad magic number
1434
1435 -1 common/cmd_ide.c Bad usage of "ide" command
1436 -1 common/cmd_ide.c No boot device
1437 -1 common/cmd_ide.c Unknown boot device
1438 -1 common/cmd_ide.c Unknown partition table
1439 -1 common/cmd_ide.c Invalid partition type
1440 -1 common/cmd_ide.c Read Error on boot device
1441 -1 common/cmd_ide.c Image header has bad magic number
1442
wdenk206c60c2003-09-18 10:02:25 +00001443 -1 common/cmd_nand.c Bad usage of "nand" command
1444 -1 common/cmd_nand.c No boot device
1445 -1 common/cmd_nand.c Unknown Chip ID on boot device
1446 -1 common/cmd_nand.c Read Error on boot device
1447 -1 common/cmd_nand.c Image header has bad magic number
1448
1449 -1 common/env_common.c Environment has a bad CRC, using default
wdenkc6097192002-11-03 00:24:07 +00001450
1451
1452Modem Support:
1453--------------
1454
wdenk85ec0bc2003-03-31 16:34:49 +00001455[so far only for SMDK2400 and TRAB boards]
wdenkc6097192002-11-03 00:24:07 +00001456
1457- Modem support endable:
1458 CONFIG_MODEM_SUPPORT
1459
1460- RTS/CTS Flow control enable:
1461 CONFIG_HWFLOW
1462
1463- Modem debug support:
1464 CONFIG_MODEM_SUPPORT_DEBUG
1465
wdenk43d96162003-03-06 00:02:04 +00001466 Enables debugging stuff (char screen[1024], dbg())
1467 for modem support. Useful only with BDI2000.
wdenkc6097192002-11-03 00:24:07 +00001468
wdenka8c7c702003-12-06 19:49:23 +00001469- Interrupt support (PPC):
1470
1471 There are common interrupt_init() and timer_interrupt()
1472 for all PPC archs. interrupt_init() calls interrupt_init_cpu()
1473 for cpu specific initialization. interrupt_init_cpu()
1474 should set decrementer_count to appropriate value. If
1475 cpu resets decrementer automatically after interrupt
1476 (ppc4xx) it should set decrementer_count to zero.
1477 timer_interrupt() calls timer_interrupt_cpu() for cpu
1478 specific handling. If board has watchdog / status_led
1479 / other_activity_monitor it works automatically from
1480 general timer_interrupt().
1481
wdenkc6097192002-11-03 00:24:07 +00001482- General:
1483
wdenk43d96162003-03-06 00:02:04 +00001484 In the target system modem support is enabled when a
1485 specific key (key combination) is pressed during
1486 power-on. Otherwise U-Boot will boot normally
1487 (autoboot). The key_pressed() fuction is called from
1488 board_init(). Currently key_pressed() is a dummy
1489 function, returning 1 and thus enabling modem
1490 initialization.
wdenkc6097192002-11-03 00:24:07 +00001491
wdenk43d96162003-03-06 00:02:04 +00001492 If there are no modem init strings in the
1493 environment, U-Boot proceed to autoboot; the
1494 previous output (banner, info printfs) will be
1495 supressed, though.
wdenkc6097192002-11-03 00:24:07 +00001496
1497 See also: doc/README.Modem
1498
1499
wdenkc6097192002-11-03 00:24:07 +00001500Configuration Settings:
1501-----------------------
1502
1503- CFG_LONGHELP: Defined when you want long help messages included;
1504 undefine this when you're short of memory.
1505
1506- CFG_PROMPT: This is what U-Boot prints on the console to
1507 prompt for user input.
1508
1509- CFG_CBSIZE: Buffer size for input from the Console
1510
1511- CFG_PBSIZE: Buffer size for Console output
1512
1513- CFG_MAXARGS: max. Number of arguments accepted for monitor commands
1514
1515- CFG_BARGSIZE: Buffer size for Boot Arguments which are passed to
1516 the application (usually a Linux kernel) when it is
1517 booted
1518
1519- CFG_BAUDRATE_TABLE:
1520 List of legal baudrate settings for this board.
1521
1522- CFG_CONSOLE_INFO_QUIET
wdenk8bde7f72003-06-27 21:31:46 +00001523 Suppress display of console information at boot.
wdenkc6097192002-11-03 00:24:07 +00001524
1525- CFG_CONSOLE_IS_IN_ENV
wdenk8bde7f72003-06-27 21:31:46 +00001526 If the board specific function
1527 extern int overwrite_console (void);
1528 returns 1, the stdin, stderr and stdout are switched to the
wdenkc6097192002-11-03 00:24:07 +00001529 serial port, else the settings in the environment are used.
1530
1531- CFG_CONSOLE_OVERWRITE_ROUTINE
wdenk8bde7f72003-06-27 21:31:46 +00001532 Enable the call to overwrite_console().
wdenkc6097192002-11-03 00:24:07 +00001533
1534- CFG_CONSOLE_ENV_OVERWRITE
1535 Enable overwrite of previous console environment settings.
1536
1537- CFG_MEMTEST_START, CFG_MEMTEST_END:
1538 Begin and End addresses of the area used by the
1539 simple memory test.
1540
1541- CFG_ALT_MEMTEST:
wdenk8bde7f72003-06-27 21:31:46 +00001542 Enable an alternate, more extensive memory test.
wdenkc6097192002-11-03 00:24:07 +00001543
wdenk5f535fe2003-09-18 09:21:33 +00001544- CFG_MEMTEST_SCRATCH:
1545 Scratch address used by the alternate memory test
1546 You only need to set this if address zero isn't writeable
1547
wdenkc6097192002-11-03 00:24:07 +00001548- CFG_TFTP_LOADADDR:
1549 Default load address for network file downloads
1550
1551- CFG_LOADS_BAUD_CHANGE:
1552 Enable temporary baudrate change while serial download
1553
1554- CFG_SDRAM_BASE:
1555 Physical start address of SDRAM. _Must_ be 0 here.
1556
1557- CFG_MBIO_BASE:
1558 Physical start address of Motherboard I/O (if using a
1559 Cogent motherboard)
1560
1561- CFG_FLASH_BASE:
1562 Physical start address of Flash memory.
1563
1564- CFG_MONITOR_BASE:
1565 Physical start address of boot monitor code (set by
1566 make config files to be same as the text base address
1567 (TEXT_BASE) used when linking) - same as
1568 CFG_FLASH_BASE when booting from flash.
1569
1570- CFG_MONITOR_LEN:
wdenk8bde7f72003-06-27 21:31:46 +00001571 Size of memory reserved for monitor code, used to
1572 determine _at_compile_time_ (!) if the environment is
1573 embedded within the U-Boot image, or in a separate
1574 flash sector.
wdenkc6097192002-11-03 00:24:07 +00001575
1576- CFG_MALLOC_LEN:
1577 Size of DRAM reserved for malloc() use.
1578
1579- CFG_BOOTMAPSZ:
1580 Maximum size of memory mapped by the startup code of
1581 the Linux kernel; all data that must be processed by
1582 the Linux kernel (bd_info, boot arguments, eventually
1583 initrd image) must be put below this limit.
1584
1585- CFG_MAX_FLASH_BANKS:
1586 Max number of Flash memory banks
1587
1588- CFG_MAX_FLASH_SECT:
1589 Max number of sectors on a Flash chip
1590
1591- CFG_FLASH_ERASE_TOUT:
1592 Timeout for Flash erase operations (in ms)
1593
1594- CFG_FLASH_WRITE_TOUT:
1595 Timeout for Flash write operations (in ms)
1596
wdenk8564acf2003-07-14 22:13:32 +00001597- CFG_FLASH_LOCK_TOUT
1598 Timeout for Flash set sector lock bit operation (in ms)
1599
1600- CFG_FLASH_UNLOCK_TOUT
1601 Timeout for Flash clear lock bits operation (in ms)
1602
1603- CFG_FLASH_PROTECTION
1604 If defined, hardware flash sectors protection is used
1605 instead of U-Boot software protection.
1606
wdenkc6097192002-11-03 00:24:07 +00001607- CFG_DIRECT_FLASH_TFTP:
1608
1609 Enable TFTP transfers directly to flash memory;
1610 without this option such a download has to be
1611 performed in two steps: (1) download to RAM, and (2)
1612 copy from RAM to flash.
1613
1614 The two-step approach is usually more reliable, since
1615 you can check if the download worked before you erase
1616 the flash, but in some situations (when sytem RAM is
1617 too limited to allow for a tempory copy of the
1618 downloaded image) this option may be very useful.
1619
1620- CFG_FLASH_CFI:
wdenk43d96162003-03-06 00:02:04 +00001621 Define if the flash driver uses extra elements in the
1622 common flash structure for storing flash geometry
wdenkc6097192002-11-03 00:24:07 +00001623
stroese53cf9432003-06-05 15:39:44 +00001624- CFG_RX_ETH_BUFFER:
1625 Defines the number of ethernet receive buffers. On some
1626 ethernet controllers it is recommended to set this value
1627 to 8 or even higher (EEPRO100 or 405 EMAC), since all
1628 buffers can be full shortly after enabling the interface
1629 on high ethernet traffic.
1630 Defaults to 4 if not defined.
1631
wdenkc6097192002-11-03 00:24:07 +00001632The following definitions that deal with the placement and management
1633of environment data (variable area); in general, we support the
1634following configurations:
1635
1636- CFG_ENV_IS_IN_FLASH:
1637
1638 Define this if the environment is in flash memory.
1639
1640 a) The environment occupies one whole flash sector, which is
1641 "embedded" in the text segment with the U-Boot code. This
1642 happens usually with "bottom boot sector" or "top boot
1643 sector" type flash chips, which have several smaller
1644 sectors at the start or the end. For instance, such a
1645 layout can have sector sizes of 8, 2x4, 16, Nx32 kB. In
1646 such a case you would place the environment in one of the
1647 4 kB sectors - with U-Boot code before and after it. With
1648 "top boot sector" type flash chips, you would put the
1649 environment in one of the last sectors, leaving a gap
1650 between U-Boot and the environment.
1651
1652 - CFG_ENV_OFFSET:
1653
1654 Offset of environment data (variable area) to the
1655 beginning of flash memory; for instance, with bottom boot
1656 type flash chips the second sector can be used: the offset
1657 for this sector is given here.
1658
1659 CFG_ENV_OFFSET is used relative to CFG_FLASH_BASE.
1660
1661 - CFG_ENV_ADDR:
1662
1663 This is just another way to specify the start address of
1664 the flash sector containing the environment (instead of
1665 CFG_ENV_OFFSET).
1666
1667 - CFG_ENV_SECT_SIZE:
1668
1669 Size of the sector containing the environment.
1670
1671
1672 b) Sometimes flash chips have few, equal sized, BIG sectors.
1673 In such a case you don't want to spend a whole sector for
1674 the environment.
1675
1676 - CFG_ENV_SIZE:
1677
1678 If you use this in combination with CFG_ENV_IS_IN_FLASH
1679 and CFG_ENV_SECT_SIZE, you can specify to use only a part
1680 of this flash sector for the environment. This saves
1681 memory for the RAM copy of the environment.
1682
1683 It may also save flash memory if you decide to use this
1684 when your environment is "embedded" within U-Boot code,
1685 since then the remainder of the flash sector could be used
1686 for U-Boot code. It should be pointed out that this is
1687 STRONGLY DISCOURAGED from a robustness point of view:
1688 updating the environment in flash makes it always
1689 necessary to erase the WHOLE sector. If something goes
1690 wrong before the contents has been restored from a copy in
1691 RAM, your target system will be dead.
1692
1693 - CFG_ENV_ADDR_REDUND
1694 CFG_ENV_SIZE_REDUND
1695
wdenk43d96162003-03-06 00:02:04 +00001696 These settings describe a second storage area used to hold
1697 a redundand copy of the environment data, so that there is
wdenk3e386912003-04-05 00:53:31 +00001698 a valid backup copy in case there is a power failure during
wdenk43d96162003-03-06 00:02:04 +00001699 a "saveenv" operation.
wdenkc6097192002-11-03 00:24:07 +00001700
1701BE CAREFUL! Any changes to the flash layout, and some changes to the
1702source code will make it necessary to adapt <board>/u-boot.lds*
1703accordingly!
1704
1705
1706- CFG_ENV_IS_IN_NVRAM:
1707
1708 Define this if you have some non-volatile memory device
1709 (NVRAM, battery buffered SRAM) which you want to use for the
1710 environment.
1711
1712 - CFG_ENV_ADDR:
1713 - CFG_ENV_SIZE:
1714
1715 These two #defines are used to determin the memory area you
1716 want to use for environment. It is assumed that this memory
1717 can just be read and written to, without any special
1718 provision.
1719
1720BE CAREFUL! The first access to the environment happens quite early
1721in U-Boot initalization (when we try to get the setting of for the
1722console baudrate). You *MUST* have mappend your NVRAM area then, or
1723U-Boot will hang.
1724
1725Please note that even with NVRAM we still use a copy of the
1726environment in RAM: we could work on NVRAM directly, but we want to
1727keep settings there always unmodified except somebody uses "saveenv"
1728to save the current settings.
1729
1730
1731- CFG_ENV_IS_IN_EEPROM:
1732
1733 Use this if you have an EEPROM or similar serial access
1734 device and a driver for it.
1735
1736 - CFG_ENV_OFFSET:
1737 - CFG_ENV_SIZE:
1738
1739 These two #defines specify the offset and size of the
1740 environment area within the total memory of your EEPROM.
1741
1742 - CFG_I2C_EEPROM_ADDR:
1743 If defined, specified the chip address of the EEPROM device.
1744 The default address is zero.
1745
1746 - CFG_EEPROM_PAGE_WRITE_BITS:
1747 If defined, the number of bits used to address bytes in a
1748 single page in the EEPROM device. A 64 byte page, for example
1749 would require six bits.
1750
1751 - CFG_EEPROM_PAGE_WRITE_DELAY_MS:
1752 If defined, the number of milliseconds to delay between
1753 page writes. The default is zero milliseconds.
1754
1755 - CFG_I2C_EEPROM_ADDR_LEN:
1756 The length in bytes of the EEPROM memory array address. Note
1757 that this is NOT the chip address length!
1758
1759 - CFG_EEPROM_SIZE:
1760 The size in bytes of the EEPROM device.
1761
wdenkc6097192002-11-03 00:24:07 +00001762
1763- CFG_SPI_INIT_OFFSET
1764
1765 Defines offset to the initial SPI buffer area in DPRAM. The
1766 area is used at an early stage (ROM part) if the environment
1767 is configured to reside in the SPI EEPROM: We need a 520 byte
1768 scratch DPRAM area. It is used between the two initialization
1769 calls (spi_init_f() and spi_init_r()). A value of 0xB00 seems
1770 to be a good choice since it makes it far enough from the
1771 start of the data area as well as from the stack pointer.
1772
1773Please note that the environment is read-only as long as the monitor
1774has been relocated to RAM and a RAM copy of the environment has been
1775created; also, when using EEPROM you will have to use getenv_r()
1776until then to read environment variables.
1777
wdenk85ec0bc2003-03-31 16:34:49 +00001778The environment is protected by a CRC32 checksum. Before the monitor
1779is relocated into RAM, as a result of a bad CRC you will be working
1780with the compiled-in default environment - *silently*!!! [This is
1781necessary, because the first environment variable we need is the
1782"baudrate" setting for the console - if we have a bad CRC, we don't
1783have any device yet where we could complain.]
wdenkc6097192002-11-03 00:24:07 +00001784
1785Note: once the monitor has been relocated, then it will complain if
1786the default environment is used; a new CRC is computed as soon as you
wdenk85ec0bc2003-03-31 16:34:49 +00001787use the "saveenv" command to store a valid environment.
wdenkc6097192002-11-03 00:24:07 +00001788
wdenkfc3e2162003-10-08 22:33:00 +00001789- CFG_FAULT_ECHO_LINK_DOWN:
wdenk42d1f032003-10-15 23:53:47 +00001790 Echo the inverted Ethernet link state to the fault LED.
wdenkfc3e2162003-10-08 22:33:00 +00001791
1792 Note: If this option is active, then CFG_FAULT_MII_ADDR
1793 also needs to be defined.
1794
1795- CFG_FAULT_MII_ADDR:
wdenk42d1f032003-10-15 23:53:47 +00001796 MII address of the PHY to check for the Ethernet link state.
wdenkc6097192002-11-03 00:24:07 +00001797
wdenkc6097192002-11-03 00:24:07 +00001798Low Level (hardware related) configuration options:
wdenkdc7c9a12003-03-26 06:55:25 +00001799---------------------------------------------------
wdenkc6097192002-11-03 00:24:07 +00001800
1801- CFG_CACHELINE_SIZE:
1802 Cache Line Size of the CPU.
1803
1804- CFG_DEFAULT_IMMR:
1805 Default address of the IMMR after system reset.
wdenk2535d602003-07-17 23:16:40 +00001806
wdenk42d1f032003-10-15 23:53:47 +00001807 Needed on some 8260 systems (MPC8260ADS, PQ2FADS-ZU,
1808 and RPXsuper) to be able to adjust the position of
1809 the IMMR register after a reset.
wdenkc6097192002-11-03 00:24:07 +00001810
wdenk7f6c2cb2002-11-10 22:06:23 +00001811- Floppy Disk Support:
1812 CFG_FDC_DRIVE_NUMBER
1813
1814 the default drive number (default value 0)
1815
1816 CFG_ISA_IO_STRIDE
1817
1818 defines the spacing between fdc chipset registers
1819 (default value 1)
1820
1821 CFG_ISA_IO_OFFSET
1822
wdenk43d96162003-03-06 00:02:04 +00001823 defines the offset of register from address. It
1824 depends on which part of the data bus is connected to
1825 the fdc chipset. (default value 0)
wdenk7f6c2cb2002-11-10 22:06:23 +00001826
wdenk43d96162003-03-06 00:02:04 +00001827 If CFG_ISA_IO_STRIDE CFG_ISA_IO_OFFSET and
1828 CFG_FDC_DRIVE_NUMBER are undefined, they take their
1829 default value.
wdenk7f6c2cb2002-11-10 22:06:23 +00001830
wdenk43d96162003-03-06 00:02:04 +00001831 if CFG_FDC_HW_INIT is defined, then the function
1832 fdc_hw_init() is called at the beginning of the FDC
1833 setup. fdc_hw_init() must be provided by the board
1834 source code. It is used to make hardware dependant
1835 initializations.
wdenk7f6c2cb2002-11-10 22:06:23 +00001836
wdenkc6097192002-11-03 00:24:07 +00001837- CFG_IMMR: Physical address of the Internal Memory Mapped
1838 Register; DO NOT CHANGE! (11-4)
1839 [MPC8xx systems only]
1840
1841- CFG_INIT_RAM_ADDR:
1842
wdenk7152b1d2003-09-05 23:19:14 +00001843 Start address of memory area that can be used for
wdenkc6097192002-11-03 00:24:07 +00001844 initial data and stack; please note that this must be
1845 writable memory that is working WITHOUT special
1846 initialization, i. e. you CANNOT use normal RAM which
1847 will become available only after programming the
1848 memory controller and running certain initialization
1849 sequences.
1850
1851 U-Boot uses the following memory types:
1852 - MPC8xx and MPC8260: IMMR (internal memory of the CPU)
1853 - MPC824X: data cache
1854 - PPC4xx: data cache
1855
wdenk85ec0bc2003-03-31 16:34:49 +00001856- CFG_GBL_DATA_OFFSET:
wdenkc6097192002-11-03 00:24:07 +00001857
1858 Offset of the initial data structure in the memory
1859 area defined by CFG_INIT_RAM_ADDR. Usually
wdenk85ec0bc2003-03-31 16:34:49 +00001860 CFG_GBL_DATA_OFFSET is chosen such that the initial
wdenkc6097192002-11-03 00:24:07 +00001861 data is located at the end of the available space
1862 (sometimes written as (CFG_INIT_RAM_END -
1863 CFG_INIT_DATA_SIZE), and the initial stack is just
1864 below that area (growing from (CFG_INIT_RAM_ADDR +
wdenk85ec0bc2003-03-31 16:34:49 +00001865 CFG_GBL_DATA_OFFSET) downward.
wdenkc6097192002-11-03 00:24:07 +00001866
1867 Note:
1868 On the MPC824X (or other systems that use the data
1869 cache for initial memory) the address chosen for
1870 CFG_INIT_RAM_ADDR is basically arbitrary - it must
1871 point to an otherwise UNUSED address space between
1872 the top of RAM and the start of the PCI space.
1873
1874- CFG_SIUMCR: SIU Module Configuration (11-6)
1875
1876- CFG_SYPCR: System Protection Control (11-9)
1877
1878- CFG_TBSCR: Time Base Status and Control (11-26)
1879
1880- CFG_PISCR: Periodic Interrupt Status and Control (11-31)
1881
1882- CFG_PLPRCR: PLL, Low-Power, and Reset Control Register (15-30)
1883
1884- CFG_SCCR: System Clock and reset Control Register (15-27)
1885
1886- CFG_OR_TIMING_SDRAM:
1887 SDRAM timing
1888
1889- CFG_MAMR_PTA:
1890 periodic timer for refresh
1891
1892- CFG_DER: Debug Event Register (37-47)
1893
1894- FLASH_BASE0_PRELIM, FLASH_BASE1_PRELIM, CFG_REMAP_OR_AM,
1895 CFG_PRELIM_OR_AM, CFG_OR_TIMING_FLASH, CFG_OR0_REMAP,
1896 CFG_OR0_PRELIM, CFG_BR0_PRELIM, CFG_OR1_REMAP, CFG_OR1_PRELIM,
1897 CFG_BR1_PRELIM:
1898 Memory Controller Definitions: BR0/1 and OR0/1 (FLASH)
1899
1900- SDRAM_BASE2_PRELIM, SDRAM_BASE3_PRELIM, SDRAM_MAX_SIZE,
1901 CFG_OR_TIMING_SDRAM, CFG_OR2_PRELIM, CFG_BR2_PRELIM,
1902 CFG_OR3_PRELIM, CFG_BR3_PRELIM:
1903 Memory Controller Definitions: BR2/3 and OR2/3 (SDRAM)
1904
1905- CFG_MAMR_PTA, CFG_MPTPR_2BK_4K, CFG_MPTPR_1BK_4K, CFG_MPTPR_2BK_8K,
1906 CFG_MPTPR_1BK_8K, CFG_MAMR_8COL, CFG_MAMR_9COL:
1907 Machine Mode Register and Memory Periodic Timer
1908 Prescaler definitions (SDRAM timing)
1909
1910- CFG_I2C_UCODE_PATCH, CFG_I2C_DPMEM_OFFSET [0x1FC0]:
1911 enable I2C microcode relocation patch (MPC8xx);
1912 define relocation offset in DPRAM [DSP2]
1913
1914- CFG_SPI_UCODE_PATCH, CFG_SPI_DPMEM_OFFSET [0x1FC0]:
1915 enable SPI microcode relocation patch (MPC8xx);
1916 define relocation offset in DPRAM [SCC4]
1917
1918- CFG_USE_OSCCLK:
1919 Use OSCM clock mode on MBX8xx board. Be careful,
1920 wrong setting might damage your board. Read
1921 doc/README.MBX before setting this variable!
1922
wdenkea909b72002-11-21 23:11:29 +00001923- CFG_CPM_POST_WORD_ADDR: (MPC8xx, MPC8260 only)
wdenk43d96162003-03-06 00:02:04 +00001924 Offset of the bootmode word in DPRAM used by post
1925 (Power On Self Tests). This definition overrides
1926 #define'd default value in commproc.h resp.
1927 cpm_8260.h.
wdenkea909b72002-11-21 23:11:29 +00001928
stroese1d49b1f2003-05-23 11:39:05 +00001929- CFG_PCI_SLV_MEM_LOCAL, CFG_PCI_SLV_MEM_BUS, CFG_PICMR0_MASK_ATTRIB,
1930 CFG_PCI_MSTR0_LOCAL, CFG_PCIMSK0_MASK, CFG_PCI_MSTR1_LOCAL,
1931 CFG_PCIMSK1_MASK, CFG_PCI_MSTR_MEM_LOCAL, CFG_PCI_MSTR_MEM_BUS,
1932 CFG_CPU_PCI_MEM_START, CFG_PCI_MSTR_MEM_SIZE, CFG_POCMR0_MASK_ATTRIB,
1933 CFG_PCI_MSTR_MEMIO_LOCAL, CFG_PCI_MSTR_MEMIO_BUS, CPU_PCI_MEMIO_START,
1934 CFG_PCI_MSTR_MEMIO_SIZE, CFG_POCMR1_MASK_ATTRIB, CFG_PCI_MSTR_IO_LOCAL,
1935 CFG_PCI_MSTR_IO_BUS, CFG_CPU_PCI_IO_START, CFG_PCI_MSTR_IO_SIZE,
wdenk5d232d02003-05-22 22:52:13 +00001936 CFG_POCMR2_MASK_ATTRIB: (MPC826x only)
1937 Overrides the default PCI memory map in cpu/mpc8260/pci.c if set.
1938
wdenkc6097192002-11-03 00:24:07 +00001939Building the Software:
1940======================
1941
1942Building U-Boot has been tested in native PPC environments (on a
1943PowerBook G3 running LinuxPPC 2000) and in cross environments
1944(running RedHat 6.x and 7.x Linux on x86, Solaris 2.6 on a SPARC, and
1945NetBSD 1.5 on x86).
1946
1947If you are not using a native PPC environment, it is assumed that you
1948have the GNU cross compiling tools available in your path and named
1949with a prefix of "powerpc-linux-". If this is not the case, (e.g. if
1950you are using Monta Vista's Hard Hat Linux CDK 1.2) you must change
1951the definition of CROSS_COMPILE in Makefile. For HHL on a 4xx CPU,
1952change it to:
1953
1954 CROSS_COMPILE = ppc_4xx-
1955
1956
1957U-Boot is intended to be simple to build. After installing the
1958sources you must configure U-Boot for one specific board type. This
1959is done by typing:
1960
1961 make NAME_config
1962
1963where "NAME_config" is the name of one of the existing
1964configurations; the following names are supported:
1965
1966 ADCIOP_config GTH_config TQM850L_config
1967 ADS860_config IP860_config TQM855L_config
1968 AR405_config IVML24_config TQM860L_config
1969 CANBT_config IVMS8_config WALNUT405_config
1970 CPCI405_config LANTEC_config cogent_common_config
1971 CPCIISER4_config MBX_config cogent_mpc8260_config
1972 CU824_config MBX860T_config cogent_mpc8xx_config
1973 ESTEEM192E_config RPXlite_config hermes_config
1974 ETX094_config RPXsuper_config hymod_config
1975 FADS823_config SM850_config lwmon_config
1976 FADS850SAR_config SPD823TS_config pcu_e_config
1977 FADS860T_config SXNI855T_config rsdproto_config
1978 FPS850L_config Sandpoint8240_config sbc8260_config
1979 GENIETV_config TQM823L_config PIP405_config
wdenk384ae022002-11-05 00:17:55 +00001980 GEN860T_config EBONY_config FPS860L_config
wdenk7f70e852003-05-20 14:25:27 +00001981 ELPT860_config cmi_mpc5xx_config NETVIA_config
wdenk2535d602003-07-17 23:16:40 +00001982 at91rm9200dk_config omap1510inn_config MPC8260ADS_config
wdenk42d1f032003-10-15 23:53:47 +00001983 omap1610inn_config ZPC1900_config MPC8540ADS_config
1984 MPC8560ADS_config
wdenk54387ac2003-10-08 22:45:44 +00001985
wdenkc6097192002-11-03 00:24:07 +00001986Note: for some board special configuration names may exist; check if
1987 additional information is available from the board vendor; for
1988 instance, the TQM8xxL systems run normally at 50 MHz and use a
1989 SCC for 10baseT ethernet; there are also systems with 80 MHz
1990 CPU clock, and an optional Fast Ethernet module is available
1991 for CPU's with FEC. You can select such additional "features"
1992 when chosing the configuration, i. e.
1993
1994 make TQM860L_config
1995 - will configure for a plain TQM860L, i. e. 50MHz, no FEC
1996
1997 make TQM860L_FEC_config
1998 - will configure for a TQM860L at 50MHz with FEC for ethernet
1999
2000 make TQM860L_80MHz_config
2001 - will configure for a TQM860L at 80 MHz, with normal 10baseT
2002 interface
2003
2004 make TQM860L_FEC_80MHz_config
2005 - will configure for a TQM860L at 80 MHz with FEC for ethernet
2006
2007 make TQM823L_LCD_config
2008 - will configure for a TQM823L with U-Boot console on LCD
2009
2010 make TQM823L_LCD_80MHz_config
2011 - will configure for a TQM823L at 80 MHz with U-Boot console on LCD
2012
2013 etc.
2014
2015
wdenk24ee89b2002-11-03 17:56:27 +00002016Finally, type "make all", and you should get some working U-Boot
wdenk7152b1d2003-09-05 23:19:14 +00002017images ready for download to / installation on your system:
wdenkc6097192002-11-03 00:24:07 +00002018
2019- "u-boot.bin" is a raw binary image
2020- "u-boot" is an image in ELF binary format
2021- "u-boot.srec" is in Motorola S-Record format
2022
2023
2024Please be aware that the Makefiles assume you are using GNU make, so
2025for instance on NetBSD you might need to use "gmake" instead of
2026native "make".
2027
2028
2029If the system board that you have is not listed, then you will need
2030to port U-Boot to your hardware platform. To do this, follow these
2031steps:
2032
20331. Add a new configuration option for your board to the toplevel
wdenk85ec0bc2003-03-31 16:34:49 +00002034 "Makefile" and to the "MAKEALL" script, using the existing
2035 entries as examples. Note that here and at many other places
wdenk7152b1d2003-09-05 23:19:14 +00002036 boards and other names are listed in alphabetical sort order. Please
wdenk85ec0bc2003-03-31 16:34:49 +00002037 keep this order.
wdenkc6097192002-11-03 00:24:07 +000020382. Create a new directory to hold your board specific code. Add any
wdenk85ec0bc2003-03-31 16:34:49 +00002039 files you need. In your board directory, you will need at least
2040 the "Makefile", a "<board>.c", "flash.c" and "u-boot.lds".
20413. Create a new configuration file "include/configs/<board>.h" for
2042 your board
wdenkc6097192002-11-03 00:24:07 +000020433. If you're porting U-Boot to a new CPU, then also create a new
2044 directory to hold your CPU specific code. Add any files you need.
wdenk85ec0bc2003-03-31 16:34:49 +000020454. Run "make <board>_config" with your new name.
wdenkc6097192002-11-03 00:24:07 +000020465. Type "make", and you should get a working "u-boot.srec" file
2047 to be installed on your target system.
wdenk85ec0bc2003-03-31 16:34:49 +000020486. Debug and solve any problems that might arise.
wdenkc6097192002-11-03 00:24:07 +00002049 [Of course, this last step is much harder than it sounds.]
2050
2051
2052Testing of U-Boot Modifications, Ports to New Hardware, etc.:
2053==============================================================
2054
2055If you have modified U-Boot sources (for instance added a new board
2056or support for new devices, a new CPU, etc.) you are expected to
2057provide feedback to the other developers. The feedback normally takes
2058the form of a "patch", i. e. a context diff against a certain (latest
2059official or latest in CVS) version of U-Boot sources.
2060
2061But before you submit such a patch, please verify that your modifi-
2062cation did not break existing code. At least make sure that *ALL* of
2063the supported boards compile WITHOUT ANY compiler warnings. To do so,
2064just run the "MAKEALL" script, which will configure and build U-Boot
2065for ALL supported system. Be warned, this will take a while. You can
wdenk7152b1d2003-09-05 23:19:14 +00002066select which (cross) compiler to use by passing a `CROSS_COMPILE'
wdenkc6097192002-11-03 00:24:07 +00002067environment variable to the script, i. e. to use the cross tools from
2068MontaVista's Hard Hat Linux you can type
2069
2070 CROSS_COMPILE=ppc_8xx- MAKEALL
2071
2072or to build on a native PowerPC system you can type
2073
2074 CROSS_COMPILE=' ' MAKEALL
2075
2076See also "U-Boot Porting Guide" below.
2077
2078
wdenkc6097192002-11-03 00:24:07 +00002079Monitor Commands - Overview:
2080============================
2081
2082go - start application at address 'addr'
2083run - run commands in an environment variable
2084bootm - boot application image from memory
2085bootp - boot image via network using BootP/TFTP protocol
2086tftpboot- boot image via network using TFTP protocol
2087 and env variables "ipaddr" and "serverip"
2088 (and eventually "gatewayip")
2089rarpboot- boot image via network using RARP/TFTP protocol
2090diskboot- boot from IDE devicebootd - boot default, i.e., run 'bootcmd'
2091loads - load S-Record file over serial line
2092loadb - load binary file over serial line (kermit mode)
2093md - memory display
2094mm - memory modify (auto-incrementing)
2095nm - memory modify (constant address)
2096mw - memory write (fill)
2097cp - memory copy
2098cmp - memory compare
2099crc32 - checksum calculation
2100imd - i2c memory display
2101imm - i2c memory modify (auto-incrementing)
2102inm - i2c memory modify (constant address)
2103imw - i2c memory write (fill)
2104icrc32 - i2c checksum calculation
2105iprobe - probe to discover valid I2C chip addresses
2106iloop - infinite loop on address range
2107isdram - print SDRAM configuration information
2108sspi - SPI utility commands
2109base - print or set address offset
2110printenv- print environment variables
2111setenv - set environment variables
2112saveenv - save environment variables to persistent storage
2113protect - enable or disable FLASH write protection
2114erase - erase FLASH memory
2115flinfo - print FLASH memory information
2116bdinfo - print Board Info structure
2117iminfo - print header information for application image
2118coninfo - print console devices and informations
2119ide - IDE sub-system
2120loop - infinite loop on address range
2121mtest - simple RAM test
2122icache - enable or disable instruction cache
2123dcache - enable or disable data cache
2124reset - Perform RESET of the CPU
2125echo - echo args to console
2126version - print monitor version
2127help - print online help
2128? - alias for 'help'
2129
2130
2131Monitor Commands - Detailed Description:
2132========================================
2133
2134TODO.
2135
2136For now: just type "help <command>".
2137
2138
2139Environment Variables:
2140======================
2141
2142U-Boot supports user configuration using Environment Variables which
2143can be made persistent by saving to Flash memory.
2144
2145Environment Variables are set using "setenv", printed using
2146"printenv", and saved to Flash using "saveenv". Using "setenv"
2147without a value can be used to delete a variable from the
2148environment. As long as you don't save the environment you are
2149working with an in-memory copy. In case the Flash area containing the
2150environment is erased by accident, a default environment is provided.
2151
2152Some configuration options can be set using Environment Variables:
2153
2154 baudrate - see CONFIG_BAUDRATE
2155
2156 bootdelay - see CONFIG_BOOTDELAY
2157
2158 bootcmd - see CONFIG_BOOTCOMMAND
2159
2160 bootargs - Boot arguments when booting an RTOS image
2161
2162 bootfile - Name of the image to load with TFTP
2163
2164 autoload - if set to "no" (any string beginning with 'n'),
2165 "bootp" will just load perform a lookup of the
2166 configuration from the BOOTP server, but not try to
2167 load any image using TFTP
2168
2169 autostart - if set to "yes", an image loaded using the "bootp",
2170 "rarpboot", "tftpboot" or "diskboot" commands will
2171 be automatically started (by internally calling
2172 "bootm")
2173
wdenk4a6fd342003-04-12 23:38:12 +00002174 If set to "no", a standalone image passed to the
2175 "bootm" command will be copied to the load address
2176 (and eventually uncompressed), but NOT be started.
2177 This can be used to load and uncompress arbitrary
2178 data.
2179
wdenkc6097192002-11-03 00:24:07 +00002180 initrd_high - restrict positioning of initrd images:
2181 If this variable is not set, initrd images will be
2182 copied to the highest possible address in RAM; this
2183 is usually what you want since it allows for
2184 maximum initrd size. If for some reason you want to
2185 make sure that the initrd image is loaded below the
2186 CFG_BOOTMAPSZ limit, you can set this environment
2187 variable to a value of "no" or "off" or "0".
2188 Alternatively, you can set it to a maximum upper
2189 address to use (U-Boot will still check that it
2190 does not overwrite the U-Boot stack and data).
2191
2192 For instance, when you have a system with 16 MB
wdenk7152b1d2003-09-05 23:19:14 +00002193 RAM, and want to reserve 4 MB from use by Linux,
wdenkc6097192002-11-03 00:24:07 +00002194 you can do this by adding "mem=12M" to the value of
2195 the "bootargs" variable. However, now you must make
wdenk7152b1d2003-09-05 23:19:14 +00002196 sure that the initrd image is placed in the first
wdenkc6097192002-11-03 00:24:07 +00002197 12 MB as well - this can be done with
2198
2199 setenv initrd_high 00c00000
2200
wdenk8bde7f72003-06-27 21:31:46 +00002201 If you set initrd_high to 0xFFFFFFFF, this is an
2202 indication to U-Boot that all addresses are legal
2203 for the Linux kernel, including addresses in flash
2204 memory. In this case U-Boot will NOT COPY the
2205 ramdisk at all. This may be useful to reduce the
2206 boot time on your system, but requires that this
2207 feature is supported by your Linux kernel.
wdenk38b99262003-05-23 23:18:21 +00002208
wdenkc6097192002-11-03 00:24:07 +00002209 ipaddr - IP address; needed for tftpboot command
2210
2211 loadaddr - Default load address for commands like "bootp",
wdenkdc7c9a12003-03-26 06:55:25 +00002212 "rarpboot", "tftpboot", "loadb" or "diskboot"
wdenkc6097192002-11-03 00:24:07 +00002213
2214 loads_echo - see CONFIG_LOADS_ECHO
2215
2216 serverip - TFTP server IP address; needed for tftpboot command
2217
2218 bootretry - see CONFIG_BOOT_RETRY_TIME
2219
2220 bootdelaykey - see CONFIG_AUTOBOOT_DELAY_STR
2221
2222 bootstopkey - see CONFIG_AUTOBOOT_STOP_STR
2223
2224
2225The following environment variables may be used and automatically
2226updated by the network boot commands ("bootp" and "rarpboot"),
2227depending the information provided by your boot server:
2228
2229 bootfile - see above
2230 dnsip - IP address of your Domain Name Server
stroesefe389a82003-08-28 14:17:32 +00002231 dnsip2 - IP address of your secondary Domain Name Server
wdenkc6097192002-11-03 00:24:07 +00002232 gatewayip - IP address of the Gateway (Router) to use
2233 hostname - Target hostname
2234 ipaddr - see above
2235 netmask - Subnet Mask
2236 rootpath - Pathname of the root filesystem on the NFS server
2237 serverip - see above
2238
2239
2240There are two special Environment Variables:
2241
2242 serial# - contains hardware identification information such
2243 as type string and/or serial number
2244 ethaddr - Ethernet address
2245
2246These variables can be set only once (usually during manufacturing of
2247the board). U-Boot refuses to delete or overwrite these variables
2248once they have been set once.
2249
2250
stroesec1551ea2003-04-04 15:53:41 +00002251Further special Environment Variables:
2252
2253 ver - Contains the U-Boot version string as printed
2254 with the "version" command. This variable is
2255 readonly (see CONFIG_VERSION_VARIABLE).
2256
2257
wdenkc6097192002-11-03 00:24:07 +00002258Please note that changes to some configuration parameters may take
2259only effect after the next boot (yes, that's just like Windoze :-).
2260
2261
wdenkf07771c2003-05-28 08:06:31 +00002262Command Line Parsing:
2263=====================
2264
wdenk7152b1d2003-09-05 23:19:14 +00002265There are two different command line parsers available with U-Boot:
2266the old "simple" one, and the much more powerful "hush" shell:
wdenkf07771c2003-05-28 08:06:31 +00002267
2268Old, simple command line parser:
2269--------------------------------
2270
2271- supports environment variables (through setenv / saveenv commands)
2272- several commands on one line, separated by ';'
2273- variable substitution using "... $(name) ..." syntax
2274- special characters ('$', ';') can be escaped by prefixing with '\',
2275 for example:
2276 setenv bootcmd bootm \$(address)
2277- You can also escape text by enclosing in single apostrophes, for example:
2278 setenv addip 'setenv bootargs $bootargs ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname::off'
2279
2280Hush shell:
2281-----------
2282
2283- similar to Bourne shell, with control structures like
2284 if...then...else...fi, for...do...done; while...do...done,
2285 until...do...done, ...
2286- supports environment ("global") variables (through setenv / saveenv
2287 commands) and local shell variables (through standard shell syntax
2288 "name=value"); only environment variables can be used with "run"
2289 command
2290
2291General rules:
2292--------------
2293
2294(1) If a command line (or an environment variable executed by a "run"
2295 command) contains several commands separated by semicolon, and
2296 one of these commands fails, then the remaining commands will be
2297 executed anyway.
2298
2299(2) If you execute several variables with one call to run (i. e.
2300 calling run with a list af variables as arguments), any failing
2301 command will cause "run" to terminate, i. e. the remaining
2302 variables are not executed.
2303
wdenkc6097192002-11-03 00:24:07 +00002304Note for Redundant Ethernet Interfaces:
2305=======================================
2306
wdenk7152b1d2003-09-05 23:19:14 +00002307Some boards come with redundant ethernet interfaces; U-Boot supports
wdenkc6097192002-11-03 00:24:07 +00002308such configurations and is capable of automatic selection of a
wdenk7152b1d2003-09-05 23:19:14 +00002309"working" interface when needed. MAC assignment works as follows:
wdenkc6097192002-11-03 00:24:07 +00002310
2311Network interfaces are numbered eth0, eth1, eth2, ... Corresponding
2312MAC addresses can be stored in the environment as "ethaddr" (=>eth0),
2313"eth1addr" (=>eth1), "eth2addr", ...
2314
2315If the network interface stores some valid MAC address (for instance
2316in SROM), this is used as default address if there is NO correspon-
2317ding setting in the environment; if the corresponding environment
2318variable is set, this overrides the settings in the card; that means:
2319
2320o If the SROM has a valid MAC address, and there is no address in the
2321 environment, the SROM's address is used.
2322
2323o If there is no valid address in the SROM, and a definition in the
2324 environment exists, then the value from the environment variable is
2325 used.
2326
2327o If both the SROM and the environment contain a MAC address, and
2328 both addresses are the same, this MAC address is used.
2329
2330o If both the SROM and the environment contain a MAC address, and the
2331 addresses differ, the value from the environment is used and a
2332 warning is printed.
2333
2334o If neither SROM nor the environment contain a MAC address, an error
2335 is raised.
2336
2337
wdenkc6097192002-11-03 00:24:07 +00002338Image Formats:
2339==============
2340
2341The "boot" commands of this monitor operate on "image" files which
2342can be basicly anything, preceeded by a special header; see the
2343definitions in include/image.h for details; basicly, the header
2344defines the following image properties:
2345
2346* Target Operating System (Provisions for OpenBSD, NetBSD, FreeBSD,
2347 4.4BSD, Linux, SVR4, Esix, Solaris, Irix, SCO, Dell, NCR, VxWorks,
wdenk7f70e852003-05-20 14:25:27 +00002348 LynxOS, pSOS, QNX, RTEMS, ARTOS;
wdenk1f4bb372003-07-27 00:21:01 +00002349 Currently supported: Linux, NetBSD, VxWorks, QNX, RTEMS, ARTOS, LynxOS).
wdenkc6097192002-11-03 00:24:07 +00002350* Target CPU Architecture (Provisions for Alpha, ARM, Intel x86,
wdenk3d1e8a92003-10-16 12:53:35 +00002351 IA64, MIPS, NIOS, PowerPC, IBM S390, SuperH, Sparc, Sparc 64 Bit;
2352 Currently supported: ARM, Intel x86, MIPS, NIOS, PowerPC).
wdenkc29fdfc2003-08-29 20:57:53 +00002353* Compression Type (uncompressed, gzip, bzip2)
wdenkc6097192002-11-03 00:24:07 +00002354* Load Address
2355* Entry Point
2356* Image Name
2357* Image Timestamp
2358
2359The header is marked by a special Magic Number, and both the header
2360and the data portions of the image are secured against corruption by
2361CRC32 checksums.
2362
2363
2364Linux Support:
2365==============
2366
2367Although U-Boot should support any OS or standalone application
wdenk7152b1d2003-09-05 23:19:14 +00002368easily, the main focus has always been on Linux during the design of
wdenkc6097192002-11-03 00:24:07 +00002369U-Boot.
2370
2371U-Boot includes many features that so far have been part of some
2372special "boot loader" code within the Linux kernel. Also, any
2373"initrd" images to be used are no longer part of one big Linux image;
2374instead, kernel and "initrd" are separate images. This implementation
wdenk7152b1d2003-09-05 23:19:14 +00002375serves several purposes:
wdenkc6097192002-11-03 00:24:07 +00002376
2377- the same features can be used for other OS or standalone
2378 applications (for instance: using compressed images to reduce the
2379 Flash memory footprint)
2380
2381- it becomes much easier to port new Linux kernel versions because
wdenk7152b1d2003-09-05 23:19:14 +00002382 lots of low-level, hardware dependent stuff are done by U-Boot
wdenkc6097192002-11-03 00:24:07 +00002383
2384- the same Linux kernel image can now be used with different "initrd"
2385 images; of course this also means that different kernel images can
2386 be run with the same "initrd". This makes testing easier (you don't
2387 have to build a new "zImage.initrd" Linux image when you just
2388 change a file in your "initrd"). Also, a field-upgrade of the
2389 software is easier now.
2390
2391
2392Linux HOWTO:
2393============
2394
2395Porting Linux to U-Boot based systems:
2396---------------------------------------
2397
2398U-Boot cannot save you from doing all the necessary modifications to
2399configure the Linux device drivers for use with your target hardware
2400(no, we don't intend to provide a full virtual machine interface to
2401Linux :-).
2402
2403But now you can ignore ALL boot loader code (in arch/ppc/mbxboot).
2404
2405Just make sure your machine specific header file (for instance
2406include/asm-ppc/tqm8xx.h) includes the same definition of the Board
2407Information structure as we define in include/u-boot.h, and make
2408sure that your definition of IMAP_ADDR uses the same value as your
2409U-Boot configuration in CFG_IMMR.
2410
2411
2412Configuring the Linux kernel:
2413-----------------------------
2414
2415No specific requirements for U-Boot. Make sure you have some root
2416device (initial ramdisk, NFS) for your target system.
2417
2418
2419Building a Linux Image:
2420-----------------------
2421
wdenk24ee89b2002-11-03 17:56:27 +00002422With U-Boot, "normal" build targets like "zImage" or "bzImage" are
2423not used. If you use recent kernel source, a new build target
2424"uImage" will exist which automatically builds an image usable by
2425U-Boot. Most older kernels also have support for a "pImage" target,
2426which was introduced for our predecessor project PPCBoot and uses a
2427100% compatible format.
wdenkc6097192002-11-03 00:24:07 +00002428
2429Example:
2430
2431 make TQM850L_config
2432 make oldconfig
2433 make dep
wdenk24ee89b2002-11-03 17:56:27 +00002434 make uImage
wdenkc6097192002-11-03 00:24:07 +00002435
wdenk24ee89b2002-11-03 17:56:27 +00002436The "uImage" build target uses a special tool (in 'tools/mkimage') to
2437encapsulate a compressed Linux kernel image with header information,
2438CRC32 checksum etc. for use with U-Boot. This is what we are doing:
wdenkc6097192002-11-03 00:24:07 +00002439
wdenk24ee89b2002-11-03 17:56:27 +00002440* build a standard "vmlinux" kernel image (in ELF binary format):
wdenkc6097192002-11-03 00:24:07 +00002441
wdenk24ee89b2002-11-03 17:56:27 +00002442* convert the kernel into a raw binary image:
2443
2444 ${CROSS_COMPILE}-objcopy -O binary \
2445 -R .note -R .comment \
2446 -S vmlinux linux.bin
2447
2448* compress the binary image:
2449
2450 gzip -9 linux.bin
2451
2452* package compressed binary image for U-Boot:
2453
2454 mkimage -A ppc -O linux -T kernel -C gzip \
2455 -a 0 -e 0 -n "Linux Kernel Image" \
2456 -d linux.bin.gz uImage
2457
2458
2459The "mkimage" tool can also be used to create ramdisk images for use
2460with U-Boot, either separated from the Linux kernel image, or
2461combined into one file. "mkimage" encapsulates the images with a 64
2462byte header containing information about target architecture,
2463operating system, image type, compression method, entry points, time
2464stamp, CRC32 checksums, etc.
2465
2466"mkimage" can be called in two ways: to verify existing images and
2467print the header information, or to build new images.
2468
2469In the first form (with "-l" option) mkimage lists the information
2470contained in the header of an existing U-Boot image; this includes
wdenkc6097192002-11-03 00:24:07 +00002471checksum verification:
2472
2473 tools/mkimage -l image
2474 -l ==> list image header information
2475
2476The second form (with "-d" option) is used to build a U-Boot image
2477from a "data file" which is used as image payload:
2478
2479 tools/mkimage -A arch -O os -T type -C comp -a addr -e ep \
2480 -n name -d data_file image
2481 -A ==> set architecture to 'arch'
2482 -O ==> set operating system to 'os'
2483 -T ==> set image type to 'type'
2484 -C ==> set compression type 'comp'
2485 -a ==> set load address to 'addr' (hex)
2486 -e ==> set entry point to 'ep' (hex)
2487 -n ==> set image name to 'name'
2488 -d ==> use image data from 'datafile'
2489
2490Right now, all Linux kernels use the same load address (0x00000000),
2491but the entry point address depends on the kernel version:
2492
2493- 2.2.x kernels have the entry point at 0x0000000C,
wdenk24ee89b2002-11-03 17:56:27 +00002494- 2.3.x and later kernels have the entry point at 0x00000000.
wdenkc6097192002-11-03 00:24:07 +00002495
2496So a typical call to build a U-Boot image would read:
2497
wdenk24ee89b2002-11-03 17:56:27 +00002498 -> tools/mkimage -n '2.4.4 kernel for TQM850L' \
2499 > -A ppc -O linux -T kernel -C gzip -a 0 -e 0 \
2500 > -d /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/ppc/coffboot/vmlinux.gz \
2501 > examples/uImage.TQM850L
2502 Image Name: 2.4.4 kernel for TQM850L
wdenkc6097192002-11-03 00:24:07 +00002503 Created: Wed Jul 19 02:34:59 2000
2504 Image Type: PowerPC Linux Kernel Image (gzip compressed)
2505 Data Size: 335725 Bytes = 327.86 kB = 0.32 MB
2506 Load Address: 0x00000000
wdenk24ee89b2002-11-03 17:56:27 +00002507 Entry Point: 0x00000000
wdenkc6097192002-11-03 00:24:07 +00002508
2509To verify the contents of the image (or check for corruption):
2510
wdenk24ee89b2002-11-03 17:56:27 +00002511 -> tools/mkimage -l examples/uImage.TQM850L
2512 Image Name: 2.4.4 kernel for TQM850L
wdenkc6097192002-11-03 00:24:07 +00002513 Created: Wed Jul 19 02:34:59 2000
2514 Image Type: PowerPC Linux Kernel Image (gzip compressed)
2515 Data Size: 335725 Bytes = 327.86 kB = 0.32 MB
2516 Load Address: 0x00000000
wdenk24ee89b2002-11-03 17:56:27 +00002517 Entry Point: 0x00000000
wdenkc6097192002-11-03 00:24:07 +00002518
2519NOTE: for embedded systems where boot time is critical you can trade
2520speed for memory and install an UNCOMPRESSED image instead: this
2521needs more space in Flash, but boots much faster since it does not
2522need to be uncompressed:
2523
wdenk24ee89b2002-11-03 17:56:27 +00002524 -> gunzip /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/ppc/coffboot/vmlinux.gz
2525 -> tools/mkimage -n '2.4.4 kernel for TQM850L' \
2526 > -A ppc -O linux -T kernel -C none -a 0 -e 0 \
2527 > -d /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/ppc/coffboot/vmlinux \
2528 > examples/uImage.TQM850L-uncompressed
2529 Image Name: 2.4.4 kernel for TQM850L
wdenkc6097192002-11-03 00:24:07 +00002530 Created: Wed Jul 19 02:34:59 2000
2531 Image Type: PowerPC Linux Kernel Image (uncompressed)
2532 Data Size: 792160 Bytes = 773.59 kB = 0.76 MB
2533 Load Address: 0x00000000
wdenk24ee89b2002-11-03 17:56:27 +00002534 Entry Point: 0x00000000
wdenkc6097192002-11-03 00:24:07 +00002535
2536
2537Similar you can build U-Boot images from a 'ramdisk.image.gz' file
2538when your kernel is intended to use an initial ramdisk:
2539
2540 -> tools/mkimage -n 'Simple Ramdisk Image' \
2541 > -A ppc -O linux -T ramdisk -C gzip \
2542 > -d /LinuxPPC/images/SIMPLE-ramdisk.image.gz examples/simple-initrd
2543 Image Name: Simple Ramdisk Image
2544 Created: Wed Jan 12 14:01:50 2000
2545 Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
2546 Data Size: 566530 Bytes = 553.25 kB = 0.54 MB
2547 Load Address: 0x00000000
2548 Entry Point: 0x00000000
2549
2550
2551Installing a Linux Image:
2552-------------------------
2553
2554To downloading a U-Boot image over the serial (console) interface,
2555you must convert the image to S-Record format:
2556
2557 objcopy -I binary -O srec examples/image examples/image.srec
2558
2559The 'objcopy' does not understand the information in the U-Boot
2560image header, so the resulting S-Record file will be relative to
2561address 0x00000000. To load it to a given address, you need to
2562specify the target address as 'offset' parameter with the 'loads'
2563command.
2564
2565Example: install the image to address 0x40100000 (which on the
2566TQM8xxL is in the first Flash bank):
2567
2568 => erase 40100000 401FFFFF
2569
2570 .......... done
2571 Erased 8 sectors
2572
2573 => loads 40100000
2574 ## Ready for S-Record download ...
2575 ~>examples/image.srec
2576 1 2 3 4 5 6 7 8 9 10 11 12 13 ...
2577 ...
2578 15989 15990 15991 15992
2579 [file transfer complete]
2580 [connected]
2581 ## Start Addr = 0x00000000
2582
2583
2584You can check the success of the download using the 'iminfo' command;
2585this includes a checksum verification so you can be sure no data
2586corruption happened:
2587
2588 => imi 40100000
2589
2590 ## Checking Image at 40100000 ...
2591 Image Name: 2.2.13 for initrd on TQM850L
2592 Image Type: PowerPC Linux Kernel Image (gzip compressed)
2593 Data Size: 335725 Bytes = 327 kB = 0 MB
2594 Load Address: 00000000
2595 Entry Point: 0000000c
2596 Verifying Checksum ... OK
2597
2598
wdenkc6097192002-11-03 00:24:07 +00002599Boot Linux:
2600-----------
2601
2602The "bootm" command is used to boot an application that is stored in
2603memory (RAM or Flash). In case of a Linux kernel image, the contents
2604of the "bootargs" environment variable is passed to the kernel as
2605parameters. You can check and modify this variable using the
2606"printenv" and "setenv" commands:
2607
2608
2609 => printenv bootargs
2610 bootargs=root=/dev/ram
2611
2612 => setenv bootargs root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2
2613
2614 => printenv bootargs
2615 bootargs=root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2
2616
2617 => bootm 40020000
2618 ## Booting Linux kernel at 40020000 ...
2619 Image Name: 2.2.13 for NFS on TQM850L
2620 Image Type: PowerPC Linux Kernel Image (gzip compressed)
2621 Data Size: 381681 Bytes = 372 kB = 0 MB
2622 Load Address: 00000000
2623 Entry Point: 0000000c
2624 Verifying Checksum ... OK
2625 Uncompressing Kernel Image ... OK
2626 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
2627 Boot arguments: root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2
2628 time_init: decrementer frequency = 187500000/60
2629 Calibrating delay loop... 49.77 BogoMIPS
2630 Memory: 15208k available (700k kernel code, 444k data, 32k init) [c0000000,c1000000]
2631 ...
2632
2633If you want to boot a Linux kernel with initial ram disk, you pass
wdenk7152b1d2003-09-05 23:19:14 +00002634the memory addresses of both the kernel and the initrd image (PPBCOOT
wdenkc6097192002-11-03 00:24:07 +00002635format!) to the "bootm" command:
2636
2637 => imi 40100000 40200000
2638
2639 ## Checking Image at 40100000 ...
2640 Image Name: 2.2.13 for initrd on TQM850L
2641 Image Type: PowerPC Linux Kernel Image (gzip compressed)
2642 Data Size: 335725 Bytes = 327 kB = 0 MB
2643 Load Address: 00000000
2644 Entry Point: 0000000c
2645 Verifying Checksum ... OK
2646
2647 ## Checking Image at 40200000 ...
2648 Image Name: Simple Ramdisk Image
2649 Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
2650 Data Size: 566530 Bytes = 553 kB = 0 MB
2651 Load Address: 00000000
2652 Entry Point: 00000000
2653 Verifying Checksum ... OK
2654
2655 => bootm 40100000 40200000
2656 ## Booting Linux kernel at 40100000 ...
2657 Image Name: 2.2.13 for initrd on TQM850L
2658 Image Type: PowerPC Linux Kernel Image (gzip compressed)
2659 Data Size: 335725 Bytes = 327 kB = 0 MB
2660 Load Address: 00000000
2661 Entry Point: 0000000c
2662 Verifying Checksum ... OK
2663 Uncompressing Kernel Image ... OK
2664 ## Loading RAMDisk Image at 40200000 ...
2665 Image Name: Simple Ramdisk Image
2666 Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
2667 Data Size: 566530 Bytes = 553 kB = 0 MB
2668 Load Address: 00000000
2669 Entry Point: 00000000
2670 Verifying Checksum ... OK
2671 Loading Ramdisk ... OK
2672 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
2673 Boot arguments: root=/dev/ram
2674 time_init: decrementer frequency = 187500000/60
2675 Calibrating delay loop... 49.77 BogoMIPS
2676 ...
2677 RAMDISK: Compressed image found at block 0
2678 VFS: Mounted root (ext2 filesystem).
2679
2680 bash#
2681
wdenk6069ff22003-02-28 00:49:47 +00002682More About U-Boot Image Types:
2683------------------------------
2684
2685U-Boot supports the following image types:
2686
2687 "Standalone Programs" are directly runnable in the environment
wdenk8bde7f72003-06-27 21:31:46 +00002688 provided by U-Boot; it is expected that (if they behave
2689 well) you can continue to work in U-Boot after return from
2690 the Standalone Program.
wdenk6069ff22003-02-28 00:49:47 +00002691 "OS Kernel Images" are usually images of some Embedded OS which
wdenk8bde7f72003-06-27 21:31:46 +00002692 will take over control completely. Usually these programs
2693 will install their own set of exception handlers, device
2694 drivers, set up the MMU, etc. - this means, that you cannot
2695 expect to re-enter U-Boot except by resetting the CPU.
wdenk6069ff22003-02-28 00:49:47 +00002696 "RAMDisk Images" are more or less just data blocks, and their
wdenk8bde7f72003-06-27 21:31:46 +00002697 parameters (address, size) are passed to an OS kernel that is
2698 being started.
wdenk6069ff22003-02-28 00:49:47 +00002699 "Multi-File Images" contain several images, typically an OS
wdenk8bde7f72003-06-27 21:31:46 +00002700 (Linux) kernel image and one or more data images like
2701 RAMDisks. This construct is useful for instance when you want
2702 to boot over the network using BOOTP etc., where the boot
2703 server provides just a single image file, but you want to get
2704 for instance an OS kernel and a RAMDisk image.
stroesec1551ea2003-04-04 15:53:41 +00002705
wdenk8bde7f72003-06-27 21:31:46 +00002706 "Multi-File Images" start with a list of image sizes, each
2707 image size (in bytes) specified by an "uint32_t" in network
2708 byte order. This list is terminated by an "(uint32_t)0".
2709 Immediately after the terminating 0 follow the images, one by
2710 one, all aligned on "uint32_t" boundaries (size rounded up to
2711 a multiple of 4 bytes).
stroesec1551ea2003-04-04 15:53:41 +00002712
wdenk6069ff22003-02-28 00:49:47 +00002713 "Firmware Images" are binary images containing firmware (like
wdenk8bde7f72003-06-27 21:31:46 +00002714 U-Boot or FPGA images) which usually will be programmed to
2715 flash memory.
stroesec1551ea2003-04-04 15:53:41 +00002716
wdenk6069ff22003-02-28 00:49:47 +00002717 "Script files" are command sequences that will be executed by
wdenk8bde7f72003-06-27 21:31:46 +00002718 U-Boot's command interpreter; this feature is especially
2719 useful when you configure U-Boot to use a real shell (hush)
2720 as command interpreter.
wdenk6069ff22003-02-28 00:49:47 +00002721
wdenkc6097192002-11-03 00:24:07 +00002722
2723Standalone HOWTO:
2724=================
2725
2726One of the features of U-Boot is that you can dynamically load and
2727run "standalone" applications, which can use some resources of
2728U-Boot like console I/O functions or interrupt services.
2729
2730Two simple examples are included with the sources:
2731
2732"Hello World" Demo:
2733-------------------
2734
2735'examples/hello_world.c' contains a small "Hello World" Demo
2736application; it is automatically compiled when you build U-Boot.
2737It's configured to run at address 0x00040004, so you can play with it
2738like that:
2739
2740 => loads
2741 ## Ready for S-Record download ...
2742 ~>examples/hello_world.srec
2743 1 2 3 4 5 6 7 8 9 10 11 ...
2744 [file transfer complete]
2745 [connected]
2746 ## Start Addr = 0x00040004
2747
2748 => go 40004 Hello World! This is a test.
2749 ## Starting application at 0x00040004 ...
2750 Hello World
2751 argc = 7
2752 argv[0] = "40004"
2753 argv[1] = "Hello"
2754 argv[2] = "World!"
2755 argv[3] = "This"
2756 argv[4] = "is"
2757 argv[5] = "a"
2758 argv[6] = "test."
2759 argv[7] = "<NULL>"
2760 Hit any key to exit ...
2761
2762 ## Application terminated, rc = 0x0
2763
2764Another example, which demonstrates how to register a CPM interrupt
2765handler with the U-Boot code, can be found in 'examples/timer.c'.
2766Here, a CPM timer is set up to generate an interrupt every second.
2767The interrupt service routine is trivial, just printing a '.'
2768character, but this is just a demo program. The application can be
2769controlled by the following keys:
2770
2771 ? - print current values og the CPM Timer registers
2772 b - enable interrupts and start timer
2773 e - stop timer and disable interrupts
2774 q - quit application
2775
2776 => loads
2777 ## Ready for S-Record download ...
2778 ~>examples/timer.srec
2779 1 2 3 4 5 6 7 8 9 10 11 ...
2780 [file transfer complete]
2781 [connected]
2782 ## Start Addr = 0x00040004
2783
2784 => go 40004
2785 ## Starting application at 0x00040004 ...
2786 TIMERS=0xfff00980
2787 Using timer 1
2788 tgcr @ 0xfff00980, tmr @ 0xfff00990, trr @ 0xfff00994, tcr @ 0xfff00998, tcn @ 0xfff0099c, ter @ 0xfff009b0
2789
2790Hit 'b':
2791 [q, b, e, ?] Set interval 1000000 us
2792 Enabling timer
2793Hit '?':
2794 [q, b, e, ?] ........
2795 tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0xef6, ter=0x0
2796Hit '?':
2797 [q, b, e, ?] .
2798 tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x2ad4, ter=0x0
2799Hit '?':
2800 [q, b, e, ?] .
2801 tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x1efc, ter=0x0
2802Hit '?':
2803 [q, b, e, ?] .
2804 tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x169d, ter=0x0
2805Hit 'e':
2806 [q, b, e, ?] ...Stopping timer
2807Hit 'q':
2808 [q, b, e, ?] ## Application terminated, rc = 0x0
2809
2810
wdenk85ec0bc2003-03-31 16:34:49 +00002811Minicom warning:
2812================
2813
wdenk7152b1d2003-09-05 23:19:14 +00002814Over time, many people have reported problems when trying to use the
wdenkf07771c2003-05-28 08:06:31 +00002815"minicom" terminal emulation program for serial download. I (wd)
2816consider minicom to be broken, and recommend not to use it. Under
2817Unix, I recommend to use C-Kermit for general purpose use (and
wdenk85ec0bc2003-03-31 16:34:49 +00002818especially for kermit binary protocol download ("loadb" command), and
2819use "cu" for S-Record download ("loads" command).
2820
wdenk52f52c12003-06-19 23:04:19 +00002821Nevertheless, if you absolutely want to use it try adding this
2822configuration to your "File transfer protocols" section:
2823
2824 Name Program Name U/D FullScr IO-Red. Multi
2825 X kermit /usr/bin/kermit -i -l %l -s Y U Y N N
2826 Y kermit /usr/bin/kermit -i -l %l -r N D Y N N
2827
2828
wdenkc6097192002-11-03 00:24:07 +00002829NetBSD Notes:
2830=============
2831
2832Starting at version 0.9.2, U-Boot supports NetBSD both as host
2833(build U-Boot) and target system (boots NetBSD/mpc8xx).
2834
2835Building requires a cross environment; it is known to work on
2836NetBSD/i386 with the cross-powerpc-netbsd-1.3 package (you will also
2837need gmake since the Makefiles are not compatible with BSD make).
2838Note that the cross-powerpc package does not install include files;
2839attempting to build U-Boot will fail because <machine/ansi.h> is
2840missing. This file has to be installed and patched manually:
2841
2842 # cd /usr/pkg/cross/powerpc-netbsd/include
2843 # mkdir powerpc
2844 # ln -s powerpc machine
2845 # cp /usr/src/sys/arch/powerpc/include/ansi.h powerpc/ansi.h
2846 # ${EDIT} powerpc/ansi.h ## must remove __va_list, _BSD_VA_LIST
2847
2848Native builds *don't* work due to incompatibilities between native
2849and U-Boot include files.
2850
2851Booting assumes that (the first part of) the image booted is a
2852stage-2 loader which in turn loads and then invokes the kernel
2853proper. Loader sources will eventually appear in the NetBSD source
2854tree (probably in sys/arc/mpc8xx/stand/u-boot_stage2/); in the
2855meantime, send mail to bruno@exet-ag.de and/or wd@denx.de for
2856details.
2857
2858
2859Implementation Internals:
2860=========================
2861
2862The following is not intended to be a complete description of every
2863implementation detail. However, it should help to understand the
2864inner workings of U-Boot and make it easier to port it to custom
2865hardware.
2866
2867
2868Initial Stack, Global Data:
2869---------------------------
2870
2871The implementation of U-Boot is complicated by the fact that U-Boot
2872starts running out of ROM (flash memory), usually without access to
2873system RAM (because the memory controller is not initialized yet).
2874This means that we don't have writable Data or BSS segments, and BSS
2875is not initialized as zero. To be able to get a C environment working
2876at all, we have to allocate at least a minimal stack. Implementation
2877options for this are defined and restricted by the CPU used: Some CPU
2878models provide on-chip memory (like the IMMR area on MPC8xx and
2879MPC826x processors), on others (parts of) the data cache can be
2880locked as (mis-) used as memory, etc.
2881
wdenk7152b1d2003-09-05 23:19:14 +00002882 Chris Hallinan posted a good summary of these issues to the
wdenk43d96162003-03-06 00:02:04 +00002883 u-boot-users mailing list:
2884
2885 Subject: RE: [U-Boot-Users] RE: More On Memory Bank x (nothingness)?
2886 From: "Chris Hallinan" <clh@net1plus.com>
2887 Date: Mon, 10 Feb 2003 16:43:46 -0500 (22:43 MET)
2888 ...
2889
2890 Correct me if I'm wrong, folks, but the way I understand it
2891 is this: Using DCACHE as initial RAM for Stack, etc, does not
2892 require any physical RAM backing up the cache. The cleverness
2893 is that the cache is being used as a temporary supply of
2894 necessary storage before the SDRAM controller is setup. It's
2895 beyond the scope of this list to expain the details, but you
2896 can see how this works by studying the cache architecture and
2897 operation in the architecture and processor-specific manuals.
2898
2899 OCM is On Chip Memory, which I believe the 405GP has 4K. It
2900 is another option for the system designer to use as an
2901 initial stack/ram area prior to SDRAM being available. Either
2902 option should work for you. Using CS 4 should be fine if your
2903 board designers haven't used it for something that would
2904 cause you grief during the initial boot! It is frequently not
2905 used.
2906
2907 CFG_INIT_RAM_ADDR should be somewhere that won't interfere
2908 with your processor/board/system design. The default value
2909 you will find in any recent u-boot distribution in
2910 Walnut405.h should work for you. I'd set it to a value larger
2911 than your SDRAM module. If you have a 64MB SDRAM module, set
2912 it above 400_0000. Just make sure your board has no resources
2913 that are supposed to respond to that address! That code in
2914 start.S has been around a while and should work as is when
2915 you get the config right.
2916
2917 -Chris Hallinan
2918 DS4.COM, Inc.
2919
wdenkc6097192002-11-03 00:24:07 +00002920It is essential to remember this, since it has some impact on the C
2921code for the initialization procedures:
2922
2923* Initialized global data (data segment) is read-only. Do not attempt
2924 to write it.
2925
2926* Do not use any unitialized global data (or implicitely initialized
2927 as zero data - BSS segment) at all - this is undefined, initiali-
wdenk7152b1d2003-09-05 23:19:14 +00002928 zation is performed later (when relocating to RAM).
wdenkc6097192002-11-03 00:24:07 +00002929
wdenk7152b1d2003-09-05 23:19:14 +00002930* Stack space is very limited. Avoid big data buffers or things like
wdenkc6097192002-11-03 00:24:07 +00002931 that.
2932
2933Having only the stack as writable memory limits means we cannot use
2934normal global data to share information beween the code. But it
2935turned out that the implementation of U-Boot can be greatly
2936simplified by making a global data structure (gd_t) available to all
2937functions. We could pass a pointer to this data as argument to _all_
2938functions, but this would bloat the code. Instead we use a feature of
2939the GCC compiler (Global Register Variables) to share the data: we
2940place a pointer (gd) to the global data into a register which we
2941reserve for this purpose.
2942
wdenk7152b1d2003-09-05 23:19:14 +00002943When choosing a register for such a purpose we are restricted by the
wdenkc6097192002-11-03 00:24:07 +00002944relevant (E)ABI specifications for the current architecture, and by
2945GCC's implementation.
2946
2947For PowerPC, the following registers have specific use:
2948 R1: stack pointer
2949 R2: TOC pointer
2950 R3-R4: parameter passing and return values
2951 R5-R10: parameter passing
2952 R13: small data area pointer
2953 R30: GOT pointer
2954 R31: frame pointer
2955
2956 (U-Boot also uses R14 as internal GOT pointer.)
2957
2958 ==> U-Boot will use R29 to hold a pointer to the global data
2959
2960 Note: on PPC, we could use a static initializer (since the
2961 address of the global data structure is known at compile time),
2962 but it turned out that reserving a register results in somewhat
2963 smaller code - although the code savings are not that big (on
2964 average for all boards 752 bytes for the whole U-Boot image,
2965 624 text + 127 data).
2966
2967On ARM, the following registers are used:
2968
2969 R0: function argument word/integer result
2970 R1-R3: function argument word
2971 R9: GOT pointer
2972 R10: stack limit (used only if stack checking if enabled)
2973 R11: argument (frame) pointer
2974 R12: temporary workspace
2975 R13: stack pointer
2976 R14: link register
2977 R15: program counter
2978
2979 ==> U-Boot will use R8 to hold a pointer to the global data
2980
2981
wdenkc6097192002-11-03 00:24:07 +00002982Memory Management:
2983------------------
2984
2985U-Boot runs in system state and uses physical addresses, i.e. the
2986MMU is not used either for address mapping nor for memory protection.
2987
2988The available memory is mapped to fixed addresses using the memory
2989controller. In this process, a contiguous block is formed for each
2990memory type (Flash, SDRAM, SRAM), even when it consists of several
2991physical memory banks.
2992
2993U-Boot is installed in the first 128 kB of the first Flash bank (on
2994TQM8xxL modules this is the range 0x40000000 ... 0x4001FFFF). After
2995booting and sizing and initializing DRAM, the code relocates itself
2996to the upper end of DRAM. Immediately below the U-Boot code some
2997memory is reserved for use by malloc() [see CFG_MALLOC_LEN
2998configuration setting]. Below that, a structure with global Board
2999Info data is placed, followed by the stack (growing downward).
3000
3001Additionally, some exception handler code is copied to the low 8 kB
3002of DRAM (0x00000000 ... 0x00001FFF).
3003
3004So a typical memory configuration with 16 MB of DRAM could look like
3005this:
3006
3007 0x0000 0000 Exception Vector code
3008 :
3009 0x0000 1FFF
3010 0x0000 2000 Free for Application Use
3011 :
3012 :
3013
3014 :
3015 :
3016 0x00FB FF20 Monitor Stack (Growing downward)
3017 0x00FB FFAC Board Info Data and permanent copy of global data
3018 0x00FC 0000 Malloc Arena
3019 :
3020 0x00FD FFFF
3021 0x00FE 0000 RAM Copy of Monitor Code
3022 ... eventually: LCD or video framebuffer
3023 ... eventually: pRAM (Protected RAM - unchanged by reset)
3024 0x00FF FFFF [End of RAM]
3025
3026
3027System Initialization:
3028----------------------
3029
3030In the reset configuration, U-Boot starts at the reset entry point
3031(on most PowerPC systens at address 0x00000100). Because of the reset
3032configuration for CS0# this is a mirror of the onboard Flash memory.
wdenk7152b1d2003-09-05 23:19:14 +00003033To be able to re-map memory U-Boot then jumps to its link address.
wdenkc6097192002-11-03 00:24:07 +00003034To be able to implement the initialization code in C, a (small!)
3035initial stack is set up in the internal Dual Ported RAM (in case CPUs
3036which provide such a feature like MPC8xx or MPC8260), or in a locked
3037part of the data cache. After that, U-Boot initializes the CPU core,
3038the caches and the SIU.
3039
3040Next, all (potentially) available memory banks are mapped using a
3041preliminary mapping. For example, we put them on 512 MB boundaries
3042(multiples of 0x20000000: SDRAM on 0x00000000 and 0x20000000, Flash
3043on 0x40000000 and 0x60000000, SRAM on 0x80000000). Then UPM A is
3044programmed for SDRAM access. Using the temporary configuration, a
3045simple memory test is run that determines the size of the SDRAM
3046banks.
3047
3048When there is more than one SDRAM bank, and the banks are of
wdenk7152b1d2003-09-05 23:19:14 +00003049different size, the largest is mapped first. For equal size, the first
wdenkc6097192002-11-03 00:24:07 +00003050bank (CS2#) is mapped first. The first mapping is always for address
30510x00000000, with any additional banks following immediately to create
3052contiguous memory starting from 0.
3053
3054Then, the monitor installs itself at the upper end of the SDRAM area
3055and allocates memory for use by malloc() and for the global Board
3056Info data; also, the exception vector code is copied to the low RAM
3057pages, and the final stack is set up.
3058
3059Only after this relocation will you have a "normal" C environment;
3060until that you are restricted in several ways, mostly because you are
3061running from ROM, and because the code will have to be relocated to a
3062new address in RAM.
3063
3064
3065U-Boot Porting Guide:
3066----------------------
3067
3068[Based on messages by Jerry Van Baren in the U-Boot-Users mailing
wdenk6aff3112002-12-17 01:51:00 +00003069list, October 2002]
wdenkc6097192002-11-03 00:24:07 +00003070
3071
3072int main (int argc, char *argv[])
3073{
3074 sighandler_t no_more_time;
3075
3076 signal (SIGALRM, no_more_time);
3077 alarm (PROJECT_DEADLINE - toSec (3 * WEEK));
3078
3079 if (available_money > available_manpower) {
3080 pay consultant to port U-Boot;
3081 return 0;
3082 }
3083
3084 Download latest U-Boot source;
3085
wdenk6aff3112002-12-17 01:51:00 +00003086 Subscribe to u-boot-users mailing list;
3087
wdenkc6097192002-11-03 00:24:07 +00003088 if (clueless) {
3089 email ("Hi, I am new to U-Boot, how do I get started?");
3090 }
3091
3092 while (learning) {
3093 Read the README file in the top level directory;
3094 Read http://www.denx.de/re/DPLG.html
3095 Read the source, Luke;
3096 }
3097
3098 if (available_money > toLocalCurrency ($2500)) {
3099 Buy a BDI2000;
3100 } else {
3101 Add a lot of aggravation and time;
3102 }
3103
3104 Create your own board support subdirectory;
3105
wdenk6aff3112002-12-17 01:51:00 +00003106 Create your own board config file;
3107
wdenkc6097192002-11-03 00:24:07 +00003108 while (!running) {
3109 do {
3110 Add / modify source code;
3111 } until (compiles);
3112 Debug;
3113 if (clueless)
3114 email ("Hi, I am having problems...");
3115 }
3116 Send patch file to Wolfgang;
3117
3118 return 0;
3119}
3120
3121void no_more_time (int sig)
3122{
3123 hire_a_guru();
3124}
3125
3126
wdenkc6097192002-11-03 00:24:07 +00003127Coding Standards:
3128-----------------
3129
3130All contributions to U-Boot should conform to the Linux kernel
3131coding style; see the file "Documentation/CodingStyle" in your Linux
3132kernel source directory.
3133
3134Please note that U-Boot is implemented in C (and to some small parts
3135in Assembler); no C++ is used, so please do not use C++ style
3136comments (//) in your code.
3137
3138Submissions which do not conform to the standards may be returned
3139with a request to reformat the changes.
3140
3141
3142Submitting Patches:
3143-------------------
3144
3145Since the number of patches for U-Boot is growing, we need to
3146establish some rules. Submissions which do not conform to these rules
3147may be rejected, even when they contain important and valuable stuff.
3148
3149
3150When you send a patch, please include the following information with
3151it:
3152
3153* For bug fixes: a description of the bug and how your patch fixes
3154 this bug. Please try to include a way of demonstrating that the
3155 patch actually fixes something.
3156
3157* For new features: a description of the feature and your
3158 implementation.
3159
3160* A CHANGELOG entry as plaintext (separate from the patch)
3161
3162* For major contributions, your entry to the CREDITS file
3163
3164* When you add support for a new board, don't forget to add this
3165 board to the MAKEALL script, too.
3166
3167* If your patch adds new configuration options, don't forget to
3168 document these in the README file.
3169
3170* The patch itself. If you are accessing the CVS repository use "cvs
3171 update; cvs diff -puRN"; else, use "diff -purN OLD NEW". If your
3172 version of diff does not support these options, then get the latest
3173 version of GNU diff.
3174
wdenk6dff5522003-07-15 07:45:49 +00003175 The current directory when running this command shall be the top
3176 level directory of the U-Boot source tree, or it's parent directory
3177 (i. e. please make sure that your patch includes sufficient
3178 directory information for the affected files).
3179
wdenkc6097192002-11-03 00:24:07 +00003180 We accept patches as plain text, MIME attachments or as uuencoded
3181 gzipped text.
3182
wdenk52f52c12003-06-19 23:04:19 +00003183* If one logical set of modifications affects or creates several
3184 files, all these changes shall be submitted in a SINGLE patch file.
3185
3186* Changesets that contain different, unrelated modifications shall be
3187 submitted as SEPARATE patches, one patch per changeset.
wdenk8bde7f72003-06-27 21:31:46 +00003188
wdenk52f52c12003-06-19 23:04:19 +00003189
wdenkc6097192002-11-03 00:24:07 +00003190Notes:
3191
3192* Before sending the patch, run the MAKEALL script on your patched
3193 source tree and make sure that no errors or warnings are reported
3194 for any of the boards.
3195
3196* Keep your modifications to the necessary minimum: A patch
3197 containing several unrelated changes or arbitrary reformats will be
3198 returned with a request to re-formatting / split it.
3199
3200* If you modify existing code, make sure that your new code does not
3201 add to the memory footprint of the code ;-) Small is beautiful!
3202 When adding new features, these should compile conditionally only
3203 (using #ifdef), and the resulting code with the new feature
3204 disabled must not need more memory than the old code without your
3205 modification.