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.

This error is usually reported when the JTAG signals are not connected correctly, though the error can also be caused by poor signal quality.

This also occurs if the debug probe is using a 4-pin JTAG when TDI and TDO are used as general-purpose inputs - outputs (GPIO) at runtime.

This can also occur if pullup or pulldown resistors are too strong, so try removing them when debugging.

This error sometimes occurs if the device is not booting correctly. Watch the power rails and XRSn with an oscilloscope to make sure that the device boots correctly and XRSn goes high. XRSn periodically rebooting is expected on unprogrammed devices due to the watchdog.

See the buffered case section of the hardware design guide.

Error connecting to the target: (Error -1015 @ 0x0) Device is not responding to the request. Device may be locked, or the debug probe connection may be unreliable. Unlock the device if possible (e.g. use wait in reset mode, and power-cycle the board.) If error persists, confirm configuration and/or try more reliable JTAG settings (e.g. lower TCLK).

1. Verify that Test Connection in the target configuration passes. If the connection fails, follow the steps for that error code.

2. Set device to wait-boot mode.

3. Follow the Manual Launch instructions and connect to the device.

4. Verify that you are able to read PARTID in the memory browser.

5. Try again to program the device.

6. If applying these steps still fails to clear the error, check the following: Are there password locations on the device? On-chip flash tool settings? Is it possible to program RAM only?

Error connecting to the target: (Error -151 @ 0x0) 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.

(Emulation package 8.0.903.2)

1. Check the target configuration file to make sure that the correct debug probe is selected.

2. Check to see if debug probe is visible in PC device manager.

3. Try replacing the USB cable, or try a different debug probe to make sure the probe in use is not damaged.

Trouble Reading Register PC: (Error -1156 @ 0x0) Device may be operating in low-power mode. Do you want to bring it out of this mode? Choose 'Yes' to force the device to wake up and retry the operation. Choose 'No' to retry the operation without waking the device.

1. Verify that Test Connection in the target configuration passes. If the connection fails, follow the steps for that error code.

2. Set device to wait-boot mode.

3. Follow the Manual Launch instructions and connect to the device.

4. Verify that you are able to read PARTID in the memory browser.

5. Try again to program the device.

6. If applying these steps still fails to clear the error, check the following: Are there password locations on the device? On-chip flash tool settings? Is it possible to program RAM only?

C28xx_CPU1: Error: (Error -1044 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation.

Try power cycling the debug probe without power cycling the target MCU. Try more reliable JTAG settings like lower clock frequency.

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 error is typically reported when the JTAG signals have poor signal quality. Try lower TCK frequency and check trace lengths.

See the buffered case section of the hardware design guide.

C28xx_CPU1: Trouble Setting Breakpoint with the Action "Continue or Finish Stepping" at 0x83146: (Error -1066 @ 0x83146) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 9.13.0.00201) C28xx_CPU1: Breakpoint Manager: Retrying with a AET breakpoint

For some devices, only one breakpoint is allowed when running code from flash since hardware breakpoints must be used. Check the device data sheet for the number of hardware breakpoints.

Error Initializing Emulator: (Error -2083 @ 0x0) Unable to communicate with the debug probe. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation.

1. Check the target configuration file to make sure that the correct debug probe is selected.

2. Check to see if debug probe is visible in the PC device manager.

3. Try replacing the USB cable, or try a different debug probe to make sure the probe in use is not damaged.

Error connecting to the target: (Error -2131 @ 0x0) Unable to access the device register. Reset the device, and retry the operation. If error persists, confirm configuration, pwer-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).

1. Verify that Test Connection in the target configuration passes. If the connection fails, follow the steps for that error code.

2. Set device to wait-boot mode.

3. Follow the Manual Launch instructions and connect to the device.

4. Verify that you are able to read PARTID in the memory browser.

5. Try again to program the device.

6. If applying these steps still fails to clear the error, check the following: Are there password locations on the device? On-chip flash tool settings? Is it possible to program RAM only?

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

The value is '-242' (0xffffff0e).

The title is 'SC_ERR_ROUTER_ACCESS_SUBPATH'.

The explanation is: A router subpath could not be accessed.

The board configuration file is probably incorrect.

1. Check the target configuration file to make sure that the correct debug probe is selected.

2. Check to see if the debug probe is visible in the PC device manager.

3. Try replacing the USB cable, or try a different debug probe to make sure the probe in use is not damaged.

Error connecting to the target: (Error -267 @ 0x0) The controller could not detect valid target supply. JTAG connection and/or connection setting specifying voltage level.

This error message only happens if the VTREF pin on the debug probe is not connected to 3.3V. Make sure that the target board is powered on.

C28xx: Failed CPU Reset: (Error -1137 @ 0x0) Device is held in reset. Take the device out of reset, and retry the operation.

1. Verify that Test Connection in the target configuration passes. If the connection fails, follow the steps for that error code.

2. Set device to wait-boot mode.

3. Follow the Manual Launch instructions and connect to the device.

4. Verify that you are able to read PARTID in the memory browser.

5. Try again to program the device.

6. If applying these steps still fails to clear the error, check the following: Are there password locations on the device? On-chip flash tool settings? Is it possible to program RAM only?

The JTAG IR Integrity scan-test has failed.

The JTAG DR Integrity scan-test has failed.

This error is reported when the JTAG signals have poor signal quality. Try lower TCK frequency and check trace lengths.

See the buffered case section of the hardware design guide.