public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: ecos-bugs@ecos.sourceware.org Subject: [Bug 1001024] STM32 USB driver and proposed USB API change Date: Fri, 15 Oct 2010 13:51:00 -0000 [thread overview] Message-ID: <20101015135132.2036A2F8000A@mail.ecoscentric.com> (raw) In-Reply-To: <bug-1001024-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=1001024 John Dallaway <john@dallaway.org.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned@bugs.ecos.source |john@dallaway.org.uk |ware.org | --- Comment #12 from John Dallaway <john@dallaway.org.uk> 2010-10-15 14:51:27 BST --- Chris, thank you for the updated driver. The cdc-acm driver on my Linux box is now reporting "Zero length descriptor references": Oct 15 13:11:27 cog kernel: usb 4-1: new full speed USB device using uhci_hcd and address 28 Oct 15 13:11:37 cog kernel: usb 4-1: configuration #1 chosen from 1 choice Oct 15 13:11:37 cog kernel: drivers/usb/class/cdc-acm.c: Zero length descriptor references Oct 15 13:11:37 cog kernel: Oct 15 13:11:37 cog kernel: cdc_acm: probe of 4-1:1.0 failed with error -22 This seems to be widely reported on the net with random ACM hardware so I have switched back to CYGDAT_IO_USB_SLAVE_CLASS_TYPE == "generic" for the time being. With the eCos "generic" USB serial support, I'm issuing: modprobe usbserial vendor=0xffff product=0x0001 and seeing: Oct 15 13:49:49 cog kernel: usb 4-1: new full speed USB device using uhci_hcd and address 35 Oct 15 13:49:59 cog kernel: usb 4-1: configuration #1 chosen from 1 choice Oct 15 13:49:59 cog kernel: usbserial_generic 4-1:1.0: generic converter detected Oct 15 13:49:59 cog kernel: usb 4-1: generic converter now attached to ttyUSB0 So far, so good. I can connect to /dev/ttyUSB0 using minicom and send/receive chars over USB. The remaining problem is that every other char I receive on the eCos side is a copy of the previous character received. If I type "abcdefgh" into minicom, eCos receives "?bbddffh". The very first char received is random. The timing of all received characters is as expected (immediately after hitting the key). The transmission of chars from eCos to minicom is working correctly. Can you see how this issue might arise with your latest STM32 USB driver code? Is there some further tracing I could add to debug this? -- 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.
next prev parent reply other threads:[~2010-10-15 13:51 UTC|newest] Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-08-25 20:36 [Bug 1001024] New: " bugzilla-daemon 2010-08-26 9:14 ` [Bug 1001024] " bugzilla-daemon 2010-08-26 11:00 ` bugzilla-daemon 2010-09-03 14:00 ` bugzilla-daemon 2010-09-13 19:31 ` bugzilla-daemon 2010-09-13 19:32 ` bugzilla-daemon 2010-09-13 19:51 ` bugzilla-daemon 2010-09-17 13:11 ` bugzilla-daemon 2010-09-17 18:03 ` bugzilla-daemon 2010-10-07 10:13 ` bugzilla-daemon 2010-10-07 19:23 ` bugzilla-daemon 2010-10-09 14:38 ` bugzilla-daemon 2010-10-15 13:51 ` bugzilla-daemon [this message] 2010-10-15 16:13 ` bugzilla-daemon 2010-10-15 17:07 ` bugzilla-daemon 2010-10-15 20:52 ` bugzilla-daemon 2010-10-16 7:41 ` bugzilla-daemon 2010-10-16 10:12 ` bugzilla-daemon 2010-10-16 10:55 ` bugzilla-daemon 2010-10-16 12:18 ` bugzilla-daemon 2010-10-16 13:53 ` bugzilla-daemon 2010-10-16 14:34 ` bugzilla-daemon 2010-10-16 19:30 ` bugzilla-daemon 2010-10-17 14:21 ` bugzilla-daemon 2010-10-17 15:06 ` bugzilla-daemon 2010-10-17 15:29 ` bugzilla-daemon 2010-10-17 18:08 ` bugzilla-daemon 2010-10-17 18:34 ` bugzilla-daemon 2010-10-18 9:36 ` bugzilla-daemon 2010-10-20 18:27 ` bugzilla-daemon 2010-10-21 8:57 ` bugzilla-daemon 2010-10-21 15:40 ` bugzilla-daemon 2010-10-21 18:32 ` bugzilla-daemon 2010-10-21 18:47 ` bugzilla-daemon 2010-10-21 21:20 ` bugzilla-daemon 2010-10-25 8:48 ` bugzilla-daemon 2010-10-26 10:50 ` bugzilla-daemon 2010-10-26 19:15 ` bugzilla-daemon 2010-10-27 10:25 ` bugzilla-daemon 2010-10-27 13:04 ` bugzilla-daemon 2010-08-25 20:36 [Bug 1001024] New: " bugzilla-daemon 2010-08-26 9:14 ` [Bug 1001024] " bugzilla-daemon 2010-08-26 11:00 ` bugzilla-daemon 2010-09-03 14:00 ` bugzilla-daemon 2010-09-13 19:31 ` bugzilla-daemon 2010-09-13 19:32 ` bugzilla-daemon 2010-09-13 19:51 ` bugzilla-daemon 2010-09-17 13:11 ` bugzilla-daemon 2010-09-17 18:03 ` bugzilla-daemon 2010-10-07 10:13 ` bugzilla-daemon 2010-10-07 19:23 ` bugzilla-daemon 2010-10-09 14:38 ` bugzilla-daemon 2010-10-15 13:51 ` bugzilla-daemon
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20101015135132.2036A2F8000A@mail.ecoscentric.com \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=ecos-bugs@ecos.sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).