• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 882 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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/TMS320F280049: XDS200USB - Failure to connect with CCS 10.0.0 on OS X Catalina 10.15.4

Leland Williams
Prodigy 70 points
Part Number: TMS320F280049
Other Parts Discussed in Thread: AM1802

Tool/software: Code Composer Studio

I am not able to get CCS to connect to a XDS200 debug probe when running v10.0.0 on OS X Catalina (10.15.4)

Here's what I know:

The XDS200 worked fine on OS X Mojave and CCS9

Failure occurs during the connection phase

XDS200 appears to properly enumerate when looking at the System Report. There aren't any obvious errors in the System Log.

Performing a connection test in Target Configurations indicates an error returned from the USCIF driver

Probing for information with xds2xx_conf from the terminal returns a failure to connect

Two ttyusb devices appear in /dev when the XDS200 is connected to the laptop

The same XDS200 connected to a Windows 10 VM running on top of OS X works fine

Using the mentioned VM, I was able to successfully update the firmware using 'update_xds2xx.sh' on the the XDS200 to v1.0.0.9 without trouble, but afterwards it still doesn't connect to CCS on OS X

An XDS110 works fine on the same platform

All updates to CCS for C2000 and emulators have been applied

I'm looking for any and all information that will allow me to use my XDS200 on OS X Catalina

I have granted full disk access to CCS in the Security Preferences

Thanks!

  • 0
    TI__Guru**** 171044 points

    Hi, 

    I am seeing the same issue as you and it does not seem locked to CCSv10.0.0 or the firmware 1.0.0.9 - I see the same issue with Catalina version 10.15.3 and several versions back to 7.4. 

    This has happened in the past with one of the OS updates: basically the port mapping is not working very well, requiring to use the direct address instead. 

    To find out the address, you can either open the System Information and check the first 16 bits of the property "Location ID" or open a terminal and list the CDC modem devices:

    terminal said:

    SDOs-MacBook-Pro:20200327095300 SDO$ ls -l /dev/cu.*
    crw-rw-rw- 1 root wheel 18, 1 Mar 27 09:46 /dev/cu.Bluetooth-Incoming-Port
    crw-rw-rw- 1 root wheel 18, 25 Mar 27 10:59 /dev/cu.usbmodem14201
    crw-rw-rw- 1 root wheel 18, 23 Mar 27 10:59 /dev/cu.usbmodem14203
    crw-rw-rw- 1 root wheel 18, 19 Mar 27 10:46 /dev/cu.usbmodem765432101
    crw-rw-rw- 1 root wheel 18, 21 Mar 27 10:46 /dev/cu.usbmodem765432104

    As you can tell above, multiple CDC devices may exist and therefore I recommend either removing all but the XDS200 or testing each one. One detail: the Debug Probe is always the first instance of the pair assigned to a specific address range. 

    terminal said:

    SDOs-MacBook-Pro:xds2xx SDO$ sudo ./xds2xx_conf get xds2xxu 0x14201
    boardRev=1
    ipAddress=0.0.0.0
    ipConfig=dhcp
    ipGateway=0.0.0.0
    ipNetmask=0.0.0.0
    productClass=XDS2XX
    productName=XDS200
    serialNum=S200-000E990394B1
    swRev=1.0.0.8
    hostCPU=AM1802
    emuCtrlType=Bit bang
    extMemType=SDRAM
    portUSB=true
    portENET=false
    portWIFI=false
    portRS232=false
    EnableUSBSerial=true
    CurrentMeasure=false
    SDOs-MacBook-Pro:xds2xx SDO$

    By adding this parameter to the Debug Port I/O Port Number of the Advanced tab of the target configuration file, you can make it work from inside CCS. Keep in mind that the port number may change with the USB port connected. 

    I'll try to check the alternatives for the port mapping issue and file a bug report.

    This issue does not affect other debug probes such as the XDS100 or XDS110.

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Prodigy 70 points

    Wow, thanks! This makes some sense - the driver is making some assumptions about udev and device names that aren't quite true. I'll give your work around a try later and report back.

  • 0 in reply to Leland Williams
    TI__Guru**** 171044 points

    Hi,

    I filed the bug report EXT_EP-9758. Please check its status in the link SIR in my signature below. 

    I apologize for the inconvenience,

    Rafael