startAdvertising(_:) - CBPeripheralManager | Apple Developer Documentation
Instance MethodAdvertises peripheral manager data.SDKsiOS 6.0+macOS 10.9+tvOS 9.0+watchOS 4.0+FrameworkCore BluetoothDeclarationfunc startAdvertising(_ advertisementData: [ : Any]?)
ParametersadvertisementDataAn optional dictionary containing the data you want to advertise. The possible keys of an advertisementData dictionary are detailed in . That said, only two of the keys are supported for peripheral manager objects:
and .DiscussionWhen you start advertising peripheral data, the peripheral manager calls the
method of its delegate object.Data advertising is done on a “best effort” basis, because space is limited and there may be multiple apps advertising simultaneously. While your app is in the foreground, it can use up to 28 bytes of space in the initial advertisement data for any combination of the supported advertising data keys. If this space is used up, there are an additional 10 bytes of space in the scan response that can be used only for the local name (represented by the value of the
key). Note that these sizes do not include the 2 bytes of header information that are required for each new data type. Any service universally unique identifiers (UUIDs) contained in the value of the
key that do not fit in the allotted space are added to a special “overflow” they can be discovered only by an iOS device that is explicitly scanning for them. While your app is in the background, the local name is not advertised and all service UUIDs are placed in the overflow area. The exact format of advertising and response data is defined in the Bluetooth 4.0 specification, Volume 3, Part C, Section 11.See AlsoManaging AdvertisingRelated Documentation扫一扫体验手机阅读
go语言创建新进程过程详解一（os.StartProcess源码分析，一下代码全部来源于go1.4.2源码）
<span type="1" blog_id="1747146" userid='
2篇文章，7735人气，0粉丝
大数据时代的微服务之路
￥51.00408人订阅
<span type="1" blog_id="1747146" userid='uboot2011.09源代码ReadMe译文
# (C) Copyright 2000 - 2011
# Wolfgang Denk, DENX Software Engineering, wd@denx.de.
#查看建立这个工程的文件列表人
#这个程序是自由软件，你可以重新分配它或者修改它在GNU通用公共许可证以由自由软件基#金会发布；第二版或者任何之后的版本。
#本程序是分布在希望它是有用的，但没有任何保证；甚至没有隐含保证。
#查看 GNU通用公共许可证对于更多的细节。
#你应该收到一份GNU通用公共许可证随着这个程序；如果没有，写信给自由软件组织。59
#Temple Place, Suite 330, Boston, MA
这个目录包含了U-Boot的源码，一个引导装载程序为基于PowerPC嵌入式板，ARM，MIPS和其他几个处理器，它可以安装在启动ROM和使用初始化和测试硬件或下载并运行应用程序代码。
U-Boot的发展与Linux是密切相关的。部分的源代码是在Linux源代码树里。我们有一些常用的头文件，并特别规定了支持引导Linux镜像。
一些关注使得这个软件更容易配置和可扩展。例如，，所有的监控命令以相同的调用接口实现，因此，它很容易添加新的命令。同时，取代永久增加很少使用代码（例如硬件测试程序）的监测，你动态地可以加载和运行它。
一般来说，所有的板中存在一个Makefile文件已经过测试，在一定程度上可以考虑“工作”。事实上，他们中的许多人都用在生产系统。遇到问题时请在CHANGELOG和CREDITS文件中查找谁贡献的特定端口。MAINTAINERS文件列出了板的维护人员。
从哪里获得帮助：
==================
如果你有问题，或对问题的贡献U-boot。你应该将消息发送到邮件&u-boot@lists.denx.de&。还有以往交通档案在邮件列表，请在要求的常见问题解答。搜索归档
请看http://lists.denx.de/pipermail/u-boot和http://dir.gmane.org/gmane.comp.boot-loaders.u-boot
从哪里获得源代码：
=========================
U-Boot源代码保存在Git库
git://www.denx.de/git/u-boot.git；你可以在网上浏览http://www.denx.de/cgi-bin/gitweb.cgi?p=u-boot.a=summary。“快照”这个网页上的链接允许你下载的压缩包任何版本，你可能会感兴趣。官方发布，也可从ftp://ftp.denx.de/pub/u-boot/
FTP下载目录。
预建的（和测试）的图像可从
我们从哪里来：
===================
从8xxrom源启动
创建PPCBoot项目（http://sourceforge.net/projects/ppcboot）
-使它更容易添加自定义板
-可以添加其他] [ PowerPC处理器
扩展功能，尤其是：
*提供扩展接口，Linux引导装载程序
* pcmcia / CompactFlash / ATA磁盘/ SCSI…启动
创建项目（http://sourceforge.net/projects/armboot）armboot
添加其他CPU的家族（从arm开始）
创建U-Boot项目（http://sourceforge.net/projects/u-boot）
目前项目页面：看http://www.denx.de/wiki/u-boot
名称和拼写：
===================
该项目的“官方”的名字是“DAS u-boot”。拼写
“U-Boot”应该被应用于所有的书面文本（文档，评论
在源文件等）。例：
这是u-boot工程的自述文件。
文件名等应该被基于字符串“u-boot”。例：
#include/asm-ppc/u-boot.h
#include &asm/u-boot.h&
变量名称，预处理器常量等应基于
字符串“u_boot”或“u_boot”。例：
U_BOOT_VERSIONu_boot_logo
IH_OS_U_BOOTu_boot_hush_start
版本控制：
===========
从十月2008开始发布，发布的名字改变数值的版本号没有更深的意义，在基于时间戳的编号。定期发布是确定的组成的发布日期的日历年和月的名字。额外的域（如果存在）表示的候选发布或bug修复发布在“稳定”维护树。
U-Boot v2009.11
- Release November 2009
- Release 1 in version November 2009 stable tree
U-Boot v2010.09-rc1 - Release candiate 1 for September 2010 release
目录层次：
====================
Directory Hierarchy:
====================
特定结构的文件
/arm 通用的arm体系文件
/cpu CPU 特定文件
/arm720t Files specific to ARM 720 CPUs
/arm920t Files specific to ARM 920 CPUs
/at91 Files specific to Atmel AT91RM9200 CPU
/imx Files specific to Freescale MC9328 i.MX CPUs
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
/ixp Files specific to Intel XScale IXP CPUs
/pxa Files specific to Intel XScale PXA CPUs
/s3c44b0Files specific to Samsung S3C44B0 CPUs
/sa1100Files specific to Intel StrongARM SA1100 CPUs
/libArchitecture specific library files
/avr32Files generic to AVR32 architecture
/cpuCPU specific files
/libArchitecture specific library files
/blackfinFiles generic to Analog Devices Blackfin architecture
/cpuCPU specific files
/libArchitecture specific library files
/x86Files generic to x86 architecture
/cpuCPU specific files
/libArchitecture specific library files
/m68kFiles generic to m68k architecture
/cpuCPU specific files
/mcf52x2Files specific to Freescale ColdFire MCF52x2 CPUs
/mcf5227xFiles specific to Freescale ColdFire MCF5227x CPUs
/mcf532xFiles specific to Freescale ColdFire MCF5329 CPUs
/mcf5445xFiles specific to Freescale ColdFire MCF5445x CPUs
/mcf547x_8xFiles specific to Freescale ColdFire MCF547x_8x CPUs
/libArchitecture specific library files
/microblazeFiles generic to microblaze architecture
/cpuCPU specific files
/libArchitecture specific library files
/mipsFiles generic to MIPS architecture
/cpuCPU specific files
/mips32Files specific to MIPS32 CPUs
/libArchitecture specific library files
/nios2Files generic to Altera NIOS2 architecture
/cpuCPU specific files
/libArchitecture specific library files
/powerpcFiles generic to PowerPC architecture
/cpuCPU specific files
/74xx_7xxFiles specific to Freescale MPC74xx and 7xx CPUs
/mpc5xxFiles specific to Freescale MPC5xx CPUs
/mpc5xxxFiles specific to Freescale MPC5xxx CPUs
/mpc8xxFiles specific to Freescale MPC8xx CPUs
/mpc8220Files specific to Freescale MPC8220 CPUs
/mpc824xFiles specific to Freescale MPC824x CPUs
/mpc8260Files specific to Freescale MPC8260 CPUs
/mpc85xxFiles specific to Freescale MPC85xx CPUs
/ppc4xxFiles specific to AMCC PowerPC 4xx CPUs
/libArchitecture specific library files
/shFiles generic to SH architecture
/cpuCPU specific files
/sh2Files specific to sh2 CPUs
/sh3Files specific to sh3 CPUs
/sh4Files specific to sh4 CPUs
/libArchitecture specific library files
/sparcFiles generic to SPARC architecture
/cpuCPU specific files
/leon2Files specific to Gaisler LEON2 SPARC CPU
/leon3Files specific to Gaisler LEON3 SPARC CPU
/libArchitecture specific library files
/apiMachine/arch independent API for external apps
/boardBoard dependent files
/commonMisc architecture independent functions
/diskCode for disk drive partition handling
/docDocumentation (don't expect too much)
/driversCommonly used device drivers
/examplesExample code for standalone applications, etc.
/fsFilesystem code (cramfs, ext2, jffs2, etc.)
/includeHeader Files
/libFiles generic to all architectures
/libfdtLibrary files to support flattened device trees
/lzmaLibrary files to support LZMA decompression
/lzoLibrary files to support LZO decompression
/netNetworking code
/postPower On Self Test
/rtcReal Time Clock drivers
/toolsTools to build S-Record or U-Boot images, etc.
软件配置：
=======================
配置通常是使用C预处理器定义的；原因是尽可能避免死代码。
有两种类型的配置变量：
* Configuration _OPTIONS_:
这些都是由用户选定的和的名字开始
"CONFIG_".
* Configuration _SETTINGS_:
这取决于硬件等不应干预如果
你不知道你在做什么；他们的名字开始
"CONFIG_SYS_".
后面我们会添加一个配置工具可能类似于甚至什么是用于Linux内核相同。现在，我们必须
手动完成配置，这意味着创建一些符号链接和编辑配置文件。我们使用TQM8xxL开发板作为一个例子。
选择处理器架构和开发板类型：
---------------------------------------------------
所有支持的板有准备使用的默认配置；
比如"make &board_name&_config"
例如：一个tqm823l模块类型：
make TQM823L_config
对于确定的平台，你同样需要指定CPU类型；
例. "make cogent_mpc8xx_config"并配置有说服力的记录文件。
配置选项：
----------------------
配置取决于板、CPU类型组合；所有这些信息保存在配置文件
"include/configs/&board_name&.h".
例如：一个tqm823l模块，所有配置设置在
"include/configs/TQM823L.h".
有许多选项准确命名为相应的Linux内核配置选项。目的是使它更容易建立一个配置工具后。
需要配置的选项如下：
- CPU Type:正确地定义一个， e.g.
CONFIG_MPC85XX.
- Board Type:Define exactly one, e.g. CONFIG_MPC8540ADS.
- CPU 子板Type: (if CONFIG_ATSTK1000 is defined)
正确地定义一个 , e.g. CONFIG_ATSTK1002
- CPU Module Type: (if CONFIG_COGENT is defined)
Define exactly one of
CONFIG_CMA286_60_OLD
--- FIXME --- not tested yet:
CONFIG_CMA286_60, CONFIG_CMA286_21, CONFIG_CMA286_60P,
CONFIG_CMA287_23, CONFIG_CMA287_50
- 主板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
- Motherboard Options: (if CONFIG_CMA101 or CONFIG_CMA102 are defined)
Define one or more of
CONFIG_LCD_HEARTBEAT- 更新一个字符的位置上液晶显示器的每一秒“旋转”|\-/|\-/
- Board 风格: (if CONFIG_MPC8260ADS is defined)
CONFIG_ADSTYPE
Possible values are:
CONFIG_SYS_8260ADS- original MPC8260ADS
CONFIG_SYS_8266ADS- MPC8266ADS
CONFIG_SYS_PQ2FADS- PQ2FADS-ZU or PQ2FADS-VR
CONFIG_SYS_8272ADS- MPC8272ADS
- Marvell Family Member
CONFIG_SYS_MVFS- define it if you want to enable
multiple fs option at one time
for marvell soc family
- 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):
CONFIG_SYS_8xx_CPUCLK_MIN
CONFIG_SYS_8xx_CPUCLK_MAX
CONFIG_8xx_CPUCLK_DEFAULT
See doc/README.MPC866
CONFIG_SYS_MEASURE_CPUCLK
定义此来衡量实际的CPU时钟而不是 依靠正确的配置 价值观。通常用于单板确保 锁相环锁定在预定的频率。注意 这需要一个（稳定）的参考时钟（32千赫 RTC时钟或config_sys_8xx_xin）(32
kHzRTC clock or CONFIG_SYS_8XX_XIN)
CONFIG_SYS_DELAYED_ICACHE
定义这个选项，当代码在ram中运行的时候如果你想使能iCache.
- 85xx CPU Options:
CONFIG_SYS_FSL_TBCLK_DIV
定义核心时基时钟分频比的 系统时钟。在大多数PQ3设备这是8，在新的QorIQ 设备可以是16或32。从SOC SOC的变化率。
CONFIG_SYS_FSL_PCIE_COMPAT
当试图定义利用PCIE设备的字符串匹配 对于给定的平台树节点。
- Intel Monahans options:
CONFIG_SYS_MONAHANS_RUN_MODE_OSC_RATIO
定义了Monahans的运行模式振荡器 比。有效值是8，16，24，31。核心 频率是这个值乘以13兆赫。
CONFIG_SYS_MONAHANS_TURBO_RUN_MODE_RATIO
定义的模式振荡器的Monahans的涡轮增压器 比。有效的值（默认为1，如果未定义） 2。上面的核心是计算的频率倍增 通过这个值。
- MIPS CPU options:
CONFIG_SYS_INIT_SP_OFFSET
Offset relative to CONFIG_SYS_SDRAM_BASE for initial stack
pointer. This is needed for the temporary stack before
relocation.
相对于config_sys_sdram_base初始偏移
指针。这是需要临时栈之前
CONFIG_SYS_MIPS_CACHE_MODE
Cache operation mode for the MIPS CPU.
See also arch/mips/include/asm/mipsregs.h.
Possible values are:
CONF_CM_CACHABLE_NO_WA
CONF_CM_CACHABLE_WA
CONF_CM_UNCACHED
CONF_CM_CACHABLE_NONCOHERENT
CONF_CM_CACHABLE_CE
CONF_CM_CACHABLE_COW
CONF_CM_CACHABLE_CUW
CONF_CM_CACHABLE_ACCELERATED
CONFIG_SYS_XWAY_EBU_BOOTCFG
Special option for Lantiq XWAY SoCs for booting from NOR flash.
See also arch/mips/cpu/mips32/start.S.
CONFIG_XWAY_SWAP_BYTES
Enable compilation of tools/xway-swap-bytes needed for Lantiq
XWAY SoCs for booting from NOR flash. The U-Boot image needs to
be swapped if a flash programmer is used.
- Linux Kernel Interface:
CONFIG_CLOCKS_IN_MHZ
U-Boot stores all clock information in Hz
internally. For binary compatibility with older Linux
kernels (which expect the clocks passed in the
bd_info data to be in MHz) 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.
When CONFIG_CLOCKS_IN_MHZ is defined, a definition of
"clocks_in_mhz=1" is automatically included in the
default environment.
CONFIG_MEMSIZE_IN_BYTES[relevant for MIPS only]
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_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 (only required for
MPC512X and MPC5xxx based boards).
OF_SOC - The proper name of the soc node (only required for
MPC512X and MPC5xxx based boards).
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
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.
CONFIG_OF_IDE_FIXUP
U-Boot can detect if an IDE device is present or not.
If not, and this new config option is activated, U-Boot
removes the ATA node from the DTS before booting Linux,
so the Linux IDE driver does not probe the device and
crash. This is needed for buggy hardware (uc101) where
no pull down resistor is connected to the signal IDE5V_DD7.
CONFIG_MACH_TYPE[relevant for ARM only][mandatory]
This setting is mandatory for all boards that have only one
machine type and must be used to specify the machine type
number as it appears in the ARM machine registry
(see http://www.arm.linux.org.uk/developer/machines/).
Only boards that have multiple machine types supported
in a single configuration file and the machine type is
runtime discoverable, do not have to use this setting.
- vxWorks boot parameters:
bootvx constructs a valid bootline using the following
environments variables: bootfile, ipaddr, serverip, hostname.
It loads the vxWorks image pointed bootfile.
CONFIG_SYS_VXWORKS_BOOT_DEVICE - The vxworks device name
CONFIG_SYS_VXWORKS_MAC_PTR - Ethernet 6 byte MA -address
CONFIG_SYS_VXWORKS_SERVERNAME - Name of the server
CONFIG_SYS_VXWORKS_BOOT_ADDR - Address of boot parameters
CONFIG_SYS_VXWORKS_ADD_PARAMS
Add it at the end of the bootline. E.g "u=username pw=secret"
Note: If a "bootargs" environment is defined, it will overwride
the defaults discussed just above.
- Cache Configuration:
CONFIG_SYS_ICACHE_OFF - Do not enable instruction cache in U-Boot
CONFIG_SYS_DCACHE_OFF - Do not enable data cache in U-Boot
CONFIG_SYS_L2CACHE_OFF- Do not enable L2 cache in U-Boot
- Cache Configuration for ARM:
CONFIG_SYS_L2_PL310 - Enable support for ARM PL310 L2 cache
controller
CONFIG_SYS_PL310_BASE - Physical base address of PL310
controller register space
- Serial Ports:
CONFIG_PL010_SERIAL
Define this if you want support for Amba PrimeCell PL010 UARTs.
CONFIG_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
CONFIG_PL011_SERIAL_RLCR
Some vendor versions of PL011 serial ports (e.g. ST-Ericsson U8500)
have separate receive and transmit line control registers.
this variable to initialize the extra register.
CONFIG_PL011_SERIAL_FLUSH_ON_INIT
On some platforms (e.g. U8500) U-Boot is loaded by a second stage
boot loader that has already initialized the UART.
Define this
variable to flush the UART at init time.
- 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_ENDIANgraphic memory organisation
(default big endian)
VIDEO_HW_RECTFILLgraphic chip supports
rectangle fill
(cf. smiLynxEM)
VIDEO_HW_BITBLTgraphic chip supports
bit-blit (cf. smiLynxEM)
VIDEO_VISIBLE_COLSvisible pixel columns
(cols=pitch)
VIDEO_VISIBLE_ROWSvisible pixel rows
VIDEO_PIXEL_SIZEbytes per pixel
VIDEO_DATA_FORMATgraphic data format
(0-5, cf. cfb_console.c)
VIDEO_FB_ADRSframebuffer address
VIDEO_KBD_INIT_FCTkeyboard int fct
(i.e. i8042_kbd_init())
VIDEO_TSTC_FCTtest char fct
(i.e. i8042_tstc)
VIDEO_GETC_FCTget char fct
(i.e. i8042_getc)
CONFIG_CONSOLE_CURSORcursor drawing on/off
(requires blink timer
cf. i8042.c)
CONFIG_SYS_CONSOLE_BLINK_COUNT blink interval (cf. i8042.c)
CONFIG_CONSOLE_TIMEdisplay time/date info in
upper right corner
(requires CONFIG_CMD_DATE)
CONFIG_VIDEO_LOGOdisplay Linux logo in
upper left corner
CONFIG_VIDEO_BMP_LOGOuse bmp_logo.h instead of
linux_logo.h for logo.
Requires CONFIG_VIDEO_LOGO
CONFIG_CONSOLE_EXTRA_INFO
additional board info beside
When CONFIG_CFB_CONSOLE is defined, video console is
default i/o. Serial console can be forced with
environment 'console=serial'.视频控制台默认的I
/ O的串行控制台可以强制环境控制台=串行”。
When CONFIG_SILENT_CONSOLE is defined, all console
messages (by U-Boot and Linux!) can be silenced with
the "silent" environment variable. See
doc/README.silent for more information.
- Console Baudrate:
CONFIG_BAUDRATE - in bps
Select one of the baudrates listed in
CONFIG_SYS_BAUDRATE_TABLE, see below.
CONFIG_SYS_BRGCLK_PRESCALE, baudrate prescale
- Console Rx buffer length
With CONFIG_SYS_SMC_RXBUFLEN it is possible to define
the maximum receive buffer length for the SMC.
This option is actual only for 82xx and 8xx possible.
If using CONFIG_SYS_SMC_RXBUFLEN also CONFIG_SYS_MAXIDLE
must be defined, to setup the maximum idle timeout for
- Boot Delay:CONFIG_BOOTDELAY - in seconds
Delay before automatically booti
set to -1 to disable autoboot.
See doc/README.autoboot for these options that
work with CONFIG_BOOTDELAY. None are required.
CONFIG_BOOT_RETRY_TIME
CONFIG_BOOT_RETRY_MIN
CONFIG_AUTOBOOT_KEYED
CONFIG_AUTOBOOT_PROMPT
CONFIG_AUTOBOOT_DELAY_STR
CONFIG_AUTOBOOT_STOP_STR
CONFIG_AUTOBOOT_DELAY_STR2
CONFIG_AUTOBOOT_STOP_STR2
CONFIG_ZERO_BOOTDELAY_CHECK
CONFIG_RESET_TO_RETRY
- Autoboot Command:
CONFIG_BOOTCOMMAND
Only needed when 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".
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.
- 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. 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.
- Kgdb Serial Baudrate: (if CONFIG_CMD_KGDB is defined)
CONFIG_KGDB_BAUDRATE
Select one of the baudrates listed in
CONFIG_SYS_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_BDI
CONFIG_CMD_BEDBUG* Include BedBug Debugger
CONFIG_CMD_BMP* BMP support
CONFIG_CMD_BSP* Board specific commands
CONFIG_CMD_BOOTD
CONFIG_CMD_CACHE* icache, dcache
CONFIG_CMD_CONSOLE
CONFIG_CMD_CRC32* crc32
CONFIG_CMD_DATE* support for RTC, date/time...
CONFIG_CMD_DHCP* DHCP support
CONFIG_CMD_DIAG* Diagnostics
CONFIG_CMD_DS4510* ds4510 I2C gpio commands
CONFIG_CMD_DS4510_INFO* ds4510 I2C info command
CONFIG_CMD_DS4510_MEM* ds4510 I2C eeprom/sram commansd
CONFIG_CMD_DS4510_RST* ds4510 I2C rst command
CONFIG_CMD_DTT* Digital Therm and Thermostat
CONFIG_CMD_ECHO
echo arguments
CONFIG_CMD_EDITENV
edit env variable
CONFIG_CMD_EEPROM* EEPROM read/write support
CONFIG_CMD_ELF* bootelf, bootvx
CONFIG_CMD_EXPORTENV* export the environment
CONFIG_CMD_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_GO* the 'go' command (exec code)
CONFIG_CMD_GREPENV* search environment
CONFIG_CMD_HWFLOW* RTS/CTS hw flow control
CONFIG_CMD_I2C* I2C serial bus support
CONFIG_CMD_IDE* IDE harddisk support
CONFIG_CMD_IMI
CONFIG_CMD_IMLS
List all found images
CONFIG_CMD_IMMAP* IMMR dump support
CONFIG_CMD_IMPORTENV* import an environment
CONFIG_CMD_IRQ* irqinfo
CONFIG_CMD_ITEST
Integer/string test of 2 values
CONFIG_CMD_JFFS2* JFFS2 Support
CONFIG_CMD_KGDB* kgdb
CONFIG_CMD_LDRINFO
ldrinfo (display Blackfin loader)
CONFIG_CMD_LOADB
CONFIG_CMD_LOADS
CONFIG_CMD_MD5SUM
print md5 message digest
(requires CONFIG_CMD_MEMORY and CONFIG_MD5)
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_MTDPARTS* MTD partition support
CONFIG_CMD_NAND* NAND support
CONFIG_CMD_NET
bootp, tftpboot, rarpboot
CONFIG_CMD_PCA953X* PCA953x I2C gpio commands
CONFIG_CMD_PCA953X_INFO* PCA953x I2C gpio info command
CONFIG_CMD_PCI* pciinfo
CONFIG_CMD_PCMCIA* PCMCIA support
CONFIG_CMD_PING* send ICMP ECHO_REQUEST to network
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_SHA1SUM
print sha1 memory digest
(requires CONFIG_CMD_MEMORY)
CONFIG_CMD_SOURCE
"source" command Support
CONFIG_CMD_SPI* SPI serial bus support
CONFIG_CMD_TFTPSRV* TFTP transfer in server mode
CONFIG_CMD_USB* USB support
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 for the SoC. There must be support in the SoC
specific code for a watchdog. For the 8xx and 8260
CPUs, the SIU Watchdog feature is enabled in the SYPCR
When supported for a specific SoC is
available, then no further board specific code should
be needed to use it.
CONFIG_HW_WATCHDOG
When using a watchdog circuitry external to the used
SoC, then define this variable and provide board
specific code for the "hw_watchdog_reset" function.
- U-Boot Version:
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.
- 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_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
CONFIG_SYS_RTC_DS1337_NOOSC- Turn off the OSC output for DS1337
CONFIG_SYS_RV3029_TCR- enable trickle charger on
RV3029 RTC.
Note that if the RTC uses I2C, then the I2C interface
must also be configured. See I2C Support, below.
- GPIO Support:
CONFIG_PCA953X- use NXP's PCA953X series I2C GPIO
CONFIG_PCA953X_INFO- enable pca953x info command
The CONFIG_SYS_I2C_PCA953X_WIDTH option specifies a list of
chip-ngpio pairs that tell the PCA953X driver the number of
pins supported by a particular chip.
Note that if the GPIO device uses I2C, then the I2C interface
must also be configured. See I2C Support, below.
- 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 .
- Partition Support:
CONFIG_MAC_PARTITION and/or CONFIG_DOS_PARTITION
and/or CONFIG_ISO_PARTITION and/or CONFIG_EFI_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:
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 CONFIG_SYS_64BIT_LBA.
Whithout these , LBA48 support uses 32bit variables and will 'only'
support disks up to 2.1TB.
CONFIG_SYS_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 define
CONFIG_SCSI_SYM53C8XX to enable it.
CONFIG_SYS_SCSI_MAX_LUN [8], CONFIG_SYS_SCSI_MAX_SCSI_ID [7] and
CONFIG_SYS_SCSI_MAX_DEVICE [CONFIG_SYS_SCSI_MAX_SCSI_ID *
CONFIG_SYS_SCSI_MAX_LUN] can be adjusted to define the
maximum numbers of LUNs, SCSI ID's and target
CONFIG_SYS_SCSI_SYM53C8XX_CCF to fix clock timing (80Mhz)
- NETWORK Support (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 /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_AT91EMAC
Support for AT91RM9200 EMAC.
CONFIG_RMII
Define this to use reduced MII inteface
CONFIG_DRIVER_AT91EMAC_QUIET
If this defined, the driver is quiet.
The driver doen't show link status messages.
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_FTGMAC100
Support for Faraday's FTGMAC100 Gigabit SoC Ethernet
CONFIG_FTGMAC100_EGIGA
Define this to use GE link update with gigabit PHY.
Define this if FTGMAC100 is connected to gigabit PHY.
If your system has 10/100 PHY only, it might not occur
wrong behavior. Because PHY usually return timeout or
useless data when polling gigabit status and gigabit
control registers. This behavior won't affect the
correctnessof 10/100 link speed update.
CONFIG_SMC911X
Support for SMSC's LAN911x and LAN921x chips
CONFIG_SMC911X_BASE
Define this to hold the physical address
of the device (I/O space)
CONFIG_SMC911X_32_BIT
Define this if data bus is 32 bits
CONFIG_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_SMC911X_32_BIT.
CONFIG_SH_ETHER
Support for Renesas on-chip Ethernet controller
CONFIG_SH_ETHER_USE_PORT
Define the number of ports to be used
CONFIG_SH_ETHER_PHY_ADDR
Define the ETH PHY's address
CONFIG_SH_ETHER_CACHE_WRITEBACK
If this option is set, the driver enables cache flush.
- USB Support:
At the moment only the UHCI host controller is
supported (PIP405, MIP405, MPC5200); define
CONFIG_USB_UHCI to enable it.
define CONFIG_USB_KEYBOARD to enable the USB Keyboard
and define CONFIG_USB_STORAGE to enable the USB
storage devices.
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_PSC3_USB
for USB on PSC3
CONFIG_USB_CONFIG
for differential drivers: 0x
for single ended drivers: 0x
for differential drivers on PSC3: 0x
for single ended drivers on PSC3: 0x
CONFIG_SYS_USB_EVENT_POLL
May be defined to allow interrupt polling
instead of using asynchronous interrupts
- USB Device:
Define the below if you wish to use the USB console.
Once firmware is rebuilt from a serial console issue the
command " 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
CONFIG_USB_TTY
Define this to have a tty type of device available to
talk to the UDC device
CONFIG_SYS_CONSOLE_IS_IN_ENV
Define this if you want stdin, stdout &/or stderr to
be set to usbtty.
CONFIG_SYS_USB_EXTC_CLK 0xBLAH
Derive USB clock from external clock "blah"
- CONFIG_SYS_USB_EXTC_CLK 0x02
CONFIG_SYS_USB_BRG_CLK 0xBLAH
Derive USB clock from brgclk
- CONFIG_SYS_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
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:
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.
CONFIG_SH_MMCIF
Support for Renesas on-chip MMCIF controller
CONFIG_SH_MMCIF_ADDR
Define the base address of MMCIF registers
CONFIG_SH_MMCIF_CLK
Define the clock frequency for MMCIF
- Journaling Flash filesystem support:
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
CONFIG_SYS_JFFS2_FIRST_SECTOR,
CONFIG_SYS_JFFS2_FIRST_BANK, CONFIG_SYS_JFFS2_NUM_BANKS
Define these for a default partition on a NOR device
CONFIG_SYS_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)
If you define only one JFFS2 partition you may also want to
#define CONFIG_SYS_JFFS_SINGLE_PART1
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
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
CONFIG_VIDEO_CT69000
Enable Chips & Technologies 69000 Video chip
CONFIG_VIDEO_SMI_LYNXEM
Enable Silicon Motion SMI 712/710/810 Video chip. The
video output is selected via environment 'videoout'
(1 = LCD and 2 = CRT). If videoout is undefined, CRT is
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.
Following standard modes are supported(* is default):
Colors640x480 800x600 2x864
-------------+---------------------------------------------
8 bits |0x301*
0x303 0x305
15 bits |0x310
0x313 0x316
16 bits |0x311
0x314 0x317
24 bits |0x312
0x315 0x318
-------------+---------------------------------------------
(i.e. setenv videomode 317;)
- "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
CONFIG_FSL_DIU_FB
Enable the Freescale DIU video driver.Reference boards for
SOCs that have a DIU should define this macro to enable DIU
support, and should also define these other macros:
CONFIG_SYS_DIU_ADDR
CONFIG_VIDEO
CONFIG_CMD_BMP
CONFIG_CFB_CONSOLE
CONFIG_VIDEO_SW_CURSOR
CONFIG_VGA_AS_SINGLE_DEVICE
CONFIG_VIDEO_LOGO
CONFIG_VIDEO_BMP_LOGO
The DIU driver will look for the 'video-mode' environment
variable, and if defined, enable the DIU as a console during
See the documentation file README.video for a
description of this variable.
- 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: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:
CONFIG_ATMEL_LCD:
HITACHI TX09D70VM1CCA, 3.5", 240x320.
CONFIG_NEC_NL6448AC33:
NEC NL. Active, color, single scan.
CONFIG_NEC_NL6448BC20
NEC NL. 6.5", 640x480.
Active, color, single scan.
CONFIG_NEC_NL
NEC NL. 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 define
CONFIG_SYS_WHITE_ON_BLACK to get it inverted.
- 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.
CONFIG_SPLASH_SCREEN_ALIGN
If this option is set the splash image can be freely positioned
on the screen. Environment variable "splashpos" specifies the
position as "x,y". If a positive number is given it is used as
number of pixel from left/top. If a negative number is given it
is used as number of pixel from right/bottom. You can also
specify 'm' for centering the image.
setenv splashpos m,m
=& image at center of screen
setenv splashpos 30,20
=& image at x = 30 and y = 20
setenv splashpos -10,m
=& vertically centered image
at x = dspWidth - bmpWidth - 9
- Gzip compressed BMP image support: 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.
- Run length encoded BMP image (RLE8) support: CONFIG_VIDEO_BMP_RLE8
If this option is set, 8-bit RLE compressed 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.
NOTE: the bzip2 algorithm requires a lot of RAM, so
the malloc area (as defined by CONFIG_SYS_MALLOC_LEN) should
be at least 4MB.
CONFIG_LZMA
If this option is set, support for lzma compressed
images is included.
Note: The LZMA algorithm adds between 2 and 4KB of code and it
requires an amount of dynamic memory that is given by the
(1846 + 768 && (lc + lp)) * sizeof(uint16)
Where lc and lp stand for, respectively, Literal context bits
and Literal pos bits.
This value is upper-bounded by 14MB in the worst case. Anyway,
for a ~4MB large kernel image, we have lc=3 and lp=0 for a
total amount of (1846 + 768 && (3 + 0)) * 2 = ~41KB... that is
a very small buffer.
Use the lzmainfo tool to determinate the lc and lp values and
then calculate the amount of needed dynamic memory (ensuring
the appropriate CONFIG_SYS_MALLOC_LEN value).
- 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)
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_ETH1ADDR
CONFIG_ETH2ADDR
CONFIG_ETH3ADDR
CONFIG_ETH4ADDR
CONFIG_ETH5ADDR
Define a default value for Ethernet address to use
for the respective Ethernet interface, in case this
is not determined automatically.
- IP address:
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:
CONFIG_SERVERIP
Defines a default value for the IP address of a TFTP
server to contact when using the "tftboot" command.
CONFIG_KEEP_SERVERADDR
Keeps the server's MAC address, in the env 'serveraddr'
for passing to bootargs (like Linux's netconsole option)
- Multicast TFTP Mode:
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.
- 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. 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:
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.
- 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
0x 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: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: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: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.
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_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 CONFIG_SYS_I2C_SPEED
to be the frequency (in Hz) at which you wish your i2c bus
to run and CONFIG_SYS_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
(arch/powerpc/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
CONFIG_SYS_I2C_SLAVE to 0.
CONFIG_SYS_I2C_INIT_MPC5XXX
When a board is reset during an i2c bus transfer
chips might think that the current transfer is still
in progress.
Reset the slave devices by sending start
commands until the slave device responds.
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):
(Optional). Any commands necessary to enable the I2C
controller or configure ports.
eg: #define I2C_INIT (immr-&im_cpm.cp_pbdir |=PB_SCL)
(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
If the data line is open collector, this
define can be null.
eg: #define I2C_ACTIVE (immr-&im_cpm.cp_pbdir |=
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)
Code that returns TRUE if the I2C data line is high,
FALSE if it is low.
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).
eg: #define I2C_SDA(bit) \
if(bit) immr-&im_cpm.cp_pbdat |=
elseimmr-&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).
eg: #define I2C_SCL(bit) \
if(bit) immr-&im_cpm.cp_pbdat |=
elseimmr-&im_cpm.cp_pbdat &= ~PB_SCL
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
#define I2C_DELAY
CONFIG_SOFT_I2C_GPIO_SCL / CONFIG_SOFT_I2C_GPIO_SDA
If your arch supports the generic GPIO framework (asm/gpio.h),
then you may alternatively define the two GPIOs that are to be
used as SCL / SDA.
Any of the previous I2C_xxx macros will
have GPIO-based defaults assigned to them as appropriate.
You should define these to the GPIO value as given directly to
the generic GPIO functions.
CONFIG_SYS_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_SYS_I2C_BOARD_LATE_INIT
An alternative to CONFIG_SYS_I2C_INIT_BOARD. If this option is
defined a custom i2c_board_late_init() routine in
boards/xxx/board.c is run AFTER the operations in i2c_init()
is completed. This callpoint can be used to unreset i2c bus
using CPU i2c controller register accesses for CPUs whose i2c
controller provide such a method. It is called at the end of
i2c_init() to allow i2c_init operations to setup the i2c bus
controller on the CPU (e.g. setting bus speed & slave address).
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
To switch to a different bus, use the 'i2c dev' command.
Note that bus numbering is zero-based.
CONFIG_SYS_I2C_NOPROBES
This option specifies a list of I2C devices that will be skipped
when the 'i2c probe' command is issued.
If CONFIG_I2C_MULTI_BUS
is set, specify a list of bus-device pairs.
Otherwise, specify
a 1D array of device addresses
#undefCONFIG_I2C_MULTI_BUS
#define CONFIG_SYS_I2C_NOPROBES{0x50,0x68}
will skip addresses 0x50 and 0x68 on a board with one I2C bus
#defineCONFIG_I2C_MULTI_BUS
#define CONFIG_SYS_I2C_MULTI_NOPROBES{{0,0x50},{0,0x68},{1,0x54}}
will skip addresses 0x50 and 0x68 on bus 0 and address 0x54 on bus 1
CONFIG_SYS_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.
CONFIG_SYS_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.
CONFIG_SYS_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_SYS_I2C_DTT_ADDR:
If defined, specifies the I2C address of the DTT device.
If not defined, then U-Boot uses predefined value for
specified DTT device.
CONFIG_FSL_I2C
Define this option if you want to use Freescale's I2C driver in
drivers/i2c/fsl_i2c.c.
CONFIG_I2C_MUX
Define this option if you have I2C devices reached over 1 .. n
I2C Muxes like the pca9544a. This option addes a new I2C
Command "i2c bus [muxtype:muxaddr:muxchannel]" which adds a
new I2C Bus to the existing I2C Busses. If you select the
new Bus with "i2c dev", u-bbot sends first the commandos for
the muxes to activate this new "bus".
CONFIG_I2C_MULTI_BUS must be also defined, to use this
Adding a new I2C Bus reached over 2 pca9544a muxes
The First mux with address 70 and channel 6
The Second mux with address 71 and channel 4
=& i2c bus pca:pca
Use the "i2c bus" command without parameter, to get a list
of I2C Busses with muxes:
=& i2c bus
Busses reached over muxes:
reached over Mux(es):
pca9544a@70 ch: 4
reached over Mux(es):
pca9544a@70 ch: 6
pca9544a@71 ch: 4
If you now switch to the new I2C Bus 3 with "i2c dev 3"
u-boot first sends the command to the mux@70 to enable
channel 6, and then the command to the mux@71 to enable
the channel 4.
After that, you can use the "normal" i2c commands as
usual to communicate with your I2C devices behind
the 2 muxes.
This option is actually implemented for the bitbanging
algorithm in common/soft_i2c.c and for the Hardware I2C
Bus on the MPC8260. But it should be not so difficult
to add this option to other architectures.
CONFIG_SOFT_I2C_READ_REPEATED_START
defining this will force the i2c_read() function in
the soft_i2c driver to perform an I2C repeated start
between writing the address pointer and reading the
If this define is omitted the default behaviour
of doing a stop-start sequence will be used.
devices can use either method, but some require one or
the other.
- SPI Support: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_SH_SPI
Enables the driver for SPI controller on SuperH. Currently
only SH7757 is supported.
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.
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.
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: 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.
CONFIG_SYS_FPGA_PROG_FEEDBACK
Enable printing of hash marks during FPGA configuration.
CONFIG_SYS_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.
CONFIG_SYS_FPGA_CHECK_CTRLC
Allow Control-C to interrupt FPGA configuration
CONFIG_SYS_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).
CONFIG_SYS_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
CONFIG_SYS_FPGA_WAIT_BUSY
Maximum time to wait for BUSY to deassert during
Virtex II FPGA configuration. The default is 5 ms.
CONFIG_SYS_FPGA_WAIT_CONFIG
Time to wait after FPGA configuration. The default is
- Configuration Management:
CONFIG_IDENT_STRING
If defined, this string will be added to the U-Boot
version information (U_BOOT_VERSION)
- 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. 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.
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:
CONFIG_PRAM
Define this variable to enable the reservation of
"protected RAM", i. e. RAM which is not overwritten
by U-Boot. Define CONFIG_PRAM to hold the number of
kB you want to reserve for pRAM. 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}
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. So far, the
following board configurations are known to be
"pRAM-clean":
ETX094, IVMS8, IVML24, SPD8xx, TQM8xxL,
HERMES, IP860, RPXlite, LWMON, LANTEC,
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.
CONFIG_ARP_TIMEOUT
Timeout waiting for an ARP reply in milliseconds.
- Command Interpreter:
CONFIG_AUTO_COMPLETE
Enable auto completion of commands using TAB.
Note that this feature has NOT been implemented yet
for the "hush" shell.
CONFIG_SYS_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.
CONFIG_SYS_PROMPT_HUSH_PS2
This defines the secondary prompt string, which is
printed when the command interpreter needs more input
to complete a command. Usually "& ".
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.
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.
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
- 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 "source" command or the
boot command first.
- DataFlash Support:
CONFIG_HAS_DATAFLASH
Defining this option enables DataFlash features and
allows to read/write in Dataflash via the standard
commands 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
CONFIG_SYS_SYSTEMACE_BASE macro. For example:
#define CONFIG_SYSTEMACE
#define CONFIG_SYS_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:
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.
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.
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:
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:
- Standalone program support:
CONFIG_STANDALONE_LOAD_ADDR
This option allows to define board specific values
for the address where standalone program gets loaded,
thus overwriting the architecutre dependent default
- Frame Buffer Address:
CONFIG_FB_ADDR
Define CONFIG_FB_ADDR if you want to use specific address for
frame buffer.
Then system will reserve the frame buffer address to defined address
instead of lcd_setmem (this function grab the memory for frame buffer
by panel's size).
Please see board_init_f function.
If you want this config option then,
please define it at your board config file
遗留的uImage格式：
1common/cmd_bootm.c
before attempting to boot an image
-1common/cmd_bootm.c
Image header has bad magic number
2common/cmd_bootm.c
Image header has correct magic number
-2common/cmd_bootm.c
Image header has bad checksum
3common/cmd_bootm.c
Image header has correct checksum
-3common/cmd_bootm.c
Image data
has bad checksum
4common/cmd_bootm.c
Image data
has correct checksum
-4common/cmd_bootm.c
Image is for unsupported architecture
5common/cmd_bootm.c
Architecture check OK
-5common/cmd_bootm.c
Wrong Image Type (not kernel, multi)
6common/cmd_bootm.c
Image Type check OK
-6common/cmd_bootm.c
gunzip uncompression error
-7common/cmd_bootm.c
Unimplemented compression type
7common/cmd_bootm.c
Uncompression OK
8common/cmd_bootm.c
No uncompress/copy overwrite error
-9common/cmd_bootm.c
Unsupported OS (not Linux, BSD, VxWorks, QNX)
9common/image.c
Start initial ramdisk verification
-10common/image.c
Ramdisk header has bad
magic number
-11common/image.c
Ramdisk header has bad
10common/image.c
Ramdisk header is OK
-12common/image.c
Ramdisk data
11common/image.c
Ramdisk data
has correct checksum
12common/image.c
Ramdisk verification complete, start loading
-13common/image.c
Wrong Image Type (not PPC Linux ramdisk)
13common/image.c
Start multifile image verification
14common/image.c
No initial ramdisk, no multifile, continue.
15arch/&arch&/lib/bootm.c
All preparation done, transferring control to OS
-30arch/powerpc/lib/board.c
Fatal error, hang the system
-31post/post.c
POST test failed, detected by post_output_backlog()
-32post/post.c
POST test failed, detected by post_run_single()
34common/cmd_doc.c
before loading a Image from a DOC device
-35common/cmd_doc.c
Bad usage of "doc" command
35common/cmd_doc.c
correct usage of "doc" command
-36common/cmd_doc.c
No boot device
36common/cmd_doc.c
correct boot device
-37common/cmd_doc.c
Unknown Chip ID on boot device
37common/cmd_doc.c
correct chip ID found, device available
-38common/cmd_doc.c
Read Error on boot device
38common/cmd_doc.c
reading Image header from DOC device OK
-39common/cmd_doc.c
Image header has bad magic number
39common/cmd_doc.c
Image header has correct magic number
-40common/cmd_doc.c
Error readi