CCS/CC1310: Still can't get XDS200 to work with OSX Catalina- work arounds fail

Hi,

I can't seem to be able to reproduce this issue on my setup here. To me the terminal shows the following:

terminal said:

Last login: Wed Apr 29 16:49:24 on ttys000

The default interactive shell is now zsh.
To update your account to use zsh, please run `chsh -s /bin/zsh`.
For more details, please visit support.apple.com/.../HT208050.
SDOs-MacBook-Pro:~ SDO$ ls /dev/cu.usbmodem1410*
/dev/cu.usbmodem14101 /dev/cu.usbmodem14103
SDOs-MacBook-Pro:~ SDO$ ls /dev/tty.usbmodem1410*
/dev/tty.usbmodem14101 /dev/tty.usbmodem14103
SDOs-MacBook-Pro:~ SDO$

And the output of the xds2xx_conf (which accesses the XDS200 at the lowest level possible) indicates the port is accessible

terminal said:

SDOs-MacBook-Pro:~ SDO$ cd /Applications/ti/ccs1000/ccs/ccs_base/common/uscif/xds2xx
SDOs-MacBook-Pro:xds2xx SDO$ ./xds2xx_conf get xds2xxu 0x14101
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.9
hostCPU=AM1802
emuCtrlType=Bit bang
extMemType=SDRAM
portUSB=true
portENET=false
portWIFI=false
portRS232=false
EnableUSBSerial=true
CurrentMeasure=false

With this in mind, I see you mentioned just one CDC port number. Is there another port number as well? The XDS200 should instantiate two. 

By the way, the serial number to be passed to CCS is the one shown in the option serialNum in the output of the xds2xx_conf command above. 

Both methods worked for me, so I am unsure what may be happening. 

I will try to "break" my system here, but a fix for this issue is scheduled to be released in May. 

Regards,

Rafael

The serial number I quoted is the lower-numbered of two closely-numbered ones instantiated in /dev, per the instructions. 

Interestingly, upon (unrelated) restart of my laptop, I get similar but different numbers:

/dev/tty.usbmodem14201 and 14203 are what I get for the XDS200.

previously, the numbers were 1417201 and '203. . . . unless I was just crosseyed that day 

In this case, I was able to get the serial number from xdx200conf

bash-3.2$ ./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-000E9904480B

swRev=1.0.0.8

hostCPU=AM1802

emuCtrlType=Bit bang

extMemType=SDRAM

portUSB=true

portENET=false

portWIFI=false

portRS232=false

EnableUSBSerial=false

CurrentMeasure=false

It's odd that the serial number printed on the device housing itself has no relationship to this number.

Anyway, I put the S200-000E9904480B in the serial number field in CCS9 (9.3.0.00012)

and tried to test configuration:

-----[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:-1727772661)

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]

... still doesn't work, even though xds2xx_conf could talk to it.

I happen to have an XDS110v3 as well, which works as-is, so I'm using that instead of spending any more time diagnosing the XDS200, even though I like the 200 better since it appears to operate faster as well as being physically smaller on my crowded desk.

I look forward to the fix and hope it solves my problem. I'm going to just use my 110 for now.

Trying this again today, no other XDS devices connected. 

ls /dev/*usb* --> nothing, as expected

plug in XDS200

$ ls -l /dev/*usb*

crw-rw-rw- 1 root wheel 18, 1 May 5 12:57 /dev/cu.usbmodem1417201

crw-rw-rw- 1 root wheel 18, 3 May 5 12:57 /dev/cu.usbmodem1417203

crw-rw-rw- 1 root wheel 18, 0 May 5 12:57 /dev/tty.usbmodem1417201

crw-rw-rw- 1 root wheel 18, 2 May 5 12:57 /dev/tty.usbmodem1417203

1417201 is my number, the lower of the pair, right?

./xds2xx_conf get xds2xxu 0x1417201 Error : Failed to open port connection : xds2xxu : 0x417201 Error : test failed

I note with interest that the "failed to open" port is shown as 6 hex digits, whereas the number given to me by OSX is 7 digits, starting with a 1 that the xds2xx_conf failed to echo in its error message.

A previous attempt didn't have that leading 1 - my machine has restarted since. 

The success I had the other day with xds2xx_conf was when the serial port number was only 6 digits wide. Today it is 7 for reasons I cannot explain, but that's what OSX tells me it is today. I tried moving the XDS200 to direct to my laptop rather than through a hub and presto, a 5-digit address (14201) and xdsxx_conf can suddenly talk to it. That's interesting.

It seems to me there is more than one issue here, one of which being xds2xx_conf has a shorter address capacity than OSX has for attached devices.

Taking advantage of the shorter address, now this worked:

./xds2xx_conf set xds2xxu 0x14201 EnableUSBSerial=true

and get reported my setting took:

:

EnableUSBSerial=true

:

which was encouraging.

So I went back to CCS9, entered my serial S200-000E9904480B in the connection properties, leaving the device connected exactly where it was such that xds2xx_conf could see it, same place it was where EnableUSBSerial worked and was confirmed, set connection props in CCS9 to "select by serial number", then tried to test it.

Still fails with 

The value is '-250' (0xffffff06).
The title is 'SC_ERR_ECOM_EMUNAME'.

Back to the XDS110v3, which works.

Hi, 

Thanks for reporting the Hub scenario; I will inform the developer. 

Regardless, you can still use the hex port number in CCS, just set it to the parameters below.

Regards,

Rafael