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.

XDS2xx emulator fail for EVMK2E - options?

It seems when I attempted to update the XDS2xx firmware (1.0.0.2) on my K2E EVM, it failed and I am no longer able to communicate with it.     At this moment I do not wish to return my K2E EVM, so I'm wondering about other options.

1) Can I load firmware on the CPLD via another method?

2) I own a Spectrum Digital XDS200 probe,    To use this I seem to need a MIPI 60 connection.   Sources for an adapter to connect it?

3) I have Xilinx tools and JTAG probes,   Is there an image that I can load directly to the device?

Thanks in advance for the guidance,

Larry

  • Larry,

    Can you explain what issue are you seeing after running the update script. Do you have a screenshot that you can share for the error when you are trying to connect to the EVM.

    Was there any error reported when you ran the update script or did you toggle power reset during the update?
    Did you unplug the USB connection from the EVM and power cycle the board after the update ran ??

    I moving this to CCS forums to get emulation experts to respond to your questions.

    Regards,
    Rahul

  • Rahul,


    I ran the update yesterday and did not see an issue.   Although I didn't think the update worked because the --version still reported 1.0.0.2.   I did power cycle the EVM each time after an update attempt.

    Today - I started fresh, meaning I rebooted my computer and power cycled my EVM and tried to debug a "hello world" project.   I get the following error which I did not receive yesterday.

    >Error initializing emulator:
    >(Error -2083 @ 0x0)
    >Unable to communicate with the debug probe. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation.
    >(Emulation package 6.0.222.0)

    I also checked the target configuration in CCS and tested the connection which gave the following error.  Yesterday the connection test passed.

    >This error is generated by TI's USCIF driver or utilities.

    >The value is '-250' (0xffffff06).
    >The title is 'SC_ERR_ECOM_EMUNAME'.

    >The explanation is:
    >An attempt to access the debug probe via USCIF ECOM has failed.

    >[End: Texas Instruments XDS2xx USB Onboard Debug Probe_0]

    I also noticed in the "updating the XDSD200 firmware" section of the XDS200 documents that old firmware releases (like the one I have 1.0.0.2) are known to have problems updating.

    Larry

  • Did you unplug the USB connection from the EVM and reconnect it to make sure the enumeration process is restarted correctly? Also please use the update script as follows to confirm the update conpleted.
    xds2xx_conf get xds2xxu 0

    This should show the version number of the firmware as 1.0.0.8.

    I have updated ard 6-8 EVMs with the script and didn`t notice any issues so I am trying to understand if there is difference in our setup. I noticed the error that you are reporting but after I reenumerated the XDS2xx USB connection, I was able to see the correct firmware version and connect in CCS.

    Can you also describe the LED behavior closest to the XDS2xx USB port as seen on the EVM.

    Regards,
    Rahul
  • Rahul, I have unplugged the USB as you suggested. I used the update script and have the following:
    Error: Failed to open port connection : XDS2xxu : 0
    Error: test failed

    Re the LEDs. I have 4 LEDS next to the USB (J3) LEDS are D6, D7, D8, D9 D7= on others = off
  • We received our XDS200 USB Debug probe today and decided to use the mipi-60 connection.   This resolves the problem of the JTAG emulator for now and we can move the project forward.