Eric Lee / smarc-uboot

Download as
Browse Code ยป

Commit 5356f5451e85695cf8f9782dee54cc8dfa5445e5

Authored by Aneesh V
Committed by Albert ARIBAUD
1 parent 74236acacc
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

ARM: enable Thumb build 

Enable Thumb build and ARM-Thumb interworking based on the new
config flag CONFIG_SYS_THUMB_BUILD

Signed-off-by: Aneesh V <aneesh@ti.com>
Acked-by: Mike Frysinger <vapier@gentoo.org>

Showing 2 changed files with 23 additions and 7 deletions Inline Diff

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