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.

SEED-XDS560PLUS and CCS V5 experiences?



Hi,

Since there is no FAQ on the SEED homepage, I want to open a posting collecting experiences about the SEED XDS560PLUS emulator together with CCS V5. I dont know how many people do the same experiments to make jtags run, I think if 2 do it is a waste of time. I spent a lot of time searching for why it is not working by just blindly installing this and that in different combinations. Since I work with TI, Jtags are always a problem and its always fun to make them run again on a different PC.

*) install directory has to be CCSdirectory\ccsv5\ccs_base

If using CCS V5, the 'CCS V4 and above' driver http://www.xds560.com/drivers.php has to be used. it is essential to manually select in the CCS V5 install directory ccsv5\ccs_base.

*) use in CCS V3 before CCS V5

In my case I have to use the XDS560 Jtag in CCS V3.3 once before it will work in CCS V5. I dont know where this comes from, but I dont get a connection in CCS V5 to the emulator (without any errormessage) unless I connect once in CCS V3

*) conflict with other XDS560 jtag

if CCS V5 is installed, use 'custom' and deselect TI XDS560 driver. If this is installed, the SEED Jtag will simply not work. You will get 'unable to connect Jtag' without any other help. In my case the SEED XDS560 has to be the only XDS560 Jtag emulator in the windows device manager section "Texas Instruments Emulators"

*) anyone has a list what the error message numbers mean?

sometimes I get error -2083:

bye,

Thomas

  • I had all kinds of problems, there was some support from Seed but that has dried up.

    I am left with 2 problems

    - Many-many blue screens - You must find a very good very short USB cable but you will still die regularly especially when resetting the emulator if anything unusual like a power cycle happens on your target.

    - Unsigned drivers, I use win7 64 bit which insists on signed drivers, seed seem unable to do this, they suggest you press f8 on every boot and go thru the menus to enable unsigned drivers. I put windows in test mode and signed them myself, but this means you have to deal with occaisonal repairs putting the unsigned drivers back.

    It is also a bit irritating that the debug tools for this extend to just an app to ask the version number.

    I know seed monitor this forum, perhaps they will at least sign the drivers.

    Chris

  • Still no signs of life from seed support, windows has a nice reliability report, this is what my graph looks like.

     

  • Still no signs of life from Seed DSP support...

  • New drivers have turned up, signed and so far more stable...