Linux 64 OS on a machine with a C2000 processor and XDS100v1

Hello,

I tried this out on my native Ubuntu 22.04LTS with CCS 12.2.0. I had multiple XDS100v1 plugged in and I did not have an issue launching a debug session for my F28069 controlstick (XDS100v1) and connecting to it.

Which linux distro and version is being used? Which exact CCS version?

Thanks

ki

Hi Ki,

They are using Linux Tumbleweed (I think the distro is OpenSUSE). I'll confirm the CCS version

Marvn Arcangel said:

They are using Linux Tumbleweed (I think the distro is OpenSUSE).

Please note that this distro is not officially supported by CCS.

I've tried multiple things but I am still unable to reproduce the issue. Multiple XDS100v1 probes on both ttyUSB0 and ttyUSB1 work without issue (I can start up debug sessions and connect for each).

Please note that the customer is using an unsupported Linux distro. The support we can provide for such distributions are limited.

Hi Ki,

In the link above the original poster is using Linux mint 17, does that mean that linux mint is also not supported? can you tell me which distro is supported?

Marvn Arcangel said:

can you tell me which distro is supported?

Please see:

https://software-dl.ti.com/ccs/esd/documents/users_guide/ccs_overview.html#linux

Hi Ki,

I see, thanks. Is there anything else we can do to support the customer? could this maybe a problem with drivers (the jtag+rs232) other than the OS?

We would need to set up a comparable linux environment and see if we can reproduce and investigate. Please note that because this is an unsupported environment, it would not be something we can investigate right away.

HI Ki, 

How long would it take to do this?

Perhaps it is something we can look at next week.

Marvn Arcangel said:

On the other hand if an ftdi device is connected in another ttyUSB port, the JTAG no longer works.

Using CCS 12.1 under Ubuntu 18.04 have a generic FT2232 serial-to-USB adaptor connected to the PC.

If create a target configuration file for XDS100v2, which defaults the "Debug Probe Selection" to "Only one XDS100 installed" then when try and start a debug session for a TMS320F28379D then:

• CCS reports the error "IcePick_C_0: Error connecting to the target: (Error -183 @ 0x0) The controller has detected a cable break far-from itself. The user must connect the cable/pod to the target. (Emulation package 9.9.0.00040)".
• From the LEDs on the generic FT2232 serial-to-USB adaptor I see CCS attempted to open the generic FT2232 serial-to-USB adaptor, rather than the XDS100v2.

What allows me to debug is:

1. Run xds100serial to identify the serial number of the XDS100v2. E.g. the following shows the serial number of the generic FT2232 serial-to-USB adaptor (FTVIZUNN) and the XDS100v2 (TIJ61P3):

$ ~/ti/ccs1210/ccs/ccs_base/common/uscif/xds100serial 
Scanning for XDS100 emulators...

VID/PID    Type            Serial #    Description
0403/6010  generic FT2232  FTVIZUNN    FT2232H device 
0403/a6d0  XDS100v1/v2     TIJ61P3     Texas Instruments Inc.XDS100 Ver 2.

2. In the CCS Target Configuration File:

• Set  "Debug Probe Selection" to "Select by serial number"
• In "-Enter the serial number" enter the XDS100v2 serial number reported by xds100serial

I don't have a XDS100v1 to try, but for a XDS100v1 CCS should also allow you to "Select by serial number".

Chester Gillon said:

I don't have a XDS100v1 to try, but for a XDS100v1 CCS should also allow you to "Select by serial number".

Yes, this is also the case for XDS100v1. I did specify the serial numbers for XDS100v1 in my environment. This is certainly worth trying for the customer