• TI Thinks Resolved

CCS/CCSTUDIO-KEYSTONE: CCS failed to connect 2 K2E EVMs with XDS200 emulator under Ubuntu 16.4, worked on Windows 7 and Windows 10

Part Number: CCSTUDIO-KEYSTONE

Tool/software: Code Composer Studio

Hi,

We have a customer using CCS to create target connection with two Keystone K2E EVMs. Their setup is:

Ubuntu 16.04 64-bit OS

CCS7.4.0 linux version

TMDXEVM66AK2E

XDS200 on board emulator

 They followed the link below:

http://software-dl.ti.com/ccs/esd/documents/sdto_ccs_multi-probe-debug.html

http://processors.wiki.ti.com/index.php/Target_Configuration_-_Custom_Configurations

So they defined the port number as "0" and "1" respectively for the two K2E EVMs using XDS 200 emulator. It never worked for them. For any individual EVM, they can connect. So this is not a HW issue.

I asked customer to do the same steps with Windows 10 machine, CCS version is 7.4.0. It always worked. We also tried locally with Windows 7 + CCS 6.1.3, it always worked.

Can you help to resolve the issue on Ubuntu machine as this is their main work enviornment?

Regards, Eric 

  • Guru 124380 points
    Eric,

    Thank you for reporting this. It seems that you already covered the scenarios that would isolate the issue to the built-in XDS200 Debug Probes of the boards.

    I will double-check this next Monday when I am back to the office and file a bug report.

    I apologize for the inconvenience,
    Rafael

    When posting, click on the link Insert Code, Attach Files and more... to attach images, files or use nice formatting.

    If my reply answers your question please click on the green button "This resolved my issue".

    Search the wiki or go to useful pages for SDOWP, Compilers, CCSv3, CCSv4, CCSv5, CCSv6, CCSv7
  • Guru 124380 points

    In reply to desouza:

    Eric,

    I filed today the bug number DBGTRC-3971. Its status can be verified in about half hour in the link SDOWP in my signature below.

    Unfortunately there is no workaround to this issue.

    I apologize for the inconvenience,
    Rafael

    When posting, click on the link Insert Code, Attach Files and more... to attach images, files or use nice formatting.

    If my reply answers your question please click on the green button "This resolved my issue".

    Search the wiki or go to useful pages for SDOWP, Compilers, CCSv3, CCSv4, CCSv5, CCSv6, CCSv7
  • Guru 124380 points

    In reply to desouza:

    Eric,

    With the help of the dev team, I verified this is not a real bug. In *nix systems, the different Debug Probes are enumerated as /dev/ttyACMn, where 'n' is presented in pairs for each Debug Probe - the first one is ttyACM0 and ttyACM1, the second debug probe ttyACM2 and ttyACM3 and so on.

    In this case, I was able to connect to my three 66AK2 boards here by using even numbers for each Debug Probe: 0, 2 and 4.

    The different operating systems enumerate in a different form, thus Windows presents the posts in a regular sequence (0, 1, 2...)

    Please give this a try and see if it works for you as well. 

    Hope this helps,

    Rafael


    When posting, click on the link Insert Code, Attach Files and more... to attach images, files or use nice formatting.

    If my reply answers your question please click on the green button "This resolved my issue".

    Search the wiki or go to useful pages for SDOWP, Compilers, CCSv3, CCSv4, CCSv5, CCSv6, CCSv7