From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31231 invoked by alias); 2 Jun 2006 08:09:38 -0000 Received: (qmail 31182 invoked by uid 22791); 2 Jun 2006 08:09:36 -0000 X-Spam-Check-By: sourceware.org Received: from londo.lunn.ch (HELO londo.lunn.ch) (80.238.139.98) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 02 Jun 2006 08:09:33 +0000 Received: from lunn by londo.lunn.ch with local (Exim 3.36 #1 (Debian)) id 1Fm4im-0003Rt-00; Fri, 02 Jun 2006 10:09:28 +0200 Date: Fri, 02 Jun 2006 08:09:00 -0000 To: John Eigelaar Cc: ecos-discuss@sources.redhat.com Message-ID: <20060602080928.GM2478@lunn.ch> Mail-Followup-To: John Eigelaar , ecos-discuss@sources.redhat.com References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11+cvs20060403 From: Andrew Lunn X-IsSubscribed: yes Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: Re: [ECOS] USB-CDC on AT91 X-SW-Source: 2006-06/txt/msg00019.txt.bz2 On Fri, Jun 02, 2006 at 07:54:57AM +0000, John Eigelaar wrote: > I have been using the recent at91 usb driver to implement a USB-CDC > (USBSerial emulation ) device on an at91sam7s256 board. > > My CDC device enumarates properly and is seens as a serial port on both > Linux and Windows. If I however try to connect to the serial port with > either minicom or hyperterminal the serial application hangs. > > I could get hyperterminal to connect once and that work fine while the > session was connect but when I hanged up and tried again hyperterminal > hung. > > I previously ported the FraaRTOS CDC code to eCos, before there was any > at91 driver available, and that code works fine as a serial port. > > Any ideas on how to go about debugging this ? > Any experiences with USB-CDC would be appreciated. > > I have SnoopyPro and the diag serial port here at my disposal ... > > Thankx > John Eigelaar Hi John I did find what i think is one silicon bug in the AT91SAM7S. Maybe it is related? I found that the first Bulk OUT message on an endpoint did not always trigger an interrupt. It was only when the second Bulk OUT message arrived was the interrupt triggered and i could process both messages. After that it seemed to work O.K. This bug causes the eCos USB tester software a problem. It sends a single Bulk OUT message and then uses the control pipe to poll to see if the message has been received. After 10 polls it gives up and gives a warning. It then sends the next Bulk OUT message and another warning is then generated by the target because it received an unexpected message.... When do you see the problem? Do you receive the first Bulk OUT message? Andrew -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss