From owner-freebsd-arm@FreeBSD.ORG Tue Jul 20 15:37:24 2010 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 780ED1065677 for ; Tue, 20 Jul 2010 15:37:24 +0000 (UTC) (envelope-from gja@ansley.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 3A94E8FC16 for ; Tue, 20 Jul 2010 15:37:23 +0000 (UTC) Received: by gwb19 with SMTP id 19so2906572gwb.13 for ; Tue, 20 Jul 2010 08:37:23 -0700 (PDT) Received: by 10.101.144.11 with SMTP id w11mr6712608ann.236.1279640242967; Tue, 20 Jul 2010 08:37:22 -0700 (PDT) Received: from G5.internal.ansley.com (99-135-104-139.lightspeed.tukrga.sbcglobal.net [99.135.104.139]) by mx.google.com with ESMTPS id 14sm75826757ant.21.2010.07.20.08.37.21 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 20 Jul 2010 08:37:22 -0700 (PDT) Sender: Greg Ansley Message-ID: <4C45C2AF.9030608@ansley.com> Date: Tue, 20 Jul 2010 11:37:19 -0400 From: Greg Ansley User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.5; en-US; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5 MIME-Version: 1.0 To: ticso@cicely.de References: <4C4590E5.1020407@ansley.com> <201007201405.43686.hselasky@c2i.net> <4C45A47A.8070403@ansley.com> <20100720135858.GA28908@cicely7.cicely.de> In-Reply-To: <20100720135858.GA28908@cicely7.cicely.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-arm@FreeBSD.org" , Bernd Walter Subject: Re: AT91RM9200: USB broken? No! X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Jul 2010 15:37:24 -0000 It's a QFP so the errors are OK. Turned out to be a bad solder joint on pin 1 of the USB connector (power). Connector on this card is not very mechanically stable with the mounting posts going into huge worthless holes. :-( Error messages were just a red herring, after not having seen them for weeks while working on the SAM9G20. Greg On 7/20/10 9:58 AM, Bernd Walter wrote: > So it looks like your device isn't noticed as being connected at all, > which is a bit strange because your error messages clearly show that > it got the faulty device connected from the secondary port. > >