• State Resolved
  • Locked Locked
  • Replies 19 replies
  • Answers 1 answer
  • Subscribers 56 subscribers
  • Views 1838 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/TMS320C6657: XDS200, Linux, EvalBoard

LazyHD
Expert 1060 points
Part Number: TMS320C6657

Tool/software: Code Composer Studio

Hello,

I bought an evaluation board for C6657, opted for the one that comes with XDS200 emulator TMDSEVM6657LS. 

Now I cannot connect to the XDS200 using CCS under Ubuntu. I tried both CCS8 and CCS9. I looked into problems and solutions already proposed previously on the forum and it is still not working for me.

I tried both USB3 and USB2 ports on my laptop, not working on neither.

Firmware Update:

http://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_xds200.html#troubleshooting

"When connected to USB3.0 ports and hubs in Linux OSes, XDS200 JTAG debuggers are not able to properly be initialized by the low-level device drivers. If you update to the latest "TI emulators" package and update the firmware on the xds200 pod then you can connected it to a USB3 port with Linux."

I booted to Windows, followed the update process and the log is shown below. Still same problem.

C:\ti\ccs901\ccs\ccs_base\common\uscif\xds2xx>update_xds2xx xds200
.
Updating Firmware ...
.
Rebooting, please wait ...
.
Updating CPLD ...
.
Reading Configuration ...
.
Check swRev is 1.0.0.8 or higher.
.
boardRev=2
ipAddress=0.0.0.0
ipConfig=dhcp
ipGateway=255.255.255.255
ipNetmask=255.255.255.255
productClass=XDS2XX
productName=XDS200
serialNum=00:0E:99:03:90:93
swRev=1.0.0.8
hostCPU=AM1802
emuCtrlType=Bit bang
extMemType=SDRAM
portUSB=true
portENET=false
portWIFI=false
portRS232=false
EnableUSBSerial=false
CurrentMeasure=false
.
Press any key to continue . . .

Seems that the firmware was successfully updated to 1.0.0.8, but my problem is still happening.

Dmesg:

[ 2031.431984] usb 1-3: new high-speed USB device number 12 using xhci_hcd
[ 2031.580965] usb 1-3: New USB device found, idVendor=0451, idProduct=bef0
[ 2031.580974] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2031.580981] usb 1-3: Product: XDS2xx USB Emulator - Composit
[ 2031.580987] usb 1-3: Manufacturer: Spectrum Digital
[ 2031.580993] usb 1-3: SerialNumber: S200-000E99039000

The probe is successfully initialized by the OS

lsusb:

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 05c8:03ac Cheng Uei Precision Industry Co., Ltd (Foxlink) 
Bus 001 Device 004: ID 8087:0aa7 Intel Corp. 
Bus 001 Device 012: ID 0451:bef0 Texas Instruments, Inc. 
Bus 001 Device 002: ID 09da:51d9 A4Tech Co., Ltd. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

CCS Test Connection:

[Start: Texas Instruments XDS2xx USB Debug Probe_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]


-----[Print the board config pathname(s)]------------------------------------

/home/hd/.ti/ccs901/0/0/BrdDat/testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 560/2xx-class product.
This utility will load the program 'xds2xxu.out'.
E_RPCENV_IO_ERROR(-6) No connection: DTC_IO_Open::dtc_io
Failed to open i/o connection (xds2xxu:0)

An error occurred while soft opening the controller.

-----[An error has occurred and this utility has aborted]--------------------

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 Debug Probe_0]

PCI USB controller:

00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller [8086:9d2f] (rev 21)

Questions:

  • There is another usb port on the board, it seems to be an XDS100. When testing with CCS this one works but it seems it is not connected to the target processor.
    Any way to connect this probe to the processor ?
  • I was planning to buy an external XDS200 debug probe, now I am worried it doesn't work on Linux. 
    Will I face the same problem with a standalone XDS200 ? Any solutions for this ?
  • Goes without saying, any solutions to make this work ?

Ubuntu 18.04
CCS8 and CCS901
Processor SDK: processor_sdk_rtos_c665x_5_02_00_10

