Hello,

Andrea Adamo said:

The value is '-230' (0xffffff1a).

The title is 'SC_ERR_PATH_MEASURE'.

 

The explanation is:

The measured lengths of the JTAG IR and DR scan-paths are invalid.

This indicates that an error exists in the link-delay or scan-path.

 

This is a low level JTAG connection error documented in the below links:

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

https://software-dl.ti.com/ccs/esd/documents/ccs_debugging_jtag_connectivity_issues.html#path-measure

While the root cause can vary, it is almost always due to some hardware connectivity issue (especially error -233), especially on custom boards and custom JTAG connections. Please check all the physical JTAG connections and make sure the signal integrity looks good. Also check that the device is not locked. You can try lowering the TCLK value also.

Hope this helps

ki

Slowing the TCLK the error change and become the seme as before, using JTAG instead of cJTAG. In addition I am not using a custom pcb or JTAG, I am using the launchpad connecter with USB. Moreover I can see the red error led turned on on the launchpad, how can I know why I have the led on?
The error now I see is:

[Start: Texas Instruments XDS110 USB Debug Probe_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]

-----[Print the board config pathname(s)]------------------------------------

C:\Users\Andrea\AppData\Local\Texas Instruments\
CCS\ccs1011\0\0\BrdDat\testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioxds110.dll'.
The library build date was 'Nov 8 2020'.
The library build time was '17:25:15'.
The library package version is '9.2.1.00042'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '5' (0x00000005).
The controller has an insertion length of '0' (0x00000000).
This utility will attempt to reset the controller.
This utility has successfully reset the controller.

-----[Print the reset-command hardware log-file]-----------------------------

The scan-path will be reset by toggling the JTAG TRST signal.
The controller is the XDS110 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for XDS110 features.
The controller cannot monitor the value on the EMU[0] pin.
The controller cannot monitor the value on the EMU[1] pin.
The controller cannot control the timing on output pins.
The controller cannot control the timing on input pins.
The scan-path link-delay has been set to exactly '0' (0x0000).

-----[An error has occurred and this utility has aborted]--------------------

This error is generated by TI's USCIF driver or utilities.

The value is '-233' (0xffffff17).
The title is 'SC_ERR_PATH_BROKEN'.

The explanation is:
The JTAG IR and DR scan-paths cannot circulate bits, they may be broken.
An attempt to scan the JTAG scan-path has failed.
The target's JTAG scan-path appears to be broken
with a stuck-at-ones or stuck-at-zero fault.

[End: Texas Instruments XDS110 USB Debug Probe_0]

Andrea Adamo said:

I am using the launchpad connecter with USB.

Are you using the on-board JTAG via USB connection? If so, the debug probe should be an XDS100v2 on that launchpad, not an XDS110.

Yes the on-board JTAG via USB connection. I have tried with XDS100vd and I gat the error below. But I think this launchpad has the XDS110, I am following this guide: 

processors.wiki.ti.com/.../LAUNCHXL2_TMS57012:_Project_0

Error:

[Start: Texas Instruments XDS100v2 USB Debug Probe_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

[Result]

-----[Print the board config pathname(s)]------------------------------------

C:\Users\Andrea\AppData\Local\Texas Instruments\
CCS\ccs1011\0\0\BrdDat\testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioserdesusb.dll'.

An error occurred while soft opening the controller.

-----[An error has occurred and this utility has aborted]--------------------

This error is generated by TI's USCIF driver or utilities.

The value is '-151' (0xffffff69).
The title is 'SC_ERR_FTDI_OPEN'.

The explanation is:
One of the FTDI driver functions used during the connect
returned bad status or an error. The cause may be one or
more of: no XDS100 is plugged in, invalid XDS100 serial number,
blank XDS100 EEPROM, missing FTDI drivers, faulty USB cable.
Use the xds100serial command-line utility in the 'common/uscif'
folder to verify the XDS100 can be located.

[End: Texas Instruments XDS100v2 USB Debug Probe_0]

This is what I see using an oscilloscope on J1, pins 1, 2 and 3, which should be the external JTAG pins TMS, nTRST, and TDI in order in the next figures.

Andrea Adamo said:

Yes the on-board JTAG via USB connection. I have tried with XDS100vd and I gat the error below. But I think this launchpad has the XDS110, I am following this guide: 

I think you are correct. I was confused because this document seems to mention both. But I think it is indeed an XDS110.

Unfortunately it does look like some low level HW failure with the target as the debugger is unable to circulate bits successfully on the scan chain. I will move this thread to the device forum for more suggestions.

Thanks

ki

Andrea Adamo said:

This is what I see using an oscilloscope on J1, pins 1, 2 and 3, which should be the external JTAG pins TMS, nTRST, and TDI in order in the next figures.

Can you confirm if are attempting to use an external debug probe, or the internal XDS110 on the launchpad?

Also, which jumpers are fitted on the launchpad?

Hi Andrea,

After the US cable is connected, what are the status of the LED4, LED6, and LED7 on the Launchpad?

J1 isn't populated on the launchpad when shipped by TI. Can you confirm if are attempting to use an external debug probe, or the internal XDS110 on the launchpad? Also, which jumpers are fitted on the launchpad?

J1 is not populated on the launchpad but I have connected some cables to look at the signals as shown in the figure below. I am trying to use the the internal XDS110 on the launchpad just connecting the launchpad to the computer with USB as shown in the figure below. I have jumpers JP2, JP3 and JP6 fitted and JP1 unfitted as shown in the figure below. 

After the US cable is connected, what are the status of the LED4, LED6, and LED7 on the Launchpad?

LED4, LED6, and LED7 are turned on as shown in the figure below, in addition, LED1 is turned on as well which is the ERROR LED in red.

Furthermore, I would like to add that this launchpad has been tried to use as a debugger, using the XDS110 into the launchpad, to program an external TMS microcontroller, for this reason, resistor R29 has been removed in the past, but now it is soldered in the launchpad. It is just a resistor wich permit the power supply of the uC TMS of the launchpad. 

Hello,

The original R29 is current sensing resistor. It is a small resistor (0.01ohmes, 1%) so as to minimize the voltage drop or power consumption. Please double check to make sure your R29 is a small one.

Yes, it is the original one, if i use the tester y see a short circuit as it is just 0.01ohmes. Any other idea? any other things I should check? This resistor (r29) has positive and negative? I suppose not.

This resistor signales go into a differential amplifier. On one side of the resistor I have 1,26150 V, in the other I have 1,260820V, and doing the calculation I see the differential amplifier works well as I see 99 mV at the output of the differential amplifier, this value go directly into a pin of the microcontroller called Hercule core. 

I finally solve the problem, a part from R29, R9 was missing, a 2.2Kohms resistor. I have soldered it and now it works.

I have tryed to load the code to the launchpad, but I get an error, ever just following the guide to blink a led: 

processors.wiki.ti.com/.../LAUNCHXL2_TMS57012:_Project_0

I get this error:

CortexR4: GEL Output: Memory Map Setup for Flash @ Address 0x0CortexR4: Loader: One or more sections of your program falls into a memory region that is not writable. These regions will not actually be written to the target. Check your linker configuration and/or memory map.
CortexR4: File Loader: Verification failed: Values at address 0x00000000 do not match Please verify target memory and memory map.
CortexR4: GEL: File: C:\Users\Andrea\workspace_v10\LaunchProj0\Debug\LaunchProj0.out: a data verification error occurred, file load failed.

Andrea,

Did you update the EMU Pack version to 9.2.1? I suspect you are running into the same issue in the thread below:

https://e2e.ti.com/support/tools/ccs/f/81/t/959921

thanks

ki