• State
  • Replies 1 reply
  • Subscribers 31 subscribers
  • Views 34 views
  • Users 0 members are here
Support feedback
Options
Options
Related

Original question:

CCS/CC3220SF-LAUNCHXL: Error -1170 when I try to download/debug mqtt_client example on CC3220SF-LAUNCHXL

LP-AM263P: Error code 1170 - DAP connection error - error connecting to the Target (ARM based MCU)

Yamuna Sundar
Prodigy 10 points

Part Number: LP-AM263P

Currently, I am using the AM263Px launchpad for bare-metal firmware development for our work project and my goal is to to get familiar with the functionality of this development board.

I am trying to test out an example program - i2c_led_blink_polling_lld_am263px-lp_r5fss0-0_nortos from the mcu_plus_sdk_am263px_26_00_00_01 using the AM263Px launchpad.

I am able to build the project successfully using CCS 12.7.1 However, when I try to debug or flash the code to the board, I am getting the  error code 1170 -  "Cortex_M4_0: Error connecting to the target: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 20.0.0.3178) ."

The error persists after implementing the below troubleshooting steps:

  • Tried all troubleshooting steps suggested in https://software-dl.ti.com/ccs/esd/documents/ccs_debugging_jtag_connectivity_issues.html.
  • Unchecked Cortex M4 under the Debug Configurations -> Main . 
  • Under target configurations - Edited the source script to halt under a reset, set reset type to hardware and  lower the TCLK.
  • Under target configuration, tested the connection between the port and the board using the Test Connection tab and the reslults were successful. 
  • Made sure the XDS110 firmware version is the recommended version for use - 3.0.0.32

I am not sure if I am missing any other steps but I am unable to resolve this issue. Any help or insight will be much appreciated. Pasted some screenshots below for reference.

 

Error 1170.pngi2c_led_blink_am263px_console_output.png

I also noticed another issue where I am not able to load some "no-rtos launchpad" examples (under drivers) from the SDK into CCS. I am using CCS 12.7.1 Not sure if this is related to the CCS version or some other issue. Even if I am able to load the required folder, the build icon is disabled. Please help.

 

 

  • 0
    TI__Mastermind 31163 points

    Hi Yamuna,

    Thank you for the detailed description of the issue. I've reviewed your setup and error logs, and I believe I've identified the root cause along with several troubleshooting steps that should resolve the Error -1170.

    Primary Issue: Incorrect Core Target

    Looking at your console output, I notice a critical mismatch. The error message shows:

    Cortex_M4_0: Error connecting to the target: (Error -1170 @ 0x0)

    However, your console output clearly indicates the AM263Px has R5F cores:

    Cortex_R5_0: GEL Output: SYS_CLK DIVBY2
    Cortex_R5_1: AM263Px
    Cortex_R5_2: AM263Px
    Cortex_R5_3: AM263Px
    While you mentioned unchecking the Cortex M4 option, the error message suggests CCS is still attempting to connect to the HSM M4 core. The i2c_led_blink_polling_lld example for r5fss0-0_nortos should target Cortex_R5_0.

    Recommended Actions

    1. Verify Debug Configuration

    • Open Debug Configurations → Target tab
    • Confirm you are connecting to Cortex_R5_0 (not Cortex_M4_0)
    • Ensure all M4 cores are unchecked if they appear in the target list
    • The example is built for r5fss0-0, which corresponds to Cortex_R5_0

    2. Re-create Target Configuration

    • Go to File → New → Target Configuration
    • Select AM263Px device
    • Select XDS110 emulator
    • Choose JTAG connection type
    • Let CCS auto-detect the cores
    • Save and set as the active configuration

    3. Additional DAP Connection Troubleshooting

    If the core target is correct but you still see Error -1170, work through these steps systematically:

    Power and Reset:

    • Power-cycle both the launchpad and your PC
    • Press the hardware reset button on the board before attempting to debug
    • Verify the target voltage is 3.3V (can check in CCS Target Configuration)

    JTAG Clock Settings:

    • In your target configuration, lower the TCLK frequency to 1 MHz or lower
    • This is especially important when the board is powered via USB only

    XDS110 Firmware:

    • You mentioned firmware version 3.0.0.32, which is correct for CCS 12.7.1
    • To verify: Help → Check for Updates → Texas Instruments Emulators
    • If available, update to the latest compatible version

    Secure Device Check:

    • If your AM263Px is a secure variant, the DAP may be locked
    • In CCS: Debug → Target Configuration → Advanced
    • Look for secure debug options and ensure they are properly configured

    Test Connection:

    • After each change above, run Test Connection in your target configuration
    • If Test Connection passes but debug still fails, capture the full console log output

    4. Start with a Simpler Example

    Before debugging the I2C example, try a basic example first:

    • Look for a simple GPIO or LED blink example without peripheral dependencies
    • This will help determine if the issue is board-wide or example-specific

    Regarding Your Second Issue: Unable to Load No-RTOS Examples

    This appears to be a separate issue related to project import. Try these steps:

    1. Verify SDK Installation:

      • Confirm the SDK path is registered in CCS: Window → Preferences → Code Composer Studio → Products
      • The path should point to your mcu_plus_sdk_am263px_26_00_00_01 installation

    2. Use Proper Import Method:

      • Use File → Import → CCS Projects instead of manually opening folders
      • Browse to the SDK examples directory
      • Select the specific example project and import

    3. Check CCS Version Compatibility:

      • SDK version 26.00.00.01 may have specific CCS version requirements
      • Verify the SDK release notes for the recommended CCS version
      • Consider updating to the latest CCS 20.x version if possible - https://www.ti.com/tool/download/CCSTUDIO/

    Next Steps

    Please try the debug configuration corrections first, particularly ensuring you're targeting Cortex_R5_0 instead of Cortex_M4_0.

    If the issue persists after these steps:

    1. Enable debug logging in CCS: View → Console → Enable Debug Logging
    2. Capture the full console output when the error occurs
    3. Note the exact error message and any additional details
    4. Reply with this information and I can provide further guidance

    Let me know how these steps work out or if you need clarification on any of the procedures.

    Best Regards,
    Zackary Fleenor