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/CC3220S-LAUNCHXL: Failure to debug CC3220 LaunchPad

Part Number: CC3220S-LAUNCHXL
Other Parts Discussed in Thread: UNIFLASH, CC3200

Tool/software: Code Composer Studio

Hello!

I'm currently unable to download a program to the CC3220 using the LaunchPad.  I'm quite sure I had this working before, but currently everything will fail with and error box in CCS:

Error connecting to the target:
(Error -261 @ 0x0)
Invalid response was received from the XDS110.
(Emulation package 7.0.100.1)

I do get the oob .zip programmed with UniFlash and that connects (SOP=001), but cannot get the debugger to connect with any SOP settings.  The output shows up in the terminal routed through the XDS110.  The target connection shows the IDCODE register as 0x2ba01477 and succeeds.  This is with the full row of jumpers installed (TMS,TCK,TDI,TDO.)  I think it woks for all CC3220, 3220S, 3220S_SWD.  SWD/JTAG fails accord to SOP0 selection.

With the jumpers removed I can connect with J-Link command line from the external connector, but that doesn't allow me to program the board (I can step and retrieve register values.)  I can't select that for CCS (Unable to find an appropriate device driver for the connection type "JLink" and isa "CORTEX_M4_CC".)  (That has CC3200, but no 3220 listed in device support.)

Any idea what I am missing here?  

  • Hi Jaakko,

    To make sure this isn't a board issue, please try the following:
    1. Set the SOP pins to (010 == Flash and Func, allows for 4-wire JTAG)
    2. Open a new UniFlash configuration for CC3220 (NOT SF)
    3. Set the configuration to Development mode
    4. Add only the latest servicepack
    5. Program the board with UniFlash
    6. Attempt to debug an example from the SDK with the XDS110

    This will make sure the device is in development mode where the JTAG can be accessed, that there is no application image re-configuring GPIOs, or putting the device in a low-power mode which could prevent JTAG access.

    Thanks,
    Ben M
  • Thank You!

    This made it work again (wonder what the problem was the last time.)