• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Subscribers 54 subscribers
  • Views 988 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/TMS320F28379D: Problem with external debugger in macOS and CCS10

Farid
Prodigy 70 points

Part Number: TMS320F28379D

Tool/software: Code Composer Studio

Hello,

We have an educational board with an onboard external debugger in our educational lab.  Students connect their laptops to these educational boards to experiment with F28379D MCUs.  With CCS10 and macOS we have a problem connecting to the MCUs. The error code is -150 (one the FTDI drivers returned bad status... ).  We use XDS100v2 as the connection on both windows and macOS.  The board is a bit old, I'm not sure if it's XDS100v1 or v2.  However we have been able to program the MCUs in windows without any problem with XDS100v2 as the connection. The original MCU on these boards was a F28035 but we replaced them with F28379D a couple of years ago.  We did not have any problems until recently with CCS10 and macOS. 

I have tried the same board with CCS10 on both windows and macOS (same laptop), I am able to connect to the MCU with windows but not with macOS.  We want to avoid using the onboard debugger since there's no access to the experiment setup because it's enclosed.  Do you have any suggestions how we can solve this problem in macOS?

Thanks,

Farid

  • 0
    TI__Guru**** 483431 points

    Hello Farid,

    Farid Naghavi said:
    The error code is -150 (one the FTDI drivers returned bad status... ).

    This error is usually due to some communication failure between the adapter and the FTDI chip... usually an issue with the FTDI driver on the host machine (mac).

    What version of macOS is being used?

    Is the error only with the external XDS100v2 probe? Did you ever get the onboard probe to work?

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 70 points

    It's macOS Catalina v10.15.6. 

    Yes, the error is only with external XDS100v2.  The onboard probe works just fine.

    Thanks,

    Farid

  • 0 in reply to Farid
    TI__Guru**** 483431 points

    I tried using my external Spectrum Digital XDS100v2 with an F28377D on my macOS Catalina 10.15.6. It seemed to work ok. I'm not sure what the issue is on your end, it must be some issue with the XDS100v2 drivers installed on the macOS (the onboard JTAG is likely an XDS100v1).

    Can you try a fresh reinstall of the latest CCS version (10.1.1)?

    Were you ever able to get that XDS100v2 working on macOS ever?

  • 0
    Guru 92251 points

    Farid Naghavi said:
    I have tried the same board with CCS10 on both windows and macOS (same laptop), I am able to connect to the MCU with windows but not with macOS.

    The problem might be a blank serial number in the XDS100 eeprom - see Code Composer 6.2 does not connect to H52C1 Concerto controlCARD

    Albeit the referenced thread was with CCSv6.

  • 0 in reply to Ki
    Prodigy 70 points

    I did a fresh reinstall of CCS 10.1.1, I still have the same problem.  Yes, the built-in debugger on the control card works in macOS I just have problem with the external debugger and macOS.  Attached are the screenshot of the driver for the external debugger.  Is it XDS100v1?  I will take a look at the forum with blank serial number of eeprom. 

    Please let me know if you have additional recommendations. 

    Thanks

  • 0 in reply to Farid
    Guru 92251 points

    Farid Naghavi said:
    I will take a look at the forum with blank serial number of eeprom.

    The serial number in your output is "TIUEEO1" and so isn't blank.

  • 0 in reply to Farid
    Guru 92251 points

    Farid Naghavi said:
    Is it XDS100v1?

    According to https://processors.wiki.ti.com/index.php/XDS100#How_to_make_an_XDS100_.2F_How_to_build_an_XDS100_hardware_emulator both a XDS100v1 and XDS100v2 have the same VID=0403 PID=A6D0, which matches your output, and are distinguished by a different device name string:

    • XDS100v1 should have a device string name of “Texas Instruments Inc.XDS100 Ver 1.0”
    • XDS100v2 should have a device string name of “Texas Instruments Inc.XDS100 Ver 2.0”

    Whereas your output appears to have a device string name of "Texas Instruments XDS100+RS232 V1.0". Therefore, think you have a XDS100v1.

    However, not sure if difference is the device string name is the cause of the problem under macOS.

    What does the driver for the built-in debugger on the control card which works show?

    If the device string name (aka product description) is the problem with the external debugger, then the FTDI FT_PROG may be able to change it.

  • 0 in reply to Chester Gillon
    Prodigy 70 points

    This is the driver detail for the built-in on-board debugger on the control card: 

  • 0 in reply to Farid
    Guru 92251 points

    Farid Naghavi said:
    Attached are the screenshot of the driver for the external debugger.  Is it XDS100v1?

    As well as the "V1.0" part of the product description string, the other thing which identifies the external debugger as a XDS100v1 is that the max speed is 12 MB/s (USB full speed).

    Whereas as the on-board XDS100v2 debugger is a 480 MB/s (USB Hi-Speed) device.

    I have just noticed that under the list of Debug Probes for macOS:

    • XDS100v2 and XDS100v3 are listed as supported
    • XDS100v1 is listed as not supported

  • 0 in reply to Chester Gillon
    TI__Guru**** 483431 points

    Farid,

    Chester is right. Your external probe is an XDS100v1 while the onboard one is an XDS100v2. And since the v1 is not supported on macOS, it explains why the external probe does not work while the onboard one does.

    Thanks

    ki