• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 79 subscribers
  • Views 354 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.

MSP430F5659: Problem implementing USB software into an existing project.

David Dudley
Expert 1290 points

Part Number: MSP430F5659

Tool/software:

OK, so I have an existing project I want to get onto USB.

First, let me start somewhere else

I built the C1_LedOnOff example successfully.  Can install it on the hardware (custom hardware) and successfully run it.

No problems so far.

Should be simple....

I have an existing project that I want to implement USB into.

Copied all the USB software (USB_API, USB_app, USB_config) into my project.

Used the MSP430 USB Descriptor tool to create my new descriptors.c/h and UsbIsr.c into the USB_config directory, just as indicated.

Added all the include directories into the project  just as indicated.

Build the project successfully (no compile errors), but when it links it gives a single error that "tOutputEndPointDescriptorBlock" is not defined.

No other errors.....

Cannot find where this is actually defined, or what I've forgotten.... 

Help would be appreciated.

David

  • 0
    Expert 1290 points

    So...

    Found the problem, but its something I wasn't expecting.

    Apparently, the USB Descriptor Tool program is creating an invalid descriptor.

    If I copy the descriptor information files from the example program, it works fine.  If I use the descriptor tool to create the configuration I actually want, it is either ignored (won't enumerate with the host), or it will actually 'hang' the host during enumeration.

    Unplugging the board from the USB is the only way to get things back on track.

    This fails both on my target program, as well as the example.

    Is there a corrected version of the Descriptor program, or has TI just totally dropped the MSP430 support?  Seems there's not much in the way of support any more.

    ALSO... this new 20.1.0.6__1.7.0 CCS is a piece of crap.  Whoever decided this was the way to go definitely decided wrong.  It locks up, fails to recognize the MSP430-FET unit half the time (only way to get it back on is to unplug and replug it), may/may not decide to program the target device, decided launch.json doesn't exist, or isn't valid (requires exiting CCS and reloading),... and a number of more things.  I HOPE there is a new version coming that will fix this garbage.  Otherwise, have to seriously think about continuing to use these products.

    Don't get me wrong... I LOVE the MSP430 product, just quality of the programming environment has gone down over time.

    David

  • 0 in reply to David Dudley
    TI__Genius 12785 points

    Hi David,

    So sorry for late reply.

    The newest version of USB Descriptor Tool is v5.0.11.22 : MSP430USBDEVPACK Application software & framework | TI.com, are you using this version?

    And for the MSP430 USB API & Descriptor Tool guide, you could refer to: Programmer's Guide

    I would also recommend looking at below posts for the similar topic: 

    (+) MSP430F5529: Device Descriptor Request Failed: Windows has stopped this device because it has reported problems. (Code 43) - MSP low-power microcontroller forum - MSP low-power microcontrollers - TI E2E support forums

    Best Regards,

    Pengfei

  • 0 in reply to Pengfei Xie
    Expert 1290 points

    That's the version I have installed.

    This is on Linux.  On our internal research network, no Windows boxes is allowed.  We have Windows on our outside office network, but it's for email/web and so on...

    No development here goes on a Windows machine.  Which is another problem, they want to do a Hercules project, but that's not supported on Linux.

    Enough complaining.....

    I can copy the files from the example project and the USB works fine, but if I try and create a custom configuration,  it doesn't work.

    Eventually, I'll get to the heart of the issue, but don't have time right now, so I'll just patch in the example configuration.

  • 0 in reply to David Dudley
    TI__Genius 12785 points

    Hi David,

    Understood.

    Actually making modification based on a SDK imported project is also the most common way that we build our project. Hope things works well with you .

    Best Regards,

    Pengfei

**Attention** This is a public forum