This is the mail archive of the
ecos-bugs@sourceware.org
mailing list for the eCos project.
[Bug 1001084] STM32 USB driver unplugging/replugging issue
- From: bugzilla-daemon at bugs dot ecos dot sourceware dot org
- To: ecos-bugs at ecos dot sourceware dot org
- Date: Wed, 1 Dec 2010 11:04:50 +0000
- Subject: [Bug 1001084] STM32 USB driver unplugging/replugging issue
- Auto-submitted: auto-generated
- References: <bug-1001084-13@http.bugs.ecos.sourceware.org/>
Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001084
--- Comment #2 from John Dallaway <john@dallaway.org.uk> 2010-12-01 11:04:47 GMT ---
Chris, thank you for your comment.
(In reply to comment #1)
> I'm guessing that you have the STM32 board powered up throughout this test.
Correct.
> If so, unmounting the file system will not be sufficient - the host will not
> perform the required control endpoint actions to take the device out of the
> configured state ready for clean removal. I think that 'eject' should do this
> correctly.
>
> To be honest, USB device testing is one place where you're better of using
> Windows...
I will experiment on Windows. If the scenario I outline in this report works
correctly on Windows, we will have a better understanding of the issue.
Clearly, it is important that eCos applications can recover from _unexpected_
USB disconnections.
--
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.