1. While booting into SAFE MODE the green ACTIVITY-1 LED and the red STATE-3 LED will both be ON.
| LED Name
|POWER ||Green ||ON- Power ON |
OFF - Power Off
|STATE-1 ||Green ||ON - CCS debugger connected |
OFF- CCS debugger disconnected
|STATE-2 ||Yellow ||ON - XDS560v2 System Trace Emulator FPGA programmed |
OFF- XDS560v2 System Trace Emulator FPGA not programmed
|STATE-3 ||Red ||ON - XDS560v2 System Trace Emulator ready (see note 1) |
OFF - XDS560v2 System Trace Emulator not ready
FLASH (momentary) - Ethernet connection refused (see note 2)
|ACTIVITY-1 ||Green ||ON - XDS560v2 System Trace Emulator is booting |
FLASH (momentary) - XDS560v2 System Trace Emulator configuration activity
|ACTIVITY-2 ||Yellow ||ON - XDS560v2 System Trace Emulator to Host activity (trace upload) |
OFF - No transfer
|ACTIVITY-3 ||Red ||ON - Data capture by STM receiver |
OFF - No capture
|Flashing ||SAFE MODE. When all three are simultaneously flashing this indicates safe mode. The likely causes are a failed firmware upgrade, or multiple failed boot attempts. See the FAQ section below. |
2. Only one ethernet client may use the XDS560v2 System Trace Debug Probe at a time. The ethernet connection will be refused if another client is already connected in CCS. In this case the error message will be "Error initializing Debug Probe".
##Q: What version of Code composer Studio is supported?
The XDS560v2 ProTrace is supported by Code Composer Studio v5.2.1 and newer.
##Q: Is Code Composer Studio v3.3 supported?
##Q: What utility can I use to configure my XDS560v2 Pro Trace?
Spectrum Digital provides the utility SD560v2Config.exe, which is installed with CCS and can be found at the directory below:
The manual is available from the menu **Help** → **Documentation** from within the utility.
##Q: How do I make sure that the XDS560v2 ProTrace is ready to use and functional?
- Once the POWER, STATE-2 and the STATE-3 LEDs are ON (all of them), XDS560v2 Pro Trace Debug Probe is ready to use.
- The **dtc_conf** configuration utility can also be used. Check the [DTC CONF](emu_dtc_conf.html) document for details.
##Q: The LEDs are flashing and I can't connect to the XDS560v2 Pro Trace, what does this mean?
This means the XDS560v2 System Trace Debug Probe is unable to boot properly. It may be either in safe mode or some hardware failure took place.
Scenarios where this may happen are a failed firmware update or a failure to properly boot multiple times.
The **dtc_conf** configuration utility can be used to put the Debug Probe out of the safe mode. Check the [DTC CONF](emu_dtc_conf.html) document for details.
##Q: When I launch CCS and try to connect, I see "Emulator not initialized" error message. What could be wrong?
Check the section **Host connection error** of the [Debugging JTAG](../ccs_debugging_jtag_connectivity_issues.html) page.
##Q: How can I check if the USB driver is setup correctly?
You should be able to look in Windows Devices to see if it is setup properly. It should look like below when USB is setup correctly.
![XDS560v2 Windows Control Panel](./images/Sdusbsetupok.jpg)
##Q: Ethernet isn't working but USB is what could be wrong with ethernet?
The Ethernet connection may not have been initialized. Connect the Ethernet cable before powering up the Debug Probe. This is due to an issue where the automatic Ethernet cable detection fails to work after the system finished booting.
The network and the Debug Probe may have mismatched configurations. Check the [DTC CONF](emu_dtc_conf.html) document for details on how to configure the proper address lease mechanism: DHCP or static IP.
Also, versions prior to and including epkRev 5.0.329.0 have a bug that can cause certain values of the dtcName variable to prevent ethernet from starting. Issue the command below to obtain the epk version and, if older, issue the second command to change the dtcName to an alphanumeric name:
C:\ti\ccs1010\ccs\ccs\_base\common\uscif> **dtc_conf get sd560v2u 0 epkRev**
C:\ti\ccs1010\ccs\ccs\_base\common\uscif> **dtc_conf set sd560v2u 0 "dtcName=Probe1"**
Check the [DTC CONF](emu_dtc_conf.html) document for details.
##Q: Why the XDS560v2 Pro Trace seems to be slower than my XDS560v2 System Trace?
Due to design constraints, the XDS560v2 Pro Trace uses a slower TCLK frequency up to 6.25MHz when compared to the faster 50MHz of the XDS560v2 System Trace pod.
##Q: When I try to start the Trace Control I get the "Target is disconnected" error message, what could be wrong?
This usually means that a device that was previously connected has been disconnected. Ensure that all the devices are connected by selecting the device in the tree list and pressing the Connect button.
##Q: I get the "failed to calibrate channel : no signal on clock : check external pin manager settings and clock circuit connection" error message from the Trace Control, what could be wrong?
The message indicates that no target transmitter clock was detected during the receiver calibration. This usually means that the external pin manager has not been enabled, requiring to assign and run the appropriate GEL script commands for your device. Some devices such as 66AK2H12 or 66AK2E05 require this to be done manually, but others feature a platform target configuration such as K2GEVM or IDK_AM572X, where these scripts are pre-configured.
##Q: I do not see the STM node in the CCS debug view even if I have this setup in the CCS setup configuration.
This is probably caused by not turning on option to view non-debuggable devices. This option can be turned on from CCS debug view options. Once the option is checked, you need to re-launch the debugger.
##Q: What if someone is already using the Debug Probe via ethernet? / What does "SC_ERR_OCS_ALREADY_OPEN" mean?
If someone is already using the Debug Probe on ethernet, you may get an error message like SC_ERR_OCS_ALREADY_OPEN. This means someone already has a connection to the Debug Probe.
##Q: How can I confirm the IP or the USB address of the XDS560v2 unit I am trying to access?
When using DTC_CONF, the ACTIVITY-1 LED should blink briefly.
##Q: When trying to use SD560v2Config.exe I get the message "Application Error: The application has failed to initialize properly (0xc0000135). Click on OK to terminate the application."
The problem is that .NET is not installed on your computer. Download and install [Microsoft .NET 3.5 Runtime](https://www.microsoft.com/downloads/en/details.aspx?FamilyID=333325FD-AE52-4E35-B531-508D977D32A6&displaylang=en) to fix the problem.