• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 462 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.

Concerto F23M35H52C USB Peripheral

Miro Petrovic
Prodigy 210 points

Other Parts Discussed in Thread: CONTROLSUITE

I had a problem with ControlSuite V120 usb_host_msc - mass storage project on Concerto evaluation board. Program displayed NODEV> prompt  with memory stick connected. I changed the card with new one and same thing happened. As I had in the past the same problem with Stellaris LM3S9B92 evaluation board I put USB0ID to GND and program started working. Does it mean that on F23M35H52C there is the same problem as on LM3S9B92 Rev. B? Does it mean that I can't use freely USB0VBUS and USB0ID pin  in host mode for other functions?

Regards,

Miro

  • 0
    TI__Mastermind 22025 points

    Miro,

    There are some known issues with regards to USB on Concerto.  Specifically the VBUS and ID pins have an issue with clamping to the supply rails.  Please check out the silicon errata for this device.  That being said the example should still work.

    Try updating your controlsuite and using the v130 device support files.  I personally released these files and tested the USB examples last week and they were in fact working.

    Regards,

    Trey

  • 0 in reply to Trey German289
    Prodigy 210 points

    I tested example with v130 device support files.( In usb_host_msc example there is no difference beetwen v120 and v130 usb_host_msc.c and startup_ccs files). The result was the same as with v120 - usb_host_msc project. It starts working only if I connect USB0ID to GND. This could be explained if the USB0ID pin has an issue with clamping to supply rails as you suggested me in your answer or that I've bad lack and 2 concerto boards with GPIO46 pin damaged. I didn't  find USB0ID clamping issue in Concerto errata. It's written that only VBUS pin has an issue. Let's speak now about VBUS pin clamping to supply rails issue. Does it mean that I can't use this pin as PF6_GPIO38 input/output or we have a problem only in case  VBUS is selected as alternate function on that pin.

    Regards,

    Miro

  • 0 in reply to Miro Petrovic
    TI__Mastermind 22025 points

    Both VBUS and ID have the same problem.  I believe the IO's still work if USB is not in use.  They are still partially functional, but this clamping issue can prevent propper operation if OTG is attempted.

    Trey

  • 0 in reply to Trey German289
    Prodigy 210 points

     I've tested VBUS and ID pins as general purpose outputs while serving USB memory stick and everything is working correctly. So for me this argument is closed.

    Thanks,

    Miro