AM263P4-Q1: DEBUGSSM_0: Error initializing emulator: (Error -260 @ 0x0) An attempt to connect to the XDS110 failed.

Hi Shilpa,

Thank you for reaching out and providing the screenshots. The error message and the "Found 0 devices" result from xdsdfu -e indicate that the XDS110 on-board debugger is not being recognized by your PC at the USB level. This is typically a prerequisite issue before firmware updates can even be attempted.

Please work through the following steps in order:

1. Verify USB Connection / Hardware

• Try a different USB cable — ensure it is a data-capable cable (not a charge-only cable). This is one of the most common causes.
• Try a different USB port on your PC (preferably a USB 2.0 port directly on the motherboard, avoiding hubs).
• Confirm the power LED on the AM263P4-LP LaunchPad is lit when connected.

2. Check Device Manager (Windows)

• Open Device Manager and look under:
  • Universal Serial Bus controllers
  • Other devices (may appear as unknown device with a yellow warning)
• If the XDS110 is not listed at all, it confirms a USB/hardware recognition issue.
• If it appears as an unknown device or with an error, try right-clicking and selecting Update Driver.

3. Try Installing / Reinstalling XDS110 USB Drivers

• Navigate to: C:\ti\ccs2050\ccs\ccs_base\common\uscif\xds110\
• Run xds110_drivers_install.bat (if present) or install drivers manually via Device Manager pointing to that directory.
• Alternatively, reinstall the drivers through CCS → Help → Install Drivers for XDS110.

4. Test on a Different PC

• If possible, connect the LaunchPad to a different computer to rule out a PC-specific USB/driver issue.

5. Board Inspection

• If none of the above resolves the issue, it is possible that the XDS110 on-board debugger has been damaged (e.g., due to ESD or a power issue). In that case, the board may need to be replaced.

Could you please let us know:

1. What OS and CCS version are you using?
2. Does the board appear anywhere in Device Manager?
3. Have you tried a different USB cable and port?

This will help us narrow down the root cause further.

Best Regards,

Zackary Fleenor

Hi Fleenor,

Thank you for your support. We followed all the steps you suggested, but unfortunately did not get any results.

The power LED is blinking, however the XDS110 debugger LED is not blinking, and the XDS110 is not appearing in Device Manager. We are using Windows 11, and the version of Code Composer Studio is 20.5.0.

Please let us know if there are any further steps we can try.

Best Regards
Shilpa

Hi Anand,

I connected with external adapter still debugger led not blinking and not detected 

Best Regards

Shilpa

Hi Shilpa,

Thanks for confirming this, can you provide feedback for the additional Q's below?

• Was this board ever successfully connected before, or is this a new out-of-box failure?
• Was any firmware update attempted through CCS that might have bricked the XDS110?
• Do you have access to an external XDS110 debug probe to verify the target MCU independently?
• What is the board revision and manufacturing date? (This helps check for known hardware batch issues.)

Best Regards,

Zackary Fleenor

Hey Shilpa,

Hi Shilpa,

Thank you for providing those details. Based on the full picture — the board initially worked, firmware updated successfully, but now the XDS110 debugger LED is off, the device is invisible in Device Manager, and xdsdfu -e finds 0 devices even after trying different cables, ports, PCs, and an external 5V/3A adapter — this strongly indicates the on-board XDS110 debugger hardware has failed [1][2].

I provided these instructions previously, but just in case, before concluding hardware failure, try this procedure which has recovered bricked XDS110 debuggers on other TI LaunchPads where the firmware became corrupted [1]:

1. Disconnect all cables from the LaunchPad.
2. Locate the TDO pin (Pin 97) of the XDS110 controller IC on your AM263P4-LP board — you'll need to reference the LaunchPad schematic for the exact test point or pad location on the PROC171A revision.
3. Ground the TDO pin by connecting it to any GND point on the board.
4. While TDO is grounded, connect the USB cable to the XDS110 USB port.
5. Keep grounded for ~5 seconds, then release. (Some cases require keeping TDO grounded through the entire process.)
6. Run xdsdfu -e to check if the device is now detected.
7. If detected: xdsdfu -f firmware_3.0.0.29.bin -r to reflash firmware.

Timing is sensitive — repeat the procedure several times if it doesn't work on the first attempt [1].

Immediate Workaround: Use Your External XDS110 Probe

Since you have an external XDS110 debug probe, you can bypass the failed on-board debugger entirely and continue development [3][4]:

• Connect the external XDS110 probe to the JTAG header on the AM263P4-LP board.
• Important: Ensure the probe's VTREF pin is connected to the target's 3.3V supply. Without this, you'll get an SC_ERR_XDS110_TARGET_SUPPLY error — the XDS110 requires sensing target voltage to set JTAG signal levels, and this check cannot be disabled in software [5][6].
• This will let you verify whether the target AM263P4 MCU itself is functional, which would confirm the issue is isolated to the on-board debugger.

If TDO Recovery Fails

The symptom pattern — debugger LED off, no Device Manager enumeration, no response to xdsdfu — consistently points to hardware damage when all cable/port/power variables have been eliminated [2]. In that case:

• Request a board replacement through your TI sales channel or distributor. You can initiate a return through TI's customer returns portal [2].

1. LAUNCHXL-F280039C: XDS110 bricked recovery via TDO pin grounding
2. TMDSEMU110-U: Debug probe does not enumerate — hardware failure and return process
3. AWR2944: Using external XDS110 debug probe to bypass onboard debugger
4. FAQ: AM26x device FAQs including XDS110/JTAG troubleshooting
5. IWR1443BOOST: XDS110 VTREF connection requirement
6. LP-XDS110: VTREF check cannot be disabled in software
7. AM263P4 Datasheet — Pin Configuration (TDO at ball C4)

Best Regards,

Zackary Fleenor