TMS320F28335: MacOS long debug problem

Hi,

Dominik Busler said:

Hi, lately i was trying to debug a project on MacBook Air M1 with CCS 12.8.1 and i stumbled upon a problem - debug takes extremely long (up to 20 minutes). I’ve seen similar thread but it was closed due to use of old debug probe (xds100v1). I am using xds100v2 and the problem persists. 

Can you tell which step is taking so long? Is it the flash erase/write? 

If you are only programming RAM, is it faster? 

Thanks,

Ben Collier

Thank you for the reply! It hangs for few minutes on GEL Expression: OnReset(0) and GEL Expression: OnTargetConnect, as well as on program loading. After 15-20 minutes program loads and works fine. Only programming ram doesn’t make it faster.

Hi,

Can you try disabling the GEL file? 

Thanks,

Ben Collier

Hi, after disabling GEL file the process takes 5 minutes.

I also tried to test connection in target config file and i get the -150 ftdi driver error. 

Hi,

Dominik Busler said:

I also tried to test connection in target config file and i get the -150 ftdi driver error. 

You fail test connection but you can still connect after a long period of time? I wonder if this has to do with MAC OS somehow, I will loop in a different expert.

Best Regards,

Ben Collier 

I tried on my macbook Air M1 processor running sequoia 15.5 with an F28035 connected via an XDS100v2 debug probe. I launched a debug session for an example project from C2000Ware. It took less than 10 seconds to launch the debugger, connect to the target, and load the program to main.

I wonder if there is some security software that is impacting things. Would it be possible to temporarily disable all antivirus/security software and see if that helps?

Dominik Busler said:

I also tried to test connection in target config file and i get the -150 ftdi driver error. 

Did you try testing the connection while in an active debug session? If so, then that error would be expected since the active debug session has control of the XDS100.

Thanks

ki

Thanks for your reply.

Ki said:

I wonder if there is some security software that is impacting things. Would it be possible to temporarily disable all antivirus/security software and see if that helps?

I don't use any antivirus software and have disabled every macOS firewall with no effect.

Ki said:

Did you try testing the connection while in an active debug session? If so, then that error would be expected since the active debug session has control of the XDS100.

I tried testing both during a debug session and outside of debug. 
When the debug session is running, I get the error: 

This error is generated by TI's USCIF driver or utilities.

The value is '-151' (0xffffff69).
The title is 'SC_ERR_FTDI_OPEN'.

The explanation is:
One of the FTDI driver functions used during the connect
returned bad status or an error. The cause may be one or
more of: no XDS100 is plugged in, invalid XDS100 serial number,
blank XDS100 EEPROM, missing FTDI drivers, faulty USB cable.
Use the xds100serial command-line utility in the 'common/uscif'
folder to verify the XDS100 can be located.

[End: Texas Instruments XDS100v2 USB Debug Probe_0]

An error occurred while hard 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 '-150' (0xffffff6a).
The title is 'SC_ERR_FTDI_FAIL'.

The explanation is:
One of the FTDI driver functions used during
configuration returned a invalid status or an error.

[End: Texas Instruments XDS100v2 USB Debug Probe_0]

and the debug works anyway, and after 5-10 minutes, loads the program correctly.

Another thing I can think about is that I am using an adapter from usb C to usb A and not a direct C-B cable. Do you think it may be the reason?

Dominik Busler said:

Another thing I can think about is that I am using an adapter from usb C to usb A and not a direct C-B cable. Do you think it may be the reason?

I don't think so. I also have used a bunch of adapters. 

I recently used a usb A to mini cable along with this USB C hub to connect my XDS100v2 to my macbook. I've also used A-C adapters without issue. 

The issue really sounds more like a potential issue with the security software running in your macbook. Did you try disabling it? 

Ki said:

The issue really sounds more like a potential issue with the security software running in your macbook. Did you try disabling it? 

Yeah, I tried disabling security in settings, and I don't have any third-party security apps. It didn't help. Later, I can try disabling whole system integrity protection in recovery mode, but I don't think it will fix anything

I am at a loss on what is happening. We have several Mac Mx machines and have not seen this issue. I do acknowledge slow flashing performance over XDS100v2 but not for RAM. Even for the flashing it should never take that long. 

Can you generate a Debug Server Log of the issue, zip the log and attach the zip to this thread?

https://software-dl.ti.com/ccs/esd/documents/ccs_diagnostic-logs.html

Thanks

ki