• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 40 subscribers
  • Views 1048 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

CCS/CC3220MOD: SC_ERR_PATH_BROKEN

CCS/CC3220SF-LAUNCHXL: SC_ERR_PATH_MEASURE -230

Tim Allen76
Prodigy 10 points
Part Number: CC3220SF-LAUNCHXL
Other Parts Discussed in Thread: UNIFLASH, CC3220SF

Tool/software: Code Composer Studio

hello All,

We have a new target board based on the Launchpad XL schematics but with a reduced board area.

I have been trying out helpful suggestions from TI field staff, but continue to see some problems when trying to connect by jtag to the new target board (it’s set for development mode) using an external XDS110 box.

The target board is up and running, such that in production mode the TI out-of-the-box demo can be loaded via uniflash, and will work with an phone just as the launchpad board does.  The loading was done with the xds110 on a launchpad attached by patch wires to the new target.  So far so good.

There is no site provided on the new target board for a normal jtag connector, hence the jtag connection is via a number of patch wires - that could be the problem - but everything buzzes out as going to the right place.  Clearly not matched for impedance or wire length though.

The problems arise when trying to load via jtag from the external XDS110, in order to debug our new code.

Using CCS v8.1.0.00011 the connection properties in CCS Target Configuration are set as follows

Autogenerate
Only one XDS110
Target supplied power
default (voltage)
User specified clock
100kHz
Don’t isolate after
JTAG 4 pin standard mode.

The error shown is currently -233 SC_ERR_PATH_BROKEN.

As a sanity check I tried the offboard XDS connected via a different cable adapter to the CC3220SF end of the launchpad board (also in development mode) via J8.  This is giving the same error as with the new target board.  A fualt with the new jtag box perhaps?

The offboard XDS110 on initial connection required a bootloader update and a serial number change.  It was showing all 0s; now set to 0000 0011.

Xdsdfu -e finds the device so that much works –

--
C:\ti\ccs_base\common\uscif\xds110>xdsdfu -e

USB Device Firmware Upgrade Utility

Copyright (c) 2008-2018 Texas Instruments Incorporated.  All rights reserved.

Scanning USB buses for supported XDS110 devices...

<<<< Device 0 >>>>

VID: 0x0451    PID: 0xbef3
Device Name:   XDS110 Probe with CMSIS-DAP
Version:       2.3.0.14
Manufacturer:  Texas Instruments
Serial Num:    00000011
Mode:          Runtime

Found 1 device.

--

Any suggestions as to where I am going wrong would be much appreciated.

Thanks in advance!
Best regards

Tim

--

  • 0
    TI__Guru**** 171094 points

    Tim,

    Thanks for the detailed post. 

    Tim Allen76 said:
    The error shown is currently -233 SC_ERR_PATH_BROKEN.

    A description of this error is shown at the following reference:

    http://software-dl.ti.com/ccs/esd/documents/ccs_debugging_jtag_connectivity_issues.html#invalid-data-read-back 

    As you can tell, you are on the right track regarding the location of the issue - between the Debug Probe and the target device, including a possibility the wiring is wrong. 

    A few details that may get in the way of a proper connection: 

    - When connecting to the Launchpad, make sure you remove all JTAG-related jumpers to avoid conflict between the external connection and the built-in XDS110

    - When connecting using flying wires, just be sure to tie them to the bottom pins on the J3 connector (I have done the opposite in the past).

    - Your JTAG TCLK speed is too low. I would use at least 500kHz or 1MHz.

    - Make sure the SOP is adequately set to operate in JTAG mode (either 000 or 010). 

    Hope this helps,

    Rafael