CoreSight Access Tool for SoC600 (CSAT600) User Guide

Overview How to use CSAT600 CSAT600 command list Command comparison between CSAT600 and CSAT Worked examples for CSAT600
Single Page

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.

  • autodetect (auto)

    Autodetect which CoreSight devices are present on the target.

    To run this command, you must have a debug probe connection. See the instructions at connect (con) for details on how to connect to your debug probe.

    Syntax

    autodetect (auto) [enum-aps] [read-rom]

    Where:

    enum-aps

    Enumerates the autodetected Access Ports (APs).

    read-rom

    Returns the contents of the read ROM table.

    Example

    %> autodetect
    Detecting platform...
    ------------+--------------------------------+---------
     Device No. | DTSL Device Name (& Address)   | AP No.
    ------------+--------------------------------+---------
              0 |                      ARMCS-DP  |
    
%> auto enum-aps
    Detecting platform...
    ------------+--------------------------------+---------
     Device No. | DTSL Device Name (& Address)   | AP No.
    ------------+--------------------------------+---------
              0 |                      ARMCS-DP  |
              1 |         CSMEMAP_0 (0x00000000) | 0
              2 |         CSMEMAP_1 (0x00000000) | 1 
    
%> autodetect read-rom
Detecting platform...
------------+--------------------------------+---------
 Device No. | DTSL Device Name (& Address)   | AP No.
------------+--------------------------------+---------
          0 |                      ARMCS-DP  |
          1 |         CSMEMAP_0 (0x00000000) | 0
          2 |      Cortex-A53_0 (0x80410000) | 0 
    ...
  • cfgbox (cfb)

    Get or set the DSTREAM probe configuration.

    To run this command, you must have a debug probe connection. See the instructions at connect (con) for details on how to connect to your debug probe.

    Syntax

    cfgbox (cfb) [<item_name> [<item_value>]]

    Where:

    item_name

    DSTREAM configuration item to be configured.

    item_value

    Value to set the DSTREAM configuration item to.

    Example

    %> cfgbox
    Linked_SRST_TRST     : 0
    SRSTOnConnect        : 0
    UserOutputPin  s     : 000000
    UseDeprecatedSWJ     : 0
    ...
    
%> cfb SRSTOnConnect
SRSTOnConnect: 1
    
%> cfb SRSTOnConnect 0
SRSTOnConnect: 0
  • cfgtplate (cfg)

    Get or set DSTREAM configuration items for the current CoreSight device.

    To run this command, you must have both an active debug probe connection, and an active CoreSight device connection. See the instructions at connect (con) for details on how to connect to your debug probe. See the instructions at devopen (dvo, device) for details on how to connect to a Coresight device.

    Syntax

    cfgtplate (cfg) [<item_name> [<item_value>]]

    Where:

    item_name

    DSTREAM configuration item to be configured.

    item_value

    Value to set the DSTREAM configuration item to.

    Example

    %> cfgtplate
    CTI_SYNCH_START      : 0
    NUM_STEP_COMPLETE_TRIES : 20
    ALLOW_BACKGROUND_PROC : 0
    DAP_DBG_RESET_ON_POWERUP : 0
    ...
    
%> cfg POST_RESET_STATE
POST_RESET_STATE: 0
    
%> cfg POST_RESET_STATE 1
POST_RESET_STATE: 1
  • chain (chn)

    Set or autodetect the JTAG scan chain and clock frequency.

    To run this command, you must have a debug probe connection. See the instructions at connect (con) for details on how to connect to your debug probe.

    Syntax

    chain (chn) [dev=device_name1,...,device_nameN | dev=auto] [clk=<freqHz> | clk=A]

    Where:

    dev

    Use this to specify one or more devices on the JTAG scan chain. Alternatively, set to auto to autodetect all of the devices on the JTAG scan chain.

    clk

    Value to set the debug adapter clock frequency to in Hz or A to use adaptive clocking.

    Example

    %> chain dev=ARMCS-DP
------------+--------------------------------+---------
 Device No. | DTSL Device Name (& Address)   | AP No.
------------+--------------------------------+---------
          0 |                      ARMCS-DP  |
    
%> chn dev=ARMCS-DP clk=10000000
    
------------+--------------------------------+---------
     Device No. | DTSL Device Name (& Address)   | AP No.
    ------------+--------------------------------+---------
              0 |                      ARMCS-DP  |
    
%> chain dev=auto
    
Detecting scanchain...
    
