CC3220SF: dslite.sh cannot connect to CC3220SF using MacOS.

Hi Steve,

This issue is different from the one in the thread you linked, but we have seen it reported recently. I will have to check with the tools team on the status. I should have an update in 1-2 days.

Best regards,

Sarah

Hi Sara,

Any word yet from the tools team on any MacOS dslite.sh workaround/fix? By the way, today I encountered yet other failure with dslite.sh and I have 4 screen shots that I've annotated that clearly show this additional issue and should make it easy for the tools team to reproduce the failure. I'll try the "insert file" icon of this posting to attach the four screen shots below. Here goes...

Thanks in advance,

Steve

Four Screen Shots Below:

Hi Steve,

Sorry for the delay. Can you try the same command as above, but without  the --port option? ImageCreator should be able to detect the port.

Also, to flash a .sli file, you should be using the ImageCreator GUI via the Serial (not bootloader) option in UniFlash. See the UniFlash ImageCreator user's guide or the ImageCreator Basics training.

Best regards,

Sarah

Hi Sara,

This is the way I use UniFlash to flash *.sli images over serial to my board all the time. In fact in my screen shots provided I show how that works. The issue is when trying to generate the dslite.sh command line. Instead of me doing various experiments that you mentioned (and I wasn't sure exactly what you meant) -- can you instead have the tools team reproduce my issue(s) and debug and experiment with possible workarounds? Thanks!

Steve

Hi Sara,

On second reading I guess your comment about removing the --port was for the first issue I spoke about, ok, yes, I tried that just now as you recommended and get the following failure: Maybe the tools team can attempt this dslite.sh command (as well as the second dslite.sh issue I brought up) and see if they get similar failures using MacOs Catalina 10.15.7. Thanks!

% /Applications/ti_09_2020/uniflash_6.1.0/dslite.sh --mode cc32xx device info
Executing the following command:
> ./SLImageCreator device info

For more details and examples, please refer to the UniFlash Quick Start guide.

Config file (cfg.json) doesn't exist, using defaults
INFO:root:FTDI not detected, trying XDS
INFO:root:
Error: SLImageCreator.exe: XDS not detected
Traceback (most recent call last):
  File "SLImageCreator.py", line 5191, in <module>
  File "SLImageCreator.py", line 5187, in main
  File "SLImageCreator.py", line 5159, in cmdline
  File "SLImageCreator.py", line 4785, in command_device_info
  File "SLImageCreator.py", line 1554, in connect_device
  File "slutils/slutils.py", line 251, in auto_detect
slutils.slutils.DeviceError:
Error: SLImageCreator.exe: Auto detect failure
[15530] Failed to execute script SLImageCreator
Kranz@SteveAndJudyKranzs-MacBook-Pro Manufacturing %

Hi Steve,

Thanks for testing without the port option. It worked on our setup, but there may be another reason your device is not detected. Are you using a LaunchPad or custom board? If you have other USB devices plugged in, can you test without?

We have reproduced the ioctl issue, but the tools team is still determining the cause.

I misunderstood your first screenshot, and I thought you were seeing an issue with the other method as well.

Best regards,

Sarah

Hi Sara,

You asked about my setup -- I've never had any other USB devices plugged in while attempting the failing dslite.sh commands. We are connecting to a custom board that is very much like LaunchPad and in fact using the UniFlash tool / and CCS debugger have been connecting, downloading, running our system. The transition to using dslite.sh for some of these steps has been the difficultly (MacOs).

Thanks, Steve

Hi Steve,

What tool are you using to connect the board for flashing? Are you using a XDS or FTDI platform?

Best regards,

Sarah

Hi Sara,

I have been using a direct FTDI connection to our CC3220SF board. This has been successful for flashing *.sli images only when using the UniFlash GUI and the SOP jumper installed on the board. This direct FTDI connection, however, has not allowed us to use the following sort of command methods:

/Applications/ti/uniflash_6.1.0/dslite.sh --mode cc32xx device info

/Applications/ti/uniflash_6.1.0/dslite.sh --mode cc32xx image program --file SLI_Programming.sli

Since my last post I have installed the TI tools at the default location “/Applications/ti/…” and this has not corrected the issue. Also, I have migrated my MacBook to the recently released BigSur OS and this also hasn’t made any difference. One thing that does make a difference is if we instead use the XDS110 interface. In this case the two dslite.sh commands I show above do work. Here is an example.

/Applications/ti/uniflash_6.1.0/dslite.sh --mode cc32xx device info

Executing the following command:

> ./SLImageCreator device info

For more details and examples, please refer to the UniFlash Quick Start guide.

Config file (cfg.json) doesn't exist, using defaults

INFO:root:FTDI not detected, trying XDS

INFO:slbootloader.slbootloader:Connecting to device

INFO:slbootloader.slbootloader:Power off

INFO:slbootloader.slbootloader:Set break signal

INFO:slbootloader.slbootloader:Power on

INFO:slbootloader.slbootloader:Clear break signal

INFO:slbootloader.slbootloader:Connection succeeded

INFO:slbootloader.slbootloader:Received storage list

Device Info  :

Type         : CC3220SF

Secure       : True

MAC          : c8:df:84:42:49:7c

PROG MAC     : None

HW Version   : 0x31

Again, using the FTDI with the UniFlash GUI does work but does not work with the dslite.sh command line method. And this includes all the screen shots I showed earlier for generating the “standalone package” from Uniflash (uniflash_osx.zip); That still does not work even with the XDS110 interface. I hope this information helps the tools team with their debug of the issue.

Thanks,

Steve K.

Hi Steve,

The tools team did find an issue with the FTDI drivers on Mac. In the meantime, are you able to use your XDS110 to continue development?

Best regards,

Sarah

Hi Sara,

Yes, I have the XDS110 board interaction as a workaround and can proceed with my MacOS based development. Thanks for asking...

Steve K.

Sara,

Correct, I have the XDS110 board interaction as a workaround and can proceed with my MacOS based development. Thanks for asking...

Steve.