Getting Started with eCosTM
Prev | Chapter 2. Overview of the release | Next

# ROM monitor image

eCos ships with a CygMon ROM monitor for the MN10300, TX39, and SPARClite evaluation boards. This includes a GDB stub, thus allowing GDB to be used to debug eCos applications on these evaluation boards. In addition to shipping the actual ROM, the image of that ROM is provided in case you need to burn identical copies for additional boards (see Chapter 10).

> Note: The TCP stack in the SPARClite version of CygMon uses timer1 of the 86940 as a freerunning millisecond counter. This means timer1 cannot be used by the application.

For the PowerPC Cogent and ARM7 PID boards, the ROM images include a GDB stub. This allows GDB to connect to the board and download eCos programs. For the ARM7 AEB-1 board, the ROM image includes a GDB stub that can be installed in the FLASH ROM on the board. See the file `hal/arm/aeb/v1_2_1/misc/Notes` for details of the downloading procedure.

> Note: When an eCos program is run on the PowerPC board, the GDB stub in ROM loses control. This means that if you require debugging capabilities, you must include GDB stub support when configuring eCos.

No ROM image is required for the synthetic Linux target.

The source code to CygMon is included as part of the GNUPro package, so that you may recompile it as described in the GNUPro documentation.

Please note that previous releases of CygMon are incompatible with eCos. You must use the version of CygMon that is provided with eCos rather than an older version of CygMon.

Prev | Home | Next
Using the simulator | Up | Tests and examples