• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 83 subscribers
  • Views 171 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.

Original question:

TMS320F28335: MacOS long debug problem

TMS320F28335: MacOS long debug time

Dominik Busler
Prodigy 20 points
Part Number: TMS320F28335
Other Parts Discussed in Thread: TMS320F28035

Tool/software:

Hi, due to some health issues, I was unable to respond to the original thread in time before it was locked. 
The issue persists, and as was requested, I am providing a debug log file. The project I am running now is just an empty project with "return 0;" in main function.

The summary of original thread:

Problem: 
Long debug time (up to 10 minutes) while debugging TMS320F28335 project on MacBook Air M1 with CCS 12.8.1 through xds100v2 debug probe.
The connection test gives: "-150 ftdi driver error." and after few minutes of debugging program loads despite that error.
I tried: 
- disabling gel file
- programming RAM only
- disabling macos security software
all with no effect.


Debug Server Log.zip

  • 0
    TI__Mastermind 19561 points

    Hi Dominik,

    Let me inform the people from the original thread about this, please allow them some time to respond

    Regards,

    Peter

  • 0
    TI__Guru**** 473001 points
    Dominik Busler said:
    Long debug time (up to 10 minutes) while debugging TMS320F28335 project on MacBook Air M1 with CCS 12.8.1 through xds100v2 debug probe.

    I tried a similar setup - TMS320F28035 project on a MacBook Air M1 running Sequoia 15.5 with CCS 12.8.1 through an XDS100v2 debug probe. Both loading to RAM and FLASH seemed fine. Are you loading to RAM? If not, can you give that a try and see if you have the same issues?

    Dominik Busler said:
    The connection test gives: "-150 ftdi driver error." and after few minutes of debugging program loads despite that error.

    This is odd because the error indicates some issue with the USB communication between the FTDI chip on the XDS100 and the CCS debugger. This is typically an unrecoverable error but the fact that it will eventually load after a long time is confusing to me. I will have engineering take a look at your log.

    Thanks

    ki

  • 0 in reply to Ki
    TI__Guru**** 473001 points
    Ki said:
    Are you loading to RAM?

    Please disregard this question. You already mentioned this in your original post. 

  • 0 in reply to Ki
    Prodigy 20 points

    Hi, Is there any progress with checking my log? Sorry for bothering, I am just want to make sure that this post won’t be shut down. 

  • 0 in reply to Dominik Busler
    TI__Guru**** 473001 points

    Sorry for the delay, this has stumped us. Loading to RAM is typically not an issue. We are unable to reproduce the issue makes troubleshooting difficult.