• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 81 subscribers
  • Views 1737 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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/LAUNCHXL-F28027F: BoostXL-DRV8301

Roberto Quintal
Prodigy 40 points
Part Number: LAUNCHXL-F28027F

Tool/software: Code Composer Studio

Using the universal GUI. After uploading the appProgram.out correctly and even being able to Enable System:

Restarting Program Model...
Initializing target : C:\ti\guicomposer\eclipse\workspace\.metadata\.plugins\com.ti.binding.program\appConfig.ccxml
Connecting target: Texas Instruments XDS100v2 USB Debug Probe/C28xx
Loading program: C:\ti\guicomposer\webapps\InstaSPIN_F2802xF_UNIVERSAL\appProgram.out
Enabling Realtime
Running Program...

I keep getting this error:

C28xx: Error (Error -150 @ 0x0) One of the FTDI driver functions used during configuration returned a invalid status or an error. (Emulation package 5.1.641.0)

I already tried reinstalling the FTDI drivers stored in:

C:\ti\ccsv6\ccs_base\emulation\windows\xds100_drivers\ftdi

I have Windows 10 Education and CCS 6

  • 0
    TI__Guru**** 168377 points
    Hi,

    The explanation of this error together with some possible workarounds is shown at the following reference:

    software-dl.ti.com/.../ccsv7_debugging_jtag_connectivity_issues.html

    You may need to use Code Composer Studio to further debug the root cause of this problem.

    Hope this helps,
    Rafael
  • 0 in reply to desouza
    Prodigy 40 points

    Hi Rafael,

    interesting enough I found a solution (maybe partial) so I changed two things:

    1. disconnected the shaft of the teknic motors, so I run the motor identificaction on a single one.

    2. changed the USB cable for a shorter one, apparently the one provided with the kit, works fine (even passed the tests) when working with the LaunchXL board alone, but something happens when debugging the combination LaunchXL and Boost-DRV. Maybe EMC problems perhaps?

    So now is up and running with a 10 cm USB cable 

    Thanks

    Roberto

  • 0 in reply to Roberto Quintal
    TI__Guru**** 168377 points
    Roberto,

    Thank you for reporting your findings. I will certainly add this thread to the pool of threads on the reference I sent above.

    If I recall correctly, you are not the first to report the BOOSTXL to cause connection problems, but I suspect it is either introducing a lot of noise on the JTAG lines or perhaps a ground loop that is overloading the output of the Debug Probe.

    Also, the USB cable may not be properly shielded, thus not having enough immunity to spurious noise coming from the motors.

    Thank you,
    Rafael