This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TMS320F2800157: LAUNCHXL-F2800157 Error -2131 @ 0x0 cannot connect via CCS

Part Number: TMS320F2800157
Other Parts Discussed in Thread: LAUNCHXL-F2800157

Hi,

I cannot connect to LAUNCHXL-F2800157 via CCS debugger.

Error: IcePick_C_0: Error -2131 @ 0x0
"Unable to access device register"

What I tried:
- JTAG Integrity test: ALL PASSED
- Lowered TCLK to 500kHz: no effect
- Emulation package: 20.0.0.3178
- CCS Version: 12.8.1
- Board: LAUNCHXL-F2800157

Please help. Thank you.

  • Hello Naohiro,

    Thank you for providing the detailed information about your connection issue with the LAUNCHXL-F2800157.

    Since you've already verified JTAG integrity and adjusted the TCLK frequency without success, let's try the following steps:

    1. Verify Hardware Connections

    • Ensure the USB cable is properly connected and the board is receiving power
    • Check that all jumpers on the LaunchPad are in their default positions
    • Verify the isolation jumpers are properly configured for XDS110 debug probe operation

    2. Reset the Target Device

    • Power cycle the LaunchPad completely (disconnect and reconnect USB)
    • Try holding down the device reset button while initiating the connection in CCS

    3. Update XDS110 Firmware

    • In CCS, go to View → Target Configurations
    • Right-click your configuration and select "Show all properties"
    • Look for the XDS110 firmware update option and ensure you have the latest version

    4. Check for Device Security

    • The F2800157 may have security features enabled that prevent debug access
    • If the device was previously programmed, code security settings could be blocking JTAG access
    • You may need to perform a device erase/unlock procedure

    5. Try GEL File Initialization

    • Ensure the proper GEL file for F2800157 is loaded in your target configuration
    • The GEL file handles device initialization which may resolve register access issues

    6. Alternative Connection Method

    • Try connecting with "On Connect: Reset the target" disabled in your target configuration
    • Alternatively, try connecting while the device is held in reset

    If these steps don't resolve the issue, please provide:

    • Your target configuration file settings
    • Whether this is a new board or if it was previously working
    • Any custom code or security settings that may have been programmed

    Best Regards,
    Zackary Fleenor