------------+--------------------------------+---------
     Device No. | DTSL Device Name (& Address)   | AP No.
    ------------+--------------------------------+---------
              0 |                      ARMCS-DP  |
  • connect (con)

    Connect to a DSTREAM debug probe via TCP or USB.

    Syntax

    connect (con) TCP:<hostname> | TCP:<ip address> | USB [config file]

    Where:

    TCP

    Use this option if you are connecting to your DSTREAM debug probe using an Ethernet connection. You must specify either the hostname or the IP address.

    USB

    Use this option if you are connecting to your DSTREAM debug probe through USB.

    config file

    Specify the System Description File (SDF) from a platform configuration used when connecting to the target. If an SDF is not supplied, you must run a CoreSight device discovery command. See instructions at autodetect (auto) or chain (chn) for details on discovering CoreSight devices.

     Example

    %> connect TCP:255.255.255.255
Connecting to TCP:255.255.255.255 ...
Connected to: DSTREAM
Base H/W: V2 Rev C-00
TurboTAP Rev: 0.16
DSTREAM Probe V1 Rev B-00
Firmware: 5.0.0, Build 7
Configuration file: C:\Users\<user>\AppData\Local\Temp\csat_scanchain_devices5451335090165749803.sdf
    
%> con USB
    Connecting to USB ...
    Connected to: DSTREAM
    Base H/W: V2 Rev C-00
    TurboTAP Rev: 0.16
    DSTREAM Probe V1 Rev B-00
    Firmware: 5.0.0, Build 7
    Configuration file: C:\Users\<user>\AppData\Local\Temp\csat_scanchain_devices713844846634569063.sdf
    
%> con TCP:myDSTREAM C:\work\target.sdf
Connecting to TCP:myDSTREAM ...
Connected to: DSTREAM
Base H/W: V2 Rev C-00
TurboTAP Rev: 0.16
DSTREAM Probe V1 Rev B-00
Firmware: 5.0.0, Build 7
Configuration file: C:\work\target.sdf
  • devclose (dvc)

    Close the connection to the CoreSight device.

    To run this command, you must have both an active debug probe connection, and an active CoreSight device connection. See the instructions at connect (con) for details on how to connect to your debug probe. See the instructions at devopen (dvo, device) for details on how to connect to a Coresight device.

    Syntax

    devclose (dvc) [<device no>]

    Where:

    device no

    CoreSight device number to close the connection to. Use the autodetect (auto), chain (chn), or list (l) commands to determine the device number.

    Example

    %> devclose
    Disconnected from device no. 2
    
%> dvc 2
    Disconnected from device no. 2
  • devopen (dvo, device)

    Open a connection to a CoreSight device.

    To run this command, you must have a debug probe connection with an SDF or a debug probe connection and have discovered CoreSight devices. See the instructions at connect (con) for details on how to connect to your debug probe. See the instructions at autodetect (auto) or chain (chn) for details on discovering CoreSight devices.

    Syntax

    devopen (dvo, device) <device no>

    Where:

    device no

    CoreSight device number to open a connection to. Use the autodetect (auto), chain (chn), or list (l) commands to determine the device number.

    Example

    %> devopen 2
    Connected to device no. 2: Cortex-A53_0, JTAG ID: 0x1ba06477, version 0x00000006
    Msg returned from device: Cortex-A53 Template
    
%> dvo 0
Connected to device no. 0: ARMCS-DP, JTAG ID: 0x1ba06477, version 0x00000006
Msg returned from device: ARM-DP Template using Rv-Msg.

    %> device 2
Connected to device no. 2: Cortex-M3, JTAG ID: 0x3ba00477, version 0x00000006
Msg returned from device: Cortex M3 template
  • disconnect (dcn)

    Disconnect from the DSTREAM probe.

    To run this command, you must have a debug probe connection. See the instructions at connect (con) for details on how to connect to your debug probe.

    Syntax

    disconnect (dcn)

    Example

    %> disconnect
Disconnected from TCP:255.255.255.255
    
%> dcn
Disconnected from USB
  • exit (x)

    Close the CSAT600 program.

    Syntax

    exit (x)

    Example

    %> exit
Disconnected from TCP:255.255.255.255
    
%> x
Disconnected from TCP:255.255.255.255
  • help (h)

    List all the available CSAT600 commands, or display the help information for a specific command.

    Syntax

    help (h) <command>

    Where:

    command

    Command name to display help content for.

    Example

    %> help
autodetect (auto)        : Autodetect which CoreSight devices are present on the target.
cfgbox     (cfb)         : Configure the DSTREAM probe.
cfgtplate  (cfg)         : Get or set DSTREAM configuration items for the current CoreSight device.
    ...
    
%> h autodetect
    Command: autodetect
            Autodetect which CoreSight devices are present on the target.
    Aliases:
            auto
    Usage:
            autodetect [enum-aps] [read-rom]
            auto [enum-aps] [read-rom]
  • list (l)

    List the available CoreSight devices.

    To run this command, you must have a debug probe connection with an SDF or a debug probe connection and have discovered CoreSight devices. See the instructions at connect (con) for details on how to connect to your debug probe. See the instructions at autodetect (auto) or chain (chn) for details on discovering CoreSight devices.

    Syntax

    list (l)

    Example 

    %> list
