From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 634 invoked by alias); 3 Sep 2007 07:46:20 -0000 Received: (qmail 618 invoked by uid 22791); 3 Sep 2007 07:46:19 -0000 X-Spam-Check-By: sourceware.org Received: from web60722.mail.yahoo.com (HELO web60722.mail.yahoo.com) (209.73.178.210) by sourceware.org (qpsmtpd/0.31) with SMTP; Mon, 03 Sep 2007 07:46:06 +0000 Received: (qmail 46107 invoked by uid 60001); 3 Sep 2007 07:46:04 -0000 X-YMail-OSG: wKaEULoVM1m1ylNtikaDt34ST4TCm9iJXpMYlpeAnM_cY9_ne4TRIzOdCUDdJ4WxkjeZGZQ7DR2iKBqC0wssqFIceWfmkwfpQRgLINJkpF9Jccyg9jitEkOh7eR_.o8- Received: from [217.147.104.33] by web60722.mail.yahoo.com via HTTP; Mon, 03 Sep 2007 00:46:03 PDT Date: Mon, 03 Sep 2007 07:46:00 -0000 From: wavecom wavecom To: Andrew Lunn Cc: ecos-discuss@ecos.sourceware.org In-Reply-To: <20070827195634.GQ19659@lunn.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <913572.45455.qm@web60722.mail.yahoo.com> X-IsSubscribed: yes Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: Re: [ECOS] USB-CDC eCos configuration X-SW-Source: 2007-09/txt/msg00014.txt.bz2 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