11. Troubleshooting¶
This chapter covers the recommended troubleshooting steps for more commonly encountered CCStudio™ IDE issues.
- 11.1. Installation
- 11.2. General IDE
- 11.3. Resource Explorer
- 11.4. Projects
- 11.5. Debug
- 11.5.1. Delete the Launch Configuration
- 11.5.2. Delete Debug Cache Files
- 11.5.3. JTAG Connectivity Issues
- 11.5.4. Data Verification Issues
- 11.5.5. Unable to Enable Trace
- 11.5.6. Flash programming fails with Target did not enter SACI after pin reset error
- 11.5.7. Debug launch fails with No matching COM port found error
- 11.6. Getting Support
- 11.7. Common JTAG Errors
- 11.7.1. Host connection error
- 11.7.2. Cable break
- 11.7.3. Power loss
- 11.7.4. Device register
- 11.7.5. SWO/SWD and cJTAG
- 11.7.6. Device hung
- 11.7.7. Lost control of device execution state
- 11.7.8. Device blocked
- 11.7.9. Invalid device ID
- 11.7.10. Low power run mode
- 11.7.11. Library error
- 11.7.12. Invalid data read back
- 11.7.13. Pipeline stalled
- 11.7.14. Dead JTAG clock
- 11.7.15. C28x the debug probe reported an error
- 11.7.16. Invalid parameters or command
- 11.7.17. Generic FTDI failure
- 11.7.18. The emulator reported an error
- 11.7.19. Cannot access the DAP
- 11.7.20. FTDI driver function error
- 11.7.21. Target timeout
- 11.7.22. Path measure
- 11.7.23. A router subpath cannot be accessed
- 11.7.24. Incorrect SWD header
- 11.7.25. Security Error
- 11.7.26. C28x Device Locked
- 11.7.27. Device is held in reset
- 11.7.28. Device status
- 11.7.29. Device is locked
- 11.7.30. Frequency out of range
- 11.7.31. PRSC errors
- 11.7.32. Required dynamic library jscserdes not found
- 11.7.33. Invalid response was received from the XDS110
- 11.7.34. Invalid TCLK programming option
- 11.7.35. Device functional clock