A target interface is a mechanism for communicating with, and controlling, a target. A target can be either a physical hardware device or a software simulation of a device. CrossStudio has a Targets window for viewing and manipulating target interfaces. For more information, see Targets window.
Before you can use a target interface, you must connect to it. You can only connect to one target interface at a time. For more information, 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, see Viewing and editing target properties.
| Target Interface | ARM7 | ARM9 | ARM11 | XScale | Cortex-M (JTAG) | Cortex-M (SWD) | Cortex-A/R |
| CrossConnect for ARM | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Generic ARM Debug Interface | Yes | Yes | Yes | No | Yes | Yes | Yes |
| Generic FT2232 Device | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Macraigor Systems's Wiggler for ARM | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Segger J-Link | Yes | Yes | No | No | Yes | Yes | Yes |
| CrossStudio ARM Simulator | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| ST-Link | No | No | No | No | Yes | Yes | No |
| ST-Link/V2 | No | No | No | No | Yes | Yes | No |
| PandE UNIT Interface DLL | No | No | No | No | Yes | No | No |
| Kinetis OSJTAG | No | No | No | No | Yes | No | No |
| Stellaris ICDI | No | No | No | No | Yes | No | No |
| CMSIS-DAP | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
Note that the Amontec JTAGkey and Olimex ARM-USB-OCD are FT2232-based devices.
See Debug Capabilities for details about the debug support CrossWorks provides for the various devices.
Note that the Segger J-Link, ST-Link, and PandE UNIT Interface DLL target interfaces require other files that are supplied by the vendor of the target interface.
The Segger J-Link target interface's J-Link DLL File property should point at the file JLinkARM.dll on Windows and to JLinkARM.so on Linux. Go to http://www.segger.com/cms/jlink-software.html for the latest downloads.
The ST-Link's ST-LINK DLL File property should point at the file STLinkUSBDriver.dll that is supplied in the ST-Link Utility, found here:
http://www.st.com/internet/com/SOFTWARE_RESOURCES/TOOL/DEVICE_PROGRAMMER/um0892.zip
The PandE UNIT Interface DLL's File Path property should point to the file unit_ngs_arm.dll. Contact Rowley Associates for the latest information on where to find this.
Do not copy the above files into the CrossWorks distribution—just reference the files where they have been installed.