Thanks

  • 0
    Expert 1060 points

    The other on-board emulator is XDS100V1 not XDS100V2 which I was originally trying. I can successfully use this one to debug my code.

    My other questions remain, if I buy a standalone XDS200 will I be able to make it work on Ubuntu ? Any other suggestions ?

    Thanks

  • 0
    Expert 1060 points

    I tested the XDS200 probe on two different laptops and it doesn't seem to work.

    I tested it on a desktop and it is working for some weird reason. On the desktop I tested on both USB2 and USB3 ports and it is working on both.

    Both laptops and the desktop running Ubuntu 18.04

    All tests with CCSv9

  • 0 in reply to LazyHD
    TI__Guru**** 420650 points

    Same here. I can't get my XDS200 to work on my Ubuntu 18.04.2 LTS. No issues on my Windows 10 PC. It looks like an issue with communication between the host and the debug probe. 

    The issue seems similar to the one mentioned in the below thread:

    https://e2e.ti.com/support/tools/ccs/f/81/p/731145/2719913

    In that thread, a workaround running the configuration utility with strace seems to work. However, I cannot get it to work for me.

    We are still investigating this issue

    Thanks

    ki

  • 0 in reply to Ki
    Expert 1060 points

    strace doesn't fix the problem for me neither.

    We will postpone the purchase order on the XDS200 probe until this is fixed. Any ETA ? Is it on active testing and looking for a fix ? Asking because the thread you linked is pretty old.

  • 0 in reply to LazyHD
    TI__Guru**** 420650 points

    I can't seem to find any recent activity on this issue. Regardless, since I can easily reproduce the issue, I will make sure it is investigated. 

  • 0 in reply to Ki
    Expert 1060 points

    hi Ki,

    Any update on this or an ETA ? Our prototypes are almost completed and we need to proceed to buy an XDS emulator.

    Thanks

  • 0 in reply to LazyHD
    TI__Guru**** 168317 points

    Hi,

    Since your probe works on Windows, it rules out any issues with the probe itself. 

    One question about the dmesg output; do you see any /dev/ttyACMn ports instantiated? You should have at least two. 

    If you see both instantiated but the probe still does not connect, can you do a quick test? From the command line, see if you can access the XDS200 using the command below:

    user@host:~/ti/ccs/ccs_base/common/uscif/xds2xx$ ./xds2xx_conf get xds2xxu 0

    If you are unable to get any information, then try to run it as sudo. If this time is successful, you need to add the udev rules by running the install scripts as shown below:

    user@host:~/ti/ccs/install_scripts$ sudo ./install_drivers.sh

    This should grant you access to the debug probe from user permissions. 

    I was able to communicate with my C6657 with the Mezzanine XDS200 on Ubuntu 18.04.2 with both CCsv8.3.0 and CCSv9.0.1.

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Expert 1060 points

    1- I never said the probe is the problem, it works fine on windows both in ccs and firmware update

    2- I do see 2 ttyACM in the dmesg

    3- I already tried the  ./xds2xx_conf get xds2xxu 0 command, and retried again now (with and without sudo) and still not working

    4- The probe works well on my Desktop computer under Ubuntu 18.04 as well but it fails to work on any laptop with Ubuntu 18.04 (I tried 3)

    5- Running strace with the  ./xds2xx_conf get xds2xxu 0 command always gets stuck in the same place, 

    ioctl(3, FIONREAD, [0]) = 0
    ioctl(3, TCFLSH, TCIOFLUSH) = 0
    ioctl(3, TCGETS, {B115200 -opost -isig -icanon -echo ...}) = 0
    ioctl(3, SNDCTL_TMR_START or TCSETS, {B115200 -opost -isig -icanon -echo ...}) = 0
    ioctl(3, TCGETS, {B115200 -opost -isig -icanon -echo ...}) = 0
    nanosleep({tv_sec=1, tv_nsec=0}, 0x7ffd84f485e0) = 0
    write(3, "\0\0\0\0\0\0\0\0", 8) = 8
    write(3, "\0\0\0\0\0\0\0\0", 8) = 8
    write(3, "\0\0\0\0\0\0\0\0", 8) = 8
    write(3, "\0\0\0\0\0\0\0\0", 8) = 8
    write(3, "\0\0\0\0\0\0\0\0", 8) = 8
    write(3, "\0\0\0\0\0\0\0\0", 8) = 8
    write(3, "\0\0\0\0\0\0\0\0", 8) = 8
    write(3, "\1f\231\0\0\22\0\0\0\30\0\0\0\0\0\0\0\0", 18) = 18
    read(3, "", 8) = 0
    read(3, "", 8) = 0
    read(3, "", 8) = 0
    read(3, "", 8) = 0
    read(3, "", 8) = 0

    It indefinetly repeats the read command, while on the desktop environment where the probe works this doesn't happen.

  • 0 in reply to LazyHD
    Expert 1060 points

    If I spam the strace ./xds2xx_conf get xds2xxu 0 command while plugging the usb cable into the laptop. The XDS probe will work once, then when i run the same command again it gets stuck as before.

    i noticed one difference in the strace:

    ioctl(3, TCGETS, {B9600 opost isig icanon echo ...}) = 0
    ioctl(3, FIONREAD, [0]) = 0
    ioctl(3, TCFLSH, TCIOFLUSH) = 0
    ioctl(3, TCGETS, {B9600 opost isig icanon echo ...}) = 0
    ioctl(3, SNDCTL_TMR_START or TCSETS, {B115200 -opost -isig -icanon -echo ...}) = 0
    ioctl(3, TCGETS, {B115200 -opost -isig -icanon -echo ...}) = 0
    nanosleep({tv_sec=1, tv_nsec=0}, ^[[A0x7fff8b6e8140) = 0
    write(3, "\0\0\0\0\0\0\0\0", 8) = 8
    write(3, "\0\0\0\0\0\0\0\0", 8) = 8
    write(3, "\0\0\0\0\0\0\0\0", 8) = 8
    write(3, "\0\0\0\0\0\0\0\0", 8) = 8
    write(3, "\0\0\0\0\0\0\0\0", 8) = 8
    write(3, "\0\0\0\0\0\0\0\0", 8) = 8
    write(3, "\0\0\0\0\0\0\0\0", 8) = 8
    write(3, "\1f\231\0\0\22\0\0\0\30\0\0\0\0\0\0\0\0", 18) = 18
    read(3, "\1\231f\0\0\36\0\0", 8) = 8

    The 9600 is there on the desktop (where the xds works) on the laptop (the first time when the xds works). 

    On subsequent commands (and anytime it doesn't work) this 9600 is 115200 and the probe doesn't work anymore. 

    I tried 

    stty -F /dev/ttyACM0 9600

    It will change the 115200 to 9600 but still the same problem.

  • 0 in reply to LazyHD
    TI__Guru**** 168317 points

    Hi,

    After my post, I issued an update to try and catch the latest updates to my Ubuntu 18.04.2 and the probe stopped working altogether. 

    After looking at your tests, this gave me an idea: I was able to communicate with the pod if I explicitly set the port speed to 9600 by issuing the following command:

    user@host:~/$ sudo stty -F /dev/ttyACM0 ospeed 9600 ispeed 9600

    Therefore some specific setting was changed in the latest revision of the OS components. Unfortunately my update had some 300 components updated and a thorough analysis will be hard to do. 

    I will do some additional tests and see which conditions trigger this scenario. 

    My Mezzanine card was plugged to a USB3.0 port of my Latitude E6520 laptop. 

    Regards,

    Rafael

  • 0 in reply to desouza
    Expert 1060 points

    I pulled the updates on my desktop PC and I can confirm that the probe stopped working. strace on both the desktop and laptop is now similar.

    'sudo stty -F /dev/ttyACMx ospeed 9600 ispeed 9600' does not help in my case on neither the desktop nor the laptop

    The only time it works, for only onc, is when I spam ./xds2xx_conf get... while plugging the usb cable. I don't know what kicks in directly after that.

    Thank you for your help

  • 0 in reply to LazyHD
    Expert 1060 points

    I had slightly less packages, I don't know if it would help comparing the common packages.

    The following NEW packages will be installed:
    gstreamer1.0-gtk3 linux-headers-4.15.0-52 linux-headers-4.15.0-52-generic linux-image-4.15.0-52-generic linux-modules-4.15.0-52-generic
    linux-modules-extra-4.15.0-52-generic python3-pyside2.qtuitools python3-pyside2.qtxml
    The following packages have been kept back:
    libio-socket-ssl-perl libnet-ssleay-perl libpython3.6 libpython3.6-minimal libpython3.6-stdlib libruby2.5 libssl-dev libssl1.1 libssl1.1:i386 nodejs nodejs-dev openssl
    python-cryptography python3-cryptography python3.6 python3.6-minimal
    The following packages will be upgraded:
    adobe-flash-properties-gtk adobe-flashplugin apt apt-transport-https apt-utils bash blender blender-data console-setup console-setup-linux cups cups-bsd cups-client
    cups-common cups-core-drivers cups-daemon cups-ipp-utils cups-ppdc cups-server-common debconf debconf-i18n fonts-lyx fonts-opensymbol freecad freecad-common freecad-python3
    freecad-runtime gedit gedit-common gir1.2-geocodeglib-1.0 gir1.2-gnomebluetooth-1.0 gir1.2-gtk-3.0 gir1.2-lokdocview-0.1 gir1.2-mutter-2 gnome-bluetooth
    gnome-control-center gnome-control-center-data gnome-control-center-faces gnome-shell gnome-shell-common gnome-software gnome-software-common gnome-software-plugin-snap
    google-chrome-stable gtk-update-icon-cache im-config initramfs-tools initramfs-tools-bin initramfs-tools-core keyboard-configuration language-selector-common
    language-selector-gnome libaio1 libapt-inst2.0 libapt-pkg5.0 libcephfs2 libcups2 libcups2:i386 libcupscgi1 libcupsimage2 libcupsmime1 libcupsppdc1 libegl1 libegl1:i386
    libfreecad-python3-0.18 libgail-3-0 libgeocode-glib0 libgl1 libgl1:i386 libgles2 libglvnd0 libglvnd0:i386 libglx0 libglx0:i386 libgnome-bluetooth13 libgtk-3-0
    libgtk-3-0:i386 libgtk-3-bin libgtk-3-common libldap-2.4-2 libldap-common liblibreofficekitgtk libmbim-glib4 libmbim-proxy libmm-glib0 libmutter-2-0 libneon27-gnutls
    libnss-myhostname libnss-systemd libnuma1 libnuma1:i386 libocct-data-exchange-7.3 libocct-foundation-7.3 libocct-modeling-algorithms-7.3 libocct-modeling-data-7.3
    libocct-ocaf-7.3 libocct-visualization-7.3 libpam-systemd libplymouth4 libpython2.7 libpython2.7-minimal libpython2.7-stdlib libqmi-glib5 libqmi-proxy librados2
    libreoffice-avmedia-backend-gstreamer libreoffice-base-core libreoffice-calc libreoffice-common libreoffice-core libreoffice-draw libreoffice-gnome libreoffice-gtk
    libreoffice-gtk2 libreoffice-gtk3 libreoffice-impress libreoffice-math libreoffice-ogltrans libreoffice-pdfimport libreoffice-style-breeze libreoffice-style-galaxy
    libreoffice-style-tango libreoffice-writer libreofficekit-data libssl-doc libsysmetrics1 libsystemd0 libsystemd0:i386 libudev1 libudev1:i386 libwww-perl linux-generic
    linux-headers-generic linux-image-extra-virtual linux-image-generic linux-libc-dev login modemmanager mutter mutter-common netplan.io nordvpn nplan openvpn
    papirus-icon-theme passwd plymouth plymouth-label plymouth-theme-ubuntu-logo plymouth-theme-ubuntu-text python-apt python-apt-common python2.7 python2.7-minimal python3-apt
    python3-debconf python3-distupgrade python3-distutils python3-gdbm python3-lib2to3 python3-software-properties python3-tk python3-uno python3-update-manager ruby2.5
    skypeforlinux snapd software-properties-common software-properties-gtk systemd systemd-sysv teamviewer ubuntu-core-launcher ubuntu-desktop ubuntu-minimal
    ubuntu-release-upgrader-core ubuntu-release-upgrader-gtk ubuntu-report ubuntu-software ubuntu-standard udev unattended-upgrades uno-libs3 update-manager update-manager-core
    update-notifier update-notifier-common ure ureadahead

  • 0 in reply to LazyHD
    TI__Guru**** 168317 points

    Hi,

    Thank you for sending the list of packages - I can spot a few such as modemmanager or udev that could influence this outcome.

    However, to be absolutely sure I would like to compare the exact versions as well. In this case, if possible would you mind attaching the relevant portion of the apt log file? 

    This file is /var/log/apt/history.log and the relevant portion would be between the specific Start-Date and End-Date that the upgrades took over.

    In my log, this displays as:

    history.log said:

    Start-Date: 2019-06-18 13:48:58
    Commandline: apt upgrade
    Requested-By: user (1000)
    Install: linux-modules-4.15.0-52-generic:amd64 (4.15.0-52.56, automatic), linux-headers-4.15.0-52-generic:amd64 (4.15.0-52.56, automatic), python3-dateutil:amd64 (2.6.1-1, automatic), linux-headers-4.15.0-52:amd64 (4.15.0-52.56, automatic), linux-image-4.15.0-52-generic:amd64 (4.15.0-52.56, automatic), gstreamer1.0-gtk3:amd64 (1.14.1-1ubuntu1~ubuntu18.04.1, automatic), linux-modules-extra-4.15.0-52-generic:amd64 (4.15.0-52.56, automatic)
    Upgrade: libpam0g:amd64 (1.1.8-3.6ubuntu2, 1.1.8-3.6ubuntu2.18.04.1), debconf:amd64 (1.5.66, 1.5.66ubuntu1), libreoffice-style-breeze:amd64 (1:6.0.7-

    ...

    0ubuntu0.18.04.6), python3-apt:amd64 (1.6.3ubuntu1, 1.6.4), libxcb-sync1:amd64 (1.13-1, 1.13-2~ubuntu18.04), libreoffice-avmedia-backend-gstreamer:amd64 (1:6.0.7-0ubuntu0.18.04.5, 1:6.0.7-0ubuntu0.18.04.6), mutter:amd64 (3.28.3-2~ubuntu18.04.2, 3.28.4-0ubuntu18.04.1), libglx-mesa0:amd64 (18.2.2-0ubuntu1~18.04.2, 18.2.8-0ubuntu0~18.04.2), libglvnd0:amd64 (1.0.0-2ubuntu2.2, 1.0.0-2ubuntu2.3), software-properties-common:amd64 (0.96.24.32.7, 0.96.24.32.9)

    End-Date: 2019-06-18 13:53:39

    This way it would be easier to compare the specific versions and try to find out the exact root cause. 

    One additional easy test I did this morning was run the prior kernel 4.15.0-51, but the debug probe still couldn't be detected, therefore the change is tied to one of the other modules and/or components. 

    If you would like to try this as well, just hold the Shift key during boot and select the kernel version via the Grub menu.

    Thank you,

    Rafael

  • 0 in reply to desouza
    TI__Guru**** 168317 points

    Hi,

    I filed today the critical bug DBGTRC-5021. In about half hour, please check its status in the link SDOWP in my signature below. 

    I apologize for the inconvenience, and I will still keep looking for possible workarounds to this issue. 

    If you are able to send the information I mentioned above, this could help us speed up the process of finding the root cause for this. 

    Thank you, 

    Rafael

  • 0 in reply to desouza
    Expert 1060 points

    Hi Desouza,

    No need to apologize, being a firmware developer I understand completely how things go chaotic after system updates.

    Please find the relevant part of the update history below. I am happy to provide you with any tests, logs.. you need from my side.

    Start-Date: 2019-06-19  00:58:39
Commandline: apt upgrade
Requested-By: lazyhd (1000)
Install: python3-pyside2.qtxml:amd64 (5.11.2-0ppa2~ubuntu18.04, automatic), linux-modules-4.15.0-52-generic:amd64 (4.15.0-52.56, automatic), linux-headers-4.15.0-52-generic:amd64 (4.15.0-52.56, automatic), python3-pyside2.qtuitools:amd64 (5.11.2-0ppa2~ubuntu18.04, automatic), linux-headers-4.15.0-52:amd64 (4.15.0-52.56, automatic), linux-image-4.15.0-52-generic:amd64 (4.15.0-52.56, automatic), gstreamer1.0-gtk3:amd64 (1.14.1-1ubuntu1~ubuntu18.04.1, automatic), linux-modules-extra-4.15.0-52-generic:amd64 (4.15.0-52.56, automatic)
Upgrade: gir1.2-lokdocview-0.1:amd64 (1:6.0.7-0ubuntu0.18.04.5, 1:6.0.7-0ubuntu0.18.04.6), debconf:amd64 (1.5.66, 1.5.66ubuntu1), libreoffice-style-breeze:amd64 (1:6.0.7-0ubuntu0.18.04.5, 1:6.0.7-0ubuntu0.18.04.6), libqmi-proxy:amd64 (1.18.0-3ubuntu1, 1.22.0-1.2~ubuntu18.04.1), gir1.2-geocodeglib-1.0:amd64 (3.25.4.1-4, 3.25.4.1-4ubuntu0.18.04.1), libreoffice-math:amd64 (1:6.0.7-0ubuntu0.18.04.5, 1:6.0.7-0ubuntu0.18.04.6), blender:amd64 (2.79.b+dfsg0-1, 2.79.b+dfsg0-1ubuntu1.18.04.1), gnome-control-center-data:amd64 (1:3.28.2-0ubuntu0.18.04.3, 1:3.28.2-0ubuntu0.18.04.4), fonts-lyx:amd64 (2.2.3-5, 2.2.4-0ubuntu0.18.04.1), netplan.io:amd64 (0.40.1~18.04.4, 0.97-0ubuntu1~18.04.1), libfreecad-python3-0.18:amd64 (2:0.18.1+dfsg1~201904061907~ubuntu18.04.1, 2:0.18.1+dfsg1~201904300243~ubuntu18.04.1), libcups2:amd64 (2.2.7-1ubuntu2.4, 2.2.7-1ubuntu2.6), libcups2:i386 (2.2.7-1ubuntu2.4, 2.2.7-1ubuntu2.6), update-manager-core:amd64 (1:18.04.11.9, 1:18.04.11.10), linux-headers-generic:amd64 (4.15.0.51.53, 4.15.0.52.54), gedit:amd64 (3.28.1-1ubuntu1.1, 3.28.1-1ubuntu1.2), ureadahead:amd64 (0.100.0-20, 0.100.0-21), gir1.2-gtk-3.0:amd64 (3.22.30-1ubuntu2, 3.22.30-1ubuntu3), python3-distutils:amd64 (3.6.7-1~18.04, 3.6.8-1~18.04), gir1.2-mutter-2:amd64 (3.28.3-2~ubuntu18.04.2, 3.28.4-0ubuntu18.04.1), gnome-control-center:amd64 (1:3.28.2-0ubuntu0.18.04.3, 1:3.28.2-0ubuntu0.18.04.4), linux-libc-dev:amd64 (4.15.0-51.55, 4.15.0-52.56), libapt-inst2.0:amd64 (1.6.10, 1.6.11), libldap-2.4-2:amd64 (2.4.45+dfsg-1ubuntu1.1, 2.4.45+dfsg-1ubuntu1.2), libegl1:amd64 (1.0.0-2ubuntu2.2, 1.0.0-2ubuntu2.3), libegl1:i386 (1.0.0-2ubuntu2.2, 1.0.0-2ubuntu2.3), python3-software-properties:amd64 (0.96.24.32.7, 0.96.24.32.9), libreofficekit-data:amd64 (1:6.0.7-0ubuntu0.18.04.5, 1:6.0.7-0ubuntu0.18.04.6), ruby2.5:amd64 (2.5.1-1ubuntu1.2, 2.5.1-1ubuntu1.4), libocct-ocaf-7.3:amd64 (7.3.0-0ppa4~ubuntu18.04.1, 7.3.0+dfsg1-5~ubuntu18.04.1), libreoffice-gtk2:amd64 (1:6.0.7-0ubuntu0.18.04.5, 1:6.0.7-0ubuntu0.18.04.6), libreoffice-gtk3:amd64 (1:6.0.7-0ubuntu0.18.04.5, 1:6.0.7-0ubuntu0.18.04.6), gnome-software-plugin-snap:amd64 (3.28.1-0ubuntu4.18.04.9, 3.28.1-0ubuntu4.18.04.10), update-notifier-common:amd64 (3.192.1.5, 3.192.1.7), libocct-data-exchange-7.3:amd64 (7.3.0-0ppa4~ubuntu18.04.1, 7.3.0+dfsg1-5~ubuntu18.04.1), libsystemd0:amd64 (237-3ubuntu10.19, 237-3ubuntu10.22), libsystemd0:i386 (237-3ubuntu10.19, 237-3ubuntu10.22), adobe-flash-properties-gtk:amd64 (1:20190409.1-0ubuntu0.18.04.1, 1:20190514.1-0ubuntu0.18.04.1), libgtk-3-common:amd64 (3.22.30-1ubuntu2, 3.22.30-1ubuntu3), linux-image-generic:amd64 (4.15.0.51.53, 4.15.0.52.54), apt:amd64 (1.6.10, 1.6.11), libgtk-3-0:amd64 (3.22.30-1ubuntu2, 3.22.30-1ubuntu3), libgtk-3-0:i386 (3.22.30-1ubuntu2, 3.22.30-1ubuntu3), openvpn:amd64 (2.4.4-2ubuntu1.1, 2.4.4-2ubuntu1.3), libgl1:amd64 (1.0.0-2ubuntu2.2, 1.0.0-2ubuntu2.3), libgl1:i386 (1.0.0-2ubuntu2.2, 1.0.0-2ubuntu2.3), libreoffice-core:amd64 (1:6.0.7-0ubuntu0.18.04.5, 1:6.0.7-0ubuntu0.18.04.6), debconf-i18n:amd64 (1.5.66, 1.5.66ubuntu1), python2.7-minimal:amd64 (2.7.15~rc1-1ubuntu0.1, 2.7.15-4ubuntu4~18.04), snapd:amd64 (2.37.4+18.04.1, 2.38+18.04), update-manager:amd64 (1:18.04.11.9, 1:18.04.11.10), freecad-runtime:amd64 (2:0.18.1+dfsg1~201904061907~ubuntu18.04.1, 2:0.18.1+dfsg1~201904300243~ubuntu18.04.1), libreoffice-gtk:amd64 (1:6.0.7-0ubuntu0.18.04.5, 1:6.0.7-0ubuntu0.18.04.6), libcephfs2:amd64 (12.2.11-0ubuntu0.18.04.1, 12.2.11-0ubuntu0.18.04.2), language-selector-common:amd64 (0.188.1, 0.188.2), papirus-icon-theme:amd64 (20190331-3213+pkg21~ubuntu18.04.1, 20190615-3356+pkg21~ubuntu18.04.1), libqmi-glib5:amd64 (1.18.0-3ubuntu1, 1.22.0-1.2~ubuntu18.04.1), gnome-software:amd64 (3.28.1-0ubuntu4.18.04.9, 3.28.1-0ubuntu4.18.04.10), liblibreofficekitgtk:amd64 (1:6.0.7-0ubuntu0.18.04.5, 1:6.0.7-0ubuntu0.18.04.6), libpython2.7:amd64 (2.7.15~rc1-1ubuntu0.1, 2.7.15-4ubuntu4~18.04), google-chrome-stable:amd64 (73.0.3683.103-1, 75.0.3770.100-1), python2.7:amd64 (2.7.15~rc1-1ubuntu0.1, 2.7.15-4ubuntu4~18.04), ubuntu-standard:amd64 (1.417, 1.417.1), console-setup-linux:amd64 (1.178ubuntu2.7, 1.178ubuntu2.9), libnuma1:amd64 (2.0.11-2.1, 2.0.11-2.1ubuntu0.1), libnuma1:i386 (2.0.11-2.1, 2.0.11-2.1ubuntu0.1), ubuntu-desktop:amd64 (1.417, 1.417.1), libmutter-2-0:amd64 (3.28.3-2~ubuntu18.04.2, 3.28.4-0ubuntu18.04.1), python-apt-common:amd64 (1.6.3ubuntu1, 1.6.4), libgnome-bluetooth13:amd64 (3.28.0-2ubuntu0.1, 3.28.0-2ubuntu0.2), blender-data:amd64 (2.79.b+dfsg0-1, 2.79.b+dfsg0-1ubuntu1.18.04.1), plymouth-label:amd64 (0.9.3-1ubuntu7.18.04.1, 0.9.3-1ubuntu7.18.04.2), libaio1:amd64 (0.3.110-5, 0.3.110-5ubuntu0.1), nordvpn:amd64 (2.2.0-3, 3.1.0-6), skypeforlinux:amd64 (8.34.0.78, 8.47.0.59), udev:amd64 (237-3ubuntu10.19, 237-3ubuntu10.22), console-setup:amd64 (1.178ubuntu2.7, 1.178ubuntu2.9), cups-server-common:amd64 (2.2.7-1ubuntu2.4, 2.2.7-1ubuntu2.6), plymouth-theme-ubuntu-text:amd64 (0.9.3-1ubuntu7.18.04.1, 0.9.3-1ubuntu7.18.04.2), passwd:amd64 (1:4.5-1ubuntu1, 1:4.5-1ubuntu2), libgles2:amd64 (1.0.0-2ubuntu2.2, 1.0.0-2ubuntu2.3), libwww-perl:amd64 (6.31-1, 6.31-1ubuntu0.1), cups-common:amd64 (2.2.7-1ubuntu2.4, 2.2.7-1ubuntu2.6), libapt-pkg5.0:amd64 (1.6.10, 1.6.11), gnome-bluetooth:amd64 (3.28.0-2ubuntu0.1, 3.28.0-2ubuntu0.2), software-properties-gtk:amd64 (0.96.24.32.7, 0.96.24.32.9), initramfs-tools-bin:amd64 (0.130ubuntu3.7, 0.130ubuntu3.8), python3-uno:amd64 (1:6.0.7-0ubuntu0.18.04.5, 1:6.0.7-0ubuntu0.18.04.6), libocct-visualization-7.3:amd64 (7.3.0-0ppa4~ubuntu18.04.1, 7.3.0+dfsg1-5~ubuntu18.04.1), libudev1:amd64 (237-3ubuntu10.19, 237-3ubuntu10.22), libudev1:i386 (237-3ubuntu10.19, 237-3ubuntu10.22), adobe-flashplugin:amd64 (1:20190409.1-0ubuntu0.18.04.1, 1:20190514.1-0ubuntu0.18.04.1), mutter-common:amd64 (3.28.3-2~ubuntu18.04.2, 3.28.4-0ubuntu18.04.1), libplymouth4:amd64 (0.9.3-1ubuntu7.18.04.1, 0.9.3-1ubuntu7.18.04.2), nplan:amd64 (0.40.1~18.04.4, 0.97-0ubuntu1~18.04.1), libgeocode-glib0:amd64 (3.25.4.1-4, 3.25.4.1-4ubuntu0.18.04.1), libreoffice-style-galaxy:amd64 (1:6.0.7-0ubuntu0.18.04.5, 1:6.0.7-0ubuntu0.18.04.6), libreoffice-base-core:amd64 (1:6.0.7-0ubuntu0.18.04.5, 1:6.0.7-0ubuntu0.18.04.6), freecad-common:amd64 (2:0.18.1+dfsg1~201904061907~ubuntu18.04.1, 2:0.18.1+dfsg1~201904300243~ubuntu18.04.1), ubuntu-minimal:amd64 (1.417, 1.417.1), libreoffice-ogltrans:amd64 (1:6.0.7-0ubuntu0.18.04.5, 1:6.0.7-0ubuntu0.18.04.6), libreoffice-impress:amd64 (1:6.0.7-0ubuntu0.18.04.5, 1:6.0.7-0ubuntu0.18.04.6), libgtk-3-bin:amd64 (3.22.30-1ubuntu2, 3.22.30-1ubuntu3), python3-distupgrade:amd64 (1:18.04.30, 1:18.04.33), python3-debconf:amd64 (1.5.66, 1.5.66ubuntu1), cups-ppdc:amd64 (2.2.7-1ubuntu2.4, 2.2.7-1ubuntu2.6), libsysmetrics1:amd64 (1.3.0~18.04, 1.3.1), ubuntu-software:amd64 (3.28.1-0ubuntu4.18.04.9, 3.28.1-0ubuntu4.18.04.10), python3-update-manager:amd64 (1:18.04.11.9, 1:18.04.11.10), libcupsmime1:amd64 (2.2.7-1ubuntu2.4, 2.2.7-1ubuntu2.6), ubuntu-release-upgrader-core:amd64 (1:18.04.30, 1:18.04.33), im-config:amd64 (0.34-1ubuntu1.2, 0.34-1ubuntu1.3), gir1.2-gnomebluetooth-1.0:amd64 (3.28.0-2ubuntu0.1, 3.28.0-2ubuntu0.2), libnss-myhostname:amd64 (237-3ubuntu10.19, 237-3ubuntu10.22), libneon27-gnutls:amd64 (0.30.2-2build1, 0.30.2-3~ubuntu18.04.1), systemd-sysv:amd64 (237-3ubuntu10.19, 237-3ubuntu10.22), libldap-common:amd64 (2.4.45+dfsg-1ubuntu1.1, 2.4.45+dfsg-1ubuntu1.2), libocct-modeling-algorithms-7.3:amd64 (7.3.0-0ppa4~ubuntu18.04.1, 7.3.0+dfsg1-5~ubuntu18.04.1), ure:amd64 (6.0.7-0ubuntu0.18.04.5, 6.0.7-0ubuntu0.18.04.6), gnome-shell-common:amd64 (3.28.3+git20190124-0ubuntu18.04.2, 3.28.4-0ubuntu18.04.1), libreoffice-writer:amd64 (1:6.0.7-0ubuntu0.18.04.5, 1:6.0.7-0ubuntu0.18.04.6), python-apt:amd64 (1.6.3ubuntu1, 1.6.4), ubuntu-core-launcher:amd64 (2.37.4+18.04.1, 2.38+18.04), libmm-glib0:amd64 (1.6.8-2ubuntu1, 1.10.0-1~ubuntu18.04.2), libpam-systemd:amd64 (237-3ubuntu10.19, 237-3ubuntu10.22), libgail-3-0:amd64 (3.22.30-1ubuntu2, 3.22.30-1ubuntu3), libreoffice-common:amd64 (1:6.0.7-0ubuntu0.18.04.5, 1:6.0.7-0ubuntu0.18.04.6), python3-lib2to3:amd64 (3.6.7-1~18.04, 3.6.8-1~18.04), gedit-common:amd64 (3.28.1-1ubuntu1.1, 3.28.1-1ubuntu1.2), libglx0:amd64 (1.0.0-2ubuntu2.2, 1.0.0-2ubuntu2.3), libglx0:i386 (1.0.0-2ubuntu2.2, 1.0.0-2ubuntu2.3), systemd:amd64 (237-3ubuntu10.19, 237-3ubuntu10.22), libmbim-proxy:amd64 (1.14.2-2.1ubuntu1, 1.18.0-1~ubuntu18.04.1), freecad:amd64 (2:0.18.1+dfsg1~201904061907~ubuntu18.04.1, 2:0.18.1+dfsg1~201904300243~ubuntu18.04.1), login:amd64 (1:4.5-1ubuntu1, 1:4.5-1ubuntu2), libssl-doc:amd64 (1.1.0g-2ubuntu4.3, 1.1.1-1ubuntu2.1~18.04.2), apt-utils:amd64 (1.6.10, 1.6.11), libnss-systemd:amd64 (237-3ubuntu10.19, 237-3ubuntu10.22), keyboard-configuration:amd64 (1.178ubuntu2.7, 1.178ubuntu2.9), plymouth:amd64 (0.9.3-1ubuntu7.18.04.1, 0.9.3-1ubuntu7.18.04.2), bash:amd64 (4.4.18-2ubuntu1, 4.4.18-2ubuntu1.1), gnome-control-center-faces:amd64 (1:3.28.2-0ubuntu0.18.04.3, 1:3.28.2-0ubuntu0.18.04.4), linux-image-extra-virtual:amd64 (4.15.0.51.53, 4.15.0.52.54), libocct-foundation-7.3:amd64 (7.3.0-0ppa4~ubuntu18.04.1, 7.3.0+dfsg1-5~ubuntu18.04.1), ubuntu-release-upgrader-gtk:amd64 (1:18.04.30, 1:18.04.33), fonts-opensymbol:amd64 (2:102.10+LibO6.0.7-0ubuntu0.18.04.5, 2:102.10+LibO6.0.7-0ubuntu0.18.04.6), libcupsppdc1:amd64 (2.2.7-1ubuntu2.4, 2.2.7-1ubuntu2.6), python3-tk:amd64 (3.6.7-1~18.04, 3.6.8-1~18.04), libpython2.7-minimal:amd64 (2.7.15~rc1-1ubuntu0.1, 2.7.15-4ubuntu4~18.04), unattended-upgrades:amd64 (1.1ubuntu1.18.04.10, 1.1ubuntu1.18.04.11), libreoffice-pdfimport:amd64 (1:6.0.7-0ubuntu0.18.04.5, 1:6.0.7-0ubuntu0.18.04.6), modemmanager:amd64 (1.6.8-2ubuntu1, 1.10.0-1~ubuntu18.04.2), libocct-modeling-data-7.3:amd64 (7.3.0-0ppa4~ubuntu18.04.1, 7.3.0+dfsg1-5~ubuntu18.04.1), uno-libs3:amd64 (6.0.7-0ubuntu0.18.04.5, 6.0.7-0ubuntu0.18.04.6), gnome-shell:amd64 (3.28.3+git20190124-0ubuntu18.04.2, 3.28.4-0ubuntu18.04.1), cups-bsd:amd64 (2.2.7-1ubuntu2.4, 2.2.7-1ubuntu2.6), libreoffice-style-tango:amd64 (1:6.0.7-0ubuntu0.18.04.5, 1:6.0.7-0ubuntu0.18.04.6), apt-transport-https:amd64 (1.6.10, 1.6.11), gtk-update-icon-cache:amd64 (3.22.30-1ubuntu2, 3.22.30-1ubuntu3), cups-core-drivers:amd64 (2.2.7-1ubuntu2.4, 2.2.7-1ubuntu2.6), cups-daemon:amd64 (2.2.7-1ubuntu2.4, 2.2.7-1ubuntu2.6), language-selector-gnome:amd64 (0.188.1, 0.188.2), plymouth-theme-ubuntu-logo:amd64 (0.9.3-1ubuntu7.18.04.1, 0.9.3-1ubuntu7.18.04.2), libreoffice-gnome:amd64 (1:6.0.7-0ubuntu0.18.04.5, 1:6.0.7-0ubuntu0.18.04.6), ubuntu-report:amd64 (1.3.0~18.04, 1.3.1), libcupsimage2:amd64 (2.2.7-1ubuntu2.4, 2.2.7-1ubuntu2.6), libpython2.7-stdlib:amd64 (2.7.15~rc1-1ubuntu0.1, 2.7.15-4ubuntu4~18.04), libreoffice-calc:amd64 (1:6.0.7-0ubuntu0.18.04.5, 1:6.0.7-0ubuntu0.18.04.6), python3-gdbm:amd64 (3.6.7-1~18.04, 3.6.8-1~18.04), cups:amd64 (2.2.7-1ubuntu2.4, 2.2.7-1ubuntu2.6), libcupscgi1:amd64 (2.2.7-1ubuntu2.4, 2.2.7-1ubuntu2.6), gnome-software-common:amd64 (3.28.1-0ubuntu4.18.04.9, 3.28.1-0ubuntu4.18.04.10), cups-client:amd64 (2.2.7-1ubuntu2.4, 2.2.7-1ubuntu2.6), cups-ipp-utils:amd64 (2.2.7-1ubuntu2.4, 2.2.7-1ubuntu2.6), libmbim-glib4:amd64 (1.14.2-2.1ubuntu1, 1.18.0-1~ubuntu18.04.1), update-notifier:amd64 (3.192.1.5, 3.192.1.7), linux-generic:amd64 (4.15.0.51.53, 4.15.0.52.54), librados2:amd64 (12.2.11-0ubuntu0.18.04.1, 12.2.11-0ubuntu0.18.04.2), initramfs-tools-core:amd64 (0.130ubuntu3.7, 0.130ubuntu3.8), initramfs-tools:amd64 (0.130ubuntu3.7, 0.130ubuntu3.8), freecad-python3:amd64 (2:0.18.1+dfsg1~201904061907~ubuntu18.04.1, 2:0.18.1+dfsg1~201904300243~ubuntu18.04.1), libreoffice-draw:amd64 (1:6.0.7-0ubuntu0.18.04.5, 1:6.0.7-0ubuntu0.18.04.6), python3-apt:amd64 (1.6.3ubuntu1, 1.6.4), libreoffice-avmedia-backend-gstreamer:amd64 (1:6.0.7-0ubuntu0.18.04.5, 1:6.0.7-0ubuntu0.18.04.6), mutter:amd64 (3.28.3-2~ubuntu18.04.2, 3.28.4-0ubuntu18.04.1), teamviewer:amd64 (14.2.2558, 14.3.4730), libglvnd0:amd64 (1.0.0-2ubuntu2.2, 1.0.0-2ubuntu2.3), libglvnd0:i386 (1.0.0-2ubuntu2.2, 1.0.0-2ubuntu2.3), software-properties-common:amd64 (0.96.24.32.7, 0.96.24.32.9)
End-Date: 2019-06-19  01:02:15

    Regards

  • 0 in reply to desouza
    Expert 1060 points

    Hi Desouza, 

    I think I found the cause and fix/workaround. I would appreciate if you can replicate and maybe it will help for finding a permanent solution.

    From what I read if the ModemManager filter is set to strict it will not follow the udev rule that tells it to ignore the device.

    This is the specific line inside 71-ti-permissions.rules that will be ignored.

    ATTRS{idVendor}=="0451",ATTRS{idProduct}=="bef0",ENV{ID_MM_DEVICE_IGNORE}="1" 

    1. Check if ModemManager filter is set to strict .
      sudo systemctl status ModemManager.service 

      ● ModemManager.service - Modem Manager 
      Loaded: loaded (/lib/systemd/system/ModemManager.service; enabled; vendor preset: enabled) 
      Active: active (running) since .....
      CGroup: /system.slice/ModemManager.service └─889 /usr/sbin/ModemManager --filter-policy=strict

    2. I highlighted the filter-policy and service path in the above lines. IF the rule is set to strict change it to default by editing the service file.

      sudo nano /lib/systemd/system/ModemManager.service
      ExecStart=/usr/sbin/ModemManager --filter-policy=default

    3. Reload the systemd service, restart ModemManager. I also rebooted my system just in case.

      sudo systemctl daemon-reload
sudo systemctl restart ModemManager

    4. Test the debug probe 

      ./xds2xx_conf get xds2xxu 0
      boardRev=2
      ipAddress=0.0.0.0
      ipConfig=dhcp
      ipGateway=255.255.255.255
      ipNetmask=255.255.255.255
      productClass=XDS2XX
      productName=XDS200
      serialNum=00:0E:99:03:90:93
      swRev=1.0.0.8
      hostCPU=AM1802
      emuCtrlType=Bit bang
      extMemType=SDRAM
      portUSB=true
      portENET=false
      portWIFI=false
      portRS232=false
      EnableUSBSerial=false
      CurrentMeasure=false
  • 0 in reply to LazyHD
    Guru 92251 points

    LazyHD said:
    I think I found the cause and fix/workaround. I would appreciate if you can replicate and maybe it will help for finding a permanent solution.

    I tried your workaround of changing the ModemManager filter-policy from strict to default on a Ubuntu 18.04.2 LTS system, and the work-around allows xds2xx_conf and the CCS 9.1 debugger to reliably connect to a XDS200 mezzanine emulator.

    Thanks for posting the work-around.

  • 0 in reply to LazyHD
    TI__Guru**** 168317 points

    Hi,

    Similar story here: the workaround works just fine on my Ubuntu 18.04.2 here as well. 

    Thank you for posting this. I will append this information to the bug report. 

    Best regards,

    Rafael

  • 0 in reply to LazyHD
    TI__Intellectual 2515 points

    Note that this has been filed as a bug against Ubuntu:

    https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1827328

    Although, I've seen much older discussions about the issue where the filter policy strict triggered this problem.  

    It is unlikely ModemManager is holding the XDS200 and blocking use.  What I've seen is that ModemManager is probing the XDS200 to see if it's a modem, and that's causing the packet handler inside the XDS200 to lock up.  It appears to happen at the low level firmware layer, so it's not going to be a quick fix.  Meanwhile, setting the filter policy to default or paranoid appears to work.