------------+--------------------------------+---------
 Device No. | DTSL Device Name (& Address)   | AP No.
------------+--------------------------------+---------
          0 |                      ARMCS-DP  |
          1 |         CSMEMAP_0 (0x00000000) | 0
          2 |      Cortex-A53_0 (0x80410000) | 0
          3 |           CSCTI_0 (0x80420000) | 0
    ...
  • log

    Control logging.

    Syntax

    log on | off | <filename>

    Where:

    on

    Turns on logging.

    off

    Turns off logging.

    filename

    Path and filename to save the logging to.

    Example 

    %> log on
Logging is enabled with logfile: C:\Users\<user>\AppData\Local\Temp\csat7441679604713525243.log
    
%> log on C:\Users\<user>\AppData\Local\Temp\csat.log
Logging is enabled with logfile: C:\Users\<user>\AppData\Local\Temp\csat.log
    
%> log off
Logging is disabled.
  • memread (mr)

    Read memory from the specified address.

    To run this command, you must have a debug probe connection with an SDF or a debug probe connection and have discovered CoreSight devices. See the instructions at connect (con) for details on how to connect to your debug probe. See the instructions at autodetect (auto) or chain (chn) for details on discovering CoreSight devices.

    Syntax

    memread (mr) <address> <number of words to read> [rule=<memory operation modifiers>]

    Where:

    address

    Address to read from.

    number of words to read

    Number of words to read starting at the specified address. A word is 32 bits or 4 bytes.

    rule

    Used to set the rule parameter of a memory access operation. The rule value varies depending on the DTSL device type being used and the associated DSTREAM functionality that uses it. This parameter is most useful for Memory Access Port (MEMAP) accesses where it can be used to modify specific parts of the AP’s CSW register. The rule parameter might have more specialist uses for some core device accesses in certain circumstances.

    For an AHB device, the rule field maps to the 5 bits of the HPROT field.

    For an AXI-AP device, the encoding of the rule field is more complex, and consists of:

    •   Mode (4 bits) << 0x10
    •   Domain (3 bits) << 0x8
    •   Ace bit << 0x7
    •   PROT (3 bits) << 0x4
    •   CACHE ( 4bits)

    See the Arm Debug Interface Architecture Specification ADIv6.0 for details of what effect these values have on the accesses using the above memory buses.

    Example

    %> memread 0x80540000 8
    Reading from device no. 1: CSMEMAP_0
    0x80540000 : 0x00000000
    0x80540004 : 0x00000000
    0x80540008 : 0x00000000
    0x8054000c : 0x00000003
    0x80540010 : 0x00000001
    0x80540014 : 0x00000000
    0x80540018 : 0x00000000
    0x8054001c : 0x00000000
    

    %> mr 0x80540000 8 rule=0
    Reading from device no. 1: CSMEMAP_0
    0x80540000 : 0x00000000
    0x80540004 : 0x00000000
    0x80540008 : 0x00000000
    0x8054000c : 0x00000003
    0x80540010 : 0x00000001
    0x80540014 : 0x00000000
    0x80540018 : 0x00000000
    0x8054001c : 0x00000000
  • memwrite (mw)

    Write memory to the specified address.

    To run this command, you must have a debug probe connection with a SDF or a debug probe connection and have discovered CoreSight devices. See connect (con) for details on how to connect to your debug probe. See autodetect (auto) or chain (chn) for details on discovering CoreSight devices.

    Syntax
    memwrite (mw) <address> <data>...[dataN]* [rule=<memory operation modifiers>]

    Where:

    address

    Address to write to.

    data...dataN

    Data to write starting at the specified address.

    rule

    Used to set the rule parameter of a memory access operation. The rule value varies depending on the DTSL device type that is being used and the associated DSTREAM functionality that uses it. This parameter is most useful for Memory Access Port (MEMAP) accesses where it can be used to modify specific parts of the CSW register of the AP. The rule parameter might have more specialist uses for some core device accesses in certain circumstances.

    For an AHB device, the rule field maps to the 5 bits of the HPROT field.

    For an AXI-AP device, the encoding of the rule field is more complex, and consists of:

    •   Mode (4 bits) << 0x10
    •   Domain (3 bits) << 0x8
    •   Ace bit << 0x7
    •   PROT (3 bits) << 0x4
    •   CACHE ( 4bits)

    See the Arm Debug Interface Architecture Specification ADIv6.0 for details of what effect these values have on the accesses using the above memory buses.

    Example

    %> memwrite 0x80540004 1
    Writing to device no. 1: CSMEMAP_0
    Wrote 4 bytes.
    
%> mw 0x80540004 0 rule=0
    Writing to device no. 1: CSMEMAP_0
    Wrote 4 bytes.
Previous Next