ARM DSTREAM-ST Getting Started Manual page 29

DSTREAM-ST Getting Started Guide
Check List
Have the target and the DSTREAM-ST unit power cycled to ensure
normal operating conditions?
Has the DSTREAM-ST unit booted successfully?
Is the target system fully powered-up?
Does the target SoC have security features that must be disabled or
unlocked during connection?
Are there any switches or jumper links to set on the target?
Is the correct debug connector used on the target board?
Is debugging disabled in the target SoC?
Is the target's operating system disabling the debug interface during
the boot process?
Is the connection attempting to load an image into the target SoC
while the cores are running?
Does the DEBUG LED flash when trying to initiate the target
connection?
Is the connection a simple Connect Only connection in the Arm
Development Studio debug configuration for your target?
Is the Clock Speed (Hz) in the platform configuration set correctly?
Are the nTRST and nSRST signals linked on the target?
Are initialization resets putting the target into an unwanted state?
Copyright © 2017–2019, 2022 Arm Limited (or its affiliates). All rights reserved.
Things to check
To restore normal operating conditions, power-cycle the target and
your DSTREAM-ST unit.
Observe the progress of the boot sequence to confirm that your
DSTREAM-ST unit is booting properly. See
for more information. Check that the STATUS LED is
sequence
glowing steady green. If the STATUS LED flashes red, a boot failure
has occured. See Restore a DSTREAM-ST unit
Check that you have followed the power up sequence specified
•
by the target's documentation correctly. Illuminated LEDs on
the target do not necessarily mean that the SoC and debug
interface are powered.
Check if there are any buttons or switches on the target which
•
must be operated to enable the SoC and debug interface.
• Check your target's documentation or support channels for
more information.
Check the documentation of the SoC for details about security
features.
On some target boards, solder-links, jumper-links, or DIP switches
must be configured to enable debug. Check target board
documentation or support channels for more information.
Some target boards use separate debug connectors for SoCs,
FPGAs, and processor core supervisors. Check if you are using the
correct debug connector.
Some targets disable debugging for security purposes. Check if
debugging is enabled on your target.
• Try connecting and stopping the target immediately after power
up.
Try postponing the boot process using a serial connection to
•
the target.
Try halting the cores through a bare-metal connection first.
Check if the host software is communicating with the correct debug
unit. If using Arm Development Studio, to identify and ensure
you are using the correct debug unit, click the Identify button in
either the Debug Hardware Firmware Installer view
Hardware Configure IP
A simple Connect Only connection is useful to verify the
connection to the hardware. This type of connection usually does
not run any scripts or load any images on the target. To start
debugging, set the connection as either Debug from entry point or
Debug from symbol in the debug configuration.
Problems might occur if the clock speed is set too high. Set the
clock speed to lower frequencies in adaptive and non-adaptive
clocking modes.
Enable Linked_SRST_TRST in the Probe Configuration tab in the
Platform Configuration Editor in Arm Development Studio.
Disable TResetOnInitConnect and AllowICETAPreset in the Probe
Configuration tab in the Platform Configuration Editor in Arm
Development Studio.
Non-Confidential
Document ID: 100892_1.0_07_en
Troubleshooting
DSTREAM-ST unit boot
for more information.
view.
Page 29 of 31
Version 1.0
or the Debug