Debug software for DSTREAM-PT
The development software on your host PC provides the interface between your debugger and the DSTREAM-PT hardware that controls the target devices. The host software translates debugger commands, such as
download, into control sequences for a particular processor.
Depending on your needs, there are several options:
- Arm Development Studio
Arm® Development Studio is a suite of tools for embedded C/C++ software development on any Arm-based device. It features an editor, compilers, debugger, and a system profiler. Combined with DSTREAM-PT, you get a comprehensive solution for developing and debugging complex systems.
For more information on debugging using Arm Development Studio, see the documentation.
You can download the latest version of Arm Development Studio from the Arm Development Studio downloads page.
- Remote Device Debug Interface (RDDI)
Third-party debuggers, both for Arm and other processors, can connect to DSTREAM-PT using the RDDI interface.
You can use the RDDI interface to:
- Address each target device individually, without affecting other devices on the board. It uses this ability to create virtual connections for each of the JTAG devices on the board. Your debugger can attach to one of these virtual connections, and perform debugging operations with no knowledge of the other devices on the board.
- Enable multiple concurrent connections to debug multiprocessor systems. Depending on the system, you can also perform a synchronized start or stop of processors for debugging multiprocessor systems where the processors interact with each other.
- Perform simple tasks. For example, for production testing, a low-level RDDI connection to DSTREAM-PT can be used to gain access to the JTAG scan-chains inside the target device.
RDDI is freely available from within the Arm Development Studio installation. It is located
<install_directory>/Arm/Development Studio <version>/sw/debugger/RDDI.
- CoreSight Access Tool (CSAT)
The CoreSight™ Access Tool (CSAT) provides a scriptable low-level interface to the CoreSight Debug Access Port (DAP) on a target. CSAT is useful to perform initial bring-up tests before a debugger connection to the target is available.
CSAT provides low-level, command-line manipulation of devices connected to a DAP, for example, custom instrumentation hardware, at the memory or register level. CSAT removes the complexity, complication, or overhead of a debugger. CSAT can be used while a debugger is connected to an Arm processor. This enables the debugging of complex hardware-related problems.
For more information, see the CoreSight Access Tool (CSAT) User Guide. In your Arm Development Studio installation, CSAT is located in
<install_directory>/Arm/Development Studio <version>/bin/csat.exe.