From: wavecom wavecom <wavecomw@yahoo.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] USB-CDC eCos configuration
Date: Mon, 03 Sep 2007 07:46:00 -0000 [thread overview]
Message-ID: <913572.45455.qm@web60722.mail.yahoo.com> (raw)
In-Reply-To: <20070827195634.GQ19659@lunn.ch>
Hi All,
During development my USB-CDC driver, I have met
another com initialization problem. Symptoms are that
hyperterminal returns “cannot initialize COMx”.
I have sniffed transmission between host and the
device. First two errors occurs in packet #12 (result
code 0xc0010000) and #13 (result code 0xc0000004).
00 20 00 00 00 00 07 00
data direction: host to device
type: standard
recipient: interface
req->request: Set line coding
21 20 00 00 00 00 07 00
data direction: host to device
type: class
recipient: interface
req->request: Set line coding
00 21 00 00 00 00 07 00
data direction: host to device
type: standard
recipient: interface
req->request: Set line coding
a1 21 00 00 00 00 07 00
data direction: host to device
type: class
recipient: interface
req->request: Set line coding
My question is what may be the cause of device replies
0xc0010000 and 0xc0000004?
I will be very grateful for any suggestions.
My driver has implementation of functions:
usbs_at91_ep0.standard_control_fn
usbs_at91_ep0.class_control_fn
usbs_at91_ep0.reserved_control_fn
functions returns USBS_CONTROL_RETURN_HANDLED
in operations
USB_SET_LINE_CODING 0x20
USB_GET_LINE_CODING 0x21
USB_SET_CONTROL_LINE_STATE 0x22 requests.
Below details of communication and all packet
sequence...
packets #12 and #13....
12 out down n/a 20.069 CLASS_INTERFACE 00 c2 01 00 01
00 08
URB Header (length: 80)
SequenceNumber: 12
Function: 001b (CLASS_INTERFACE)
PipeHandle: 851ac7e0
SetupPacket:
0000: 00 20 00 00 00 00 07 00
bmRequestType: 00
DIR: Host-To-Device
TYPE: Standard
RECIPIENT: Device
bRequest: 20
unknown!
TransferBuffer: 0x00000007 (7) length
0000: 00 c2 01 00 01 00 08
12 out up n/a 50.092 CONTROL_TRANSFER - 0xc0010000
URB Header (length: 80)
SequenceNumber: 12
Function: 0008 (CONTROL_TRANSFER)
PipeHandle: 851ac7e0
SetupPacket:
0000: 21 20 00 00 00 00 07 00
bmRequestType: 21
DIR: Host-To-Device
TYPE: Class
RECIPIENT: Interface
bRequest: 20
No TransferBuffer
13 out down n/a 50.092 CLASS_INTERFACE -
URB Header (length: 80)
SequenceNumber: 13
Function: 001b (CLASS_INTERFACE)
PipeHandle: 851ac7e0
SetupPacket:
0000: 00 21 00 00 00 00 07 00
bmRequestType: 00
DIR: Host-To-Device
TYPE: Standard
RECIPIENT: Device
bRequest: 21
unknown!
No TransferBuffer
13 in up n/a 50.112 CONTROL_TRANSFER 0xc0000004
URB Header (length: 80)
SequenceNumber: 13
Function: 0008 (CONTROL_TRANSFER)
PipeHandle: 851ac7e0
SetupPacket:
0000: a1 21 00 00 00 00 07 00
bmRequestType: a1
DIR: Device-To-Host
TYPE: Class
RECIPIENT: Interface
bRequest: 21
TransferBuffer: 0x00000000 (0) length
All transmission:
1 in down n/a 0.000 GET_DESCRIPTOR_FROM_DEVICE
1 in up n/a 0.000 CONTROL_TRANSFER 12 01 10 01 02 00
00 08 0x00000000
2 in down n/a 0.000 GET_DESCRIPTOR_FROM_DEVICE
2 in up n/a 0.000 CONTROL_TRANSFER 09 02 43 00 02 01
00 c0 0x00000000
3 ??? down n/a 0.000 SELECT_CONFIGURATION
3 ??? up n/a 0.060 SELECT_CONFIGURATION 0x00000000
4 out down n/a 0.060 CLASS_INTERFACE -
4 in up n/a 0.060 CONTROL_TRANSFER 00 c2 01 00 01 00
08 0x00000000
5 out down n/a 0.060 CLASS_INTERFACE -
5 out up n/a 0.060 CONTROL_TRANSFER - 0x00000000
6 ??? down n/a 0.060 BULK_OR_INTERRUPT_TRANSFER -
7 ??? down n/a 0.060 BULK_OR_INTERRUPT_TRANSFER -
8 out down n/a 20.049 CLASS_INTERFACE -
8 in up n/a 20.049 CONTROL_TRANSFER 00 c2 01 00 01 00
08 0x00000000
9 out down n/a 20.049 CLASS_INTERFACE -
9 in up n/a 20.049 CONTROL_TRANSFER 00 c2 01 00 01 00
08 0x00000000
10 out down n/a 20.049 CLASS_INTERFACE -
10 in up n/a 20.049 CONTROL_TRANSFER 00 c2 01 00 01 00
08 0x00000000
11 out down n/a 20.069 CLASS_INTERFACE -
11 in up n/a 20.069 CONTROL_TRANSFER 00 c2 01 00 01 00
08 0x00000000
12 out down n/a 20.069 CLASS_INTERFACE 00 c2 01 00 01
00 08
12 out up n/a 50.092 CONTROL_TRANSFER - 0xc0010000
13 out down n/a 50.092 CLASS_INTERFACE -
13 in up n/a 50.112 CONTROL_TRANSFER 0xc0000004
14 out down n/a 50.112 CLASS_INTERFACE -
14 in up n/a 50.112 CONTROL_TRANSFER 0xc0000004
15 out down n/a 50.112 CLASS_INTERFACE -
15 in up n/a 50.112 CONTROL_TRANSFER 0xc0000004
16 out down n/a 50.112 CLASS_INTERFACE b0 04 00 00 01
00 08
16 out up n/a 50.112 CONTROL_TRANSFER - 0xc0000004
17 out down n/a 50.112 CLASS_INTERFACE -
17 in up n/a 50.112 CONTROL_TRANSFER 0xc0000004
18 out down n/a 50.112 CLASS_INTERFACE -
18 out up n/a 50.112 CONTROL_TRANSFER - 0xc0000004
____________________________________________________________________________________
Pinpoint customers who are looking for what you sell.
http://searchmarketing.yahoo.com/
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2007-09-03 7:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 7:20 wavecom wavecom
2007-08-27 7:33 ` Andrew Lunn
2007-08-27 12:16 ` wavecom wavecom
2007-08-27 20:01 ` Andrew Lunn
2007-09-03 7:46 ` wavecom wavecom [this message]
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=913572.45455.qm@web60722.mail.yahoo.com \
--to=wavecomw@yahoo.com \
--cc=andrew@lunn.ch \
--cc=ecos-discuss@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: link
Be 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).