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.

CCS/CC3220SF-LAUNCHXL: CC3220SF-LAUNCHXL

Part Number: CC3220SF-LAUNCHXL

Tool/software: Code Composer Studio

After the latest CCS update (Nov 8 2020) I am starting to see debugger problems, specifically:

Cortex_M4_0: JTAG Communication Error: (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 9.2.1.00042) 

Cortex_M4_0: Failed to remove the debug state from the target before disconnecting.  There may still be breakpoint op-codes embedded in program memory.  It is recommended that you reset the emulator before you connect and reload your program before you continue debugging

Sometimes resetting the DAP or debugger or the entire toolchain (CCS, computer) it gets going again but I am not convinced any of these are not just a monkey trick.  When it fails, my target board restarts with the onboard code which I can connect to (connect target). If I show all cores the Probe/IcePick_C is off line (not surprisingly).

I cannot quite figure out what causes this and/or how I remedy it.

CCS:  Version: 9.3.0.00012

macOS: 10.15.7, 32G, 8 Core i9

  • Hi joost,

    The DAP -1170 error occurs when the CC32xx device locks the JTAG pins in Production mode. Can you flash your LaunchPad in Development mode again? See the ImageCreator Basics training.

    I also suggest trying a different USB cable and port.

    Best regards,

    Sarah

  • Hi Sarah,

    I suspected the device was in production mode and made sure it is in dev mode already. I also already changed cables and the USB-C to USB2/3 converter. Using a CalDigit port converter seemed in general better to work with the development board. But again, no dice.

    joost

  • Hi joost,

    Are you able to test the latest CCS version? https://www.ti.com/tool/download/CCSTUDIO

    DAP issues may indicate a hardware problem. Do you have another LaunchPad you can try?

    Best regards,

    Sarah

  • I do have a second LaunchPad and it behaves the same way.  I will have a look at CCS V10 though I am a bit leery of installing a complete new ccs which may break all sorts of other things.

  • The issue was found.

    At the (roughly) the same time CCS 9 had an update, I added WatchDog functionality to my firmware. Every time I reset the target, it starts its firmware just before I start the JTAG download of new testable code. That firmware had the WD running which caused the reset.

    All very understandable and clear.  But boy, why not have a note in the example watchdog driver code about this? Would have saved me a ton of time.

  • Hi joost,

    Thanks for posting that resolution.

    You're correct, the bootloader will start executing the flashed application binary upon reset which can conflict if you are then trying to start a debug session. (A similar issue may occur if the power policy enters a low-power mode.) I haven't seen your particular issue with the watchdog before, but I'll see if we can clarify that behavior with the JTAG.

    Best regards,

    Sarah