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.

  • TI Thinks Resolved

Linux: XDS2xx unbrick procedure and some other questions.

Intellectual 420 points

Replies: 1

Views: 101

Tool/software: Linux

Hi experts,

  I use Linux host from 1994 and use TI products (DSP) from a couple of years, then I am not a newbie.


Two years ago I have bricked an XDS2xx Rev B used on a evaluation board C6657, today I have bricked
a second XDS2xx Rev C board used on EVMK2H, nothing is changed in this two years about that.

I suppose that the linux procedure to update that development tool is a "bit" wrong, I have found the warning
after done the update attempt.

1) Exist a procedure to repair the FW on that tool using (for example) a XDS100v3 board or other jtag emulator?
2) Why you don't insert an WARNING printout in cs_base/common/uscif/xds2xx/ReadMe.txt to avoid this behaviour?
3) Exists an HW compatibility list with DSP/CPU/eval <-> JTAG emulator <-> CCS version?
     (to be used for choice the compatible JTAG debugger)
4) With a special adapter (if exists) is usable the XDS100V3 version on TMS320C66AK2H14 (and now for
    TCI6636K2H mounted on EVMK2H evaluation board)?

Thank you for your answers.

I am sorry for my bad English.

Dario

  • Guru 145985 points
    Dario,

    Please apologize for the trouble. The C66x development boards were manufactured with a very old version of the XDS200 firmware which did not work reliably on Linux hosts. This was found some time after these boards were manufactured and therefore stock may still contain this version of the firmware.

    The procedure to update the firmware is documented on the reference below:
    software-dl.ti.com/.../emu_xds200.html

    Since you are past the point of updating the firmware via USB, the two threads below talk about the procedure to recover the bricked XDS200 using an external Debug Probe such as the XDS100v3:
    e2e.ti.com/.../580450
    e2e.ti.com/.../2181766

    Answering your questions:
    1) Please see above.
    2) Unfortunately very few people read the ReadMe.txt file and therefore such warning did not occur to be added. I will certainly ask the package providers to do so.
    3) The tab "Tools and Software" present on every device page contains the compatible products for it.
    Also, each debug probe product page has a compatibility list per device family and core - check the description named "Devices Supported" in a page for the XDS200, for example.
    www.ti.com/.../TMDSEMU200-U
    4) Specific adapters exist for resale. Check the table with several part number suggestions at:
    software-dl.ti.com/.../emu_jtag_adapters.html
    However, keep in mind the XDS100 Debug Probe is quite slow for the devices you are using. I personally woudl try to recover the original XDS200 following the procedure mentioned before.

    (your english is very good)

    Hope this helps,
    Rafael

    When posting, click on the link Insert Code, Attach Files and more... to attach images, files or use nice formatting.

    If my reply answers your question please click on the green button "This resolved my issue".

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.