10. Troubleshooting¶
This chapter covers the recommended troubleshooting steps for more commonly encountered Code Composer Studio™ issues.
- 10.1. Installation
- 10.2. General IDE
- 10.3. Resource Explorer
- 10.4. Projects
- 10.5. Debug
- 10.5.1. Delete the Launch Configuration
- 10.5.2. Delete Debug Cache Files
- 10.5.3. JTAG Connectivity Issues
- 10.5.4. Data Verification Issues
- 10.5.5. Unable to Enable Trace
- 10.5.6. CPU Reset is not resetting all cores in the group
- 10.5.7. Flash programming fails with Target did not enter SACI after pin reset error
- 10.5.8. Unable to Set Hardware Breakpoints and Watchpoints on Daisy-Chained Devices
- 10.6. Getting Support
- 10.7. Common JTAG Errors
- 10.7.1. Host connection error
- 10.7.2. Cable break
- 10.7.3. Power loss
- 10.7.4. Device register
- 10.7.5. SWO/SWD and cJTAG
- 10.7.6. Device hung
- 10.7.7. Lost control of device execution state
- 10.7.8. Device blocked
- 10.7.9. Invalid device ID
- 10.7.10. Low power run mode
- 10.7.11. Library error
- 10.7.12. Invalid data read back
- 10.7.13. Pipeline stalled
- 10.7.14. Dead JTAG clock
- 10.7.15. C28x the debug probe reported an error
- 10.7.16. Invalid parameters or command
- 10.7.17. Generic FTDI failure
- 10.7.18. The emulator reported an error
- 10.7.19. Cannot access the DAP
- 10.7.20. FTDI driver function error
- 10.7.21. Target timeout
- 10.7.22. Path measure
- 10.7.23. A router subpath cannot be accessed
- 10.7.24. Incorrect SWD header
- 10.7.25. Security Error
- 10.7.26. C28x Device Locked
- 10.7.27. Device is held in reset
- 10.7.28. Device status
- 10.7.29. Device is locked
- 10.7.30. Frequency out of range
- 10.7.31. PRSC errors
- 10.7.32. Required dynamic library jscserdes not found
- 10.7.33. Invalid response was received from the XDS110
- 10.7.34. Invalid TCLK programming option
- 10.7.35. Device functional clock