Eric Lee / smarc-uboot

Download as
Browse Code ยป

Commit cf946c6d09938e1e6ef01a7488c6e75a1cf71c47

Authored by Lei Wen
Committed by Albert Aribaud
1 parent 495df3bad9
Exists in master and in 54 other branches 8qm-imx_v2020.04_5.4.70_2.3.0, emb_lf_v2022.04, imx_v2015.04_4.1.15_1.0.0_ga, pitx_8mp_lf_v2020.04, smarc-8m-android-10.0.0_2.6.0, smarc-8m-android-11.0.0_2.0.0, smarc-8mp-android-11.0.0_2.0.0, smarc-emmc-imx_v2014.04_3.10.53_1.1.0_ga, smarc-emmc-imx_v2014.04_3.14.28_1.0.0_ga, smarc-imx-l5.0.0_1.0.0-ga, smarc-imx6_v2018.03_4.14.98_2.0.0_ga, smarc-imx7_v2017.03_4.9.11_1.0.0_ga, smarc-imx7_v2018.03_4.14.98_2.0.0_ga, smarc-imx_v2014.04_3.14.28_1.0.0_ga, smarc-imx_v2015.04_4.1.15_1.0.0_ga, smarc-imx_v2017.03_4.9.11_1.0.0_ga, smarc-imx_v2017.03_4.9.88_2.0.0_ga, smarc-imx_v2017.03_o8.1.0_1.3.0_8m, smarc-imx_v2018.03_4.14.78_1.0.0_ga, smarc-m6.0.1_2.1.0-ga, smarc-n7.1.2_2.0.0-ga, smarc-rel_imx_4.1.15_2.0.0_ga, smarc_8m-imx_v2018.03_4.14.98_2.0.0_ga, smarc_8m-imx_v2019.04_4.19.35_1.1.0, smarc_8m_00d0-imx_v2018.03_4.14.98_2.0.0_ga, smarc_8mm-imx_v2018.03_4.14.98_2.0.0_ga, smarc_8mm-imx_v2019.04_4.19.35_1.1.0, smarc_8mm-imx_v2020.04_5.4.24_2.1.0, smarc_8mp_lf_v2020.04, smarc_8mq-imx_v2020.04_5.4.24_2.1.0, smarc_8mq_lf_v2020.04, ti-u-boot-2015.07, u-boot-2013.01.y, v2013.10, v2013.10-smarct33, v2013.10-smartmen, v2014.01, v2014.04, v2014.04-smarct33, v2014.04-smarct33-emmc, v2014.04-smartmen, v2014.07, v2014.07-smarct33, v2014.07-smartmen, v2015.07-smarct33, v2015.07-smarct33-emmc, v2015.07-smarct4x, v2016.05-dlt, v2016.05-smarct3x, v2016.05-smarct3x-emmc, v2016.05-smarct4x, v2017.01-smarct3x, v2017.01-smarct3x-emmc, v2017.01-smarct4x

mv: seperate kirkwood and armada from common setting 

Since there are lots of difference between kirkwood and armada series,
it is better to seperate them but still keep the most common file
shared by all marvell platform in the mv-common configure file.

This patch move the kirkwood only driver definitoin in mv-common to
the <soc_name>/config.h.

This patch is tested with compilation for armada100 and guruplug.

Signed-off-by: Lei Wen <leiwen@marvell.com>

Showing 5 changed files with 223 additions and 126 deletions Inline Diff

1 # 1 #
2 # (C) Copyright 2000 - 2009 2 # (C) Copyright 2000 - 2009
3 # Wolfgang Denk, DENX Software Engineering, wd@denx.de. 3 # Wolfgang Denk, DENX Software Engineering, wd@denx.de.
4 # 4 #
5 # See file CREDITS for list of people who contributed to this 5 # See file CREDITS for list of people who contributed to this
6 # project. 6 # project.
7 # 7 #
8 # This program is free software; you can redistribute it and/or 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 9 # modify it under the terms of the GNU General Public License as
10 # published by the Free Software Foundation; either version 2 of 10 # published by the Free Software Foundation; either version 2 of
11 # the License, or (at your option) any later version. 11 # the License, or (at your option) any later version.
12 # 12 #
13 # This program is distributed in the hope that it will be useful, 13 # This program is distributed in the hope that it will be useful,
14 # but WITHOUT ANY WARRANTY; without even the implied warranty of 14 # but WITHOUT ANY WARRANTY; without even the implied warranty of
15 # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 15 # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
16 # GNU General Public License for more details. 16 # GNU General Public License for more details.
17 # 17 #
18 # You should have received a copy of the GNU General Public License 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 19 # along with this program; if not, write to the Free Software
20 # Foundation, Inc., 59 Temple Place, Suite 330, Boston, 20 # Foundation, Inc., 59 Temple Place, Suite 330, Boston,
21 # MA 02111-1307 USA 21 # MA 02111-1307 USA
22 # 22 #
23 23
24 Summary: 24 Summary:
25 ======== 25 ========
26 26
27 This directory contains the source code for U-Boot, a boot loader for 27 This directory contains the source code for U-Boot, a boot loader for
28 Embedded boards based on PowerPC, ARM, MIPS and several other 28 Embedded boards based on PowerPC, ARM, MIPS and several other
29 processors, which can be installed in a boot ROM and used to 29 processors, which can be installed in a boot ROM and used to
30 initialize and test the hardware or to download and run application 30 initialize and test the hardware or to download and run application
31 code. 31 code.
32 32
33 The development of U-Boot is closely related to Linux: some parts of 33 The development of U-Boot is closely related to Linux: some parts of
34 the source code originate in the Linux source tree, we have some 34 the source code originate in the Linux source tree, we have some
35 header files in common, and special provision has been made to 35 header files in common, and special provision has been made to
36 support booting of Linux images. 36 support booting of Linux images.
37 37
38 Some attention has been paid to make this software easily 38 Some attention has been paid to make this software easily
39 configurable and extendable. For instance, all monitor commands are 39 configurable and extendable. For instance, all monitor commands are
40 implemented with the same call interface, so that it's very easy to 40 implemented with the same call interface, so that it's very easy to
41 add new commands. Also, instead of permanently adding rarely used 41 add new commands. Also, instead of permanently adding rarely used
42 code (for instance hardware test utilities) to the monitor, you can 42 code (for instance hardware test utilities) to the monitor, you can
43 load and run it dynamically. 43 load and run it dynamically.
44 44
45 45
46 Status: 46 Status:
47 ======= 47 =======
48 48
49 In general, all boards for which a configuration option exists in the 49 In general, all boards for which a configuration option exists in the
50 Makefile have been tested to some extent and can be considered 50 Makefile have been tested to some extent and can be considered
51 "working". In fact, many of them are used in production systems. 51 "working". In fact, many of them are used in production systems.
52 52
53 In case of problems see the CHANGELOG and CREDITS files to find out 53 In case of problems see the CHANGELOG and CREDITS files to find out
54 who contributed the specific port. The MAINTAINERS file lists board 54 who contributed the specific port. The MAINTAINERS file lists board
55 maintainers. 55 maintainers.
56 56
57 57
58 Where to get help: 58 Where to get help:
59 ================== 59 ==================
60 60
61 In case you have questions about, problems with or contributions for 61 In case you have questions about, problems with or contributions for
62 U-Boot you should send a message to the U-Boot mailing list at 62 U-Boot you should send a message to the U-Boot mailing list at
63 <u-boot@lists.denx.de>. There is also an archive of previous traffic 63 <u-boot@lists.denx.de>. There is also an archive of previous traffic
64 on the mailing list - please search the archive before asking FAQ's. 64 on the mailing list - please search the archive before asking FAQ's.
65 Please see http://lists.denx.de/pipermail/u-boot and 65 Please see http://lists.denx.de/pipermail/u-boot and
66 http://dir.gmane.org/gmane.comp.boot-loaders.u-boot 66 http://dir.gmane.org/gmane.comp.boot-loaders.u-boot
67 67
68 68
69 Where to get source code: 69 Where to get source code:
70 ========================= 70 =========================
71 71
72 The U-Boot source code is maintained in the git repository at 72 The U-Boot source code is maintained in the git repository at
73 git://www.denx.de/git/u-boot.git ; you can browse it online at 73 git://www.denx.de/git/u-boot.git ; you can browse it online at
74 http://www.denx.de/cgi-bin/gitweb.cgi?p=u-boot.git;a=summary 74 http://www.denx.de/cgi-bin/gitweb.cgi?p=u-boot.git;a=summary
75 75
76 The "snapshot" links on this page allow you to download tarballs of 76 The "snapshot" links on this page allow you to download tarballs of
77 any version you might be interested in. Official releases are also 77 any version you might be interested in. Official releases are also
78 available for FTP download from the ftp://ftp.denx.de/pub/u-boot/ 78 available for FTP download from the ftp://ftp.denx.de/pub/u-boot/
79 directory. 79 directory.
80 80
81 Pre-built (and tested) images are available from 81 Pre-built (and tested) images are available from
82 ftp://ftp.denx.de/pub/u-boot/images/ 82 ftp://ftp.denx.de/pub/u-boot/images/
83 83
84 84
85 Where we come from: 85 Where we come from:
86 =================== 86 ===================
87 87
88 - start from 8xxrom sources 88 - start from 8xxrom sources
89 - create PPCBoot project (http://sourceforge.net/projects/ppcboot) 89 - create PPCBoot project (http://sourceforge.net/projects/ppcboot)
90 - clean up code 90 - clean up code
91 - make it easier to add custom boards 91 - make it easier to add custom boards
92 - make it possible to add other [PowerPC] CPUs 92 - make it possible to add other [PowerPC] CPUs
93 - extend functions, especially: 93 - extend functions, especially:
94 * Provide extended interface to Linux boot loader 94 * Provide extended interface to Linux boot loader
95 * S-Record download 95 * S-Record download
96 * network boot 96 * network boot
97 * PCMCIA / CompactFlash / ATA disk / SCSI ... boot 97 * PCMCIA / CompactFlash / ATA disk / SCSI ... boot
98 - create ARMBoot project (http://sourceforge.net/projects/armboot) 98 - create ARMBoot project (http://sourceforge.net/projects/armboot)
99 - add other CPU families (starting with ARM) 99 - add other CPU families (starting with ARM)
100 - create U-Boot project (http://sourceforge.net/projects/u-boot) 100 - create U-Boot project (http://sourceforge.net/projects/u-boot)
101 - current project page: see http://www.denx.de/wiki/U-Boot 101 - current project page: see http://www.denx.de/wiki/U-Boot
102 102
103 103
104 Names and Spelling: 104 Names and Spelling:
105 =================== 105 ===================
106 106
107 The "official" name of this project is "Das U-Boot". The spelling 107 The "official" name of this project is "Das U-Boot". The spelling
108 "U-Boot" shall be used in all written text (documentation, comments 108 "U-Boot" shall be used in all written text (documentation, comments
109 in source files etc.). Example: 109 in source files etc.). Example:
110 110
111 This is the README file for the U-Boot project. 111 This is the README file for the U-Boot project.
112 112
113 File names etc. shall be based on the string "u-boot". Examples: 113 File names etc. shall be based on the string "u-boot". Examples:
114 114
115 include/asm-ppc/u-boot.h 115 include/asm-ppc/u-boot.h
116 116
117 #include <asm/u-boot.h> 117 #include <asm/u-boot.h>
118 118
119 Variable names, preprocessor constants etc. shall be either based on 119 Variable names, preprocessor constants etc. shall be either based on
120 the string "u_boot" or on "U_BOOT". Example: 120 the string "u_boot" or on "U_BOOT". Example:
121 121
122 U_BOOT_VERSION u_boot_logo 122 U_BOOT_VERSION u_boot_logo
123 IH_OS_U_BOOT u_boot_hush_start 123 IH_OS_U_BOOT u_boot_hush_start
124 124
125 125
126 Versioning: 126 Versioning:
127 =========== 127 ===========
128 128
129 Starting with the release in October 2008, the names of the releases 129 Starting with the release in October 2008, the names of the releases
130 were changed from numerical release numbers without deeper meaning 130 were changed from numerical release numbers without deeper meaning
131 into a time stamp based numbering. Regular releases are identified by 131 into a time stamp based numbering. Regular releases are identified by
132 names consisting of the calendar year and month of the release date. 132 names consisting of the calendar year and month of the release date.
133 Additional fields (if present) indicate release candidates or bug fix 133 Additional fields (if present) indicate release candidates or bug fix
134 releases in "stable" maintenance trees. 134 releases in "stable" maintenance trees.
135 135
136 Examples: 136 Examples:
137 U-Boot v2009.11 - Release November 2009 137 U-Boot v2009.11 - Release November 2009
138 U-Boot v2009.11.1 - Release 1 in version November 2009 stable tree 138 U-Boot v2009.11.1 - Release 1 in version November 2009 stable tree
139 U-Boot v2010.09-rc1 - Release candiate 1 for September 2010 release 139 U-Boot v2010.09-rc1 - Release candiate 1 for September 2010 release
140 140
141 141
142 Directory Hierarchy: 142 Directory Hierarchy:
143 ==================== 143 ====================
144 144
145 /arch Architecture specific files 145 /arch Architecture specific files
146 /arm Files generic to ARM architecture 146 /arm Files generic to ARM architecture
147 /cpu CPU specific files 147 /cpu CPU specific files
148 /arm720t Files specific to ARM 720 CPUs 148 /arm720t Files specific to ARM 720 CPUs
149 /arm920t Files specific to ARM 920 CPUs 149 /arm920t Files specific to ARM 920 CPUs
150 /at91rm9200 Files specific to Atmel AT91RM9200 CPU 150 /at91rm9200 Files specific to Atmel AT91RM9200 CPU
151 /imx Files specific to Freescale MC9328 i.MX CPUs 151 /imx Files specific to Freescale MC9328 i.MX CPUs
152 /s3c24x0 Files specific to Samsung S3C24X0 CPUs 152 /s3c24x0 Files specific to Samsung S3C24X0 CPUs
153 /arm925t Files specific to ARM 925 CPUs 153 /arm925t Files specific to ARM 925 CPUs
154 /arm926ejs Files specific to ARM 926 CPUs 154 /arm926ejs Files specific to ARM 926 CPUs
155 /arm1136 Files specific to ARM 1136 CPUs 155 /arm1136 Files specific to ARM 1136 CPUs
156 /ixp Files specific to Intel XScale IXP CPUs 156 /ixp Files specific to Intel XScale IXP CPUs
157 /pxa Files specific to Intel XScale PXA CPUs 157 /pxa Files specific to Intel XScale PXA CPUs
158 /s3c44b0 Files specific to Samsung S3C44B0 CPUs 158 /s3c44b0 Files specific to Samsung S3C44B0 CPUs
159 /sa1100 Files specific to Intel StrongARM SA1100 CPUs 159 /sa1100 Files specific to Intel StrongARM SA1100 CPUs
160 /lib Architecture specific library files 160 /lib Architecture specific library files
161 /avr32 Files generic to AVR32 architecture 161 /avr32 Files generic to AVR32 architecture
162 /cpu CPU specific files 162 /cpu CPU specific files
163 /lib Architecture specific library files 163 /lib Architecture specific library files
164 /blackfin Files generic to Analog Devices Blackfin architecture 164 /blackfin Files generic to Analog Devices Blackfin architecture
165 /cpu CPU specific files 165 /cpu CPU specific files
166 /lib Architecture specific library files 166 /lib Architecture specific library files
167 /i386 Files generic to i386 architecture 167 /i386 Files generic to i386 architecture
168 /cpu CPU specific files 168 /cpu CPU specific files
169 /lib Architecture specific library files 169 /lib Architecture specific library files
170 /m68k Files generic to m68k architecture 170 /m68k Files generic to m68k architecture
171 /cpu CPU specific files 171 /cpu CPU specific files
172 /mcf52x2 Files specific to Freescale ColdFire MCF52x2 CPUs 172 /mcf52x2 Files specific to Freescale ColdFire MCF52x2 CPUs
173 /mcf5227x Files specific to Freescale ColdFire MCF5227x CPUs 173 /mcf5227x Files specific to Freescale ColdFire MCF5227x CPUs
174 /mcf532x Files specific to Freescale ColdFire MCF5329 CPUs 174 /mcf532x Files specific to Freescale ColdFire MCF5329 CPUs
175 /mcf5445x Files specific to Freescale ColdFire MCF5445x CPUs 175 /mcf5445x Files specific to Freescale ColdFire MCF5445x CPUs
176 /mcf547x_8x Files specific to Freescale ColdFire MCF547x_8x CPUs 176 /mcf547x_8x Files specific to Freescale ColdFire MCF547x_8x CPUs
177 /lib Architecture specific library files 177 /lib Architecture specific library files
178 /microblaze Files generic to microblaze architecture 178 /microblaze Files generic to microblaze architecture
179 /cpu CPU specific files 179 /cpu CPU specific files
180 /lib Architecture specific library files 180 /lib Architecture specific library files
181 /mips Files generic to MIPS architecture 181 /mips Files generic to MIPS architecture
182 /cpu CPU specific files 182 /cpu CPU specific files
183 /lib Architecture specific library files 183 /lib Architecture specific library files
184 /nios2 Files generic to Altera NIOS2 architecture 184 /nios2 Files generic to Altera NIOS2 architecture
185 /cpu CPU specific files 185 /cpu CPU specific files
186 /lib Architecture specific library files 186 /lib Architecture specific library files
187 /powerpc Files generic to PowerPC architecture 187 /powerpc Files generic to PowerPC architecture
188 /cpu CPU specific files 188 /cpu CPU specific files
189 /74xx_7xx Files specific to Freescale MPC74xx and 7xx CPUs 189 /74xx_7xx Files specific to Freescale MPC74xx and 7xx CPUs
190 /mpc5xx Files specific to Freescale MPC5xx CPUs 190 /mpc5xx Files specific to Freescale MPC5xx CPUs
191 /mpc5xxx Files specific to Freescale MPC5xxx CPUs 191 /mpc5xxx Files specific to Freescale MPC5xxx CPUs
192 /mpc8xx Files specific to Freescale MPC8xx CPUs 192 /mpc8xx Files specific to Freescale MPC8xx CPUs
193 /mpc8220 Files specific to Freescale MPC8220 CPUs 193 /mpc8220 Files specific to Freescale MPC8220 CPUs
194 /mpc824x Files specific to Freescale MPC824x CPUs 194 /mpc824x Files specific to Freescale MPC824x CPUs
195 /mpc8260 Files specific to Freescale MPC8260 CPUs 195 /mpc8260 Files specific to Freescale MPC8260 CPUs
196 /mpc85xx Files specific to Freescale MPC85xx CPUs 196 /mpc85xx Files specific to Freescale MPC85xx CPUs
197 /ppc4xx Files specific to AMCC PowerPC 4xx CPUs 197 /ppc4xx Files specific to AMCC PowerPC 4xx CPUs
198 /lib Architecture specific library files 198 /lib Architecture specific library files
199 /sh Files generic to SH architecture 199 /sh Files generic to SH architecture
200 /cpu CPU specific files 200 /cpu CPU specific files
201 /sh2 Files specific to sh2 CPUs 201 /sh2 Files specific to sh2 CPUs
202 /sh3 Files specific to sh3 CPUs 202 /sh3 Files specific to sh3 CPUs
203 /sh4 Files specific to sh4 CPUs 203 /sh4 Files specific to sh4 CPUs
204 /lib Architecture specific library files 204 /lib Architecture specific library files
205 /sparc Files generic to SPARC architecture 205 /sparc Files generic to SPARC architecture
206 /cpu CPU specific files 206 /cpu CPU specific files
207 /leon2 Files specific to Gaisler LEON2 SPARC CPU 207 /leon2 Files specific to Gaisler LEON2 SPARC CPU
208 /leon3 Files specific to Gaisler LEON3 SPARC CPU 208 /leon3 Files specific to Gaisler LEON3 SPARC CPU
209 /lib Architecture specific library files 209 /lib Architecture specific library files
210 /api Machine/arch independent API for external apps 210 /api Machine/arch independent API for external apps
211 /board Board dependent files 211 /board Board dependent files
212 /common Misc architecture independent functions 212 /common Misc architecture independent functions
213 /disk Code for disk drive partition handling 213 /disk Code for disk drive partition handling
214 /doc Documentation (don't expect too much) 214 /doc Documentation (don't expect too much)
215 /drivers Commonly used device drivers 215 /drivers Commonly used device drivers
216 /examples Example code for standalone applications, etc. 216 /examples Example code for standalone applications, etc.
217 /fs Filesystem code (cramfs, ext2, jffs2, etc.) 217 /fs Filesystem code (cramfs, ext2, jffs2, etc.)
218 /include Header Files 218 /include Header Files
219 /lib Files generic to all architectures 219 /lib Files generic to all architectures
220 /libfdt Library files to support flattened device trees 220 /libfdt Library files to support flattened device trees
221 /lzma Library files to support LZMA decompression 221 /lzma Library files to support LZMA decompression
222 /lzo Library files to support LZO decompression 222 /lzo Library files to support LZO decompression
223 /net Networking code 223 /net Networking code
224 /post Power On Self Test 224 /post Power On Self Test
225 /rtc Real Time Clock drivers 225 /rtc Real Time Clock drivers
226 /tools Tools to build S-Record or U-Boot images, etc. 226 /tools Tools to build S-Record or U-Boot images, etc.
227 227
228 Software Configuration: 228 Software Configuration:
229 ======================= 229 =======================
230 230
231 Configuration is usually done using C preprocessor defines; the 231 Configuration is usually done using C preprocessor defines; the
232 rationale behind that is to avoid dead code whenever possible. 232 rationale behind that is to avoid dead code whenever possible.
233 233
234 There are two classes of configuration variables: 234 There are two classes of configuration variables:
235 235
236 * Configuration _OPTIONS_: 236 * Configuration _OPTIONS_:
237 These are selectable by the user and have names beginning with 237 These are selectable by the user and have names beginning with
238 "CONFIG_". 238 "CONFIG_".
239 239
240 * Configuration _SETTINGS_: 240 * Configuration _SETTINGS_:
241 These depend on the hardware etc. and should not be meddled with if 241 These depend on the hardware etc. and should not be meddled with if
242 you don't know what you're doing; they have names beginning with 242 you don't know what you're doing; they have names beginning with
243 "CONFIG_SYS_". 243 "CONFIG_SYS_".
244 244
245 Later we will add a configuration tool - probably similar to or even 245 Later we will add a configuration tool - probably similar to or even
246 identical to what's used for the Linux kernel. Right now, we have to 246 identical to what's used for the Linux kernel. Right now, we have to
247 do the configuration by hand, which means creating some symbolic 247 do the configuration by hand, which means creating some symbolic
248 links and editing some configuration files. We use the TQM8xxL boards 248 links and editing some configuration files. We use the TQM8xxL boards
249 as an example here. 249 as an example here.
250 250
251 251
252 Selection of Processor Architecture and Board Type: 252 Selection of Processor Architecture and Board Type:
253 --------------------------------------------------- 253 ---------------------------------------------------
254 254
255 For all supported boards there are ready-to-use default 255 For all supported boards there are ready-to-use default
256 configurations available; just type "make <board_name>_config". 256 configurations available; just type "make <board_name>_config".
257 257
258 Example: For a TQM823L module type: 258 Example: For a TQM823L module type:
259 259
260 cd u-boot 260 cd u-boot
261 make TQM823L_config 261 make TQM823L_config
262 262
263 For the Cogent platform, you need to specify the CPU type as well; 263 For the Cogent platform, you need to specify the CPU type as well;
264 e.g. "make cogent_mpc8xx_config". And also configure the cogent 264 e.g. "make cogent_mpc8xx_config". And also configure the cogent
265 directory according to the instructions in cogent/README. 265 directory according to the instructions in cogent/README.
266 266
267 267
268 Configuration Options: 268 Configuration Options:
269 ---------------------- 269 ----------------------
270 270
271 Configuration depends on the combination of board and CPU type; all 271 Configuration depends on the combination of board and CPU type; all
272 such information is kept in a configuration file 272 such information is kept in a configuration file
273 "include/configs/<board_name>.h". 273 "include/configs/<board_name>.h".
274 274
275 Example: For a TQM823L module, all configuration settings are in 275 Example: For a TQM823L module, all configuration settings are in
276 "include/configs/TQM823L.h". 276 "include/configs/TQM823L.h".
277 277
278 278
279 Many of the options are named exactly as the corresponding Linux 279 Many of the options are named exactly as the corresponding Linux
280 kernel configuration options. The intention is to make it easier to 280 kernel configuration options. The intention is to make it easier to
281 build a config tool - later. 281 build a config tool - later.
282 282
283 283
284 The following options need to be configured: 284 The following options need to be configured:
285 285
286 - CPU Type: Define exactly one, e.g. CONFIG_MPC85XX. 286 - CPU Type: Define exactly one, e.g. CONFIG_MPC85XX.
287 287
288 - Board Type: Define exactly one, e.g. CONFIG_MPC8540ADS. 288 - Board Type: Define exactly one, e.g. CONFIG_MPC8540ADS.
289 289
290 - CPU Daughterboard Type: (if CONFIG_ATSTK1000 is defined) 290 - CPU Daughterboard Type: (if CONFIG_ATSTK1000 is defined)
291 Define exactly one, e.g. CONFIG_ATSTK1002 291 Define exactly one, e.g. CONFIG_ATSTK1002
292 292
293 - CPU Module Type: (if CONFIG_COGENT is defined) 293 - CPU Module Type: (if CONFIG_COGENT is defined)
294 Define exactly one of 294 Define exactly one of
295 CONFIG_CMA286_60_OLD 295 CONFIG_CMA286_60_OLD
296 --- FIXME --- not tested yet: 296 --- FIXME --- not tested yet:
297 CONFIG_CMA286_60, CONFIG_CMA286_21, CONFIG_CMA286_60P, 297 CONFIG_CMA286_60, CONFIG_CMA286_21, CONFIG_CMA286_60P,
298 CONFIG_CMA287_23, CONFIG_CMA287_50 298 CONFIG_CMA287_23, CONFIG_CMA287_50
299 299
300 - Motherboard Type: (if CONFIG_COGENT is defined) 300 - Motherboard Type: (if CONFIG_COGENT is defined)
301 Define exactly one of 301 Define exactly one of
302 CONFIG_CMA101, CONFIG_CMA102 302 CONFIG_CMA101, CONFIG_CMA102
303 303
304 - Motherboard I/O Modules: (if CONFIG_COGENT is defined) 304 - Motherboard I/O Modules: (if CONFIG_COGENT is defined)
305 Define one or more of 305 Define one or more of
306 CONFIG_CMA302 306 CONFIG_CMA302
307 307
308 - Motherboard Options: (if CONFIG_CMA101 or CONFIG_CMA102 are defined) 308 - Motherboard Options: (if CONFIG_CMA101 or CONFIG_CMA102 are defined)
309 Define one or more of 309 Define one or more of
310 CONFIG_LCD_HEARTBEAT - update a character position on 310 CONFIG_LCD_HEARTBEAT - update a character position on
311 the LCD display every second with 311 the LCD display every second with
312 a "rotator" |\-/|\-/ 312 a "rotator" |\-/|\-/
313 313
314 - Board flavour: (if CONFIG_MPC8260ADS is defined) 314 - Board flavour: (if CONFIG_MPC8260ADS is defined)
315 CONFIG_ADSTYPE 315 CONFIG_ADSTYPE
316 Possible values are: 316 Possible values are:
317 CONFIG_SYS_8260ADS - original MPC8260ADS 317 CONFIG_SYS_8260ADS - original MPC8260ADS
318 CONFIG_SYS_8266ADS - MPC8266ADS 318 CONFIG_SYS_8266ADS - MPC8266ADS
319 CONFIG_SYS_PQ2FADS - PQ2FADS-ZU or PQ2FADS-VR 319 CONFIG_SYS_PQ2FADS - PQ2FADS-ZU or PQ2FADS-VR
320 CONFIG_SYS_8272ADS - MPC8272ADS 320 CONFIG_SYS_8272ADS - MPC8272ADS
321 321
322 - Marvell Family Member
323 CONFIG_SYS_MVFS - define it if you want to enable
324 multiple fs option at one time
325 for marvell soc family
326
322 - MPC824X Family Member (if CONFIG_MPC824X is defined) 327 - MPC824X Family Member (if CONFIG_MPC824X is defined)
323 Define exactly one of 328 Define exactly one of
324 CONFIG_MPC8240, CONFIG_MPC8245 329 CONFIG_MPC8240, CONFIG_MPC8245
325 330
326 - 8xx CPU Options: (if using an MPC8xx CPU) 331 - 8xx CPU Options: (if using an MPC8xx CPU)
327 CONFIG_8xx_GCLK_FREQ - deprecated: CPU clock if 332 CONFIG_8xx_GCLK_FREQ - deprecated: CPU clock if
328 get_gclk_freq() cannot work 333 get_gclk_freq() cannot work
329 e.g. if there is no 32KHz 334 e.g. if there is no 32KHz
330 reference PIT/RTC clock 335 reference PIT/RTC clock
331 CONFIG_8xx_OSCLK - PLL input clock (either EXTCLK 336 CONFIG_8xx_OSCLK - PLL input clock (either EXTCLK
332 or XTAL/EXTAL) 337 or XTAL/EXTAL)
333 338
334 - 859/866/885 CPU options: (if using a MPC859 or MPC866 or MPC885 CPU): 339 - 859/866/885 CPU options: (if using a MPC859 or MPC866 or MPC885 CPU):
335 CONFIG_SYS_8xx_CPUCLK_MIN 340 CONFIG_SYS_8xx_CPUCLK_MIN
336 CONFIG_SYS_8xx_CPUCLK_MAX 341 CONFIG_SYS_8xx_CPUCLK_MAX
337 CONFIG_8xx_CPUCLK_DEFAULT 342 CONFIG_8xx_CPUCLK_DEFAULT
338 See doc/README.MPC866 343 See doc/README.MPC866
339 344
340 CONFIG_SYS_MEASURE_CPUCLK 345 CONFIG_SYS_MEASURE_CPUCLK
341 346
342 Define this to measure the actual CPU clock instead 347 Define this to measure the actual CPU clock instead
343 of relying on the correctness of the configured 348 of relying on the correctness of the configured
344 values. Mostly useful for board bringup to make sure 349 values. Mostly useful for board bringup to make sure
345 the PLL is locked at the intended frequency. Note 350 the PLL is locked at the intended frequency. Note
346 that this requires a (stable) reference clock (32 kHz 351 that this requires a (stable) reference clock (32 kHz
347 RTC clock or CONFIG_SYS_8XX_XIN) 352 RTC clock or CONFIG_SYS_8XX_XIN)
348 353
349 CONFIG_SYS_DELAYED_ICACHE 354 CONFIG_SYS_DELAYED_ICACHE
350 355
351 Define this option if you want to enable the 356 Define this option if you want to enable the
352 ICache only when Code runs from RAM. 357 ICache only when Code runs from RAM.
353 358
354 - Intel Monahans options: 359 - Intel Monahans options:
355 CONFIG_SYS_MONAHANS_RUN_MODE_OSC_RATIO 360 CONFIG_SYS_MONAHANS_RUN_MODE_OSC_RATIO
356 361
357 Defines the Monahans run mode to oscillator 362 Defines the Monahans run mode to oscillator
358 ratio. Valid values are 8, 16, 24, 31. The core 363 ratio. Valid values are 8, 16, 24, 31. The core
359 frequency is this value multiplied by 13 MHz. 364 frequency is this value multiplied by 13 MHz.
360 365
361 CONFIG_SYS_MONAHANS_TURBO_RUN_MODE_RATIO 366 CONFIG_SYS_MONAHANS_TURBO_RUN_MODE_RATIO
362 367
363 Defines the Monahans turbo mode to oscillator 368 Defines the Monahans turbo mode to oscillator
364 ratio. Valid values are 1 (default if undefined) and 369 ratio. Valid values are 1 (default if undefined) and
365 2. The core frequency as calculated above is multiplied 370 2. The core frequency as calculated above is multiplied
366 by this value. 371 by this value.
367 372
368 - Linux Kernel Interface: 373 - Linux Kernel Interface:
369 CONFIG_CLOCKS_IN_MHZ 374 CONFIG_CLOCKS_IN_MHZ
370 375
371 U-Boot stores all clock information in Hz 376 U-Boot stores all clock information in Hz
372 internally. For binary compatibility with older Linux 377 internally. For binary compatibility with older Linux
373 kernels (which expect the clocks passed in the 378 kernels (which expect the clocks passed in the
374 bd_info data to be in MHz) the environment variable 379 bd_info data to be in MHz) the environment variable
375 "clocks_in_mhz" can be defined so that U-Boot 380 "clocks_in_mhz" can be defined so that U-Boot
376 converts clock data to MHZ before passing it to the 381 converts clock data to MHZ before passing it to the
377 Linux kernel. 382 Linux kernel.
378 When CONFIG_CLOCKS_IN_MHZ is defined, a definition of 383 When CONFIG_CLOCKS_IN_MHZ is defined, a definition of
379 "clocks_in_mhz=1" is automatically included in the 384 "clocks_in_mhz=1" is automatically included in the
380 default environment. 385 default environment.
381 386
382 CONFIG_MEMSIZE_IN_BYTES [relevant for MIPS only] 387 CONFIG_MEMSIZE_IN_BYTES [relevant for MIPS only]
383 388
384 When transferring memsize parameter to linux, some versions 389 When transferring memsize parameter to linux, some versions
385 expect it to be in bytes, others in MB. 390 expect it to be in bytes, others in MB.
386 Define CONFIG_MEMSIZE_IN_BYTES to make it in bytes. 391 Define CONFIG_MEMSIZE_IN_BYTES to make it in bytes.
387 392
388 CONFIG_OF_LIBFDT 393 CONFIG_OF_LIBFDT
389 394
390 New kernel versions are expecting firmware settings to be 395 New kernel versions are expecting firmware settings to be
391 passed using flattened device trees (based on open firmware 396 passed using flattened device trees (based on open firmware
392 concepts). 397 concepts).
393 398
394 CONFIG_OF_LIBFDT 399 CONFIG_OF_LIBFDT
395 * New libfdt-based support 400 * New libfdt-based support
396 * Adds the "fdt" command 401 * Adds the "fdt" command
397 * The bootm command automatically updates the fdt 402 * The bootm command automatically updates the fdt
398 403
399 OF_CPU - The proper name of the cpus node (only required for 404 OF_CPU - The proper name of the cpus node (only required for
400 MPC512X and MPC5xxx based boards). 405 MPC512X and MPC5xxx based boards).
401 OF_SOC - The proper name of the soc node (only required for 406 OF_SOC - The proper name of the soc node (only required for
402 MPC512X and MPC5xxx based boards). 407 MPC512X and MPC5xxx based boards).
403 OF_TBCLK - The timebase frequency. 408 OF_TBCLK - The timebase frequency.
404 OF_STDOUT_PATH - The path to the console device 409 OF_STDOUT_PATH - The path to the console device
405 410
406 boards with QUICC Engines require OF_QE to set UCC MAC 411 boards with QUICC Engines require OF_QE to set UCC MAC
407 addresses 412 addresses
408 413
409 CONFIG_OF_BOARD_SETUP 414 CONFIG_OF_BOARD_SETUP
410 415
411 Board code has addition modification that it wants to make 416 Board code has addition modification that it wants to make
412 to the flat device tree before handing it off to the kernel 417 to the flat device tree before handing it off to the kernel
413 418
414 CONFIG_OF_BOOT_CPU 419 CONFIG_OF_BOOT_CPU
415 420
416 This define fills in the correct boot CPU in the boot 421 This define fills in the correct boot CPU in the boot
417 param header, the default value is zero if undefined. 422 param header, the default value is zero if undefined.
418 423
419 CONFIG_OF_IDE_FIXUP 424 CONFIG_OF_IDE_FIXUP
420 425
421 U-Boot can detect if an IDE device is present or not. 426 U-Boot can detect if an IDE device is present or not.
422 If not, and this new config option is activated, U-Boot 427 If not, and this new config option is activated, U-Boot
423 removes the ATA node from the DTS before booting Linux, 428 removes the ATA node from the DTS before booting Linux,
424 so the Linux IDE driver does not probe the device and 429 so the Linux IDE driver does not probe the device and
425 crash. This is needed for buggy hardware (uc101) where 430 crash. This is needed for buggy hardware (uc101) where
426 no pull down resistor is connected to the signal IDE5V_DD7. 431 no pull down resistor is connected to the signal IDE5V_DD7.
427 432
428 - vxWorks boot parameters: 433 - vxWorks boot parameters:
429 434
430 bootvx constructs a valid bootline using the following 435 bootvx constructs a valid bootline using the following
431 environments variables: bootfile, ipaddr, serverip, hostname. 436 environments variables: bootfile, ipaddr, serverip, hostname.
432 It loads the vxWorks image pointed bootfile. 437 It loads the vxWorks image pointed bootfile.
433 438
434 CONFIG_SYS_VXWORKS_BOOT_DEVICE - The vxworks device name 439 CONFIG_SYS_VXWORKS_BOOT_DEVICE - The vxworks device name
435 CONFIG_SYS_VXWORKS_MAC_PTR - Ethernet 6 byte MA -address 440 CONFIG_SYS_VXWORKS_MAC_PTR - Ethernet 6 byte MA -address
436 CONFIG_SYS_VXWORKS_SERVERNAME - Name of the server 441 CONFIG_SYS_VXWORKS_SERVERNAME - Name of the server
437 CONFIG_SYS_VXWORKS_BOOT_ADDR - Address of boot parameters 442 CONFIG_SYS_VXWORKS_BOOT_ADDR - Address of boot parameters
438 443
439 CONFIG_SYS_VXWORKS_ADD_PARAMS 444 CONFIG_SYS_VXWORKS_ADD_PARAMS
440 445
441 Add it at the end of the bootline. E.g "u=username pw=secret" 446 Add it at the end of the bootline. E.g "u=username pw=secret"
442 447
443 Note: If a "bootargs" environment is defined, it will overwride 448 Note: If a "bootargs" environment is defined, it will overwride
444 the defaults discussed just above. 449 the defaults discussed just above.
445 450
446 - Serial Ports: 451 - Serial Ports:
447 CONFIG_PL010_SERIAL 452 CONFIG_PL010_SERIAL
448 453
449 Define this if you want support for Amba PrimeCell PL010 UARTs. 454 Define this if you want support for Amba PrimeCell PL010 UARTs.
450 455
451 CONFIG_PL011_SERIAL 456 CONFIG_PL011_SERIAL
452 457
453 Define this if you want support for Amba PrimeCell PL011 UARTs. 458 Define this if you want support for Amba PrimeCell PL011 UARTs.
454 459
455 CONFIG_PL011_CLOCK 460 CONFIG_PL011_CLOCK
456 461
457 If you have Amba PrimeCell PL011 UARTs, set this variable to 462 If you have Amba PrimeCell PL011 UARTs, set this variable to
458 the clock speed of the UARTs. 463 the clock speed of the UARTs.
459 464
460 CONFIG_PL01x_PORTS 465 CONFIG_PL01x_PORTS
461 466
462 If you have Amba PrimeCell PL010 or PL011 UARTs on your board, 467 If you have Amba PrimeCell PL010 or PL011 UARTs on your board,
463 define this to a list of base addresses for each (supported) 468 define this to a list of base addresses for each (supported)
464 port. See e.g. include/configs/versatile.h 469 port. See e.g. include/configs/versatile.h
465 470
466 471
467 - Console Interface: 472 - Console Interface:
468 Depending on board, define exactly one serial port 473 Depending on board, define exactly one serial port
469 (like CONFIG_8xx_CONS_SMC1, CONFIG_8xx_CONS_SMC2, 474 (like CONFIG_8xx_CONS_SMC1, CONFIG_8xx_CONS_SMC2,
470 CONFIG_8xx_CONS_SCC1, ...), or switch off the serial 475 CONFIG_8xx_CONS_SCC1, ...), or switch off the serial
471 console by defining CONFIG_8xx_CONS_NONE 476 console by defining CONFIG_8xx_CONS_NONE
472 477
473 Note: if CONFIG_8xx_CONS_NONE is defined, the serial 478 Note: if CONFIG_8xx_CONS_NONE is defined, the serial
474 port routines must be defined elsewhere 479 port routines must be defined elsewhere
475 (i.e. serial_init(), serial_getc(), ...) 480 (i.e. serial_init(), serial_getc(), ...)
476 481
477 CONFIG_CFB_CONSOLE 482 CONFIG_CFB_CONSOLE
478 Enables console device for a color framebuffer. Needs following 483 Enables console device for a color framebuffer. Needs following
479 defines (cf. smiLynxEM, i8042, board/eltec/bab7xx) 484 defines (cf. smiLynxEM, i8042, board/eltec/bab7xx)
480 VIDEO_FB_LITTLE_ENDIAN graphic memory organisation 485 VIDEO_FB_LITTLE_ENDIAN graphic memory organisation
481 (default big endian) 486 (default big endian)
482 VIDEO_HW_RECTFILL graphic chip supports 487 VIDEO_HW_RECTFILL graphic chip supports
483 rectangle fill 488 rectangle fill
484 (cf. smiLynxEM) 489 (cf. smiLynxEM)
485 VIDEO_HW_BITBLT graphic chip supports 490 VIDEO_HW_BITBLT graphic chip supports
486 bit-blit (cf. smiLynxEM) 491 bit-blit (cf. smiLynxEM)
487 VIDEO_VISIBLE_COLS visible pixel columns 492 VIDEO_VISIBLE_COLS visible pixel columns
488 (cols=pitch) 493 (cols=pitch)
489 VIDEO_VISIBLE_ROWS visible pixel rows 494 VIDEO_VISIBLE_ROWS visible pixel rows
490 VIDEO_PIXEL_SIZE bytes per pixel 495 VIDEO_PIXEL_SIZE bytes per pixel
491 VIDEO_DATA_FORMAT graphic data format 496 VIDEO_DATA_FORMAT graphic data format
492 (0-5, cf. cfb_console.c) 497 (0-5, cf. cfb_console.c)
493 VIDEO_FB_ADRS framebuffer address 498 VIDEO_FB_ADRS framebuffer address
494 VIDEO_KBD_INIT_FCT keyboard int fct 499 VIDEO_KBD_INIT_FCT keyboard int fct
495 (i.e. i8042_kbd_init()) 500 (i.e. i8042_kbd_init())
496 VIDEO_TSTC_FCT test char fct 501 VIDEO_TSTC_FCT test char fct
497 (i.e. i8042_tstc) 502 (i.e. i8042_tstc)
498 VIDEO_GETC_FCT get char fct 503 VIDEO_GETC_FCT get char fct
499 (i.e. i8042_getc) 504 (i.e. i8042_getc)
500 CONFIG_CONSOLE_CURSOR cursor drawing on/off 505 CONFIG_CONSOLE_CURSOR cursor drawing on/off
501 (requires blink timer 506 (requires blink timer
502 cf. i8042.c) 507 cf. i8042.c)
503 CONFIG_SYS_CONSOLE_BLINK_COUNT blink interval (cf. i8042.c) 508 CONFIG_SYS_CONSOLE_BLINK_COUNT blink interval (cf. i8042.c)
504 CONFIG_CONSOLE_TIME display time/date info in 509 CONFIG_CONSOLE_TIME display time/date info in
505 upper right corner 510 upper right corner
506 (requires CONFIG_CMD_DATE) 511 (requires CONFIG_CMD_DATE)
507 CONFIG_VIDEO_LOGO display Linux logo in 512 CONFIG_VIDEO_LOGO display Linux logo in
508 upper left corner 513 upper left corner
509 CONFIG_VIDEO_BMP_LOGO use bmp_logo.h instead of 514 CONFIG_VIDEO_BMP_LOGO use bmp_logo.h instead of
510 linux_logo.h for logo. 515 linux_logo.h for logo.
511 Requires CONFIG_VIDEO_LOGO 516 Requires CONFIG_VIDEO_LOGO
512 CONFIG_CONSOLE_EXTRA_INFO 517 CONFIG_CONSOLE_EXTRA_INFO
513 additional board info beside 518 additional board info beside
514 the logo 519 the logo
515 520
516 When CONFIG_CFB_CONSOLE is defined, video console is 521 When CONFIG_CFB_CONSOLE is defined, video console is
517 default i/o. Serial console can be forced with 522 default i/o. Serial console can be forced with
518 environment 'console=serial'. 523 environment 'console=serial'.
519 524
520 When CONFIG_SILENT_CONSOLE is defined, all console 525 When CONFIG_SILENT_CONSOLE is defined, all console
521 messages (by U-Boot and Linux!) can be silenced with 526 messages (by U-Boot and Linux!) can be silenced with
522 the "silent" environment variable. See 527 the "silent" environment variable. See
523 doc/README.silent for more information. 528 doc/README.silent for more information.
524 529
525 - Console Baudrate: 530 - Console Baudrate:
526 CONFIG_BAUDRATE - in bps 531 CONFIG_BAUDRATE - in bps
527 Select one of the baudrates listed in 532 Select one of the baudrates listed in
528 CONFIG_SYS_BAUDRATE_TABLE, see below. 533 CONFIG_SYS_BAUDRATE_TABLE, see below.
529 CONFIG_SYS_BRGCLK_PRESCALE, baudrate prescale 534 CONFIG_SYS_BRGCLK_PRESCALE, baudrate prescale
530 535
531 - Console Rx buffer length 536 - Console Rx buffer length
532 With CONFIG_SYS_SMC_RXBUFLEN it is possible to define 537 With CONFIG_SYS_SMC_RXBUFLEN it is possible to define
533 the maximum receive buffer length for the SMC. 538 the maximum receive buffer length for the SMC.
534 This option is actual only for 82xx and 8xx possible. 539 This option is actual only for 82xx and 8xx possible.
535 If using CONFIG_SYS_SMC_RXBUFLEN also CONFIG_SYS_MAXIDLE 540 If using CONFIG_SYS_SMC_RXBUFLEN also CONFIG_SYS_MAXIDLE
536 must be defined, to setup the maximum idle timeout for 541 must be defined, to setup the maximum idle timeout for
537 the SMC. 542 the SMC.
538 543
539 - Boot Delay: CONFIG_BOOTDELAY - in seconds 544 - Boot Delay: CONFIG_BOOTDELAY - in seconds
540 Delay before automatically booting the default image; 545 Delay before automatically booting the default image;
541 set to -1 to disable autoboot. 546 set to -1 to disable autoboot.
542 547
543 See doc/README.autoboot for these options that 548 See doc/README.autoboot for these options that
544 work with CONFIG_BOOTDELAY. None are required. 549 work with CONFIG_BOOTDELAY. None are required.
545 CONFIG_BOOT_RETRY_TIME 550 CONFIG_BOOT_RETRY_TIME
546 CONFIG_BOOT_RETRY_MIN 551 CONFIG_BOOT_RETRY_MIN
547 CONFIG_AUTOBOOT_KEYED 552 CONFIG_AUTOBOOT_KEYED
548 CONFIG_AUTOBOOT_PROMPT 553 CONFIG_AUTOBOOT_PROMPT
549 CONFIG_AUTOBOOT_DELAY_STR 554 CONFIG_AUTOBOOT_DELAY_STR
550 CONFIG_AUTOBOOT_STOP_STR 555 CONFIG_AUTOBOOT_STOP_STR
551 CONFIG_AUTOBOOT_DELAY_STR2 556 CONFIG_AUTOBOOT_DELAY_STR2
552 CONFIG_AUTOBOOT_STOP_STR2 557 CONFIG_AUTOBOOT_STOP_STR2
553 CONFIG_ZERO_BOOTDELAY_CHECK 558 CONFIG_ZERO_BOOTDELAY_CHECK
554 CONFIG_RESET_TO_RETRY 559 CONFIG_RESET_TO_RETRY
555 560
556 - Autoboot Command: 561 - Autoboot Command:
557 CONFIG_BOOTCOMMAND 562 CONFIG_BOOTCOMMAND
558 Only needed when CONFIG_BOOTDELAY is enabled; 563 Only needed when CONFIG_BOOTDELAY is enabled;
559 define a command string that is automatically executed 564 define a command string that is automatically executed
560 when no character is read on the console interface 565 when no character is read on the console interface
561 within "Boot Delay" after reset. 566 within "Boot Delay" after reset.
562 567
563 CONFIG_BOOTARGS 568 CONFIG_BOOTARGS
564 This can be used to pass arguments to the bootm 569 This can be used to pass arguments to the bootm
565 command. The value of CONFIG_BOOTARGS goes into the 570 command. The value of CONFIG_BOOTARGS goes into the
566 environment value "bootargs". 571 environment value "bootargs".
567 572
568 CONFIG_RAMBOOT and CONFIG_NFSBOOT 573 CONFIG_RAMBOOT and CONFIG_NFSBOOT
569 The value of these goes into the environment as 574 The value of these goes into the environment as
570 "ramboot" and "nfsboot" respectively, and can be used 575 "ramboot" and "nfsboot" respectively, and can be used
571 as a convenience, when switching between booting from 576 as a convenience, when switching between booting from
572 RAM and NFS. 577 RAM and NFS.
573 578
574 - Pre-Boot Commands: 579 - Pre-Boot Commands:
575 CONFIG_PREBOOT 580 CONFIG_PREBOOT
576 581
577 When this option is #defined, the existence of the 582 When this option is #defined, the existence of the
578 environment variable "preboot" will be checked 583 environment variable "preboot" will be checked
579 immediately before starting the CONFIG_BOOTDELAY 584 immediately before starting the CONFIG_BOOTDELAY
580 countdown and/or running the auto-boot command resp. 585 countdown and/or running the auto-boot command resp.
581 entering interactive mode. 586 entering interactive mode.
582 587
583 This feature is especially useful when "preboot" is 588 This feature is especially useful when "preboot" is
584 automatically generated or modified. For an example 589 automatically generated or modified. For an example
585 see the LWMON board specific code: here "preboot" is 590 see the LWMON board specific code: here "preboot" is
586 modified when the user holds down a certain 591 modified when the user holds down a certain
587 combination of keys on the (special) keyboard when 592 combination of keys on the (special) keyboard when
588 booting the systems 593 booting the systems
589 594
590 - Serial Download Echo Mode: 595 - Serial Download Echo Mode:
591 CONFIG_LOADS_ECHO 596 CONFIG_LOADS_ECHO
592 If defined to 1, all characters received during a 597 If defined to 1, all characters received during a
593 serial download (using the "loads" command) are 598 serial download (using the "loads" command) are
594 echoed back. This might be needed by some terminal 599 echoed back. This might be needed by some terminal
595 emulations (like "cu"), but may as well just take 600 emulations (like "cu"), but may as well just take
596 time on others. This setting #define's the initial 601 time on others. This setting #define's the initial
597 value of the "loads_echo" environment variable. 602 value of the "loads_echo" environment variable.
598 603
599 - Kgdb Serial Baudrate: (if CONFIG_CMD_KGDB is defined) 604 - Kgdb Serial Baudrate: (if CONFIG_CMD_KGDB is defined)
600 CONFIG_KGDB_BAUDRATE 605 CONFIG_KGDB_BAUDRATE
601 Select one of the baudrates listed in 606 Select one of the baudrates listed in
602 CONFIG_SYS_BAUDRATE_TABLE, see below. 607 CONFIG_SYS_BAUDRATE_TABLE, see below.
603 608
604 - Monitor Functions: 609 - Monitor Functions:
605 Monitor commands can be included or excluded 610 Monitor commands can be included or excluded
606 from the build by using the #include files 611 from the build by using the #include files
607 "config_cmd_all.h" and #undef'ing unwanted 612 "config_cmd_all.h" and #undef'ing unwanted
608 commands, or using "config_cmd_default.h" 613 commands, or using "config_cmd_default.h"
609 and augmenting with additional #define's 614 and augmenting with additional #define's
610 for wanted commands. 615 for wanted commands.
611 616
612 The default command configuration includes all commands 617 The default command configuration includes all commands
613 except those marked below with a "*". 618 except those marked below with a "*".
614 619
615 CONFIG_CMD_ASKENV * ask for env variable 620 CONFIG_CMD_ASKENV * ask for env variable
616 CONFIG_CMD_BDI bdinfo 621 CONFIG_CMD_BDI bdinfo
617 CONFIG_CMD_BEDBUG * Include BedBug Debugger 622 CONFIG_CMD_BEDBUG * Include BedBug Debugger
618 CONFIG_CMD_BMP * BMP support 623 CONFIG_CMD_BMP * BMP support
619 CONFIG_CMD_BSP * Board specific commands 624 CONFIG_CMD_BSP * Board specific commands
620 CONFIG_CMD_BOOTD bootd 625 CONFIG_CMD_BOOTD bootd
621 CONFIG_CMD_CACHE * icache, dcache 626 CONFIG_CMD_CACHE * icache, dcache
622 CONFIG_CMD_CONSOLE coninfo 627 CONFIG_CMD_CONSOLE coninfo
623 CONFIG_CMD_DATE * support for RTC, date/time... 628 CONFIG_CMD_DATE * support for RTC, date/time...
624 CONFIG_CMD_DHCP * DHCP support 629 CONFIG_CMD_DHCP * DHCP support
625 CONFIG_CMD_DIAG * Diagnostics 630 CONFIG_CMD_DIAG * Diagnostics
626 CONFIG_CMD_DS4510 * ds4510 I2C gpio commands 631 CONFIG_CMD_DS4510 * ds4510 I2C gpio commands
627 CONFIG_CMD_DS4510_INFO * ds4510 I2C info command 632 CONFIG_CMD_DS4510_INFO * ds4510 I2C info command
628 CONFIG_CMD_DS4510_MEM * ds4510 I2C eeprom/sram commansd 633 CONFIG_CMD_DS4510_MEM * ds4510 I2C eeprom/sram commansd
629 CONFIG_CMD_DS4510_RST * ds4510 I2C rst command 634 CONFIG_CMD_DS4510_RST * ds4510 I2C rst command
630 CONFIG_CMD_DTT * Digital Therm and Thermostat 635 CONFIG_CMD_DTT * Digital Therm and Thermostat
631 CONFIG_CMD_ECHO echo arguments 636 CONFIG_CMD_ECHO echo arguments
632 CONFIG_CMD_EDITENV edit env variable 637 CONFIG_CMD_EDITENV edit env variable
633 CONFIG_CMD_EEPROM * EEPROM read/write support 638 CONFIG_CMD_EEPROM * EEPROM read/write support
634 CONFIG_CMD_ELF * bootelf, bootvx 639 CONFIG_CMD_ELF * bootelf, bootvx
635 CONFIG_CMD_SAVEENV saveenv 640 CONFIG_CMD_SAVEENV saveenv
636 CONFIG_CMD_FDC * Floppy Disk Support 641 CONFIG_CMD_FDC * Floppy Disk Support
637 CONFIG_CMD_FAT * FAT partition support 642 CONFIG_CMD_FAT * FAT partition support
638 CONFIG_CMD_FDOS * Dos diskette Support 643 CONFIG_CMD_FDOS * Dos diskette Support
639 CONFIG_CMD_FLASH flinfo, erase, protect 644 CONFIG_CMD_FLASH flinfo, erase, protect
640 CONFIG_CMD_FPGA FPGA device initialization support 645 CONFIG_CMD_FPGA FPGA device initialization support
641 CONFIG_CMD_HWFLOW * RTS/CTS hw flow control 646 CONFIG_CMD_HWFLOW * RTS/CTS hw flow control
642 CONFIG_CMD_I2C * I2C serial bus support 647 CONFIG_CMD_I2C * I2C serial bus support
643 CONFIG_CMD_IDE * IDE harddisk support 648 CONFIG_CMD_IDE * IDE harddisk support
644 CONFIG_CMD_IMI iminfo 649 CONFIG_CMD_IMI iminfo
645 CONFIG_CMD_IMLS List all found images 650 CONFIG_CMD_IMLS List all found images
646 CONFIG_CMD_IMMAP * IMMR dump support 651 CONFIG_CMD_IMMAP * IMMR dump support
647 CONFIG_CMD_IRQ * irqinfo 652 CONFIG_CMD_IRQ * irqinfo
648 CONFIG_CMD_ITEST Integer/string test of 2 values 653 CONFIG_CMD_ITEST Integer/string test of 2 values
649 CONFIG_CMD_JFFS2 * JFFS2 Support 654 CONFIG_CMD_JFFS2 * JFFS2 Support
650 CONFIG_CMD_KGDB * kgdb 655 CONFIG_CMD_KGDB * kgdb
651 CONFIG_CMD_LOADB loadb 656 CONFIG_CMD_LOADB loadb
652 CONFIG_CMD_LOADS loads 657 CONFIG_CMD_LOADS loads
653 CONFIG_CMD_MD5SUM print md5 message digest 658 CONFIG_CMD_MD5SUM print md5 message digest
654 (requires CONFIG_CMD_MEMORY and CONFIG_MD5) 659 (requires CONFIG_CMD_MEMORY and CONFIG_MD5)
655 CONFIG_CMD_MEMORY md, mm, nm, mw, cp, cmp, crc, base, 660 CONFIG_CMD_MEMORY md, mm, nm, mw, cp, cmp, crc, base,
656 loop, loopw, mtest 661 loop, loopw, mtest
657 CONFIG_CMD_MISC Misc functions like sleep etc 662 CONFIG_CMD_MISC Misc functions like sleep etc
658 CONFIG_CMD_MMC * MMC memory mapped support 663 CONFIG_CMD_MMC * MMC memory mapped support
659 CONFIG_CMD_MII * MII utility commands 664 CONFIG_CMD_MII * MII utility commands
660 CONFIG_CMD_MTDPARTS * MTD partition support 665 CONFIG_CMD_MTDPARTS * MTD partition support
661 CONFIG_CMD_NAND * NAND support 666 CONFIG_CMD_NAND * NAND support
662 CONFIG_CMD_NET bootp, tftpboot, rarpboot 667 CONFIG_CMD_NET bootp, tftpboot, rarpboot
663 CONFIG_CMD_PCA953X * PCA953x I2C gpio commands 668 CONFIG_CMD_PCA953X * PCA953x I2C gpio commands
664 CONFIG_CMD_PCA953X_INFO * PCA953x I2C gpio info command 669 CONFIG_CMD_PCA953X_INFO * PCA953x I2C gpio info command
665 CONFIG_CMD_PCI * pciinfo 670 CONFIG_CMD_PCI * pciinfo
666 CONFIG_CMD_PCMCIA * PCMCIA support 671 CONFIG_CMD_PCMCIA * PCMCIA support
667 CONFIG_CMD_PING * send ICMP ECHO_REQUEST to network 672 CONFIG_CMD_PING * send ICMP ECHO_REQUEST to network
668 host 673 host
669 CONFIG_CMD_PORTIO * Port I/O 674 CONFIG_CMD_PORTIO * Port I/O
670 CONFIG_CMD_REGINFO * Register dump 675 CONFIG_CMD_REGINFO * Register dump
671 CONFIG_CMD_RUN run command in env variable 676 CONFIG_CMD_RUN run command in env variable
672 CONFIG_CMD_SAVES * save S record dump 677 CONFIG_CMD_SAVES * save S record dump
673 CONFIG_CMD_SCSI * SCSI Support 678 CONFIG_CMD_SCSI * SCSI Support
674 CONFIG_CMD_SDRAM * print SDRAM configuration information 679 CONFIG_CMD_SDRAM * print SDRAM configuration information
675 (requires CONFIG_CMD_I2C) 680 (requires CONFIG_CMD_I2C)
676 CONFIG_CMD_SETGETDCR Support for DCR Register access 681 CONFIG_CMD_SETGETDCR Support for DCR Register access
677 (4xx only) 682 (4xx only)
678 CONFIG_CMD_SHA1SUM print sha1 memory digest 683 CONFIG_CMD_SHA1SUM print sha1 memory digest
679 (requires CONFIG_CMD_MEMORY) 684 (requires CONFIG_CMD_MEMORY)
680 CONFIG_CMD_SOURCE "source" command Support 685 CONFIG_CMD_SOURCE "source" command Support
681 CONFIG_CMD_SPI * SPI serial bus support 686 CONFIG_CMD_SPI * SPI serial bus support
682 CONFIG_CMD_USB * USB support 687 CONFIG_CMD_USB * USB support
683 CONFIG_CMD_VFD * VFD support (TRAB) 688 CONFIG_CMD_VFD * VFD support (TRAB)
684 CONFIG_CMD_CDP * Cisco Discover Protocol support 689 CONFIG_CMD_CDP * Cisco Discover Protocol support
685 CONFIG_CMD_FSL * Microblaze FSL support 690 CONFIG_CMD_FSL * Microblaze FSL support
686 691
687 692
688 EXAMPLE: If you want all functions except of network 693 EXAMPLE: If you want all functions except of network
689 support you can write: 694 support you can write:
690 695
691 #include "config_cmd_all.h" 696 #include "config_cmd_all.h"
692 #undef CONFIG_CMD_NET 697 #undef CONFIG_CMD_NET
693 698
694 Other Commands: 699 Other Commands:
695 fdt (flattened device tree) command: CONFIG_OF_LIBFDT 700 fdt (flattened device tree) command: CONFIG_OF_LIBFDT
696 701
697 Note: Don't enable the "icache" and "dcache" commands 702 Note: Don't enable the "icache" and "dcache" commands
698 (configuration option CONFIG_CMD_CACHE) unless you know 703 (configuration option CONFIG_CMD_CACHE) unless you know
699 what you (and your U-Boot users) are doing. Data 704 what you (and your U-Boot users) are doing. Data
700 cache cannot be enabled on systems like the 8xx or 705 cache cannot be enabled on systems like the 8xx or
701 8260 (where accesses to the IMMR region must be 706 8260 (where accesses to the IMMR region must be
702 uncached), and it cannot be disabled on all other 707 uncached), and it cannot be disabled on all other
703 systems where we (mis-) use the data cache to hold an 708 systems where we (mis-) use the data cache to hold an
704 initial stack and some data. 709 initial stack and some data.
705 710
706 711
707 XXX - this list needs to get updated! 712 XXX - this list needs to get updated!
708 713
709 - Watchdog: 714 - Watchdog:
710 CONFIG_WATCHDOG 715 CONFIG_WATCHDOG
711 If this variable is defined, it enables watchdog 716 If this variable is defined, it enables watchdog
712 support. There must be support in the platform specific 717 support. There must be support in the platform specific
713 code for a watchdog. For the 8xx and 8260 CPUs, the 718 code for a watchdog. For the 8xx and 8260 CPUs, the
714 SIU Watchdog feature is enabled in the SYPCR 719 SIU Watchdog feature is enabled in the SYPCR
715 register. 720 register.
716 721
717 - U-Boot Version: 722 - U-Boot Version:
718 CONFIG_VERSION_VARIABLE 723 CONFIG_VERSION_VARIABLE
719 If this variable is defined, an environment variable 724 If this variable is defined, an environment variable
720 named "ver" is created by U-Boot showing the U-Boot 725 named "ver" is created by U-Boot showing the U-Boot
721 version as printed by the "version" command. 726 version as printed by the "version" command.
722 This variable is readonly. 727 This variable is readonly.
723 728
724 - Real-Time Clock: 729 - Real-Time Clock:
725 730
726 When CONFIG_CMD_DATE is selected, the type of the RTC 731 When CONFIG_CMD_DATE is selected, the type of the RTC
727 has to be selected, too. Define exactly one of the 732 has to be selected, too. Define exactly one of the
728 following options: 733 following options:
729 734
730 CONFIG_RTC_MPC8xx - use internal RTC of MPC8xx 735 CONFIG_RTC_MPC8xx - use internal RTC of MPC8xx
731 CONFIG_RTC_PCF8563 - use Philips PCF8563 RTC 736 CONFIG_RTC_PCF8563 - use Philips PCF8563 RTC
732 CONFIG_RTC_MC13783 - use MC13783 RTC 737 CONFIG_RTC_MC13783 - use MC13783 RTC
733 CONFIG_RTC_MC146818 - use MC146818 RTC 738 CONFIG_RTC_MC146818 - use MC146818 RTC
734 CONFIG_RTC_DS1307 - use Maxim, Inc. DS1307 RTC 739 CONFIG_RTC_DS1307 - use Maxim, Inc. DS1307 RTC
735 CONFIG_RTC_DS1337 - use Maxim, Inc. DS1337 RTC 740 CONFIG_RTC_DS1337 - use Maxim, Inc. DS1337 RTC
736 CONFIG_RTC_DS1338 - use Maxim, Inc. DS1338 RTC 741 CONFIG_RTC_DS1338 - use Maxim, Inc. DS1338 RTC
737 CONFIG_RTC_DS164x - use Dallas DS164x RTC 742 CONFIG_RTC_DS164x - use Dallas DS164x RTC
738 CONFIG_RTC_ISL1208 - use Intersil ISL1208 RTC 743 CONFIG_RTC_ISL1208 - use Intersil ISL1208 RTC
739 CONFIG_RTC_MAX6900 - use Maxim, Inc. MAX6900 RTC 744 CONFIG_RTC_MAX6900 - use Maxim, Inc. MAX6900 RTC
740 CONFIG_SYS_RTC_DS1337_NOOSC - Turn off the OSC output for DS1337 745 CONFIG_SYS_RTC_DS1337_NOOSC - Turn off the OSC output for DS1337
741 746
742 Note that if the RTC uses I2C, then the I2C interface 747 Note that if the RTC uses I2C, then the I2C interface
743 must also be configured. See I2C Support, below. 748 must also be configured. See I2C Support, below.
744 749
745 - GPIO Support: 750 - GPIO Support:
746 CONFIG_PCA953X - use NXP's PCA953X series I2C GPIO 751 CONFIG_PCA953X - use NXP's PCA953X series I2C GPIO
747 CONFIG_PCA953X_INFO - enable pca953x info command 752 CONFIG_PCA953X_INFO - enable pca953x info command
748 753
749 The CONFIG_SYS_I2C_PCA953X_WIDTH option specifies a list of 754 The CONFIG_SYS_I2C_PCA953X_WIDTH option specifies a list of
750 chip-ngpio pairs that tell the PCA953X driver the number of 755 chip-ngpio pairs that tell the PCA953X driver the number of
751 pins supported by a particular chip. 756 pins supported by a particular chip.
752 757
753 Note that if the GPIO device uses I2C, then the I2C interface 758 Note that if the GPIO device uses I2C, then the I2C interface
754 must also be configured. See I2C Support, below. 759 must also be configured. See I2C Support, below.
755 760
756 - Timestamp Support: 761 - Timestamp Support:
757 762
758 When CONFIG_TIMESTAMP is selected, the timestamp 763 When CONFIG_TIMESTAMP is selected, the timestamp
759 (date and time) of an image is printed by image 764 (date and time) of an image is printed by image
760 commands like bootm or iminfo. This option is 765 commands like bootm or iminfo. This option is
761 automatically enabled when you select CONFIG_CMD_DATE . 766 automatically enabled when you select CONFIG_CMD_DATE .
762 767
763 - Partition Support: 768 - Partition Support:
764 CONFIG_MAC_PARTITION and/or CONFIG_DOS_PARTITION 769 CONFIG_MAC_PARTITION and/or CONFIG_DOS_PARTITION
765 and/or CONFIG_ISO_PARTITION and/or CONFIG_EFI_PARTITION 770 and/or CONFIG_ISO_PARTITION and/or CONFIG_EFI_PARTITION
766 771
767 If IDE or SCSI support is enabled (CONFIG_CMD_IDE or 772 If IDE or SCSI support is enabled (CONFIG_CMD_IDE or
768 CONFIG_CMD_SCSI) you must configure support for at 773 CONFIG_CMD_SCSI) you must configure support for at
769 least one partition type as well. 774 least one partition type as well.
770 775
771 - IDE Reset method: 776 - IDE Reset method:
772 CONFIG_IDE_RESET_ROUTINE - this is defined in several 777 CONFIG_IDE_RESET_ROUTINE - this is defined in several
773 board configurations files but used nowhere! 778 board configurations files but used nowhere!
774 779
775 CONFIG_IDE_RESET - is this is defined, IDE Reset will 780 CONFIG_IDE_RESET - is this is defined, IDE Reset will
776 be performed by calling the function 781 be performed by calling the function
777 ide_set_reset(int reset) 782 ide_set_reset(int reset)
778 which has to be defined in a board specific file 783 which has to be defined in a board specific file
779 784
780 - ATAPI Support: 785 - ATAPI Support:
781 CONFIG_ATAPI 786 CONFIG_ATAPI
782 787
783 Set this to enable ATAPI support. 788 Set this to enable ATAPI support.
784 789
785 - LBA48 Support 790 - LBA48 Support
786 CONFIG_LBA48 791 CONFIG_LBA48
787 792
788 Set this to enable support for disks larger than 137GB 793 Set this to enable support for disks larger than 137GB
789 Also look at CONFIG_SYS_64BIT_LBA. 794 Also look at CONFIG_SYS_64BIT_LBA.
790 Whithout these , LBA48 support uses 32bit variables and will 'only' 795 Whithout these , LBA48 support uses 32bit variables and will 'only'
791 support disks up to 2.1TB. 796 support disks up to 2.1TB.
792 797
793 CONFIG_SYS_64BIT_LBA: 798 CONFIG_SYS_64BIT_LBA:
794 When enabled, makes the IDE subsystem use 64bit sector addresses. 799 When enabled, makes the IDE subsystem use 64bit sector addresses.
795 Default is 32bit. 800 Default is 32bit.
796 801
797 - SCSI Support: 802 - SCSI Support:
798 At the moment only there is only support for the 803 At the moment only there is only support for the
799 SYM53C8XX SCSI controller; define 804 SYM53C8XX SCSI controller; define
800 CONFIG_SCSI_SYM53C8XX to enable it. 805 CONFIG_SCSI_SYM53C8XX to enable it.
801 806
802 CONFIG_SYS_SCSI_MAX_LUN [8], CONFIG_SYS_SCSI_MAX_SCSI_ID [7] and 807 CONFIG_SYS_SCSI_MAX_LUN [8], CONFIG_SYS_SCSI_MAX_SCSI_ID [7] and
803 CONFIG_SYS_SCSI_MAX_DEVICE [CONFIG_SYS_SCSI_MAX_SCSI_ID * 808 CONFIG_SYS_SCSI_MAX_DEVICE [CONFIG_SYS_SCSI_MAX_SCSI_ID *
804 CONFIG_SYS_SCSI_MAX_LUN] can be adjusted to define the 809 CONFIG_SYS_SCSI_MAX_LUN] can be adjusted to define the
805 maximum numbers of LUNs, SCSI ID's and target 810 maximum numbers of LUNs, SCSI ID's and target
806 devices. 811 devices.
807 CONFIG_SYS_SCSI_SYM53C8XX_CCF to fix clock timing (80Mhz) 812 CONFIG_SYS_SCSI_SYM53C8XX_CCF to fix clock timing (80Mhz)
808 813
809 - NETWORK Support (PCI): 814 - NETWORK Support (PCI):
810 CONFIG_E1000 815 CONFIG_E1000
811 Support for Intel 8254x gigabit chips. 816 Support for Intel 8254x gigabit chips.
812 817
813 CONFIG_E1000_FALLBACK_MAC 818 CONFIG_E1000_FALLBACK_MAC
814 default MAC for empty EEPROM after production. 819 default MAC for empty EEPROM after production.
815 820
816 CONFIG_EEPRO100 821 CONFIG_EEPRO100
817 Support for Intel 82557/82559/82559ER chips. 822 Support for Intel 82557/82559/82559ER chips.
818 Optional CONFIG_EEPRO100_SROM_WRITE enables EEPROM 823 Optional CONFIG_EEPRO100_SROM_WRITE enables EEPROM
819 write routine for first time initialisation. 824 write routine for first time initialisation.
820 825
821 CONFIG_TULIP 826 CONFIG_TULIP
822 Support for Digital 2114x chips. 827 Support for Digital 2114x chips.
823 Optional CONFIG_TULIP_SELECT_MEDIA for board specific 828 Optional CONFIG_TULIP_SELECT_MEDIA for board specific
824 modem chip initialisation (KS8761/QS6611). 829 modem chip initialisation (KS8761/QS6611).
825 830
826 CONFIG_NATSEMI 831 CONFIG_NATSEMI
827 Support for National dp83815 chips. 832 Support for National dp83815 chips.
828 833
829 CONFIG_NS8382X 834 CONFIG_NS8382X
830 Support for National dp8382[01] gigabit chips. 835 Support for National dp8382[01] gigabit chips.
831 836
832 - NETWORK Support (other): 837 - NETWORK Support (other):
833 838
834 CONFIG_DRIVER_AT91EMAC 839 CONFIG_DRIVER_AT91EMAC
835 Support for AT91RM9200 EMAC. 840 Support for AT91RM9200 EMAC.
836 841
837 CONFIG_RMII 842 CONFIG_RMII
838 Define this to use reduced MII inteface 843 Define this to use reduced MII inteface
839 844
840 CONFIG_DRIVER_AT91EMAC_QUIET 845 CONFIG_DRIVER_AT91EMAC_QUIET
841 If this defined, the driver is quiet. 846 If this defined, the driver is quiet.
842 The driver doen't show link status messages. 847 The driver doen't show link status messages.
843 848
844 CONFIG_DRIVER_LAN91C96 849 CONFIG_DRIVER_LAN91C96
845 Support for SMSC's LAN91C96 chips. 850 Support for SMSC's LAN91C96 chips.
846 851
847 CONFIG_LAN91C96_BASE 852 CONFIG_LAN91C96_BASE
848 Define this to hold the physical address 853 Define this to hold the physical address
849 of the LAN91C96's I/O space 854 of the LAN91C96's I/O space
850 855
851 CONFIG_LAN91C96_USE_32_BIT 856 CONFIG_LAN91C96_USE_32_BIT
852 Define this to enable 32 bit addressing 857 Define this to enable 32 bit addressing
853 858
854 CONFIG_DRIVER_SMC91111 859 CONFIG_DRIVER_SMC91111
855 Support for SMSC's LAN91C111 chip 860 Support for SMSC's LAN91C111 chip
856 861
857 CONFIG_SMC91111_BASE 862 CONFIG_SMC91111_BASE
858 Define this to hold the physical address 863 Define this to hold the physical address
859 of the device (I/O space) 864 of the device (I/O space)
860 865
861 CONFIG_SMC_USE_32_BIT 866 CONFIG_SMC_USE_32_BIT
862 Define this if data bus is 32 bits 867 Define this if data bus is 32 bits
863 868
864 CONFIG_SMC_USE_IOFUNCS 869 CONFIG_SMC_USE_IOFUNCS
865 Define this to use i/o functions instead of macros 870 Define this to use i/o functions instead of macros
866 (some hardware wont work with macros) 871 (some hardware wont work with macros)
867 872
868 CONFIG_FTGMAC100 873 CONFIG_FTGMAC100
869 Support for Faraday's FTGMAC100 Gigabit SoC Ethernet 874 Support for Faraday's FTGMAC100 Gigabit SoC Ethernet
870 875
871 CONFIG_FTGMAC100_EGIGA 876 CONFIG_FTGMAC100_EGIGA
872 Define this to use GE link update with gigabit PHY. 877 Define this to use GE link update with gigabit PHY.
873 Define this if FTGMAC100 is connected to gigabit PHY. 878 Define this if FTGMAC100 is connected to gigabit PHY.
874 If your system has 10/100 PHY only, it might not occur 879 If your system has 10/100 PHY only, it might not occur
875 wrong behavior. Because PHY usually return timeout or 880 wrong behavior. Because PHY usually return timeout or
876 useless data when polling gigabit status and gigabit 881 useless data when polling gigabit status and gigabit
877 control registers. This behavior won't affect the 882 control registers. This behavior won't affect the
878 correctnessof 10/100 link speed update. 883 correctnessof 10/100 link speed update.
879 884
880 CONFIG_SMC911X 885 CONFIG_SMC911X
881 Support for SMSC's LAN911x and LAN921x chips 886 Support for SMSC's LAN911x and LAN921x chips
882 887
883 CONFIG_SMC911X_BASE 888 CONFIG_SMC911X_BASE
884 Define this to hold the physical address 889 Define this to hold the physical address
885 of the device (I/O space) 890 of the device (I/O space)
886 891
887 CONFIG_SMC911X_32_BIT 892 CONFIG_SMC911X_32_BIT
888 Define this if data bus is 32 bits 893 Define this if data bus is 32 bits
889 894
890 CONFIG_SMC911X_16_BIT 895 CONFIG_SMC911X_16_BIT
891 Define this if data bus is 16 bits. If your processor 896 Define this if data bus is 16 bits. If your processor
892 automatically converts one 32 bit word to two 16 bit 897 automatically converts one 32 bit word to two 16 bit
893 words you may also try CONFIG_SMC911X_32_BIT. 898 words you may also try CONFIG_SMC911X_32_BIT.
894 899
895 CONFIG_SH_ETHER 900 CONFIG_SH_ETHER
896 Support for Renesas on-chip Ethernet controller 901 Support for Renesas on-chip Ethernet controller
897 902
898 CONFIG_SH_ETHER_USE_PORT 903 CONFIG_SH_ETHER_USE_PORT
899 Define the number of ports to be used 904 Define the number of ports to be used
900 905
901 CONFIG_SH_ETHER_PHY_ADDR 906 CONFIG_SH_ETHER_PHY_ADDR
902 Define the ETH PHY's address 907 Define the ETH PHY's address
903 908
904 CONFIG_SH_ETHER_CACHE_WRITEBACK 909 CONFIG_SH_ETHER_CACHE_WRITEBACK
905 If this option is set, the driver enables cache flush. 910 If this option is set, the driver enables cache flush.
906 911
907 - USB Support: 912 - USB Support:
908 At the moment only the UHCI host controller is 913 At the moment only the UHCI host controller is
909 supported (PIP405, MIP405, MPC5200); define 914 supported (PIP405, MIP405, MPC5200); define
910 CONFIG_USB_UHCI to enable it. 915 CONFIG_USB_UHCI to enable it.
911 define CONFIG_USB_KEYBOARD to enable the USB Keyboard 916 define CONFIG_USB_KEYBOARD to enable the USB Keyboard
912 and define CONFIG_USB_STORAGE to enable the USB 917 and define CONFIG_USB_STORAGE to enable the USB
913 storage devices. 918 storage devices.
914 Note: 919 Note:
915 Supported are USB Keyboards and USB Floppy drives 920 Supported are USB Keyboards and USB Floppy drives
916 (TEAC FD-05PUB). 921 (TEAC FD-05PUB).
917 MPC5200 USB requires additional defines: 922 MPC5200 USB requires additional defines:
918 CONFIG_USB_CLOCK 923 CONFIG_USB_CLOCK
919 for 528 MHz Clock: 0x0001bbbb 924 for 528 MHz Clock: 0x0001bbbb
920 CONFIG_PSC3_USB 925 CONFIG_PSC3_USB
921 for USB on PSC3 926 for USB on PSC3
922 CONFIG_USB_CONFIG 927 CONFIG_USB_CONFIG
923 for differential drivers: 0x00001000 928 for differential drivers: 0x00001000
924 for single ended drivers: 0x00005000 929 for single ended drivers: 0x00005000
925 for differential drivers on PSC3: 0x00000100 930 for differential drivers on PSC3: 0x00000100
926 for single ended drivers on PSC3: 0x00004100 931 for single ended drivers on PSC3: 0x00004100
927 CONFIG_SYS_USB_EVENT_POLL 932 CONFIG_SYS_USB_EVENT_POLL
928 May be defined to allow interrupt polling 933 May be defined to allow interrupt polling
929 instead of using asynchronous interrupts 934 instead of using asynchronous interrupts
930 935
931 - USB Device: 936 - USB Device:
932 Define the below if you wish to use the USB console. 937 Define the below if you wish to use the USB console.
933 Once firmware is rebuilt from a serial console issue the 938 Once firmware is rebuilt from a serial console issue the
934 command "setenv stdin usbtty; setenv stdout usbtty" and 939 command "setenv stdin usbtty; setenv stdout usbtty" and
935 attach your USB cable. The Unix command "dmesg" should print 940 attach your USB cable. The Unix command "dmesg" should print
936 it has found a new device. The environment variable usbtty 941 it has found a new device. The environment variable usbtty
937 can be set to gserial or cdc_acm to enable your device to 942 can be set to gserial or cdc_acm to enable your device to
938 appear to a USB host as a Linux gserial device or a 943 appear to a USB host as a Linux gserial device or a
939 Common Device Class Abstract Control Model serial device. 944 Common Device Class Abstract Control Model serial device.
940 If you select usbtty = gserial you should be able to enumerate 945 If you select usbtty = gserial you should be able to enumerate
941 a Linux host by 946 a Linux host by
942 # modprobe usbserial vendor=0xVendorID product=0xProductID 947 # modprobe usbserial vendor=0xVendorID product=0xProductID
943 else if using cdc_acm, simply setting the environment 948 else if using cdc_acm, simply setting the environment
944 variable usbtty to be cdc_acm should suffice. The following 949 variable usbtty to be cdc_acm should suffice. The following
945 might be defined in YourBoardName.h 950 might be defined in YourBoardName.h
946 951
947 CONFIG_USB_DEVICE 952 CONFIG_USB_DEVICE
948 Define this to build a UDC device 953 Define this to build a UDC device
949 954
950 CONFIG_USB_TTY 955 CONFIG_USB_TTY
951 Define this to have a tty type of device available to 956 Define this to have a tty type of device available to
952 talk to the UDC device 957 talk to the UDC device
953 958
954 CONFIG_SYS_CONSOLE_IS_IN_ENV 959 CONFIG_SYS_CONSOLE_IS_IN_ENV
955 Define this if you want stdin, stdout &/or stderr to 960 Define this if you want stdin, stdout &/or stderr to
956 be set to usbtty. 961 be set to usbtty.
957 962
958 mpc8xx: 963 mpc8xx:
959 CONFIG_SYS_USB_EXTC_CLK 0xBLAH 964 CONFIG_SYS_USB_EXTC_CLK 0xBLAH
960 Derive USB clock from external clock "blah" 965 Derive USB clock from external clock "blah"
961 - CONFIG_SYS_USB_EXTC_CLK 0x02 966 - CONFIG_SYS_USB_EXTC_CLK 0x02
962 967
963 CONFIG_SYS_USB_BRG_CLK 0xBLAH 968 CONFIG_SYS_USB_BRG_CLK 0xBLAH
964 Derive USB clock from brgclk 969 Derive USB clock from brgclk
965 - CONFIG_SYS_USB_BRG_CLK 0x04 970 - CONFIG_SYS_USB_BRG_CLK 0x04
966 971
967 If you have a USB-IF assigned VendorID then you may wish to 972 If you have a USB-IF assigned VendorID then you may wish to
968 define your own vendor specific values either in BoardName.h 973 define your own vendor specific values either in BoardName.h
969 or directly in usbd_vendor_info.h. If you don't define 974 or directly in usbd_vendor_info.h. If you don't define
970 CONFIG_USBD_MANUFACTURER, CONFIG_USBD_PRODUCT_NAME, 975 CONFIG_USBD_MANUFACTURER, CONFIG_USBD_PRODUCT_NAME,
971 CONFIG_USBD_VENDORID and CONFIG_USBD_PRODUCTID, then U-Boot 976 CONFIG_USBD_VENDORID and CONFIG_USBD_PRODUCTID, then U-Boot
972 should pretend to be a Linux device to it's target host. 977 should pretend to be a Linux device to it's target host.
973 978
974 CONFIG_USBD_MANUFACTURER 979 CONFIG_USBD_MANUFACTURER
975 Define this string as the name of your company for 980 Define this string as the name of your company for
976 - CONFIG_USBD_MANUFACTURER "my company" 981 - CONFIG_USBD_MANUFACTURER "my company"
977 982
978 CONFIG_USBD_PRODUCT_NAME 983 CONFIG_USBD_PRODUCT_NAME
979 Define this string as the name of your product 984 Define this string as the name of your product
980 - CONFIG_USBD_PRODUCT_NAME "acme usb device" 985 - CONFIG_USBD_PRODUCT_NAME "acme usb device"
981 986
982 CONFIG_USBD_VENDORID 987 CONFIG_USBD_VENDORID
983 Define this as your assigned Vendor ID from the USB 988 Define this as your assigned Vendor ID from the USB
984 Implementors Forum. This *must* be a genuine Vendor ID 989 Implementors Forum. This *must* be a genuine Vendor ID
985 to avoid polluting the USB namespace. 990 to avoid polluting the USB namespace.
986 - CONFIG_USBD_VENDORID 0xFFFF 991 - CONFIG_USBD_VENDORID 0xFFFF
987 992
988 CONFIG_USBD_PRODUCTID 993 CONFIG_USBD_PRODUCTID
989 Define this as the unique Product ID 994 Define this as the unique Product ID
990 for your device 995 for your device
991 - CONFIG_USBD_PRODUCTID 0xFFFF 996 - CONFIG_USBD_PRODUCTID 0xFFFF
992 997
993 998
994 - MMC Support: 999 - MMC Support:
995 The MMC controller on the Intel PXA is supported. To 1000 The MMC controller on the Intel PXA is supported. To
996 enable this define CONFIG_MMC. The MMC can be 1001 enable this define CONFIG_MMC. The MMC can be
997 accessed from the boot prompt by mapping the device 1002 accessed from the boot prompt by mapping the device
998 to physical memory similar to flash. Command line is 1003 to physical memory similar to flash. Command line is
999 enabled with CONFIG_CMD_MMC. The MMC driver also works with 1004 enabled with CONFIG_CMD_MMC. The MMC driver also works with
1000 the FAT fs. This is enabled with CONFIG_CMD_FAT. 1005 the FAT fs. This is enabled with CONFIG_CMD_FAT.
1001 1006
1002 - Journaling Flash filesystem support: 1007 - Journaling Flash filesystem support:
1003 CONFIG_JFFS2_NAND, CONFIG_JFFS2_NAND_OFF, CONFIG_JFFS2_NAND_SIZE, 1008 CONFIG_JFFS2_NAND, CONFIG_JFFS2_NAND_OFF, CONFIG_JFFS2_NAND_SIZE,
1004 CONFIG_JFFS2_NAND_DEV 1009 CONFIG_JFFS2_NAND_DEV
1005 Define these for a default partition on a NAND device 1010 Define these for a default partition on a NAND device
1006 1011
1007 CONFIG_SYS_JFFS2_FIRST_SECTOR, 1012 CONFIG_SYS_JFFS2_FIRST_SECTOR,
1008 CONFIG_SYS_JFFS2_FIRST_BANK, CONFIG_SYS_JFFS2_NUM_BANKS 1013 CONFIG_SYS_JFFS2_FIRST_BANK, CONFIG_SYS_JFFS2_NUM_BANKS
1009 Define these for a default partition on a NOR device 1014 Define these for a default partition on a NOR device
1010 1015
1011 CONFIG_SYS_JFFS_CUSTOM_PART 1016 CONFIG_SYS_JFFS_CUSTOM_PART
1012 Define this to create an own partition. You have to provide a 1017 Define this to create an own partition. You have to provide a
1013 function struct part_info* jffs2_part_info(int part_num) 1018 function struct part_info* jffs2_part_info(int part_num)
1014 1019
1015 If you define only one JFFS2 partition you may also want to 1020 If you define only one JFFS2 partition you may also want to
1016 #define CONFIG_SYS_JFFS_SINGLE_PART 1 1021 #define CONFIG_SYS_JFFS_SINGLE_PART 1
1017 to disable the command chpart. This is the default when you 1022 to disable the command chpart. This is the default when you
1018 have not defined a custom partition 1023 have not defined a custom partition
1019 1024
1020 - Keyboard Support: 1025 - Keyboard Support:
1021 CONFIG_ISA_KEYBOARD 1026 CONFIG_ISA_KEYBOARD
1022 1027
1023 Define this to enable standard (PC-Style) keyboard 1028 Define this to enable standard (PC-Style) keyboard
1024 support 1029 support
1025 1030
1026 CONFIG_I8042_KBD 1031 CONFIG_I8042_KBD
1027 Standard PC keyboard driver with US (is default) and 1032 Standard PC keyboard driver with US (is default) and
1028 GERMAN key layout (switch via environment 'keymap=de') support. 1033 GERMAN key layout (switch via environment 'keymap=de') support.
1029 Export function i8042_kbd_init, i8042_tstc and i8042_getc 1034 Export function i8042_kbd_init, i8042_tstc and i8042_getc
1030 for cfb_console. Supports cursor blinking. 1035 for cfb_console. Supports cursor blinking.
1031 1036
1032 - Video support: 1037 - Video support:
1033 CONFIG_VIDEO 1038 CONFIG_VIDEO
1034 1039
1035 Define this to enable video support (for output to 1040 Define this to enable video support (for output to
1036 video). 1041 video).
1037 1042
1038 CONFIG_VIDEO_CT69000 1043 CONFIG_VIDEO_CT69000
1039 1044
1040 Enable Chips & Technologies 69000 Video chip 1045 Enable Chips & Technologies 69000 Video chip
1041 1046
1042 CONFIG_VIDEO_SMI_LYNXEM 1047 CONFIG_VIDEO_SMI_LYNXEM
1043 Enable Silicon Motion SMI 712/710/810 Video chip. The 1048 Enable Silicon Motion SMI 712/710/810 Video chip. The
1044 video output is selected via environment 'videoout' 1049 video output is selected via environment 'videoout'
1045 (1 = LCD and 2 = CRT). If videoout is undefined, CRT is 1050 (1 = LCD and 2 = CRT). If videoout is undefined, CRT is
1046 assumed. 1051 assumed.
1047 1052
1048 For the CT69000 and SMI_LYNXEM drivers, videomode is 1053 For the CT69000 and SMI_LYNXEM drivers, videomode is
1049 selected via environment 'videomode'. Two different ways 1054 selected via environment 'videomode'. Two different ways
1050 are possible: 1055 are possible:
1051 - "videomode=num" 'num' is a standard LiLo mode numbers. 1056 - "videomode=num" 'num' is a standard LiLo mode numbers.
1052 Following standard modes are supported (* is default): 1057 Following standard modes are supported (* is default):
1053 1058
1054 Colors 640x480 800x600 1024x768 1152x864 1280x1024 1059 Colors 640x480 800x600 1024x768 1152x864 1280x1024
1055 -------------+--------------------------------------------- 1060 -------------+---------------------------------------------
1056 8 bits | 0x301* 0x303 0x305 0x161 0x307 1061 8 bits | 0x301* 0x303 0x305 0x161 0x307
1057 15 bits | 0x310 0x313 0x316 0x162 0x319 1062 15 bits | 0x310 0x313 0x316 0x162 0x319
1058 16 bits | 0x311 0x314 0x317 0x163 0x31A 1063 16 bits | 0x311 0x314 0x317 0x163 0x31A
1059 24 bits | 0x312 0x315 0x318 ? 0x31B 1064 24 bits | 0x312 0x315 0x318 ? 0x31B
1060 -------------+--------------------------------------------- 1065 -------------+---------------------------------------------
1061 (i.e. setenv videomode 317; saveenv; reset;) 1066 (i.e. setenv videomode 317; saveenv; reset;)
1062 1067
1063 - "videomode=bootargs" all the video parameters are parsed 1068 - "videomode=bootargs" all the video parameters are parsed
1064 from the bootargs. (See drivers/video/videomodes.c) 1069 from the bootargs. (See drivers/video/videomodes.c)
1065 1070
1066 1071
1067 CONFIG_VIDEO_SED13806 1072 CONFIG_VIDEO_SED13806
1068 Enable Epson SED13806 driver. This driver supports 8bpp 1073 Enable Epson SED13806 driver. This driver supports 8bpp
1069 and 16bpp modes defined by CONFIG_VIDEO_SED13806_8BPP 1074 and 16bpp modes defined by CONFIG_VIDEO_SED13806_8BPP
1070 or CONFIG_VIDEO_SED13806_16BPP 1075 or CONFIG_VIDEO_SED13806_16BPP
1071 1076
1072 - Keyboard Support: 1077 - Keyboard Support:
1073 CONFIG_KEYBOARD 1078 CONFIG_KEYBOARD
1074 1079
1075 Define this to enable a custom keyboard support. 1080 Define this to enable a custom keyboard support.
1076 This simply calls drv_keyboard_init() which must be 1081 This simply calls drv_keyboard_init() which must be
1077 defined in your board-specific files. 1082 defined in your board-specific files.
1078 The only board using this so far is RBC823. 1083 The only board using this so far is RBC823.
1079 1084
1080 - LCD Support: CONFIG_LCD 1085 - LCD Support: CONFIG_LCD
1081 1086
1082 Define this to enable LCD support (for output to LCD 1087 Define this to enable LCD support (for output to LCD
1083 display); also select one of the supported displays 1088 display); also select one of the supported displays
1084 by defining one of these: 1089 by defining one of these:
1085 1090
1086 CONFIG_ATMEL_LCD: 1091 CONFIG_ATMEL_LCD:
1087 1092
1088 HITACHI TX09D70VM1CCA, 3.5", 240x320. 1093 HITACHI TX09D70VM1CCA, 3.5", 240x320.
1089 1094
1090 CONFIG_NEC_NL6448AC33: 1095 CONFIG_NEC_NL6448AC33:
1091 1096
1092 NEC NL6448AC33-18. Active, color, single scan. 1097 NEC NL6448AC33-18. Active, color, single scan.
1093 1098
1094 CONFIG_NEC_NL6448BC20 1099 CONFIG_NEC_NL6448BC20
1095 1100
1096 NEC NL6448BC20-08. 6.5", 640x480. 1101 NEC NL6448BC20-08. 6.5", 640x480.
1097 Active, color, single scan. 1102 Active, color, single scan.
1098 1103
1099 CONFIG_NEC_NL6448BC33_54 1104 CONFIG_NEC_NL6448BC33_54
1100 1105
1101 NEC NL6448BC33-54. 10.4", 640x480. 1106 NEC NL6448BC33-54. 10.4", 640x480.
1102 Active, color, single scan. 1107 Active, color, single scan.
1103 1108
1104 CONFIG_SHARP_16x9 1109 CONFIG_SHARP_16x9
1105 1110
1106 Sharp 320x240. Active, color, single scan. 1111 Sharp 320x240. Active, color, single scan.
1107 It isn't 16x9, and I am not sure what it is. 1112 It isn't 16x9, and I am not sure what it is.
1108 1113
1109 CONFIG_SHARP_LQ64D341 1114 CONFIG_SHARP_LQ64D341
1110 1115
1111 Sharp LQ64D341 display, 640x480. 1116 Sharp LQ64D341 display, 640x480.
1112 Active, color, single scan. 1117 Active, color, single scan.
1113 1118
1114 CONFIG_HLD1045 1119 CONFIG_HLD1045
1115 1120
1116 HLD1045 display, 640x480. 1121 HLD1045 display, 640x480.
1117 Active, color, single scan. 1122 Active, color, single scan.
1118 1123
1119 CONFIG_OPTREX_BW 1124 CONFIG_OPTREX_BW
1120 1125
1121 Optrex CBL50840-2 NF-FW 99 22 M5 1126 Optrex CBL50840-2 NF-FW 99 22 M5
1122 or 1127 or
1123 Hitachi LMG6912RPFC-00T 1128 Hitachi LMG6912RPFC-00T
1124 or 1129 or
1125 Hitachi SP14Q002 1130 Hitachi SP14Q002
1126 1131
1127 320x240. Black & white. 1132 320x240. Black & white.
1128 1133
1129 Normally display is black on white background; define 1134 Normally display is black on white background; define
1130 CONFIG_SYS_WHITE_ON_BLACK to get it inverted. 1135 CONFIG_SYS_WHITE_ON_BLACK to get it inverted.
1131 1136
1132 - Splash Screen Support: CONFIG_SPLASH_SCREEN 1137 - Splash Screen Support: CONFIG_SPLASH_SCREEN
1133 1138
1134 If this option is set, the environment is checked for 1139 If this option is set, the environment is checked for
1135 a variable "splashimage". If found, the usual display 1140 a variable "splashimage". If found, the usual display
1136 of logo, copyright and system information on the LCD 1141 of logo, copyright and system information on the LCD
1137 is suppressed and the BMP image at the address 1142 is suppressed and the BMP image at the address
1138 specified in "splashimage" is loaded instead. The 1143 specified in "splashimage" is loaded instead. The
1139 console is redirected to the "nulldev", too. This 1144 console is redirected to the "nulldev", too. This
1140 allows for a "silent" boot where a splash screen is 1145 allows for a "silent" boot where a splash screen is
1141 loaded very quickly after power-on. 1146 loaded very quickly after power-on.
1142 1147
1143 CONFIG_SPLASH_SCREEN_ALIGN 1148 CONFIG_SPLASH_SCREEN_ALIGN
1144 1149
1145 If this option is set the splash image can be freely positioned 1150 If this option is set the splash image can be freely positioned
1146 on the screen. Environment variable "splashpos" specifies the 1151 on the screen. Environment variable "splashpos" specifies the
1147 position as "x,y". If a positive number is given it is used as 1152 position as "x,y". If a positive number is given it is used as
1148 number of pixel from left/top. If a negative number is given it 1153 number of pixel from left/top. If a negative number is given it
1149 is used as number of pixel from right/bottom. You can also 1154 is used as number of pixel from right/bottom. You can also
1150 specify 'm' for centering the image. 1155 specify 'm' for centering the image.
1151 1156
1152 Example: 1157 Example:
1153 setenv splashpos m,m 1158 setenv splashpos m,m
1154 => image at center of screen 1159 => image at center of screen
1155 1160
1156 setenv splashpos 30,20 1161 setenv splashpos 30,20
1157 => image at x = 30 and y = 20 1162 => image at x = 30 and y = 20
1158 1163
1159 setenv splashpos -10,m 1164 setenv splashpos -10,m
1160 => vertically centered image 1165 => vertically centered image
1161 at x = dspWidth - bmpWidth - 9 1166 at x = dspWidth - bmpWidth - 9
1162 1167
1163 - Gzip compressed BMP image support: CONFIG_VIDEO_BMP_GZIP 1168 - Gzip compressed BMP image support: CONFIG_VIDEO_BMP_GZIP
1164 1169
1165 If this option is set, additionally to standard BMP 1170 If this option is set, additionally to standard BMP
1166 images, gzipped BMP images can be displayed via the 1171 images, gzipped BMP images can be displayed via the
1167 splashscreen support or the bmp command. 1172 splashscreen support or the bmp command.
1168 1173
1169 - Run length encoded BMP image (RLE8) support: CONFIG_VIDEO_BMP_RLE8 1174 - Run length encoded BMP image (RLE8) support: CONFIG_VIDEO_BMP_RLE8
1170 1175
1171 If this option is set, 8-bit RLE compressed BMP images 1176 If this option is set, 8-bit RLE compressed BMP images
1172 can be displayed via the splashscreen support or the 1177 can be displayed via the splashscreen support or the
1173 bmp command. 1178 bmp command.
1174 1179
1175 - Compression support: 1180 - Compression support:
1176 CONFIG_BZIP2 1181 CONFIG_BZIP2
1177 1182
1178 If this option is set, support for bzip2 compressed 1183 If this option is set, support for bzip2 compressed
1179 images is included. If not, only uncompressed and gzip 1184 images is included. If not, only uncompressed and gzip
1180 compressed images are supported. 1185 compressed images are supported.
1181 1186
1182 NOTE: the bzip2 algorithm requires a lot of RAM, so 1187 NOTE: the bzip2 algorithm requires a lot of RAM, so
1183 the malloc area (as defined by CONFIG_SYS_MALLOC_LEN) should 1188 the malloc area (as defined by CONFIG_SYS_MALLOC_LEN) should
1184 be at least 4MB. 1189 be at least 4MB.
1185 1190
1186 CONFIG_LZMA 1191 CONFIG_LZMA
1187 1192
1188 If this option is set, support for lzma compressed 1193 If this option is set, support for lzma compressed
1189 images is included. 1194 images is included.
1190 1195
1191 Note: The LZMA algorithm adds between 2 and 4KB of code and it 1196 Note: The LZMA algorithm adds between 2 and 4KB of code and it
1192 requires an amount of dynamic memory that is given by the 1197 requires an amount of dynamic memory that is given by the
1193 formula: 1198 formula:
1194 1199
1195 (1846 + 768 << (lc + lp)) * sizeof(uint16) 1200 (1846 + 768 << (lc + lp)) * sizeof(uint16)
1196 1201
1197 Where lc and lp stand for, respectively, Literal context bits 1202 Where lc and lp stand for, respectively, Literal context bits
1198 and Literal pos bits. 1203 and Literal pos bits.
1199 1204
1200 This value is upper-bounded by 14MB in the worst case. Anyway, 1205 This value is upper-bounded by 14MB in the worst case. Anyway,
1201 for a ~4MB large kernel image, we have lc=3 and lp=0 for a 1206 for a ~4MB large kernel image, we have lc=3 and lp=0 for a
1202 total amount of (1846 + 768 << (3 + 0)) * 2 = ~41KB... that is 1207 total amount of (1846 + 768 << (3 + 0)) * 2 = ~41KB... that is
1203 a very small buffer. 1208 a very small buffer.
1204 1209
1205 Use the lzmainfo tool to determinate the lc and lp values and 1210 Use the lzmainfo tool to determinate the lc and lp values and
1206 then calculate the amount of needed dynamic memory (ensuring 1211 then calculate the amount of needed dynamic memory (ensuring
1207 the appropriate CONFIG_SYS_MALLOC_LEN value). 1212 the appropriate CONFIG_SYS_MALLOC_LEN value).
1208 1213
1209 - MII/PHY support: 1214 - MII/PHY support:
1210 CONFIG_PHY_ADDR 1215 CONFIG_PHY_ADDR
1211 1216
1212 The address of PHY on MII bus. 1217 The address of PHY on MII bus.
1213 1218
1214 CONFIG_PHY_CLOCK_FREQ (ppc4xx) 1219 CONFIG_PHY_CLOCK_FREQ (ppc4xx)
1215 1220
1216 The clock frequency of the MII bus 1221 The clock frequency of the MII bus
1217 1222
1218 CONFIG_PHY_GIGE 1223 CONFIG_PHY_GIGE
1219 1224
1220 If this option is set, support for speed/duplex 1225 If this option is set, support for speed/duplex
1221 detection of gigabit PHY is included. 1226 detection of gigabit PHY is included.
1222 1227
1223 CONFIG_PHY_RESET_DELAY 1228 CONFIG_PHY_RESET_DELAY
1224 1229
1225 Some PHY like Intel LXT971A need extra delay after 1230 Some PHY like Intel LXT971A need extra delay after
1226 reset before any MII register access is possible. 1231 reset before any MII register access is possible.
1227 For such PHY, set this option to the usec delay 1232 For such PHY, set this option to the usec delay
1228 required. (minimum 300usec for LXT971A) 1233 required. (minimum 300usec for LXT971A)
1229 1234
1230 CONFIG_PHY_CMD_DELAY (ppc4xx) 1235 CONFIG_PHY_CMD_DELAY (ppc4xx)
1231 1236
1232 Some PHY like Intel LXT971A need extra delay after 1237 Some PHY like Intel LXT971A need extra delay after
1233 command issued before MII status register can be read 1238 command issued before MII status register can be read
1234 1239
1235 - Ethernet address: 1240 - Ethernet address:
1236 CONFIG_ETHADDR 1241 CONFIG_ETHADDR
1237 CONFIG_ETH1ADDR 1242 CONFIG_ETH1ADDR
1238 CONFIG_ETH2ADDR 1243 CONFIG_ETH2ADDR
1239 CONFIG_ETH3ADDR 1244 CONFIG_ETH3ADDR
1240 CONFIG_ETH4ADDR 1245 CONFIG_ETH4ADDR
1241 CONFIG_ETH5ADDR 1246 CONFIG_ETH5ADDR
1242 1247
1243 Define a default value for Ethernet address to use 1248 Define a default value for Ethernet address to use
1244 for the respective Ethernet interface, in case this 1249 for the respective Ethernet interface, in case this
1245 is not determined automatically. 1250 is not determined automatically.
1246 1251
1247 - IP address: 1252 - IP address:
1248 CONFIG_IPADDR 1253 CONFIG_IPADDR
1249 1254
1250 Define a default value for the IP address to use for 1255 Define a default value for the IP address to use for
1251 the default Ethernet interface, in case this is not 1256 the default Ethernet interface, in case this is not
1252 determined through e.g. bootp. 1257 determined through e.g. bootp.
1253 1258
1254 - Server IP address: 1259 - Server IP address:
1255 CONFIG_SERVERIP 1260 CONFIG_SERVERIP
1256 1261
1257 Defines a default value for the IP address of a TFTP 1262 Defines a default value for the IP address of a TFTP
1258 server to contact when using the "tftboot" command. 1263 server to contact when using the "tftboot" command.
1259 1264
1260 CONFIG_KEEP_SERVERADDR 1265 CONFIG_KEEP_SERVERADDR
1261 1266
1262 Keeps the server's MAC address, in the env 'serveraddr' 1267 Keeps the server's MAC address, in the env 'serveraddr'
1263 for passing to bootargs (like Linux's netconsole option) 1268 for passing to bootargs (like Linux's netconsole option)
1264 1269
1265 - Multicast TFTP Mode: 1270 - Multicast TFTP Mode:
1266 CONFIG_MCAST_TFTP 1271 CONFIG_MCAST_TFTP
1267 1272
1268 Defines whether you want to support multicast TFTP as per 1273 Defines whether you want to support multicast TFTP as per
1269 rfc-2090; for example to work with atftp. Lets lots of targets 1274 rfc-2090; for example to work with atftp. Lets lots of targets
1270 tftp down the same boot image concurrently. Note: the Ethernet 1275 tftp down the same boot image concurrently. Note: the Ethernet
1271 driver in use must provide a function: mcast() to join/leave a 1276 driver in use must provide a function: mcast() to join/leave a
1272 multicast group. 1277 multicast group.
1273 1278
1274 CONFIG_BOOTP_RANDOM_DELAY 1279 CONFIG_BOOTP_RANDOM_DELAY
1275 - BOOTP Recovery Mode: 1280 - BOOTP Recovery Mode:
1276 CONFIG_BOOTP_RANDOM_DELAY 1281 CONFIG_BOOTP_RANDOM_DELAY
1277 1282
1278 If you have many targets in a network that try to 1283 If you have many targets in a network that try to
1279 boot using BOOTP, you may want to avoid that all 1284 boot using BOOTP, you may want to avoid that all
1280 systems send out BOOTP requests at precisely the same 1285 systems send out BOOTP requests at precisely the same
1281 moment (which would happen for instance at recovery 1286 moment (which would happen for instance at recovery
1282 from a power failure, when all systems will try to 1287 from a power failure, when all systems will try to
1283 boot, thus flooding the BOOTP server. Defining 1288 boot, thus flooding the BOOTP server. Defining
1284 CONFIG_BOOTP_RANDOM_DELAY causes a random delay to be 1289 CONFIG_BOOTP_RANDOM_DELAY causes a random delay to be
1285 inserted before sending out BOOTP requests. The 1290 inserted before sending out BOOTP requests. The
1286 following delays are inserted then: 1291 following delays are inserted then:
1287 1292
1288 1st BOOTP request: delay 0 ... 1 sec 1293 1st BOOTP request: delay 0 ... 1 sec
1289 2nd BOOTP request: delay 0 ... 2 sec 1294 2nd BOOTP request: delay 0 ... 2 sec
1290 3rd BOOTP request: delay 0 ... 4 sec 1295 3rd BOOTP request: delay 0 ... 4 sec
1291 4th and following 1296 4th and following
1292 BOOTP requests: delay 0 ... 8 sec 1297 BOOTP requests: delay 0 ... 8 sec
1293 1298
1294 - DHCP Advanced Options: 1299 - DHCP Advanced Options:
1295 You can fine tune the DHCP functionality by defining 1300 You can fine tune the DHCP functionality by defining
1296 CONFIG_BOOTP_* symbols: 1301 CONFIG_BOOTP_* symbols:
1297 1302
1298 CONFIG_BOOTP_SUBNETMASK 1303 CONFIG_BOOTP_SUBNETMASK
1299 CONFIG_BOOTP_GATEWAY 1304 CONFIG_BOOTP_GATEWAY
1300 CONFIG_BOOTP_HOSTNAME 1305 CONFIG_BOOTP_HOSTNAME
1301 CONFIG_BOOTP_NISDOMAIN 1306 CONFIG_BOOTP_NISDOMAIN
1302 CONFIG_BOOTP_BOOTPATH 1307 CONFIG_BOOTP_BOOTPATH
1303 CONFIG_BOOTP_BOOTFILESIZE 1308 CONFIG_BOOTP_BOOTFILESIZE
1304 CONFIG_BOOTP_DNS 1309 CONFIG_BOOTP_DNS
1305 CONFIG_BOOTP_DNS2 1310 CONFIG_BOOTP_DNS2
1306 CONFIG_BOOTP_SEND_HOSTNAME 1311 CONFIG_BOOTP_SEND_HOSTNAME
1307 CONFIG_BOOTP_NTPSERVER 1312 CONFIG_BOOTP_NTPSERVER
1308 CONFIG_BOOTP_TIMEOFFSET 1313 CONFIG_BOOTP_TIMEOFFSET
1309 CONFIG_BOOTP_VENDOREX 1314 CONFIG_BOOTP_VENDOREX
1310 1315
1311 CONFIG_BOOTP_SERVERIP - TFTP server will be the serverip 1316 CONFIG_BOOTP_SERVERIP - TFTP server will be the serverip
1312 environment variable, not the BOOTP server. 1317 environment variable, not the BOOTP server.
1313 1318
1314 CONFIG_BOOTP_DNS2 - If a DHCP client requests the DNS 1319 CONFIG_BOOTP_DNS2 - If a DHCP client requests the DNS
1315 serverip from a DHCP server, it is possible that more 1320 serverip from a DHCP server, it is possible that more
1316 than one DNS serverip is offered to the client. 1321 than one DNS serverip is offered to the client.
1317 If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS 1322 If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS
1318 serverip will be stored in the additional environment 1323 serverip will be stored in the additional environment
1319 variable "dnsip2". The first DNS serverip is always 1324 variable "dnsip2". The first DNS serverip is always
1320 stored in the variable "dnsip", when CONFIG_BOOTP_DNS 1325 stored in the variable "dnsip", when CONFIG_BOOTP_DNS
1321 is defined. 1326 is defined.
1322 1327
1323 CONFIG_BOOTP_SEND_HOSTNAME - Some DHCP servers are capable 1328 CONFIG_BOOTP_SEND_HOSTNAME - Some DHCP servers are capable
1324 to do a dynamic update of a DNS server. To do this, they 1329 to do a dynamic update of a DNS server. To do this, they
1325 need the hostname of the DHCP requester. 1330 need the hostname of the DHCP requester.
1326 If CONFIG_BOOTP_SEND_HOSTNAME is defined, the content 1331 If CONFIG_BOOTP_SEND_HOSTNAME is defined, the content
1327 of the "hostname" environment variable is passed as 1332 of the "hostname" environment variable is passed as
1328 option 12 to the DHCP server. 1333 option 12 to the DHCP server.
1329 1334
1330 CONFIG_BOOTP_DHCP_REQUEST_DELAY 1335 CONFIG_BOOTP_DHCP_REQUEST_DELAY
1331 1336
1332 A 32bit value in microseconds for a delay between 1337 A 32bit value in microseconds for a delay between
1333 receiving a "DHCP Offer" and sending the "DHCP Request". 1338 receiving a "DHCP Offer" and sending the "DHCP Request".
1334 This fixes a problem with certain DHCP servers that don't 1339 This fixes a problem with certain DHCP servers that don't
1335 respond 100% of the time to a "DHCP request". E.g. On an 1340 respond 100% of the time to a "DHCP request". E.g. On an
1336 AT91RM9200 processor running at 180MHz, this delay needed 1341 AT91RM9200 processor running at 180MHz, this delay needed
1337 to be *at least* 15,000 usec before a Windows Server 2003 1342 to be *at least* 15,000 usec before a Windows Server 2003
1338 DHCP server would reply 100% of the time. I recommend at 1343 DHCP server would reply 100% of the time. I recommend at
1339 least 50,000 usec to be safe. The alternative is to hope 1344 least 50,000 usec to be safe. The alternative is to hope
1340 that one of the retries will be successful but note that 1345 that one of the retries will be successful but note that
1341 the DHCP timeout and retry process takes a longer than 1346 the DHCP timeout and retry process takes a longer than
1342 this delay. 1347 this delay.
1343 1348
1344 - CDP Options: 1349 - CDP Options:
1345 CONFIG_CDP_DEVICE_ID 1350 CONFIG_CDP_DEVICE_ID
1346 1351
1347 The device id used in CDP trigger frames. 1352 The device id used in CDP trigger frames.
1348 1353
1349 CONFIG_CDP_DEVICE_ID_PREFIX 1354 CONFIG_CDP_DEVICE_ID_PREFIX
1350 1355
1351 A two character string which is prefixed to the MAC address 1356 A two character string which is prefixed to the MAC address
1352 of the device. 1357 of the device.
1353 1358
1354 CONFIG_CDP_PORT_ID 1359 CONFIG_CDP_PORT_ID
1355 1360
1356 A printf format string which contains the ascii name of 1361 A printf format string which contains the ascii name of
1357 the port. Normally is set to "eth%d" which sets 1362 the port. Normally is set to "eth%d" which sets
1358 eth0 for the first Ethernet, eth1 for the second etc. 1363 eth0 for the first Ethernet, eth1 for the second etc.
1359 1364
1360 CONFIG_CDP_CAPABILITIES 1365 CONFIG_CDP_CAPABILITIES
1361 1366
1362 A 32bit integer which indicates the device capabilities; 1367 A 32bit integer which indicates the device capabilities;
1363 0x00000010 for a normal host which does not forwards. 1368 0x00000010 for a normal host which does not forwards.
1364 1369
1365 CONFIG_CDP_VERSION 1370 CONFIG_CDP_VERSION
1366 1371
1367 An ascii string containing the version of the software. 1372 An ascii string containing the version of the software.
1368 1373
1369 CONFIG_CDP_PLATFORM 1374 CONFIG_CDP_PLATFORM
1370 1375
1371 An ascii string containing the name of the platform. 1376 An ascii string containing the name of the platform.
1372 1377
1373 CONFIG_CDP_TRIGGER 1378 CONFIG_CDP_TRIGGER
1374 1379
1375 A 32bit integer sent on the trigger. 1380 A 32bit integer sent on the trigger.
1376 1381
1377 CONFIG_CDP_POWER_CONSUMPTION 1382 CONFIG_CDP_POWER_CONSUMPTION
1378 1383
1379 A 16bit integer containing the power consumption of the 1384 A 16bit integer containing the power consumption of the
1380 device in .1 of milliwatts. 1385 device in .1 of milliwatts.
1381 1386
1382 CONFIG_CDP_APPLIANCE_VLAN_TYPE 1387 CONFIG_CDP_APPLIANCE_VLAN_TYPE
1383 1388
1384 A byte containing the id of the VLAN. 1389 A byte containing the id of the VLAN.
1385 1390
1386 - Status LED: CONFIG_STATUS_LED 1391 - Status LED: CONFIG_STATUS_LED
1387 1392
1388 Several configurations allow to display the current 1393 Several configurations allow to display the current
1389 status using a LED. For instance, the LED will blink 1394 status using a LED. For instance, the LED will blink
1390 fast while running U-Boot code, stop blinking as 1395 fast while running U-Boot code, stop blinking as
1391 soon as a reply to a BOOTP request was received, and 1396 soon as a reply to a BOOTP request was received, and
1392 start blinking slow once the Linux kernel is running 1397 start blinking slow once the Linux kernel is running
1393 (supported by a status LED driver in the Linux 1398 (supported by a status LED driver in the Linux
1394 kernel). Defining CONFIG_STATUS_LED enables this 1399 kernel). Defining CONFIG_STATUS_LED enables this
1395 feature in U-Boot. 1400 feature in U-Boot.
1396 1401
1397 - CAN Support: CONFIG_CAN_DRIVER 1402 - CAN Support: CONFIG_CAN_DRIVER
1398 1403
1399 Defining CONFIG_CAN_DRIVER enables CAN driver support 1404 Defining CONFIG_CAN_DRIVER enables CAN driver support
1400 on those systems that support this (optional) 1405 on those systems that support this (optional)
1401 feature, like the TQM8xxL modules. 1406 feature, like the TQM8xxL modules.
1402 1407
1403 - I2C Support: CONFIG_HARD_I2C | CONFIG_SOFT_I2C 1408 - I2C Support: CONFIG_HARD_I2C | CONFIG_SOFT_I2C
1404 1409
1405 These enable I2C serial bus commands. Defining either of 1410 These enable I2C serial bus commands. Defining either of
1406 (but not both of) CONFIG_HARD_I2C or CONFIG_SOFT_I2C will 1411 (but not both of) CONFIG_HARD_I2C or CONFIG_SOFT_I2C will
1407 include the appropriate I2C driver for the selected CPU. 1412 include the appropriate I2C driver for the selected CPU.
1408 1413
1409 This will allow you to use i2c commands at the u-boot 1414 This will allow you to use i2c commands at the u-boot
1410 command line (as long as you set CONFIG_CMD_I2C in 1415 command line (as long as you set CONFIG_CMD_I2C in
1411 CONFIG_COMMANDS) and communicate with i2c based realtime 1416 CONFIG_COMMANDS) and communicate with i2c based realtime
1412 clock chips. See common/cmd_i2c.c for a description of the 1417 clock chips. See common/cmd_i2c.c for a description of the
1413 command line interface. 1418 command line interface.
1414 1419
1415 CONFIG_HARD_I2C selects a hardware I2C controller. 1420 CONFIG_HARD_I2C selects a hardware I2C controller.
1416 1421
1417 CONFIG_SOFT_I2C configures u-boot to use a software (aka 1422 CONFIG_SOFT_I2C configures u-boot to use a software (aka
1418 bit-banging) driver instead of CPM or similar hardware 1423 bit-banging) driver instead of CPM or similar hardware
1419 support for I2C. 1424 support for I2C.
1420 1425
1421 There are several other quantities that must also be 1426 There are several other quantities that must also be
1422 defined when you define CONFIG_HARD_I2C or CONFIG_SOFT_I2C. 1427 defined when you define CONFIG_HARD_I2C or CONFIG_SOFT_I2C.
1423 1428
1424 In both cases you will need to define CONFIG_SYS_I2C_SPEED 1429 In both cases you will need to define CONFIG_SYS_I2C_SPEED
1425 to be the frequency (in Hz) at which you wish your i2c bus 1430 to be the frequency (in Hz) at which you wish your i2c bus
1426 to run and CONFIG_SYS_I2C_SLAVE to be the address of this node (ie 1431 to run and CONFIG_SYS_I2C_SLAVE to be the address of this node (ie
1427 the CPU's i2c node address). 1432 the CPU's i2c node address).
1428 1433
1429 Now, the u-boot i2c code for the mpc8xx 1434 Now, the u-boot i2c code for the mpc8xx
1430 (arch/powerpc/cpu/mpc8xx/i2c.c) sets the CPU up as a master node 1435 (arch/powerpc/cpu/mpc8xx/i2c.c) sets the CPU up as a master node
1431 and so its address should therefore be cleared to 0 (See, 1436 and so its address should therefore be cleared to 0 (See,
1432 eg, MPC823e User's Manual p.16-473). So, set 1437 eg, MPC823e User's Manual p.16-473). So, set
1433 CONFIG_SYS_I2C_SLAVE to 0. 1438 CONFIG_SYS_I2C_SLAVE to 0.
1434 1439
1435 CONFIG_SYS_I2C_INIT_MPC5XXX 1440 CONFIG_SYS_I2C_INIT_MPC5XXX
1436 1441
1437 When a board is reset during an i2c bus transfer 1442 When a board is reset during an i2c bus transfer
1438 chips might think that the current transfer is still 1443 chips might think that the current transfer is still
1439 in progress. Reset the slave devices by sending start 1444 in progress. Reset the slave devices by sending start
1440 commands until the slave device responds. 1445 commands until the slave device responds.
1441 1446
1442 That's all that's required for CONFIG_HARD_I2C. 1447 That's all that's required for CONFIG_HARD_I2C.
1443 1448
1444 If you use the software i2c interface (CONFIG_SOFT_I2C) 1449 If you use the software i2c interface (CONFIG_SOFT_I2C)
1445 then the following macros need to be defined (examples are 1450 then the following macros need to be defined (examples are
1446 from include/configs/lwmon.h): 1451 from include/configs/lwmon.h):
1447 1452
1448 I2C_INIT 1453 I2C_INIT
1449 1454
1450 (Optional). Any commands necessary to enable the I2C 1455 (Optional). Any commands necessary to enable the I2C
1451 controller or configure ports. 1456 controller or configure ports.
1452 1457
1453 eg: #define I2C_INIT (immr->im_cpm.cp_pbdir |= PB_SCL) 1458 eg: #define I2C_INIT (immr->im_cpm.cp_pbdir |= PB_SCL)
1454 1459
1455 I2C_PORT 1460 I2C_PORT
1456 1461
1457 (Only for MPC8260 CPU). The I/O port to use (the code 1462 (Only for MPC8260 CPU). The I/O port to use (the code
1458 assumes both bits are on the same port). Valid values 1463 assumes both bits are on the same port). Valid values
1459 are 0..3 for ports A..D. 1464 are 0..3 for ports A..D.
1460 1465
1461 I2C_ACTIVE 1466 I2C_ACTIVE
1462 1467
1463 The code necessary to make the I2C data line active 1468 The code necessary to make the I2C data line active
1464 (driven). If the data line is open collector, this 1469 (driven). If the data line is open collector, this
1465 define can be null. 1470 define can be null.
1466 1471
1467 eg: #define I2C_ACTIVE (immr->im_cpm.cp_pbdir |= PB_SDA) 1472 eg: #define I2C_ACTIVE (immr->im_cpm.cp_pbdir |= PB_SDA)
1468 1473
1469 I2C_TRISTATE 1474 I2C_TRISTATE
1470 1475
1471 The code necessary to make the I2C data line tri-stated 1476 The code necessary to make the I2C data line tri-stated
1472 (inactive). If the data line is open collector, this 1477 (inactive). If the data line is open collector, this
1473 define can be null. 1478 define can be null.
1474 1479
1475 eg: #define I2C_TRISTATE (immr->im_cpm.cp_pbdir &= ~PB_SDA) 1480 eg: #define I2C_TRISTATE (immr->im_cpm.cp_pbdir &= ~PB_SDA)
1476 1481
1477 I2C_READ 1482 I2C_READ
1478 1483
1479 Code that returns TRUE if the I2C data line is high, 1484 Code that returns TRUE if the I2C data line is high,
1480 FALSE if it is low. 1485 FALSE if it is low.
1481 1486
1482 eg: #define I2C_READ ((immr->im_cpm.cp_pbdat & PB_SDA) != 0) 1487 eg: #define I2C_READ ((immr->im_cpm.cp_pbdat & PB_SDA) != 0)
1483 1488
1484 I2C_SDA(bit) 1489 I2C_SDA(bit)
1485 1490
1486 If <bit> is TRUE, sets the I2C data line high. If it 1491 If <bit> is TRUE, sets the I2C data line high. If it
1487 is FALSE, it clears it (low). 1492 is FALSE, it clears it (low).
1488 1493
1489 eg: #define I2C_SDA(bit) \ 1494 eg: #define I2C_SDA(bit) \
1490 if(bit) immr->im_cpm.cp_pbdat |= PB_SDA; \ 1495 if(bit) immr->im_cpm.cp_pbdat |= PB_SDA; \
1491 else immr->im_cpm.cp_pbdat &= ~PB_SDA 1496 else immr->im_cpm.cp_pbdat &= ~PB_SDA
1492 1497
1493 I2C_SCL(bit) 1498 I2C_SCL(bit)
1494 1499
1495 If <bit> is TRUE, sets the I2C clock line high. If it 1500 If <bit> is TRUE, sets the I2C clock line high. If it
1496 is FALSE, it clears it (low). 1501 is FALSE, it clears it (low).
1497 1502
1498 eg: #define I2C_SCL(bit) \ 1503 eg: #define I2C_SCL(bit) \
1499 if(bit) immr->im_cpm.cp_pbdat |= PB_SCL; \ 1504 if(bit) immr->im_cpm.cp_pbdat |= PB_SCL; \
1500 else immr->im_cpm.cp_pbdat &= ~PB_SCL 1505 else immr->im_cpm.cp_pbdat &= ~PB_SCL
1501 1506
1502 I2C_DELAY 1507 I2C_DELAY
1503 1508
1504 This delay is invoked four times per clock cycle so this 1509 This delay is invoked four times per clock cycle so this
1505 controls the rate of data transfer. The data rate thus 1510 controls the rate of data transfer. The data rate thus
1506 is 1 / (I2C_DELAY * 4). Often defined to be something 1511 is 1 / (I2C_DELAY * 4). Often defined to be something
1507 like: 1512 like:
1508 1513
1509 #define I2C_DELAY udelay(2) 1514 #define I2C_DELAY udelay(2)
1510 1515
1511 CONFIG_SOFT_I2C_GPIO_SCL / CONFIG_SOFT_I2C_GPIO_SDA 1516 CONFIG_SOFT_I2C_GPIO_SCL / CONFIG_SOFT_I2C_GPIO_SDA
1512 1517
1513 If your arch supports the generic GPIO framework (asm/gpio.h), 1518 If your arch supports the generic GPIO framework (asm/gpio.h),
1514 then you may alternatively define the two GPIOs that are to be 1519 then you may alternatively define the two GPIOs that are to be
1515 used as SCL / SDA. Any of the previous I2C_xxx macros will 1520 used as SCL / SDA. Any of the previous I2C_xxx macros will
1516 have GPIO-based defaults assigned to them as appropriate. 1521 have GPIO-based defaults assigned to them as appropriate.
1517 1522
1518 You should define these to the GPIO value as given directly to 1523 You should define these to the GPIO value as given directly to
1519 the generic GPIO functions. 1524 the generic GPIO functions.
1520 1525
1521 CONFIG_SYS_I2C_INIT_BOARD 1526 CONFIG_SYS_I2C_INIT_BOARD
1522 1527
1523 When a board is reset during an i2c bus transfer 1528 When a board is reset during an i2c bus transfer
1524 chips might think that the current transfer is still 1529 chips might think that the current transfer is still
1525 in progress. On some boards it is possible to access 1530 in progress. On some boards it is possible to access
1526 the i2c SCLK line directly, either by using the 1531 the i2c SCLK line directly, either by using the
1527 processor pin as a GPIO or by having a second pin 1532 processor pin as a GPIO or by having a second pin
1528 connected to the bus. If this option is defined a 1533 connected to the bus. If this option is defined a
1529 custom i2c_init_board() routine in boards/xxx/board.c 1534 custom i2c_init_board() routine in boards/xxx/board.c
1530 is run early in the boot sequence. 1535 is run early in the boot sequence.
1531 1536
1532 CONFIG_SYS_I2C_BOARD_LATE_INIT 1537 CONFIG_SYS_I2C_BOARD_LATE_INIT
1533 1538
1534 An alternative to CONFIG_SYS_I2C_INIT_BOARD. If this option is 1539 An alternative to CONFIG_SYS_I2C_INIT_BOARD. If this option is
1535 defined a custom i2c_board_late_init() routine in 1540 defined a custom i2c_board_late_init() routine in
1536 boards/xxx/board.c is run AFTER the operations in i2c_init() 1541 boards/xxx/board.c is run AFTER the operations in i2c_init()
1537 is completed. This callpoint can be used to unreset i2c bus 1542 is completed. This callpoint can be used to unreset i2c bus
1538 using CPU i2c controller register accesses for CPUs whose i2c 1543 using CPU i2c controller register accesses for CPUs whose i2c
1539 controller provide such a method. It is called at the end of 1544 controller provide such a method. It is called at the end of
1540 i2c_init() to allow i2c_init operations to setup the i2c bus 1545 i2c_init() to allow i2c_init operations to setup the i2c bus
1541 controller on the CPU (e.g. setting bus speed & slave address). 1546 controller on the CPU (e.g. setting bus speed & slave address).
1542 1547
1543 CONFIG_I2CFAST (PPC405GP|PPC405EP only) 1548 CONFIG_I2CFAST (PPC405GP|PPC405EP only)
1544 1549
1545 This option enables configuration of bi_iic_fast[] flags 1550 This option enables configuration of bi_iic_fast[] flags
1546 in u-boot bd_info structure based on u-boot environment 1551 in u-boot bd_info structure based on u-boot environment
1547 variable "i2cfast". (see also i2cfast) 1552 variable "i2cfast". (see also i2cfast)
1548 1553
1549 CONFIG_I2C_MULTI_BUS 1554 CONFIG_I2C_MULTI_BUS
1550 1555
1551 This option allows the use of multiple I2C buses, each of which 1556 This option allows the use of multiple I2C buses, each of which
1552 must have a controller. At any point in time, only one bus is 1557 must have a controller. At any point in time, only one bus is
1553 active. To switch to a different bus, use the 'i2c dev' command. 1558 active. To switch to a different bus, use the 'i2c dev' command.
1554 Note that bus numbering is zero-based. 1559 Note that bus numbering is zero-based.
1555 1560
1556 CONFIG_SYS_I2C_NOPROBES 1561 CONFIG_SYS_I2C_NOPROBES
1557 1562
1558 This option specifies a list of I2C devices that will be skipped 1563 This option specifies a list of I2C devices that will be skipped
1559 when the 'i2c probe' command is issued. If CONFIG_I2C_MULTI_BUS 1564 when the 'i2c probe' command is issued. If CONFIG_I2C_MULTI_BUS
1560 is set, specify a list of bus-device pairs. Otherwise, specify 1565 is set, specify a list of bus-device pairs. Otherwise, specify
1561 a 1D array of device addresses 1566 a 1D array of device addresses
1562 1567
1563 e.g. 1568 e.g.
1564 #undef CONFIG_I2C_MULTI_BUS 1569 #undef CONFIG_I2C_MULTI_BUS
1565 #define CONFIG_SYS_I2C_NOPROBES {0x50,0x68} 1570 #define CONFIG_SYS_I2C_NOPROBES {0x50,0x68}
1566 1571
1567 will skip addresses 0x50 and 0x68 on a board with one I2C bus 1572 will skip addresses 0x50 and 0x68 on a board with one I2C bus
1568 1573
1569 #define CONFIG_I2C_MULTI_BUS 1574 #define CONFIG_I2C_MULTI_BUS
1570 #define CONFIG_SYS_I2C_MULTI_NOPROBES {{0,0x50},{0,0x68},{1,0x54}} 1575 #define CONFIG_SYS_I2C_MULTI_NOPROBES {{0,0x50},{0,0x68},{1,0x54}}
1571 1576
1572 will skip addresses 0x50 and 0x68 on bus 0 and address 0x54 on bus 1 1577 will skip addresses 0x50 and 0x68 on bus 0 and address 0x54 on bus 1
1573 1578
1574 CONFIG_SYS_SPD_BUS_NUM 1579 CONFIG_SYS_SPD_BUS_NUM
1575 1580
1576 If defined, then this indicates the I2C bus number for DDR SPD. 1581 If defined, then this indicates the I2C bus number for DDR SPD.
1577 If not defined, then U-Boot assumes that SPD is on I2C bus 0. 1582 If not defined, then U-Boot assumes that SPD is on I2C bus 0.
1578 1583
1579 CONFIG_SYS_RTC_BUS_NUM 1584 CONFIG_SYS_RTC_BUS_NUM
1580 1585
1581 If defined, then this indicates the I2C bus number for the RTC. 1586 If defined, then this indicates the I2C bus number for the RTC.
1582 If not defined, then U-Boot assumes that RTC is on I2C bus 0. 1587 If not defined, then U-Boot assumes that RTC is on I2C bus 0.
1583 1588
1584 CONFIG_SYS_DTT_BUS_NUM 1589 CONFIG_SYS_DTT_BUS_NUM
1585 1590
1586 If defined, then this indicates the I2C bus number for the DTT. 1591 If defined, then this indicates the I2C bus number for the DTT.
1587 If not defined, then U-Boot assumes that DTT is on I2C bus 0. 1592 If not defined, then U-Boot assumes that DTT is on I2C bus 0.
1588 1593
1589 CONFIG_SYS_I2C_DTT_ADDR: 1594 CONFIG_SYS_I2C_DTT_ADDR:
1590 1595
1591 If defined, specifies the I2C address of the DTT device. 1596 If defined, specifies the I2C address of the DTT device.
1592 If not defined, then U-Boot uses predefined value for 1597 If not defined, then U-Boot uses predefined value for
1593 specified DTT device. 1598 specified DTT device.
1594 1599
1595 CONFIG_FSL_I2C 1600 CONFIG_FSL_I2C
1596 1601
1597 Define this option if you want to use Freescale's I2C driver in 1602 Define this option if you want to use Freescale's I2C driver in
1598 drivers/i2c/fsl_i2c.c. 1603 drivers/i2c/fsl_i2c.c.
1599 1604
1600 CONFIG_I2C_MUX 1605 CONFIG_I2C_MUX
1601 1606
1602 Define this option if you have I2C devices reached over 1 .. n 1607 Define this option if you have I2C devices reached over 1 .. n
1603 I2C Muxes like the pca9544a. This option addes a new I2C 1608 I2C Muxes like the pca9544a. This option addes a new I2C
1604 Command "i2c bus [muxtype:muxaddr:muxchannel]" which adds a 1609 Command "i2c bus [muxtype:muxaddr:muxchannel]" which adds a
1605 new I2C Bus to the existing I2C Busses. If you select the 1610 new I2C Bus to the existing I2C Busses. If you select the
1606 new Bus with "i2c dev", u-bbot sends first the commandos for 1611 new Bus with "i2c dev", u-bbot sends first the commandos for
1607 the muxes to activate this new "bus". 1612 the muxes to activate this new "bus".
1608 1613
1609 CONFIG_I2C_MULTI_BUS must be also defined, to use this 1614 CONFIG_I2C_MULTI_BUS must be also defined, to use this
1610 feature! 1615 feature!
1611 1616
1612 Example: 1617 Example:
1613 Adding a new I2C Bus reached over 2 pca9544a muxes 1618 Adding a new I2C Bus reached over 2 pca9544a muxes
1614 The First mux with address 70 and channel 6 1619 The First mux with address 70 and channel 6
1615 The Second mux with address 71 and channel 4 1620 The Second mux with address 71 and channel 4
1616 1621
1617 => i2c bus pca9544a:70:6:pca9544a:71:4 1622 => i2c bus pca9544a:70:6:pca9544a:71:4
1618 1623
1619 Use the "i2c bus" command without parameter, to get a list 1624 Use the "i2c bus" command without parameter, to get a list
1620 of I2C Busses with muxes: 1625 of I2C Busses with muxes:
1621 1626
1622 => i2c bus 1627 => i2c bus
1623 Busses reached over muxes: 1628 Busses reached over muxes:
1624 Bus ID: 2 1629 Bus ID: 2
1625 reached over Mux(es): 1630 reached over Mux(es):
1626 pca9544a@70 ch: 4 1631 pca9544a@70 ch: 4
1627 Bus ID: 3 1632 Bus ID: 3
1628 reached over Mux(es): 1633 reached over Mux(es):
1629 pca9544a@70 ch: 6 1634 pca9544a@70 ch: 6
1630 pca9544a@71 ch: 4 1635 pca9544a@71 ch: 4
1631 => 1636 =>
1632 1637
1633 If you now switch to the new I2C Bus 3 with "i2c dev 3" 1638 If you now switch to the new I2C Bus 3 with "i2c dev 3"
1634 u-boot sends First the Commando to the mux@70 to enable 1639 u-boot sends First the Commando to the mux@70 to enable
1635 channel 6, and then the Commando to the mux@71 to enable 1640 channel 6, and then the Commando to the mux@71 to enable
1636 the channel 4. 1641 the channel 4.
1637 1642
1638 After that, you can use the "normal" i2c commands as 1643 After that, you can use the "normal" i2c commands as
1639 usual, to communicate with your I2C devices behind 1644 usual, to communicate with your I2C devices behind
1640 the 2 muxes. 1645 the 2 muxes.
1641 1646
1642 This option is actually implemented for the bitbanging 1647 This option is actually implemented for the bitbanging
1643 algorithm in common/soft_i2c.c and for the Hardware I2C 1648 algorithm in common/soft_i2c.c and for the Hardware I2C
1644 Bus on the MPC8260. But it should be not so difficult 1649 Bus on the MPC8260. But it should be not so difficult
1645 to add this option to other architectures. 1650 to add this option to other architectures.
1646 1651
1647 CONFIG_SOFT_I2C_READ_REPEATED_START 1652 CONFIG_SOFT_I2C_READ_REPEATED_START
1648 1653
1649 defining this will force the i2c_read() function in 1654 defining this will force the i2c_read() function in
1650 the soft_i2c driver to perform an I2C repeated start 1655 the soft_i2c driver to perform an I2C repeated start
1651 between writing the address pointer and reading the 1656 between writing the address pointer and reading the
1652 data. If this define is omitted the default behaviour 1657 data. If this define is omitted the default behaviour
1653 of doing a stop-start sequence will be used. Most I2C 1658 of doing a stop-start sequence will be used. Most I2C
1654 devices can use either method, but some require one or 1659 devices can use either method, but some require one or
1655 the other. 1660 the other.
1656 1661
1657 - SPI Support: CONFIG_SPI 1662 - SPI Support: CONFIG_SPI
1658 1663
1659 Enables SPI driver (so far only tested with 1664 Enables SPI driver (so far only tested with
1660 SPI EEPROM, also an instance works with Crystal A/D and 1665 SPI EEPROM, also an instance works with Crystal A/D and
1661 D/As on the SACSng board) 1666 D/As on the SACSng board)
1662 1667
1663 CONFIG_SH_SPI 1668 CONFIG_SH_SPI
1664 1669
1665 Enables the driver for SPI controller on SuperH. Currently 1670 Enables the driver for SPI controller on SuperH. Currently
1666 only SH7757 is supported. 1671 only SH7757 is supported.
1667 1672
1668 CONFIG_SPI_X 1673 CONFIG_SPI_X
1669 1674
1670 Enables extended (16-bit) SPI EEPROM addressing. 1675 Enables extended (16-bit) SPI EEPROM addressing.
1671 (symmetrical to CONFIG_I2C_X) 1676 (symmetrical to CONFIG_I2C_X)
1672 1677
1673 CONFIG_SOFT_SPI 1678 CONFIG_SOFT_SPI
1674 1679
1675 Enables a software (bit-bang) SPI driver rather than 1680 Enables a software (bit-bang) SPI driver rather than
1676 using hardware support. This is a general purpose 1681 using hardware support. This is a general purpose
1677 driver that only requires three general I/O port pins 1682 driver that only requires three general I/O port pins
1678 (two outputs, one input) to function. If this is 1683 (two outputs, one input) to function. If this is
1679 defined, the board configuration must define several 1684 defined, the board configuration must define several
1680 SPI configuration items (port pins to use, etc). For 1685 SPI configuration items (port pins to use, etc). For
1681 an example, see include/configs/sacsng.h. 1686 an example, see include/configs/sacsng.h.
1682 1687
1683 CONFIG_HARD_SPI 1688 CONFIG_HARD_SPI
1684 1689
1685 Enables a hardware SPI driver for general-purpose reads 1690 Enables a hardware SPI driver for general-purpose reads
1686 and writes. As with CONFIG_SOFT_SPI, the board configuration 1691 and writes. As with CONFIG_SOFT_SPI, the board configuration
1687 must define a list of chip-select function pointers. 1692 must define a list of chip-select function pointers.
1688 Currently supported on some MPC8xxx processors. For an 1693 Currently supported on some MPC8xxx processors. For an
1689 example, see include/configs/mpc8349emds.h. 1694 example, see include/configs/mpc8349emds.h.
1690 1695
1691 CONFIG_MXC_SPI 1696 CONFIG_MXC_SPI
1692 1697
1693 Enables the driver for the SPI controllers on i.MX and MXC 1698 Enables the driver for the SPI controllers on i.MX and MXC
1694 SoCs. Currently only i.MX31 is supported. 1699 SoCs. Currently only i.MX31 is supported.
1695 1700
1696 - FPGA Support: CONFIG_FPGA 1701 - FPGA Support: CONFIG_FPGA
1697 1702
1698 Enables FPGA subsystem. 1703 Enables FPGA subsystem.
1699 1704
1700 CONFIG_FPGA_<vendor> 1705 CONFIG_FPGA_<vendor>
1701 1706
1702 Enables support for specific chip vendors. 1707 Enables support for specific chip vendors.
1703 (ALTERA, XILINX) 1708 (ALTERA, XILINX)
1704 1709
1705 CONFIG_FPGA_<family> 1710 CONFIG_FPGA_<family>
1706 1711
1707 Enables support for FPGA family. 1712 Enables support for FPGA family.
1708 (SPARTAN2, SPARTAN3, VIRTEX2, CYCLONE2, ACEX1K, ACEX) 1713 (SPARTAN2, SPARTAN3, VIRTEX2, CYCLONE2, ACEX1K, ACEX)
1709 1714
1710 CONFIG_FPGA_COUNT 1715 CONFIG_FPGA_COUNT
1711 1716
1712 Specify the number of FPGA devices to support. 1717 Specify the number of FPGA devices to support.
1713 1718
1714 CONFIG_SYS_FPGA_PROG_FEEDBACK 1719 CONFIG_SYS_FPGA_PROG_FEEDBACK
1715 1720
1716 Enable printing of hash marks during FPGA configuration. 1721 Enable printing of hash marks during FPGA configuration.
1717 1722
1718 CONFIG_SYS_FPGA_CHECK_BUSY 1723 CONFIG_SYS_FPGA_CHECK_BUSY
1719 1724
1720 Enable checks on FPGA configuration interface busy 1725 Enable checks on FPGA configuration interface busy
1721 status by the configuration function. This option 1726 status by the configuration function. This option
1722 will require a board or device specific function to 1727 will require a board or device specific function to
1723 be written. 1728 be written.
1724 1729
1725 CONFIG_FPGA_DELAY 1730 CONFIG_FPGA_DELAY
1726 1731
1727 If defined, a function that provides delays in the FPGA 1732 If defined, a function that provides delays in the FPGA
1728 configuration driver. 1733 configuration driver.
1729 1734
1730 CONFIG_SYS_FPGA_CHECK_CTRLC 1735 CONFIG_SYS_FPGA_CHECK_CTRLC
1731 Allow Control-C to interrupt FPGA configuration 1736 Allow Control-C to interrupt FPGA configuration
1732 1737
1733 CONFIG_SYS_FPGA_CHECK_ERROR 1738 CONFIG_SYS_FPGA_CHECK_ERROR
1734 1739
1735 Check for configuration errors during FPGA bitfile 1740 Check for configuration errors during FPGA bitfile
1736 loading. For example, abort during Virtex II 1741 loading. For example, abort during Virtex II
1737 configuration if the INIT_B line goes low (which 1742 configuration if the INIT_B line goes low (which
1738 indicated a CRC error). 1743 indicated a CRC error).
1739 1744
1740 CONFIG_SYS_FPGA_WAIT_INIT 1745 CONFIG_SYS_FPGA_WAIT_INIT
1741 1746
1742 Maximum time to wait for the INIT_B line to deassert 1747 Maximum time to wait for the INIT_B line to deassert
1743 after PROB_B has been deasserted during a Virtex II 1748 after PROB_B has been deasserted during a Virtex II
1744 FPGA configuration sequence. The default time is 500 1749 FPGA configuration sequence. The default time is 500
1745 ms. 1750 ms.
1746 1751
1747 CONFIG_SYS_FPGA_WAIT_BUSY 1752 CONFIG_SYS_FPGA_WAIT_BUSY
1748 1753
1749 Maximum time to wait for BUSY to deassert during 1754 Maximum time to wait for BUSY to deassert during
1750 Virtex II FPGA configuration. The default is 5 ms. 1755 Virtex II FPGA configuration. The default is 5 ms.
1751 1756
1752 CONFIG_SYS_FPGA_WAIT_CONFIG 1757 CONFIG_SYS_FPGA_WAIT_CONFIG
1753 1758
1754 Time to wait after FPGA configuration. The default is 1759 Time to wait after FPGA configuration. The default is
1755 200 ms. 1760 200 ms.
1756 1761
1757 - Configuration Management: 1762 - Configuration Management:
1758 CONFIG_IDENT_STRING 1763 CONFIG_IDENT_STRING
1759 1764
1760 If defined, this string will be added to the U-Boot 1765 If defined, this string will be added to the U-Boot
1761 version information (U_BOOT_VERSION) 1766 version information (U_BOOT_VERSION)
1762 1767
1763 - Vendor Parameter Protection: 1768 - Vendor Parameter Protection:
1764 1769
1765 U-Boot considers the values of the environment 1770 U-Boot considers the values of the environment
1766 variables "serial#" (Board Serial Number) and 1771 variables "serial#" (Board Serial Number) and
1767 "ethaddr" (Ethernet Address) to be parameters that 1772 "ethaddr" (Ethernet Address) to be parameters that
1768 are set once by the board vendor / manufacturer, and 1773 are set once by the board vendor / manufacturer, and
1769 protects these variables from casual modification by 1774 protects these variables from casual modification by
1770 the user. Once set, these variables are read-only, 1775 the user. Once set, these variables are read-only,
1771 and write or delete attempts are rejected. You can 1776 and write or delete attempts are rejected. You can
1772 change this behaviour: 1777 change this behaviour:
1773 1778
1774 If CONFIG_ENV_OVERWRITE is #defined in your config 1779 If CONFIG_ENV_OVERWRITE is #defined in your config
1775 file, the write protection for vendor parameters is 1780 file, the write protection for vendor parameters is
1776 completely disabled. Anybody can change or delete 1781 completely disabled. Anybody can change or delete
1777 these parameters. 1782 these parameters.
1778 1783
1779 Alternatively, if you #define _both_ CONFIG_ETHADDR 1784 Alternatively, if you #define _both_ CONFIG_ETHADDR
1780 _and_ CONFIG_OVERWRITE_ETHADDR_ONCE, a default 1785 _and_ CONFIG_OVERWRITE_ETHADDR_ONCE, a default
1781 Ethernet address is installed in the environment, 1786 Ethernet address is installed in the environment,
1782 which can be changed exactly ONCE by the user. [The 1787 which can be changed exactly ONCE by the user. [The
1783 serial# is unaffected by this, i. e. it remains 1788 serial# is unaffected by this, i. e. it remains
1784 read-only.] 1789 read-only.]
1785 1790
1786 - Protected RAM: 1791 - Protected RAM:
1787 CONFIG_PRAM 1792 CONFIG_PRAM
1788 1793
1789 Define this variable to enable the reservation of 1794 Define this variable to enable the reservation of
1790 "protected RAM", i. e. RAM which is not overwritten 1795 "protected RAM", i. e. RAM which is not overwritten
1791 by U-Boot. Define CONFIG_PRAM to hold the number of 1796 by U-Boot. Define CONFIG_PRAM to hold the number of
1792 kB you want to reserve for pRAM. You can overwrite 1797 kB you want to reserve for pRAM. You can overwrite
1793 this default value by defining an environment 1798 this default value by defining an environment
1794 variable "pram" to the number of kB you want to 1799 variable "pram" to the number of kB you want to
1795 reserve. Note that the board info structure will 1800 reserve. Note that the board info structure will
1796 still show the full amount of RAM. If pRAM is 1801 still show the full amount of RAM. If pRAM is
1797 reserved, a new environment variable "mem" will 1802 reserved, a new environment variable "mem" will
1798 automatically be defined to hold the amount of 1803 automatically be defined to hold the amount of
1799 remaining RAM in a form that can be passed as boot 1804 remaining RAM in a form that can be passed as boot
1800 argument to Linux, for instance like that: 1805 argument to Linux, for instance like that:
1801 1806
1802 setenv bootargs ... mem=\${mem} 1807 setenv bootargs ... mem=\${mem}
1803 saveenv 1808 saveenv
1804 1809
1805 This way you can tell Linux not to use this memory, 1810 This way you can tell Linux not to use this memory,
1806 either, which results in a memory region that will 1811 either, which results in a memory region that will
1807 not be affected by reboots. 1812 not be affected by reboots.
1808 1813
1809 *WARNING* If your board configuration uses automatic 1814 *WARNING* If your board configuration uses automatic
1810 detection of the RAM size, you must make sure that 1815 detection of the RAM size, you must make sure that
1811 this memory test is non-destructive. So far, the 1816 this memory test is non-destructive. So far, the
1812 following board configurations are known to be 1817 following board configurations are known to be
1813 "pRAM-clean": 1818 "pRAM-clean":
1814 1819
1815 ETX094, IVMS8, IVML24, SPD8xx, TQM8xxL, 1820 ETX094, IVMS8, IVML24, SPD8xx, TQM8xxL,
1816 HERMES, IP860, RPXlite, LWMON, LANTEC, 1821 HERMES, IP860, RPXlite, LWMON, LANTEC,
1817 FLAGADM, TQM8260 1822 FLAGADM, TQM8260
1818 1823
1819 - Error Recovery: 1824 - Error Recovery:
1820 CONFIG_PANIC_HANG 1825 CONFIG_PANIC_HANG
1821 1826
1822 Define this variable to stop the system in case of a 1827 Define this variable to stop the system in case of a
1823 fatal error, so that you have to reset it manually. 1828 fatal error, so that you have to reset it manually.
1824 This is probably NOT a good idea for an embedded 1829 This is probably NOT a good idea for an embedded
1825 system where you want the system to reboot 1830 system where you want the system to reboot
1826 automatically as fast as possible, but it may be 1831 automatically as fast as possible, but it may be
1827 useful during development since you can try to debug 1832 useful during development since you can try to debug
1828 the conditions that lead to the situation. 1833 the conditions that lead to the situation.
1829 1834
1830 CONFIG_NET_RETRY_COUNT 1835 CONFIG_NET_RETRY_COUNT
1831 1836
1832 This variable defines the number of retries for 1837 This variable defines the number of retries for
1833 network operations like ARP, RARP, TFTP, or BOOTP 1838 network operations like ARP, RARP, TFTP, or BOOTP
1834 before giving up the operation. If not defined, a 1839 before giving up the operation. If not defined, a
1835 default value of 5 is used. 1840 default value of 5 is used.
1836 1841
1837 CONFIG_ARP_TIMEOUT 1842 CONFIG_ARP_TIMEOUT
1838 1843
1839 Timeout waiting for an ARP reply in milliseconds. 1844 Timeout waiting for an ARP reply in milliseconds.
1840 1845
1841 - Command Interpreter: 1846 - Command Interpreter:
1842 CONFIG_AUTO_COMPLETE 1847 CONFIG_AUTO_COMPLETE
1843 1848
1844 Enable auto completion of commands using TAB. 1849 Enable auto completion of commands using TAB.
1845 1850
1846 Note that this feature has NOT been implemented yet 1851 Note that this feature has NOT been implemented yet
1847 for the "hush" shell. 1852 for the "hush" shell.
1848 1853
1849 1854
1850 CONFIG_SYS_HUSH_PARSER 1855 CONFIG_SYS_HUSH_PARSER
1851 1856
1852 Define this variable to enable the "hush" shell (from 1857 Define this variable to enable the "hush" shell (from
1853 Busybox) as command line interpreter, thus enabling 1858 Busybox) as command line interpreter, thus enabling
1854 powerful command line syntax like 1859 powerful command line syntax like
1855 if...then...else...fi conditionals or `&&' and '||' 1860 if...then...else...fi conditionals or `&&' and '||'
1856 constructs ("shell scripts"). 1861 constructs ("shell scripts").
1857 1862
1858 If undefined, you get the old, much simpler behaviour 1863 If undefined, you get the old, much simpler behaviour
1859 with a somewhat smaller memory footprint. 1864 with a somewhat smaller memory footprint.
1860 1865
1861 1866
1862 CONFIG_SYS_PROMPT_HUSH_PS2 1867 CONFIG_SYS_PROMPT_HUSH_PS2
1863 1868
1864 This defines the secondary prompt string, which is 1869 This defines the secondary prompt string, which is
1865 printed when the command interpreter needs more input 1870 printed when the command interpreter needs more input
1866 to complete a command. Usually "> ". 1871 to complete a command. Usually "> ".
1867 1872
1868 Note: 1873 Note:
1869 1874
1870 In the current implementation, the local variables 1875 In the current implementation, the local variables
1871 space and global environment variables space are 1876 space and global environment variables space are
1872 separated. Local variables are those you define by 1877 separated. Local variables are those you define by
1873 simply typing `name=value'. To access a local 1878 simply typing `name=value'. To access a local
1874 variable later on, you have write `$name' or 1879 variable later on, you have write `$name' or
1875 `${name}'; to execute the contents of a variable 1880 `${name}'; to execute the contents of a variable
1876 directly type `$name' at the command prompt. 1881 directly type `$name' at the command prompt.
1877 1882
1878 Global environment variables are those you use 1883 Global environment variables are those you use
1879 setenv/printenv to work with. To run a command stored 1884 setenv/printenv to work with. To run a command stored
1880 in such a variable, you need to use the run command, 1885 in such a variable, you need to use the run command,
1881 and you must not use the '$' sign to access them. 1886 and you must not use the '$' sign to access them.
1882 1887
1883 To store commands and special characters in a 1888 To store commands and special characters in a
1884 variable, please use double quotation marks 1889 variable, please use double quotation marks
1885 surrounding the whole text of the variable, instead 1890 surrounding the whole text of the variable, instead
1886 of the backslashes before semicolons and special 1891 of the backslashes before semicolons and special
1887 symbols. 1892 symbols.
1888 1893
1889 - Commandline Editing and History: 1894 - Commandline Editing and History:
1890 CONFIG_CMDLINE_EDITING 1895 CONFIG_CMDLINE_EDITING
1891 1896
1892 Enable editing and History functions for interactive 1897 Enable editing and History functions for interactive
1893 commandline input operations 1898 commandline input operations
1894 1899
1895 - Default Environment: 1900 - Default Environment:
1896 CONFIG_EXTRA_ENV_SETTINGS 1901 CONFIG_EXTRA_ENV_SETTINGS
1897 1902
1898 Define this to contain any number of null terminated 1903 Define this to contain any number of null terminated
1899 strings (variable = value pairs) that will be part of 1904 strings (variable = value pairs) that will be part of
1900 the default environment compiled into the boot image. 1905 the default environment compiled into the boot image.
1901 1906
1902 For example, place something like this in your 1907 For example, place something like this in your
1903 board's config file: 1908 board's config file:
1904 1909
1905 #define CONFIG_EXTRA_ENV_SETTINGS \ 1910 #define CONFIG_EXTRA_ENV_SETTINGS \
1906 "myvar1=value1\0" \ 1911 "myvar1=value1\0" \
1907 "myvar2=value2\0" 1912 "myvar2=value2\0"
1908 1913
1909 Warning: This method is based on knowledge about the 1914 Warning: This method is based on knowledge about the
1910 internal format how the environment is stored by the 1915 internal format how the environment is stored by the
1911 U-Boot code. This is NOT an official, exported 1916 U-Boot code. This is NOT an official, exported
1912 interface! Although it is unlikely that this format 1917 interface! Although it is unlikely that this format
1913 will change soon, there is no guarantee either. 1918 will change soon, there is no guarantee either.
1914 You better know what you are doing here. 1919 You better know what you are doing here.
1915 1920
1916 Note: overly (ab)use of the default environment is 1921 Note: overly (ab)use of the default environment is
1917 discouraged. Make sure to check other ways to preset 1922 discouraged. Make sure to check other ways to preset
1918 the environment like the "source" command or the 1923 the environment like the "source" command or the
1919 boot command first. 1924 boot command first.
1920 1925
1921 - DataFlash Support: 1926 - DataFlash Support:
1922 CONFIG_HAS_DATAFLASH 1927 CONFIG_HAS_DATAFLASH
1923 1928
1924 Defining this option enables DataFlash features and 1929 Defining this option enables DataFlash features and
1925 allows to read/write in Dataflash via the standard 1930 allows to read/write in Dataflash via the standard
1926 commands cp, md... 1931 commands cp, md...
1927 1932
1928 - SystemACE Support: 1933 - SystemACE Support:
1929 CONFIG_SYSTEMACE 1934 CONFIG_SYSTEMACE
1930 1935
1931 Adding this option adds support for Xilinx SystemACE 1936 Adding this option adds support for Xilinx SystemACE
1932 chips attached via some sort of local bus. The address 1937 chips attached via some sort of local bus. The address
1933 of the chip must also be defined in the 1938 of the chip must also be defined in the
1934 CONFIG_SYS_SYSTEMACE_BASE macro. For example: 1939 CONFIG_SYS_SYSTEMACE_BASE macro. For example:
1935 1940
1936 #define CONFIG_SYSTEMACE 1941 #define CONFIG_SYSTEMACE
1937 #define CONFIG_SYS_SYSTEMACE_BASE 0xf0000000 1942 #define CONFIG_SYS_SYSTEMACE_BASE 0xf0000000
1938 1943
1939 When SystemACE support is added, the "ace" device type 1944 When SystemACE support is added, the "ace" device type
1940 becomes available to the fat commands, i.e. fatls. 1945 becomes available to the fat commands, i.e. fatls.
1941 1946
1942 - TFTP Fixed UDP Port: 1947 - TFTP Fixed UDP Port:
1943 CONFIG_TFTP_PORT 1948 CONFIG_TFTP_PORT
1944 1949
1945 If this is defined, the environment variable tftpsrcp 1950 If this is defined, the environment variable tftpsrcp
1946 is used to supply the TFTP UDP source port value. 1951 is used to supply the TFTP UDP source port value.
1947 If tftpsrcp isn't defined, the normal pseudo-random port 1952 If tftpsrcp isn't defined, the normal pseudo-random port
1948 number generator is used. 1953 number generator is used.
1949 1954
1950 Also, the environment variable tftpdstp is used to supply 1955 Also, the environment variable tftpdstp is used to supply
1951 the TFTP UDP destination port value. If tftpdstp isn't 1956 the TFTP UDP destination port value. If tftpdstp isn't
1952 defined, the normal port 69 is used. 1957 defined, the normal port 69 is used.
1953 1958
1954 The purpose for tftpsrcp is to allow a TFTP server to 1959 The purpose for tftpsrcp is to allow a TFTP server to
1955 blindly start the TFTP transfer using the pre-configured 1960 blindly start the TFTP transfer using the pre-configured
1956 target IP address and UDP port. This has the effect of 1961 target IP address and UDP port. This has the effect of
1957 "punching through" the (Windows XP) firewall, allowing 1962 "punching through" the (Windows XP) firewall, allowing
1958 the remainder of the TFTP transfer to proceed normally. 1963 the remainder of the TFTP transfer to proceed normally.
1959 A better solution is to properly configure the firewall, 1964 A better solution is to properly configure the firewall,
1960 but sometimes that is not allowed. 1965 but sometimes that is not allowed.
1961 1966
1962 - Show boot progress: 1967 - Show boot progress:
1963 CONFIG_SHOW_BOOT_PROGRESS 1968 CONFIG_SHOW_BOOT_PROGRESS
1964 1969
1965 Defining this option allows to add some board- 1970 Defining this option allows to add some board-
1966 specific code (calling a user-provided function 1971 specific code (calling a user-provided function
1967 "show_boot_progress(int)") that enables you to show 1972 "show_boot_progress(int)") that enables you to show
1968 the system's boot progress on some display (for 1973 the system's boot progress on some display (for
1969 example, some LED's) on your board. At the moment, 1974 example, some LED's) on your board. At the moment,
1970 the following checkpoints are implemented: 1975 the following checkpoints are implemented:
1971 1976
1972 Legacy uImage format: 1977 Legacy uImage format:
1973 1978
1974 Arg Where When 1979 Arg Where When
1975 1 common/cmd_bootm.c before attempting to boot an image 1980 1 common/cmd_bootm.c before attempting to boot an image
1976 -1 common/cmd_bootm.c Image header has bad magic number 1981 -1 common/cmd_bootm.c Image header has bad magic number
1977 2 common/cmd_bootm.c Image header has correct magic number 1982 2 common/cmd_bootm.c Image header has correct magic number
1978 -2 common/cmd_bootm.c Image header has bad checksum 1983 -2 common/cmd_bootm.c Image header has bad checksum
1979 3 common/cmd_bootm.c Image header has correct checksum 1984 3 common/cmd_bootm.c Image header has correct checksum
1980 -3 common/cmd_bootm.c Image data has bad checksum 1985 -3 common/cmd_bootm.c Image data has bad checksum
1981 4 common/cmd_bootm.c Image data has correct checksum 1986 4 common/cmd_bootm.c Image data has correct checksum
1982 -4 common/cmd_bootm.c Image is for unsupported architecture 1987 -4 common/cmd_bootm.c Image is for unsupported architecture
1983 5 common/cmd_bootm.c Architecture check OK 1988 5 common/cmd_bootm.c Architecture check OK
1984 -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi) 1989 -5 common/cmd_bootm.c Wrong Image Type (not kernel, multi)
1985 6 common/cmd_bootm.c Image Type check OK 1990 6 common/cmd_bootm.c Image Type check OK
1986 -6 common/cmd_bootm.c gunzip uncompression error 1991 -6 common/cmd_bootm.c gunzip uncompression error
1987 -7 common/cmd_bootm.c Unimplemented compression type 1992 -7 common/cmd_bootm.c Unimplemented compression type
1988 7 common/cmd_bootm.c Uncompression OK 1993 7 common/cmd_bootm.c Uncompression OK
1989 8 common/cmd_bootm.c No uncompress/copy overwrite error 1994 8 common/cmd_bootm.c No uncompress/copy overwrite error
1990 -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX) 1995 -9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)
1991 1996
1992 9 common/image.c Start initial ramdisk verification 1997 9 common/image.c Start initial ramdisk verification
1993 -10 common/image.c Ramdisk header has bad magic number 1998 -10 common/image.c Ramdisk header has bad magic number
1994 -11 common/image.c Ramdisk header has bad checksum 1999 -11 common/image.c Ramdisk header has bad checksum
1995 10 common/image.c Ramdisk header is OK 2000 10 common/image.c Ramdisk header is OK
1996 -12 common/image.c Ramdisk data has bad checksum 2001 -12 common/image.c Ramdisk data has bad checksum
1997 11 common/image.c Ramdisk data has correct checksum 2002 11 common/image.c Ramdisk data has correct checksum
1998 12 common/image.c Ramdisk verification complete, start loading 2003 12 common/image.c Ramdisk verification complete, start loading
1999 -13 common/image.c Wrong Image Type (not PPC Linux ramdisk) 2004 -13 common/image.c Wrong Image Type (not PPC Linux ramdisk)
2000 13 common/image.c Start multifile image verification 2005 13 common/image.c Start multifile image verification
2001 14 common/image.c No initial ramdisk, no multifile, continue. 2006 14 common/image.c No initial ramdisk, no multifile, continue.
2002 2007
2003 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS 2008 15 arch/<arch>/lib/bootm.c All preparation done, transferring control to OS
2004 2009
2005 -30 arch/powerpc/lib/board.c Fatal error, hang the system 2010 -30 arch/powerpc/lib/board.c Fatal error, hang the system
2006 -31 post/post.c POST test failed, detected by post_output_backlog() 2011 -31 post/post.c POST test failed, detected by post_output_backlog()
2007 -32 post/post.c POST test failed, detected by post_run_single() 2012 -32 post/post.c POST test failed, detected by post_run_single()
2008 2013
2009 34 common/cmd_doc.c before loading a Image from a DOC device 2014 34 common/cmd_doc.c before loading a Image from a DOC device
2010 -35 common/cmd_doc.c Bad usage of "doc" command 2015 -35 common/cmd_doc.c Bad usage of "doc" command
2011 35 common/cmd_doc.c correct usage of "doc" command 2016 35 common/cmd_doc.c correct usage of "doc" command
2012 -36 common/cmd_doc.c No boot device 2017 -36 common/cmd_doc.c No boot device
2013 36 common/cmd_doc.c correct boot device 2018 36 common/cmd_doc.c correct boot device
2014 -37 common/cmd_doc.c Unknown Chip ID on boot device 2019 -37 common/cmd_doc.c Unknown Chip ID on boot device
2015 37 common/cmd_doc.c correct chip ID found, device available 2020 37 common/cmd_doc.c correct chip ID found, device available
2016 -38 common/cmd_doc.c Read Error on boot device 2021 -38 common/cmd_doc.c Read Error on boot device
2017 38 common/cmd_doc.c reading Image header from DOC device OK 2022 38 common/cmd_doc.c reading Image header from DOC device OK
2018 -39 common/cmd_doc.c Image header has bad magic number 2023 -39 common/cmd_doc.c Image header has bad magic number
2019 39 common/cmd_doc.c Image header has correct magic number 2024 39 common/cmd_doc.c Image header has correct magic number
2020 -40 common/cmd_doc.c Error reading Image from DOC device 2025 -40 common/cmd_doc.c Error reading Image from DOC device
2021 40 common/cmd_doc.c Image header has correct magic number 2026 40 common/cmd_doc.c Image header has correct magic number
2022 41 common/cmd_ide.c before loading a Image from a IDE device 2027 41 common/cmd_ide.c before loading a Image from a IDE device
2023 -42 common/cmd_ide.c Bad usage of "ide" command 2028 -42 common/cmd_ide.c Bad usage of "ide" command
2024 42 common/cmd_ide.c correct usage of "ide" command 2029 42 common/cmd_ide.c correct usage of "ide" command
2025 -43 common/cmd_ide.c No boot device 2030 -43 common/cmd_ide.c No boot device
2026 43 common/cmd_ide.c boot device found 2031 43 common/cmd_ide.c boot device found
2027 -44 common/cmd_ide.c Device not available 2032 -44 common/cmd_ide.c Device not available
2028 44 common/cmd_ide.c Device available 2033 44 common/cmd_ide.c Device available
2029 -45 common/cmd_ide.c wrong partition selected 2034 -45 common/cmd_ide.c wrong partition selected
2030 45 common/cmd_ide.c partition selected 2035 45 common/cmd_ide.c partition selected
2031 -46 common/cmd_ide.c Unknown partition table 2036 -46 common/cmd_ide.c Unknown partition table
2032 46 common/cmd_ide.c valid partition table found 2037 46 common/cmd_ide.c valid partition table found
2033 -47 common/cmd_ide.c Invalid partition type 2038 -47 common/cmd_ide.c Invalid partition type
2034 47 common/cmd_ide.c correct partition type 2039 47 common/cmd_ide.c correct partition type
2035 -48 common/cmd_ide.c Error reading Image Header on boot device 2040 -48 common/cmd_ide.c Error reading Image Header on boot device
2036 48 common/cmd_ide.c reading Image Header from IDE device OK 2041 48 common/cmd_ide.c reading Image Header from IDE device OK
2037 -49 common/cmd_ide.c Image header has bad magic number 2042 -49 common/cmd_ide.c Image header has bad magic number
2038 49 common/cmd_ide.c Image header has correct magic number 2043 49 common/cmd_ide.c Image header has correct magic number
2039 -50 common/cmd_ide.c Image header has bad checksum 2044 -50 common/cmd_ide.c Image header has bad checksum
2040 50 common/cmd_ide.c Image header has correct checksum 2045 50 common/cmd_ide.c Image header has correct checksum
2041 -51 common/cmd_ide.c Error reading Image from IDE device 2046 -51 common/cmd_ide.c Error reading Image from IDE device
2042 51 common/cmd_ide.c reading Image from IDE device OK 2047 51 common/cmd_ide.c reading Image from IDE device OK
2043 52 common/cmd_nand.c before loading a Image from a NAND device 2048 52 common/cmd_nand.c before loading a Image from a NAND device
2044 -53 common/cmd_nand.c Bad usage of "nand" command 2049 -53 common/cmd_nand.c Bad usage of "nand" command
2045 53 common/cmd_nand.c correct usage of "nand" command 2050 53 common/cmd_nand.c correct usage of "nand" command
2046 -54 common/cmd_nand.c No boot device 2051 -54 common/cmd_nand.c No boot device
2047 54 common/cmd_nand.c boot device found 2052 54 common/cmd_nand.c boot device found
2048 -55 common/cmd_nand.c Unknown Chip ID on boot device 2053 -55 common/cmd_nand.c Unknown Chip ID on boot device
2049 55 common/cmd_nand.c correct chip ID found, device available 2054 55 common/cmd_nand.c correct chip ID found, device available
2050 -56 common/cmd_nand.c Error reading Image Header on boot device 2055 -56 common/cmd_nand.c Error reading Image Header on boot device
2051 56 common/cmd_nand.c reading Image Header from NAND device OK 2056 56 common/cmd_nand.c reading Image Header from NAND device OK
2052 -57 common/cmd_nand.c Image header has bad magic number 2057 -57 common/cmd_nand.c Image header has bad magic number
2053 57 common/cmd_nand.c Image header has correct magic number 2058 57 common/cmd_nand.c Image header has correct magic number
2054 -58 common/cmd_nand.c Error reading Image from NAND device 2059 -58 common/cmd_nand.c Error reading Image from NAND device
2055 58 common/cmd_nand.c reading Image from NAND device OK 2060 58 common/cmd_nand.c reading Image from NAND device OK
2056 2061
2057 -60 common/env_common.c Environment has a bad CRC, using default 2062 -60 common/env_common.c Environment has a bad CRC, using default
2058 2063
2059 64 net/eth.c starting with Ethernet configuration. 2064 64 net/eth.c starting with Ethernet configuration.
2060 -64 net/eth.c no Ethernet found. 2065 -64 net/eth.c no Ethernet found.
2061 65 net/eth.c Ethernet found. 2066 65 net/eth.c Ethernet found.
2062 2067
2063 -80 common/cmd_net.c usage wrong 2068 -80 common/cmd_net.c usage wrong
2064 80 common/cmd_net.c before calling NetLoop() 2069 80 common/cmd_net.c before calling NetLoop()
2065 -81 common/cmd_net.c some error in NetLoop() occurred 2070 -81 common/cmd_net.c some error in NetLoop() occurred
2066 81 common/cmd_net.c NetLoop() back without error 2071 81 common/cmd_net.c NetLoop() back without error
2067 -82 common/cmd_net.c size == 0 (File with size 0 loaded) 2072 -82 common/cmd_net.c size == 0 (File with size 0 loaded)
2068 82 common/cmd_net.c trying automatic boot 2073 82 common/cmd_net.c trying automatic boot
2069 83 common/cmd_net.c running "source" command 2074 83 common/cmd_net.c running "source" command
2070 -83 common/cmd_net.c some error in automatic boot or "source" command 2075 -83 common/cmd_net.c some error in automatic boot or "source" command
2071 84 common/cmd_net.c end without errors 2076 84 common/cmd_net.c end without errors
2072 2077
2073 FIT uImage format: 2078 FIT uImage format:
2074 2079
2075 Arg Where When 2080 Arg Where When
2076 100 common/cmd_bootm.c Kernel FIT Image has correct format 2081 100 common/cmd_bootm.c Kernel FIT Image has correct format
2077 -100 common/cmd_bootm.c Kernel FIT Image has incorrect format 2082 -100 common/cmd_bootm.c Kernel FIT Image has incorrect format
2078 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration 2083 101 common/cmd_bootm.c No Kernel subimage unit name, using configuration
2079 -101 common/cmd_bootm.c Can't get configuration for kernel subimage 2084 -101 common/cmd_bootm.c Can't get configuration for kernel subimage
2080 102 common/cmd_bootm.c Kernel unit name specified 2085 102 common/cmd_bootm.c Kernel unit name specified
2081 -103 common/cmd_bootm.c Can't get kernel subimage node offset 2086 -103 common/cmd_bootm.c Can't get kernel subimage node offset
2082 103 common/cmd_bootm.c Found configuration node 2087 103 common/cmd_bootm.c Found configuration node
2083 104 common/cmd_bootm.c Got kernel subimage node offset 2088 104 common/cmd_bootm.c Got kernel subimage node offset
2084 -104 common/cmd_bootm.c Kernel subimage hash verification failed 2089 -104 common/cmd_bootm.c Kernel subimage hash verification failed
2085 105 common/cmd_bootm.c Kernel subimage hash verification OK 2090 105 common/cmd_bootm.c Kernel subimage hash verification OK
2086 -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture 2091 -105 common/cmd_bootm.c Kernel subimage is for unsupported architecture
2087 106 common/cmd_bootm.c Architecture check OK 2092 106 common/cmd_bootm.c Architecture check OK
2088 -106 common/cmd_bootm.c Kernel subimage has wrong type 2093 -106 common/cmd_bootm.c Kernel subimage has wrong type
2089 107 common/cmd_bootm.c Kernel subimage type OK 2094 107 common/cmd_bootm.c Kernel subimage type OK
2090 -107 common/cmd_bootm.c Can't get kernel subimage data/size 2095 -107 common/cmd_bootm.c Can't get kernel subimage data/size
2091 108 common/cmd_bootm.c Got kernel subimage data/size 2096 108 common/cmd_bootm.c Got kernel subimage data/size
2092 -108 common/cmd_bootm.c Wrong image type (not legacy, FIT) 2097 -108 common/cmd_bootm.c Wrong image type (not legacy, FIT)
2093 -109 common/cmd_bootm.c Can't get kernel subimage type 2098 -109 common/cmd_bootm.c Can't get kernel subimage type
2094 -110 common/cmd_bootm.c Can't get kernel subimage comp 2099 -110 common/cmd_bootm.c Can't get kernel subimage comp
2095 -111 common/cmd_bootm.c Can't get kernel subimage os 2100 -111 common/cmd_bootm.c Can't get kernel subimage os
2096 -112 common/cmd_bootm.c Can't get kernel subimage load address 2101 -112 common/cmd_bootm.c Can't get kernel subimage load address
2097 -113 common/cmd_bootm.c Image uncompress/copy overwrite error 2102 -113 common/cmd_bootm.c Image uncompress/copy overwrite error
2098 2103
2099 120 common/image.c Start initial ramdisk verification 2104 120 common/image.c Start initial ramdisk verification
2100 -120 common/image.c Ramdisk FIT image has incorrect format 2105 -120 common/image.c Ramdisk FIT image has incorrect format
2101 121 common/image.c Ramdisk FIT image has correct format 2106 121 common/image.c Ramdisk FIT image has correct format
2102 122 common/image.c No ramdisk subimage unit name, using configuration 2107 122 common/image.c No ramdisk subimage unit name, using configuration
2103 -122 common/image.c Can't get configuration for ramdisk subimage 2108 -122 common/image.c Can't get configuration for ramdisk subimage
2104 123 common/image.c Ramdisk unit name specified 2109 123 common/image.c Ramdisk unit name specified
2105 -124 common/image.c Can't get ramdisk subimage node offset 2110 -124 common/image.c Can't get ramdisk subimage node offset
2106 125 common/image.c Got ramdisk subimage node offset 2111 125 common/image.c Got ramdisk subimage node offset
2107 -125 common/image.c Ramdisk subimage hash verification failed 2112 -125 common/image.c Ramdisk subimage hash verification failed
2108 126 common/image.c Ramdisk subimage hash verification OK 2113 126 common/image.c Ramdisk subimage hash verification OK
2109 -126 common/image.c Ramdisk subimage for unsupported architecture 2114 -126 common/image.c Ramdisk subimage for unsupported architecture
2110 127 common/image.c Architecture check OK 2115 127 common/image.c Architecture check OK
2111 -127 common/image.c Can't get ramdisk subimage data/size 2116 -127 common/image.c Can't get ramdisk subimage data/size
2112 128 common/image.c Got ramdisk subimage data/size 2117 128 common/image.c Got ramdisk subimage data/size
2113 129 common/image.c Can't get ramdisk load address 2118 129 common/image.c Can't get ramdisk load address
2114 -129 common/image.c Got ramdisk load address 2119 -129 common/image.c Got ramdisk load address
2115 2120
2116 -130 common/cmd_doc.c Incorrect FIT image format 2121 -130 common/cmd_doc.c Incorrect FIT image format
2117 131 common/cmd_doc.c FIT image format OK 2122 131 common/cmd_doc.c FIT image format OK
2118 2123
2119 -140 common/cmd_ide.c Incorrect FIT image format 2124 -140 common/cmd_ide.c Incorrect FIT image format
2120 141 common/cmd_ide.c FIT image format OK 2125 141 common/cmd_ide.c FIT image format OK
2121 2126
2122 -150 common/cmd_nand.c Incorrect FIT image format 2127 -150 common/cmd_nand.c Incorrect FIT image format
2123 151 common/cmd_nand.c FIT image format OK 2128 151 common/cmd_nand.c FIT image format OK
2124 2129
2125 - Automatic software updates via TFTP server 2130 - Automatic software updates via TFTP server
2126 CONFIG_UPDATE_TFTP 2131 CONFIG_UPDATE_TFTP
2127 CONFIG_UPDATE_TFTP_CNT_MAX 2132 CONFIG_UPDATE_TFTP_CNT_MAX
2128 CONFIG_UPDATE_TFTP_MSEC_MAX 2133 CONFIG_UPDATE_TFTP_MSEC_MAX
2129 2134
2130 These options enable and control the auto-update feature; 2135 These options enable and control the auto-update feature;
2131 for a more detailed description refer to doc/README.update. 2136 for a more detailed description refer to doc/README.update.
2132 2137
2133 - MTD Support (mtdparts command, UBI support) 2138 - MTD Support (mtdparts command, UBI support)
2134 CONFIG_MTD_DEVICE 2139 CONFIG_MTD_DEVICE
2135 2140
2136 Adds the MTD device infrastructure from the Linux kernel. 2141 Adds the MTD device infrastructure from the Linux kernel.
2137 Needed for mtdparts command support. 2142 Needed for mtdparts command support.
2138 2143
2139 CONFIG_MTD_PARTITIONS 2144 CONFIG_MTD_PARTITIONS
2140 2145
2141 Adds the MTD partitioning infrastructure from the Linux 2146 Adds the MTD partitioning infrastructure from the Linux
2142 kernel. Needed for UBI support. 2147 kernel. Needed for UBI support.
2143 2148
2144 2149
2145 Modem Support: 2150 Modem Support:
2146 -------------- 2151 --------------
2147 2152
2148 [so far only for SMDK2400 and TRAB boards] 2153 [so far only for SMDK2400 and TRAB boards]
2149 2154
2150 - Modem support enable: 2155 - Modem support enable:
2151 CONFIG_MODEM_SUPPORT 2156 CONFIG_MODEM_SUPPORT
2152 2157
2153 - RTS/CTS Flow control enable: 2158 - RTS/CTS Flow control enable:
2154 CONFIG_HWFLOW 2159 CONFIG_HWFLOW
2155 2160
2156 - Modem debug support: 2161 - Modem debug support:
2157 CONFIG_MODEM_SUPPORT_DEBUG 2162 CONFIG_MODEM_SUPPORT_DEBUG
2158 2163
2159 Enables debugging stuff (char screen[1024], dbg()) 2164 Enables debugging stuff (char screen[1024], dbg())
2160 for modem support. Useful only with BDI2000. 2165 for modem support. Useful only with BDI2000.
2161 2166
2162 - Interrupt support (PPC): 2167 - Interrupt support (PPC):
2163 2168
2164 There are common interrupt_init() and timer_interrupt() 2169 There are common interrupt_init() and timer_interrupt()
2165 for all PPC archs. interrupt_init() calls interrupt_init_cpu() 2170 for all PPC archs. interrupt_init() calls interrupt_init_cpu()
2166 for CPU specific initialization. interrupt_init_cpu() 2171 for CPU specific initialization. interrupt_init_cpu()
2167 should set decrementer_count to appropriate value. If 2172 should set decrementer_count to appropriate value. If
2168 CPU resets decrementer automatically after interrupt 2173 CPU resets decrementer automatically after interrupt
2169 (ppc4xx) it should set decrementer_count to zero. 2174 (ppc4xx) it should set decrementer_count to zero.
2170 timer_interrupt() calls timer_interrupt_cpu() for CPU 2175 timer_interrupt() calls timer_interrupt_cpu() for CPU
2171 specific handling. If board has watchdog / status_led 2176 specific handling. If board has watchdog / status_led
2172 / other_activity_monitor it works automatically from 2177 / other_activity_monitor it works automatically from
2173 general timer_interrupt(). 2178 general timer_interrupt().
2174 2179
2175 - General: 2180 - General:
2176 2181
2177 In the target system modem support is enabled when a 2182 In the target system modem support is enabled when a
2178 specific key (key combination) is pressed during 2183 specific key (key combination) is pressed during
2179 power-on. Otherwise U-Boot will boot normally 2184 power-on. Otherwise U-Boot will boot normally
2180 (autoboot). The key_pressed() function is called from 2185 (autoboot). The key_pressed() function is called from
2181 board_init(). Currently key_pressed() is a dummy 2186 board_init(). Currently key_pressed() is a dummy
2182 function, returning 1 and thus enabling modem 2187 function, returning 1 and thus enabling modem
2183 initialization. 2188 initialization.
2184 2189
2185 If there are no modem init strings in the 2190 If there are no modem init strings in the
2186 environment, U-Boot proceed to autoboot; the 2191 environment, U-Boot proceed to autoboot; the
2187 previous output (banner, info printfs) will be 2192 previous output (banner, info printfs) will be
2188 suppressed, though. 2193 suppressed, though.
2189 2194
2190 See also: doc/README.Modem 2195 See also: doc/README.Modem
2191 2196
2192 2197
2193 Configuration Settings: 2198 Configuration Settings:
2194 ----------------------- 2199 -----------------------
2195 2200
2196 - CONFIG_SYS_LONGHELP: Defined when you want long help messages included; 2201 - CONFIG_SYS_LONGHELP: Defined when you want long help messages included;
2197 undefine this when you're short of memory. 2202 undefine this when you're short of memory.
2198 2203
2199 - CONFIG_SYS_HELP_CMD_WIDTH: Defined when you want to override the default 2204 - CONFIG_SYS_HELP_CMD_WIDTH: Defined when you want to override the default
2200 width of the commands listed in the 'help' command output. 2205 width of the commands listed in the 'help' command output.
2201 2206
2202 - CONFIG_SYS_PROMPT: This is what U-Boot prints on the console to 2207 - CONFIG_SYS_PROMPT: This is what U-Boot prints on the console to
2203 prompt for user input. 2208 prompt for user input.
2204 2209
2205 - CONFIG_SYS_CBSIZE: Buffer size for input from the Console 2210 - CONFIG_SYS_CBSIZE: Buffer size for input from the Console
2206 2211
2207 - CONFIG_SYS_PBSIZE: Buffer size for Console output 2212 - CONFIG_SYS_PBSIZE: Buffer size for Console output
2208 2213
2209 - CONFIG_SYS_MAXARGS: max. Number of arguments accepted for monitor commands 2214 - CONFIG_SYS_MAXARGS: max. Number of arguments accepted for monitor commands
2210 2215
2211 - CONFIG_SYS_BARGSIZE: Buffer size for Boot Arguments which are passed to 2216 - CONFIG_SYS_BARGSIZE: Buffer size for Boot Arguments which are passed to
2212 the application (usually a Linux kernel) when it is 2217 the application (usually a Linux kernel) when it is
2213 booted 2218 booted
2214 2219
2215 - CONFIG_SYS_BAUDRATE_TABLE: 2220 - CONFIG_SYS_BAUDRATE_TABLE:
2216 List of legal baudrate settings for this board. 2221 List of legal baudrate settings for this board.
2217 2222
2218 - CONFIG_SYS_CONSOLE_INFO_QUIET 2223 - CONFIG_SYS_CONSOLE_INFO_QUIET
2219 Suppress display of console information at boot. 2224 Suppress display of console information at boot.
2220 2225
2221 - CONFIG_SYS_CONSOLE_IS_IN_ENV 2226 - CONFIG_SYS_CONSOLE_IS_IN_ENV
2222 If the board specific function 2227 If the board specific function
2223 extern int overwrite_console (void); 2228 extern int overwrite_console (void);
2224 returns 1, the stdin, stderr and stdout are switched to the 2229 returns 1, the stdin, stderr and stdout are switched to the
2225 serial port, else the settings in the environment are used. 2230 serial port, else the settings in the environment are used.
2226 2231
2227 - CONFIG_SYS_CONSOLE_OVERWRITE_ROUTINE 2232 - CONFIG_SYS_CONSOLE_OVERWRITE_ROUTINE
2228 Enable the call to overwrite_console(). 2233 Enable the call to overwrite_console().
2229 2234
2230 - CONFIG_SYS_CONSOLE_ENV_OVERWRITE 2235 - CONFIG_SYS_CONSOLE_ENV_OVERWRITE
2231 Enable overwrite of previous console environment settings. 2236 Enable overwrite of previous console environment settings.
2232 2237
2233 - CONFIG_SYS_MEMTEST_START, CONFIG_SYS_MEMTEST_END: 2238 - CONFIG_SYS_MEMTEST_START, CONFIG_SYS_MEMTEST_END:
2234 Begin and End addresses of the area used by the 2239 Begin and End addresses of the area used by the
2235 simple memory test. 2240 simple memory test.
2236 2241
2237 - CONFIG_SYS_ALT_MEMTEST: 2242 - CONFIG_SYS_ALT_MEMTEST:
2238 Enable an alternate, more extensive memory test. 2243 Enable an alternate, more extensive memory test.
2239 2244
2240 - CONFIG_SYS_MEMTEST_SCRATCH: 2245 - CONFIG_SYS_MEMTEST_SCRATCH:
2241 Scratch address used by the alternate memory test 2246 Scratch address used by the alternate memory test
2242 You only need to set this if address zero isn't writeable 2247 You only need to set this if address zero isn't writeable
2243 2248
2244 - CONFIG_SYS_MEM_TOP_HIDE (PPC only): 2249 - CONFIG_SYS_MEM_TOP_HIDE (PPC only):
2245 If CONFIG_SYS_MEM_TOP_HIDE is defined in the board config header, 2250 If CONFIG_SYS_MEM_TOP_HIDE is defined in the board config header,
2246 this specified memory area will get subtracted from the top 2251 this specified memory area will get subtracted from the top
2247 (end) of RAM and won't get "touched" at all by U-Boot. By 2252 (end) of RAM and won't get "touched" at all by U-Boot. By
2248 fixing up gd->ram_size the Linux kernel should gets passed 2253 fixing up gd->ram_size the Linux kernel should gets passed
2249 the now "corrected" memory size and won't touch it either. 2254 the now "corrected" memory size and won't touch it either.
2250 This should work for arch/ppc and arch/powerpc. Only Linux 2255 This should work for arch/ppc and arch/powerpc. Only Linux
2251 board ports in arch/powerpc with bootwrapper support that 2256 board ports in arch/powerpc with bootwrapper support that
2252 recalculate the memory size from the SDRAM controller setup 2257 recalculate the memory size from the SDRAM controller setup
2253 will have to get fixed in Linux additionally. 2258 will have to get fixed in Linux additionally.
2254 2259
2255 This option can be used as a workaround for the 440EPx/GRx 2260 This option can be used as a workaround for the 440EPx/GRx
2256 CHIP 11 errata where the last 256 bytes in SDRAM shouldn't 2261 CHIP 11 errata where the last 256 bytes in SDRAM shouldn't
2257 be touched. 2262 be touched.
2258 2263
2259 WARNING: Please make sure that this value is a multiple of 2264 WARNING: Please make sure that this value is a multiple of
2260 the Linux page size (normally 4k). If this is not the case, 2265 the Linux page size (normally 4k). If this is not the case,
2261 then the end address of the Linux memory will be located at a 2266 then the end address of the Linux memory will be located at a
2262 non page size aligned address and this could cause major 2267 non page size aligned address and this could cause major
2263 problems. 2268 problems.
2264 2269
2265 - CONFIG_SYS_TFTP_LOADADDR: 2270 - CONFIG_SYS_TFTP_LOADADDR:
2266 Default load address for network file downloads 2271 Default load address for network file downloads
2267 2272
2268 - CONFIG_SYS_LOADS_BAUD_CHANGE: 2273 - CONFIG_SYS_LOADS_BAUD_CHANGE:
2269 Enable temporary baudrate change while serial download 2274 Enable temporary baudrate change while serial download
2270 2275
2271 - CONFIG_SYS_SDRAM_BASE: 2276 - CONFIG_SYS_SDRAM_BASE:
2272 Physical start address of SDRAM. _Must_ be 0 here. 2277 Physical start address of SDRAM. _Must_ be 0 here.
2273 2278
2274 - CONFIG_SYS_MBIO_BASE: 2279 - CONFIG_SYS_MBIO_BASE:
2275 Physical start address of Motherboard I/O (if using a 2280 Physical start address of Motherboard I/O (if using a
2276 Cogent motherboard) 2281 Cogent motherboard)
2277 2282
2278 - CONFIG_SYS_FLASH_BASE: 2283 - CONFIG_SYS_FLASH_BASE:
2279 Physical start address of Flash memory. 2284 Physical start address of Flash memory.
2280 2285
2281 - CONFIG_SYS_MONITOR_BASE: 2286 - CONFIG_SYS_MONITOR_BASE:
2282 Physical start address of boot monitor code (set by 2287 Physical start address of boot monitor code (set by
2283 make config files to be same as the text base address 2288 make config files to be same as the text base address
2284 (CONFIG_SYS_TEXT_BASE) used when linking) - same as 2289 (CONFIG_SYS_TEXT_BASE) used when linking) - same as
2285 CONFIG_SYS_FLASH_BASE when booting from flash. 2290 CONFIG_SYS_FLASH_BASE when booting from flash.
2286 2291
2287 - CONFIG_SYS_MONITOR_LEN: 2292 - CONFIG_SYS_MONITOR_LEN:
2288 Size of memory reserved for monitor code, used to 2293 Size of memory reserved for monitor code, used to
2289 determine _at_compile_time_ (!) if the environment is 2294 determine _at_compile_time_ (!) if the environment is
2290 embedded within the U-Boot image, or in a separate 2295 embedded within the U-Boot image, or in a separate
2291 flash sector. 2296 flash sector.
2292 2297
2293 - CONFIG_SYS_MALLOC_LEN: 2298 - CONFIG_SYS_MALLOC_LEN:
2294 Size of DRAM reserved for malloc() use. 2299 Size of DRAM reserved for malloc() use.
2295 2300
2296 - CONFIG_SYS_BOOTM_LEN: 2301 - CONFIG_SYS_BOOTM_LEN:
2297 Normally compressed uImages are limited to an 2302 Normally compressed uImages are limited to an
2298 uncompressed size of 8 MBytes. If this is not enough, 2303 uncompressed size of 8 MBytes. If this is not enough,
2299 you can define CONFIG_SYS_BOOTM_LEN in your board config file 2304 you can define CONFIG_SYS_BOOTM_LEN in your board config file
2300 to adjust this setting to your needs. 2305 to adjust this setting to your needs.
2301 2306
2302 - CONFIG_SYS_BOOTMAPSZ: 2307 - CONFIG_SYS_BOOTMAPSZ:
2303 Maximum size of memory mapped by the startup code of 2308 Maximum size of memory mapped by the startup code of
2304 the Linux kernel; all data that must be processed by 2309 the Linux kernel; all data that must be processed by
2305 the Linux kernel (bd_info, boot arguments, FDT blob if 2310 the Linux kernel (bd_info, boot arguments, FDT blob if
2306 used) must be put below this limit, unless "bootm_low" 2311 used) must be put below this limit, unless "bootm_low"
2307 enviroment variable is defined and non-zero. In such case 2312 enviroment variable is defined and non-zero. In such case
2308 all data for the Linux kernel must be between "bootm_low" 2313 all data for the Linux kernel must be between "bootm_low"
2309 and "bootm_low" + CONFIG_SYS_BOOTMAPSZ. 2314 and "bootm_low" + CONFIG_SYS_BOOTMAPSZ.
2310 2315
2311 - CONFIG_SYS_BOOT_RAMDISK_HIGH: 2316 - CONFIG_SYS_BOOT_RAMDISK_HIGH:
2312 Enable initrd_high functionality. If defined then the 2317 Enable initrd_high functionality. If defined then the
2313 initrd_high feature is enabled and the bootm ramdisk subcommand 2318 initrd_high feature is enabled and the bootm ramdisk subcommand
2314 is enabled. 2319 is enabled.
2315 2320
2316 - CONFIG_SYS_BOOT_GET_CMDLINE: 2321 - CONFIG_SYS_BOOT_GET_CMDLINE:
2317 Enables allocating and saving kernel cmdline in space between 2322 Enables allocating and saving kernel cmdline in space between
2318 "bootm_low" and "bootm_low" + BOOTMAPSZ. 2323 "bootm_low" and "bootm_low" + BOOTMAPSZ.
2319 2324
2320 - CONFIG_SYS_BOOT_GET_KBD: 2325 - CONFIG_SYS_BOOT_GET_KBD:
2321 Enables allocating and saving a kernel copy of the bd_info in 2326 Enables allocating and saving a kernel copy of the bd_info in
2322 space between "bootm_low" and "bootm_low" + BOOTMAPSZ. 2327 space between "bootm_low" and "bootm_low" + BOOTMAPSZ.
2323 2328
2324 - CONFIG_SYS_MAX_FLASH_BANKS: 2329 - CONFIG_SYS_MAX_FLASH_BANKS:
2325 Max number of Flash memory banks 2330 Max number of Flash memory banks
2326 2331
2327 - CONFIG_SYS_MAX_FLASH_SECT: 2332 - CONFIG_SYS_MAX_FLASH_SECT:
2328 Max number of sectors on a Flash chip 2333 Max number of sectors on a Flash chip
2329 2334
2330 - CONFIG_SYS_FLASH_ERASE_TOUT: 2335 - CONFIG_SYS_FLASH_ERASE_TOUT:
2331 Timeout for Flash erase operations (in ms) 2336 Timeout for Flash erase operations (in ms)
2332 2337
2333 - CONFIG_SYS_FLASH_WRITE_TOUT: 2338 - CONFIG_SYS_FLASH_WRITE_TOUT:
2334 Timeout for Flash write operations (in ms) 2339 Timeout for Flash write operations (in ms)
2335 2340
2336 - CONFIG_SYS_FLASH_LOCK_TOUT 2341 - CONFIG_SYS_FLASH_LOCK_TOUT
2337 Timeout for Flash set sector lock bit operation (in ms) 2342 Timeout for Flash set sector lock bit operation (in ms)
2338 2343
2339 - CONFIG_SYS_FLASH_UNLOCK_TOUT 2344 - CONFIG_SYS_FLASH_UNLOCK_TOUT
2340 Timeout for Flash clear lock bits operation (in ms) 2345 Timeout for Flash clear lock bits operation (in ms)
2341 2346
2342 - CONFIG_SYS_FLASH_PROTECTION 2347 - CONFIG_SYS_FLASH_PROTECTION
2343 If defined, hardware flash sectors protection is used 2348 If defined, hardware flash sectors protection is used
2344 instead of U-Boot software protection. 2349 instead of U-Boot software protection.
2345 2350
2346 - CONFIG_SYS_DIRECT_FLASH_TFTP: 2351 - CONFIG_SYS_DIRECT_FLASH_TFTP:
2347 2352
2348 Enable TFTP transfers directly to flash memory; 2353 Enable TFTP transfers directly to flash memory;
2349 without this option such a download has to be 2354 without this option such a download has to be
2350 performed in two steps: (1) download to RAM, and (2) 2355 performed in two steps: (1) download to RAM, and (2)
2351 copy from RAM to flash. 2356 copy from RAM to flash.
2352 2357
2353 The two-step approach is usually more reliable, since 2358 The two-step approach is usually more reliable, since
2354 you can check if the download worked before you erase 2359 you can check if the download worked before you erase
2355 the flash, but in some situations (when system RAM is 2360 the flash, but in some situations (when system RAM is
2356 too limited to allow for a temporary copy of the 2361 too limited to allow for a temporary copy of the
2357 downloaded image) this option may be very useful. 2362 downloaded image) this option may be very useful.
2358 2363
2359 - CONFIG_SYS_FLASH_CFI: 2364 - CONFIG_SYS_FLASH_CFI:
2360 Define if the flash driver uses extra elements in the 2365 Define if the flash driver uses extra elements in the
2361 common flash structure for storing flash geometry. 2366 common flash structure for storing flash geometry.
2362 2367
2363 - CONFIG_FLASH_CFI_DRIVER 2368 - CONFIG_FLASH_CFI_DRIVER
2364 This option also enables the building of the cfi_flash driver 2369 This option also enables the building of the cfi_flash driver
2365 in the drivers directory 2370 in the drivers directory
2366 2371
2367 - CONFIG_FLASH_CFI_MTD 2372 - CONFIG_FLASH_CFI_MTD
2368 This option enables the building of the cfi_mtd driver 2373 This option enables the building of the cfi_mtd driver
2369 in the drivers directory. The driver exports CFI flash 2374 in the drivers directory. The driver exports CFI flash
2370 to the MTD layer. 2375 to the MTD layer.
2371 2376
2372 - CONFIG_SYS_FLASH_USE_BUFFER_WRITE 2377 - CONFIG_SYS_FLASH_USE_BUFFER_WRITE
2373 Use buffered writes to flash. 2378 Use buffered writes to flash.
2374 2379
2375 - CONFIG_FLASH_SPANSION_S29WS_N 2380 - CONFIG_FLASH_SPANSION_S29WS_N
2376 s29ws-n MirrorBit flash has non-standard addresses for buffered 2381 s29ws-n MirrorBit flash has non-standard addresses for buffered
2377 write commands. 2382 write commands.
2378 2383
2379 - CONFIG_SYS_FLASH_QUIET_TEST 2384 - CONFIG_SYS_FLASH_QUIET_TEST
2380 If this option is defined, the common CFI flash doesn't 2385 If this option is defined, the common CFI flash doesn't
2381 print it's warning upon not recognized FLASH banks. This 2386 print it's warning upon not recognized FLASH banks. This
2382 is useful, if some of the configured banks are only 2387 is useful, if some of the configured banks are only
2383 optionally available. 2388 optionally available.
2384 2389
2385 - CONFIG_FLASH_SHOW_PROGRESS 2390 - CONFIG_FLASH_SHOW_PROGRESS
2386 If defined (must be an integer), print out countdown 2391 If defined (must be an integer), print out countdown
2387 digits and dots. Recommended value: 45 (9..1) for 80 2392 digits and dots. Recommended value: 45 (9..1) for 80
2388 column displays, 15 (3..1) for 40 column displays. 2393 column displays, 15 (3..1) for 40 column displays.
2389 2394
2390 - CONFIG_SYS_RX_ETH_BUFFER: 2395 - CONFIG_SYS_RX_ETH_BUFFER:
2391 Defines the number of Ethernet receive buffers. On some 2396 Defines the number of Ethernet receive buffers. On some
2392 Ethernet controllers it is recommended to set this value 2397 Ethernet controllers it is recommended to set this value
2393 to 8 or even higher (EEPRO100 or 405 EMAC), since all 2398 to 8 or even higher (EEPRO100 or 405 EMAC), since all
2394 buffers can be full shortly after enabling the interface 2399 buffers can be full shortly after enabling the interface
2395 on high Ethernet traffic. 2400 on high Ethernet traffic.
2396 Defaults to 4 if not defined. 2401 Defaults to 4 if not defined.
2397 2402
2398 - CONFIG_ENV_MAX_ENTRIES 2403 - CONFIG_ENV_MAX_ENTRIES
2399 2404
2400 Maximum number of entries in the hash table that is used 2405 Maximum number of entries in the hash table that is used
2401 internally to store the environment settings. The default 2406 internally to store the environment settings. The default
2402 setting is supposed to be generous and should work in most 2407 setting is supposed to be generous and should work in most
2403 cases. This setting can be used to tune behaviour; see 2408 cases. This setting can be used to tune behaviour; see
2404 lib/hashtable.c for details. 2409 lib/hashtable.c for details.
2405 2410
2406 The following definitions that deal with the placement and management 2411 The following definitions that deal with the placement and management
2407 of environment data (variable area); in general, we support the 2412 of environment data (variable area); in general, we support the
2408 following configurations: 2413 following configurations:
2409 2414
2410 - CONFIG_ENV_IS_IN_FLASH: 2415 - CONFIG_ENV_IS_IN_FLASH:
2411 2416
2412 Define this if the environment is in flash memory. 2417 Define this if the environment is in flash memory.
2413 2418
2414 a) The environment occupies one whole flash sector, which is 2419 a) The environment occupies one whole flash sector, which is
2415 "embedded" in the text segment with the U-Boot code. This 2420 "embedded" in the text segment with the U-Boot code. This
2416 happens usually with "bottom boot sector" or "top boot 2421 happens usually with "bottom boot sector" or "top boot
2417 sector" type flash chips, which have several smaller 2422 sector" type flash chips, which have several smaller
2418 sectors at the start or the end. For instance, such a 2423 sectors at the start or the end. For instance, such a
2419 layout can have sector sizes of 8, 2x4, 16, Nx32 kB. In 2424 layout can have sector sizes of 8, 2x4, 16, Nx32 kB. In
2420 such a case you would place the environment in one of the 2425 such a case you would place the environment in one of the
2421 4 kB sectors - with U-Boot code before and after it. With 2426 4 kB sectors - with U-Boot code before and after it. With
2422 "top boot sector" type flash chips, you would put the 2427 "top boot sector" type flash chips, you would put the
2423 environment in one of the last sectors, leaving a gap 2428 environment in one of the last sectors, leaving a gap
2424 between U-Boot and the environment. 2429 between U-Boot and the environment.
2425 2430
2426 - CONFIG_ENV_OFFSET: 2431 - CONFIG_ENV_OFFSET:
2427 2432
2428 Offset of environment data (variable area) to the 2433 Offset of environment data (variable area) to the
2429 beginning of flash memory; for instance, with bottom boot 2434 beginning of flash memory; for instance, with bottom boot
2430 type flash chips the second sector can be used: the offset 2435 type flash chips the second sector can be used: the offset
2431 for this sector is given here. 2436 for this sector is given here.
2432 2437
2433 CONFIG_ENV_OFFSET is used relative to CONFIG_SYS_FLASH_BASE. 2438 CONFIG_ENV_OFFSET is used relative to CONFIG_SYS_FLASH_BASE.
2434 2439
2435 - CONFIG_ENV_ADDR: 2440 - CONFIG_ENV_ADDR:
2436 2441
2437 This is just another way to specify the start address of 2442 This is just another way to specify the start address of
2438 the flash sector containing the environment (instead of 2443 the flash sector containing the environment (instead of
2439 CONFIG_ENV_OFFSET). 2444 CONFIG_ENV_OFFSET).
2440 2445
2441 - CONFIG_ENV_SECT_SIZE: 2446 - CONFIG_ENV_SECT_SIZE:
2442 2447
2443 Size of the sector containing the environment. 2448 Size of the sector containing the environment.
2444 2449
2445 2450
2446 b) Sometimes flash chips have few, equal sized, BIG sectors. 2451 b) Sometimes flash chips have few, equal sized, BIG sectors.
2447 In such a case you don't want to spend a whole sector for 2452 In such a case you don't want to spend a whole sector for
2448 the environment. 2453 the environment.
2449 2454
2450 - CONFIG_ENV_SIZE: 2455 - CONFIG_ENV_SIZE:
2451 2456
2452 If you use this in combination with CONFIG_ENV_IS_IN_FLASH 2457 If you use this in combination with CONFIG_ENV_IS_IN_FLASH
2453 and CONFIG_ENV_SECT_SIZE, you can specify to use only a part 2458 and CONFIG_ENV_SECT_SIZE, you can specify to use only a part
2454 of this flash sector for the environment. This saves 2459 of this flash sector for the environment. This saves
2455 memory for the RAM copy of the environment. 2460 memory for the RAM copy of the environment.
2456 2461
2457 It may also save flash memory if you decide to use this 2462 It may also save flash memory if you decide to use this
2458 when your environment is "embedded" within U-Boot code, 2463 when your environment is "embedded" within U-Boot code,
2459 since then the remainder of the flash sector could be used 2464 since then the remainder of the flash sector could be used
2460 for U-Boot code. It should be pointed out that this is 2465 for U-Boot code. It should be pointed out that this is
2461 STRONGLY DISCOURAGED from a robustness point of view: 2466 STRONGLY DISCOURAGED from a robustness point of view:
2462 updating the environment in flash makes it always 2467 updating the environment in flash makes it always
2463 necessary to erase the WHOLE sector. If something goes 2468 necessary to erase the WHOLE sector. If something goes
2464 wrong before the contents has been restored from a copy in 2469 wrong before the contents has been restored from a copy in
2465 RAM, your target system will be dead. 2470 RAM, your target system will be dead.
2466 2471
2467 - CONFIG_ENV_ADDR_REDUND 2472 - CONFIG_ENV_ADDR_REDUND
2468 CONFIG_ENV_SIZE_REDUND 2473 CONFIG_ENV_SIZE_REDUND
2469 2474
2470 These settings describe a second storage area used to hold 2475 These settings describe a second storage area used to hold
2471 a redundant copy of the environment data, so that there is 2476 a redundant copy of the environment data, so that there is
2472 a valid backup copy in case there is a power failure during 2477 a valid backup copy in case there is a power failure during
2473 a "saveenv" operation. 2478 a "saveenv" operation.
2474 2479
2475 BE CAREFUL! Any changes to the flash layout, and some changes to the 2480 BE CAREFUL! Any changes to the flash layout, and some changes to the
2476 source code will make it necessary to adapt <board>/u-boot.lds* 2481 source code will make it necessary to adapt <board>/u-boot.lds*
2477 accordingly! 2482 accordingly!
2478 2483
2479 2484
2480 - CONFIG_ENV_IS_IN_NVRAM: 2485 - CONFIG_ENV_IS_IN_NVRAM:
2481 2486
2482 Define this if you have some non-volatile memory device 2487 Define this if you have some non-volatile memory device
2483 (NVRAM, battery buffered SRAM) which you want to use for the 2488 (NVRAM, battery buffered SRAM) which you want to use for the
2484 environment. 2489 environment.
2485 2490
2486 - CONFIG_ENV_ADDR: 2491 - CONFIG_ENV_ADDR:
2487 - CONFIG_ENV_SIZE: 2492 - CONFIG_ENV_SIZE:
2488 2493
2489 These two #defines are used to determine the memory area you 2494 These two #defines are used to determine the memory area you
2490 want to use for environment. It is assumed that this memory 2495 want to use for environment. It is assumed that this memory
2491 can just be read and written to, without any special 2496 can just be read and written to, without any special
2492 provision. 2497 provision.
2493 2498
2494 BE CAREFUL! The first access to the environment happens quite early 2499 BE CAREFUL! The first access to the environment happens quite early
2495 in U-Boot initalization (when we try to get the setting of for the 2500 in U-Boot initalization (when we try to get the setting of for the
2496 console baudrate). You *MUST* have mapped your NVRAM area then, or 2501 console baudrate). You *MUST* have mapped your NVRAM area then, or
2497 U-Boot will hang. 2502 U-Boot will hang.
2498 2503
2499 Please note that even with NVRAM we still use a copy of the 2504 Please note that even with NVRAM we still use a copy of the
2500 environment in RAM: we could work on NVRAM directly, but we want to 2505 environment in RAM: we could work on NVRAM directly, but we want to
2501 keep settings there always unmodified except somebody uses "saveenv" 2506 keep settings there always unmodified except somebody uses "saveenv"
2502 to save the current settings. 2507 to save the current settings.
2503 2508
2504 2509
2505 - CONFIG_ENV_IS_IN_EEPROM: 2510 - CONFIG_ENV_IS_IN_EEPROM:
2506 2511
2507 Use this if you have an EEPROM or similar serial access 2512 Use this if you have an EEPROM or similar serial access
2508 device and a driver for it. 2513 device and a driver for it.
2509 2514
2510 - CONFIG_ENV_OFFSET: 2515 - CONFIG_ENV_OFFSET:
2511 - CONFIG_ENV_SIZE: 2516 - CONFIG_ENV_SIZE:
2512 2517
2513 These two #defines specify the offset and size of the 2518 These two #defines specify the offset and size of the
2514 environment area within the total memory of your EEPROM. 2519 environment area within the total memory of your EEPROM.
2515 2520
2516 - CONFIG_SYS_I2C_EEPROM_ADDR: 2521 - CONFIG_SYS_I2C_EEPROM_ADDR:
2517 If defined, specified the chip address of the EEPROM device. 2522 If defined, specified the chip address of the EEPROM device.
2518 The default address is zero. 2523 The default address is zero.
2519 2524
2520 - CONFIG_SYS_EEPROM_PAGE_WRITE_BITS: 2525 - CONFIG_SYS_EEPROM_PAGE_WRITE_BITS:
2521 If defined, the number of bits used to address bytes in a 2526 If defined, the number of bits used to address bytes in a
2522 single page in the EEPROM device. A 64 byte page, for example 2527 single page in the EEPROM device. A 64 byte page, for example
2523 would require six bits. 2528 would require six bits.
2524 2529
2525 - CONFIG_SYS_EEPROM_PAGE_WRITE_DELAY_MS: 2530 - CONFIG_SYS_EEPROM_PAGE_WRITE_DELAY_MS:
2526 If defined, the number of milliseconds to delay between 2531 If defined, the number of milliseconds to delay between
2527 page writes. The default is zero milliseconds. 2532 page writes. The default is zero milliseconds.
2528 2533
2529 - CONFIG_SYS_I2C_EEPROM_ADDR_LEN: 2534 - CONFIG_SYS_I2C_EEPROM_ADDR_LEN:
2530 The length in bytes of the EEPROM memory array address. Note 2535 The length in bytes of the EEPROM memory array address. Note
2531 that this is NOT the chip address length! 2536 that this is NOT the chip address length!
2532 2537
2533 - CONFIG_SYS_I2C_EEPROM_ADDR_OVERFLOW: 2538 - CONFIG_SYS_I2C_EEPROM_ADDR_OVERFLOW:
2534 EEPROM chips that implement "address overflow" are ones 2539 EEPROM chips that implement "address overflow" are ones
2535 like Catalyst 24WC04/08/16 which has 9/10/11 bits of 2540 like Catalyst 24WC04/08/16 which has 9/10/11 bits of
2536 address and the extra bits end up in the "chip address" bit 2541 address and the extra bits end up in the "chip address" bit
2537 slots. This makes a 24WC08 (1Kbyte) chip look like four 256 2542 slots. This makes a 24WC08 (1Kbyte) chip look like four 256
2538 byte chips. 2543 byte chips.
2539 2544
2540 Note that we consider the length of the address field to 2545 Note that we consider the length of the address field to
2541 still be one byte because the extra address bits are hidden 2546 still be one byte because the extra address bits are hidden
2542 in the chip address. 2547 in the chip address.
2543 2548
2544 - CONFIG_SYS_EEPROM_SIZE: 2549 - CONFIG_SYS_EEPROM_SIZE:
2545 The size in bytes of the EEPROM device. 2550 The size in bytes of the EEPROM device.
2546 2551
2547 - CONFIG_ENV_EEPROM_IS_ON_I2C 2552 - CONFIG_ENV_EEPROM_IS_ON_I2C
2548 define this, if you have I2C and SPI activated, and your 2553 define this, if you have I2C and SPI activated, and your
2549 EEPROM, which holds the environment, is on the I2C bus. 2554 EEPROM, which holds the environment, is on the I2C bus.
2550 2555
2551 - CONFIG_I2C_ENV_EEPROM_BUS 2556 - CONFIG_I2C_ENV_EEPROM_BUS
2552 if you have an Environment on an EEPROM reached over 2557 if you have an Environment on an EEPROM reached over
2553 I2C muxes, you can define here, how to reach this 2558 I2C muxes, you can define here, how to reach this
2554 EEPROM. For example: 2559 EEPROM. For example:
2555 2560
2556 #define CONFIG_I2C_ENV_EEPROM_BUS "pca9547:70:d\0" 2561 #define CONFIG_I2C_ENV_EEPROM_BUS "pca9547:70:d\0"
2557 2562
2558 EEPROM which holds the environment, is reached over 2563 EEPROM which holds the environment, is reached over
2559 a pca9547 i2c mux with address 0x70, channel 3. 2564 a pca9547 i2c mux with address 0x70, channel 3.
2560 2565
2561 - CONFIG_ENV_IS_IN_DATAFLASH: 2566 - CONFIG_ENV_IS_IN_DATAFLASH:
2562 2567
2563 Define this if you have a DataFlash memory device which you 2568 Define this if you have a DataFlash memory device which you
2564 want to use for the environment. 2569 want to use for the environment.
2565 2570
2566 - CONFIG_ENV_OFFSET: 2571 - CONFIG_ENV_OFFSET:
2567 - CONFIG_ENV_ADDR: 2572 - CONFIG_ENV_ADDR:
2568 - CONFIG_ENV_SIZE: 2573 - CONFIG_ENV_SIZE:
2569 2574
2570 These three #defines specify the offset and size of the 2575 These three #defines specify the offset and size of the
2571 environment area within the total memory of your DataFlash placed 2576 environment area within the total memory of your DataFlash placed
2572 at the specified address. 2577 at the specified address.
2573 2578
2574 - CONFIG_ENV_IS_IN_NAND: 2579 - CONFIG_ENV_IS_IN_NAND:
2575 2580
2576 Define this if you have a NAND device which you want to use 2581 Define this if you have a NAND device which you want to use
2577 for the environment. 2582 for the environment.
2578 2583
2579 - CONFIG_ENV_OFFSET: 2584 - CONFIG_ENV_OFFSET:
2580 - CONFIG_ENV_SIZE: 2585 - CONFIG_ENV_SIZE:
2581 2586
2582 These two #defines specify the offset and size of the environment 2587 These two #defines specify the offset and size of the environment
2583 area within the first NAND device. CONFIG_ENV_OFFSET must be 2588 area within the first NAND device. CONFIG_ENV_OFFSET must be
2584 aligned to an erase block boundary. 2589 aligned to an erase block boundary.
2585 2590
2586 - CONFIG_ENV_OFFSET_REDUND (optional): 2591 - CONFIG_ENV_OFFSET_REDUND (optional):
2587 2592
2588 This setting describes a second storage area of CONFIG_ENV_SIZE 2593 This setting describes a second storage area of CONFIG_ENV_SIZE
2589 size used to hold a redundant copy of the environment data, so 2594 size used to hold a redundant copy of the environment data, so
2590 that there is a valid backup copy in case there is a power failure 2595 that there is a valid backup copy in case there is a power failure
2591 during a "saveenv" operation. CONFIG_ENV_OFFSET_RENDUND must be 2596 during a "saveenv" operation. CONFIG_ENV_OFFSET_RENDUND must be
2592 aligned to an erase block boundary. 2597 aligned to an erase block boundary.
2593 2598
2594 - CONFIG_ENV_RANGE (optional): 2599 - CONFIG_ENV_RANGE (optional):
2595 2600
2596 Specifies the length of the region in which the environment 2601 Specifies the length of the region in which the environment
2597 can be written. This should be a multiple of the NAND device's 2602 can be written. This should be a multiple of the NAND device's
2598 block size. Specifying a range with more erase blocks than 2603 block size. Specifying a range with more erase blocks than
2599 are needed to hold CONFIG_ENV_SIZE allows bad blocks within 2604 are needed to hold CONFIG_ENV_SIZE allows bad blocks within
2600 the range to be avoided. 2605 the range to be avoided.
2601 2606
2602 - CONFIG_ENV_OFFSET_OOB (optional): 2607 - CONFIG_ENV_OFFSET_OOB (optional):
2603 2608
2604 Enables support for dynamically retrieving the offset of the 2609 Enables support for dynamically retrieving the offset of the
2605 environment from block zero's out-of-band data. The 2610 environment from block zero's out-of-band data. The
2606 "nand env.oob" command can be used to record this offset. 2611 "nand env.oob" command can be used to record this offset.
2607 Currently, CONFIG_ENV_OFFSET_REDUND is not supported when 2612 Currently, CONFIG_ENV_OFFSET_REDUND is not supported when
2608 using CONFIG_ENV_OFFSET_OOB. 2613 using CONFIG_ENV_OFFSET_OOB.
2609 2614
2610 - CONFIG_NAND_ENV_DST 2615 - CONFIG_NAND_ENV_DST
2611 2616
2612 Defines address in RAM to which the nand_spl code should copy the 2617 Defines address in RAM to which the nand_spl code should copy the
2613 environment. If redundant environment is used, it will be copied to 2618 environment. If redundant environment is used, it will be copied to
2614 CONFIG_NAND_ENV_DST + CONFIG_ENV_SIZE. 2619 CONFIG_NAND_ENV_DST + CONFIG_ENV_SIZE.
2615 2620
2616 - CONFIG_SYS_SPI_INIT_OFFSET 2621 - CONFIG_SYS_SPI_INIT_OFFSET
2617 2622
2618 Defines offset to the initial SPI buffer area in DPRAM. The 2623 Defines offset to the initial SPI buffer area in DPRAM. The
2619 area is used at an early stage (ROM part) if the environment 2624 area is used at an early stage (ROM part) if the environment
2620 is configured to reside in the SPI EEPROM: We need a 520 byte 2625 is configured to reside in the SPI EEPROM: We need a 520 byte
2621 scratch DPRAM area. It is used between the two initialization 2626 scratch DPRAM area. It is used between the two initialization
2622 calls (spi_init_f() and spi_init_r()). A value of 0xB00 seems 2627 calls (spi_init_f() and spi_init_r()). A value of 0xB00 seems
2623 to be a good choice since it makes it far enough from the 2628 to be a good choice since it makes it far enough from the
2624 start of the data area as well as from the stack pointer. 2629 start of the data area as well as from the stack pointer.
2625 2630
2626 Please note that the environment is read-only until the monitor 2631 Please note that the environment is read-only until the monitor
2627 has been relocated to RAM and a RAM copy of the environment has been 2632 has been relocated to RAM and a RAM copy of the environment has been
2628 created; also, when using EEPROM you will have to use getenv_f() 2633 created; also, when using EEPROM you will have to use getenv_f()
2629 until then to read environment variables. 2634 until then to read environment variables.
2630 2635
2631 The environment is protected by a CRC32 checksum. Before the monitor 2636 The environment is protected by a CRC32 checksum. Before the monitor
2632 is relocated into RAM, as a result of a bad CRC you will be working 2637 is relocated into RAM, as a result of a bad CRC you will be working
2633 with the compiled-in default environment - *silently*!!! [This is 2638 with the compiled-in default environment - *silently*!!! [This is
2634 necessary, because the first environment variable we need is the 2639 necessary, because the first environment variable we need is the
2635 "baudrate" setting for the console - if we have a bad CRC, we don't 2640 "baudrate" setting for the console - if we have a bad CRC, we don't
2636 have any device yet where we could complain.] 2641 have any device yet where we could complain.]
2637 2642
2638 Note: once the monitor has been relocated, then it will complain if 2643 Note: once the monitor has been relocated, then it will complain if
2639 the default environment is used; a new CRC is computed as soon as you 2644 the default environment is used; a new CRC is computed as soon as you
2640 use the "saveenv" command to store a valid environment. 2645 use the "saveenv" command to store a valid environment.
2641 2646
2642 - CONFIG_SYS_FAULT_ECHO_LINK_DOWN: 2647 - CONFIG_SYS_FAULT_ECHO_LINK_DOWN:
2643 Echo the inverted Ethernet link state to the fault LED. 2648 Echo the inverted Ethernet link state to the fault LED.
2644 2649
2645 Note: If this option is active, then CONFIG_SYS_FAULT_MII_ADDR 2650 Note: If this option is active, then CONFIG_SYS_FAULT_MII_ADDR
2646 also needs to be defined. 2651 also needs to be defined.
2647 2652
2648 - CONFIG_SYS_FAULT_MII_ADDR: 2653 - CONFIG_SYS_FAULT_MII_ADDR:
2649 MII address of the PHY to check for the Ethernet link state. 2654 MII address of the PHY to check for the Ethernet link state.
2650 2655
2651 - CONFIG_NS16550_MIN_FUNCTIONS: 2656 - CONFIG_NS16550_MIN_FUNCTIONS:
2652 Define this if you desire to only have use of the NS16550_init 2657 Define this if you desire to only have use of the NS16550_init
2653 and NS16550_putc functions for the serial driver located at 2658 and NS16550_putc functions for the serial driver located at
2654 drivers/serial/ns16550.c. This option is useful for saving 2659 drivers/serial/ns16550.c. This option is useful for saving
2655 space for already greatly restricted images, including but not 2660 space for already greatly restricted images, including but not
2656 limited to NAND_SPL configurations. 2661 limited to NAND_SPL configurations.
2657 2662
2658 Low Level (hardware related) configuration options: 2663 Low Level (hardware related) configuration options:
2659 --------------------------------------------------- 2664 ---------------------------------------------------
2660 2665
2661 - CONFIG_SYS_CACHELINE_SIZE: 2666 - CONFIG_SYS_CACHELINE_SIZE:
2662 Cache Line Size of the CPU. 2667 Cache Line Size of the CPU.
2663 2668
2664 - CONFIG_SYS_DEFAULT_IMMR: 2669 - CONFIG_SYS_DEFAULT_IMMR:
2665 Default address of the IMMR after system reset. 2670 Default address of the IMMR after system reset.
2666 2671
2667 Needed on some 8260 systems (MPC8260ADS, PQ2FADS-ZU, 2672 Needed on some 8260 systems (MPC8260ADS, PQ2FADS-ZU,
2668 and RPXsuper) to be able to adjust the position of 2673 and RPXsuper) to be able to adjust the position of
2669 the IMMR register after a reset. 2674 the IMMR register after a reset.
2670 2675
2671 - Floppy Disk Support: 2676 - Floppy Disk Support:
2672 CONFIG_SYS_FDC_DRIVE_NUMBER 2677 CONFIG_SYS_FDC_DRIVE_NUMBER
2673 2678
2674 the default drive number (default value 0) 2679 the default drive number (default value 0)
2675 2680
2676 CONFIG_SYS_ISA_IO_STRIDE 2681 CONFIG_SYS_ISA_IO_STRIDE
2677 2682
2678 defines the spacing between FDC chipset registers 2683 defines the spacing between FDC chipset registers
2679 (default value 1) 2684 (default value 1)
2680 2685
2681 CONFIG_SYS_ISA_IO_OFFSET 2686 CONFIG_SYS_ISA_IO_OFFSET
2682 2687
2683 defines the offset of register from address. It 2688 defines the offset of register from address. It
2684 depends on which part of the data bus is connected to 2689 depends on which part of the data bus is connected to
2685 the FDC chipset. (default value 0) 2690 the FDC chipset. (default value 0)
2686 2691
2687 If CONFIG_SYS_ISA_IO_STRIDE CONFIG_SYS_ISA_IO_OFFSET and 2692 If CONFIG_SYS_ISA_IO_STRIDE CONFIG_SYS_ISA_IO_OFFSET and
2688 CONFIG_SYS_FDC_DRIVE_NUMBER are undefined, they take their 2693 CONFIG_SYS_FDC_DRIVE_NUMBER are undefined, they take their
2689 default value. 2694 default value.
2690 2695
2691 if CONFIG_SYS_FDC_HW_INIT is defined, then the function 2696 if CONFIG_SYS_FDC_HW_INIT is defined, then the function
2692 fdc_hw_init() is called at the beginning of the FDC 2697 fdc_hw_init() is called at the beginning of the FDC
2693 setup. fdc_hw_init() must be provided by the board 2698 setup. fdc_hw_init() must be provided by the board
2694 source code. It is used to make hardware dependant 2699 source code. It is used to make hardware dependant
2695 initializations. 2700 initializations.
2696 2701
2697 - CONFIG_SYS_IMMR: Physical address of the Internal Memory. 2702 - CONFIG_SYS_IMMR: Physical address of the Internal Memory.
2698 DO NOT CHANGE unless you know exactly what you're 2703 DO NOT CHANGE unless you know exactly what you're
2699 doing! (11-4) [MPC8xx/82xx systems only] 2704 doing! (11-4) [MPC8xx/82xx systems only]
2700 2705
2701 - CONFIG_SYS_INIT_RAM_ADDR: 2706 - CONFIG_SYS_INIT_RAM_ADDR:
2702 2707
2703 Start address of memory area that can be used for 2708 Start address of memory area that can be used for
2704 initial data and stack; please note that this must be 2709 initial data and stack; please note that this must be
2705 writable memory that is working WITHOUT special 2710 writable memory that is working WITHOUT special
2706 initialization, i. e. you CANNOT use normal RAM which 2711 initialization, i. e. you CANNOT use normal RAM which
2707 will become available only after programming the 2712 will become available only after programming the
2708 memory controller and running certain initialization 2713 memory controller and running certain initialization
2709 sequences. 2714 sequences.
2710 2715
2711 U-Boot uses the following memory types: 2716 U-Boot uses the following memory types:
2712 - MPC8xx and MPC8260: IMMR (internal memory of the CPU) 2717 - MPC8xx and MPC8260: IMMR (internal memory of the CPU)
2713 - MPC824X: data cache 2718 - MPC824X: data cache
2714 - PPC4xx: data cache 2719 - PPC4xx: data cache
2715 2720
2716 - CONFIG_SYS_GBL_DATA_OFFSET: 2721 - CONFIG_SYS_GBL_DATA_OFFSET:
2717 2722
2718 Offset of the initial data structure in the memory 2723 Offset of the initial data structure in the memory
2719 area defined by CONFIG_SYS_INIT_RAM_ADDR. Usually 2724 area defined by CONFIG_SYS_INIT_RAM_ADDR. Usually
2720 CONFIG_SYS_GBL_DATA_OFFSET is chosen such that the initial 2725 CONFIG_SYS_GBL_DATA_OFFSET is chosen such that the initial
2721 data is located at the end of the available space 2726 data is located at the end of the available space
2722 (sometimes written as (CONFIG_SYS_INIT_RAM_SIZE - 2727 (sometimes written as (CONFIG_SYS_INIT_RAM_SIZE -
2723 CONFIG_SYS_INIT_DATA_SIZE), and the initial stack is just 2728 CONFIG_SYS_INIT_DATA_SIZE), and the initial stack is just
2724 below that area (growing from (CONFIG_SYS_INIT_RAM_ADDR + 2729 below that area (growing from (CONFIG_SYS_INIT_RAM_ADDR +
2725 CONFIG_SYS_GBL_DATA_OFFSET) downward. 2730 CONFIG_SYS_GBL_DATA_OFFSET) downward.
2726 2731
2727 Note: 2732 Note:
2728 On the MPC824X (or other systems that use the data 2733 On the MPC824X (or other systems that use the data
2729 cache for initial memory) the address chosen for 2734 cache for initial memory) the address chosen for
2730 CONFIG_SYS_INIT_RAM_ADDR is basically arbitrary - it must 2735 CONFIG_SYS_INIT_RAM_ADDR is basically arbitrary - it must
2731 point to an otherwise UNUSED address space between 2736 point to an otherwise UNUSED address space between
2732 the top of RAM and the start of the PCI space. 2737 the top of RAM and the start of the PCI space.
2733 2738
2734 - CONFIG_SYS_SIUMCR: SIU Module Configuration (11-6) 2739 - CONFIG_SYS_SIUMCR: SIU Module Configuration (11-6)
2735 2740
2736 - CONFIG_SYS_SYPCR: System Protection Control (11-9) 2741 - CONFIG_SYS_SYPCR: System Protection Control (11-9)
2737 2742
2738 - CONFIG_SYS_TBSCR: Time Base Status and Control (11-26) 2743 - CONFIG_SYS_TBSCR: Time Base Status and Control (11-26)
2739 2744
2740 - CONFIG_SYS_PISCR: Periodic Interrupt Status and Control (11-31) 2745 - CONFIG_SYS_PISCR: Periodic Interrupt Status and Control (11-31)
2741 2746
2742 - CONFIG_SYS_PLPRCR: PLL, Low-Power, and Reset Control Register (15-30) 2747 - CONFIG_SYS_PLPRCR: PLL, Low-Power, and Reset Control Register (15-30)
2743 2748
2744 - CONFIG_SYS_SCCR: System Clock and reset Control Register (15-27) 2749 - CONFIG_SYS_SCCR: System Clock and reset Control Register (15-27)
2745 2750
2746 - CONFIG_SYS_OR_TIMING_SDRAM: 2751 - CONFIG_SYS_OR_TIMING_SDRAM:
2747 SDRAM timing 2752 SDRAM timing
2748 2753
2749 - CONFIG_SYS_MAMR_PTA: 2754 - CONFIG_SYS_MAMR_PTA:
2750 periodic timer for refresh 2755 periodic timer for refresh
2751 2756
2752 - CONFIG_SYS_DER: Debug Event Register (37-47) 2757 - CONFIG_SYS_DER: Debug Event Register (37-47)
2753 2758
2754 - FLASH_BASE0_PRELIM, FLASH_BASE1_PRELIM, CONFIG_SYS_REMAP_OR_AM, 2759 - FLASH_BASE0_PRELIM, FLASH_BASE1_PRELIM, CONFIG_SYS_REMAP_OR_AM,
2755 CONFIG_SYS_PRELIM_OR_AM, CONFIG_SYS_OR_TIMING_FLASH, CONFIG_SYS_OR0_REMAP, 2760 CONFIG_SYS_PRELIM_OR_AM, CONFIG_SYS_OR_TIMING_FLASH, CONFIG_SYS_OR0_REMAP,
2756 CONFIG_SYS_OR0_PRELIM, CONFIG_SYS_BR0_PRELIM, CONFIG_SYS_OR1_REMAP, CONFIG_SYS_OR1_PRELIM, 2761 CONFIG_SYS_OR0_PRELIM, CONFIG_SYS_BR0_PRELIM, CONFIG_SYS_OR1_REMAP, CONFIG_SYS_OR1_PRELIM,
2757 CONFIG_SYS_BR1_PRELIM: 2762 CONFIG_SYS_BR1_PRELIM:
2758 Memory Controller Definitions: BR0/1 and OR0/1 (FLASH) 2763 Memory Controller Definitions: BR0/1 and OR0/1 (FLASH)
2759 2764
2760 - SDRAM_BASE2_PRELIM, SDRAM_BASE3_PRELIM, SDRAM_MAX_SIZE, 2765 - SDRAM_BASE2_PRELIM, SDRAM_BASE3_PRELIM, SDRAM_MAX_SIZE,
2761 CONFIG_SYS_OR_TIMING_SDRAM, CONFIG_SYS_OR2_PRELIM, CONFIG_SYS_BR2_PRELIM, 2766 CONFIG_SYS_OR_TIMING_SDRAM, CONFIG_SYS_OR2_PRELIM, CONFIG_SYS_BR2_PRELIM,
2762 CONFIG_SYS_OR3_PRELIM, CONFIG_SYS_BR3_PRELIM: 2767 CONFIG_SYS_OR3_PRELIM, CONFIG_SYS_BR3_PRELIM:
2763 Memory Controller Definitions: BR2/3 and OR2/3 (SDRAM) 2768 Memory Controller Definitions: BR2/3 and OR2/3 (SDRAM)
2764 2769
2765 - CONFIG_SYS_MAMR_PTA, CONFIG_SYS_MPTPR_2BK_4K, CONFIG_SYS_MPTPR_1BK_4K, CONFIG_SYS_MPTPR_2BK_8K, 2770 - CONFIG_SYS_MAMR_PTA, CONFIG_SYS_MPTPR_2BK_4K, CONFIG_SYS_MPTPR_1BK_4K, CONFIG_SYS_MPTPR_2BK_8K,
2766 CONFIG_SYS_MPTPR_1BK_8K, CONFIG_SYS_MAMR_8COL, CONFIG_SYS_MAMR_9COL: 2771 CONFIG_SYS_MPTPR_1BK_8K, CONFIG_SYS_MAMR_8COL, CONFIG_SYS_MAMR_9COL:
2767 Machine Mode Register and Memory Periodic Timer 2772 Machine Mode Register and Memory Periodic Timer
2768 Prescaler definitions (SDRAM timing) 2773 Prescaler definitions (SDRAM timing)
2769 2774
2770 - CONFIG_SYS_I2C_UCODE_PATCH, CONFIG_SYS_I2C_DPMEM_OFFSET [0x1FC0]: 2775 - CONFIG_SYS_I2C_UCODE_PATCH, CONFIG_SYS_I2C_DPMEM_OFFSET [0x1FC0]:
2771 enable I2C microcode relocation patch (MPC8xx); 2776 enable I2C microcode relocation patch (MPC8xx);
2772 define relocation offset in DPRAM [DSP2] 2777 define relocation offset in DPRAM [DSP2]
2773 2778
2774 - CONFIG_SYS_SMC_UCODE_PATCH, CONFIG_SYS_SMC_DPMEM_OFFSET [0x1FC0]: 2779 - CONFIG_SYS_SMC_UCODE_PATCH, CONFIG_SYS_SMC_DPMEM_OFFSET [0x1FC0]:
2775 enable SMC microcode relocation patch (MPC8xx); 2780 enable SMC microcode relocation patch (MPC8xx);
2776 define relocation offset in DPRAM [SMC1] 2781 define relocation offset in DPRAM [SMC1]
2777 2782
2778 - CONFIG_SYS_SPI_UCODE_PATCH, CONFIG_SYS_SPI_DPMEM_OFFSET [0x1FC0]: 2783 - CONFIG_SYS_SPI_UCODE_PATCH, CONFIG_SYS_SPI_DPMEM_OFFSET [0x1FC0]:
2779 enable SPI microcode relocation patch (MPC8xx); 2784 enable SPI microcode relocation patch (MPC8xx);
2780 define relocation offset in DPRAM [SCC4] 2785 define relocation offset in DPRAM [SCC4]
2781 2786
2782 - CONFIG_SYS_USE_OSCCLK: 2787 - CONFIG_SYS_USE_OSCCLK:
2783 Use OSCM clock mode on MBX8xx board. Be careful, 2788 Use OSCM clock mode on MBX8xx board. Be careful,
2784 wrong setting might damage your board. Read 2789 wrong setting might damage your board. Read
2785 doc/README.MBX before setting this variable! 2790 doc/README.MBX before setting this variable!
2786 2791
2787 - CONFIG_SYS_CPM_POST_WORD_ADDR: (MPC8xx, MPC8260 only) 2792 - CONFIG_SYS_CPM_POST_WORD_ADDR: (MPC8xx, MPC8260 only)
2788 Offset of the bootmode word in DPRAM used by post 2793 Offset of the bootmode word in DPRAM used by post
2789 (Power On Self Tests). This definition overrides 2794 (Power On Self Tests). This definition overrides
2790 #define'd default value in commproc.h resp. 2795 #define'd default value in commproc.h resp.
2791 cpm_8260.h. 2796 cpm_8260.h.
2792 2797
2793 - CONFIG_SYS_PCI_SLV_MEM_LOCAL, CONFIG_SYS_PCI_SLV_MEM_BUS, CONFIG_SYS_PICMR0_MASK_ATTRIB, 2798 - CONFIG_SYS_PCI_SLV_MEM_LOCAL, CONFIG_SYS_PCI_SLV_MEM_BUS, CONFIG_SYS_PICMR0_MASK_ATTRIB,
2794 CONFIG_SYS_PCI_MSTR0_LOCAL, CONFIG_SYS_PCIMSK0_MASK, CONFIG_SYS_PCI_MSTR1_LOCAL, 2799 CONFIG_SYS_PCI_MSTR0_LOCAL, CONFIG_SYS_PCIMSK0_MASK, CONFIG_SYS_PCI_MSTR1_LOCAL,
2795 CONFIG_SYS_PCIMSK1_MASK, CONFIG_SYS_PCI_MSTR_MEM_LOCAL, CONFIG_SYS_PCI_MSTR_MEM_BUS, 2800 CONFIG_SYS_PCIMSK1_MASK, CONFIG_SYS_PCI_MSTR_MEM_LOCAL, CONFIG_SYS_PCI_MSTR_MEM_BUS,
2796 CONFIG_SYS_CPU_PCI_MEM_START, CONFIG_SYS_PCI_MSTR_MEM_SIZE, CONFIG_SYS_POCMR0_MASK_ATTRIB, 2801 CONFIG_SYS_CPU_PCI_MEM_START, CONFIG_SYS_PCI_MSTR_MEM_SIZE, CONFIG_SYS_POCMR0_MASK_ATTRIB,
2797 CONFIG_SYS_PCI_MSTR_MEMIO_LOCAL, CONFIG_SYS_PCI_MSTR_MEMIO_BUS, CPU_PCI_MEMIO_START, 2802 CONFIG_SYS_PCI_MSTR_MEMIO_LOCAL, CONFIG_SYS_PCI_MSTR_MEMIO_BUS, CPU_PCI_MEMIO_START,
2798 CONFIG_SYS_PCI_MSTR_MEMIO_SIZE, CONFIG_SYS_POCMR1_MASK_ATTRIB, CONFIG_SYS_PCI_MSTR_IO_LOCAL, 2803 CONFIG_SYS_PCI_MSTR_MEMIO_SIZE, CONFIG_SYS_POCMR1_MASK_ATTRIB, CONFIG_SYS_PCI_MSTR_IO_LOCAL,
2799 CONFIG_SYS_PCI_MSTR_IO_BUS, CONFIG_SYS_CPU_PCI_IO_START, CONFIG_SYS_PCI_MSTR_IO_SIZE, 2804 CONFIG_SYS_PCI_MSTR_IO_BUS, CONFIG_SYS_CPU_PCI_IO_START, CONFIG_SYS_PCI_MSTR_IO_SIZE,
2800 CONFIG_SYS_POCMR2_MASK_ATTRIB: (MPC826x only) 2805 CONFIG_SYS_POCMR2_MASK_ATTRIB: (MPC826x only)
2801 Overrides the default PCI memory map in arch/powerpc/cpu/mpc8260/pci.c if set. 2806 Overrides the default PCI memory map in arch/powerpc/cpu/mpc8260/pci.c if set.
2802 2807
2803 - CONFIG_PCI_DISABLE_PCIE: 2808 - CONFIG_PCI_DISABLE_PCIE:
2804 Disable PCI-Express on systems where it is supported but not 2809 Disable PCI-Express on systems where it is supported but not
2805 required. 2810 required.
2806 2811
2807 - CONFIG_SYS_SRIO: 2812 - CONFIG_SYS_SRIO:
2808 Chip has SRIO or not 2813 Chip has SRIO or not
2809 2814
2810 - CONFIG_SRIO1: 2815 - CONFIG_SRIO1:
2811 Board has SRIO 1 port available 2816 Board has SRIO 1 port available
2812 2817
2813 - CONFIG_SRIO2: 2818 - CONFIG_SRIO2:
2814 Board has SRIO 2 port available 2819 Board has SRIO 2 port available
2815 2820
2816 - CONFIG_SYS_SRIOn_MEM_VIRT: 2821 - CONFIG_SYS_SRIOn_MEM_VIRT:
2817 Virtual Address of SRIO port 'n' memory region 2822 Virtual Address of SRIO port 'n' memory region
2818 2823
2819 - CONFIG_SYS_SRIOn_MEM_PHYS: 2824 - CONFIG_SYS_SRIOn_MEM_PHYS:
2820 Physical Address of SRIO port 'n' memory region 2825 Physical Address of SRIO port 'n' memory region
2821 2826
2822 - CONFIG_SYS_SRIOn_MEM_SIZE: 2827 - CONFIG_SYS_SRIOn_MEM_SIZE:
2823 Size of SRIO port 'n' memory region 2828 Size of SRIO port 'n' memory region
2824 2829
2825 - CONFIG_SPD_EEPROM 2830 - CONFIG_SPD_EEPROM
2826 Get DDR timing information from an I2C EEPROM. Common 2831 Get DDR timing information from an I2C EEPROM. Common
2827 with pluggable memory modules such as SODIMMs 2832 with pluggable memory modules such as SODIMMs
2828 2833
2829 SPD_EEPROM_ADDRESS 2834 SPD_EEPROM_ADDRESS
2830 I2C address of the SPD EEPROM 2835 I2C address of the SPD EEPROM
2831 2836
2832 - CONFIG_SYS_SPD_BUS_NUM 2837 - CONFIG_SYS_SPD_BUS_NUM
2833 If SPD EEPROM is on an I2C bus other than the first 2838 If SPD EEPROM is on an I2C bus other than the first
2834 one, specify here. Note that the value must resolve 2839 one, specify here. Note that the value must resolve
2835 to something your driver can deal with. 2840 to something your driver can deal with.
2836 2841
2837 - CONFIG_SYS_83XX_DDR_USES_CS0 2842 - CONFIG_SYS_83XX_DDR_USES_CS0
2838 Only for 83xx systems. If specified, then DDR should 2843 Only for 83xx systems. If specified, then DDR should
2839 be configured using CS0 and CS1 instead of CS2 and CS3. 2844 be configured using CS0 and CS1 instead of CS2 and CS3.
2840 2845
2841 - CONFIG_ETHER_ON_FEC[12] 2846 - CONFIG_ETHER_ON_FEC[12]
2842 Define to enable FEC[12] on a 8xx series processor. 2847 Define to enable FEC[12] on a 8xx series processor.
2843 2848
2844 - CONFIG_FEC[12]_PHY 2849 - CONFIG_FEC[12]_PHY
2845 Define to the hardcoded PHY address which corresponds 2850 Define to the hardcoded PHY address which corresponds
2846 to the given FEC; i. e. 2851 to the given FEC; i. e.
2847 #define CONFIG_FEC1_PHY 4 2852 #define CONFIG_FEC1_PHY 4
2848 means that the PHY with address 4 is connected to FEC1 2853 means that the PHY with address 4 is connected to FEC1
2849 2854
2850 When set to -1, means to probe for first available. 2855 When set to -1, means to probe for first available.
2851 2856
2852 - CONFIG_FEC[12]_PHY_NORXERR 2857 - CONFIG_FEC[12]_PHY_NORXERR
2853 The PHY does not have a RXERR line (RMII only). 2858 The PHY does not have a RXERR line (RMII only).
2854 (so program the FEC to ignore it). 2859 (so program the FEC to ignore it).
2855 2860
2856 - CONFIG_RMII 2861 - CONFIG_RMII
2857 Enable RMII mode for all FECs. 2862 Enable RMII mode for all FECs.
2858 Note that this is a global option, we can't 2863 Note that this is a global option, we can't
2859 have one FEC in standard MII mode and another in RMII mode. 2864 have one FEC in standard MII mode and another in RMII mode.
2860 2865
2861 - CONFIG_CRC32_VERIFY 2866 - CONFIG_CRC32_VERIFY
2862 Add a verify option to the crc32 command. 2867 Add a verify option to the crc32 command.
2863 The syntax is: 2868 The syntax is:
2864 2869
2865 => crc32 -v <address> <count> <crc32> 2870 => crc32 -v <address> <count> <crc32>
2866 2871
2867 Where address/count indicate a memory area 2872 Where address/count indicate a memory area
2868 and crc32 is the correct crc32 which the 2873 and crc32 is the correct crc32 which the
2869 area should have. 2874 area should have.
2870 2875
2871 - CONFIG_LOOPW 2876 - CONFIG_LOOPW
2872 Add the "loopw" memory command. This only takes effect if 2877 Add the "loopw" memory command. This only takes effect if
2873 the memory commands are activated globally (CONFIG_CMD_MEM). 2878 the memory commands are activated globally (CONFIG_CMD_MEM).
2874 2879
2875 - CONFIG_MX_CYCLIC 2880 - CONFIG_MX_CYCLIC
2876 Add the "mdc" and "mwc" memory commands. These are cyclic 2881 Add the "mdc" and "mwc" memory commands. These are cyclic
2877 "md/mw" commands. 2882 "md/mw" commands.
2878 Examples: 2883 Examples:
2879 2884
2880 => mdc.b 10 4 500 2885 => mdc.b 10 4 500
2881 This command will print 4 bytes (10,11,12,13) each 500 ms. 2886 This command will print 4 bytes (10,11,12,13) each 500 ms.
2882 2887
2883 => mwc.l 100 12345678 10 2888 => mwc.l 100 12345678 10
2884 This command will write 12345678 to address 100 all 10 ms. 2889 This command will write 12345678 to address 100 all 10 ms.
2885 2890
2886 This only takes effect if the memory commands are activated 2891 This only takes effect if the memory commands are activated
2887 globally (CONFIG_CMD_MEM). 2892 globally (CONFIG_CMD_MEM).
2888 2893
2889 - CONFIG_SKIP_LOWLEVEL_INIT 2894 - CONFIG_SKIP_LOWLEVEL_INIT
2890 [ARM only] If this variable is defined, then certain 2895 [ARM only] If this variable is defined, then certain
2891 low level initializations (like setting up the memory 2896 low level initializations (like setting up the memory
2892 controller) are omitted and/or U-Boot does not 2897 controller) are omitted and/or U-Boot does not
2893 relocate itself into RAM. 2898 relocate itself into RAM.
2894 2899
2895 Normally this variable MUST NOT be defined. The only 2900 Normally this variable MUST NOT be defined. The only
2896 exception is when U-Boot is loaded (to RAM) by some 2901 exception is when U-Boot is loaded (to RAM) by some
2897 other boot loader or by a debugger which performs 2902 other boot loader or by a debugger which performs
2898 these initializations itself. 2903 these initializations itself.
2899 2904
2900 - CONFIG_PRELOADER 2905 - CONFIG_PRELOADER
2901 Modifies the behaviour of start.S when compiling a loader 2906 Modifies the behaviour of start.S when compiling a loader
2902 that is executed before the actual U-Boot. E.g. when 2907 that is executed before the actual U-Boot. E.g. when
2903 compiling a NAND SPL. 2908 compiling a NAND SPL.
2904 2909
2905 Building the Software: 2910 Building the Software:
2906 ====================== 2911 ======================
2907 2912
2908 Building U-Boot has been tested in several native build environments 2913 Building U-Boot has been tested in several native build environments
2909 and in many different cross environments. Of course we cannot support 2914 and in many different cross environments. Of course we cannot support
2910 all possibly existing versions of cross development tools in all 2915 all possibly existing versions of cross development tools in all
2911 (potentially obsolete) versions. In case of tool chain problems we 2916 (potentially obsolete) versions. In case of tool chain problems we
2912 recommend to use the ELDK (see http://www.denx.de/wiki/DULG/ELDK) 2917 recommend to use the ELDK (see http://www.denx.de/wiki/DULG/ELDK)
2913 which is extensively used to build and test U-Boot. 2918 which is extensively used to build and test U-Boot.
2914 2919
2915 If you are not using a native environment, it is assumed that you 2920 If you are not using a native environment, it is assumed that you
2916 have GNU cross compiling tools available in your path. In this case, 2921 have GNU cross compiling tools available in your path. In this case,
2917 you must set the environment variable CROSS_COMPILE in your shell. 2922 you must set the environment variable CROSS_COMPILE in your shell.
2918 Note that no changes to the Makefile or any other source files are 2923 Note that no changes to the Makefile or any other source files are
2919 necessary. For example using the ELDK on a 4xx CPU, please enter: 2924 necessary. For example using the ELDK on a 4xx CPU, please enter:
2920 2925
2921 $ CROSS_COMPILE=ppc_4xx- 2926 $ CROSS_COMPILE=ppc_4xx-
2922 $ export CROSS_COMPILE 2927 $ export CROSS_COMPILE
2923 2928
2924 Note: If you wish to generate Windows versions of the utilities in 2929 Note: If you wish to generate Windows versions of the utilities in
2925 the tools directory you can use the MinGW toolchain 2930 the tools directory you can use the MinGW toolchain
2926 (http://www.mingw.org). Set your HOST tools to the MinGW 2931 (http://www.mingw.org). Set your HOST tools to the MinGW
2927 toolchain and execute 'make tools'. For example: 2932 toolchain and execute 'make tools'. For example:
2928 2933
2929 $ make HOSTCC=i586-mingw32msvc-gcc HOSTSTRIP=i586-mingw32msvc-strip tools 2934 $ make HOSTCC=i586-mingw32msvc-gcc HOSTSTRIP=i586-mingw32msvc-strip tools
2930 2935
2931 Binaries such as tools/mkimage.exe will be created which can 2936 Binaries such as tools/mkimage.exe will be created which can
2932 be executed on computers running Windows. 2937 be executed on computers running Windows.
2933 2938
2934 U-Boot is intended to be simple to build. After installing the 2939 U-Boot is intended to be simple to build. After installing the
2935 sources you must configure U-Boot for one specific board type. This 2940 sources you must configure U-Boot for one specific board type. This
2936 is done by typing: 2941 is done by typing:
2937 2942
2938 make NAME_config 2943 make NAME_config
2939 2944
2940 where "NAME_config" is the name of one of the existing configu- 2945 where "NAME_config" is the name of one of the existing configu-
2941 rations; see the main Makefile for supported names. 2946 rations; see the main Makefile for supported names.
2942 2947
2943 Note: for some board special configuration names may exist; check if 2948 Note: for some board special configuration names may exist; check if
2944 additional information is available from the board vendor; for 2949 additional information is available from the board vendor; for
2945 instance, the TQM823L systems are available without (standard) 2950 instance, the TQM823L systems are available without (standard)
2946 or with LCD support. You can select such additional "features" 2951 or with LCD support. You can select such additional "features"
2947 when choosing the configuration, i. e. 2952 when choosing the configuration, i. e.
2948 2953
2949 make TQM823L_config 2954 make TQM823L_config
2950 - will configure for a plain TQM823L, i. e. no LCD support 2955 - will configure for a plain TQM823L, i. e. no LCD support
2951 2956
2952 make TQM823L_LCD_config 2957 make TQM823L_LCD_config
2953 - will configure for a TQM823L with U-Boot console on LCD 2958 - will configure for a TQM823L with U-Boot console on LCD
2954 2959
2955 etc. 2960 etc.
2956 2961
2957 2962
2958 Finally, type "make all", and you should get some working U-Boot 2963 Finally, type "make all", and you should get some working U-Boot
2959 images ready for download to / installation on your system: 2964 images ready for download to / installation on your system:
2960 2965
2961 - "u-boot.bin" is a raw binary image 2966 - "u-boot.bin" is a raw binary image
2962 - "u-boot" is an image in ELF binary format 2967 - "u-boot" is an image in ELF binary format
2963 - "u-boot.srec" is in Motorola S-Record format 2968 - "u-boot.srec" is in Motorola S-Record format
2964 2969
2965 By default the build is performed locally and the objects are saved 2970 By default the build is performed locally and the objects are saved
2966 in the source directory. One of the two methods can be used to change 2971 in the source directory. One of the two methods can be used to change
2967 this behavior and build U-Boot to some external directory: 2972 this behavior and build U-Boot to some external directory:
2968 2973
2969 1. Add O= to the make command line invocations: 2974 1. Add O= to the make command line invocations:
2970 2975
2971 make O=/tmp/build distclean 2976 make O=/tmp/build distclean
2972 make O=/tmp/build NAME_config 2977 make O=/tmp/build NAME_config
2973 make O=/tmp/build all 2978 make O=/tmp/build all
2974 2979
2975 2. Set environment variable BUILD_DIR to point to the desired location: 2980 2. Set environment variable BUILD_DIR to point to the desired location:
2976 2981
2977 export BUILD_DIR=/tmp/build 2982 export BUILD_DIR=/tmp/build
2978 make distclean 2983 make distclean
2979 make NAME_config 2984 make NAME_config
2980 make all 2985 make all
2981 2986
2982 Note that the command line "O=" setting overrides the BUILD_DIR environment 2987 Note that the command line "O=" setting overrides the BUILD_DIR environment
2983 variable. 2988 variable.
2984 2989
2985 2990
2986 Please be aware that the Makefiles assume you are using GNU make, so 2991 Please be aware that the Makefiles assume you are using GNU make, so
2987 for instance on NetBSD you might need to use "gmake" instead of 2992 for instance on NetBSD you might need to use "gmake" instead of
2988 native "make". 2993 native "make".
2989 2994
2990 2995
2991 If the system board that you have is not listed, then you will need 2996 If the system board that you have is not listed, then you will need
2992 to port U-Boot to your hardware platform. To do this, follow these 2997 to port U-Boot to your hardware platform. To do this, follow these
2993 steps: 2998 steps:
2994 2999
2995 1. Add a new configuration option for your board to the toplevel 3000 1. Add a new configuration option for your board to the toplevel
2996 "Makefile" and to the "MAKEALL" script, using the existing 3001 "Makefile" and to the "MAKEALL" script, using the existing
2997 entries as examples. Note that here and at many other places 3002 entries as examples. Note that here and at many other places
2998 boards and other names are listed in alphabetical sort order. Please 3003 boards and other names are listed in alphabetical sort order. Please
2999 keep this order. 3004 keep this order.
3000 2. Create a new directory to hold your board specific code. Add any 3005 2. Create a new directory to hold your board specific code. Add any
3001 files you need. In your board directory, you will need at least 3006 files you need. In your board directory, you will need at least
3002 the "Makefile", a "<board>.c", "flash.c" and "u-boot.lds". 3007 the "Makefile", a "<board>.c", "flash.c" and "u-boot.lds".
3003 3. Create a new configuration file "include/configs/<board>.h" for 3008 3. Create a new configuration file "include/configs/<board>.h" for
3004 your board 3009 your board
3005 3. If you're porting U-Boot to a new CPU, then also create a new 3010 3. If you're porting U-Boot to a new CPU, then also create a new
3006 directory to hold your CPU specific code. Add any files you need. 3011 directory to hold your CPU specific code. Add any files you need.
3007 4. Run "make <board>_config" with your new name. 3012 4. Run "make <board>_config" with your new name.
3008 5. Type "make", and you should get a working "u-boot.srec" file 3013 5. Type "make", and you should get a working "u-boot.srec" file
3009 to be installed on your target system. 3014 to be installed on your target system.
3010 6. Debug and solve any problems that might arise. 3015 6. Debug and solve any problems that might arise.
3011 [Of course, this last step is much harder than it sounds.] 3016 [Of course, this last step is much harder than it sounds.]
3012 3017
3013 3018
3014 Testing of U-Boot Modifications, Ports to New Hardware, etc.: 3019 Testing of U-Boot Modifications, Ports to New Hardware, etc.:
3015 ============================================================== 3020 ==============================================================
3016 3021
3017 If you have modified U-Boot sources (for instance added a new board 3022 If you have modified U-Boot sources (for instance added a new board
3018 or support for new devices, a new CPU, etc.) you are expected to 3023 or support for new devices, a new CPU, etc.) you are expected to
3019 provide feedback to the other developers. The feedback normally takes 3024 provide feedback to the other developers. The feedback normally takes
3020 the form of a "patch", i. e. a context diff against a certain (latest 3025 the form of a "patch", i. e. a context diff against a certain (latest
3021 official or latest in the git repository) version of U-Boot sources. 3026 official or latest in the git repository) version of U-Boot sources.
3022 3027
3023 But before you submit such a patch, please verify that your modifi- 3028 But before you submit such a patch, please verify that your modifi-
3024 cation did not break existing code. At least make sure that *ALL* of 3029 cation did not break existing code. At least make sure that *ALL* of
3025 the supported boards compile WITHOUT ANY compiler warnings. To do so, 3030 the supported boards compile WITHOUT ANY compiler warnings. To do so,
3026 just run the "MAKEALL" script, which will configure and build U-Boot 3031 just run the "MAKEALL" script, which will configure and build U-Boot
3027 for ALL supported system. Be warned, this will take a while. You can 3032 for ALL supported system. Be warned, this will take a while. You can
3028 select which (cross) compiler to use by passing a `CROSS_COMPILE' 3033 select which (cross) compiler to use by passing a `CROSS_COMPILE'
3029 environment variable to the script, i. e. to use the ELDK cross tools 3034 environment variable to the script, i. e. to use the ELDK cross tools
3030 you can type 3035 you can type
3031 3036
3032 CROSS_COMPILE=ppc_8xx- MAKEALL 3037 CROSS_COMPILE=ppc_8xx- MAKEALL
3033 3038
3034 or to build on a native PowerPC system you can type 3039 or to build on a native PowerPC system you can type
3035 3040
3036 CROSS_COMPILE=' ' MAKEALL 3041 CROSS_COMPILE=' ' MAKEALL
3037 3042
3038 When using the MAKEALL script, the default behaviour is to build 3043 When using the MAKEALL script, the default behaviour is to build
3039 U-Boot in the source directory. This location can be changed by 3044 U-Boot in the source directory. This location can be changed by
3040 setting the BUILD_DIR environment variable. Also, for each target 3045 setting the BUILD_DIR environment variable. Also, for each target
3041 built, the MAKEALL script saves two log files (<target>.ERR and 3046 built, the MAKEALL script saves two log files (<target>.ERR and
3042 <target>.MAKEALL) in the <source dir>/LOG directory. This default 3047 <target>.MAKEALL) in the <source dir>/LOG directory. This default
3043 location can be changed by setting the MAKEALL_LOGDIR environment 3048 location can be changed by setting the MAKEALL_LOGDIR environment
3044 variable. For example: 3049 variable. For example:
3045 3050
3046 export BUILD_DIR=/tmp/build 3051 export BUILD_DIR=/tmp/build
3047 export MAKEALL_LOGDIR=/tmp/log 3052 export MAKEALL_LOGDIR=/tmp/log
3048 CROSS_COMPILE=ppc_8xx- MAKEALL 3053 CROSS_COMPILE=ppc_8xx- MAKEALL
3049 3054
3050 With the above settings build objects are saved in the /tmp/build, 3055 With the above settings build objects are saved in the /tmp/build,
3051 log files are saved in the /tmp/log and the source tree remains clean 3056 log files are saved in the /tmp/log and the source tree remains clean
3052 during the whole build process. 3057 during the whole build process.
3053 3058
3054 3059
3055 See also "U-Boot Porting Guide" below. 3060 See also "U-Boot Porting Guide" below.
3056 3061
3057 3062
3058 Monitor Commands - Overview: 3063 Monitor Commands - Overview:
3059 ============================ 3064 ============================
3060 3065
3061 go - start application at address 'addr' 3066 go - start application at address 'addr'
3062 run - run commands in an environment variable 3067 run - run commands in an environment variable
3063 bootm - boot application image from memory 3068 bootm - boot application image from memory
3064 bootp - boot image via network using BootP/TFTP protocol 3069 bootp - boot image via network using BootP/TFTP protocol
3065 tftpboot- boot image via network using TFTP protocol 3070 tftpboot- boot image via network using TFTP protocol
3066 and env variables "ipaddr" and "serverip" 3071 and env variables "ipaddr" and "serverip"
3067 (and eventually "gatewayip") 3072 (and eventually "gatewayip")
3068 rarpboot- boot image via network using RARP/TFTP protocol 3073 rarpboot- boot image via network using RARP/TFTP protocol
3069 diskboot- boot from IDE devicebootd - boot default, i.e., run 'bootcmd' 3074 diskboot- boot from IDE devicebootd - boot default, i.e., run 'bootcmd'
3070 loads - load S-Record file over serial line 3075 loads - load S-Record file over serial line
3071 loadb - load binary file over serial line (kermit mode) 3076 loadb - load binary file over serial line (kermit mode)
3072 md - memory display 3077 md - memory display
3073 mm - memory modify (auto-incrementing) 3078 mm - memory modify (auto-incrementing)
3074 nm - memory modify (constant address) 3079 nm - memory modify (constant address)
3075 mw - memory write (fill) 3080 mw - memory write (fill)
3076 cp - memory copy 3081 cp - memory copy
3077 cmp - memory compare 3082 cmp - memory compare
3078 crc32 - checksum calculation 3083 crc32 - checksum calculation
3079 i2c - I2C sub-system 3084 i2c - I2C sub-system
3080 sspi - SPI utility commands 3085 sspi - SPI utility commands
3081 base - print or set address offset 3086 base - print or set address offset
3082 printenv- print environment variables 3087 printenv- print environment variables
3083 setenv - set environment variables 3088 setenv - set environment variables
3084 saveenv - save environment variables to persistent storage 3089 saveenv - save environment variables to persistent storage
3085 protect - enable or disable FLASH write protection 3090 protect - enable or disable FLASH write protection
3086 erase - erase FLASH memory 3091 erase - erase FLASH memory
3087 flinfo - print FLASH memory information 3092 flinfo - print FLASH memory information
3088 bdinfo - print Board Info structure 3093 bdinfo - print Board Info structure
3089 iminfo - print header information for application image 3094 iminfo - print header information for application image
3090 coninfo - print console devices and informations 3095 coninfo - print console devices and informations
3091 ide - IDE sub-system 3096 ide - IDE sub-system
3092 loop - infinite loop on address range 3097 loop - infinite loop on address range
3093 loopw - infinite write loop on address range 3098 loopw - infinite write loop on address range
3094 mtest - simple RAM test 3099 mtest - simple RAM test
3095 icache - enable or disable instruction cache 3100 icache - enable or disable instruction cache
3096 dcache - enable or disable data cache 3101 dcache - enable or disable data cache
3097 reset - Perform RESET of the CPU 3102 reset - Perform RESET of the CPU
3098 echo - echo args to console 3103 echo - echo args to console
3099 version - print monitor version 3104 version - print monitor version
3100 help - print online help 3105 help - print online help
3101 ? - alias for 'help' 3106 ? - alias for 'help'
3102 3107
3103 3108
3104 Monitor Commands - Detailed Description: 3109 Monitor Commands - Detailed Description:
3105 ======================================== 3110 ========================================
3106 3111
3107 TODO. 3112 TODO.
3108 3113
3109 For now: just type "help <command>". 3114 For now: just type "help <command>".
3110 3115
3111 3116
3112 Environment Variables: 3117 Environment Variables:
3113 ====================== 3118 ======================
3114 3119
3115 U-Boot supports user configuration using Environment Variables which 3120 U-Boot supports user configuration using Environment Variables which
3116 can be made persistent by saving to Flash memory. 3121 can be made persistent by saving to Flash memory.
3117 3122
3118 Environment Variables are set using "setenv", printed using 3123 Environment Variables are set using "setenv", printed using
3119 "printenv", and saved to Flash using "saveenv". Using "setenv" 3124 "printenv", and saved to Flash using "saveenv". Using "setenv"
3120 without a value can be used to delete a variable from the 3125 without a value can be used to delete a variable from the
3121 environment. As long as you don't save the environment you are 3126 environment. As long as you don't save the environment you are
3122 working with an in-memory copy. In case the Flash area containing the 3127 working with an in-memory copy. In case the Flash area containing the
3123 environment is erased by accident, a default environment is provided. 3128 environment is erased by accident, a default environment is provided.
3124 3129
3125 Some configuration options can be set using Environment Variables. 3130 Some configuration options can be set using Environment Variables.
3126 3131
3127 List of environment variables (most likely not complete): 3132 List of environment variables (most likely not complete):
3128 3133
3129 baudrate - see CONFIG_BAUDRATE 3134 baudrate - see CONFIG_BAUDRATE
3130 3135
3131 bootdelay - see CONFIG_BOOTDELAY 3136 bootdelay - see CONFIG_BOOTDELAY
3132 3137
3133 bootcmd - see CONFIG_BOOTCOMMAND 3138 bootcmd - see CONFIG_BOOTCOMMAND
3134 3139
3135 bootargs - Boot arguments when booting an RTOS image 3140 bootargs - Boot arguments when booting an RTOS image
3136 3141
3137 bootfile - Name of the image to load with TFTP 3142 bootfile - Name of the image to load with TFTP
3138 3143
3139 bootm_low - Memory range available for image processing in the bootm 3144 bootm_low - Memory range available for image processing in the bootm
3140 command can be restricted. This variable is given as 3145 command can be restricted. This variable is given as
3141 a hexadecimal number and defines lowest address allowed 3146 a hexadecimal number and defines lowest address allowed
3142 for use by the bootm command. See also "bootm_size" 3147 for use by the bootm command. See also "bootm_size"
3143 environment variable. Address defined by "bootm_low" is 3148 environment variable. Address defined by "bootm_low" is
3144 also the base of the initial memory mapping for the Linux 3149 also the base of the initial memory mapping for the Linux
3145 kernel -- see the description of CONFIG_SYS_BOOTMAPSZ. 3150 kernel -- see the description of CONFIG_SYS_BOOTMAPSZ.
3146 3151
3147 bootm_size - Memory range available for image processing in the bootm 3152 bootm_size - Memory range available for image processing in the bootm
3148 command can be restricted. This variable is given as 3153 command can be restricted. This variable is given as
3149 a hexadecimal number and defines the size of the region 3154 a hexadecimal number and defines the size of the region
3150 allowed for use by the bootm command. See also "bootm_low" 3155 allowed for use by the bootm command. See also "bootm_low"
3151 environment variable. 3156 environment variable.
3152 3157
3153 updatefile - Location of the software update file on a TFTP server, used 3158 updatefile - Location of the software update file on a TFTP server, used
3154 by the automatic software update feature. Please refer to 3159 by the automatic software update feature. Please refer to
3155 documentation in doc/README.update for more details. 3160 documentation in doc/README.update for more details.
3156 3161
3157 autoload - if set to "no" (any string beginning with 'n'), 3162 autoload - if set to "no" (any string beginning with 'n'),
3158 "bootp" will just load perform a lookup of the 3163 "bootp" will just load perform a lookup of the
3159 configuration from the BOOTP server, but not try to 3164 configuration from the BOOTP server, but not try to
3160 load any image using TFTP 3165 load any image using TFTP
3161 3166
3162 autostart - if set to "yes", an image loaded using the "bootp", 3167 autostart - if set to "yes", an image loaded using the "bootp",
3163 "rarpboot", "tftpboot" or "diskboot" commands will 3168 "rarpboot", "tftpboot" or "diskboot" commands will
3164 be automatically started (by internally calling 3169 be automatically started (by internally calling
3165 "bootm") 3170 "bootm")
3166 3171
3167 If set to "no", a standalone image passed to the 3172 If set to "no", a standalone image passed to the
3168 "bootm" command will be copied to the load address 3173 "bootm" command will be copied to the load address
3169 (and eventually uncompressed), but NOT be started. 3174 (and eventually uncompressed), but NOT be started.
3170 This can be used to load and uncompress arbitrary 3175 This can be used to load and uncompress arbitrary
3171 data. 3176 data.
3172 3177
3173 i2cfast - (PPC405GP|PPC405EP only) 3178 i2cfast - (PPC405GP|PPC405EP only)
3174 if set to 'y' configures Linux I2C driver for fast 3179 if set to 'y' configures Linux I2C driver for fast
3175 mode (400kHZ). This environment variable is used in 3180 mode (400kHZ). This environment variable is used in
3176 initialization code. So, for changes to be effective 3181 initialization code. So, for changes to be effective
3177 it must be saved and board must be reset. 3182 it must be saved and board must be reset.
3178 3183
3179 initrd_high - restrict positioning of initrd images: 3184 initrd_high - restrict positioning of initrd images:
3180 If this variable is not set, initrd images will be 3185 If this variable is not set, initrd images will be
3181 copied to the highest possible address in RAM; this 3186 copied to the highest possible address in RAM; this
3182 is usually what you want since it allows for 3187 is usually what you want since it allows for
3183 maximum initrd size. If for some reason you want to 3188 maximum initrd size. If for some reason you want to
3184 make sure that the initrd image is loaded below the 3189 make sure that the initrd image is loaded below the
3185 CONFIG_SYS_BOOTMAPSZ limit, you can set this environment 3190 CONFIG_SYS_BOOTMAPSZ limit, you can set this environment
3186 variable to a value of "no" or "off" or "0". 3191 variable to a value of "no" or "off" or "0".
3187 Alternatively, you can set it to a maximum upper 3192 Alternatively, you can set it to a maximum upper
3188 address to use (U-Boot will still check that it 3193 address to use (U-Boot will still check that it
3189 does not overwrite the U-Boot stack and data). 3194 does not overwrite the U-Boot stack and data).
3190 3195
3191 For instance, when you have a system with 16 MB 3196 For instance, when you have a system with 16 MB
3192 RAM, and want to reserve 4 MB from use by Linux, 3197 RAM, and want to reserve 4 MB from use by Linux,
3193 you can do this by adding "mem=12M" to the value of 3198 you can do this by adding "mem=12M" to the value of
3194 the "bootargs" variable. However, now you must make 3199 the "bootargs" variable. However, now you must make
3195 sure that the initrd image is placed in the first 3200 sure that the initrd image is placed in the first
3196 12 MB as well - this can be done with 3201 12 MB as well - this can be done with
3197 3202
3198 setenv initrd_high 00c00000 3203 setenv initrd_high 00c00000
3199 3204
3200 If you set initrd_high to 0xFFFFFFFF, this is an 3205 If you set initrd_high to 0xFFFFFFFF, this is an
3201 indication to U-Boot that all addresses are legal 3206 indication to U-Boot that all addresses are legal
3202 for the Linux kernel, including addresses in flash 3207 for the Linux kernel, including addresses in flash
3203 memory. In this case U-Boot will NOT COPY the 3208 memory. In this case U-Boot will NOT COPY the
3204 ramdisk at all. This may be useful to reduce the 3209 ramdisk at all. This may be useful to reduce the
3205 boot time on your system, but requires that this 3210 boot time on your system, but requires that this
3206 feature is supported by your Linux kernel. 3211 feature is supported by your Linux kernel.
3207 3212
3208 ipaddr - IP address; needed for tftpboot command 3213 ipaddr - IP address; needed for tftpboot command
3209 3214
3210 loadaddr - Default load address for commands like "bootp", 3215 loadaddr - Default load address for commands like "bootp",
3211 "rarpboot", "tftpboot", "loadb" or "diskboot" 3216 "rarpboot", "tftpboot", "loadb" or "diskboot"
3212 3217
3213 loads_echo - see CONFIG_LOADS_ECHO 3218 loads_echo - see CONFIG_LOADS_ECHO
3214 3219
3215 serverip - TFTP server IP address; needed for tftpboot command 3220 serverip - TFTP server IP address; needed for tftpboot command
3216 3221
3217 bootretry - see CONFIG_BOOT_RETRY_TIME 3222 bootretry - see CONFIG_BOOT_RETRY_TIME
3218 3223
3219 bootdelaykey - see CONFIG_AUTOBOOT_DELAY_STR 3224 bootdelaykey - see CONFIG_AUTOBOOT_DELAY_STR
3220 3225
3221 bootstopkey - see CONFIG_AUTOBOOT_STOP_STR 3226 bootstopkey - see CONFIG_AUTOBOOT_STOP_STR
3222 3227
3223 ethprime - When CONFIG_NET_MULTI is enabled controls which 3228 ethprime - When CONFIG_NET_MULTI is enabled controls which
3224 interface is used first. 3229 interface is used first.
3225 3230
3226 ethact - When CONFIG_NET_MULTI is enabled controls which 3231 ethact - When CONFIG_NET_MULTI is enabled controls which
3227 interface is currently active. For example you 3232 interface is currently active. For example you
3228 can do the following 3233 can do the following
3229 3234
3230 => setenv ethact FEC 3235 => setenv ethact FEC
3231 => ping 192.168.0.1 # traffic sent on FEC 3236 => ping 192.168.0.1 # traffic sent on FEC
3232 => setenv ethact SCC 3237 => setenv ethact SCC
3233 => ping 10.0.0.1 # traffic sent on SCC 3238 => ping 10.0.0.1 # traffic sent on SCC
3234 3239
3235 ethrotate - When set to "no" U-Boot does not go through all 3240 ethrotate - When set to "no" U-Boot does not go through all
3236 available network interfaces. 3241 available network interfaces.
3237 It just stays at the currently selected interface. 3242 It just stays at the currently selected interface.
3238 3243
3239 netretry - When set to "no" each network operation will 3244 netretry - When set to "no" each network operation will
3240 either succeed or fail without retrying. 3245 either succeed or fail without retrying.
3241 When set to "once" the network operation will 3246 When set to "once" the network operation will
3242 fail when all the available network interfaces 3247 fail when all the available network interfaces
3243 are tried once without success. 3248 are tried once without success.
3244 Useful on scripts which control the retry operation 3249 Useful on scripts which control the retry operation
3245 themselves. 3250 themselves.
3246 3251
3247 npe_ucode - set load address for the NPE microcode 3252 npe_ucode - set load address for the NPE microcode
3248 3253
3249 tftpsrcport - If this is set, the value is used for TFTP's 3254 tftpsrcport - If this is set, the value is used for TFTP's
3250 UDP source port. 3255 UDP source port.
3251 3256
3252 tftpdstport - If this is set, the value is used for TFTP's UDP 3257 tftpdstport - If this is set, the value is used for TFTP's UDP
3253 destination port instead of the Well Know Port 69. 3258 destination port instead of the Well Know Port 69.
3254 3259
3255 tftpblocksize - Block size to use for TFTP transfers; if not set, 3260 tftpblocksize - Block size to use for TFTP transfers; if not set,
3256 we use the TFTP server's default block size 3261 we use the TFTP server's default block size
3257 3262
3258 tftptimeout - Retransmission timeout for TFTP packets (in milli- 3263 tftptimeout - Retransmission timeout for TFTP packets (in milli-
3259 seconds, minimum value is 1000 = 1 second). Defines 3264 seconds, minimum value is 1000 = 1 second). Defines
3260 when a packet is considered to be lost so it has to 3265 when a packet is considered to be lost so it has to
3261 be retransmitted. The default is 5000 = 5 seconds. 3266 be retransmitted. The default is 5000 = 5 seconds.
3262 Lowering this value may make downloads succeed 3267 Lowering this value may make downloads succeed
3263 faster in networks with high packet loss rates or 3268 faster in networks with high packet loss rates or
3264 with unreliable TFTP servers. 3269 with unreliable TFTP servers.
3265 3270
3266 vlan - When set to a value < 4095 the traffic over 3271 vlan - When set to a value < 4095 the traffic over
3267 Ethernet is encapsulated/received over 802.1q 3272 Ethernet is encapsulated/received over 802.1q
3268 VLAN tagged frames. 3273 VLAN tagged frames.
3269 3274
3270 The following environment variables may be used and automatically 3275 The following environment variables may be used and automatically
3271 updated by the network boot commands ("bootp" and "rarpboot"), 3276 updated by the network boot commands ("bootp" and "rarpboot"),
3272 depending the information provided by your boot server: 3277 depending the information provided by your boot server:
3273 3278
3274 bootfile - see above 3279 bootfile - see above
3275 dnsip - IP address of your Domain Name Server 3280 dnsip - IP address of your Domain Name Server
3276 dnsip2 - IP address of your secondary Domain Name Server 3281 dnsip2 - IP address of your secondary Domain Name Server
3277 gatewayip - IP address of the Gateway (Router) to use 3282 gatewayip - IP address of the Gateway (Router) to use
3278 hostname - Target hostname 3283 hostname - Target hostname
3279 ipaddr - see above 3284 ipaddr - see above
3280 netmask - Subnet Mask 3285 netmask - Subnet Mask
3281 rootpath - Pathname of the root filesystem on the NFS server 3286 rootpath - Pathname of the root filesystem on the NFS server
3282 serverip - see above 3287 serverip - see above
3283 3288
3284 3289
3285 There are two special Environment Variables: 3290 There are two special Environment Variables:
3286 3291
3287 serial# - contains hardware identification information such 3292 serial# - contains hardware identification information such
3288 as type string and/or serial number 3293 as type string and/or serial number
3289 ethaddr - Ethernet address 3294 ethaddr - Ethernet address
3290 3295
3291 These variables can be set only once (usually during manufacturing of 3296 These variables can be set only once (usually during manufacturing of
3292 the board). U-Boot refuses to delete or overwrite these variables 3297 the board). U-Boot refuses to delete or overwrite these variables
3293 once they have been set once. 3298 once they have been set once.
3294 3299
3295 3300
3296 Further special Environment Variables: 3301 Further special Environment Variables:
3297 3302
3298 ver - Contains the U-Boot version string as printed 3303 ver - Contains the U-Boot version string as printed
3299 with the "version" command. This variable is 3304 with the "version" command. This variable is
3300 readonly (see CONFIG_VERSION_VARIABLE). 3305 readonly (see CONFIG_VERSION_VARIABLE).
3301 3306
3302 3307
3303 Please note that changes to some configuration parameters may take 3308 Please note that changes to some configuration parameters may take
3304 only effect after the next boot (yes, that's just like Windoze :-). 3309 only effect after the next boot (yes, that's just like Windoze :-).
3305 3310
3306 3311
3307 Command Line Parsing: 3312 Command Line Parsing:
3308 ===================== 3313 =====================
3309 3314
3310 There are two different command line parsers available with U-Boot: 3315 There are two different command line parsers available with U-Boot:
3311 the old "simple" one, and the much more powerful "hush" shell: 3316 the old "simple" one, and the much more powerful "hush" shell:
3312 3317
3313 Old, simple command line parser: 3318 Old, simple command line parser:
3314 -------------------------------- 3319 --------------------------------
3315 3320
3316 - supports environment variables (through setenv / saveenv commands) 3321 - supports environment variables (through setenv / saveenv commands)
3317 - several commands on one line, separated by ';' 3322 - several commands on one line, separated by ';'
3318 - variable substitution using "... ${name} ..." syntax 3323 - variable substitution using "... ${name} ..." syntax
3319 - special characters ('$', ';') can be escaped by prefixing with '\', 3324 - special characters ('$', ';') can be escaped by prefixing with '\',
3320 for example: 3325 for example:
3321 setenv bootcmd bootm \${address} 3326 setenv bootcmd bootm \${address}
3322 - You can also escape text by enclosing in single apostrophes, for example: 3327 - You can also escape text by enclosing in single apostrophes, for example:
3323 setenv addip 'setenv bootargs $bootargs ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname::off' 3328 setenv addip 'setenv bootargs $bootargs ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname::off'
3324 3329
3325 Hush shell: 3330 Hush shell:
3326 ----------- 3331 -----------
3327 3332
3328 - similar to Bourne shell, with control structures like 3333 - similar to Bourne shell, with control structures like
3329 if...then...else...fi, for...do...done; while...do...done, 3334 if...then...else...fi, for...do...done; while...do...done,
3330 until...do...done, ... 3335 until...do...done, ...
3331 - supports environment ("global") variables (through setenv / saveenv 3336 - supports environment ("global") variables (through setenv / saveenv
3332 commands) and local shell variables (through standard shell syntax 3337 commands) and local shell variables (through standard shell syntax
3333 "name=value"); only environment variables can be used with "run" 3338 "name=value"); only environment variables can be used with "run"
3334 command 3339 command
3335 3340
3336 General rules: 3341 General rules:
3337 -------------- 3342 --------------
3338 3343
3339 (1) If a command line (or an environment variable executed by a "run" 3344 (1) If a command line (or an environment variable executed by a "run"
3340 command) contains several commands separated by semicolon, and 3345 command) contains several commands separated by semicolon, and
3341 one of these commands fails, then the remaining commands will be 3346 one of these commands fails, then the remaining commands will be
3342 executed anyway. 3347 executed anyway.
3343 3348
3344 (2) If you execute several variables with one call to run (i. e. 3349 (2) If you execute several variables with one call to run (i. e.
3345 calling run with a list of variables as arguments), any failing 3350 calling run with a list of variables as arguments), any failing
3346 command will cause "run" to terminate, i. e. the remaining 3351 command will cause "run" to terminate, i. e. the remaining
3347 variables are not executed. 3352 variables are not executed.
3348 3353
3349 Note for Redundant Ethernet Interfaces: 3354 Note for Redundant Ethernet Interfaces:
3350 ======================================= 3355 =======================================
3351 3356
3352 Some boards come with redundant Ethernet interfaces; U-Boot supports 3357 Some boards come with redundant Ethernet interfaces; U-Boot supports
3353 such configurations and is capable of automatic selection of a 3358 such configurations and is capable of automatic selection of a
3354 "working" interface when needed. MAC assignment works as follows: 3359 "working" interface when needed. MAC assignment works as follows:
3355 3360
3356 Network interfaces are numbered eth0, eth1, eth2, ... Corresponding 3361 Network interfaces are numbered eth0, eth1, eth2, ... Corresponding
3357 MAC addresses can be stored in the environment as "ethaddr" (=>eth0), 3362 MAC addresses can be stored in the environment as "ethaddr" (=>eth0),
3358 "eth1addr" (=>eth1), "eth2addr", ... 3363 "eth1addr" (=>eth1), "eth2addr", ...
3359 3364
3360 If the network interface stores some valid MAC address (for instance 3365 If the network interface stores some valid MAC address (for instance
3361 in SROM), this is used as default address if there is NO correspon- 3366 in SROM), this is used as default address if there is NO correspon-
3362 ding setting in the environment; if the corresponding environment 3367 ding setting in the environment; if the corresponding environment
3363 variable is set, this overrides the settings in the card; that means: 3368 variable is set, this overrides the settings in the card; that means:
3364 3369
3365 o If the SROM has a valid MAC address, and there is no address in the 3370 o If the SROM has a valid MAC address, and there is no address in the
3366 environment, the SROM's address is used. 3371 environment, the SROM's address is used.
3367 3372
3368 o If there is no valid address in the SROM, and a definition in the 3373 o If there is no valid address in the SROM, and a definition in the
3369 environment exists, then the value from the environment variable is 3374 environment exists, then the value from the environment variable is
3370 used. 3375 used.
3371 3376
3372 o If both the SROM and the environment contain a MAC address, and 3377 o If both the SROM and the environment contain a MAC address, and
3373 both addresses are the same, this MAC address is used. 3378 both addresses are the same, this MAC address is used.
3374 3379
3375 o If both the SROM and the environment contain a MAC address, and the 3380 o If both the SROM and the environment contain a MAC address, and the
3376 addresses differ, the value from the environment is used and a 3381 addresses differ, the value from the environment is used and a
3377 warning is printed. 3382 warning is printed.
3378 3383
3379 o If neither SROM nor the environment contain a MAC address, an error 3384 o If neither SROM nor the environment contain a MAC address, an error
3380 is raised. 3385 is raised.
3381 3386
3382 If Ethernet drivers implement the 'write_hwaddr' function, valid MAC addresses 3387 If Ethernet drivers implement the 'write_hwaddr' function, valid MAC addresses
3383 will be programmed into hardware as part of the initialization process. This 3388 will be programmed into hardware as part of the initialization process. This
3384 may be skipped by setting the appropriate 'ethmacskip' environment variable. 3389 may be skipped by setting the appropriate 'ethmacskip' environment variable.
3385 The naming convention is as follows: 3390 The naming convention is as follows:
3386 "ethmacskip" (=>eth0), "eth1macskip" (=>eth1) etc. 3391 "ethmacskip" (=>eth0), "eth1macskip" (=>eth1) etc.
3387 3392
3388 Image Formats: 3393 Image Formats:
3389 ============== 3394 ==============
3390 3395
3391 U-Boot is capable of booting (and performing other auxiliary operations on) 3396 U-Boot is capable of booting (and performing other auxiliary operations on)
3392 images in two formats: 3397 images in two formats:
3393 3398
3394 New uImage format (FIT) 3399 New uImage format (FIT)
3395 ----------------------- 3400 -----------------------
3396 3401
3397 Flexible and powerful format based on Flattened Image Tree -- FIT (similar 3402 Flexible and powerful format based on Flattened Image Tree -- FIT (similar
3398 to Flattened Device Tree). It allows the use of images with multiple 3403 to Flattened Device Tree). It allows the use of images with multiple
3399 components (several kernels, ramdisks, etc.), with contents protected by 3404 components (several kernels, ramdisks, etc.), with contents protected by
3400 SHA1, MD5 or CRC32. More details are found in the doc/uImage.FIT directory. 3405 SHA1, MD5 or CRC32. More details are found in the doc/uImage.FIT directory.
3401 3406
3402 3407
3403 Old uImage format 3408 Old uImage format
3404 ----------------- 3409 -----------------
3405 3410
3406 Old image format is based on binary files which can be basically anything, 3411 Old image format is based on binary files which can be basically anything,
3407 preceded by a special header; see the definitions in include/image.h for 3412 preceded by a special header; see the definitions in include/image.h for
3408 details; basically, the header defines the following image properties: 3413 details; basically, the header defines the following image properties:
3409 3414
3410 * Target Operating System (Provisions for OpenBSD, NetBSD, FreeBSD, 3415 * Target Operating System (Provisions for OpenBSD, NetBSD, FreeBSD,
3411 4.4BSD, Linux, SVR4, Esix, Solaris, Irix, SCO, Dell, NCR, VxWorks, 3416 4.4BSD, Linux, SVR4, Esix, Solaris, Irix, SCO, Dell, NCR, VxWorks,
3412 LynxOS, pSOS, QNX, RTEMS, INTEGRITY; 3417 LynxOS, pSOS, QNX, RTEMS, INTEGRITY;
3413 Currently supported: Linux, NetBSD, VxWorks, QNX, RTEMS, LynxOS, 3418 Currently supported: Linux, NetBSD, VxWorks, QNX, RTEMS, LynxOS,
3414 INTEGRITY). 3419 INTEGRITY).
3415 * Target CPU Architecture (Provisions for Alpha, ARM, AVR32, Intel x86, 3420 * Target CPU Architecture (Provisions for Alpha, ARM, AVR32, Intel x86,
3416 IA64, MIPS, Nios II, PowerPC, IBM S390, SuperH, Sparc, Sparc 64 Bit; 3421 IA64, MIPS, Nios II, PowerPC, IBM S390, SuperH, Sparc, Sparc 64 Bit;
3417 Currently supported: ARM, AVR32, Intel x86, MIPS, Nios II, PowerPC). 3422 Currently supported: ARM, AVR32, Intel x86, MIPS, Nios II, PowerPC).
3418 * Compression Type (uncompressed, gzip, bzip2) 3423 * Compression Type (uncompressed, gzip, bzip2)
3419 * Load Address 3424 * Load Address
3420 * Entry Point 3425 * Entry Point
3421 * Image Name 3426 * Image Name
3422 * Image Timestamp 3427 * Image Timestamp
3423 3428
3424 The header is marked by a special Magic Number, and both the header 3429 The header is marked by a special Magic Number, and both the header
3425 and the data portions of the image are secured against corruption by 3430 and the data portions of the image are secured against corruption by
3426 CRC32 checksums. 3431 CRC32 checksums.
3427 3432
3428 3433
3429 Linux Support: 3434 Linux Support:
3430 ============== 3435 ==============
3431 3436
3432 Although U-Boot should support any OS or standalone application 3437 Although U-Boot should support any OS or standalone application
3433 easily, the main focus has always been on Linux during the design of 3438 easily, the main focus has always been on Linux during the design of
3434 U-Boot. 3439 U-Boot.
3435 3440
3436 U-Boot includes many features that so far have been part of some 3441 U-Boot includes many features that so far have been part of some
3437 special "boot loader" code within the Linux kernel. Also, any 3442 special "boot loader" code within the Linux kernel. Also, any
3438 "initrd" images to be used are no longer part of one big Linux image; 3443 "initrd" images to be used are no longer part of one big Linux image;
3439 instead, kernel and "initrd" are separate images. This implementation 3444 instead, kernel and "initrd" are separate images. This implementation
3440 serves several purposes: 3445 serves several purposes:
3441 3446
3442 - the same features can be used for other OS or standalone 3447 - the same features can be used for other OS or standalone
3443 applications (for instance: using compressed images to reduce the 3448 applications (for instance: using compressed images to reduce the
3444 Flash memory footprint) 3449 Flash memory footprint)
3445 3450
3446 - it becomes much easier to port new Linux kernel versions because 3451 - it becomes much easier to port new Linux kernel versions because
3447 lots of low-level, hardware dependent stuff are done by U-Boot 3452 lots of low-level, hardware dependent stuff are done by U-Boot
3448 3453
3449 - the same Linux kernel image can now be used with different "initrd" 3454 - the same Linux kernel image can now be used with different "initrd"
3450 images; of course this also means that different kernel images can 3455 images; of course this also means that different kernel images can
3451 be run with the same "initrd". This makes testing easier (you don't 3456 be run with the same "initrd". This makes testing easier (you don't
3452 have to build a new "zImage.initrd" Linux image when you just 3457 have to build a new "zImage.initrd" Linux image when you just
3453 change a file in your "initrd"). Also, a field-upgrade of the 3458 change a file in your "initrd"). Also, a field-upgrade of the
3454 software is easier now. 3459 software is easier now.
3455 3460
3456 3461
3457 Linux HOWTO: 3462 Linux HOWTO:
3458 ============ 3463 ============
3459 3464
3460 Porting Linux to U-Boot based systems: 3465 Porting Linux to U-Boot based systems:
3461 --------------------------------------- 3466 ---------------------------------------
3462 3467
3463 U-Boot cannot save you from doing all the necessary modifications to 3468 U-Boot cannot save you from doing all the necessary modifications to
3464 configure the Linux device drivers for use with your target hardware 3469 configure the Linux device drivers for use with your target hardware
3465 (no, we don't intend to provide a full virtual machine interface to 3470 (no, we don't intend to provide a full virtual machine interface to
3466 Linux :-). 3471 Linux :-).
3467 3472
3468 But now you can ignore ALL boot loader code (in arch/powerpc/mbxboot). 3473 But now you can ignore ALL boot loader code (in arch/powerpc/mbxboot).
3469 3474
3470 Just make sure your machine specific header file (for instance 3475 Just make sure your machine specific header file (for instance
3471 include/asm-ppc/tqm8xx.h) includes the same definition of the Board 3476 include/asm-ppc/tqm8xx.h) includes the same definition of the Board
3472 Information structure as we define in include/asm-<arch>/u-boot.h, 3477 Information structure as we define in include/asm-<arch>/u-boot.h,
3473 and make sure that your definition of IMAP_ADDR uses the same value 3478 and make sure that your definition of IMAP_ADDR uses the same value
3474 as your U-Boot configuration in CONFIG_SYS_IMMR. 3479 as your U-Boot configuration in CONFIG_SYS_IMMR.
3475 3480
3476 3481
3477 Configuring the Linux kernel: 3482 Configuring the Linux kernel:
3478 ----------------------------- 3483 -----------------------------
3479 3484
3480 No specific requirements for U-Boot. Make sure you have some root 3485 No specific requirements for U-Boot. Make sure you have some root
3481 device (initial ramdisk, NFS) for your target system. 3486 device (initial ramdisk, NFS) for your target system.
3482 3487
3483 3488
3484 Building a Linux Image: 3489 Building a Linux Image:
3485 ----------------------- 3490 -----------------------
3486 3491
3487 With U-Boot, "normal" build targets like "zImage" or "bzImage" are 3492 With U-Boot, "normal" build targets like "zImage" or "bzImage" are
3488 not used. If you use recent kernel source, a new build target 3493 not used. If you use recent kernel source, a new build target
3489 "uImage" will exist which automatically builds an image usable by 3494 "uImage" will exist which automatically builds an image usable by
3490 U-Boot. Most older kernels also have support for a "pImage" target, 3495 U-Boot. Most older kernels also have support for a "pImage" target,
3491 which was introduced for our predecessor project PPCBoot and uses a 3496 which was introduced for our predecessor project PPCBoot and uses a
3492 100% compatible format. 3497 100% compatible format.
3493 3498
3494 Example: 3499 Example:
3495 3500
3496 make TQM850L_config 3501 make TQM850L_config
3497 make oldconfig 3502 make oldconfig
3498 make dep 3503 make dep
3499 make uImage 3504 make uImage
3500 3505
3501 The "uImage" build target uses a special tool (in 'tools/mkimage') to 3506 The "uImage" build target uses a special tool (in 'tools/mkimage') to
3502 encapsulate a compressed Linux kernel image with header information, 3507 encapsulate a compressed Linux kernel image with header information,
3503 CRC32 checksum etc. for use with U-Boot. This is what we are doing: 3508 CRC32 checksum etc. for use with U-Boot. This is what we are doing:
3504 3509
3505 * build a standard "vmlinux" kernel image (in ELF binary format): 3510 * build a standard "vmlinux" kernel image (in ELF binary format):
3506 3511
3507 * convert the kernel into a raw binary image: 3512 * convert the kernel into a raw binary image:
3508 3513
3509 ${CROSS_COMPILE}-objcopy -O binary \ 3514 ${CROSS_COMPILE}-objcopy -O binary \
3510 -R .note -R .comment \ 3515 -R .note -R .comment \
3511 -S vmlinux linux.bin 3516 -S vmlinux linux.bin
3512 3517
3513 * compress the binary image: 3518 * compress the binary image:
3514 3519
3515 gzip -9 linux.bin 3520 gzip -9 linux.bin
3516 3521
3517 * package compressed binary image for U-Boot: 3522 * package compressed binary image for U-Boot:
3518 3523
3519 mkimage -A ppc -O linux -T kernel -C gzip \ 3524 mkimage -A ppc -O linux -T kernel -C gzip \
3520 -a 0 -e 0 -n "Linux Kernel Image" \ 3525 -a 0 -e 0 -n "Linux Kernel Image" \
3521 -d linux.bin.gz uImage 3526 -d linux.bin.gz uImage
3522 3527
3523 3528
3524 The "mkimage" tool can also be used to create ramdisk images for use 3529 The "mkimage" tool can also be used to create ramdisk images for use
3525 with U-Boot, either separated from the Linux kernel image, or 3530 with U-Boot, either separated from the Linux kernel image, or
3526 combined into one file. "mkimage" encapsulates the images with a 64 3531 combined into one file. "mkimage" encapsulates the images with a 64
3527 byte header containing information about target architecture, 3532 byte header containing information about target architecture,
3528 operating system, image type, compression method, entry points, time 3533 operating system, image type, compression method, entry points, time
3529 stamp, CRC32 checksums, etc. 3534 stamp, CRC32 checksums, etc.
3530 3535
3531 "mkimage" can be called in two ways: to verify existing images and 3536 "mkimage" can be called in two ways: to verify existing images and
3532 print the header information, or to build new images. 3537 print the header information, or to build new images.
3533 3538
3534 In the first form (with "-l" option) mkimage lists the information 3539 In the first form (with "-l" option) mkimage lists the information
3535 contained in the header of an existing U-Boot image; this includes 3540 contained in the header of an existing U-Boot image; this includes
3536 checksum verification: 3541 checksum verification:
3537 3542
3538 tools/mkimage -l image 3543 tools/mkimage -l image
3539 -l ==> list image header information 3544 -l ==> list image header information
3540 3545
3541 The second form (with "-d" option) is used to build a U-Boot image 3546 The second form (with "-d" option) is used to build a U-Boot image
3542 from a "data file" which is used as image payload: 3547 from a "data file" which is used as image payload:
3543 3548
3544 tools/mkimage -A arch -O os -T type -C comp -a addr -e ep \ 3549 tools/mkimage -A arch -O os -T type -C comp -a addr -e ep \
3545 -n name -d data_file image 3550 -n name -d data_file image
3546 -A ==> set architecture to 'arch' 3551 -A ==> set architecture to 'arch'
3547 -O ==> set operating system to 'os' 3552 -O ==> set operating system to 'os'
3548 -T ==> set image type to 'type' 3553 -T ==> set image type to 'type'
3549 -C ==> set compression type 'comp' 3554 -C ==> set compression type 'comp'
3550 -a ==> set load address to 'addr' (hex) 3555 -a ==> set load address to 'addr' (hex)
3551 -e ==> set entry point to 'ep' (hex) 3556 -e ==> set entry point to 'ep' (hex)
3552 -n ==> set image name to 'name' 3557 -n ==> set image name to 'name'
3553 -d ==> use image data from 'datafile' 3558 -d ==> use image data from 'datafile'
3554 3559
3555 Right now, all Linux kernels for PowerPC systems use the same load 3560 Right now, all Linux kernels for PowerPC systems use the same load
3556 address (0x00000000), but the entry point address depends on the 3561 address (0x00000000), but the entry point address depends on the
3557 kernel version: 3562 kernel version:
3558 3563
3559 - 2.2.x kernels have the entry point at 0x0000000C, 3564 - 2.2.x kernels have the entry point at 0x0000000C,
3560 - 2.3.x and later kernels have the entry point at 0x00000000. 3565 - 2.3.x and later kernels have the entry point at 0x00000000.
3561 3566
3562 So a typical call to build a U-Boot image would read: 3567 So a typical call to build a U-Boot image would read:
3563 3568
3564 -> tools/mkimage -n '2.4.4 kernel for TQM850L' \ 3569 -> tools/mkimage -n '2.4.4 kernel for TQM850L' \
3565 > -A ppc -O linux -T kernel -C gzip -a 0 -e 0 \ 3570 > -A ppc -O linux -T kernel -C gzip -a 0 -e 0 \
3566 > -d /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/powerpc/coffboot/vmlinux.gz \ 3571 > -d /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/powerpc/coffboot/vmlinux.gz \
3567 > examples/uImage.TQM850L 3572 > examples/uImage.TQM850L
3568 Image Name: 2.4.4 kernel for TQM850L 3573 Image Name: 2.4.4 kernel for TQM850L
3569 Created: Wed Jul 19 02:34:59 2000 3574 Created: Wed Jul 19 02:34:59 2000
3570 Image Type: PowerPC Linux Kernel Image (gzip compressed) 3575 Image Type: PowerPC Linux Kernel Image (gzip compressed)
3571 Data Size: 335725 Bytes = 327.86 kB = 0.32 MB 3576 Data Size: 335725 Bytes = 327.86 kB = 0.32 MB
3572 Load Address: 0x00000000 3577 Load Address: 0x00000000
3573 Entry Point: 0x00000000 3578 Entry Point: 0x00000000
3574 3579
3575 To verify the contents of the image (or check for corruption): 3580 To verify the contents of the image (or check for corruption):
3576 3581
3577 -> tools/mkimage -l examples/uImage.TQM850L 3582 -> tools/mkimage -l examples/uImage.TQM850L
3578 Image Name: 2.4.4 kernel for TQM850L 3583 Image Name: 2.4.4 kernel for TQM850L
3579 Created: Wed Jul 19 02:34:59 2000 3584 Created: Wed Jul 19 02:34:59 2000
3580 Image Type: PowerPC Linux Kernel Image (gzip compressed) 3585 Image Type: PowerPC Linux Kernel Image (gzip compressed)
3581 Data Size: 335725 Bytes = 327.86 kB = 0.32 MB 3586 Data Size: 335725 Bytes = 327.86 kB = 0.32 MB
3582 Load Address: 0x00000000 3587 Load Address: 0x00000000
3583 Entry Point: 0x00000000 3588 Entry Point: 0x00000000
3584 3589
3585 NOTE: for embedded systems where boot time is critical you can trade 3590 NOTE: for embedded systems where boot time is critical you can trade
3586 speed for memory and install an UNCOMPRESSED image instead: this 3591 speed for memory and install an UNCOMPRESSED image instead: this
3587 needs more space in Flash, but boots much faster since it does not 3592 needs more space in Flash, but boots much faster since it does not
3588 need to be uncompressed: 3593 need to be uncompressed:
3589 3594
3590 -> gunzip /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/powerpc/coffboot/vmlinux.gz 3595 -> gunzip /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/powerpc/coffboot/vmlinux.gz
3591 -> tools/mkimage -n '2.4.4 kernel for TQM850L' \ 3596 -> tools/mkimage -n '2.4.4 kernel for TQM850L' \
3592 > -A ppc -O linux -T kernel -C none -a 0 -e 0 \ 3597 > -A ppc -O linux -T kernel -C none -a 0 -e 0 \
3593 > -d /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/powerpc/coffboot/vmlinux \ 3598 > -d /opt/elsk/ppc_8xx/usr/src/linux-2.4.4/arch/powerpc/coffboot/vmlinux \
3594 > examples/uImage.TQM850L-uncompressed 3599 > examples/uImage.TQM850L-uncompressed
3595 Image Name: 2.4.4 kernel for TQM850L 3600 Image Name: 2.4.4 kernel for TQM850L
3596 Created: Wed Jul 19 02:34:59 2000 3601 Created: Wed Jul 19 02:34:59 2000
3597 Image Type: PowerPC Linux Kernel Image (uncompressed) 3602 Image Type: PowerPC Linux Kernel Image (uncompressed)
3598 Data Size: 792160 Bytes = 773.59 kB = 0.76 MB 3603 Data Size: 792160 Bytes = 773.59 kB = 0.76 MB
3599 Load Address: 0x00000000 3604 Load Address: 0x00000000
3600 Entry Point: 0x00000000 3605 Entry Point: 0x00000000
3601 3606
3602 3607
3603 Similar you can build U-Boot images from a 'ramdisk.image.gz' file 3608 Similar you can build U-Boot images from a 'ramdisk.image.gz' file
3604 when your kernel is intended to use an initial ramdisk: 3609 when your kernel is intended to use an initial ramdisk:
3605 3610
3606 -> tools/mkimage -n 'Simple Ramdisk Image' \ 3611 -> tools/mkimage -n 'Simple Ramdisk Image' \
3607 > -A ppc -O linux -T ramdisk -C gzip \ 3612 > -A ppc -O linux -T ramdisk -C gzip \
3608 > -d /LinuxPPC/images/SIMPLE-ramdisk.image.gz examples/simple-initrd 3613 > -d /LinuxPPC/images/SIMPLE-ramdisk.image.gz examples/simple-initrd
3609 Image Name: Simple Ramdisk Image 3614 Image Name: Simple Ramdisk Image
3610 Created: Wed Jan 12 14:01:50 2000 3615 Created: Wed Jan 12 14:01:50 2000
3611 Image Type: PowerPC Linux RAMDisk Image (gzip compressed) 3616 Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
3612 Data Size: 566530 Bytes = 553.25 kB = 0.54 MB 3617 Data Size: 566530 Bytes = 553.25 kB = 0.54 MB
3613 Load Address: 0x00000000 3618 Load Address: 0x00000000
3614 Entry Point: 0x00000000 3619 Entry Point: 0x00000000
3615 3620
3616 3621
3617 Installing a Linux Image: 3622 Installing a Linux Image:
3618 ------------------------- 3623 -------------------------
3619 3624
3620 To downloading a U-Boot image over the serial (console) interface, 3625 To downloading a U-Boot image over the serial (console) interface,
3621 you must convert the image to S-Record format: 3626 you must convert the image to S-Record format:
3622 3627
3623 objcopy -I binary -O srec examples/image examples/image.srec 3628 objcopy -I binary -O srec examples/image examples/image.srec
3624 3629
3625 The 'objcopy' does not understand the information in the U-Boot 3630 The 'objcopy' does not understand the information in the U-Boot
3626 image header, so the resulting S-Record file will be relative to 3631 image header, so the resulting S-Record file will be relative to
3627 address 0x00000000. To load it to a given address, you need to 3632 address 0x00000000. To load it to a given address, you need to
3628 specify the target address as 'offset' parameter with the 'loads' 3633 specify the target address as 'offset' parameter with the 'loads'
3629 command. 3634 command.
3630 3635
3631 Example: install the image to address 0x40100000 (which on the 3636 Example: install the image to address 0x40100000 (which on the
3632 TQM8xxL is in the first Flash bank): 3637 TQM8xxL is in the first Flash bank):
3633 3638
3634 => erase 40100000 401FFFFF 3639 => erase 40100000 401FFFFF
3635 3640
3636 .......... done 3641 .......... done
3637 Erased 8 sectors 3642 Erased 8 sectors
3638 3643
3639 => loads 40100000 3644 => loads 40100000
3640 ## Ready for S-Record download ... 3645 ## Ready for S-Record download ...
3641 ~>examples/image.srec 3646 ~>examples/image.srec
3642 1 2 3 4 5 6 7 8 9 10 11 12 13 ... 3647 1 2 3 4 5 6 7 8 9 10 11 12 13 ...
3643 ... 3648 ...
3644 15989 15990 15991 15992 3649 15989 15990 15991 15992
3645 [file transfer complete] 3650 [file transfer complete]
3646 [connected] 3651 [connected]
3647 ## Start Addr = 0x00000000 3652 ## Start Addr = 0x00000000
3648 3653
3649 3654
3650 You can check the success of the download using the 'iminfo' command; 3655 You can check the success of the download using the 'iminfo' command;
3651 this includes a checksum verification so you can be sure no data 3656 this includes a checksum verification so you can be sure no data
3652 corruption happened: 3657 corruption happened:
3653 3658
3654 => imi 40100000 3659 => imi 40100000
3655 3660
3656 ## Checking Image at 40100000 ... 3661 ## Checking Image at 40100000 ...
3657 Image Name: 2.2.13 for initrd on TQM850L 3662 Image Name: 2.2.13 for initrd on TQM850L
3658 Image Type: PowerPC Linux Kernel Image (gzip compressed) 3663 Image Type: PowerPC Linux Kernel Image (gzip compressed)
3659 Data Size: 335725 Bytes = 327 kB = 0 MB 3664 Data Size: 335725 Bytes = 327 kB = 0 MB
3660 Load Address: 00000000 3665 Load Address: 00000000
3661 Entry Point: 0000000c 3666 Entry Point: 0000000c
3662 Verifying Checksum ... OK 3667 Verifying Checksum ... OK
3663 3668
3664 3669
3665 Boot Linux: 3670 Boot Linux:
3666 ----------- 3671 -----------
3667 3672
3668 The "bootm" command is used to boot an application that is stored in 3673 The "bootm" command is used to boot an application that is stored in
3669 memory (RAM or Flash). In case of a Linux kernel image, the contents 3674 memory (RAM or Flash). In case of a Linux kernel image, the contents
3670 of the "bootargs" environment variable is passed to the kernel as 3675 of the "bootargs" environment variable is passed to the kernel as
3671 parameters. You can check and modify this variable using the 3676 parameters. You can check and modify this variable using the
3672 "printenv" and "setenv" commands: 3677 "printenv" and "setenv" commands:
3673 3678
3674 3679
3675 => printenv bootargs 3680 => printenv bootargs
3676 bootargs=root=/dev/ram 3681 bootargs=root=/dev/ram
3677 3682
3678 => setenv bootargs root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2 3683 => setenv bootargs root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2
3679 3684
3680 => printenv bootargs 3685 => printenv bootargs
3681 bootargs=root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2 3686 bootargs=root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2
3682 3687
3683 => bootm 40020000 3688 => bootm 40020000
3684 ## Booting Linux kernel at 40020000 ... 3689 ## Booting Linux kernel at 40020000 ...
3685 Image Name: 2.2.13 for NFS on TQM850L 3690 Image Name: 2.2.13 for NFS on TQM850L
3686 Image Type: PowerPC Linux Kernel Image (gzip compressed) 3691 Image Type: PowerPC Linux Kernel Image (gzip compressed)
3687 Data Size: 381681 Bytes = 372 kB = 0 MB 3692 Data Size: 381681 Bytes = 372 kB = 0 MB
3688 Load Address: 00000000 3693 Load Address: 00000000
3689 Entry Point: 0000000c 3694 Entry Point: 0000000c
3690 Verifying Checksum ... OK 3695 Verifying Checksum ... OK
3691 Uncompressing Kernel Image ... OK 3696 Uncompressing Kernel Image ... OK
3692 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 3697 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
3693 Boot arguments: root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2 3698 Boot arguments: root=/dev/nfs rw nfsroot=10.0.0.2:/LinuxPPC nfsaddrs=10.0.0.99:10.0.0.2
3694 time_init: decrementer frequency = 187500000/60 3699 time_init: decrementer frequency = 187500000/60
3695 Calibrating delay loop... 49.77 BogoMIPS 3700 Calibrating delay loop... 49.77 BogoMIPS
3696 Memory: 15208k available (700k kernel code, 444k data, 32k init) [c0000000,c1000000] 3701 Memory: 15208k available (700k kernel code, 444k data, 32k init) [c0000000,c1000000]
3697 ... 3702 ...
3698 3703
3699 If you want to boot a Linux kernel with initial RAM disk, you pass 3704 If you want to boot a Linux kernel with initial RAM disk, you pass
3700 the memory addresses of both the kernel and the initrd image (PPBCOOT 3705 the memory addresses of both the kernel and the initrd image (PPBCOOT
3701 format!) to the "bootm" command: 3706 format!) to the "bootm" command:
3702 3707
3703 => imi 40100000 40200000 3708 => imi 40100000 40200000
3704 3709
3705 ## Checking Image at 40100000 ... 3710 ## Checking Image at 40100000 ...
3706 Image Name: 2.2.13 for initrd on TQM850L 3711 Image Name: 2.2.13 for initrd on TQM850L
3707 Image Type: PowerPC Linux Kernel Image (gzip compressed) 3712 Image Type: PowerPC Linux Kernel Image (gzip compressed)
3708 Data Size: 335725 Bytes = 327 kB = 0 MB 3713 Data Size: 335725 Bytes = 327 kB = 0 MB
3709 Load Address: 00000000 3714 Load Address: 00000000
3710 Entry Point: 0000000c 3715 Entry Point: 0000000c
3711 Verifying Checksum ... OK 3716 Verifying Checksum ... OK
3712 3717
3713 ## Checking Image at 40200000 ... 3718 ## Checking Image at 40200000 ...
3714 Image Name: Simple Ramdisk Image 3719 Image Name: Simple Ramdisk Image
3715 Image Type: PowerPC Linux RAMDisk Image (gzip compressed) 3720 Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
3716 Data Size: 566530 Bytes = 553 kB = 0 MB 3721 Data Size: 566530 Bytes = 553 kB = 0 MB
3717 Load Address: 00000000 3722 Load Address: 00000000
3718 Entry Point: 00000000 3723 Entry Point: 00000000
3719 Verifying Checksum ... OK 3724 Verifying Checksum ... OK
3720 3725
3721 => bootm 40100000 40200000 3726 => bootm 40100000 40200000
3722 ## Booting Linux kernel at 40100000 ... 3727 ## Booting Linux kernel at 40100000 ...
3723 Image Name: 2.2.13 for initrd on TQM850L 3728 Image Name: 2.2.13 for initrd on TQM850L
3724 Image Type: PowerPC Linux Kernel Image (gzip compressed) 3729 Image Type: PowerPC Linux Kernel Image (gzip compressed)
3725 Data Size: 335725 Bytes = 327 kB = 0 MB 3730 Data Size: 335725 Bytes = 327 kB = 0 MB
3726 Load Address: 00000000 3731 Load Address: 00000000
3727 Entry Point: 0000000c 3732 Entry Point: 0000000c
3728 Verifying Checksum ... OK 3733 Verifying Checksum ... OK
3729 Uncompressing Kernel Image ... OK 3734 Uncompressing Kernel Image ... OK
3730 ## Loading RAMDisk Image at 40200000 ... 3735 ## Loading RAMDisk Image at 40200000 ...
3731 Image Name: Simple Ramdisk Image 3736 Image Name: Simple Ramdisk Image
3732 Image Type: PowerPC Linux RAMDisk Image (gzip compressed) 3737 Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
3733 Data Size: 566530 Bytes = 553 kB = 0 MB 3738 Data Size: 566530 Bytes = 553 kB = 0 MB
3734 Load Address: 00000000 3739 Load Address: 00000000
3735 Entry Point: 00000000 3740 Entry Point: 00000000
3736 Verifying Checksum ... OK 3741 Verifying Checksum ... OK
3737 Loading Ramdisk ... OK 3742 Loading Ramdisk ... OK
3738 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 3743 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
3739 Boot arguments: root=/dev/ram 3744 Boot arguments: root=/dev/ram
3740 time_init: decrementer frequency = 187500000/60 3745 time_init: decrementer frequency = 187500000/60
3741 Calibrating delay loop... 49.77 BogoMIPS 3746 Calibrating delay loop... 49.77 BogoMIPS
3742 ... 3747 ...
3743 RAMDISK: Compressed image found at block 0 3748 RAMDISK: Compressed image found at block 0
3744 VFS: Mounted root (ext2 filesystem). 3749 VFS: Mounted root (ext2 filesystem).
3745 3750
3746 bash# 3751 bash#
3747 3752
3748 Boot Linux and pass a flat device tree: 3753 Boot Linux and pass a flat device tree:
3749 ----------- 3754 -----------
3750 3755
3751 First, U-Boot must be compiled with the appropriate defines. See the section 3756 First, U-Boot must be compiled with the appropriate defines. See the section
3752 titled "Linux Kernel Interface" above for a more in depth explanation. The 3757 titled "Linux Kernel Interface" above for a more in depth explanation. The
3753 following is an example of how to start a kernel and pass an updated 3758 following is an example of how to start a kernel and pass an updated
3754 flat device tree: 3759 flat device tree:
3755 3760
3756 => print oftaddr 3761 => print oftaddr
3757 oftaddr=0x300000 3762 oftaddr=0x300000
3758 => print oft 3763 => print oft
3759 oft=oftrees/mpc8540ads.dtb 3764 oft=oftrees/mpc8540ads.dtb
3760 => tftp $oftaddr $oft 3765 => tftp $oftaddr $oft
3761 Speed: 1000, full duplex 3766 Speed: 1000, full duplex
3762 Using TSEC0 device 3767 Using TSEC0 device
3763 TFTP from server 192.168.1.1; our IP address is 192.168.1.101 3768 TFTP from server 192.168.1.1; our IP address is 192.168.1.101
3764 Filename 'oftrees/mpc8540ads.dtb'. 3769 Filename 'oftrees/mpc8540ads.dtb'.
3765 Load address: 0x300000 3770 Load address: 0x300000
3766 Loading: # 3771 Loading: #
3767 done 3772 done
3768 Bytes transferred = 4106 (100a hex) 3773 Bytes transferred = 4106 (100a hex)
3769 => tftp $loadaddr $bootfile 3774 => tftp $loadaddr $bootfile
3770 Speed: 1000, full duplex 3775 Speed: 1000, full duplex
3771 Using TSEC0 device 3776 Using TSEC0 device
3772 TFTP from server 192.168.1.1; our IP address is 192.168.1.2 3777 TFTP from server 192.168.1.1; our IP address is 192.168.1.2
3773 Filename 'uImage'. 3778 Filename 'uImage'.
3774 Load address: 0x200000 3779 Load address: 0x200000
3775 Loading:############ 3780 Loading:############
3776 done 3781 done
3777 Bytes transferred = 1029407 (fb51f hex) 3782 Bytes transferred = 1029407 (fb51f hex)
3778 => print loadaddr 3783 => print loadaddr
3779 loadaddr=200000 3784 loadaddr=200000
3780 => print oftaddr 3785 => print oftaddr
3781 oftaddr=0x300000 3786 oftaddr=0x300000
3782 => bootm $loadaddr - $oftaddr 3787 => bootm $loadaddr - $oftaddr
3783 ## Booting image at 00200000 ... 3788 ## Booting image at 00200000 ...
3784 Image Name: Linux-2.6.17-dirty 3789 Image Name: Linux-2.6.17-dirty
3785 Image Type: PowerPC Linux Kernel Image (gzip compressed) 3790 Image Type: PowerPC Linux Kernel Image (gzip compressed)
3786 Data Size: 1029343 Bytes = 1005.2 kB 3791 Data Size: 1029343 Bytes = 1005.2 kB
3787 Load Address: 00000000 3792 Load Address: 00000000
3788 Entry Point: 00000000 3793 Entry Point: 00000000
3789 Verifying Checksum ... OK 3794 Verifying Checksum ... OK
3790 Uncompressing Kernel Image ... OK 3795 Uncompressing Kernel Image ... OK
3791 Booting using flat device tree at 0x300000 3796 Booting using flat device tree at 0x300000
3792 Using MPC85xx ADS machine description 3797 Using MPC85xx ADS machine description
3793 Memory CAM mapping: CAM0=256Mb, CAM1=256Mb, CAM2=0Mb residual: 0Mb 3798 Memory CAM mapping: CAM0=256Mb, CAM1=256Mb, CAM2=0Mb residual: 0Mb
3794 [snip] 3799 [snip]
3795 3800
3796 3801
3797 More About U-Boot Image Types: 3802 More About U-Boot Image Types:
3798 ------------------------------ 3803 ------------------------------
3799 3804
3800 U-Boot supports the following image types: 3805 U-Boot supports the following image types:
3801 3806
3802 "Standalone Programs" are directly runnable in the environment 3807 "Standalone Programs" are directly runnable in the environment
3803 provided by U-Boot; it is expected that (if they behave 3808 provided by U-Boot; it is expected that (if they behave
3804 well) you can continue to work in U-Boot after return from 3809 well) you can continue to work in U-Boot after return from
3805 the Standalone Program. 3810 the Standalone Program.
3806 "OS Kernel Images" are usually images of some Embedded OS which 3811 "OS Kernel Images" are usually images of some Embedded OS which
3807 will take over control completely. Usually these programs 3812 will take over control completely. Usually these programs
3808 will install their own set of exception handlers, device 3813 will install their own set of exception handlers, device
3809 drivers, set up the MMU, etc. - this means, that you cannot 3814 drivers, set up the MMU, etc. - this means, that you cannot
3810 expect to re-enter U-Boot except by resetting the CPU. 3815 expect to re-enter U-Boot except by resetting the CPU.
3811 "RAMDisk Images" are more or less just data blocks, and their 3816 "RAMDisk Images" are more or less just data blocks, and their
3812 parameters (address, size) are passed to an OS kernel that is 3817 parameters (address, size) are passed to an OS kernel that is
3813 being started. 3818 being started.
3814 "Multi-File Images" contain several images, typically an OS 3819 "Multi-File Images" contain several images, typically an OS
3815 (Linux) kernel image and one or more data images like 3820 (Linux) kernel image and one or more data images like
3816 RAMDisks. This construct is useful for instance when you want 3821 RAMDisks. This construct is useful for instance when you want
3817 to boot over the network using BOOTP etc., where the boot 3822 to boot over the network using BOOTP etc., where the boot
3818 server provides just a single image file, but you want to get 3823 server provides just a single image file, but you want to get
3819 for instance an OS kernel and a RAMDisk image. 3824 for instance an OS kernel and a RAMDisk image.
3820 3825
3821 "Multi-File Images" start with a list of image sizes, each 3826 "Multi-File Images" start with a list of image sizes, each
3822 image size (in bytes) specified by an "uint32_t" in network 3827 image size (in bytes) specified by an "uint32_t" in network
3823 byte order. This list is terminated by an "(uint32_t)0". 3828 byte order. This list is terminated by an "(uint32_t)0".
3824 Immediately after the terminating 0 follow the images, one by 3829 Immediately after the terminating 0 follow the images, one by
3825 one, all aligned on "uint32_t" boundaries (size rounded up to 3830 one, all aligned on "uint32_t" boundaries (size rounded up to
3826 a multiple of 4 bytes). 3831 a multiple of 4 bytes).
3827 3832
3828 "Firmware Images" are binary images containing firmware (like 3833 "Firmware Images" are binary images containing firmware (like
3829 U-Boot or FPGA images) which usually will be programmed to 3834 U-Boot or FPGA images) which usually will be programmed to
3830 flash memory. 3835 flash memory.
3831 3836
3832 "Script files" are command sequences that will be executed by 3837 "Script files" are command sequences that will be executed by
3833 U-Boot's command interpreter; this feature is especially 3838 U-Boot's command interpreter; this feature is especially
3834 useful when you configure U-Boot to use a real shell (hush) 3839 useful when you configure U-Boot to use a real shell (hush)
3835 as command interpreter. 3840 as command interpreter.
3836 3841
3837 3842
3838 Standalone HOWTO: 3843 Standalone HOWTO:
3839 ================= 3844 =================
3840 3845
3841 One of the features of U-Boot is that you can dynamically load and 3846 One of the features of U-Boot is that you can dynamically load and
3842 run "standalone" applications, which can use some resources of 3847 run "standalone" applications, which can use some resources of
3843 U-Boot like console I/O functions or interrupt services. 3848 U-Boot like console I/O functions or interrupt services.
3844 3849
3845 Two simple examples are included with the sources: 3850 Two simple examples are included with the sources:
3846 3851
3847 "Hello World" Demo: 3852 "Hello World" Demo:
3848 ------------------- 3853 -------------------
3849 3854
3850 'examples/hello_world.c' contains a small "Hello World" Demo 3855 'examples/hello_world.c' contains a small "Hello World" Demo
3851 application; it is automatically compiled when you build U-Boot. 3856 application; it is automatically compiled when you build U-Boot.
3852 It's configured to run at address 0x00040004, so you can play with it 3857 It's configured to run at address 0x00040004, so you can play with it
3853 like that: 3858 like that:
3854 3859
3855 => loads 3860 => loads
3856 ## Ready for S-Record download ... 3861 ## Ready for S-Record download ...
3857 ~>examples/hello_world.srec 3862 ~>examples/hello_world.srec
3858 1 2 3 4 5 6 7 8 9 10 11 ... 3863 1 2 3 4 5 6 7 8 9 10 11 ...
3859 [file transfer complete] 3864 [file transfer complete]
3860 [connected] 3865 [connected]
3861 ## Start Addr = 0x00040004 3866 ## Start Addr = 0x00040004
3862 3867
3863 => go 40004 Hello World! This is a test. 3868 => go 40004 Hello World! This is a test.
3864 ## Starting application at 0x00040004 ... 3869 ## Starting application at 0x00040004 ...
3865 Hello World 3870 Hello World
3866 argc = 7 3871 argc = 7
3867 argv[0] = "40004" 3872 argv[0] = "40004"
3868 argv[1] = "Hello" 3873 argv[1] = "Hello"
3869 argv[2] = "World!" 3874 argv[2] = "World!"
3870 argv[3] = "This" 3875 argv[3] = "This"
3871 argv[4] = "is" 3876 argv[4] = "is"
3872 argv[5] = "a" 3877 argv[5] = "a"
3873 argv[6] = "test." 3878 argv[6] = "test."
3874 argv[7] = "<NULL>" 3879 argv[7] = "<NULL>"
3875 Hit any key to exit ... 3880 Hit any key to exit ...
3876 3881
3877 ## Application terminated, rc = 0x0 3882 ## Application terminated, rc = 0x0
3878 3883
3879 Another example, which demonstrates how to register a CPM interrupt 3884 Another example, which demonstrates how to register a CPM interrupt
3880 handler with the U-Boot code, can be found in 'examples/timer.c'. 3885 handler with the U-Boot code, can be found in 'examples/timer.c'.
3881 Here, a CPM timer is set up to generate an interrupt every second. 3886 Here, a CPM timer is set up to generate an interrupt every second.
3882 The interrupt service routine is trivial, just printing a '.' 3887 The interrupt service routine is trivial, just printing a '.'
3883 character, but this is just a demo program. The application can be 3888 character, but this is just a demo program. The application can be
3884 controlled by the following keys: 3889 controlled by the following keys:
3885 3890
3886 ? - print current values og the CPM Timer registers 3891 ? - print current values og the CPM Timer registers
3887 b - enable interrupts and start timer 3892 b - enable interrupts and start timer
3888 e - stop timer and disable interrupts 3893 e - stop timer and disable interrupts
3889 q - quit application 3894 q - quit application
3890 3895
3891 => loads 3896 => loads
3892 ## Ready for S-Record download ... 3897 ## Ready for S-Record download ...
3893 ~>examples/timer.srec 3898 ~>examples/timer.srec
3894 1 2 3 4 5 6 7 8 9 10 11 ... 3899 1 2 3 4 5 6 7 8 9 10 11 ...
3895 [file transfer complete] 3900 [file transfer complete]
3896 [connected] 3901 [connected]
3897 ## Start Addr = 0x00040004 3902 ## Start Addr = 0x00040004
3898 3903
3899 => go 40004 3904 => go 40004
3900 ## Starting application at 0x00040004 ... 3905 ## Starting application at 0x00040004 ...
3901 TIMERS=0xfff00980 3906 TIMERS=0xfff00980
3902 Using timer 1 3907 Using timer 1
3903 tgcr @ 0xfff00980, tmr @ 0xfff00990, trr @ 0xfff00994, tcr @ 0xfff00998, tcn @ 0xfff0099c, ter @ 0xfff009b0 3908 tgcr @ 0xfff00980, tmr @ 0xfff00990, trr @ 0xfff00994, tcr @ 0xfff00998, tcn @ 0xfff0099c, ter @ 0xfff009b0
3904 3909
3905 Hit 'b': 3910 Hit 'b':
3906 [q, b, e, ?] Set interval 1000000 us 3911 [q, b, e, ?] Set interval 1000000 us
3907 Enabling timer 3912 Enabling timer
3908 Hit '?': 3913 Hit '?':
3909 [q, b, e, ?] ........ 3914 [q, b, e, ?] ........
3910 tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0xef6, ter=0x0 3915 tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0xef6, ter=0x0
3911 Hit '?': 3916 Hit '?':
3912 [q, b, e, ?] . 3917 [q, b, e, ?] .
3913 tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x2ad4, ter=0x0 3918 tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x2ad4, ter=0x0
3914 Hit '?': 3919 Hit '?':
3915 [q, b, e, ?] . 3920 [q, b, e, ?] .
3916 tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x1efc, ter=0x0 3921 tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x1efc, ter=0x0
3917 Hit '?': 3922 Hit '?':
3918 [q, b, e, ?] . 3923 [q, b, e, ?] .
3919 tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x169d, ter=0x0 3924 tgcr=0x1, tmr=0xff1c, trr=0x3d09, tcr=0x0, tcn=0x169d, ter=0x0
3920 Hit 'e': 3925 Hit 'e':
3921 [q, b, e, ?] ...Stopping timer 3926 [q, b, e, ?] ...Stopping timer
3922 Hit 'q': 3927 Hit 'q':
3923 [q, b, e, ?] ## Application terminated, rc = 0x0 3928 [q, b, e, ?] ## Application terminated, rc = 0x0
3924 3929
3925 3930
3926 Minicom warning: 3931 Minicom warning:
3927 ================ 3932 ================
3928 3933
3929 Over time, many people have reported problems when trying to use the 3934 Over time, many people have reported problems when trying to use the
3930 "minicom" terminal emulation program for serial download. I (wd) 3935 "minicom" terminal emulation program for serial download. I (wd)
3931 consider minicom to be broken, and recommend not to use it. Under 3936 consider minicom to be broken, and recommend not to use it. Under
3932 Unix, I recommend to use C-Kermit for general purpose use (and 3937 Unix, I recommend to use C-Kermit for general purpose use (and
3933 especially for kermit binary protocol download ("loadb" command), and 3938 especially for kermit binary protocol download ("loadb" command), and
3934 use "cu" for S-Record download ("loads" command). 3939 use "cu" for S-Record download ("loads" command).
3935 3940
3936 Nevertheless, if you absolutely want to use it try adding this 3941 Nevertheless, if you absolutely want to use it try adding this
3937 configuration to your "File transfer protocols" section: 3942 configuration to your "File transfer protocols" section:
3938 3943
3939 Name Program Name U/D FullScr IO-Red. Multi 3944 Name Program Name U/D FullScr IO-Red. Multi
3940 X kermit /usr/bin/kermit -i -l %l -s Y U Y N N 3945 X kermit /usr/bin/kermit -i -l %l -s Y U Y N N
3941 Y kermit /usr/bin/kermit -i -l %l -r N D Y N N 3946 Y kermit /usr/bin/kermit -i -l %l -r N D Y N N
3942 3947
3943 3948
3944 NetBSD Notes: 3949 NetBSD Notes:
3945 ============= 3950 =============
3946 3951
3947 Starting at version 0.9.2, U-Boot supports NetBSD both as host 3952 Starting at version 0.9.2, U-Boot supports NetBSD both as host
3948 (build U-Boot) and target system (boots NetBSD/mpc8xx). 3953 (build U-Boot) and target system (boots NetBSD/mpc8xx).
3949 3954
3950 Building requires a cross environment; it is known to work on 3955 Building requires a cross environment; it is known to work on
3951 NetBSD/i386 with the cross-powerpc-netbsd-1.3 package (you will also 3956 NetBSD/i386 with the cross-powerpc-netbsd-1.3 package (you will also
3952 need gmake since the Makefiles are not compatible with BSD make). 3957 need gmake since the Makefiles are not compatible with BSD make).
3953 Note that the cross-powerpc package does not install include files; 3958 Note that the cross-powerpc package does not install include files;
3954 attempting to build U-Boot will fail because <machine/ansi.h> is 3959 attempting to build U-Boot will fail because <machine/ansi.h> is
3955 missing. This file has to be installed and patched manually: 3960 missing. This file has to be installed and patched manually:
3956 3961
3957 # cd /usr/pkg/cross/powerpc-netbsd/include 3962 # cd /usr/pkg/cross/powerpc-netbsd/include
3958 # mkdir powerpc 3963 # mkdir powerpc
3959 # ln -s powerpc machine 3964 # ln -s powerpc machine
3960 # cp /usr/src/sys/arch/powerpc/include/ansi.h powerpc/ansi.h 3965 # cp /usr/src/sys/arch/powerpc/include/ansi.h powerpc/ansi.h
3961 # ${EDIT} powerpc/ansi.h ## must remove __va_list, _BSD_VA_LIST 3966 # ${EDIT} powerpc/ansi.h ## must remove __va_list, _BSD_VA_LIST
3962 3967
3963 Native builds *don't* work due to incompatibilities between native 3968 Native builds *don't* work due to incompatibilities between native
3964 and U-Boot include files. 3969 and U-Boot include files.
3965 3970
3966 Booting assumes that (the first part of) the image booted is a 3971 Booting assumes that (the first part of) the image booted is a
3967 stage-2 loader which in turn loads and then invokes the kernel 3972 stage-2 loader which in turn loads and then invokes the kernel
3968 proper. Loader sources will eventually appear in the NetBSD source 3973 proper. Loader sources will eventually appear in the NetBSD source
3969 tree (probably in sys/arc/mpc8xx/stand/u-boot_stage2/); in the 3974 tree (probably in sys/arc/mpc8xx/stand/u-boot_stage2/); in the
3970 meantime, see ftp://ftp.denx.de/pub/u-boot/ppcboot_stage2.tar.gz 3975 meantime, see ftp://ftp.denx.de/pub/u-boot/ppcboot_stage2.tar.gz
3971 3976
3972 3977
3973 Implementation Internals: 3978 Implementation Internals:
3974 ========================= 3979 =========================
3975 3980
3976 The following is not intended to be a complete description of every 3981 The following is not intended to be a complete description of every
3977 implementation detail. However, it should help to understand the 3982 implementation detail. However, it should help to understand the
3978 inner workings of U-Boot and make it easier to port it to custom 3983 inner workings of U-Boot and make it easier to port it to custom
3979 hardware. 3984 hardware.
3980 3985
3981 3986
3982 Initial Stack, Global Data: 3987 Initial Stack, Global Data:
3983 --------------------------- 3988 ---------------------------
3984 3989
3985 The implementation of U-Boot is complicated by the fact that U-Boot 3990 The implementation of U-Boot is complicated by the fact that U-Boot
3986 starts running out of ROM (flash memory), usually without access to 3991 starts running out of ROM (flash memory), usually without access to
3987 system RAM (because the memory controller is not initialized yet). 3992 system RAM (because the memory controller is not initialized yet).
3988 This means that we don't have writable Data or BSS segments, and BSS 3993 This means that we don't have writable Data or BSS segments, and BSS
3989 is not initialized as zero. To be able to get a C environment working 3994 is not initialized as zero. To be able to get a C environment working
3990 at all, we have to allocate at least a minimal stack. Implementation 3995 at all, we have to allocate at least a minimal stack. Implementation
3991 options for this are defined and restricted by the CPU used: Some CPU 3996 options for this are defined and restricted by the CPU used: Some CPU
3992 models provide on-chip memory (like the IMMR area on MPC8xx and 3997 models provide on-chip memory (like the IMMR area on MPC8xx and
3993 MPC826x processors), on others (parts of) the data cache can be 3998 MPC826x processors), on others (parts of) the data cache can be
3994 locked as (mis-) used as memory, etc. 3999 locked as (mis-) used as memory, etc.
3995 4000
3996 Chris Hallinan posted a good summary of these issues to the 4001 Chris Hallinan posted a good summary of these issues to the
3997 U-Boot mailing list: 4002 U-Boot mailing list:
3998 4003
3999 Subject: RE: [U-Boot-Users] RE: More On Memory Bank x (nothingness)? 4004 Subject: RE: [U-Boot-Users] RE: More On Memory Bank x (nothingness)?
4000 From: "Chris Hallinan" <clh@net1plus.com> 4005 From: "Chris Hallinan" <clh@net1plus.com>
4001 Date: Mon, 10 Feb 2003 16:43:46 -0500 (22:43 MET) 4006 Date: Mon, 10 Feb 2003 16:43:46 -0500 (22:43 MET)
4002 ... 4007 ...
4003 4008
4004 Correct me if I'm wrong, folks, but the way I understand it 4009 Correct me if I'm wrong, folks, but the way I understand it
4005 is this: Using DCACHE as initial RAM for Stack, etc, does not 4010 is this: Using DCACHE as initial RAM for Stack, etc, does not
4006 require any physical RAM backing up the cache. The cleverness 4011 require any physical RAM backing up the cache. The cleverness
4007 is that the cache is being used as a temporary supply of 4012 is that the cache is being used as a temporary supply of
4008 necessary storage before the SDRAM controller is setup. It's 4013 necessary storage before the SDRAM controller is setup. It's
4009 beyond the scope of this list to explain the details, but you 4014 beyond the scope of this list to explain the details, but you
4010 can see how this works by studying the cache architecture and 4015 can see how this works by studying the cache architecture and
4011 operation in the architecture and processor-specific manuals. 4016 operation in the architecture and processor-specific manuals.
4012 4017
4013 OCM is On Chip Memory, which I believe the 405GP has 4K. It 4018 OCM is On Chip Memory, which I believe the 405GP has 4K. It
4014 is another option for the system designer to use as an 4019 is another option for the system designer to use as an
4015 initial stack/RAM area prior to SDRAM being available. Either 4020 initial stack/RAM area prior to SDRAM being available. Either
4016 option should work for you. Using CS 4 should be fine if your 4021 option should work for you. Using CS 4 should be fine if your
4017 board designers haven't used it for something that would 4022 board designers haven't used it for something that would
4018 cause you grief during the initial boot! It is frequently not 4023 cause you grief during the initial boot! It is frequently not
4019 used. 4024 used.
4020 4025
4021 CONFIG_SYS_INIT_RAM_ADDR should be somewhere that won't interfere 4026 CONFIG_SYS_INIT_RAM_ADDR should be somewhere that won't interfere
4022 with your processor/board/system design. The default value 4027 with your processor/board/system design. The default value
4023 you will find in any recent u-boot distribution in 4028 you will find in any recent u-boot distribution in
4024 walnut.h should work for you. I'd set it to a value larger 4029 walnut.h should work for you. I'd set it to a value larger
4025 than your SDRAM module. If you have a 64MB SDRAM module, set 4030 than your SDRAM module. If you have a 64MB SDRAM module, set
4026 it above 400_0000. Just make sure your board has no resources 4031 it above 400_0000. Just make sure your board has no resources
4027 that are supposed to respond to that address! That code in 4032 that are supposed to respond to that address! That code in
4028 start.S has been around a while and should work as is when 4033 start.S has been around a while and should work as is when
4029 you get the config right. 4034 you get the config right.
4030 4035
4031 -Chris Hallinan 4036 -Chris Hallinan
4032 DS4.COM, Inc. 4037 DS4.COM, Inc.
4033 4038
4034 It is essential to remember this, since it has some impact on the C 4039 It is essential to remember this, since it has some impact on the C
4035 code for the initialization procedures: 4040 code for the initialization procedures:
4036 4041
4037 * Initialized global data (data segment) is read-only. Do not attempt 4042 * Initialized global data (data segment) is read-only. Do not attempt
4038 to write it. 4043 to write it.
4039 4044
4040 * Do not use any uninitialized global data (or implicitely initialized 4045 * Do not use any uninitialized global data (or implicitely initialized
4041 as zero data - BSS segment) at all - this is undefined, initiali- 4046 as zero data - BSS segment) at all - this is undefined, initiali-
4042 zation is performed later (when relocating to RAM). 4047 zation is performed later (when relocating to RAM).
4043 4048
4044 * Stack space is very limited. Avoid big data buffers or things like 4049 * Stack space is very limited. Avoid big data buffers or things like
4045 that. 4050 that.
4046 4051
4047 Having only the stack as writable memory limits means we cannot use 4052 Having only the stack as writable memory limits means we cannot use
4048 normal global data to share information beween the code. But it 4053 normal global data to share information beween the code. But it
4049 turned out that the implementation of U-Boot can be greatly 4054 turned out that the implementation of U-Boot can be greatly
4050 simplified by making a global data structure (gd_t) available to all 4055 simplified by making a global data structure (gd_t) available to all
4051 functions. We could pass a pointer to this data as argument to _all_ 4056 functions. We could pass a pointer to this data as argument to _all_
4052 functions, but this would bloat the code. Instead we use a feature of 4057 functions, but this would bloat the code. Instead we use a feature of
4053 the GCC compiler (Global Register Variables) to share the data: we 4058 the GCC compiler (Global Register Variables) to share the data: we
4054 place a pointer (gd) to the global data into a register which we 4059 place a pointer (gd) to the global data into a register which we
4055 reserve for this purpose. 4060 reserve for this purpose.
4056 4061
4057 When choosing a register for such a purpose we are restricted by the 4062 When choosing a register for such a purpose we are restricted by the
4058 relevant (E)ABI specifications for the current architecture, and by 4063 relevant (E)ABI specifications for the current architecture, and by
4059 GCC's implementation. 4064 GCC's implementation.
4060 4065
4061 For PowerPC, the following registers have specific use: 4066 For PowerPC, the following registers have specific use:
4062 R1: stack pointer 4067 R1: stack pointer
4063 R2: reserved for system use 4068 R2: reserved for system use
4064 R3-R4: parameter passing and return values 4069 R3-R4: parameter passing and return values
4065 R5-R10: parameter passing 4070 R5-R10: parameter passing
4066 R13: small data area pointer 4071 R13: small data area pointer
4067 R30: GOT pointer 4072 R30: GOT pointer
4068 R31: frame pointer 4073 R31: frame pointer
4069 4074
4070 (U-Boot also uses R12 as internal GOT pointer. r12 4075 (U-Boot also uses R12 as internal GOT pointer. r12
4071 is a volatile register so r12 needs to be reset when 4076 is a volatile register so r12 needs to be reset when
4072 going back and forth between asm and C) 4077 going back and forth between asm and C)
4073 4078
4074 ==> U-Boot will use R2 to hold a pointer to the global data 4079 ==> U-Boot will use R2 to hold a pointer to the global data
4075 4080
4076 Note: on PPC, we could use a static initializer (since the 4081 Note: on PPC, we could use a static initializer (since the
4077 address of the global data structure is known at compile time), 4082 address of the global data structure is known at compile time),
4078 but it turned out that reserving a register results in somewhat 4083 but it turned out that reserving a register results in somewhat
4079 smaller code - although the code savings are not that big (on 4084 smaller code - although the code savings are not that big (on
4080 average for all boards 752 bytes for the whole U-Boot image, 4085 average for all boards 752 bytes for the whole U-Boot image,
4081 624 text + 127 data). 4086 624 text + 127 data).
4082 4087
4083 On Blackfin, the normal C ABI (except for P3) is followed as documented here: 4088 On Blackfin, the normal C ABI (except for P3) is followed as documented here:
4084 http://docs.blackfin.uclinux.org/doku.php?id=application_binary_interface 4089 http://docs.blackfin.uclinux.org/doku.php?id=application_binary_interface
4085 4090
4086 ==> U-Boot will use P3 to hold a pointer to the global data 4091 ==> U-Boot will use P3 to hold a pointer to the global data
4087 4092
4088 On ARM, the following registers are used: 4093 On ARM, the following registers are used:
4089 4094
4090 R0: function argument word/integer result 4095 R0: function argument word/integer result
4091 R1-R3: function argument word 4096 R1-R3: function argument word
4092 R9: GOT pointer 4097 R9: GOT pointer
4093 R10: stack limit (used only if stack checking if enabled) 4098 R10: stack limit (used only if stack checking if enabled)
4094 R11: argument (frame) pointer 4099 R11: argument (frame) pointer
4095 R12: temporary workspace 4100 R12: temporary workspace
4096 R13: stack pointer 4101 R13: stack pointer
4097 R14: link register 4102 R14: link register
4098 R15: program counter 4103 R15: program counter
4099 4104
4100 ==> U-Boot will use R8 to hold a pointer to the global data 4105 ==> U-Boot will use R8 to hold a pointer to the global data
4101 4106
4102 On Nios II, the ABI is documented here: 4107 On Nios II, the ABI is documented here:
4103 http://www.altera.com/literature/hb/nios2/n2cpu_nii51016.pdf 4108 http://www.altera.com/literature/hb/nios2/n2cpu_nii51016.pdf
4104 4109
4105 ==> U-Boot will use gp to hold a pointer to the global data 4110 ==> U-Boot will use gp to hold a pointer to the global data
4106 4111
4107 Note: on Nios II, we give "-G0" option to gcc and don't use gp 4112 Note: on Nios II, we give "-G0" option to gcc and don't use gp
4108 to access small data sections, so gp is free. 4113 to access small data sections, so gp is free.
4109 4114
4110 NOTE: DECLARE_GLOBAL_DATA_PTR must be used with file-global scope, 4115 NOTE: DECLARE_GLOBAL_DATA_PTR must be used with file-global scope,
4111 or current versions of GCC may "optimize" the code too much. 4116 or current versions of GCC may "optimize" the code too much.
4112 4117
4113 Memory Management: 4118 Memory Management:
4114 ------------------ 4119 ------------------
4115 4120
4116 U-Boot runs in system state and uses physical addresses, i.e. the 4121 U-Boot runs in system state and uses physical addresses, i.e. the
4117 MMU is not used either for address mapping nor for memory protection. 4122 MMU is not used either for address mapping nor for memory protection.
4118 4123
4119 The available memory is mapped to fixed addresses using the memory 4124 The available memory is mapped to fixed addresses using the memory
4120 controller. In this process, a contiguous block is formed for each 4125 controller. In this process, a contiguous block is formed for each
4121 memory type (Flash, SDRAM, SRAM), even when it consists of several 4126 memory type (Flash, SDRAM, SRAM), even when it consists of several
4122 physical memory banks. 4127 physical memory banks.
4123 4128
4124 U-Boot is installed in the first 128 kB of the first Flash bank (on 4129 U-Boot is installed in the first 128 kB of the first Flash bank (on
4125 TQM8xxL modules this is the range 0x40000000 ... 0x4001FFFF). After 4130 TQM8xxL modules this is the range 0x40000000 ... 0x4001FFFF). After
4126 booting and sizing and initializing DRAM, the code relocates itself 4131 booting and sizing and initializing DRAM, the code relocates itself
4127 to the upper end of DRAM. Immediately below the U-Boot code some 4132 to the upper end of DRAM. Immediately below the U-Boot code some
4128 memory is reserved for use by malloc() [see CONFIG_SYS_MALLOC_LEN 4133 memory is reserved for use by malloc() [see CONFIG_SYS_MALLOC_LEN
4129 configuration setting]. Below that, a structure with global Board 4134 configuration setting]. Below that, a structure with global Board
4130 Info data is placed, followed by the stack (growing downward). 4135 Info data is placed, followed by the stack (growing downward).
4131 4136
4132 Additionally, some exception handler code is copied to the low 8 kB 4137 Additionally, some exception handler code is copied to the low 8 kB
4133 of DRAM (0x00000000 ... 0x00001FFF). 4138 of DRAM (0x00000000 ... 0x00001FFF).
4134 4139
4135 So a typical memory configuration with 16 MB of DRAM could look like 4140 So a typical memory configuration with 16 MB of DRAM could look like
4136 this: 4141 this:
4137 4142
4138 0x0000 0000 Exception Vector code 4143 0x0000 0000 Exception Vector code
4139 : 4144 :
4140 0x0000 1FFF 4145 0x0000 1FFF
4141 0x0000 2000 Free for Application Use 4146 0x0000 2000 Free for Application Use
4142 : 4147 :
4143 : 4148 :
4144 4149
4145 : 4150 :
4146 : 4151 :
4147 0x00FB FF20 Monitor Stack (Growing downward) 4152 0x00FB FF20 Monitor Stack (Growing downward)
4148 0x00FB FFAC Board Info Data and permanent copy of global data 4153 0x00FB FFAC Board Info Data and permanent copy of global data
4149 0x00FC 0000 Malloc Arena 4154 0x00FC 0000 Malloc Arena
4150 : 4155 :
4151 0x00FD FFFF 4156 0x00FD FFFF
4152 0x00FE 0000 RAM Copy of Monitor Code 4157 0x00FE 0000 RAM Copy of Monitor Code
4153 ... eventually: LCD or video framebuffer 4158 ... eventually: LCD or video framebuffer
4154 ... eventually: pRAM (Protected RAM - unchanged by reset) 4159 ... eventually: pRAM (Protected RAM - unchanged by reset)
4155 0x00FF FFFF [End of RAM] 4160 0x00FF FFFF [End of RAM]
4156 4161
4157 4162
4158 System Initialization: 4163 System Initialization:
4159 ---------------------- 4164 ----------------------
4160 4165
4161 In the reset configuration, U-Boot starts at the reset entry point 4166 In the reset configuration, U-Boot starts at the reset entry point
4162 (on most PowerPC systems at address 0x00000100). Because of the reset 4167 (on most PowerPC systems at address 0x00000100). Because of the reset
4163 configuration for CS0# this is a mirror of the onboard Flash memory. 4168 configuration for CS0# this is a mirror of the onboard Flash memory.
4164 To be able to re-map memory U-Boot then jumps to its link address. 4169 To be able to re-map memory U-Boot then jumps to its link address.
4165 To be able to implement the initialization code in C, a (small!) 4170 To be able to implement the initialization code in C, a (small!)
4166 initial stack is set up in the internal Dual Ported RAM (in case CPUs 4171 initial stack is set up in the internal Dual Ported RAM (in case CPUs
4167 which provide such a feature like MPC8xx or MPC8260), or in a locked 4172 which provide such a feature like MPC8xx or MPC8260), or in a locked
4168 part of the data cache. After that, U-Boot initializes the CPU core, 4173 part of the data cache. After that, U-Boot initializes the CPU core,
4169 the caches and the SIU. 4174 the caches and the SIU.
4170 4175
4171 Next, all (potentially) available memory banks are mapped using a 4176 Next, all (potentially) available memory banks are mapped using a
4172 preliminary mapping. For example, we put them on 512 MB boundaries 4177 preliminary mapping. For example, we put them on 512 MB boundaries
4173 (multiples of 0x20000000: SDRAM on 0x00000000 and 0x20000000, Flash 4178 (multiples of 0x20000000: SDRAM on 0x00000000 and 0x20000000, Flash
4174 on 0x40000000 and 0x60000000, SRAM on 0x80000000). Then UPM A is 4179 on 0x40000000 and 0x60000000, SRAM on 0x80000000). Then UPM A is
4175 programmed for SDRAM access. Using the temporary configuration, a 4180 programmed for SDRAM access. Using the temporary configuration, a
4176 simple memory test is run that determines the size of the SDRAM 4181 simple memory test is run that determines the size of the SDRAM
4177 banks. 4182 banks.
4178 4183
4179 When there is more than one SDRAM bank, and the banks are of 4184 When there is more than one SDRAM bank, and the banks are of
4180 different size, the largest is mapped first. For equal size, the first 4185 different size, the largest is mapped first. For equal size, the first
4181 bank (CS2#) is mapped first. The first mapping is always for address 4186 bank (CS2#) is mapped first. The first mapping is always for address
4182 0x00000000, with any additional banks following immediately to create 4187 0x00000000, with any additional banks following immediately to create
4183 contiguous memory starting from 0. 4188 contiguous memory starting from 0.
4184 4189
4185 Then, the monitor installs itself at the upper end of the SDRAM area 4190 Then, the monitor installs itself at the upper end of the SDRAM area
4186 and allocates memory for use by malloc() and for the global Board 4191 and allocates memory for use by malloc() and for the global Board
4187 Info data; also, the exception vector code is copied to the low RAM 4192 Info data; also, the exception vector code is copied to the low RAM
4188 pages, and the final stack is set up. 4193 pages, and the final stack is set up.
4189 4194
4190 Only after this relocation will you have a "normal" C environment; 4195 Only after this relocation will you have a "normal" C environment;
4191 until that you are restricted in several ways, mostly because you are 4196 until that you are restricted in several ways, mostly because you are
4192 running from ROM, and because the code will have to be relocated to a 4197 running from ROM, and because the code will have to be relocated to a
4193 new address in RAM. 4198 new address in RAM.
4194 4199
4195 4200
4196 U-Boot Porting Guide: 4201 U-Boot Porting Guide:
4197 ---------------------- 4202 ----------------------
4198 4203
4199 [Based on messages by Jerry Van Baren in the U-Boot-Users mailing 4204 [Based on messages by Jerry Van Baren in the U-Boot-Users mailing
4200 list, October 2002] 4205 list, October 2002]
4201 4206
4202 4207
4203 int main(int argc, char *argv[]) 4208 int main(int argc, char *argv[])
4204 { 4209 {
4205 sighandler_t no_more_time; 4210 sighandler_t no_more_time;
4206 4211
4207 signal(SIGALRM, no_more_time); 4212 signal(SIGALRM, no_more_time);
4208 alarm(PROJECT_DEADLINE - toSec (3 * WEEK)); 4213 alarm(PROJECT_DEADLINE - toSec (3 * WEEK));
4209 4214
4210 if (available_money > available_manpower) { 4215 if (available_money > available_manpower) {
4211 Pay consultant to port U-Boot; 4216 Pay consultant to port U-Boot;
4212 return 0; 4217 return 0;
4213 } 4218 }
4214 4219
4215 Download latest U-Boot source; 4220 Download latest U-Boot source;
4216 4221
4217 Subscribe to u-boot mailing list; 4222 Subscribe to u-boot mailing list;
4218 4223
4219 if (clueless) 4224 if (clueless)
4220 email("Hi, I am new to U-Boot, how do I get started?"); 4225 email("Hi, I am new to U-Boot, how do I get started?");
4221 4226
4222 while (learning) { 4227 while (learning) {
4223 Read the README file in the top level directory; 4228 Read the README file in the top level directory;
4224 Read http://www.denx.de/twiki/bin/view/DULG/Manual; 4229 Read http://www.denx.de/twiki/bin/view/DULG/Manual;
4225 Read applicable doc/*.README; 4230 Read applicable doc/*.README;
4226 Read the source, Luke; 4231 Read the source, Luke;
4227 /* find . -name "*.[chS]" | xargs grep -i <keyword> */ 4232 /* find . -name "*.[chS]" | xargs grep -i <keyword> */
4228 } 4233 }
4229 4234
4230 if (available_money > toLocalCurrency ($2500)) 4235 if (available_money > toLocalCurrency ($2500))
4231 Buy a BDI3000; 4236 Buy a BDI3000;
4232 else 4237 else
4233 Add a lot of aggravation and time; 4238 Add a lot of aggravation and time;
4234 4239
4235 if (a similar board exists) { /* hopefully... */ 4240 if (a similar board exists) { /* hopefully... */
4236 cp -a board/<similar> board/<myboard> 4241 cp -a board/<similar> board/<myboard>
4237 cp include/configs/<similar>.h include/configs/<myboard>.h 4242 cp include/configs/<similar>.h include/configs/<myboard>.h
4238 } else { 4243 } else {
4239 Create your own board support subdirectory; 4244 Create your own board support subdirectory;
4240 Create your own board include/configs/<myboard>.h file; 4245 Create your own board include/configs/<myboard>.h file;
4241 } 4246 }
4242 Edit new board/<myboard> files 4247 Edit new board/<myboard> files
4243 Edit new include/configs/<myboard>.h 4248 Edit new include/configs/<myboard>.h
4244 4249
4245 while (!accepted) { 4250 while (!accepted) {
4246 while (!running) { 4251 while (!running) {
4247 do { 4252 do {
4248 Add / modify source code; 4253 Add / modify source code;
4249 } until (compiles); 4254 } until (compiles);
4250 Debug; 4255 Debug;
4251 if (clueless) 4256 if (clueless)
4252 email("Hi, I am having problems..."); 4257 email("Hi, I am having problems...");
4253 } 4258 }
4254 Send patch file to the U-Boot email list; 4259 Send patch file to the U-Boot email list;
4255 if (reasonable critiques) 4260 if (reasonable critiques)
4256 Incorporate improvements from email list code review; 4261 Incorporate improvements from email list code review;
4257 else 4262 else
4258 Defend code as written; 4263 Defend code as written;
4259 } 4264 }
4260 4265
4261 return 0; 4266 return 0;
4262 } 4267 }
4263 4268
4264 void no_more_time (int sig) 4269 void no_more_time (int sig)
4265 { 4270 {
4266 hire_a_guru(); 4271 hire_a_guru();
4267 } 4272 }
4268 4273
4269 4274
4270 Coding Standards: 4275 Coding Standards:
4271 ----------------- 4276 -----------------
4272 4277
4273 All contributions to U-Boot should conform to the Linux kernel 4278 All contributions to U-Boot should conform to the Linux kernel
4274 coding style; see the file "Documentation/CodingStyle" and the script 4279 coding style; see the file "Documentation/CodingStyle" and the script
4275 "scripts/Lindent" in your Linux kernel source directory. In sources 4280 "scripts/Lindent" in your Linux kernel source directory. In sources
4276 originating from U-Boot a style corresponding to "Lindent -pcs" (adding 4281 originating from U-Boot a style corresponding to "Lindent -pcs" (adding
4277 spaces before parameters to function calls) is actually used. 4282 spaces before parameters to function calls) is actually used.
4278 4283
4279 Source files originating from a different project (for example the 4284 Source files originating from a different project (for example the
4280 MTD subsystem) are generally exempt from these guidelines and are not 4285 MTD subsystem) are generally exempt from these guidelines and are not
4281 reformated to ease subsequent migration to newer versions of those 4286 reformated to ease subsequent migration to newer versions of those
4282 sources. 4287 sources.
4283 4288
4284 Please note that U-Boot is implemented in C (and to some small parts in 4289 Please note that U-Boot is implemented in C (and to some small parts in
4285 Assembler); no C++ is used, so please do not use C++ style comments (//) 4290 Assembler); no C++ is used, so please do not use C++ style comments (//)
4286 in your code. 4291 in your code.
4287 4292
4288 Please also stick to the following formatting rules: 4293 Please also stick to the following formatting rules:
4289 - remove any trailing white space 4294 - remove any trailing white space
4290 - use TAB characters for indentation, not spaces 4295 - use TAB characters for indentation, not spaces
4291 - make sure NOT to use DOS '\r\n' line feeds 4296 - make sure NOT to use DOS '\r\n' line feeds
4292 - do not add more than 2 empty lines to source files 4297 - do not add more than 2 empty lines to source files
4293 - do not add trailing empty lines to source files 4298 - do not add trailing empty lines to source files
4294 4299
4295 Submissions which do not conform to the standards may be returned 4300 Submissions which do not conform to the standards may be returned
4296 with a request to reformat the changes. 4301 with a request to reformat the changes.
4297 4302
4298 4303
4299 Submitting Patches: 4304 Submitting Patches:
4300 ------------------- 4305 -------------------
4301 4306
4302 Since the number of patches for U-Boot is growing, we need to 4307 Since the number of patches for U-Boot is growing, we need to
4303 establish some rules. Submissions which do not conform to these rules 4308 establish some rules. Submissions which do not conform to these rules
4304 may be rejected, even when they contain important and valuable stuff. 4309 may be rejected, even when they contain important and valuable stuff.
4305 4310
4306 Please see http://www.denx.de/wiki/U-Boot/Patches for details. 4311 Please see http://www.denx.de/wiki/U-Boot/Patches for details.
4307 4312
4308 Patches shall be sent to the u-boot mailing list <u-boot@lists.denx.de>; 4313 Patches shall be sent to the u-boot mailing list <u-boot@lists.denx.de>;
4309 see http://lists.denx.de/mailman/listinfo/u-boot 4314 see http://lists.denx.de/mailman/listinfo/u-boot
4310 4315
4311 When you send a patch, please include the following information with 4316 When you send a patch, please include the following information with
4312 it: 4317 it:
4313 4318
4314 * For bug fixes: a description of the bug and how your patch fixes 4319 * For bug fixes: a description of the bug and how your patch fixes
4315 this bug. Please try to include a way of demonstrating that the 4320 this bug. Please try to include a way of demonstrating that the
4316 patch actually fixes something. 4321 patch actually fixes something.
4317 4322
4318 * For new features: a description of the feature and your 4323 * For new features: a description of the feature and your
4319 implementation. 4324 implementation.
4320 4325
4321 * A CHANGELOG entry as plaintext (separate from the patch) 4326 * A CHANGELOG entry as plaintext (separate from the patch)
4322 4327
4323 * For major contributions, your entry to the CREDITS file 4328 * For major contributions, your entry to the CREDITS file
4324 4329
4325 * When you add support for a new board, don't forget to add this 4330 * When you add support for a new board, don't forget to add this
4326 board to the MAKEALL script, too. 4331 board to the MAKEALL script, too.
4327 4332
4328 * If your patch adds new configuration options, don't forget to 4333 * If your patch adds new configuration options, don't forget to
4329 document these in the README file. 4334 document these in the README file.
4330 4335
4331 * The patch itself. If you are using git (which is *strongly* 4336 * The patch itself. If you are using git (which is *strongly*
4332 recommended) you can easily generate the patch using the 4337 recommended) you can easily generate the patch using the
4333 "git-format-patch". If you then use "git-send-email" to send it to 4338 "git-format-patch". If you then use "git-send-email" to send it to
4334 the U-Boot mailing list, you will avoid most of the common problems 4339 the U-Boot mailing list, you will avoid most of the common problems
4335 with some other mail clients. 4340 with some other mail clients.
4336 4341
4337 If you cannot use git, use "diff -purN OLD NEW". If your version of 4342 If you cannot use git, use "diff -purN OLD NEW". If your version of
4338 diff does not support these options, then get the latest version of 4343 diff does not support these options, then get the latest version of
4339 GNU diff. 4344 GNU diff.
4340 4345
4341 The current directory when running this command shall be the parent 4346 The current directory when running this command shall be the parent
4342 directory of the U-Boot source tree (i. e. please make sure that 4347 directory of the U-Boot source tree (i. e. please make sure that
4343 your patch includes sufficient directory information for the 4348 your patch includes sufficient directory information for the
4344 affected files). 4349 affected files).
4345 4350
4346 We prefer patches as plain text. MIME attachments are discouraged, 4351 We prefer patches as plain text. MIME attachments are discouraged,
4347 and compressed attachments must not be used. 4352 and compressed attachments must not be used.
4348 4353
4349 * If one logical set of modifications affects or creates several 4354 * If one logical set of modifications affects or creates several
4350 files, all these changes shall be submitted in a SINGLE patch file. 4355 files, all these changes shall be submitted in a SINGLE patch file.
4351 4356
4352 * Changesets that contain different, unrelated modifications shall be 4357 * Changesets that contain different, unrelated modifications shall be
4353 submitted as SEPARATE patches, one patch per changeset. 4358 submitted as SEPARATE patches, one patch per changeset.
4354 4359
4355 4360
4356 Notes: 4361 Notes:
4357 4362
4358 * Before sending the patch, run the MAKEALL script on your patched 4363 * Before sending the patch, run the MAKEALL script on your patched
4359 source tree and make sure that no errors or warnings are reported 4364 source tree and make sure that no errors or warnings are reported
4360 for any of the boards. 4365 for any of the boards.
4361 4366
4362 * Keep your modifications to the necessary minimum: A patch 4367 * Keep your modifications to the necessary minimum: A patch
4363 containing several unrelated changes or arbitrary reformats will be 4368 containing several unrelated changes or arbitrary reformats will be
4364 returned with a request to re-formatting / split it. 4369 returned with a request to re-formatting / split it.
4365 4370
4366 * If you modify existing code, make sure that your new code does not 4371 * If you modify existing code, make sure that your new code does not
4367 add to the memory footprint of the code ;-) Small is beautiful! 4372 add to the memory footprint of the code ;-) Small is beautiful!
4368 When adding new features, these should compile conditionally only 4373 When adding new features, these should compile conditionally only
4369 (using #ifdef), and the resulting code with the new feature 4374 (using #ifdef), and the resulting code with the new feature
4370 disabled must not need more memory than the old code without your 4375 disabled must not need more memory than the old code without your
4371 modification. 4376 modification.
4372 4377
4373 * Remember that there is a size limit of 100 kB per message on the 4378 * Remember that there is a size limit of 100 kB per message on the
4374 u-boot mailing list. Bigger patches will be moderated. If they are 4379 u-boot mailing list. Bigger patches will be moderated. If they are
4375 reasonable and not too big, they will be acknowledged. But patches 4380 reasonable and not too big, they will be acknowledged. But patches
4376 bigger than the size limit should be avoided. 4381 bigger than the size limit should be avoided.
4377 4382
arch/arm/include/asm/arch-armada100/config.h
Diff comments   View file @ cf946c6
File was created 1 /*
2 * (C) Copyright 2011
3 * Marvell Semiconductor <www.marvell.com>
4 * Written-by: Lei Wen <leiwen@marvell.com>
5 *
6 * See file CREDITS for list of people who contributed to this
7 * project.
8 *
9 * This program is free software; you can redistribute it and/or
10 * modify it under the terms of the GNU General Public License as
11 * published by the Free Software Foundation; either version 2 of
12 * the License, or (at your option) any later version.
13 *
14 * This program is distributed in the hope that it will be useful,
15 * but WITHOUT ANY WARRANTY; without even the implied warranty of
16 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
17 * GNU General Public License for more details.
18 *
19 * You should have received a copy of the GNU General Public License
20 * along with this program; if not, write to the Free Software
21 * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
22 * MA 02110-1301 USA
23 */
24
25 /*
26 * This file should be included in board config header file.
27 *
28 * It supports common definitions for Armada100 platform
29 */
30
31 #ifndef _ARMD1_CONFIG_H
32 #define _ARMD1_CONFIG_H
33
34 #define CONFIG_ARM926EJS 1 /* Basic Architecture */
35
36 #define CONFIG_SYS_TCLK (14745600) /* NS16550 clk config */
37 #define CONFIG_SYS_HZ_CLOCK (3250000) /* Timer Freq. 3.25MHZ */
38 #define CONFIG_MARVELL_MFP /* Enable mvmfp driver */
39 #define MV_MFPR_BASE ARMD1_MFPR_BASE
40 #define MV_UART_CONSOLE_BASE ARMD1_UART1_BASE
41 #define CONFIG_SYS_NS16550_IER (1 << 6) /* Bit 6 in UART_IER register
42 represents UART Unit Enable */
43
44 #endif /* _ARMD1_CONFIG_H */
45
arch/arm/include/asm/arch-kirkwood/config.h
Diff comments   View file @ cf946c6
File was created 1 /*
2 * (C) Copyright 2011
3 * Marvell Semiconductor <www.marvell.com>
4 * Written-by: Lei Wen <leiwen@marvell.com>
5 *
6 * See file CREDITS for list of people who contributed to this
7 * project.
8 *
9 * This program is free software; you can redistribute it and/or
10 * modify it under the terms of the GNU General Public License as
11 * published by the Free Software Foundation; either version 2 of
12 * the License, or (at your option) any later version.
13 *
14 * This program is distributed in the hope that it will be useful,
15 * but WITHOUT ANY WARRANTY; without even the implied warranty of
16 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
17 * GNU General Public License for more details.
18 *
19 * You should have received a copy of the GNU General Public License
20 * along with this program; if not, write to the Free Software
21 * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
22 * MA 02110-1301 USA
23 */
24
25 /*
26 * This file should be included in board config header file.
27 *
28 * It supports common definitions for Kirkwood platform
29 */
30
31 #ifndef _KW_CONFIG_H
32 #define _KW_CONFIG_H
33
34 #if defined (CONFIG_KW88F6281)
35 #include <asm/arch/kw88f6281.h>
36 #elif defined (CONFIG_KW88F6192)
37 #include <asm/arch/kw88f6192.h>
38 #else
39 #error "SOC Name not defined"
40 #endif /* CONFIG_KW88F6281 */
41
42 #define CONFIG_ARM926EJS 1 /* Basic Architecture */
43
44 #define CONFIG_MD5 /* get_random_hex on krikwood needs MD5 support */
45 #define CONFIG_KIRKWOOD_EGIGA_INIT /* Enable GbePort0/1 for kernel */
46 #define CONFIG_KIRKWOOD_RGMII_PAD_1V8 /* Set RGMII Pad voltage to 1.8V */
47 #define CONFIG_KIRKWOOD_PCIE_INIT /* Enable PCIE Port0 for kernel */
48
49 /*
50 * By default kwbimage.cfg from board specific folder is used
51 * If for some board, different configuration file need to be used,
52 * CONFIG_SYS_KWD_CONFIG should be defined in board specific header file
53 */
54 #ifndef CONFIG_SYS_KWD_CONFIG
55 #define CONFIG_SYS_KWD_CONFIG $(SRCTREE)/$(CONFIG_BOARDDIR)/kwbimage.cfg
56 #endif /* CONFIG_SYS_KWD_CONFIG */
57
58 /* Kirkwood has 2k of Security SRAM, use it for SP */
59 #define CONFIG_SYS_INIT_SP_ADDR 0xC8012000
60 #define CONFIG_NR_DRAM_BANKS_MAX 2
61
62 #define CONFIG_I2C_MVTWSI_BASE KW_TWSI_BASE
63 #define MV_UART_CONSOLE_BASE KW_UART0_BASE
64 #define MV_SATA_BASE KW_SATA_BASE
65 #define MV_SATA_PORT0_OFFSET KW_SATA_PORT0_OFFSET
66 #define MV_SATA_PORT1_OFFSET KW_SATA_PORT1_OFFSET
67
68 /*
69 * NAND configuration
70 */
71 #ifdef CONFIG_CMD_NAND
72 #define CONFIG_NAND_KIRKWOOD
73 #define CONFIG_SYS_NAND_BASE 0xD8000000 /* MV_DEFADR_NANDF */
74 #define NAND_ALLOW_ERASE_ALL 1
75 #endif
76
77 /*
78 * SPI Flash configuration
79 */
80 #ifdef CONFIG_CMD_SF
81 #define CONFIG_HARD_SPI 1
82 #define CONFIG_KIRKWOOD_SPI 1
83 #define CONFIG_ENV_SPI_BUS 0
84 #define CONFIG_ENV_SPI_CS 0
85 #define CONFIG_ENV_SPI_MAX_HZ 50000000 /*50Mhz */
86 #endif
87
88 /*
89 * Ethernet Driver configuration
90 */
91 #ifdef CONFIG_CMD_NET
92 #define CONFIG_CMD_MII
93 #define CONFIG_NETCONSOLE /* include NetConsole support */
94 #define CONFIG_NET_MULTI /* specify more that one ports available */
95 #define CONFIG_MII /* expose smi ove miiphy interface */
96 #define CONFIG_MVGBE /* Enable Marvell Gbe Controller Driver */
97 #define CONFIG_SYS_FAULT_ECHO_LINK_DOWN /* detect link using phy */
98 #define CONFIG_ENV_OVERWRITE /* ethaddr can be reprogrammed */
99 #define CONFIG_RESET_PHY_R /* use reset_phy() to init mv8831116 PHY */
100 #endif /* CONFIG_CMD_NET */
101
102 /*
103 * USB/EHCI
104 */
105 #ifdef CONFIG_CMD_USB
106 #define CONFIG_USB_EHCI_KIRKWOOD
107 #define CONFIG_EHCI_IS_TDI
108 #endif /* CONFIG_CMD_USB */
109
110 /*
111 * IDE Support on SATA ports
112 */
113 #ifdef CONFIG_CMD_IDE
114 #define __io
115 #define CONFIG_CMD_EXT2
116 #define CONFIG_MVSATA_IDE
117 #define CONFIG_IDE_PREINIT
118 #define CONFIG_MVSATA_IDE_USE_PORT1
119 /* Needs byte-swapping for ATA data register */
120 #define CONFIG_IDE_SWAP_IO
121 /* Data, registers and alternate blocks are at the same offset */
122 #define CONFIG_SYS_ATA_DATA_OFFSET (0x0100)
123 #define CONFIG_SYS_ATA_REG_OFFSET (0x0100)
124 #define CONFIG_SYS_ATA_ALT_OFFSET (0x0100)
125 /* Each 8-bit ATA register is aligned to a 4-bytes address */
126 #define CONFIG_SYS_ATA_STRIDE 4
127 /* Controller supports 48-bits LBA addressing */
128 #define CONFIG_LBA48
129 /* CONFIG_CMD_IDE requires some #defines for ATA registers */
130 #define CONFIG_SYS_IDE_MAXBUS 2
131 #define CONFIG_SYS_IDE_MAXDEVICE 2
132 /* ATA registers base is at SATA controller base */
133 #define CONFIG_SYS_ATA_BASE_ADDR MV_SATA_BASE
134 #endif /* CONFIG_CMD_IDE */
135
136 /*
137 * I2C related stuff
138 */
139 #ifdef CONFIG_CMD_I2C
140 #define CONFIG_I2C_MVTWSI
141 #define CONFIG_SYS_I2C_SLAVE 0x0
142 #define CONFIG_SYS_I2C_SPEED 100000
143 #endif
144
145 #endif /* _KW_CONFIG_H */
146
include/configs/aspenite.h
Diff comments   View file @ cf946c6
1 /* 1 /*
2 * (C) Copyright 2010 2 * (C) Copyright 2010
3 * Marvell Semiconductor <www.marvell.com> 3 * Marvell Semiconductor <www.marvell.com>
4 * Written-by: Prafulla Wadaskar <prafulla@marvell.com> 4 * Written-by: Prafulla Wadaskar <prafulla@marvell.com>
5 * Contributor: Mahavir Jain <mjain@marvell.com> 5 * Contributor: Mahavir Jain <mjain@marvell.com>
6 * 6 *
7 * See file CREDITS for list of people who contributed to this 7 * See file CREDITS for list of people who contributed to this
8 * project. 8 * project.
9 * 9 *
10 * This program is free software; you can redistribute it and/or 10 * This program is free software; you can redistribute it and/or
11 * modify it under the terms of the GNU General Public License as 11 * modify it under the terms of the GNU General Public License as
12 * published by the Free Software Foundation; either version 2 of 12 * published by the Free Software Foundation; either version 2 of
13 * the License, or (at your option) any later version. 13 * the License, or (at your option) any later version.
14 * 14 *
15 * This program is distributed in the hope that it will be useful, 15 * This program is distributed in the hope that it will be useful,
16 * but WITHOUT ANY WARRANTY; without even the implied warranty of 16 * but WITHOUT ANY WARRANTY; without even the implied warranty of
17 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 17 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
18 * GNU General Public License for more details. 18 * GNU General Public License for more details.
19 * 19 *
20 * You should have received a copy of the GNU General Public License 20 * You should have received a copy of the GNU General Public License
21 * along with this program; if not, write to the Free Software 21 * along with this program; if not, write to the Free Software
22 * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, 22 * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
23 * MA 02110-1301 USA 23 * MA 02110-1301 USA
24 */ 24 */
25 25
26 #ifndef __CONFIG_ASPENITE_H 26 #ifndef __CONFIG_ASPENITE_H
27 #define __CONFIG_ASPENITE_H 27 #define __CONFIG_ASPENITE_H
28 28
29 /* 29 /*
30 * Version number information 30 * Version number information
31 */ 31 */
32 #define CONFIG_IDENT_STRING "\nMarvell-Aspenite DB" 32 #define CONFIG_IDENT_STRING "\nMarvell-Aspenite DB"
33 33
34 /* 34 /*
35 * High Level Configuration Options 35 * High Level Configuration Options
36 */ 36 */
37 #define CONFIG_SHEEVA_88SV331xV5 1 /* CPU Core subversion */ 37 #define CONFIG_SHEEVA_88SV331xV5 1 /* CPU Core subversion */
38 #define CONFIG_ARMADA100 1 /* SOC Family Name */ 38 #define CONFIG_ARMADA100 1 /* SOC Family Name */
39 #define CONFIG_ARMADA168 1 /* SOC Used on this Board */ 39 #define CONFIG_ARMADA168 1 /* SOC Used on this Board */
40 #define CONFIG_MACH_ASPENITE /* Machine type */ 40 #define CONFIG_MACH_ASPENITE /* Machine type */
41 #define CONFIG_SKIP_LOWLEVEL_INIT /* disable board lowlevel_init */ 41 #define CONFIG_SKIP_LOWLEVEL_INIT /* disable board lowlevel_init */
42 42
43 /* 43 /*
44 * There is no internal RAM in ARMADA100, using DRAM
45 * TBD: dcache to be used for this
46 */
47 #define CONFIG_SYS_INIT_SP_ADDR (CONFIG_SYS_TEXT_BASE - 0x00200000)
48 #define CONFIG_NR_DRAM_BANKS_MAX 2
49
50 /*
44 * Commands configuration 51 * Commands configuration
45 */ 52 */
46 #define CONFIG_SYS_NO_FLASH /* Declare no flash (NOR/SPI) */ 53 #define CONFIG_SYS_NO_FLASH /* Declare no flash (NOR/SPI) */
47 #include <config_cmd_default.h> 54 #include <config_cmd_default.h>
48 #define CONFIG_CMD_AUTOSCRIPT 55 #define CONFIG_CMD_AUTOSCRIPT
49 #undef CONFIG_CMD_NET 56 #undef CONFIG_CMD_NET
50 #undef CONFIG_CMD_NFS 57 #undef CONFIG_CMD_NFS
51 /* 58 /*
52 * mv-common.h should be defined after CMD configs since it used them 59 * mv-common.h should be defined after CMD configs since it used them
53 * to enable certain macros 60 * to enable certain macros
54 */ 61 */
55 #include "mv-common.h" 62 #include "mv-common.h"
63 #undef CONFIG_ARCH_MISC_INIT
56 64
57 /* 65 /*
58 * Environment variables configurations 66 * Environment variables configurations
59 */ 67 */
60 #define CONFIG_ENV_IS_NOWHERE 1 /* if env in SDRAM */ 68 #define CONFIG_ENV_IS_NOWHERE 1 /* if env in SDRAM */
61 #define CONFIG_ENV_SIZE 0x20000 /* 64k */ 69 #define CONFIG_ENV_SIZE 0x20000 /* 64k */
62 70
63 #endif /* __CONFIG_ASPENITE_H */ 71 #endif /* __CONFIG_ASPENITE_H */
64 72
include/configs/mv-common.h
Diff comments   View file @ cf946c6
1 /* 1 /*
2 * (C) Copyright 2010 2 * (C) Copyright 2010
3 * Marvell Semiconductor <www.marvell.com> 3 * Marvell Semiconductor <www.marvell.com>
4 * Written-by: Prafulla Wadaskar <prafulla@marvell.com> 4 * Written-by: Prafulla Wadaskar <prafulla@marvell.com>
5 * 5 *
6 * See file CREDITS for list of people who contributed to this 6 * See file CREDITS for list of people who contributed to this
7 * project. 7 * project.
8 * 8 *
9 * This program is free software; you can redistribute it and/or 9 * This program is free software; you can redistribute it and/or
10 * modify it under the terms of the GNU General Public License as 10 * modify it under the terms of the GNU General Public License as
11 * published by the Free Software Foundation; either version 2 of 11 * published by the Free Software Foundation; either version 2 of
12 * the License, or (at your option) any later version. 12 * the License, or (at your option) any later version.
13 * 13 *
14 * This program is distributed in the hope that it will be useful, 14 * This program is distributed in the hope that it will be useful,
15 * but WITHOUT ANY WARRANTY; without even the implied warranty of 15 * but WITHOUT ANY WARRANTY; without even the implied warranty of
16 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 16 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
17 * GNU General Public License for more details. 17 * GNU General Public License for more details.
18 * 18 *
19 * You should have received a copy of the GNU General Public License 19 * You should have received a copy of the GNU General Public License
20 * along with this program; if not, write to the Free Software 20 * along with this program; if not, write to the Free Software
21 * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, 21 * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
22 * MA 02110-1301 USA 22 * MA 02110-1301 USA
23 */ 23 */
24 24
25 /* 25 /*
26 * This file contains Marvell Board Specific common defincations. 26 * This file contains Marvell Board Specific common defincations.
27 * This file should be included in board config header file. 27 * This file should be included in board config header file.
28 * 28 *
29 * It supports common definations for Kirkwood platform 29 * It supports common definations for Kirkwood platform
30 * TBD: support for Orion5X platforms 30 * TBD: support for Orion5X platforms
31 */ 31 */
32 32
33 #ifndef _MV_COMMON_H 33 #ifndef _MV_COMMON_H
34 #define _MV_COMMON_H 34 #define _MV_COMMON_H
35 35
36 /* 36 /*
37 * High Level Configuration Options (easy to change) 37 * High Level Configuration Options (easy to change)
38 */ 38 */
39 #define CONFIG_MARVELL 1 39 #define CONFIG_MARVELL 1
40 #define CONFIG_ARM926EJS 1 /* Basic Architecture */
41 40
42 /* ====> Kirkwood Platform Common Definations */
43 #if defined(CONFIG_KIRKWOOD)
44 #define CONFIG_MD5 /* get_random_hex on krikwood needs MD5 support */
45 #define CONFIG_KIRKWOOD_EGIGA_INIT /* Enable GbePort0/1 for kernel */
46 #define CONFIG_KIRKWOOD_RGMII_PAD_1V8 /* Set RGMII Pad voltage to 1.8V */
47 #define CONFIG_KIRKWOOD_PCIE_INIT /* Enable PCIE Port0 for kernel */
48
49 /* 41 /*
50 * By default kwbimage.cfg from board specific folder is used
51 * If for some board, different configuration file need to be used,
52 * CONFIG_SYS_KWD_CONFIG should be defined in board specific header file
53 */
54 #ifndef CONFIG_SYS_KWD_CONFIG
55 #define CONFIG_SYS_KWD_CONFIG $(SRCTREE)/$(CONFIG_BOARDDIR)/kwbimage.cfg
56 #endif /* CONFIG_SYS_KWD_CONFIG */
57
58 /* Kirkwood has 2k of Security SRAM, use it for SP */
59 #define CONFIG_SYS_INIT_SP_ADDR 0xC8012000
60 #define CONFIG_NR_DRAM_BANKS_MAX 2
61
62 #define CONFIG_I2C_MVTWSI_BASE KW_TWSI_BASE
63 #define MV_UART_CONSOLE_BASE KW_UART0_BASE
64 #define MV_SATA_BASE KW_SATA_BASE
65 #define MV_SATA_PORT0_OFFSET KW_SATA_PORT0_OFFSET
66 #define MV_SATA_PORT1_OFFSET KW_SATA_PORT1_OFFSET
67
68 /* ====> ARMADA100 Platform Common Definations */
69 #elif defined (CONFIG_ARMADA100)
70
71 #define CONFIG_SYS_TCLK (14745600) /* NS16550 clk config */
72 #define CONFIG_SYS_HZ_CLOCK (3250000) /* Timer Freq. 3.25MHZ */
73 #define CONFIG_MARVELL_MFP /* Enable mvmfp driver */
74 #define MV_MFPR_BASE ARMD1_MFPR_BASE
75 #define MV_UART_CONSOLE_BASE ARMD1_UART1_BASE
76 #define CONFIG_SYS_NS16550_IER (1 << 6) /* Bit 6 in UART_IER register
77 represents UART Unit Enable */
78 /*
79 * There is no internal RAM in ARMADA100, using DRAM
80 * TBD: dcache to be used for this
81 */
82 #define CONFIG_SYS_INIT_SP_ADDR (CONFIG_SYS_TEXT_BASE - 0x00200000)
83 #define CONFIG_NR_DRAM_BANKS_MAX 2
84
85 #else
86 #error "Unsupported SoC Platform..."
87 #endif
88
89 /*
90 * Custom CONFIG_SYS_TEXT_BASE can be done in <board>.h 42 * Custom CONFIG_SYS_TEXT_BASE can be done in <board>.h
91 */ 43 */
92 #ifndef CONFIG_SYS_TEXT_BASE 44 #ifndef CONFIG_SYS_TEXT_BASE
93 #define CONFIG_SYS_TEXT_BASE 0x00600000 45 #define CONFIG_SYS_TEXT_BASE 0x00600000
94 #endif /* CONFIG_SYS_TEXT_BASE */ 46 #endif /* CONFIG_SYS_TEXT_BASE */
95 47
96 /* additions for new ARM relocation support */ 48 /* additions for new ARM relocation support */
97 #define CONFIG_SYS_SDRAM_BASE 0x00000000 49 #define CONFIG_SYS_SDRAM_BASE 0x00000000
98 50
99 /* 51 /*
100 * CLKs configurations 52 * CLKs configurations
101 */ 53 */
102 #define CONFIG_SYS_HZ 1000 54 #define CONFIG_SYS_HZ 1000
103 55
104 /* 56 /*
105 * NS16550 Configuration 57 * NS16550 Configuration
106 */ 58 */
107 #define CONFIG_SYS_NS16550 59 #define CONFIG_SYS_NS16550
108 #define CONFIG_SYS_NS16550_SERIAL 60 #define CONFIG_SYS_NS16550_SERIAL
109 #define CONFIG_SYS_NS16550_REG_SIZE (-4) 61 #define CONFIG_SYS_NS16550_REG_SIZE (-4)
110 #define CONFIG_SYS_NS16550_CLK CONFIG_SYS_TCLK 62 #define CONFIG_SYS_NS16550_CLK CONFIG_SYS_TCLK
111 #define CONFIG_SYS_NS16550_COM1 MV_UART_CONSOLE_BASE 63 #define CONFIG_SYS_NS16550_COM1 MV_UART_CONSOLE_BASE
112 64
113 /* 65 /*
114 * Serial Port configuration 66 * Serial Port configuration
115 * The following definitions let you select what serial you want to use 67 * The following definitions let you select what serial you want to use
116 * for your console driver. 68 * for your console driver.
117 */ 69 */
118 70
119 #define CONFIG_CONS_INDEX 1 /*Console on UART0 */ 71 #define CONFIG_CONS_INDEX 1 /*Console on UART0 */
120 #define CONFIG_BAUDRATE 115200 72 #define CONFIG_BAUDRATE 115200
121 #define CONFIG_SYS_BAUDRATE_TABLE { 9600, 19200, 38400, 57600, \ 73 #define CONFIG_SYS_BAUDRATE_TABLE { 9600, 19200, 38400, 57600, \
122 115200,230400, 460800, 921600 } 74 115200,230400, 460800, 921600 }
123 /* auto boot */ 75 /* auto boot */
124 #define CONFIG_BOOTDELAY 3 /* default enable autoboot */ 76 #define CONFIG_BOOTDELAY 3 /* default enable autoboot */
125 77
126 /* 78 /*
127 * For booting Linux, the board info and command line data 79 * For booting Linux, the board info and command line data
128 * have to be in the first 8 MB of memory, since this is 80 * have to be in the first 8 MB of memory, since this is
129 * the maximum mapped by the Linux kernel during initialization. 81 * the maximum mapped by the Linux kernel during initialization.
130 */ 82 */
131 #define CONFIG_CMDLINE_TAG 1 /* enable passing of ATAGs */ 83 #define CONFIG_CMDLINE_TAG 1 /* enable passing of ATAGs */
132 #define CONFIG_INITRD_TAG 1 /* enable INITRD tag */ 84 #define CONFIG_INITRD_TAG 1 /* enable INITRD tag */
133 #define CONFIG_SETUP_MEMORY_TAGS 1 /* enable memory tag */ 85 #define CONFIG_SETUP_MEMORY_TAGS 1 /* enable memory tag */
134 86
135 #define CONFIG_SYS_PROMPT "Marvell>> " /* Command Prompt */ 87 #define CONFIG_SYS_PROMPT "Marvell>> " /* Command Prompt */
136 #define CONFIG_SYS_CBSIZE 1024 /* Console I/O Buff Size */ 88 #define CONFIG_SYS_CBSIZE 1024 /* Console I/O Buff Size */
137 #define CONFIG_SYS_PBSIZE (CONFIG_SYS_CBSIZE \ 89 #define CONFIG_SYS_PBSIZE (CONFIG_SYS_CBSIZE \
138 +sizeof(CONFIG_SYS_PROMPT) + 16) /* Print Buff */ 90 +sizeof(CONFIG_SYS_PROMPT) + 16) /* Print Buff */
139 91
140 /* 92 /*
141 * NAND configuration
142 */
143 #ifdef CONFIG_CMD_NAND
144 #define CONFIG_NAND_KIRKWOOD
145 #define CONFIG_SYS_MAX_NAND_DEVICE 1
146 #define NAND_MAX_CHIPS 1
147 #define CONFIG_SYS_NAND_BASE 0xD8000000 /* MV_DEFADR_NANDF */
148 #define NAND_ALLOW_ERASE_ALL 1
149 #define CONFIG_SYS_64BIT_VSPRINTF /* needed for nand_util.c */
150 #endif
151
152 /*
153 * SPI Flash configuration
154 */
155 #ifdef CONFIG_CMD_SF
156 #define CONFIG_SPI_FLASH 1
157 #define CONFIG_HARD_SPI 1
158 #define CONFIG_KIRKWOOD_SPI 1
159 #define CONFIG_SPI_FLASH_MACRONIX 1
160 #define CONFIG_ENV_SPI_BUS 0
161 #define CONFIG_ENV_SPI_CS 0
162 #define CONFIG_ENV_SPI_MAX_HZ 50000000 /*50Mhz */
163 #endif
164
165 /*
166 * Size of malloc() pool 93 * Size of malloc() pool
167 */ 94 */
168 #define CONFIG_SYS_MALLOC_LEN (1024 * 1024) /* 1MiB for malloc() */ 95 #define CONFIG_SYS_MALLOC_LEN (1024 * 1024) /* 1MiB for malloc() */
169 /* size in bytes reserved for initial data */ 96 /* size in bytes reserved for initial data */
170 97
171 /* 98 /*
172 * Other required minimal configurations 99 * Other required minimal configurations
173 */ 100 */
174 #define CONFIG_SYS_LONGHELP 101 #define CONFIG_SYS_LONGHELP
175 #define CONFIG_AUTO_COMPLETE 102 #define CONFIG_AUTO_COMPLETE
176 #define CONFIG_CMDLINE_EDITING 103 #define CONFIG_CMDLINE_EDITING
177 #define CONFIG_CONSOLE_INFO_QUIET /* some code reduction */ 104 #define CONFIG_CONSOLE_INFO_QUIET /* some code reduction */
178 #define CONFIG_ARCH_CPU_INIT /* call arch_cpu_init() */ 105 #define CONFIG_ARCH_CPU_INIT /* call arch_cpu_init() */
179 #ifndef CONFIG_ARMADA100 /* will be removed latter */
180 #define CONFIG_ARCH_MISC_INIT /* call arch_misc_init() */ 106 #define CONFIG_ARCH_MISC_INIT /* call arch_misc_init() */
181 #endif /* CONFIG_ARMADA100 */
182 #define CONFIG_BOARD_EARLY_INIT_F /* call board_init_f for early inits */ 107 #define CONFIG_BOARD_EARLY_INIT_F /* call board_init_f for early inits */
183 #define CONFIG_DISPLAY_CPUINFO /* Display cpu info */ 108 #define CONFIG_DISPLAY_CPUINFO /* Display cpu info */
184 #define CONFIG_STACKSIZE 0x00100000 /* regular stack- 1M */ 109 #define CONFIG_STACKSIZE 0x00100000 /* regular stack- 1M */
185 #define CONFIG_SYS_LOAD_ADDR 0x00800000 /* default load adr- 8M */ 110 #define CONFIG_SYS_LOAD_ADDR 0x00800000 /* default load adr- 8M */
186 #define CONFIG_SYS_MEMTEST_START 0x00800000 /* 8M */ 111 #define CONFIG_SYS_MEMTEST_START 0x00800000 /* 8M */
187 #define CONFIG_SYS_MEMTEST_END 0x00ffffff /*(_16M -1) */ 112 #define CONFIG_SYS_MEMTEST_END 0x00ffffff /*(_16M -1) */
188 #define CONFIG_SYS_RESET_ADDRESS 0xffff0000 /* Rst Vector Adr */ 113 #define CONFIG_SYS_RESET_ADDRESS 0xffff0000 /* Rst Vector Adr */
189 #define CONFIG_SYS_MAXARGS 16 /* max number of command args */ 114 #define CONFIG_SYS_MAXARGS 16 /* max number of command args */
190 115
191 /* 116 /*
192 * DRAM Banks configuration, Custom config can be done in <board>.h 117 * DRAM Banks configuration, Custom config can be done in <board>.h
193 */ 118 */
194 #ifndef CONFIG_NR_DRAM_BANKS 119 #ifndef CONFIG_NR_DRAM_BANKS
195 #define CONFIG_NR_DRAM_BANKS CONFIG_NR_DRAM_BANKS_MAX 120 #define CONFIG_NR_DRAM_BANKS CONFIG_NR_DRAM_BANKS_MAX
196 #else 121 #else
197 #if (CONFIG_NR_DRAM_BANKS > CONFIG_NR_DRAM_BANKS_MAX) 122 #if (CONFIG_NR_DRAM_BANKS > CONFIG_NR_DRAM_BANKS_MAX)
198 #error CONFIG_NR_DRAM_BANKS Configurated more than available 123 #error CONFIG_NR_DRAM_BANKS Configurated more than available
199 #endif 124 #endif
200 #endif /* CONFIG_NR_DRAM_BANKS */ 125 #endif /* CONFIG_NR_DRAM_BANKS */
201 126
127 /* ====> Include platform Common Definations */
128 #include <asm/arch/config.h>
129
130 /* ====> Include driver Common Definations */
202 /* 131 /*
203 * Ethernet Driver configuration 132 * Common NAND configuration
204 */ 133 */
205 #ifdef CONFIG_CMD_NET 134 #ifdef CONFIG_CMD_NAND
206 #define CONFIG_CMD_MII 135 #define CONFIG_SYS_MAX_NAND_DEVICE 1
207 #define CONFIG_NETCONSOLE /* include NetConsole support */ 136 #define NAND_MAX_CHIPS 1
208 #define CONFIG_NET_MULTI /* specify more that one ports available */ 137 #define CONFIG_SYS_64BIT_VSPRINTF /* needed for nand_util.c */
209 #define CONFIG_MII /* expose smi ove miiphy interface */ 138 #endif
210 #define CONFIG_MVGBE /* Enable Marvell Gbe Controller Driver */
211 #define CONFIG_SYS_FAULT_ECHO_LINK_DOWN /* detect link using phy */
212 #define CONFIG_ENV_OVERWRITE /* ethaddr can be reprogrammed */
213 #define CONFIG_RESET_PHY_R /* use reset_phy() to init mv8831116 PHY */
214 #endif /* CONFIG_CMD_NET */
215 139
216 /* 140 /*
217 * USB/EHCI 141 * Common SPI Flash configuration
218 */ 142 */
143 #ifdef CONFIG_CMD_SF
144 #define CONFIG_SPI_FLASH 1
145 #define CONFIG_SPI_FLASH_MACRONIX 1
146 #endif
147
148 /*
149 * Common USB/EHCI configuration
150 */
219 #ifdef CONFIG_CMD_USB 151 #ifdef CONFIG_CMD_USB
220 #define CONFIG_USB_EHCI /* Enable EHCI USB support */ 152 #define CONFIG_USB_EHCI /* Enable EHCI USB support */
221 #define CONFIG_USB_EHCI_KIRKWOOD
222 #define CONFIG_EHCI_IS_TDI
223 #define CONFIG_USB_STORAGE 153 #define CONFIG_USB_STORAGE
224 #define CONFIG_DOS_PARTITION 154 #define CONFIG_DOS_PARTITION
225 #define CONFIG_ISO_PARTITION 155 #define CONFIG_ISO_PARTITION
226 #define CONFIG_SUPPORT_VFAT 156 #define CONFIG_SUPPORT_VFAT
227 #endif /* CONFIG_CMD_USB */ 157 #endif /* CONFIG_CMD_USB */
228 158
229 /* 159 /*
230 * IDE Support on SATA ports
231 */
232 #ifdef CONFIG_CMD_IDE
233 #define __io
234 #define CONFIG_CMD_EXT2
235 #define CONFIG_MVSATA_IDE
236 #define CONFIG_IDE_PREINIT
237 #define CONFIG_MVSATA_IDE_USE_PORT1
238 /* Needs byte-swapping for ATA data register */
239 #define CONFIG_IDE_SWAP_IO
240 /* Data, registers and alternate blocks are at the same offset */
241 #define CONFIG_SYS_ATA_DATA_OFFSET (0x0100)
242 #define CONFIG_SYS_ATA_REG_OFFSET (0x0100)
243 #define CONFIG_SYS_ATA_ALT_OFFSET (0x0100)
244 /* Each 8-bit ATA register is aligned to a 4-bytes address */
245 #define CONFIG_SYS_ATA_STRIDE 4
246 /* Controller supports 48-bits LBA addressing */
247 #define CONFIG_LBA48
248 /* CONFIG_CMD_IDE requires some #defines for ATA registers */
249 #define CONFIG_SYS_IDE_MAXBUS 2
250 #define CONFIG_SYS_IDE_MAXDEVICE 2
251 /* ATA registers base is at SATA controller base */
252 #define CONFIG_SYS_ATA_BASE_ADDR MV_SATA_BASE
253 #endif /* CONFIG_CMD_IDE */
254
255 /*
256 * I2C related stuff
257 */
258 #ifdef CONFIG_CMD_I2C
259 #define CONFIG_I2C_MVTWSI
260 #define CONFIG_SYS_I2C_SLAVE 0x0
261 #define CONFIG_SYS_I2C_SPEED 100000
262 #endif
263
264 /*
265 * File system 160 * File system
266 */ 161 */
267 #ifndef CONFIG_ARMADA100 /* will be removed latter */ 162 #ifdef CONFIG_SYS_MVFS
268 #define CONFIG_CMD_EXT2 163 #define CONFIG_CMD_EXT2
269 #define CONFIG_CMD_JFFS2 164 #define CONFIG_CMD_JFFS2