• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 747 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.

How do I read the IDCODE? (absolute beginner)

Chris Roberts
Intellectual 305 points
Other Parts Discussed in Thread: TMS320C6416

Let me start by saying I have never touched any type of DSP/FPGA or anything like that so I have no idea what I'm doing.  Though I have been reading a lot and really just used this forum as a last resort since I have a feeling this question is simple.

I have a TMS320C6416 DSK and am using it for practice.  It has a on board XDS560 and I have an extra XDS100v2.  I have successfully got it working with CCS v5.3.0.

So, all I want to do is get the IDCODE for the devices attached to the JTAG pins.  Please help me out.

  • 0
    TI__Guru* 84110 points

    Chris,

    Welcome to the TI E2E forum. I hope you will find many good answers here and in the TI.com documents and in the TI Wiki Pages. Be sure to search those for helpful information and to browse for the questions others may have asked on similar topics.

    Are you sure there is an on-board XDS560, or just that there is an on-board emulator? Depending on the board vendor, there may be different emulators on the board. But it probably does not matter.

    Why do you want to get the IDCODE for the devices attached to the JTAG pins? For programming the DSP or using the DSK, there is no need to know anything about the JTAG scan chain or its components. I have been using these DSP for many years and have never needed to do this and have never seen anything to tell me how to do it.

    If you want to become a JTAG scan chain expert, then TI is probably not the best place to be looking for that information since we are users of IEEE 1149.1 and not in the business of documenting the details of that standard. We do have JTAG emulation documentation, but it is from the point-of-view of the programmer and board designer. Go to the TMS320C6416 Product Folder to look for those documents (search for JTAG on the page).

    Otherwise, you may be best served by going to the IEEE website and looking for their documentation on the 1149.1 standard.

    Regards,
    RandyP

  • 0 in reply to RandyP
    Intellectual 305 points

    Randy,

    Thanks for getting back with me.  I basically want to be able to read the IDCODE for the device on this dev kit just as a practice.  My absolute goal is to connect to a JTAG header on a PCB with unknown components and be able to find out what devices are attached to it (manufacturer and device family or part number).  It seems that should be possible, just don't know where to start really. 

    >Are you sure there is an on-board XDS560, or just that there is an on-board emulator?

    I'm not sure, but I also have a stand-alone XDS100v2.


    I guess I was just hoping that CCS could report the IDCODE of the TI chips.  If not that's fine, I just have to find a tool that lets me perform a JTAG scan chain (and since I'm so new, googling the right lingo can be difficult, but I'm getting better :)

    Thanks again,

    -Chris

  • 0 in reply to Chris Roberts
    TI__Guru* 84110 points

    Chris,

    What you are looking for is outside the scope of this forum, or at least what support can be offered by TI.

    CCS does not have this capability.

    My recommendations are:

    1. Work with the vendor of JTAG emulators to see if they support boundary scan with their emulators. TI does not offer that support as a standard software or tool product.

    2. Go to the web and search for "jtag test equipment" or "jtag boundary scan" or "ieee 1149.1" (no quotes needed) to find companies that offer boundary scan products you could look at. I noticed a TI JTAG Testability Primer that you might find interesting.

    3. Go to ieee.org and find the 1149.1 standard's documentation.

    Regards,
    RandyP

  • 0 in reply to RandyP
    Intellectual 305 points

    I think you are probably right.


    Thanks.