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

MSP430F5510 Custom Board with USB not detected

SHASHANK JAGADISH
Expert 1690 points
Other Parts Discussed in Thread: MSP430F5510, MSPBSL

Hello TI Community,

We have a custom MSP430F5510 board with USB .

We have connected a 4Mhz Crystal to XT2 pin and all the necessary connections have been take care off.

When we connect the board to a windows PC, Should it be recognized as a COM port or HUD device ?

Nothing happens and when we pull the USB PUR pin high on the board

Windows detects it but fails to recognize the device and gives the error as

Unknown USB Device ( request for the USB device descriptor failed ) ( attached screenshot )

Our aim is to burn the firmware onto the F5510's flash - I have also attached our USB schematic

Kindly help us to solve this issue

  • 0
    Guru 243820 points
    Are C2 and C3 really on the same line?

    Why is D1 rated for 1000 V? This should be a small Schottky diode.

    It is hard to debug USB protocol problems in Windows. Can you plug it into a Linux system?
  • 0 in reply to Clemens Ladisch
    Expert 1690 points
    Hello Clemens,

    We have connected a 5v Zener Diode on our Board as suggested in "TI USB design document".

    Connecting C2 and C3 both on the line DM is a mistake. Is that causing problems here? because we feel they just act as decoupling capacitors.
  • 0 in reply to SHASHANK JAGADISH
    Guru 243820 points

    I don't know how large the effect of the wrong capacitors it. But you should better fix this.

    The 1N4007 is not a Zender diode. Anyway, this diode must not be a Zener diode; SLAA457 is using the wrong symbol. Section 42.2.2.1 of the User's Guide says:

    It is required that power from the USB cable's VBUS be directed through a Schottky diode prior to entering the VBUS terminal. This prevents current from draining into the cable's VBUS from the LDO input, allowing the MSP430 to tolerate a suspended or unpowered USB cable that remains electrically connected.

    And the diode is not always required; when the device is only bus powered, i.e., when there is no separate power supply, there is no current that can flow back. For testing, just short it.

  • 0 in reply to Clemens Ladisch
    Expert 1690 points

    Hello Clemens,

    I have a couple of doubts regarding the USB

    1. If we design a custom board using MSP430F5510 with USB following all the necessary TI guidelines, And if connect it to windows for the very first time will it get detected as a COM port or HUD port ? Or are there any steps we need to follow here after connecting it to Windows pc ?


    2. Also if my USB design was correct can I flash firmware directly on MSP430F5510 using tools like LMFlash etc ? And then later If I need to debug can i use Code    Composer Studio directly? or do I need to use the USB Descriptor Tool to generate the Descriptor files and include them in my project and handle USB Initialization and Interrupts ?

    Thanks a lot for your help.

  • 0 in reply to SHASHANK JAGADISH
    Guru 243820 points

    If there is no application in the flash, the BSL runs automatically.
    The BSL uses a custom protocol on top of the HID protocol (there is nothing called "HUD").

    LMFlash is not for MSP430s.
    You could load your firmware with the BSL Scripter tool (see MSPBSL), or write your own tool that uses the BSL protocol.

    Debugging requires going through the JTAG/Spy-Bi-Wire pins with an emulator tool; this would be a connection separate from USB. On the LaunchPad, the F5529's SBW pins are connected to the emulator MCU; you can connect the LaunchPad's emulator to your own board instead if you have remembered to add a pin header for those signals. (The debugger would also allow writing your app to the flash.)

**Attention** This is a public forum