• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 54 subscribers
  • Views 98 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TMDSEMU110-U: TMDSEMU110-U programmer issuse

Deva sai kumar Peddiboina
Prodigy 10 points

Part Number: TMDSEMU110-U
Other Parts Discussed in Thread: RM48L540,

Dear TI Support Team,
Iam facing an issue with the TMDSEMU110-U programmer while working with the RM48L540 controller.

The programmer is not functioning with the RM48series  device. However, the same TMDSEMU110-U works correctly when used with ARM Cortex-M0 controllers, which indicates that the units are generally operational.

Additionally, I have observed this issue consistently across three of our existing programmers. Recently, we ordered two new TMDSEMU110-U units, and those are working fine with the RM48L540 under the same setup.

 

Could you please help identify the root cause and advise if there is any firmware update, configuration change, or known issue related to this behavior?

 

Looking forward to your support.

  • 0
    TI__Mastermind 31543 points

    Hello,

    A Few Things That Would Help Narrow This Down Further

    Before diving in, it would be useful to know:

    • What firmware version is currently on your three older TMDSEMU110-U units vs. the two new ones?
    • What version of Code Composer Studio (CCS) are you using?
    • What specific error messages or failure symptoms do you see when the older units attempt to connect to the RM48L540?
    • Have you ever run a firmware update on the older units through CCS or the standalone xdsdfu utility?

    That said, the pattern you describe — older units fail on RM48L540 but work on Cortex-M0, while newly purchased units work on both — points strongly to a single root cause.

    Root Cause: Outdated XDS110 Firmware

    The XDS110 is officially listed as a supported JTAG emulator for the RM48L540 [1], so there is no inherent hardware incompatibility. The XDS110 probe firmware is designed to be updated over time, and CCS automatically updates probe firmware [2] when connected — but only if you're running a sufficiently recent CCS version. Your newer units shipped with current firmware from the factory, which is why they work immediately.

    The RM48L540 uses an ICEPICK_C module to manage JTAG access [1] and has silicon-revision-specific JTAG ID codes [1] — both of which require up-to-date firmware and device support files to handle correctly. Simpler Cortex-M0 targets don't exercise these same code paths, which explains why your older probes still work with them.

    How to Fix This

    Step 1 — Update XDS110 Firmware via xdsdfu

    The XDS110 firmware can be updated using the xdsdfu utility [3] included with CCS:

    xdsdfu -e # List connected XDS110 probes and current firmware version
xdsdfu -m # Put the probe into DFU (Device Firmware Update) mode
xdsdfu -f firmware.bin -r # Flash new firmware and reboot
    xdsdfu -e # List connected XDS110 probes and current firmware version
xdsdfu -m # Put the probe into DFU (Device Firmware Update) mode
xdsdfu -f firmware.bin -r # Flash new firmware and reboot

    The firmware binary is located in your CCS installation directory under the ccs_base/common/uscif/xds110/ folder. Run this for each of your three older units.

    Step 2 — Update CCS and Device Support Packages

    Ensure you are running CCS v7.0 or later (required minimum for XDS110 [3]) — ideally the latest available version. Then:

    Step 3 — Verify the Connection

    If issues persist after the firmware update, use the dbgjtag diagnostic utility [3] to test JTAG scan path integrity:

    dbgjtag -S integrity

    This will test DR/IR scan paths and read the target IDCODE, confirming whether the probe can properly communicate with the RM48L540's JTAG interface.

    Summary

    Item
    Detail
    Root cause
    Outdated firmware on older XDS110 probes
    Why Cortex-M0 works
    Simpler JTAG topology; doesn't require ICEPICK_C handling
    Why new units work
    Shipped with current firmware from factory
    Fix
    Update firmware via xdsdfu, update CCS + device support packages
    Verify
    Use dbgjtag -S integrity to confirm JTAG connectivity

    After updating the firmware on your three existing units, they should behave identically to the two new ones. If the problem persists after the update, please share the exact error messages and firmware version numbers — that will help diagnose any remaining issues.

    Resources:

    1. RM48L540 Datasheet
    2. XDS110 Debug Probe User's Guide (SPRUH35)
    3. XDS110 JTAG Debug Probe User's Guide (SPRUI94)
    4. CCS Device Support Application Note (SPNA232A)

    Best Regards,

    Zackary Fleenor