• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 53 subscribers
  • Views 1556 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.

Open XDS110 design file?

Robert Chen
Mastermind 9135 points

Other Parts Discussed in Thread: CC2640

The performance of XDS110 on CC2640 DevPack is better than XDS100v3. I am wondering if TI have any plan to release the design files of XDS110 so that we (users) can make a standalone XDS110 debugger by ourselves?

XDS100v3's performance is just not good enough. When I used it almost every day, I feel frustrated while waiting for the CCS UI to update stepping info. I know it is due to the bad throughput of XDS100v3.

A robust debugger is very important for embedded system development. Instead of using XDS110 on DevPack by jumping wires to my target boards, I would like to make a standalone XDS110 debugger if TI can release design files.

  • 0
    Guru 735695 points
    Hi Robert,
    You can find XDS110 design files at www.ti.com/.../cc-devpack-debug
  • 0 in reply to YiKai Chen
    TI__Guru** 106705 points
    Hi Robert and Yikai,

    I would rather recommend looking at the LaunchPad design files, as this has been designed to work as a stand-alone debugger also. www.ti.com/.../swrc319

    In fact, you can simply buy LaunchPads and use them as debuggers.

    Cheers,
    Fredrik
  • 0 in reply to Fredrik K
    Guru 735695 points
    Yes, use CC26xx LaunchPad as debugger works too.
  • 0 in reply to YiKai Chen
    Mastermind 9135 points

    Thanks YiKai & Fredrik,

    I have the schematic of both DevPack and LaunchPad. The schematic is no problem. My point is to design a rigid/robust standalone debugger like XDS100/XDS200. So far, if we use DevPack/LaunchPad to debug customized boards then we have to jump wires. This is not a robust way. In my past experience, these wires are very easy to fail without notice. So, I prefer a robust cable with standard TI-14 or cTI-20 header.

    In fact, I have designed my own 4-pin & 8-pin adaptors with 1.27mm pin-pitch to be used with XDS100v3. For my XDS100v3, I also print a housing to protect it since it is bare board from SpectrumDigital. It is risky for debuggers without housing since the debugger may get damaged by ESD or shorted with target boards.

    The purpose of DevPack and LaunchPad is to provide a way for beginners to get started with the lowest cost. The intention is good. But when talking about serious project development, I prefer to make everything robust. I can't imagine what will happen if the debugger is damaged and the project schedule is very tight. My customer will probably kill me.

    So, my plan is to design a stand-alone XDS100 debugger with cTI-20 header. I know how to design the schematic but I will need the firmware for TM4C which is not provided in TI website. For XDS100v3, all the design files including firmware are provided.

  • 0 in reply to Robert Chen
    TI__Guru** 106705 points
    Hi Robert,

    The DevPack Debug has been designed only to work with the SensorTag which is why you need to modify it to work as a stand-alone debugger.

    The LaunchPad however is specifically designed to be able to debug external targets. It has a dedicated 10-pin Cortex Debug connector with ESD protection for this purpose, and it also has level shifters so you can run your target board at different voltages.

    If we were to make a dedicated XDS110 debugger, it would not be designed differently than the current LaunchPad. For development I am not sure what else you need. If you are worried about a debugger breaking, buy one more and keep as back-up.

    As for the XDS FW question, I recommend that you post on the CCS forum as they are the experts on this.

    Cheers,
    Fredrik
  • 0 in reply to Robert Chen
    Intellectual 455 points
    I personally just use a DevPack Debug to debug my custom board. You can do this pretty nicely if you use pin headers with the same footprint and pin assignments as the Sensortag.
  • 0 in reply to Fredrik K
    Mastermind 9135 points
    Hi Fredrik,

    I will leave a post in CCS forum.
  • 0 in reply to Venemo
    Mastermind 9135 points
    Hi Venemo,

    Thanks for your comment.

    Several months ago, I have a project which needs the debugger to be attached on a machine. So, the debugger is hanging in the air and it could touch the metal part of the machine. For development on desktop, there is usually no problem. For debugging industrial products, I prefer a robust way.

    I TI CCS team won't release XDS110 TM4C firmware, I might need to print a housing for DevPack and make a robust cable & header for it.