uboot readme

前面是 Uboot 的发展，下载地址，如何获得帮助，以及版本说明

Directory Hierarchy:

目录层次

====================

- board Board dependent files

开发板相关文件

- common Misc architecture independent functions

多体系结构独立函数

- cpu CPU specific files

CPU 相关文件

- 74xx_7xx Files specific to Freescale MPC74xx and 7xx CPUs

Freescale MPC74XX 的 CPU 相关文件

- arm720t Files specific to ARM 720 CPUs

ARM720 相关文件

- arm920t Files specific to ARM 920 CPUs

ARM920 相关文件

- at91rm9200 Files specific to Atmel AT91RM9200 CPU

AT91RM9200 相关

- imx Files specific to Freescale MC9328 i.MX CPUs

Freescale i.MX 相关

- s3c24x0 Files specific to Samsung S3C24X0 CPUs

- arm925t Files specific to ARM 925 CPUs

- arm926ejs Files specific to ARM 926 CPUs

- arm1136 Files specific to ARM 1136 CPUs

- at32ap Files specific to Atmel AVR32 AP CPUs

- i386 Files specific to i386 CPUs

- ixp Files specific to Intel XScale IXP CPUs

- leon2 Files specific to Gaisler LEON2 SPARC CPU

- leon3 Files specific to Gaisler LEON3 SPARC CPU

- mcf52x2 Files specific to Freescale ColdFire MCF52x2 CPUs

- mcf5227x Files specific to Freescale ColdFire MCF5227x CPUs

- mcf532x Files specific to Freescale ColdFire MCF5329 CPUs

- mcf5445x Files specific to Freescale ColdFire MCF5445x CPUs

- mcf547x_8x Files specific to Freescale ColdFire MCF547x_8x CPUs

- mips Files specific to MIPS CPUs

- mpc5xx Files specific to Freescale MPC5xx CPUs

- mpc5xxx Files specific to Freescale MPC5xxx CPUs

- mpc8xx Files specific to Freescale MPC8xx CPUs

- mpc8220 Files specific to Freescale MPC8220 CPUs

- mpc824x Files specific to Freescale MPC824x CPUs

- mpc8260 Files specific to Freescale MPC8260 CPUs

- mpc85xx Files specific to Freescale MPC85xx CPUs

- nios Files specific to Altera NIOS CPUs

- nios2 Files specific to Altera Nios-II CPUs

- ppc4xx Files specific to AMCC PowerPC 4xx CPUs

- pxa Files specific to Intel XScale PXA CPUs

- s3c44b0 Files specific to Samsung S3C44B0 CPUs

- sa1100 Files specific to Intel StrongARM SA1100 CPUs

- disk Code for disk drive partition handling

磁盘驱动，及分区操作的代码

