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.

Cannot create target for TMDSDSK6416-T using CCS v5.2 on Linux

I want to use the TMDSDSK6416-T from Spectrum Digital with TI Code Composer Studio (CCS) v5.2 on Linux. When I create a new target configuration in CCS and select "Spectrum Digital XDS510USB Emulator", there is no option for the C6416-T chip, so I have been unable to compile for the target. Is this configuration supported on Linux? Where do I find instructions and drivers to do this?

  • Hi David

    David Diel said:
    I want to use the TMDSDSK6416-T from Spectrum Digital with TI Code Composer Studio (CCS) v5.2 on Linux.

    Sorry, C641x is currently not supported on Linux Host:

    http://processors.wiki.ti.com/index.php/Linux_Host_Support#Supported_ISAs_.2F_Device_families

    We do have some tentative plans to support 6416 in the future but I don't have a clear date on when this would happen.

    Thanks

    ki

  • ki,

    For the Windows version of CCS v5, does it matter whether we use Windows 7 or Windows 8? Does it matter whether we use a 32-bit or 64-bit installation?

    David

  • David Diel said:
    For the Windows version of CCS v5, does it matter whether we use Windows 7 or Windows 8?

    CCSv5 officially supports Windows 7 but not Windows 8 (though CCSv5.3 should work). CCSv5.4 will officially support Windows 8.

    David Diel said:
    Does it matter whether we use a 32-bit or 64-bit installation?

    No. CCSv5 fully supports 32 and 64 bit Windows.

    Thanks

    ki

  • ki,

    Now we have CCSv5 running on Windows XP. The Spectrum Digital DSK diagnostic utility runs and the board passes tests. However, when trying to debug using the XDS510USB Emulator (DSK6416) target configuration, I get the message: "Error initializing emulator."

    Do you have any idea why this is not working?

    On a related note, is Windows XP fully supported?

    David

  • If all the SDConfig emulator tests are passing then it looks like CCS is having problems accessing the emulator. Sometimes I get this and a simple PC reboot will clear this up. If that doesn't, try using a new clean workspace.

    Also note that the 6416DSK has an on-board emulator which I believe is the default. You may have to play around with the switches on your board to use an external emulator. I've run into this with some of their other DSKs. Check the documentation for your board:

    http://c6000.spectrumdigital.com/dsk6416/V3/docs/dsk6416_TechRef.pdf

    Thanks

    ki

  • Hi,

    David Diel said:

    Now we have CCSv5 running on Windows XP. The Spectrum Digital DSK diagnostic utility runs and the board passes tests. However, when trying to debug using the XDS510USB Emulator (DSK6416) target configuration, I get the message: "Error initializing emulator."

    Just a remark: for embedded emulators you must select the embedded emulator, and not the XDS510USB:

    Hope this helps,

    Rafael

  • Hi Rafael,

    Thank you for suggesting the Spectrum Digital DSK-EVM-eZdsp onboard USB Emulator. However, with that configuration, I received the same error.

    David

  • David,

    I am almost positive you tried that already, but can you try switching the USB port you are using? I've seen sometimes the emulator JTAG device drivers be somewhat finicky about the USB port... Actually it just happened in my Windows 8/64 laptop.

    Also, when you are connecting, do you see a small dialog box pop up at the bottom right of the screen? This is exclusive to SD XDS510USB emulators and indicates the device driver is at least properly found (other errors may come up after that, but this at least may indicate some progress).

    Unfortunately my C6416T DSK decided to give up a few months ago, but I tested with my DM6437 EVM and it worked well.

    Regards,

    Rafael

  • Rafael,

    It was the USB port! I don't know why, but switching to another USB port solved the problem. This seems like a bug, but at least I have a workaround.

    Thanks!

    David