A target interface is a mechanism for communicating with and controlling a target. A target maybe be a physical hardware device or a simulator.
CrossStudio has a targets window for viewing and manipulating target interfaces. For more information on the targets window, see Targets Window.
Before a target interface can be used, it must be connected. CrossStudio permits connection to only one target at a time. For more information on connecting to target interfaces, see Connecting to a target.
All target interfaces have a set of properties. The properties provide information on the connected target and allow the target interface to be configured. For more information on viewing and editing target properties, see Viewing and editing target properties.
CrossWorks supports a number of different ARM debug interfaces, each target interface can support one or more of these. The following table summarises the supported target interfaces and the ARM debug interfaces supported:
Target Interface | ARM7DI | ARM7TDI | ARM9TDI | XScale | ADIv5 |
CrossConnect for ARM | Yes | Yes | Yes | Yes | Yes |
Amontec JTAGkey | Yes | Yes | Yes | Yes | Yes |
Generic FT2232 Device | Yes | Yes | Yes | Yes | Yes |
Macraigor System's Wiggler for ARM | Yes | Yes | Yes | Yes | Yes |
Olimex ARM-USB-OCD | Yes | Yes | Yes | Yes | Yes |
Segger J-Link | Yes | Yes | Yes | No | No |
CrossStudio ARM Simulator | Yes | Yes | Yes | Yes | Yes |
The following table summarises the debug facilities available to each ARM debug interface:
ARM Debug Architecture | Software Breakpoints | Hardware Breakpoints | Break on Exception |
ARM7DI | Unlimited (1 hardware breakpoint used) | 2 | No |
ARM7TDI | Unlimited (1 hardware breakpoint used) | 2 | No |
ARM9TDI | Unlimited (1 hardware breakpoint used) | 2 | Yes |
XScale | Unlimited | 4 (2 instruction and 2 data) | Yes |
ADIv5 | Unlimited | 10 (6 instruction and 4 data) | Yes |