• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 4599 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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/XEVMK2LX: On board XDS200 cannot be accessed

Dorothea Pfeiffer
Prodigy 200 points

Part Number: XEVMK2LX

Tool/software: Code Composer Studio

Dear community,

I have problems accessing the on board XDS200 on my XEVMK2LX board.I'm using XDS Emulation Software release 6.0.579.0 and CCS 7.1.0.00015 on Ubuntu 16.0.4.

The board itself seems ok, the pre-installed applications are running, and I can access the BMC as explained in the hardware guide. When I first connected the mini-USB cable for the xds200 (correct USB port, LEDs 1 and 2 on as shown in e2e.ti.com/.../540221, the devices ttyACM0 and ttyACM1 appeared on my host PS.  I tried to test the connection with CCS7, but got the following error:

E_RPCENV_IO_ERROR(-6) No connection: DTC_IO_Open::dtc_io
Failed to open i/o connection (xds2xxu:0)

After that I tried to update the firmware (10.0.0.2), which failed.

> update_xds2xx.sh xds200

Updating CPLD
Error : test failed
.
Updating Firmware
ERROR: failed firmware update
Error : test failed
.
Rebooting
.
Reading Configuration
.
Check swRev is 1.0.0.8 or higher
.
Error : Failed to open port connection : xds2xxu : 0
Error : test failed
.
Hit any key to exit

After the attempted update, the LED2 on the board was not lit anymore, and also the devices ttyACM0 and ttyACM1 disappeared. I also tried with MacOS and Windows, but it seems that the USB device is not recognized any more.

So it looks like I fried the onboad xds200? Any idea of the wiring of the LED 2, so what exactly is broken? What do you recommend? Get an external debug probe and try to use that before I send the board back? Which one would you choose for the XEVMK2LX? Advice and help greatly appreciated, I just can't believe that I fried the board :-(((

Cheers

Dorothea

  • 0
    TI__Guru**** 169754 points

    Dorothea,

    Due to unknown (at least to me) reasons the Keystone II boards like yours were pre-programmed from the factory with a very old firmware on their XDS200 embedded debuggers.

    As you noticed (and reported in the XDS200 wiki page), the original firmware does not work in Linux, therefore an update is mandatory it you need to use it in this OS. Unfortunately due to this very same reason the update should only be done in a Windows OS (as noted in section 7 of the XDS200 wiki page), as Linux can't properly communicate with the probe.

    In this case you were caught in an unfortunate situation where the XDS200 may, in fact, be bricked (not necessarily fried as there is no physical damage to it). As a last recourse I would try to connect the board to a Windows host and see if the JTAG debugger can be detected and updated. Otherwise a RMA would be required. 

    In the meantime I will try to see if there is a documented method to write the firmware using the JTAG port of the AM1802 device (the 20-pin connector near it). 

    I apologize for the inconvenience,

    Rafael

  • 0 in reply to desouza
    Prodigy 200 points
    Hi Rafael,

    thank you so much for your answer! The sad thing is that I did actually read the xds200 TWIKI page before I tried to update the firmware. I got confused concerning the version of the xds200 firmware, since the EVM has a sticker on the Ethernet socket which reads "EVM v 1.0.3.0". And me, idiotically, took that as version of the xds200 firmware, wrongly assuming that it was not the dreaded 1.0.0.2 version.

    Anyway, damage done, and I learned something :-). I thought that I really fried something, because the LED 2 is not lit anymore, no matter whether I connect the USB cable to a Windows PC, Mac OS or Linux. Also, the USB devices are not created any more. But if the xds200 is just bricked as you say, It would be so great if you could figure out how to write the firmware via the AM1802. In the mean time I ordered a XDS560v2 with MIPI 60 connector, to be able to work with the board even if the on board xds200 cannot be recovered.

    Three more little question:
    1. Boot modes, I'm a little confused why there are so many of them. To run user programs or the pre-installed software, I set SW1 to 0,0,1,0 (NOR SPI Boot) . For the JTAG I have to set it to 1,1,1,1 (NO BOOT). When do I use the other ones?

    2. I installed the latest CCS 7 and the processor SDK, although the EVM came with CCS5 and MSDK. Is it the correct strategy to go for the latest versions? Because sometimes the documentation for the XEVMK2LX is confusing because it refers to the MSDK.

    3. Processor-SDK: For the ARM processors, should one choose the Linux or the RT Linux? I guess it depends on the application, but what would be best for a total Keystone II beginner?

    Cheers

    Dorothea
  • 0 in reply to Dorothea Pfeiffer
    TI__Guru**** 169754 points

    Dorothea,

    Dorothea Pfeiffer said:
    thank you so much for your answer! The sad thing is that I did actually read the xds200 TWIKI page before I tried to update the firmware. I got confused concerning the version of the xds200 firmware, since the EVM has a sticker on the Ethernet socket which reads "EVM v 1.0.3.0". And me, idiotically, took that as version of the xds200 firmware, wrongly assuming that it was not the dreaded 1.0.0.2 version.

    I feel your pain... I have a bricked XDS200 mezzanine card that had the 1.0.0.2 firmware and I did exactly the same as you: I tried to update it using a MacOS host... 

    Dorothea Pfeiffer said:
    Anyway, damage done, and I learned something :-). I thought that I really fried something, because the LED 2 is not lit anymore, no matter whether I connect the USB cable to a Windows PC, Mac OS or Linux. Also, the USB devices are not created any more. But if the xds200 is just bricked as you say, It would be so great if you could figure out how to write the firmware via the AM1802. In the mean time I ordered a XDS560v2 with MIPI 60 connector, to be able to work with the board even if the on board xds200 cannot be recovered.

    It is good that you are going to get an external JTAG debugger - you would need one to un-brick the onboard XDS200. 

    By playing with my bricked XDS200 I think I was able to find a way to make it work. The procedure below takes into consideration the original XDS200 bootloader in flash memory is intact - there is no way to know until you try the procedure and see if it works after a disconnect/connect.

    - Connect an external JTAG debugger to the JTAG port of the XDS200 onboard debugger. 

    - Start CCS and create a target configuration using the external JTAG debugger as a connection and the AM1802 as the target device.

    - Follow the steps on the video below (I will eventually "beautify it" to publish somewhere else)

    Dorothea Pfeiffer said:
    Three more little question:

    The most experienced folks that can reply to these questions are residents of the Keystone II forum, therefore I would definitely post these questions there. 

    However, I can take a stab at them:

    1. The multiple boot modes in a device are generically suitable for the various applications where it can be used. The two boot modes mentioned in the documentation take into account the board hardware, but if the device runs in a different HW infrastructure it can boot from different peripherals such as the Ethernet, PCIe, etc.

    2. The Processor SDK is the evolution of the MCSDK and, IIRC, supports CCSv6.2 or CCSv7.0. Given the support for the MCSDK may be stale or non-existing, I would certainly try to move ahead with the newer SDK. 

    3. As you said, the application will demand which version of Linux SDK is more suitable. RT Linux has time-dependent mechanisms at the expense of a performance impact, while Linux is leaner but less deterministic. 

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Prodigy 200 points
    Hi Rafael,

    following your instructions in the video worked like a charm! Great job! I used my Ubuntu 16.0.4 host and connected the xds560v2 with the MIPI60 to 20 pin adapter to the 20 pin JTAG of the AM1802. While doing that the xds200 on board mini-USB cable has to be connected, otherwise CCS complains about no power for the controller. From this point on it was smooth sailing, the video is already very easy to follow and very detailed.

    Now I have two JTAGs working on Ubuntu 16.0.4, and I'm in a very good mood!

    Thanks so much!! So issue is closed for me..

    Cheers

    Dorothea
  • 0 in reply to desouza
    Intellectual 455 points
    Hi Rafael/Dorothea,

    Can you please repost the link to the video for the steps to recover the XDS200, as I cant seem to find a link in the post above? I am in the exact same situation as Dorothea , and am desperate to resolve this issue.

    Thanks and Regards
    Nishant Bhaskar