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 "not USB FET was found" + "Unknown Device" in Dev Manager

Other Parts Discussed in Thread: MSP430F5510

Hi there,

I have finished soldering my custom MSP430 board today and now would like to flash a blink program to it. (My previous MSP430 experience comes from the eZ430-F2013 and the Chronos)

I loaded the MSP430F5510 Blink sample, connected a 150Ohms Resistor between VBUS and PUR to trigger the USB BSL and connected the Board which then showed up as "Unknown Device" in the Device Manager and when looking at the device info it says that the device was stopped (Code: 43). Is that normal so far?

I then tried flashing and debugging the Blink program using CCS5, however upon starting debug, it confronted me with the error "No USB FET was found". Other threads on the topic have not been able to help me so far (e.g. changing the USB port in the general options)

I have to say that I had soldered a HTC74 chip wrong way round on to the board and upon power connect, that got really warm. After turning the chip right way round, I did some tests using a current limited power supply, everything seemed okay, so I don't think that the MSP430 was damaged by that.

Any help on this one would be great!

  • check for a short, even a small one can cause device manager to not recognize the board. Also you mentioned that you connected a chip the wrong way. You probably fried the chip because you pumped voltage into pin that were not meant to receive it. From my experience, when a chip overheats unexpectedly it usually gets fried.

    Tyler

  • I have checked several times, I couldn't find any shorts, but thanks for the tip.

    About the chip, well even if its fried, it shouldn't affect the MSP because its on the 5V USB supply and the MSPs LDO still outputs stable 3.3V which poweres everything else.

    Regards,

    Max

    PS: I have attached a copy of the schematic. The "BSL Switch" is currently not included, i hope to be able to call the BSL via software in the future. Sorry for the size, I couldn't find a way to just attach it as a file...

    /Picture Edited out/

  • Hello Max,

    I've also worked with MSP4305510 USB. Here a link to thread (maybe helpful now or in the future): http://e2e.ti.com/support/microcontrollers/msp430/f/166/t/201314.aspx

    Where is pull-up for reset pin?  

    Please note PCB layout is also important in USB designs.

  • Hi Mikolaj,

    thanks for the links, seems pretty interesting.

    I chose not to attach a pull-up, as the Datasheet states "All devices except the MSP430F543x (non-A devices) have the internal pullup enabled. In
    this case, no external pullup resistor is required."

    I just re-checked that. However, how i noticed afterwards, TI recommends a Cap in this case:

    "47-kΩ pullup or internal pullup selected with 10-nF (2.2 nF) pulldown(2)"

    I may have gotten this totally wrong...

    I just measured the potentials of the data lines as well, D+ has 3V to GND, D- is on the same potential as GND. I supposed there's nothing wrong with that?

    I have attached the PCB layout.

    Regards,

    Max

    /Picture edited out/

  • I've done only 2 projects with USB, so I'm not an expert. I can only guess. :P

    Max said:
    I just measured the potentials of the data lines as well, D+ has 3V to GND, D- is on the same potential as GND. I supposed there's nothing wrong with that?

    The voltages are reliable but, if I remember, in my projects D- wasn't equal exactly 0V - it was 0-0.2V and wasn't constant.

    And I don't like this layout. D+ and D- should run next to each other, have similar length, minimal number of vias, direction changes and other signals nearness. These rules I remember and in my projects I always connected USB components and crystal firstly. I think you have found the design references in MSP430 guides.

    Anyway, I haven't created a lot of projects with USB and maybe layout here isn't a problem. You need to wait for someone with more experience.

    Best regard,

    Mikolaj

  • Hi,

    it's my first board that I designed totally on my own and I tried to follow as many rules as possible but I knew it wouldn't be perfect ;)

    I have now reattached the board to a USB 3.0 port on the back and on this port the MSP430 enumerates as a HID USB Device in the Device Manager. That gives me hope that the circuit is still alive.. somehow.

    However when trying to debug the blink program, I still get the "Error initializing emulator:
    No USB FET was found"

    error.

    Any further ideas and recommendations would be great.

    Regards,

    Max

  • It's great there is a progress.

    Max said:
    However when trying to debug the blink program, I still get the "Error initializing emulator:
    No USB FET was found"

    I haven't use USB BSL, but I remember there were design considerations for USB BSL (like a special push-button on PUR line). I've found a PDF: http://www.ti.com/lit/an/slaa452b/slaa452b.pdf

  • Hi Mikolaj,

    thanks for your constant support! The PDF confirmed what I was suspecting already from bits and pieces from other user guides.

    The BSL just be triggered, because I pull up the PUR pin using an extra resistor (not included in the schematic) and also the RESET vector should be blank, as its a new MSP430.

    I am now wondering why the board failes to enumerate on a USB 2.0 hub port (front panel port) but sucessfully enumerates on a USB3.0 . In my opinion this indicates a fault with the circuit, that USB3.0 port tolerate, but 2.0 Ports don't.

    I will reply when I got something new, till then, any comments are welcome.


    Regards,

    Max

  • Quick update:

    Using the usb firmware upgrade example from this page:

    http://software-dl.ti.com/msp430/msp430_public_sw/mcu/msp430/MSP430_USB_Developers_Package/latest/index_FDS.html

    I was successfully able to flash a Firmware to the device. Does that mean that my device as such is not compatible with CSS5 or do i need to adjust any settings?

    Regards,

    Max

    EDIT: Well I suppose its not possible to program a USB BSL using just CCS. I'm happy so far with the firmware tool, but I'm going to leave this open in case somebody has an answer

**Attention** This is a public forum