Part Number: TMS320F280048C
Brand new launch pad demo worked great but first attempt to use debug CCS 9.1 say it has to update XDS110, do not unplug. Also noticed the blue LED3 stay on all the time. Blue LED2 blinks in loop back test and send of out.bin file but LED2 stay on blue no blinky.
So we have BoostXLDRV8320RS kit set on site 2 (user.h site 2) and JP1-3 removed, J8 2 jumpers installed. Have used another USB cable and other TI XDS100 works from other lauch pads via CCS 9.1
The XDS110 failing on brand new launch pad windows drivers installed. We need to send this broken x49c back to TI for ship a working launch pad ASAP. The POR runs the firmware but the XDC110 is broken.
[Start: Texas Instruments XDS110 USB Debug Probe] Execute the command: %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity [Result] -----[Print the board config pathname(s)]------------------------------------ C:\Users\BRETT~1.WIN\AppData\Local\TEXASI~1\ CCS\ccs910\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 25 2019'. The library build time was '16:55:29'. The library package version is '8.4.0.00006'. 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]