• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 98 subscribers
  • Views 1218 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.

USB Stick is not detected after a warm reset on OMAP3530/WinCE device

Luan Le
Expert 2280 points
Other Parts Discussed in Thread: OMAP3530

Hi,

A USB stick connected to EHCI Host port is detected and displayed as "Hard Disk" on OMAP3530 EVM as well as my WinCE device after power-on.  After doing a warm reset (by momentarily pressing WARM_RST button, S2 on the  OMAP3530 EVM ), the device reboots normally and goes the shell.  Exploring "My Device", "Hard Disk" is no longer there.  Unplugging and re-plugging the USB stick does not help, even when using a hub.

I did use the original EVM_3530 OS to verify this problem on the EVM.

Do you have any advice for me on how to resolve this issue?  In some cases, our application needs to reset the board.

In appreciation,

Luan

  • 0
    TI__Genius 9185 points

    Which BSP version are you using?

  • 0 in reply to Jatin Jain
    Expert 2280 points

    I am using BSP version 6.15.00.

  • 0 in reply to Luan Le
    TI__Genius 9185 points

    Also what boot method are you using (SD, NAND, ethernet). Thanks.

     

  • 0 in reply to Jatin Jain
    Expert 2280 points

    Hi Jatin,

    I try both boot methods, NAND and ethernet, and have the same result.  When booting from ethernet with a debug build, after power-on reset, all the correct drivers are loaded and unloaded as shown on the PB outputs when inserting and removing the usb stick, mouse, or keyboard.  Doing a warm reset with the usb stick, mouse, and keyboard attached, none of the drivers are loaded for these devices.   After that, inserting or removing any of the usb device does not cause any additional output, even when debug zones in several usb DLLs (usbd.dll, musbfn.dll, musbhcd.dll) are enabled.

    You should be able to reproduce this issue easily.  Do you think this is a hardware or software problem? 

    Thanks,

    Luan

  • 0 in reply to Luan Le
    Expert 2280 points

    Hi Jatin,

    Have you had a chance to duplicate or look into this problem?  In addition to what I report in the previous post, when usb stick, mouse, and key board are connected to a hub, which is connected to the EHCI HOST port, I also see that

    After a cold reset, all of the following DLLs are loaded

    usbd.dll
    ehcihcd.dll

    usbhid.dll
    mouhid.dll
    kbdhid.dll
    hidparse.dll
    usbdisk6.dll
    usbmsc.dll

    After a warm reset, only usbd.dll and ehcihcd.dll are loaded.  The rest of them are not and there are no indications of loading failures.

    Do you have any tips on how to figure out why these DLLs are not getting loaded after a warm reset?

    Thanks,

    Luan

     

  • 0 in reply to Luan Le
    TI__Genius 9185 points

    Luan,

    We are seeing the same problem with SD and Ethernet warm boot with BSP 6.15 release. 

    We have a new release coming out in the next few days and it does not exhibit the same problem.  But the release is a slightly different from the BSP 6.xx base line (mostly a superset with changes to support additional chips as well some difference in the BSP structure, BSP catalog entries and such.). 

    Jatin

     

  • 0 in reply to Jatin Jain
    TI__Genius 9185 points

    Luan: Please refer to the announcement with the latest release (this one does not exhibit the warm reset issue). http://e2e.ti.com/support/embedded/f/353/t/79548.aspx

    As you can see at the end of that post we are not planning any more updates to the BSP 6.xx releases. The new baseline allows us to efficiently support multiple TI chips with ARM_A8 processors (OMAP35x; DM/AM37x; AM35x etc). This release is a superset of the BSP 6.15 release. And we only plan to do maintenance release if needed on the new baseline.