TMS320F280039C: Issue in flashing

Hi,

What hardware are you using? TI Evaluation board or custom PCB? Please check the target config file settings and advanced settings.

Best,

Kevin

Hi,

I tested it with a custom board as well as the LAUNCHXL-F280039C and it leads to the same result:

This is the log directly on the LAUNCHXL, originally out of the box (I tested several ones):

[Start]

Execute the command:

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

[Result]


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

C:\Users\SEBAST~1\AppData\Local\TEXASI~1\
    CCS\ccs1210\0\0\BrdDat\testBoard.dat

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

This utility has selected a 100/110/510 class product.
This utility will load the adapter 'jioxds110.dll'.
The library build date was 'Jun  2 2023'.
The library build time was '12:47:07'.
The library package version is '9.12.0.00150'.
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]

So exactly the same issue with a TI board. The verification is done in the universal_motorcontrol_test project properties:

A verification under the .ccxml works and the XDS110 is correctly identified there:

I could once flash the LAUNCHXL kit with the universal motor control firmware and now I always get this error when I try to flash it in the CCS:

It doesn't matter if I restart the PC, power off the device or using another USB port. Always the same error occurs

What I found out is, that this error only occurs in the universal motor control project, I really don't know why.

Hi,

It should be an issue with the target config file being used. Can you try 'Option 2: Manually launching target configuration' explained in the Academy module below:

https://dev.ti.com/tirex/explore/content/c2000_academy_2_05_00_51/_build_c2000_academy_2_05_00_51/source/c2000_get_started/c2000_getstarted.html#set-up-target-configuration

Best,

Kevin