- doc Documentation (don't expect too much)

文档（不要期待太多（搞不懂为什么了 ? ））

- drivers Commonly used device drivers

通用设备驱动

- dtt Digital Thermometer and Thermostat drivers

数字温度器及调温装置驱动

- examples Example code for standalone applications, etc.

独立应用程序的例子

- include Header Files

头文件

- lib_arm Files generic to ARM architecture

ARM 体系结构通用的文件

- lib_avr32 Files generic to AVR32 architecture

- lib_generic Files generic to all architectures

所有体系结构通用的文件

- lib_i386 Files generic to i386 architecture

- lib_m68k Files generic to m68k architecture

- lib_mips Files generic to MIPS architecture

- lib_nios Files generic to NIOS architecture

- lib_ppc Files generic to PowerPC architecture

- lib_sparc Files generic to SPARC architecture

- libfdt Library files to support flattened device trees

支持平板设备树的库文件

- net Networking code

网络代码

- post Power On Self Test

上电自检

- rtc Real Time Clock drivers

实时时钟驱动

- tools Tools to build S-Record or U-Boot images, etc.

编译 S-Record 和 U-Boot 镜像的工具

- api

1.3 版本的 UBOOT 还增加了一个 API 的文件夹，

这里放的是一些扩展应用的独立的 API 函数

Software Configuration:

软件配置：

=======================

Configuration is usually done using C preprocessor defines; the

rationale behind that is to avoid dead code whenever possible.

配置是通过 C 预处理程序完成。

There are two classes of configuration variables:

有两类配置变量：

* Configuration _OPTIONS_:

配置选项：

These are selectable by the user and have names beginning with

"CONFIG_".

是可由用户选择并以“ CONFIG_ ”开头

* Configuration _SETTINGS_:

配置设置

These depend on the hardware etc. and should not be meddled with if

you don't know what you're doing; they have names beginning with

"CFG_".

依赖于硬件，由“ CFG_ ”开头

Later we will add a configuration tool - probably similar to or even

identical to what's used for the Linux kernel. Right now, we have to

do the configuration by hand, which means creating some symbolic

links and editing some configuration files. We use the TQM8xxL boards

as an example here.

以后我们将加入类似 Linux 内核一样的配置工具。但现在只能手工配置。

我们将以 TQM8XXL 为例。

第一步：

Selection of Processor Architecture and Board Type:

选择处理器架构和板类型：

---------------------------------------------------

For all supported boards there are ready-to-use default

configurations available; just type "make <board_name>_config".

对所有已至此的板都已经有可用的默认配置，只要执行：

make <boare_name>_config

下面是例子

Example: For a TQM823L module type:

cd u-boot

make TQM823L_config

For the Cogent platform, you need to specify the CPU type as well;

e.g. "make cogent_mpc8xx_config". And also configure the cogent

directory according to the instructions in cogent/README.

对于加强型平台还要指定 CPU 类型，请阅读 cogent/READM

第二步

Configuration Options:

配置选项：

----------------------

Configuration depends on the combination of board and CPU type; all

such information is kept in a configuration file

配置依赖于板和 CPU ，所有配置设置信息保存在：

"include/configs/<board_name>.h ".

Example: For a TQM823L module, all configuration settings are in

"include/configs/TQM823L.h".

Many of the options are named exactly as the corresponding Linux

kernel configuration options. The intention is to make it easier to

build a config tool - later.

The following options need to be configured:

以下的选项需要被配置：

这里 MPC 的配置比较多，如果是 SMDK2410 的话配置会少很多

- CPU Type: Define exactly one, e.g. CONFIG_MPC85XX.

CPU 类型：正确地定义一个种类，比如： CONFIG_MPC85XX

- Board Type: Define exactly one, e.g. CONFIG_MPC8540ADS.

板类型：比如： CONFIG_MPC8540ADS

- CPU Daughterboard Type: (if CONFIG_ATSTK1000 is defined)

Define exactly one, e.g. CONFIG_ATSTK1002

CPU 子类

- CPU Module Type: (if CONFIG_COGENT is defined)

Define exactly one of

CONFIG_CMA286_60_OLD

CPU 模型

--- FIXME --- not tested yet:

CONFIG_CMA286_60, CONFIG_CMA286_21, CONFIG_CMA286_60P,

CONFIG_CMA287_23, CONFIG_CMA287_50

- Motherboard Type: (if CONFIG_COGENT is defined)

Define exactly one of

CONFIG_CMA101, CONFIG_CMA102

主板

- Motherboard I/O Modules: (if CONFIG_COGENT is defined)

Define one or more of

CONFIG_CMA302

主板 I/O 模式

- Motherboard Options: (if CONFIG_CMA101 or CONFIG_CMA102 are defined)

Define one or more of

CONFIG_LCD_HEARTBEAT - update a character position on

the LCD display every second with

a "rotator" |/-/|/-/

- Board flavour: (if CONFIG_MPC8260ADS is defined)

CONFIG_ADSTYPE

Possible values are:

CFG_8260ADS - original MPC8260ADS

CFG_8266ADS - MPC8266ADS

CFG_PQ2FADS - PQ2FADS-ZU or PQ2FADS-VR

CFG_8272ADS - MPC8272ADS

- MPC824X Family Member (if CONFIG_MPC824X is defined)

Define exactly one of

CONFIG_MPC8240, CONFIG_MPC8245

- 8xx CPU Options: (if using an MPC8xx CPU)

CONFIG_8xx_GCLK_FREQ - deprecated: CPU clock if

get_gclk_freq() cannot work

e.g. if there is no 32KHz

reference PIT/RTC clock

CONFIG_8xx_OSCLK - PLL input clock (either EXTCLK

or XTAL/EXTAL)

- 859/866/885 CPU options: (if using a MPC859 or MPC866 or MPC885 CPU):

CFG_8xx_CPUCLK_MIN

CFG_8xx_CPUCLK_MAX

CONFIG_8xx_CPUCLK_DEFAULT

See doc/README.MPC866

CFG_MEASURE_CPUCLK

Define this to measure the actual CPU clock instead

of relying on the correctness of the configured

values. Mostly useful for board bringup to make sure

the PLL is locked at the intended frequency. Note

that this requires a (stable) reference clock (32 kHz

RTC clock or CFG_8XX_XIN)

- Intel Monahans options:

CFG_MONAHANS_RUN_MODE_OSC_RATIO

Defines the Monahans run mode to oscillator

ratio. Valid values are 8, 16, 24, 31. The core

frequency is this value multiplied by 13 MHz.

CFG_MONAHANS_TURBO_RUN_MODE_RATIO

Defines the Monahans turbo mode to oscillator

ratio. Valid values are 1 (default if undefined) and

2. The core frequency as calculated above is multiplied

by this value.

- Linux Kernel Interface:

- Linux 内核接口

CONFIG_CLOCKS_IN_MHZ

U-Boot stores all clock information in Hz

internally.

UBOOT 以 Hz 位单位存储时钟信息

For binary compatibility with older Linux

kernels (which expect the clocks passed in the

bd_info data to be in MHz

Linux 内核期望时钟是以 MHz 位单位传到 bd_info 的 )

the environment variable

为了和内核兼容可以定义环境变量

"clocks_in_mhz " can be defined so that U-Boot

converts clock data to MHZ before passing it to the

Linux kernel.

把 UBOOT 的时钟数据转换位 MHz 后传入内核

When CONFIG_CLOCKS_IN_MHZ is defined, a definition of

"clocks_in_mhz=1" is automatically included in the

default environment.

当 CONFIG_CLOCKS_IN_MHZ 被定义后 clocks_in_mhz=1

会被自动包含到环境中

CONFIG_MEMSIZE_IN_BYTES [relevant for MIPS only]

只跟 MIPS 相关

When transferring memsize parameter to linux, some versions

expect it to be in bytes, others in MB.

Define CONFIG_MEMSIZE_IN_BYTES to make it in bytes.

对于内存大小的参数可以定义 CONFIG_MEMSIZE_IN_BYTES

以 BYTES 位单位

CONFIG_OF_LIBFDT

New kernel versions are expecting firmware settings to be

passed using flattened device trees (based on open firmware

concepts).

CONFIG_OF_LIBFDT

* New libfdt-based support

* Adds the "fdt" command

* The bootm command automatically updates the fdt

OF_CPU - The proper name of the cpus node.

OF_SOC - The proper name of the soc node.

OF_TBCLK - The timebase frequency.

OF_STDOUT_PATH - The path to the console device

boards with QUICC Engines require OF_QE to set UCC MAC

addresses

CONFIG_OF_BOARD_SETUP

Board code has addition modification that it wants to make

to the flat device tree before handing it off to the kernel

CONFIG_OF_BOOT_CPU

This define fills in the correct boot CPU in the boot

param header, the default value is zero if undefined.

- Serial Ports:

- 串口

CFG_PL010_SERIAL

Define this if you want support for Amba PrimeCell PL010 UARTs.

要支持 Amba PrimeCell PL010 UARTs 就定义此项

CFG_PL011_SERIAL

Define this if you want support for Amba PrimeCell PL011 UARTs.

CONFIG_PL011_CLOCK

If you have Amba PrimeCell PL011 UARTs, set this variable to

the clock speed of the UARTs.

CONFIG_PL01x_PORTS

If you have Amba PrimeCell PL010 or PL011 UARTs on your board,

define this to a list of base addresses for each (supported)

port. See e.g. include/configs/versatile.h

- Console Interface:

- 控制台接口

Depending on board, define exactly one serial port

(like CONFIG_8xx_CONS_SMC1, CONFIG_8xx_CONS_SMC2,

CONFIG_8xx_CONS_SCC1, ...), or switch off the serial

console by defining CONFIG_8xx_CONS_NONE

依赖于板，定义一个串口

Note: if CONFIG_8xx_CONS_NONE is defined, the serial

port routines must be defined elsewhere

(i.e. serial_init(), serial_getc(), ...)

CONFIG_CFB_CONSOLE

Enables console device for a color framebuffer.

使能控制台器件的彩色帧缓存

Needs following

defines (cf. smiLynxEM, i8042, board/eltec/bab7xx)

VIDEO_FB_LITTLE_ENDIAN graphic memory organisation

(default big endian)

VIDEO_HW_RECTFILL graphic chip supports

rectangle fill

(cf. smiLynxEM)

VIDEO_HW_BITBLT graphic chip supports

bit-blit (cf. smiLynxEM)

VIDEO_VISIBLE_COLS visible pixel columns

(cols=pitch)

VIDEO_VISIBLE_ROWS visible pixel rows

VIDEO_PIXEL_SIZE bytes per pixel

VIDEO_DATA_FORMAT graphic data format

(0-5, cf. cfb_console.c)

VIDEO_FB_ADRS framebuffer address

VIDEO_KBD_INIT_FCT keyboard int fct

(i.e. i8042_kbd_init())

VIDEO_TSTC_FCT test char fct

(i.e. i8042_tstc)

VIDEO_GETC_FCT get char fct

(i.e. i8042_getc)

CONFIG_CONSOLE_CURSOR cursor drawing on/off

(requires blink timer

cf. i8042.c)

CFG_CONSOLE_BLINK_COUNT blink interval (cf. i8042.c)

CONFIG_CONSOLE_TIME display time/date info in

upper right corner

(requires CONFIG_CMD_DATE)

CONFIG_VIDEO_LOGO display Linux logo in

upper left corner

CONFIG_VIDEO_BMP_LOGO use bmp_logo.h instead of

linux_logo.h for logo.

Requires CONFIG_VIDEO_LOGO

CONFIG_CONSOLE_EXTRA_INFO

additional board info beside

the logo

When CONFIG_CFB_CONSOLE is defined, video console is

default i/o.

当定义了 CONFIG_CFB_CONSOLE 后，视频控制台位默认 I/O

Serial console can be forced with

environment 'console=serial'.

When CONFIG_SILENT_CONSOLE is defined, all console

messages (by U-Boot and Linux!) can be silenced with

the "silent" environment variable.

若定义了 CONFIG_SILENT_CONSOLE ，则所有控制台信息

都为缄默模式

See

doc/README.silent for more information.

查看 doc/README.silent 获得帮助

- Console Baudrate:

- 控制台波特率

CONFIG_BAUDRATE - in bps

Select one of the baudrates listed in

CFG_BAUDRATE_TABLE , see below.

CFG_BRGCLK_PRESCALE , baudrate prescale

- Interrupt driven serial port input:

- 中断驱动串口输入

CONFIG_SERIAL_SOFTWARE_FIFO

PPC405GP only.

仅对 PPC405GP

Use an interrupt handler for receiving data on the

serial port. It also enables using hardware handshake

(RTS/CTS) and UART's built-in FIFO. Set the number of

bytes the interrupt driven input buffer should have.

Leave undefined to disable this feature, including

disable the buffer and hardware handshake.

- Console UART Number:

- 控制台 UART 数

CONFIG_UART1_CONSOLE

AMCC PPC4xx only.

仅对 AMCC PPC4XX

If defined internal UART1 (and not UART0) is used

as default U-Boot console.

- Boot Delay:

- 启动延时

- CONFIG_BOOTDELAY - in seconds

Delay before automatically booting the default image;

自动引导默认镜像的延时

set to -1 to disable autoboot.

-1 为禁止自动启动

See doc/README.autoboot for these options that

work with CONFIG_BOOTDELAY. None are required.

关于 CONFIG_BOOTDELAY 的选项请查阅 doc/README.autoboot

引导重试环境变量

CONFIG_BOOT_RETRY_TIME

CONFIG_BOOT_RETRY_MIN

这两个决定在 UBOOT 停止引导等待命令过程中的行为，

若环境变量 "bootretry" 存在，则 "bootretry" 的值将被应用，否则默认超时时间为

CONFIG_BOOT_RETRY_TIME 的值， CONFIG_BOOT_RETRY_MIN 被选为 CONFIG_BOOT_RETRY_TIME 的缺省值，若 CONFIG_BOOT_RETRY_TIME 为负则不会发生超时。

CONFIG_AUTOBOOT_KEYED

CONFIG_AUTOBOOT_PROMPT

CONFIG_AUTOBOOT_DELAY_STR

CONFIG_AUTOBOOT_STOP_STR

CONFIG_AUTOBOOT_DELAY_STR2

CONFIG_AUTOBOOT_STOP_STR2

"bootdelaykey" environment variable

"bootstopkey" environment variable

"bootdelaykey2" environment variable

"bootstopkey2" environment variable

这些选项给停止自动引导提供更多的控制。当应用他们时就需要输入特定的字符或字符串来停止或延时自动引导。

CONFIG_AUTOBOOT_PROMPT 显示一些信，但 CONFIG_BOOTDELAY 必须被定义。

#define CONFIG_AUTOBOOT_PROMPT /

"autoboot in %d seconds/n",bootdelay

若 CONFIG_AUTOBOOT_DELAY_STR 或 "bootdelaykey" 被定义，但从控制台输入特定字符时，就会出现 UBOOT 提示符，停止自动引导。超时后自动重新引导。

若 CONFIG_AUTOBOOT_STOP_STR 或 "bootstopkey" 被定义，但从控制台输入特定字符时，就会出现 UBOOT 提示符，停止自动引导。超时后不自动重新引导。

CONFIG_AUTOBOOT_DELAY_STR2 或 "bootstopkey2" 则允许你有两个进入字符

CONFIG_ZERO_BOOTDELAY_CHECK

CONFIG_RESET_TO_RETRY

CONFIG_ZERO_BOOTDELAY_CHECK 此选项能让你通过敲击一个键来停止自动引导。

CONFIG_RESET_TO_RETRY 当 CONFIG_BOOT_RETRY_TIME 被定义时才有效。当超时时板将重启。

- Autoboot Command:

- 自动引导命令

CONFIG_BOOTCOMMAND

Only needed when CONFIG_BOOTDELAY is enabled;

当 CONFIG_BOOTDELAY 使能使需要

define a command string that is automatically executed

when no character is read on the console interface

within "Boot Delay" after reset.

当启动延时时间内没有从控制接口都取字符时自动执行

它定义的命令字符

CONFIG_BOOTARGS

This can be used to pass arguments to the bootm

command. The value of CONFIG_BOOTARGS goes into the

environment value "bootargs".

传递参数到 bootm 命令

CONFIG_RAMBOOT and CONFIG_NFSBOOT

The value of these goes into the environment as

"ramboot" and "nfsboot" respectively, and can be used

as a convenience, when switching between booting from

RAM and NFS.

实现从 RAM 和 NFS 启动的转换

- Pre-Boot Commands:

CONFIG_PREBOOT

When this option is #defined, the existence of the

environment variable "preboot" will be checked

immediately before starting the CONFIG_BOOTDELAY

countdown and/or running the auto-boot command resp.

entering interactive mode.

This feature is especially useful when "preboot" is

automatically generated or modified. For an example

see the LWMON board specific code: here "preboot" is

modified when the user holds down a certain

combination of keys on the (special) keyboard when

booting the systems

- Serial Download Echo Mode:

- 串口下载回显模式

CONFIG_LOADS_ECHO

If defined to 1, all characters received during a

serial download (using the "loads" command) are

echoed back.

当设置为 1 时串口在下载时所有接受的字符都回显出来

This might be needed by some terminal

emulations (like "cu"), but may as well just take

time on others. This setting #define's the initial

value of the "loads_echo" environment variable.

这个设置定义了 "loads_echo" 的环境变量

- Kgdb Serial Baudrate: (if CONFIG_CMD_KGDB is defined )

- Kgdb 串口波特率

CONFIG_KGDB_BAUDRATE

Select one of the baudrates listed in

CFG_BAUDRATE_TABLE ,

这里定义了所有可用波特率的表

see below.

- Monitor Functions:

- 监视函数

Monitor commands can be included or excluded

from the build by using the #include files

通过编译时包含 "config_cmd_all.h" 头文件来包含所有的监控命令

And 通过 #undef'ing 去掉不需要的命令 unwanted

commands, or using "config_cmd_default.h" 为包含默认命令

and augmenting with additional #define's

for wanted commands.

The default command configuration includes all commands

except those marked below with a "*".

默认命令配置包含所有不带“ * ”标记的命令

CONFIG_CMD_ASKENV * ask for env variable

请求环境变量

CONFIG_CMD_AUTOSCRIPT Autoscript Support

自动脚本支持

CONFIG_CMD_BDI bdinfo

CONFIG_CMD_BEDBUG * Include BedBug Debugger

CONFIG_CMD_BMP * BMP support

CONFIG_CMD_BSP * Board specific commands

CONFIG_CMD_BOOTD bootd

CONFIG_CMD_CACHE * icache, dcache

CONFIG_CMD_CONSOLE coninfo

CONFIG_CMD_DATE * support for RTC, date/time...

CONFIG_CMD_DHCP * DHCP support

CONFIG_CMD_DIAG * Diagnostics

CONFIG_CMD_DOC * Disk-On-Chip Support

CONFIG_CMD_DTT * Digital Therm and Thermostat

CONFIG_CMD_ECHO echo arguments

CONFIG_CMD_EEPROM * EEPROM read/write support

CONFIG_CMD_ELF * bootelf, bootvx

CONFIG_CMD_ENV saveenv

CONFIG_CMD_FDC * Floppy Disk Support

CONFIG_CMD_FAT * FAT partition support

CONFIG_CMD_FDOS * Dos diskette Support

CONFIG_CMD_FLASH flinfo, erase, protect

CONFIG_CMD_FPGA FPGA device initialization support

CONFIG_CMD_HWFLOW * RTS/CTS hw flow control

CONFIG_CMD_I2C * I2C serial bus support

CONFIG_CMD_IDE * IDE harddisk support

CONFIG_CMD_IMI iminfo

CONFIG_CMD_IMLS List all found images

CONFIG_CMD_IMMAP * IMMR dump support

CONFIG_CMD_IRQ * irqinfo

CONFIG_CMD_ITEST Integer/string test of 2 values

CONFIG_CMD_JFFS2 * JFFS2 Support

CONFIG_CMD_KGDB * kgdb

CONFIG_CMD_LOADB loadb

CONFIG_CMD_LOADS loads

CONFIG_CMD_MEMORY md, mm, nm, mw, cp, cmp, crc, base,

loop, loopw, mtest

CONFIG_CMD_MISC Misc functions like sleep etc

CONFIG_CMD_MMC * MMC memory mapped support

CONFIG_CMD_MII * MII utility commands

CONFIG_CMD_NAND * NAND support

CONFIG_CMD_NET bootp, tftpboot, rarpboot

CONFIG_CMD_PCI * pciinfo

CONFIG_CMD_PCMCIA * PCMCIA support

CONFIG_CMD_PING * send ICMP ECHO_REQUEST to network

host

CONFIG_CMD_PORTIO * Port I/O

CONFIG_CMD_REGINFO * Register dump

CONFIG_CMD_RUN run command in env variable

CONFIG_CMD_SAVES * save S record dump

CONFIG_CMD_SCSI * SCSI Support

CONFIG_CMD_SDRAM * print SDRAM configuration information

(requires CONFIG_CMD_I2C)

CONFIG_CMD_SETGETDCR Support for DCR Register access

(4xx only)

CONFIG_CMD_SPI * SPI serial bus support

CONFIG_CMD_USB * USB support

CONFIG_CMD_VFD * VFD support (TRAB)

CONFIG_CMD_CDP * Cisco Discover Protocol support

CONFIG_CMD_FSL * Microblaze FSL support

EXAMPLE: If you want all functions except of network

support you can write:

比如你需要除网络外的所有函数，你可以写入下面几行

#include "config_cmd_all.h"

#undef CONFIG_CMD_NET

Other Commands:

fdt (flattened device tree) command: CONFIG_OF_LIBFDT

Note: Don't enable the "icache" and "dcache" commands

(configuration option CONFIG_CMD_CACHE) unless you know

what you (and your U-Boot users) are doing. Data

cache cannot be enabled on systems like the 8xx or

8260 (where accesses to the IMMR region must be

uncached), and it cannot be disabled on all other

systems where we (mis-) use the data cache to hold an

initial stack and some data.

XXX - this list needs to get updated!

- Watchdog:

- 看门狗

CONFIG_WATCHDOG

If this variable is defined, it enables watchdog

support.

若被定义则支持看门狗

There must be support in the platform specific

code for a watchdog. For the 8xx and 8260 CPUs, the

SIU Watchdog feature is enabled in the SYPCR

- U-Boot Version:

- UBOOT 版本

CONFIG_VERSION_VARIABLE

If this variable is defined, an environment variable

named "ver" is created by U-Boot showing the U-Boot

version as printed by the "version" command.

This variable is readonly.

若这个变量被定义则 "ver" 的环境变量被 UBOOT 创建，通过 "version" 命令进行读取，此变量为只读

- Real-Time Clock:

- 实时时钟

When CONFIG_CMD_DATE is selected, the type of the RTC

has to be selected, too. Define exactly one of the

following options:

当 CONFIG_CMD_DATE 被选取时， RTC 的类型也要被选取，从以下选项中选一个最接近的

CONFIG_RTC_MPC8xx - use internal RTC of MPC8xx

CONFIG_RTC_PCF8563 - use Philips PCF8563 RTC

CONFIG_RTC_MC13783 - use MC13783 RTC

CONFIG_RTC_MC146818 - use MC146818 RTC

CONFIG_RTC_DS1307 - use Maxim, Inc. DS1307 RTC

CONFIG_RTC_DS1337 - use Maxim, Inc. DS1337 RTC

CONFIG_RTC_DS1338 - use Maxim, Inc. DS1338 RTC

CONFIG_RTC_DS164x - use Dallas DS164x RTC

CONFIG_RTC_ISL1208 - use Intersil ISL1208 RTC

CONFIG_RTC_MAX6900 - use Maxim, Inc. MAX6900 RTC

CFG_RTC_DS1337_NOOSC - Turn off the OSC output for DS1337

Note that if the RTC uses I2C, then the I2C interface

must also be configured. See I2C Support, below.

若 RTC 用 I2C ，则 I2C 接口也要被配置。

- Timestamp Support:

- 时间戳支持

When CONFIG_TIMESTAMP is selected, the timestamp

(date and time) of an image is printed by image

commands like bootm or iminfo. This option is

automatically enabled when you select CONFIG_CMD_DATE .

当选择了 CONFIG_CMD_DATE 后这个选项被自动使能，通过映像命令来打印映像的时间戳

- Partition Support:

- 分区支持

CONFIG_MAC_PARTITION and/or CONFIG_DOS_PARTITION

and/or CONFIG_ISO_PARTITION

If IDE or SCSI support is enabled (CONFIG_CMD_IDE or

CONFIG_CMD_SCSI ) you must configure support for at

least one partition type as well.

- IDE Reset method:

- 对 IDE 的支持

CONFIG_IDE_RESET_ROUTINE - this is defined in several

board configurations files but used nowhere!

CONFIG_IDE_RESET - is this is defined, IDE Reset will

be performed by calling the function

ide_set_reset(int reset)

which has to be defined in a board specific file

- ATAPI Support:

CONFIG_ATAPI

Set this to enable ATAPI support.

- LBA48 Support

CONFIG_LBA48

Set this to enable support for disks larger than 137GB

Also look at CFG_64BIT_LBA ,CFG_64BIT_VSPRINTF and CFG_64BIT_STRTOUL

Whithout these , LBA48 support uses 32bit variables and will 'only'

support disks up to 2.1TB.

CFG_64BIT_LBA:

When enabled, makes the IDE subsystem use 64bit sector addresses.

Default is 32bit.

- SCSI Support:

At the moment only there is only support for the

SYM53C8XX SCSI controller; define

CONFIG_SCSI_SYM53C8XX to enable it.

CFG_SCSI_MAX_LUN [8], CFG_SCSI_MAX_SCSI_ID [7] and

CFG_SCSI_MAX_DEVICE [CFG_SCSI_MAX_SCSI_ID *

CFG_SCSI_MAX_LUN] can be adjusted to define the

maximum numbers of LUNs, SCSI ID's and target

devices.

CFG_SCSI_SYM53C8XX_CCF to fix clock timing (80Mhz)

- NETWORK Support (PCI):

- 网络支持（ PCI ）

CONFIG_E1000

Support for Intel 8254x gigabit chips.

CONFIG_E1000_FALLBACK_MAC

default MAC for empty EEPROM after production.

CONFIG_EEPRO100

Support for Intel 82557/82559/82559ER chips.

Optional CONFIG_EEPRO100_SROM_WRITE enables EEPROM

write routine for first time initialisation.

CONFIG_TULIP

Support for Digital 2114x chips.

Optional CONFIG_TULIP_SELECT_MEDIA for board specific

modem chip initialisation (KS8761/QS6611).

CONFIG_NATSEMI

Support for National dp83815 chips.

CONFIG_NS8382X

Support for National dp8382[01] gigabit chips.

- NETWORK Support (other):

CONFIG_DRIVER_LAN91C96

Support for SMSC's LAN91C96 chips.

CONFIG_LAN91C96_BASE

Define this to hold the physical address

of the LAN91C96's I/O space

CONFIG_LAN91C96_USE_32_BIT

Define this to enable 32 bit addressing

CONFIG_DRIVER_SMC91111

Support for SMSC's LAN91C111 chip

CONFIG_SMC91111_BASE

Define this to hold the physical address

of the device (I/O space)

CONFIG_SMC_USE_32_BIT

Define this if data bus is 32 bits

CONFIG_SMC_USE_IOFUNCS

Define this to use i/o functions instead of macros

(some hardware wont work with macros)

CONFIG_DRIVER_SMC911X

Support for SMSC's LAN911x and LAN921x chips

CONFIG_DRIVER_SMC911X_BASE

Define this to hold the physical address

of the device (I/O space)

CONFIG_DRIVER_SMC911X_32_BIT

Define this if data bus is 32 bits

CONFIG_DRIVER_SMC911X_16_BIT

Define this if data bus is 16 bits. If your processor

automatically converts one 32 bit word to two 16 bit

words you may also try CONFIG_DRIVER_SMC911X_32_BIT.

- USB Support:

- USB 支持

At the moment only the UHCI host controller is

supported (PIP405, MIP405, MPC5200);

目前只支持通用主控制器接口的主控制器

defineCONFIG_USB_UHCI to enable it.

定义 CONFIG_USB_UHCI 允许 USB 主控制器

define CONFIG_USB_KEYBOARD to enable the USB Keyboard

定义 CONFIG_USB_KEYBOARD 允许 USB 键盘

and define CONFIG_USB_STORAGE to enable the USB

定义 CONFIG_USB_STORAGE 来允许 USB 储存器

storage devices.

Note:

Supported are USB Keyboards and USB Floppy drives

(TEAC FD-05PUB).

MPC5200 USB requires additional defines:

CONFIG_USB_CLOCK

for 528 MHz Clock: 0x0001bbbb

CONFIG_USB_CONFIG

for differential drivers: 0x00001000

for single ended drivers: 0x00005000

CFG_USB_EVENT_POLL

May be defined to allow interrupt polling

instead of using asynchronous interrupts

- USB Device:

- USB 器件

Define the below if you wish to use the USB console.

若想使用 USB 控制台，定义下面的变量

Once firmware is rebuilt from a serial console issue the

command "setenv stdin usbtty; setenv stdout usbtty" and

attach your USB cable. The Unix command "dmesg" should print

it has found a new device. The environment variable usbtty

can be set to gserial or cdc_acm to enable your device to

appear to a USB host as a Linux gserial device or a

Common Device Class Abstract Control Model serial device.

If you select usbtty = gserial you should be able to enumerate

a Linux host by

# modprobe usbserial vendor=0xVendorID product=0xProductID

else if using cdc_acm, simply setting the environment

variable usbtty to be cdc_acm should suffice. The following

might be defined in YourBoardName.h

CONFIG_USB_DEVICE

Define this to build a UDC device

定义这项来构建 UDC 设备

CONFIG_USB_TTY

Define this to have a tty type of device available to

talk to the UDC device

定义，以拥有一个和 UDC 通信的 tty 设备。

CFG_CONSOLE_IS_IN_ENV

Define this if you want stdin, stdout &/or stderr to

be set to usbtty.

若想 stdin,stdout,stderr 被设置到 usbtty 就定义此项

mpc8xx:

CFG_USB_EXTC_CLK 0xBLAH

Derive USB clock from external clock "blah"

- CFG_USB_EXTC_CLK 0x02

CFG_USB_BRG_CLK 0xBLAH

Derive USB clock from brgclk

- CFG_USB_BRG_CLK 0x04

If you have a USB-IF assigned VendorID then you may wish to

define your own vendor specific values either in BoardName.h

or directly in usbd_vendor_info.h . If you don't define

CONFIG_USBD_MANUFACTURER, CONFIG_USBD_PRODUCT_NAME,

CONFIG_USBD_VENDORID and CONFIG_USBD_PRODUCTID, then U-Boot

should pretend to be a Linux device to it's target host.

若没有定义 CONFIG_USBD_MANUFACTURER, CONFIG_USBD_PRODUCT_NAME,

CONFIG_USBD_VENDORID and CONFIG_USBD_PRODUCTID 则 UBOOT 就对其目标主机假装成一个 Linux 设备

CONFIG_USBD_MANUFACTURER

Define this string as the name of your company for

- CONFIG_USBD_MANUFACTURER "my company"

CONFIG_USBD_PRODUCT_NAME

Define this string as the name of your product

- CONFIG_USBD_PRODUCT_NAME "acme usb device"

CONFIG_USBD_VENDORID

Define this as your assigned Vendor ID from the USB

Implementors Forum. This *must* be a genuine Vendor ID

to avoid polluting the USB namespace.

- CONFIG_USBD_VENDORID 0xFFFF

CONFIG_USBD_PRODUCTID

Define this as the unique Product ID

for your device

- CONFIG_USBD_PRODUCTID 0xFFFF

- MMC Support:

- MMC 支持

The MMC controller on the Intel PXA is supported. To

enable this define CONFIG_MMC. The MMC can be

accessed from the boot prompt by mapping the device

to physical memory similar to flash. Command line is

enabled with CONFIG_CMD_MMC. The MMC driver also works with

the FAT fs. This is enabled with CONFIG_CMD_FAT.

- Journaling Flash filesystem support:

- Flash 日志文件系统支持

CONFIG_JFFS2_NAND, CONFIG_JFFS2_NAND_OFF, CONFIG_JFFS2_NAND_SIZE,

CONFIG_JFFS2_NAND_DEV

Define these for a default partition on a NAND device

定义这些作为 NAND 缺省分区支持

CFG_JFFS2_FIRST_SECTOR,

CFG_JFFS2_FIRST_BANK, CFG_JFFS2_NUM_BANKS

Define these for a default partition on a NOR device

定义这些作为 NOR 缺省分区支持

CFG_JFFS_CUSTOM_PART

Define this to create an own partition. You have to provide a

function struct part_info* jffs2_part_info(int part_num)

定义自己的分区，你必须提供函数结构

part_info* jffs2_part_info(int part_num)

If you define only one JFFS2 partition you may also want to

若只定义一个 JFFF2 分区则用以下命令

#define CFG_JFFS_SINGLE_PART 1

to disable the command chpart. This is the default when you

have not defined a custom partition

- Keyboard Support:

CONFIG_ISA_KEYBOARD

Define this to enable standard (PC-Style) keyboard

support

CONFIG_I8042_KBD

Standard PC keyboard driver with US (is default) and

GERMAN key layout (switch via environment 'keymap=de') support.

Export function i8042_kbd_init, i8042_tstc and i8042_getc

for cfb_console. Supports cursor blinking.

- Video support:

- 视频支持

CONFIG_VIDEO

Define this to enable video support (for output to

video).

定义此项允许输出视频

CONFIG_VIDEO_CT69000

Enable Chips & Technologies 69000 Video chip

CONFIG_VIDEO_SMI_LYNXEM

Enable Silicon Motion SMI 712/710/810 Video chip.

支持慧荣科技 SMI 712/710/810 视频芯片

The

video output is selected via environment 'videoout'

(1 = LCD and 2 = CRT). If videoout is undefined, CRT is

assumed.

视频输出通过环境变量 'videoout' 选择， 1 为 LCD ， 2 为 CRT ，默认为 CRT

For the CT69000 and SMI_LYNXEM drivers, videomode is

selected via environment 'videomode'. Two different ways

are possible:

- "videomode=num" 'num' is a standard LiLo mode numbers.

视频模式由环境变量 'videomode' 选择

- "videomode=num"

Following standard modes are supported (* is default):

Colors 640x480 800x600 1024x768 1152x864 1280x1024

-------------+---------------------------------------------

8 bits | 0x301* 0x303 0x305 0x161 0x307

15 bits | 0x310 0x313 0x316 0x162 0x319

16 bits | 0x311 0x314 0x317 0x163 0x31A

24 bits | 0x312 0x315 0x318 ? 0x31B

-------------+---------------------------------------------

应用举例

(i.e. setenv videomode 317; saveenv; reset;)

- "videomode=bootargs" all the video parameters are parsed

from the bootargs. (See drivers/video/videomodes.c )

CONFIG_VIDEO_SED13806

Enable Epson SED13806 driver. This driver supports 8bpp

and 16bpp modes defined by CONFIG_VIDEO_SED13806_8BPP

or CONFIG_VIDEO_SED13806_16BPP

- Keyboard Support:

CONFIG_KEYBOARD

Define this to enable a custom keyboard support.

This simply calls drv_keyboard_init() which must be

defined in your board-specific files.

The only board using this so far is RBC823.

- LCD Support:

- 支持 LCD

CONFIG_LCD

Define this to enable LCD support (for output to LCD

display); also select one of the supported displays

by defining one of these:

定义此项来支持 LCD 输出，同时从以下几个选项中选一个来配置

CONFIG_ATMEL_LCD:

HITACHI TX09D70VM1CCA, 3.5", 240x320.

日立 TX09D70VM1CCA, 3.5", 240x320

CONFIG_NEC_NL6448AC33:

NEC NL6448AC33-18. Active, color, single scan.

CONFIG_NEC_NL6448BC20

NEC NL6448BC20-08. 6.5", 640x480.

Active, color, single scan.

CONFIG_NEC_NL6448BC33_54

NEC NL6448BC33-54. 10.4", 640x480.

Active, color, single scan.

CONFIG_SHARP_16x9

Sharp 320x240. Active, color, single scan.

It isn't 16x9, and I am not sure what it is.

CONFIG_SHARP_LQ64D341

Sharp LQ64D341 display, 640x480.

Active, color, single scan.

CONFIG_HLD1045

HLD1045 display, 640x480.

Active, color, single scan.

CONFIG_OPTREX_BW

Optrex CBL50840-2 NF-FW 99 22 M5

Hitachi LMG6912RPFC-00T

Hitachi SP14Q002

320x240. Black & white.

Normally display is black on white background;

正常显示为白底黑字

Define CFG_WHITE_ON_BLACK to get it inverted.

定义 CFG_WHITE_ON_BLACK 取得反白效果

- Splash Screen Support:

- 溅射屏幕（程序启动画面）支持

CONFIG_SPLASH_SCREEN

If this option is set, the environment is checked for

a variable "splashimage". If found, the usual display

of logo, copyright and system information on the LCD

is suppressed and the BMP image at the address

specified in "splashimage" is loaded instead. The

console is redirected to the "nulldev", too. This

allows for a "silent" boot where a splash screen is

loaded very quickly after power-on.

若被设置，就会在启动时显示放于环境变量 "splashimage" 中的 BMP 图片

- Gzip compressed BMP image support:

- Gzip 压缩 BMP 图片支持

CONFIG_VIDEO_BMP_GZIP

If this option is set, additionally to standard BMP

images, gzipped BMP images can be displayed via the

splashscreen support or the bmp command.

- Compression support:

- 压缩支持

CONFIG_BZIP2

If this option is set, support for bzip2 compressed

images is included. If not, only uncompressed and gzip

compressed images are supported.

若被设置就能支持 bzip2 压缩格式的映像

NOTE: the bzip2 algorithm requires a lot of RAM, so

the malloc area (as defined by CFG_MALLOC_LEN) should

be at least 4MB.

- MII/PHY support:

- 媒体独立接口 / 物理接口收发器支持

CONFIG_PHY_ADDR

The address of PHY on MII bus.

媒体独立接口中物理层的地址

CONFIG_PHY_CLOCK_FREQ (ppc4xx)

The clock frequency of the MII bus

媒体独立接口时钟频率

CONFIG_PHY_GIGE

If this option is set, support for speed/duplex

detection of gigabit PHY is included.

CONFIG_PHY_RESET_DELAY

Some PHY like Intel LXT971A need extra delay after

reset before any MII register access is possible.

For such PHY, set this option to the usec delay

required. (minimum 300usec for LXT971A)

物理层接口延时，某些物理层接口如 Intel LXT971A 重启后需要一定延时时间

CONFIG_PHY_CMD_DELAY (ppc4xx)

Some PHY like Intel LXT971A need extra delay after

command issued before MII status register can be read

- Ethernet address:

- 以太网地址

CONFIG_ETHADDR

CONFIG_ETH2ADDR

CONFIG_ETH3ADDR

Define a default value for Ethernet address to use

for the respective Ethernet interface, in case this

is not determined automatically.

配置不同以太网接口的地址

- IP address:

- IP 地址

CONFIG_IPADDR

Define a default value for the IP address to use for

the default Ethernet interface, in case this is not

determined through e.g. bootp.

- Server IP address:

- 服务器 IP 地址

CONFIG_SERVERIP

Defines a default value for the IP address of a TFTP

server to contact when using the "tftboot" command.

为 "tftboot" 命令的 TFTP 服务定义一个缺省的 IP 地址

- Multicast TFTP Mode:

- 多点传送 TFTP 模式

CONFIG_MCAST_TFTP

Defines whether you want to support multicast TFTP as per

rfc-2090; for example to work with atftp. Lets lots of targets

tftp down the same boot image concurrently. Note: the Ethernet

driver in use must provide a function: mcast() to join/leave a

multicast group.

定义是否支持多目标 tftp 同时下载同一映像，在以太网驱动中必须用 mcast() 函数来加入 / 离开多点传送。

CONFIG_BOOTP_RANDOM_DELAY

- BOOTP Recovery Mode:

CONFIG_BOOTP_RANDOM_DELAY

If you have many targets in a network that try to

boot using BOOTP, you may want to avoid that all

systems send out BOOTP requests at precisely the same

moment (which would happen for instance at recovery

from a power failure, when all systems will try to

boot, thus flooding the BOOTP server. Defining

CONFIG_BOOTP_RANDOM_DELAY causes a random delay to be

inserted before sending out BOOTP requests.

定义一个 BOOTP 请求发送延时来避免所有系统正好同时发出 BOOTP 请求（同时发请求会导致 BOOTP 服务器溢出）

The following delays are inserted then:

插入的延时时间表

1st BOOTP request: delay 0 ... 1 sec

2nd BOOTP request: delay 0 ... 2 sec

3rd BOOTP request: delay 0 ... 4 sec

4th and following

BOOTP requests: delay 0 ... 8 sec

- DHCP Advanced Options:

- DHCP 高级选项

You can fine tune the DHCP functionality by defining

CONFIG_BOOTP_* symbols:

CONFIG_BOOTP_SUBNETMASK

CONFIG_BOOTP_GATEWAY

CONFIG_BOOTP_HOSTNAME

CONFIG_BOOTP_NISDOMAIN

CONFIG_BOOTP_BOOTPATH

CONFIG_BOOTP_BOOTFILESIZE

CONFIG_BOOTP_DNS

CONFIG_BOOTP_DNS2

CONFIG_BOOTP_SEND_HOSTNAME

CONFIG_BOOTP_NTPSERVER

CONFIG_BOOTP_TIMEOFFSET

CONFIG_BOOTP_VENDOREX

CONFIG_BOOTP_SERVERIP - TFTP server will be the serverip

environment variable, not the BOOTP server.

CONFIG_BOOTP_DNS2 - If a DHCP client requests the DNS

serverip from a DHCP server, it is possible that more

than one DNS serverip is offered to the client.

If CONFIG_BOOTP_DNS2 is enabled, the secondary DNS

serverip will be stored in the additional environment

variable "dnsip2". The first DNS serverip is always

stored in the variable "dnsip", when CONFIG_BOOTP_DNS

is defined.

CONFIG_BOOTP_SEND_HOSTNAME - Some DHCP servers are capable

to do a dynamic update of a DNS server. To do this, they

need the hostname of the DHCP requester.

If CONFIG_BOOTP_SEND_HOSTNAME is defined, the content

of the "hostname" environment variable is passed as

option 12 to the DHCP server.

CONFIG_BOOTP_DHCP_REQUEST_DELAY

A 32bit value in microseconds for a delay between

receiving a "DHCP Offer" and sending the "DHCP Request".

This fixes a problem with certain DHCP servers that don't

respond 100% of the time to a "DHCP request". E.g. On an

AT91RM9200 processor running at 180MHz, this delay needed

to be *at least* 15,000 usec before a Windows Server 2003

DHCP server would reply 100% of the time. I recommend at

least 50,000 usec to be safe. The alternative is to hope

that one of the retries will be successful but note that

the DHCP timeout and retry process takes a longer than

this delay.

推荐值为 50000

- CDP Options:

CONFIG_CDP_DEVICE_ID

The device id used in CDP trigger frames.

CONFIG_CDP_DEVICE_ID_PREFIX

A two character string which is prefixed to the MAC address

of the device.

CONFIG_CDP_PORT_ID

A printf format string which contains the ascii name of

the port. Normally is set to "eth%d" which sets

eth0 for the first Ethernet, eth1 for the second etc.

CONFIG_CDP_CAPABILITIES

A 32bit integer which indicates the device capabilities;

0x00000010 for a normal host which does not forwards.

CONFIG_CDP_VERSION

An ascii string containing the version of the software.

CONFIG_CDP_PLATFORM

An ascii string containing the name of the platform.

CONFIG_CDP_TRIGGER

A 32bit integer sent on the trigger.

CONFIG_CDP_POWER_CONSUMPTION

A 16bit integer containing the power consumption of the

device in .1 of milliwatts.

CONFIG_CDP_APPLIANCE_VLAN_TYPE

A byte containing the id of the VLAN.

- Status LED:

- 状态 LED

CONFIG_STATUS_LED

Several configurations allow to display the current

status using a LED. For instance, the LED will blink

fast while running U-Boot code, stop blinking as

soon as a reply to a BOOTP request was received, and

start blinking slow once the Linux kernel is running

(supported by a status LED driver in the Linux

kernel). Defining CONFIG_STATUS_LED enables this

feature in U-Boot.

- CAN Support:

- CAN 总线支持

CONFIG_CAN_DRIVER

Defining CONFIG_CAN_DRIVER enables CAN driver support

on those systems that support this (optional)

feature, like the TQM8xxL modules.

- I2C Support:

- I2C 支持

CONFIG_HARD_I2C | CONFIG_SOFT_I2C

These enable I2C serial bus commands. Defining either of

(but not both of) CONFIG_HARD_I2C or CONFIG_SOFT_I2C will

include the appropriate I2C driver for the selected CPU.

定义这两项将允许 I2C 串行总线命令。配置这两项将包含相应的驱动

This will allow you to use i2c commands at the u-boot

command line (as long as you set CONFIG_CMD_I2C in

CONFIG_COMMANDS) and communicate with i2c based realtime

clock chips. See common/cmd_i2c.c for a description of the

command line interface.

CONFIG_I2C_CMD_TREE is a recommended option that places

all I2C commands under a single 'i2c' root command. The

older 'imm', 'imd', 'iprobe' etc. commands are considered

deprecated and may disappear in the future.

CONFIG_HARD_I2C selects a hardware I2C controller.

CONFIG_SOFT_I2C configures u-boot to use a software (aka

bit-banging) driver instead of CPM or similar hardware

support for I2C.

There are several other quantities that must also be

defined when you define CONFIG_HARD_I2C or CONFIG_SOFT_I2C.

In both cases you will need to define CFG_I2C_SPEED

to be the frequency (in Hz) at which you wish your i2c bus

to run and CFG_I2C_SLAVE to be the address of this node (ie

the CPU's i2c node address).

Now, the u-boot i2c code for the mpc8xx (cpu/mpc8xx/i2c.c)

sets the CPU up as a master node and so its address should

therefore be cleared to 0 (See, eg, MPC823e User's Manual

p.16-473). So, set CFG_I2C_SLAVE to 0.

That's all that's required for CONFIG_HARD_I2C.

If you use the software i2c interface (CONFIG_SOFT_I2C)

then the following macros need to be defined (examples are

from include/configs/lwmon.h ):

若用软件 I2C 接口，则下面的宏应被定义

I2C_INIT

(Optional). Any commands necessary to enable the I2C

controller or configure ports.

eg: #define I2C_INIT (immr->im_cpm.cp_pbdir |= PB_SCL)

I2C_PORT

(Only for MPC8260 CPU). The I/O port to use (the code

assumes both bits are on the same port). Valid values

are 0..3 for ports A..D.

I2C_ACTIVE

The code necessary to make the I2C data line active

(driven). If the data line is open collector, this

define can be null.

用来激活 I2C 数据线

eg: #define I2C_ACTIVE (immr->im_cpm.cp_pbdir |= PB_SDA)

I2C_TRISTATE

The code necessary to make the I2C data line tri-stated

(inactive). If the data line is open collector, this

define can be null.

eg: #define I2C_TRISTATE (immr->im_cpm.cp_pbdir &= ~PB_SDA)

I2C_READ

Code that returns TRUE if the I2C data line is high,

FALSE if it is low.

当 I2C 数据线为高则返回 TRUE ，为低则返回 FALSE

eg: #define I2C_READ ((immr->im_cpm.cp_pbdat & PB_SDA) != 0)

I2C_SDA(bit)

If <bit> is TRUE, sets the I2C data line high. If it

is FALSE, it clears it (low).

Bit 为 TRUE 则设置 I2C 数据线为高

eg: #define I2C_SDA(bit) /

if(bit) immr->im_cpm.cp_pbdat |= PB_SDA; /

else immr->im_cpm.cp_pbdat &= ~PB_SDA

I2C_SCL(bit)

If <bit> is TRUE, sets the I2C clock line high. If it

is FALSE, it clears it (low).

Bit 为 TRUE 则设置 I2C 时钟线为高

eg: #define I2C_SCL(bit) /

if(bit) immr->im_cpm.cp_pbdat |= PB_SCL; /

else immr->im_cpm.cp_pbdat &= ~PB_SCL

I2C_DELAY

This delay is invoked four times per clock cycle so this

controls the rate of data transfer.

一个时钟周期调用四次延时，所以它决定了数据传输速率

The data rate thus is

数据速率为 1 / (I2C_DELAY * 4) . Often defined to be something

like:

#define I2C_DELAY udelay(2)

CFG_I2C_INIT_BOARD

When a board is reset during an i2c bus transfer

chips might think that the current transfer is still

in progress. On some boards it is possible to access

the i2c SCLK line directly, either by using the

processor pin as a GPIO or by having a second pin

connected to the bus. If this option is defined a

custom i2c_init_board() routine in boards/xxx/board.c

is run early in the boot sequence.

CONFIG_I2CFAST (PPC405GP|PPC405EP only)

This option enables configuration of bi_iic_fast[] flags

in u-boot bd_info structure based on u-boot environment

variable "i2cfast". (see also i2cfast)

CONFIG_I2C_MULTI_BUS

This option allows the use of multiple I2C buses, each of which

must have a controller. At any point in time, only one bus is

active. To switch to a different bus, use the 'i2c dev' command.

Note that bus numbering is zero-based.

多 I2C 总线支持通过 'i2c dev' 命令切换

CFG_I2C_NOPROBES

This option specifies a list of I2C devices that will be skipped

when the 'i2c probe' command is issued (or 'iprobe' using the legacy

command).

当输入命令 'i2c probe' 时将跳过这些 I2C 设备

If CONFIG_I2C_MULTI_BUS is set, specify a list of bus-device

pairs. Otherwise, specify a 1D array of device addresses

e.g.

#undef CONFIG_I2C_MULTI_BUS

#define CFG_I2C_NOPROBES {0x50,0x68}

will skip addresses 0x50 and 0x68 on a board with one I2C bus

跳过地址 0x50 和 0x68

#define CONFIG_I2C_MULTI_BUS

#define CFG_I2C_MULTI_NOPROBES {{0,0x50},{0,0x68},{1,0x54}}

will skip addresses 0x50 and 0x68 on bus 0 and address 0x54 on bus 1

跳过总线 0 的地址 0x50 和 0x68 ，总线 1 的地址 0X54

CFG_SPD_BUS_NUM

If defined, then this indicates the I2C bus number for DDR SPD.

If not defined, then U-Boot assumes that SPD is on I2C bus 0.

指出 DDR SPD 所在 I2C 的总线，默认为 0 总线

CFG_RTC_BUS_NUM

If defined, then this indicates the I2C bus number for the RTC.

If not defined, then U-Boot assumes that RTC is on I2C bus 0.

CFG_DTT_BUS_NUM

If defined, then this indicates the I2C bus number for the DTT.

If not defined, then U-Boot assumes that DTT is on I2C bus 0.

CONFIG_FSL_I2C

Define this option if you want to use Freescale's I2C driver in

drivers/i2c/fsl_i2c.c .

若用飞思卡尔的 I2C 驱动则定义

- SPI Support:

- SPI 支持

CONFIG_SPI

Enables SPI driver (so far only tested with

SPI EEPROM, also an instance works with Crystal A/D and

D/As on the SACSng board)

CONFIG_SPI_X

Enables extended (16-bit) SPI EEPROM addressing.

(symmetrical to CONFIG_I2C_X)

CONFIG_SOFT_SPI

Enables a software (bit-bang) SPI driver rather than

using hardware support. This is a general purpose

driver that only requires three general I/O port pins

(two outputs, one input) to function. If this is

defined, the board configuration must define several

SPI configuration items (port pins to use, etc). For

an example, see include/configs/sacsng.h.

允许不依赖硬件的软件 SPI 驱动，若想使用此项，则还在定义一些 SPI 配置选项，如 IO 管脚等，查看 include/configs/sacsng.h.

CONFIG_HARD_SPI

Enables a hardware SPI driver for general-purpose reads

and writes. As with CONFIG_SOFT_SPI, the board configuration

must define a list of chip-select function pointers.

Currently supported on some MPC8xxx processors. For an

example, see include/configs/mpc8349emds.h.

CONFIG_MXC_SPI

Enables the driver for the SPI controllers on i.MX and MXC

SoCs. Currently only i.MX31 is supported.

- FPGA Support:

- FPGA 支持

CONFIG_FPGA

Enables FPGA subsystem.

CONFIG_FPGA_<vendor>

Enables support for specific chip vendors.

(ALTERA, XILINX)

CONFIG_FPGA_<family>

Enables support for FPGA family.

(SPARTAN2, SPARTAN3, VIRTEX2, CYCLONE2, ACEX1K, ACEX)

CONFIG_FPGA_COUNT

Specify the number of FPGA devices to support.

CFG_FPGA_PROG_FEEDBACK

Enable printing of hash marks during FPGA configuration.

CFG_FPGA_CHECK_BUSY

Enable checks on FPGA configuration interface busy

status by the configuration function. This option

will require a board or device specific function to

be written.

CONFIG_FPGA_DELAY

If defined, a function that provides delays in the FPGA

configuration driver.

CFG_FPGA_CHECK_CTRLC

Allow Control-C to interrupt FPGA configuration

CFG_FPGA_CHECK_ERROR

Check for configuration errors during FPGA bitfile

loading. For example, abort during Virtex II

configuration if the INIT_B line goes low (which

indicated a CRC error).

CFG_FPGA_WAIT_INIT

Maximum time to wait for the INIT_B line to deassert

after PROB_B has been deasserted during a Virtex II

FPGA configuration sequence. The default time is 500

ms.

CFG_FPGA_WAIT_BUSY

Maximum time to wait for BUSY to deassert during

Virtex II FPGA configuration. The default is 5 ms.

CFG_FPGA_WAIT_CONFIG

Time to wait after FPGA configuration. The default is

200 ms.

- Configuration Management:

- 结构管理

CONFIG_IDENT_STRING

If defined, this string will be added to the U-Boot

version information (U_BOOT_VERSION)

定义的字符串将出现在 UBOOT 版本信息里

- Vendor Parameter Protection:

卖主参数保护

U-Boot considers the values of the environment

variables "serial#" (Board Serial Number) and

"ethaddr" (Ethernet Address) to be parameters that

are set once by the board vendor / manufacturer, and

protects these variables from casual modification by

the user. Once set, these variables are read-only,

and write or delete attempts are rejected.

UBOOT 把环境变量 "serial#" 和 "ethaddr" 当作板卖主或是制造商一次性写入的，为防止用户偶然性的更改而对这些变量加以保护，一旦设置，这些变量就为只读，所有写入或删除操作将被拒绝

You can change this behaviour:

If CONFIG_ENV_OVERWRITE is #defined in your config

file, the write protection for vendor parameters is

completely disabled. Anybody can change or delete

these parameters.

一旦 CONFIG_ENV_OVERWRITE 在配置文件中被定义，则所有卖主参数的写保护都被禁止，任何人可以进行更改和读写

Alternatively, if you #define _both_ CONFIG_ETHADDR

_and_ CONFIG_OVERWRITE_ETHADDR_ONCE , a default

Ethernet address is installed in the environment,

which can be changed exactly ONCE by the user. [The

serial# is unaffected by this, i. e. it remains

read-only.]

- Protected RAM:

- 保护 RAM

CONFIG_PRAM

Define this variable to enable the reservation of

"protected RAM", i. e. RAM which is not overwritten

by U-Boot.

保护的 RAM 将不会被 UBOOT 覆盖

Define CONFIG_PRAM to hold the number of

kB you want to reserve for pRAM.

定义你想保护的字节大小，单位为 KB

You can overwrite

this default value by defining an environment

variable "pram" to the number of kB you want to

reserve. Note that the board info structure will

still show the full amount of RAM. If pRAM is

reserved, a new environment variable "mem" will

automatically be defined to hold the amount of

remaining RAM in a form that can be passed as boot

argument to Linux, for instance like that:

setenv bootargs ... mem=/${mem}

saveenv

This way you can tell Linux not to use this memory,

either, which results in a memory region that will

not be affected by reboots.

*WARNING* If your board configuration uses automatic

detection of the RAM size, you must make sure that

this memory test is non-destructive.

若板子配置为自动检测 RAM 大小，请确保检测是无损的

So far, the

following board configurations are known to be

"pRAM-clean":

ETX094, IVMS8, IVML24, SPD8xx, TQM8xxL,

HERMES, IP860, RPXlite, LWMON, LANTEC,

PCU_E, FLAGADM, TQM8260

- Error Recovery:

- 错误纠正

CONFIG_PANIC_HANG

Define this variable to stop the system in case of a

fatal error, so that you have to reset it manually.

一旦发生错误就停止系统，并要手动重启

This is probably NOT a good idea for an embedded

system where you want the system to reboot

automatically as fast as possible, but it may be

useful during development since you can try to debug

the conditions that lead to the situation.

CONFIG_NET_RETRY_COUNT

This variable defines the number of retries for

network operations like ARP, RARP, TFTP, or BOOTP

before giving up the operation. If not defined, a

default value of 5 is used.

定义网络操作的重试次数，默认为 5

CONFIG_ARP_TIMEOUT

Timeout waiting for an ARP reply in milliseconds.

- Command Interpreter:

- 命令解释

CONFIG_AUTO_COMPLETE

Enable auto completion of commands using TAB.

允许用 TAB 来自动完成命令

Note that this feature has NOT been implemented yet

for the "hush" shell.

CFG_HUSH_PARSER

Define this variable to enable the "hush" shell (from

Busybox) as command line interpreter, thus enabling

powerful command line syntax like

if...then...else...fi conditionals or `&&' and '||'

constructs ("shell scripts").

If undefined, you get the old, much simpler behaviour

with a somewhat smaller memory footprint.

CFG_PROMPT_HUSH_PS2

This defines the secondary prompt string, which is

printed when the command interpreter needs more input

to complete a command. Usually "> ".

定义命令行的第二个提示符

Note:

In the current implementation, the local variables

space and global environment variables space are

separated. Local variables are those you define by

simply typing `name=value'. To access a local

variable later on, you have write `$name' or

`${name}'; to execute the contents of a variable

directly type `$name' at the command prompt.

目前本地变量空间和全局环境变量空间是分开的，本地变量是通过

`name=value' 定义的，可通过 `$name' 或 `${name}' 来访问，在命令提示符下输入 `$name' 来访问变量内容

Global environment variables are those you use

setenv/printenv to work with. To run a command stored

in such a variable, you need to use the run command,

and you must not use the '$' sign to access them.

全局环境变量是通过 setenv/printenv 来运行和访问的

To store commands and special characters in a

variable, please use double quotation marks

surrounding the whole text of the variable, instead

of the backslashes before semicolons and special

symbols.

- Commandline Editing and History:

CONFIG_CMDLINE_EDITING

Enable editing and History functions for interactive

commandline input operations

- Default Environment:

CONFIG_EXTRA_ENV_SETTINGS

Define this to contain any number of null terminated

strings (variable = value pairs) that will be part of

the default environment compiled into the boot image.

For example, place something like this in your

board's config file:

#define CONFIG_EXTRA_ENV_SETTINGS /

"myvar1=value1/0" /

"myvar2=value2/0"

Warning: This method is based on knowledge about the

internal format how the environment is stored by the

U-Boot code. This is NOT an official, exported

interface! Although it is unlikely that this format

will change soon, there is no guarantee either.

You better know what you are doing here.

Note: overly (ab)use of the default environment is

discouraged. Make sure to check other ways to preset

the environment like the autoscript function or the

boot command first.

- DataFlash Support:

- 数据 Flash 支持

CONFIG_HAS_DATAFLASH

Defining this option enables DataFlash features and

allows to read/write in Dataflash via the standard

commands cp, md...

定义此项来允许数据 Flash 特性，如 cp,md 命令

- SystemACE Support:

CONFIG_SYSTEMACE

Adding this option adds support for Xilinx SystemACE

chips attached via some sort of local bus. The address

of the chip must also be defined in the

CFG_SYSTEMACE_BASE macro. For example:

#define CONFIG_SYSTEMACE

#define CFG_SYSTEMACE_BASE 0xf0000000

When SystemACE support is added, the "ace" device type

becomes available to the fat commands, i.e. fatls.

- TFTP Fixed UDP Port:

- TFTP 固定 UDP 端口

CONFIG_TFTP_PORT

If this is defined, the environment variable tftpsrcp

is used to supply the TFTP UDP source port value.

If tftpsrcp isn't defined, the normal pseudo-random port

number generator is used.

若被定义则环境变量 tftpsrcp 用来提供 TFTP UDP 源端口值，

若 tftpsrcp 没被定义则默认一个伪随机端口

Also, the environment variable tftpdstp is used to supply

the TFTP UDP destination port value. If tftpdstp isn't

defined, the normal port 69 is used.

Tftpdstp 环境变来用来指定目的端口，若不定义则默认 69

The purpose for tftpsrcp is to allow a TFTP server to

blindly start the TFTP transfer using the pre-configured

target IP address and UDP port. This has the effect of

"punching through" the (Windows XP) firewall, allowing

the remainder of the TFTP transfer to proceed normally.

A better solution is to properly configure the firewall,

but sometimes that is not allowed.

- Show boot progress:

- 显示 BOOT 过程

CONFIG_SHOW_BOOT_PROGRESS

Defining this option allows to add some board-

specific code (calling a user-provided function

"show_boot_progress(int)") that enables you to show

the system's boot progress on some display (for

example, some LED's) on your board. At the moment,

the following checkpoints are implemented:

允许用户通过调用函数 "show_boot_progress(int)" 在特定设备显示系统启动过程，此刻下面的检查点将被执行

Legacy uImage format:

Arg Where When

1 common/cmd_bootm.c before attempting to boot an image

-1 common/cmd_bootm.c Image header has bad magic number

2 common/cmd_bootm.c Image header has correct magic number

-2 common/cmd_bootm.c Image header has bad checksum

3 common/cmd_bootm.c Image header has correct checksum

-3 common/cmd_bootm.c Image data has bad checksum

4 common/cmd_bootm.c Image data has correct checksum

-4 common/cmd_bootm.c Image is for unsupported architecture

5 common/cmd_bootm.c Architecture check OK

-5 common/cmd_bootm.c Wrong Image Type (not kernel, multi)

6 common/cmd_bootm.c Image Type check OK

-6 common/cmd_bootm.c gunzip uncompression error

-7 common/cmd_bootm.c Unimplemented compression type

7 common/cmd_bootm.c Uncompression OK

8 common/cmd_bootm.c No uncompress/copy overwrite error

-9 common/cmd_bootm.c Unsupported OS (not Linux, BSD, VxWorks, QNX)

9 common/image.c Start initial ramdisk verification

-10 common/image.c Ramdisk header has bad magic number

-11 common/image.c Ramdisk header has bad checksum

10 common/image.c Ramdisk header is OK

-12 common/image.c Ramdisk data has bad checksum

11 common/image.c Ramdisk data has correct checksum

12 common/image.c Ramdisk verification complete, start loading

-13 common/image.c Wrong Image Type (not PPC Linux ramdisk)

13 common/image.c Start multifile image verification

14 common/image.c No initial ramdisk, no multifile, continue.

15 lib_<arch>/bootm.c All preparation done, transferring control to OS

-30 lib_ppc/board.c Fatal error, hang the system

-31 post/post.c POST test failed, detected by post_output_backlog()

-32 post/post.c POST test failed, detected by post_run_single()

34 common/cmd_doc.c before loading a Image from a DOC device

-35 common/cmd_doc.c Bad usage of "doc" command

35 common/cmd_doc.c correct usage of "doc" command

-36 common/cmd_doc.c No boot device

36 common/cmd_doc.c correct boot device

-37 common/cmd_doc.c Unknown Chip ID on boot device

37 common/cmd_doc.c correct chip ID found, device available

-38 common/cmd_doc.c Read Error on boot device

38 common/cmd_doc.c reading Image header from DOC device OK

-39 common/cmd_doc.c Image header has bad magic number

39 common/cmd_doc.c Image header has correct magic number

-40 common/cmd_doc.c Error reading Image from DOC device

40 common/cmd_doc.c Image header has correct magic number

41 common/cmd_ide.c before loading a Image from a IDE device

-42 common/cmd_ide.c Bad usage of "ide" command

42 common/cmd_ide.c correct usage of "ide" command

-43 common/cmd_ide.c No boot device

43 common/cmd_ide.c boot device found

-44 common/cmd_ide.c Device not available

44 common/cmd_ide.c Device available

-45 common/cmd_ide.c wrong partition selected

45 common/cmd_ide.c partition selected

-46 common/cmd_ide.c Unknown partition table

46 common/cmd_ide.c valid partition table found

-47 common/cmd_ide.c Invalid partition type

47 common/cmd_ide.c correct partition type

-48 common/cmd_ide.c Error reading Image Header on boot device

48 common/cmd_ide.c reading Image Header from IDE device OK

-49 common/cmd_ide.c Image header has bad magic number

49 common/cmd_ide.c Image header has correct magic number

-50 common/cmd_ide.c Image header has bad checksum

50 common/cmd_ide.c Image header has correct checksum

-51 common/cmd_ide.c Error reading Image from IDE device

51 common/cmd_ide.c reading Image from IDE device OK

52 common/cmd_nand.c before loading a Image from a NAND device

-53 common/cmd_nand.c Bad usage of "nand" command

53 common/cmd_nand.c correct usage of "nand" command

-54 common/cmd_nand.c No boot device

54 common/cmd_nand.c boot device found

-55 common/cmd_nand.c Unknown Chip ID on boot device

55 common/cmd_nand.c correct chip ID found, device available

-56 common/cmd_nand.c Error reading Image Header on boot device

56 common/cmd_nand.c reading Image Header from NAND device OK

-57 common/cmd_nand.c Image header has bad magic number

57 common/cmd_nand.c Image header has correct magic number

-58 common/cmd_nand.c Error reading Image from NAND device

58 common/cmd_nand.c reading Image from NAND device OK

-60 common/env_common.c Environment has a bad CRC, using default

64 net/eth.c starting with Ethernet configuration.

-64 net/eth.c no Ethernet found.

65 net/eth.c Ethernet found.

-80 common/cmd_net.c usage wrong

80 common/cmd_net.c before calling NetLoop()

-81 common/cmd_net.c some error in NetLoop() occurred

81 common/cmd_net.c NetLoop() back without error

-82 common/cmd_net.c size == 0 (File with size 0 loaded)

82 common/cmd_net.c trying automatic boot

83 common/cmd_net.c running autoscript

-83 common/cmd_net.c some error in automatic boot or autoscript

84 common/cmd_net.c end without errors

FIT uImage format:

Arg Where When

100 common/cmd_bootm.c Kernel FIT Image has correct format

-100 common/cmd_bootm.c Kernel FIT Image has incorrect format

101 common/cmd_bootm.c No Kernel subimage unit name, using configuration

-101 common/cmd_bootm.c Can't get configuration for kernel subimage

102 common/cmd_bootm.c Kernel unit name specified

-103 common/cmd_bootm.c Can't get kernel subimage node offset

103 common/cmd_bootm.c Found configuration node

104 common/cmd_bootm.c Got kernel subimage node offset

-104 common/cmd_bootm.c Kernel subimage hash verification failed

105 common/cmd_bootm.c Kernel subimage hash verification OK

-105 common/cmd_bootm.c Kernel subimage is for unsupported architecture

106 common/cmd_bootm.c Architecture check OK

-106 common/cmd_bootm.c Kernel subimage has wrong type

107 common/cmd_bootm.c Kernel subimage type OK

-107 common/cmd_bootm.c Can't get kernel subimage data/size

108 common/cmd_bootm.c Got kernel subimage data/size

-108 common/cmd_bootm.c Wrong image type (not legacy, FIT)

-109 common/cmd_bootm.c Can't get kernel subimage type

-110 common/cmd_bootm.c Can't get kernel subimage comp

-111 common/cmd_bootm.c Can't get kernel subimage os

-112 common/cmd_bootm.c Can't get kernel subimage load address

-113 common/cmd_bootm.c Image uncompress/copy overwrite error

120 common/image.c Start initial ramdisk verification

-120 common/image.c Ramdisk FIT image has incorrect format

121 common/image.c Ramdisk FIT image has correct format

122 common/image.c No ramdisk subimage unit name, using configuration

-122 common/image.c Can't get configuration for ramdisk subimage

123 common/image.c Ramdisk unit name specified

-124 common/image.c Can't get ramdisk subimage node offset

125 common/image.c Got ramdisk subimage node offset

-125 common/image.c Ramdisk subimage hash verification failed

126 common/image.c Ramdisk subimage hash verification OK

-126 common/image.c Ramdisk subimage for unsupported architecture

127 common/image.c Architecture check OK

-127 common/image.c Can't get ramdisk subimage data/size

128 common/image.c Got ramdisk subimage data/size

129 common/image.c Can't get ramdisk load address

-129 common/image.c Got ramdisk load address

-130 common/cmd_doc.c Incorrect FIT image format

131 common/cmd_doc.c FIT image format OK

-140 common/cmd_ide.c Incorrect FIT image format

141 common/cmd_ide.c FIT image format OK

-150 common/cmd_nand.c Incorrect FIT image format

151 common/cmd_nand.c FIT image format OK

Modem Support:

调制解调器支持

--------------

[so far only for SMDK2400 and TRAB boards]

目前只支持 SMDK2400 和 TRAB 板

- Modem support enable:

CONFIG_MODEM_SUPPORT

- RTS/CTS Flow control enable:

CONFIG_HWFLOW

- Modem debug support:

CONFIG_MODEM_SUPPORT_DEBUG

Enables debugging stuff (char screen[1024], dbg())

for modem support. Useful only with BDI2000.

- Interrupt support (PPC):

- 中断支持（ PPC ）

There are common interrupt_init() and timer_interrupt()

for all PPC archs. interrupt_init() calls interrupt_init_cpu()

for CPU specific initialization. interrupt_init_cpu()

should set decrementer_count to appropriate value. If

CPU resets decrementer automatically after interrupt

(ppc4xx) it should set decrementer_count to zero.

timer_interrupt() calls timer_interrupt_cpu() for CPU

specific handling. If board has watchdog / status_led

/ other_activity_monitor it works automatically from

general timer_interrupt().

- General:

In the target system modem support is enabled when a

specific key (key combination) is pressed during

power-on. Otherwise U-Boot will boot normally

(autoboot). The key_pressed() function is called from

board_init(). Currently key_pressed() is a dummy

function, returning 1 and thus enabling modem

initialization.

If there are no modem init strings in the

environment, U-Boot proceed to autoboot; the

previous output (banner, info printfs) will be

suppressed, though.

uboot readme相关推荐

uboot readme 文件 (1)
Software Configuration: ======================= 软件的配置 Configuration is usually done using C preproce ...
u-boot README翻译
u-boot 根目录README文件翻译 Summary Status Where to get help Where to get source code Where we come from N ...
【嵌入式开发】 Bootloader 详解 ( 代码环境 | ARM 启动流程 | uboot 工作流程 | 架构设计)
作者 : 韩曙亮博客地址 : http://blog.csdn.net/shulianghan/article/details/42462795 转载请著名出处相关资源下载 : -- u-boo ...
iMX6Q Sabresd Board SPL Mode
uboot 2014以后的版本已经加入了支持快速启动的spl模式,本文用iMX6Q-SDP开发板做个简单讲解在官方的yocot中下载fsl-L4.9.11_1.0.0-ga版本代码并编译,提取出ub ...
移植u-boot-2009-11-S3c44b0公板
移植u-boot-2009-11->S3c44b0公板 by panasonic.lin@163.com 网上有关porting u-boot for 44b0的大牛们的教程绝大多数都是以dav ...
uboot的readme导读(转)
uboot的readme导读(转) UBOOT的移植其实并没有想象中的难,这主要归功于众多的工程师已经将常见的平台代码写入了UBOOT,我们所要做的就是一点小小的更改,在网上看了很多相关的移植,也 ...
Uboot学习笔记①---(文件目录结构、README摘要、uImage的64字节头信息)
uboot下载地址ftp://ftp.denx.de/pub/u-boot/ 1.查看uboot文件目录结构 Directory Hierarchy: ====================/arc ...
[u-boot 2020.07] README
挖坑,难填! 摘要: 状态: 在哪里获得帮助: 在哪里获取源代码: 我们来自哪里: 名称和拼写: 版本控制: 目录层次结构: 软件配置: 处理器架构和板类型的选择: 沙盒环境(Sandbox): Bo ...
uboot源码分析笔记
前几天看了ucos的源码,后面开始学习uboot的源码网上看到一些uboot的文章,当然都是牛人写出来的,不过基本版本有点老,我这越是初学者,越想学习新版本的代码我下载的是u-boot-2014. ...

uboot readme

uboot readme相关推荐

最新文章

热门文章