eCosPro® Reference Manual
Prev |  | Next

# JTAG debugging support

## Name

JTAG support -- Usage

## Use of JTAG for debugging

JTAG can be used to single-step and debug loaded applications, including RedBoot. Only ROM configuration applications should be debugged using JTAG, RAM applications assume the presence of RedBoot.

### Ronetix PEEDI notes

On the Ronetix PEEDI, the `peedi.at91sam9261ek.cfg` file should be used to setup and configure the hardware to an appropriate state to load programs. This includes setting up the SDRAM controller.

The `peedi.at91sam9261ek.cfg` file also contains an option to define whether hardware or software breakpoints are used by default, using the CORE0_BREAKMODE directive in the [PLATFORM_ARM] section. Edit this file if you wish to use hardware break points, and remember to restart the PEEDI to make the changes take effect.

On the PEEDI, debugging can be performed either via the telnet interface or using arm-eabi-gdb and the GDB interface. In the case of the latter, arm-eabi-gdb needs to connect to TCP port 2000 on the PEEDI's IP address. For example:

    (gdb) target remote 111.222.333.444:2000

By default when the PEEDI is powered up, the target will always run the initialization section of the `peedi.at91sam9261ek.cfg` file (which configures the SDRAM among other things), and halts the target. This behavior is repeated with the reset command.

If the board is reset (either with the 'reset', or by pressing the reset button) and the 'go' command is then given, then the board will boot as normal. If a second-level bootstrap and ROM RedBoot is resident in DataFlash, it will be run.

Consult the PEEDI documentation for information on other features.

### Running ROM applications

Applications configured for ROM startup can be run directly under JTAG. Once loaded and running via JTAG, HAL diagnostic output will appear by default on the serial debug port.

Prev | Home | Next
Configuration | Up | The HAL Port