• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 99 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.

Struggling with USB on OMAP 3530 EVM

Dan Eisenhut
Prodigy 150 points


I'm using the OMAP 3530 EVM2 (Rev G) with the current BSP (6.14.01.01) and I cannot get anything to work with USB.  The ehcihcd.dll is being built and I've verified it is being loaded by NK.exe.  I have a powered USB 2.0 hub attached to the EHCI port.  I've tried it using an unmodified version of the EVM OSDesign.  And I have multiple identical EVM boards and I've tried it with each.

Any device I attach to the port, whether a mouse, keyboard, SD-Card reader, etc, doesn't appear to have any effect.  I've built a debug OS and turned on all the debug zones I could find related to it and there doesn't appear to be any activity on attach or remove.  I've tried enabling the BSP_HSUSB1_12PIN=1 and BSP_HSUSB2_12PIN=1, but no effect.

This seems like such a simple thing that should work out of the box.  I must be doing something wrong.  Any assistance would be greatly appreciated.

Thanks,

Dan

  • 0
    TI__Genius 9185 points

    Dan,

    The EHCI port should work fine with the BSP 6.14.01.01 release. To narrow down the issue,

    1. Did you use these board with a previous version of BSP and was the port working fine?

    2. Can you download the prebuilt 6.14.01.01 Demo images from the BSP download page and boot the image (under Demo\6.14.01.01\Images\EVM_3530\SD) using an SD card and then try the EHCI port. If that does not work there must be a problem with the board.

    As documented EHCI port has some limitations. It only works in HS mode and hence only HS devices should be attached to the port. If you connect a LS/FS device then the port completely stops functioning and a cold boot is needed to recover. Your email seems to suggest that all devices were connected via a USB 2.0 hub. That should have worked fine. 

    Jatin

  • 0 in reply to Jatin Jain
    Prodigy 150 points

    Jatin,

    Both EVM boards that I'm testing with now are brand new and have never been used with a previous BSP.  I have a third board, but I haven't tested USB on that one yet.  They all have the daughter board attached in case that makes a difference.  And all devices were connected via a USB 2.0 hub after reading the USB limitation in the BSP documentation.

    I will attempt the load the 6.14.01.01 Demo image on Monday when I get back into the office.

    Thanks,

    Dan

  • 0 in reply to Dan Eisenhut
    TI__Genius 9185 points

    Dan,

    Okay we will wait for the result of your experiment with the 6.14.01.01 Demo image. Even before that one more easy thing worth trying: The EVM box must have come with a WinCE SD card (older version of BSP: 6.12.04). Boot with that SD card and try the EHCI port.  If this works we can eliminate hw issue. Then try the Demo 6.14.01.01 image to narrow down the issue further. 

    Thanks.

    Jatin

  • 0 in reply to Jatin Jain
    Prodigy 150 points

    Jatin,

    I loaded the SD-Card that came with the board (6.12.04) and USB worked fine.  I downloaded the demo for 6.14.01 and it worked fine as well.  I copied a fresh copy of the EVM_3530 OSDesign and BSP into my root and built clean, USB worked.  So I diffed the two.  The only USB related difference was the batch file setting for BSP_HSUSB1_12PIN that I had enabled.  But I enabled that because USB was not working in the first place.

    Thinking back, I may have enabled that setting before I read that I needed a powered USB hub.  And I failed to remove the setting once I had attached the hub.  Therefore, operator error.

    Thanks for your time,

    Dan