readme

Intel XScale PXA255 引导Linux的Redboot 版bootloader源代码！

README for eCos directory <PACKAGES>hal/arm/sa2sim/<VERSION>/simcfg


Configuration files for Coyanosa AKA StrongARM 2 simulator - eCos version.

This directory contains files that the simulator uses to control both the
hardware configuration that is to be simulated, and various actions to take
outside the simulated world in consequence of events within the simulation.

These files are based on those provided by Intel for use with the
simulator, with some minor changes to assist in eCos testing and
debuggability.

-rw-rw----   1 hmt          mmmm Feb 18 18:08 README
-rw-r-----   1 hmt          1126 Feb 18 17:25 conf.hdl
-rw-r-----   1 hmt           953 Feb 18 17:25 bangirq.pil
-rw-r-----   1 hmt          4209 Feb 18 17:25 cpu.pil

conf.hdl is unmodified - it connects the CPU to memory, and clocks to each
and instantiates other pulse sources for driving interrupts.

bangirq.pil controls a "banger" - something which bangs an interrupts
periodically.  This is used to cause periodic interrupts on the external
IRQ line (nIRQ) to provide eCos' real time clock.  It also controls logging
information from the IRQ banger - recording cycle count information for
each IRQ event in bangirq.log when the simulator is running.

cpu.pil controls the cpu initialization and logging information.  It is
extended to provided specific log information (in cpu.log) about events
such as IRQs and SWIs, and to halt the simulation if an ABORT or UNDEF
instruction trap occurs.


The simulator is invoked by

(Solaris/SH)
	MEMFILES="<PATH>/lilmon.elf <PATH2>/<TESTCASE>"
        export MEMFILES
	coysimsun conf.hdl 0

(Solaris/CSH)
	setenv MEMFILES "<PATH>/lilmon.elf <PATH2>/<TESTCASE>"
	coysimsun conf.hdl 0

(NT)
	set MEMFILES="<PATH>\lilmon.elf <PATH2>\<TESTCASE>"
	coysim conf.hdl 0

In each case, the control files conf.hdl bangirq.pil cpu.pil should be in
the directory where the simulator is invoked, and the logfiles will be
created in that same directory.

lilmon.elf has the same role as a "boot ROM" in starting the system - it is
loaded into memory from address zero, and jumps to address 0x8000, the
start of the linked RAM startup eCos application.  Both must be provided in
the variable MEMFILES.

The application diagnostic text output appears on the simulator's output.


For information on modifying lilmon.elf, see the README in neighbouring
directory "lilmon" where its sources and build instructions live, together
with an example lilmon.elf prebuilt.