ARM Linux - Developer FoxICE For ARM仿真器

高速程序代码下载速度200KBytes/S以上、内置对于GDB Remote Serial Protocol协议支持、FoxICE仿真器完美支持GDB 的 File IO扩展协议、免费赠送Eclipse for ARM V 3.2.1集成开发环境、支持Nand Flash( S3C2410或 S3C2440可任选一种 )的烧写，支持超低电压的处理器调试, 目标范围为：0.65 ～ 5.5V
详细信息 >>

In order to boot ARM Linux, you require a boot loader, which is a small program that runs before the main kernel. The boot loader is expected to initialise various devices, and eventually call the Linux kernel, passing information to the kernel.
Essentially, the boot loader should provide (as a minimum) the following:

Setup and initialise the RAM.
Initialise one serial port.
Detect the machine type.
Setup the kernel tagged list.
Call the kernel image.

Setup and initialise RAM
Existing boot loaders: MANDATORY
New boot loaders: MANDATORY

The boot loader is expected to find and initialise all RAM that the kernel will use for volatile data storage in the system. It performs this in a machine dependent manner. (It may use internal algorithms to automatically locate and size all RAM, or it may use knowledge of the RAM in the machine, or any
other method the boot loader designer sees fit.)
Initialise one serial port
Existing boot loaders: OPTIONAL, RECOMMENDED
New boot loaders: OPTIONAL, RECOMMENDED

The boot loader should initialise and enable one serial port on the target. This allows the kernel serial driver to automatically detect which serial port it should use for the kernel console (generally used for debugging purposes, or communication with the target.)

As an alternative, the boot loader can pass the relevant 'console=' option to the kernel via the tagged lists specifing the port, and serial format options as described in linux/Documentation/kernel-parameters.txt.
Detect the machine type
Existing boot loaders: OPTIONAL
New boot loaders: MANDATORY

The boot loader should detect the machine type its running on by some method. Whether this is a hard coded value or some algorithm that looks at the connected hardware is beyond the scope of this document. The boot loader must ultimately be able to provide a MACH_TYPE_xxx value to the kernel. (see linux/arch/arm/tools/mach-types).