https://e2e.ti.com/support/site-support-group/site-support/The central location for the latest E2E news, training, feature updates, member feedback and E2E specific site support.en-USTelligent Community 13https://e2e.ti.com/support/site-support-group/site-support/f/site-support-forum/1642582/xds110iso-evm-xds110-debugger-unable-to-program-debug-mcu/6340766Mon, 11 May 2026 22:36:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:9ef1b70e-d037-420e-9cbf-223dde28bf71FleenorHi Sandeep, I understand you've exhausted the standard troubleshooting steps and are now requesting RMA guidance. Before concluding the debugger is defective, there are a few final diagnostic tests that can definitively confirm hardware failure—and one critical piece of information is still missing that could change the diagnosis entirely. Critical Missing Information What specific error message or error code does CCS display when the connection fails? This is essential. The error message differentiates between a configuration issue (fixable) and hardware failure (requires RMA). For example, "SC_ERR_PATH_BROKEN" points to a scan path issue, while a timeout error suggests different root causes [1]. Without this, we cannot definitively rule out a software/configuration problem. Final Diagnostic Tests Before RMA 1. Verify Firmware Version Output Run the following from a command prompt: cd [CCS_INSTALL_DIR]\ccs\ccs_base\common\uscif\xds110 xdsdfu -e Share the exact firmware version reported. A known issue exists where firmware v2.3.0.16 (installed by EMUPack 8.0.903.4) breaks connectivity even when the debugger appears functional on the PC [2]. If you have this version, update CCS via Help → Check for Updates to get firmware v2.3.0.18 or later [3]. 2. Measure Power Test Points on XDS110ISO-EVM Using a multimeter, measure the following test points on the board (all referenced to ground at TP5 ) [4]: Test Point Expected Voltage Tolerance TP3 (+5V0) 5.0V ±10% TP4 (VCC_3V3) 3.3V ±10% TP2 (DAC reference) 4.0V ±10% TP6 (+5V0_A) 5.0V ±10% If any of these voltages are out of spec, it confirms the internal power architecture (TLV70333DBVR LDO or LM4120IM5-4.1 reference generator) has failed—definitive evidence of hardware damage [4]. 3. Firmware Recovery Attempt (Final Software Test) If the debugger's emulation controller firmware was corrupted during the initial update, it can appear detected but fail to communicate with targets. Try the recovery procedure [5]: Disconnect all cables from the XDS110ISO-EVM Ground the TDO pin (Pin 97 of the TM4C1294NCPDT on the bottom side of the board) to any ground point While TDO is grounded, connect the USB cable Keep grounded for ~5 seconds, then release Run xdsdfu -e — if the debugger enters DFU mode, reflash with: xdsdfu -c 1 -f firmware_3.0.0.29.bin -r If this recovery fails (debugger doesn't enter DFU mode), it strongly indicates hardware failure. 4. Cross-Test with a Known-Good Target If possible, test the XDS110 with a different CC2340R5 board (or any other TI MCU target) to isolate whether the failure is debugger-side or target-side. Similarly, if you have access to another XDS110 (e.g., from a LaunchPad), try connecting it to your CC2340R5 target board. Regarding RMA/Replacement The standard path is: If purchased directly from TI: Contact TI support through ti.com/support with your order number, the test point voltage measurements above, and the CCS error message as evidence of hardware failure. If purchased through a distributor: Initiate the return through that distributor's RMA process. Provide the voltage measurements and firmware recovery results as diagnostic evidence—TI support will typically require this before approving a replacement. To help refine this recommendation, it would be helpful to know: The exact error message/code shown in CCS during the connection attempt The output of xdsdfu -e (current firmware version) Voltage measurements at TP2, TP3, TP4, and TP6 LED status (D1–D4) on the XDS110ISO-EVM during connection attempts Whether you've tested the debugger with any other target board Which connector (J1 or J3) and adapter you're using XDS110 Connection Issues - SC_ERR_PATH_BROKEN EMUPack 8.0.903.4 Incompatibility Advisory EMUPack Fix Confirmation - Firmware v2.3.0.18 XDS110ISO-EVM User's Guide - Power Test Points XDS110 Firmware Recovery Procedure JTAG Debug Probe Troubleshooting Flow Best Regards, Zackary Fleenorhttps://e2e.ti.com/support/site-support-group/site-support/f/site-support-forum/1642582/xds110iso-evm-xds110-debugger-unable-to-program-debug-mcu/6339257Mon, 11 May 2026 05:46:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:e77483cf-f71f-45bf-ae9b-81fb548f3055Sandeep KumarHi, Thank you for the detailed troubleshooting guidance. We are using the following setup: Target MCU: CC2340R5 IDE: Code Composer Studio v12.0.2 Debugger: XDS110 / XDS110ISO-EVM Interface: SWD/JTAG connection to target board Target Supply: Target board is powered externally, and VTRef is available to the debugger We have already verified the suggested points: XDS110 detection on PC The debugger is detected by the PC, and the COM/debug ports are visible. Firmware check/update We checked the XDS110 firmware using the xdsdfu utility. The debugger firmware update process was completed successfully. Hardware connection VTRef, GND, TMS/SWDIO, TCK/SWCLK, and nRESET connections were checked. We also verified the adapter wiring and connector orientation. CCS target configuration The target configuration was checked for CC2340R5, and the correct debug probe and connection settings were selected. Target board condition The target board supply is stable, and the MCU power pins are getting the required voltage. We also checked the reset line condition. Even after completing the above checks, the debugger is still not able to connect, debug, or flash the HEX file into the CC2340R5 MCU . Since the debugger is detected by the PC but fails during target connection/programming, we suspect that the debug interface hardware of the XDS110 may be damaged or not functioning properly. Kindly support us with the next step for debugger replacement/RMA process , or please suggest any final diagnostic test that can confirm the debugger hardware failure. Regards, Sandeep Kumarhttps://e2e.ti.com/support/site-support-group/site-support/f/site-support-forum/1642970/tps53318-technology-process-for-tps53318/6335525Thu, 07 May 2026 00:13:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:7b1d1c48-f292-49d3-91b1-61eb83f2c218Calan ElayaHello, For this device, it was 150nm process node. Thank you, Calanhttps://e2e.ti.com/support/site-support-group/site-support/f/site-support-forum/1642675/cd74hc4016-cd74hc4016pw-lot-differences/6335474Wed, 06 May 2026 22:37:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:559fed42-8928-47ae-9252-f02e51fd32baAidan SinghI see. I've looked up both lot numbers and both were made at the same fab with the same die, so I am unsure why there is a difference. I also find it odd that the new lot requires -0.1 V to turn off. Would you be able to send me a graph showing at exactly what voltage the switch turns off and on? This device should be turning off when nE is 0.5 V, 1.35 V, or 1.8 V depending on the VCC.https://e2e.ti.com/support/site-support-group/site-support/f/site-support-forum/1642984/tps53318-technology-process/6335327Wed, 06 May 2026 20:10:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:304a22eb-b256-4eee-a977-730f722931a7Calan ElayaHello, For this device, it was 150nm process node. Thank you, Calanhttps://e2e.ti.com/support/site-support-group/site-support/f/site-support-forum/1642675/cd74hc4016-cd74hc4016pw-lot-differences/6334663Wed, 06 May 2026 12:56:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:0ea3ea92-76b1-418f-ab18-70a82db9ef46E PAidan, Your first statement is correct the switching for the 2 lots happens at slightly different voltages. This is not violating anything with the stated voltages on the Datasheet but for our design it makes a difference. Thank you Ehttps://e2e.ti.com/support/site-support-group/site-support/f/site-support-forum/1642984/tps53318-technology-processWed, 06 May 2026 09:57:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:82865672-4249-4331-8aa2-794195bd967dDan BarrPart Number: TPS53318 What was the technical process node use to manufacure the TPS53318. Jejomar Ildefonso of the Texas Instruments | Customer Support Center suggested I direct this question to this E2E forum support form. Specifically, what was the smallest processing node used to produce these Power BiCMOS devices.tps53318https://e2e.ti.com/support/site-support-group/site-support/f/site-support-forum/1642970/tps53318-technology-process-for-tps53318Wed, 06 May 2026 09:39:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:1ed13e0f-846a-44d4-bac3-8ad56273b533Dan BarrPart Number: TPS53318 What was the smallest technical process node (Jejomar's response showed "multiple") used to manufacure the TPS53318. Jejomar Ildefonso of the Texas Instruments | Customer Support Center suggested I direct this question to this E2E forum support form.tps53318https://e2e.ti.com/support/site-support-group/site-support/f/site-support-forum/1642675/cd74hc4016-cd74hc4016pw-lot-differences/6333601Tue, 05 May 2026 19:21:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:07d84b8e-67c0-416a-9a73-7f80f33a04b9Aidan SinghHello, I'm having trouble understanding what you mean. Do you mean the required nE voltages to turn the switch off are 0.2 V and -0.1 V, for D1J4 and A37R marked muxes respectively? Or are you saying when the mux is switched on, that the output pins are at a different voltage than expected? Thank you, Aidanhttps://e2e.ti.com/support/site-support-group/site-support/f/site-support-forum/1642675/cd74hc4016-cd74hc4016pw-lot-differencesTue, 05 May 2026 14:59:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:df535ca8-5a8d-4265-b7e9-f200b83f4045E PPart Number: CD74HC4016 Hello, We have used CD74HC4016PW for many years and it has worked fine, lately we have seen that the switches are not switching to an as low of a voltage as they used to. The switching voltage at pins 13, 5 and 6 has not changed. We were able to track it down to lot numbers, for example parts with marking number D1J4 works and switches at the voltages that has always switched around 0.2V , but parts with marking numbers A37R do not switch at the typical voltage and require a much lower voltage to switch almost -0.1V. Have there been any changes between the 2 lots? We might still be able to use the newer lots but I am trying to figure out a root cause. Any help would be appreciated. Thank youCD74HC4016https://e2e.ti.com/support/site-support-group/site-support/f/site-support-forum/1642582/xds110iso-evm-xds110-debugger-unable-to-program-debug-mcu/6333160Tue, 05 May 2026 13:40:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:00bbfcaf-b238-4f59-b0fc-9e6f00275447FleenorHi Sandeep, To provide targeted guidance, please share: Which specific MCU/target device are you trying to program (e.g., C2000, MSP432, Sitara, CC series)? What error message appears in CCS when you attempt to connect? (e.g., "SC_ERR_PATH_BROKEN", connection timeout, etc.) Which connector are you using on the XDS110ISO-EVM — the 16-pin isolated connector (J3) or the 120-pin non-isolated connector (J1)? Which adapter board (10-pin, 14-pin, or 20-pin) are you using to connect to your target? Troubleshooting Steps Even without the specifics above, this is a well-documented failure pattern. Since your XDS110 is detected on the PC but cannot connect to the target, the issue is almost certainly hardware configuration, firmware incompatibility, or CCS target configuration — not a driver problem. Here's a systematic approach: 1. Verify XDS110 Firmware Version Open a command prompt and navigate to your CCS installation directory: cd C:\ti\ccs \ccs_base\common\uscif\xds110\ xdsdfu -e Check the reported firmware version. A known issue exists where certain EMU pack versions install incompatible XDS110 firmware that breaks connectivity [1]. If your firmware is v2.3.0.16, it's the problematic version. Fix: In CCS, go to Help → Check for Updates and install the latest EMU pack. This will automatically update the XDS110 firmware to a compatible version (v2.3.0.18 or later) [2]. 2. Verify Hardware Configuration on XDS110ISO-EVM The XDS110ISO-EVM has critical switches and connectors that must be set correctly [3]: Component Purpose Action Required S1 (JTAG/cJTAG switch) Selects debug protocol Must match your target MCU's protocol S2 (SPI/UART switch) Routes serial signals Set according to your use case Connector selection Isolated (J3, 16-pin) vs. Non-isolated (J1, 120-pin) Use only one; match your adapter VTRef Target voltage reference Your target board must supply VTRef to the debugger 3. Verify Adapter Board Wiring If using an adapter board (10-pin, 14-pin, or 20-pin), confirm correct pinout — particularly VTRef and GND connections . Incorrect wiring of these is a common cause of programming failure [3]. 4. CCS Target Configuration In your .ccxml target configuration file: Open the Advanced tab Set the correct JTAG/SWD/cJTAG Mode for your target MCU [4]: For 4-pin JTAG targets: select "JTAG (1149.1), SWD and cJTAG are disabled" For cJTAG targets (e.g., C2000): select "cJTAG (1149.7) 2-pin advanced modes" with OSCAN2 format 5. Firmware Recovery (If Debugger Is Bricked) If the above steps don't work and the debugger appears unresponsive, a firmware recovery procedure exists that involves grounding the TDO pin during power-up and manually reflashing using xdsdfu [5]. To Help Refine This Recommendation, It Would Be Helpful to Know: Current XDS110 firmware version (output of xdsdfu -e ) Your CCS version and installed EMU pack version Current position of mode switches S1 and S2 on the XDS110ISO-EVM Whether your target board is powered and providing VTRef voltage Status of LED indicators (D1–D4) on the XDS110ISO-EVM during connection attempts The specific error message shown in CCS EMUPack 8.0.903.4 incompatibility advisory EMUPack fix confirmation XDS110ISO-EVM User's Guide F29H85x LaunchPad FAQ - CCS Target Configuration XDS110 Firmware Recovery Procedure Best Regards, Zackary Fleenorhttps://e2e.ti.com/support/site-support-group/site-support/f/site-support-forum/1635000/lmh13000rqeevm-lmh13000rqeevm-connections/6333060Tue, 05 May 2026 11:41:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:acb7a620-906b-49b9-9427-785c8e7d70adAnant SinhaShilpa, I have shared the Iout noise plot to you over email. Please let me know if you have any query. Regards Ananthttps://e2e.ti.com/support/site-support-group/site-support/f/site-support-forum/1642582/xds110iso-evm-xds110-debugger-unable-to-program-debug-mcuTue, 05 May 2026 10:01:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:b7a1b1c3-a3cf-49a9-a2ed-322ba711c20cSandeep KumarPart Number: XDS110ISO-EVM Other Parts Discussed in Thread: CC2340R5 , TM4C1294NCPDT Dear TI Support Team, We recently purchased an XDS110 debugger . When we connected it to the PC for the first time, it prompted for a firmware update. We completed the firmware update successfully. After the update, the debugger is detected on the PC and appears in the port/device list. However, we are unable to program or debug the MCU using this XDS110 debugger. Please support us in resolving this issue. Kindly let us know if any driver, firmware recovery, CCS configuration, or hardware check is required. Issue summary: Debugger: XDS110 Firmware update completed successfully Device is detected on PC / port list Unable to program or debug the MCU MCU/toolchain used: [mention] Please guide us with the next troubleshooting steps.power deliveryTM4C1294NCPDTXDS110ISO-EVMCC2340R5https://e2e.ti.com/support/site-support-group/site-support/f/site-support-forum/1641829/arm-cgt-requesting-access-to-arm-cgt-compiler-version-5-2-9/6331024Fri, 01 May 2026 18:09:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:c252992d-abce-43d1-a8aa-1696e8822149George Mock[quote userid="697470" url="~/support/site-support-group/site-support/f/site-support-forum/1641829/arm-cgt-requesting-access-to-arm-cgt-compiler-version-5-2-9"]My team is in need of the ARM-CGT Compiler version 5.2.9, but the download page for it shows no files to download.[/quote] It is still available for external download from here . Thanks and regards, -Georgehttps://e2e.ti.com/support/site-support-group/site-support/f/site-support-forum/1641829/arm-cgt-requesting-access-to-arm-cgt-compiler-version-5-2-9Thu, 30 Apr 2026 08:30:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:522c1a49-6371-4e9b-8bf1-f85acaa12756Runar SaurePart Number: ARM-CGT Hello! My team is in need of the ARM-CGT Compiler version 5.2.9, but the download page for it shows no files to download. Is it still possible to get access to this version of the tools, preferably Linux version?ARM-CGThttps://e2e.ti.com/support/site-support-group/site-support/f/site-support-forum/1633032/tmdscncd28379d-connecting-the-control-card-to-a-custom-made-board/6328840Wed, 29 Apr 2026 21:45:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:8450b890-b34e-4f57-ad1b-9b9b3965adcaStevan DuraskovicPer data sheet page 50, TMS320F2837xS Real-Time Microcontrollers datasheet (Rev. K), Max is 3.47Vhttps://e2e.ti.com/support/site-support-group/site-support/f/site-support-forum/1633032/tmdscncd28379d-connecting-the-control-card-to-a-custom-made-board/6328695Wed, 29 Apr 2026 20:00:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:4739d1ef-b270-4bbe-95c4-119f8c99e860Neetusha KalarikkalHi, Thank you so much. I have a follow up question. What is the maximum analog voltage allowed. I assume it is 3.3 V. Thank you.https://e2e.ti.com/support/site-support-group/site-support/f/site-support-forum/1639025/lm117hvqml-check-lead-post-gold-plating-thickness-of-the-below-pn/6328500Wed, 29 Apr 2026 17:50:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:68598b0b-7683-420f-bfdd-c6ea166bf6fbAden TaylorHi Pooi, For LM137H/883 and LM117H/883, the gold plating spec requirement is at minimum 30µ. For LM137H, the gold plating spec requirement is at minimum 50µ Best, Adenhttps://e2e.ti.com/support/site-support-group/site-support/f/site-support-forum/1639635/wilink-hw-design-review-git-clone---not-all-4-clone-options-are-working-anymore/6328281Wed, 29 Apr 2026 15:25:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:f6a2e32b-3f21-4606-ad2f-025dd77567efMatthias ProskeThank you for feedback.https://e2e.ti.com/support/site-support-group/site-support/f/site-support-forum/1635589/lm117hvqml-request-lead-post-gold-plating-thickness-for-utas50-00083-000-and-utas50-00082-000/6327226Tue, 28 Apr 2026 23:45:00 GMTcb01d8b2-d089-468d-babb-77d1d8683490:96672ad5-f379-4447-8d83-6d7617634558Gregory ThompsonHi Sinlin, Thank you for asking us! Unfortunately I cannot locate the lead post plating thickness of the LM137H or LM117H and am reaching out to the packaging team for more information Best, Gregory Thompson