public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: unassigned@bugs.ecos.sourceware.org Subject: [Bug 1001024] STM32 USB driver and proposed USB API change Date: Fri, 17 Sep 2010 13:11:00 -0000 [thread overview] Message-ID: <20100917131104.93C622F7800E@mail.ecoscentric.com> (raw) In-Reply-To: <bug-1001024-777@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 ---------------------------------------------------------------------------- CC| |fpagliughi@mindspring.com --- Comment #7 from John Dallaway <john@dallaway.org.uk> 2010-09-17 14:11:01 BST --- Chris, thank you for the attachments. I've been experimenting with them and have reached the point where my linux box is recognising the connection of a serial device: Sep 17 13:38:35 cog kernel: usb 4-1: new full speed USB device using uhci_hcd and address 20 Sep 17 13:38:35 cog kernel: usb 4-1: device descriptor read/all, error -71 Sep 17 13:38:35 cog kernel: usb 4-1: new full speed USB device using uhci_hcd and address 21 Sep 17 13:38:35 cog kernel: usb 4-1: device descriptor read/all, error -71 Sep 17 13:38:35 cog kernel: usb 4-1: new full speed USB device using uhci_hcd and address 22 Sep 17 13:38:35 cog kernel: usb 4-1: device descriptor read/8, error -71 Sep 17 13:38:35 cog kernel: usb 4-1: configuration #1 chosen from 1 choice Meanwhile, the STM32 USB driver reports: ### 3:Powered ### ### 4:Reset ### ### 4:Reset ### ### 4:Reset ### ### 4:Reset ### STM32 USB : Setting USB device address = 20 ### 5:Addressed ### ### 4:Reset ### ### 4:Reset ### STM32 USB : Setting USB device address = 21 ### 5:Addressed ### ### 4:Reset ### STM32 USB : Setting USB device address = 22 ### 5:Addressed ### STM32 USB : Setting USB configuration = 1 ### 6:Configured ### To get this far, I have: a) set CYGDAT_IO_USB_SLAVE_SERIAL_EP0 == "cyg_usbs_cortexm_stm32_ep0c" b) commented out references to the static rx/tx/intr endpoint structs in usbs_serial.c, and c) modified the parameters passed into usbs_serial_init(): void usbs_serial_start(void) { usbs_serial_init(&usbs_ser0, usbs_get_tx_endpoint(usbs_serial_ep0, TX_EP_NUM), usbs_get_rx_endpoint(usbs_serial_ep0, RX_EP_NUM)); ...... lsusb reports: Bus 004 Device 022: ID ffff:0001 Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0xffff idProduct 0x0001 bcdDevice 0.00 iManufacturer 1 eCos iProduct 2 eCos USB Serial Device iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 "Vendor Specific Class" doesn't look good. Are there any clues here as to the problem? I am adding Frank Pagliughi (eCos USB slave serial author) to the CC list in case he has some insights on how to debug this. -- Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
next prev parent reply other threads:[~2010-09-17 13:11 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 [this message] 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 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 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
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=20100917131104.93C622F7800E@mail.ecoscentric.com \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=unassigned@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).