CoreSight Access Tool for SoC600 (CSAT600) provides access to Arm Debug Interface Architecture Specification ADIv6.0 or CoreSight SoC-600 targets. The CSAT600 tool is used to interact with CoreSight SoC-600 targets at a CoreSight architecture level. This level of interaction is useful when trying to debug target behavior at a low debug architectural level.
This user guide provides information on how to use the CSAT600 tool, and how the CSAT600 tool commands compare to the commands in the original CSAT tool. The guide also explains what CSAT600 tool commands are available and how to use them, and provides examples demonstrating common CSAT600 tool use cases.
Before you begin
To use the CSAT600 tool, you need:
- Arm Development Studio 2019.0 or later
- A working knowledge of the Arm Debug Interface Architecture Specification ADIv6.0
- A CoreSight SoC-600 target
The CSAT600 tool differs from the original CoreSight Access Tool (CSAT). This is because CSAT only works with Arm Debug Interface Architecture Specification ADIv5.2 or earlier CoreSight targets. Wherever possible, the command syntax of the CSAT600 tool mimics the command syntax of CSAT.
Using the CSAT600 tool to access memory on a CoreSight SoC-600 target is easiest when the tool is connected to a target using a DSTREAM family debug probe. You can also use other methods of target connection, for example, ULINKpro.
Note: Register access in the CSAT tool is currently performed using manual memory accesses. Please contact Arm Support for future enhancements and upcoming features.
How to use CSAT600
The CSAT600 tool is only available in Arm Development Studio 2019.0 or later.
To use the CSAT600 tool:
- Open a command prompt to <Arm Development Studio installation directory>\bin
You should see the following output in the command prompt:
** Welcome to CSAT for SoC600 **
Note: To run the original CSAT tool, run
csat in an Arm Development Studio bin directory command prompt.
CSAT600 command list
For Arm Development Studio 2019.0, the following commands listed on this page are available for the CSAT600 tool. Additional commands will be available in future Arm Development Studio releases. You should be aware that:
- Most commands have a command alias that is used to execute the same operation. Any command aliases are in () beside the full command name.
- In the command's Example section, "..." denotes that executing the command provides further output. The further output is not shown in this user guide.
Command comparison between CSAT600 and CSAT
CSAT600 and CSAT use the same command names and formats where possible. The following table shows the command differences between CSAT600 and CSAT.
<device no> used in CSAT600 has the same meaning as
<devid> used in CSAT.
||CSAT600 does not allow the
|| CSAT600 does not allow connecting to USB using the serial number of a debug probe. CSAT does not allow specifying a
|| CSAT does not allow using the
|| CSAT does not allow using the
||CSAT lists the available trace functions. CSAT does not have an equivalent help command that lists all functions available. CSAT600 prints a list of all available commands.
Worked examples for CSAT600
Here are some examples of using CSAT600 to perform particular tasks. Because CSAT600 is a flexible tool with many applications, these example are here to show you the kind of command call order and possible output that you might see from the commands.