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.

CCS/TMDSEVM6657: On board emulator does not connect

Part Number: TMDSEVM6657

Tool/software: Code Composer Studio

I have recently purchased the TMDSEVM6657LS. When I tried to connect to the processor through the on-board emulator, it just will not connect. I tried following the debugging guide and it led me to the following step where I need to update the emulator fw.

https://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_xds200.html#updating-the-xds200-firmware

The query command came back with proper info but the update step failed.

So how should I proceed in this case.

Thanks.

  • Hi,

    If you read the C6657 EVM Technical Reference Manual , the onboard emulator is XDS100, not XDS200. Specifically, please select "XDS100V1 USB Debug Probe" in CCS target connection.

    Regards, Eric

  • I have the TMDSEVM6657LS, not the TMDSEVM6657L. So am I not supposed to use the XDS200? I thought on the LS, the XDS200 is the preferred one.

  • HI,

    XDS200 is a Mezzanine card (it is a small card on top of the EVM). If you want to use XDS200, you can use it. But you said>>>> On board emulator does not connect>>>> On board emulator is XDS100V1.

    So, if you want to use:

    • On-board emulator: you need to remove the mezzanine card and use xds100v1, this is not the preferred given you bought LS EVM, not L EVM
    • xds200 mezzanine card, you need to select xds200 in ccxml target configuration. Can you try without updating the firmware? I have some other EVMs (K2H) with on-board XDS200 emulator, when I try to connect, it also asks me for firmware update, I just ignore that (the update didn't successful), I still be able to connect to the EVM.

    If XDS200 didn't connect, you can try "test connection" and please attach the result and CCS console log for the failure.

    Regards, Eric

  • When I used "Verify" connection, it will just sit there with the following and never finish.

  • Hi,

    Thanks for the update! Unfortunately I don't have any XDS200 mezzanine card to test on 6657 EVM. I added the CCS team engineers to see if them can help.

    Regards, Eric 

  • Hi Charles,

    There have been other reports of similar issues with updating the firmware for the XDS200 mezzanine cards. For some of these old cards, it was not possible to update via USB port. I'll will need to confirm and if so, find an alternate way to update it.

    Thanks

    ki

  • Hi Charles,

    I have been communicating with Blackhawk (the manufacturers of the mezzanine card). The suggested you contact them directly at:  support@blackhawk-dsp.com

    Thanks

    ki

  • I have contacted Blackhawk's support team and they told me that it is eInfoChip that makes the mezzanine card. Anyway, they provided me a similar procedure in updating the FW. The only difference that I can see is the sequence. On the TI website, here is the sequence:

    Run the commands in the exact order shown below:

    C:\ti\ccs1000\ccs\ccs_base\common\uscif\xds2xx>xds2xx_conf update xds2xxu 0 xds200_firmware_v1009.bin

    C:\ti\ccs1000\ccs\ccs_base\common\uscif\xds2xx>xds2xx_conf program xds2xxu 0 xds2xx_cpld_v1009.xsvf

    C:\ti\ccs1000\ccs\ccs_base\common\uscif\xds2xx>xds2xx_conf boot xds2xxu 0


    And they give me the following sequence:

    1. xds2xx_conf program xds2xxu 0 xds2xx_cpld_v1009.xsvf
    2. xds2xx_conf update xds2xxu 0 xds200_firmware_v1009.bin

    So which sequence is correct? I don't want to brick my emulator so I want to confirm. I tried the sequence on TI website and it failed at the updating step. So should I try the Blackhawk's sequence which does the programming step first before updating?

    Thanks.

  • The sequence on the TI website is our recommended procedure. It has worked for many others. 

    I did risk trying the sequence from Blackhawk. I didn't get any errors and my probe seems to still work. Since my probe already had the latest version, I'm not sure if the firmware upgrade would have been successful.

    Perhaps try contacting eInfoChip. Sorry for the misdirection to Blackhawk.

    ki