X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Date: Fri, 2 Dec 2011 11:17:30 +0100
From: Attila Kinali <attila AT kinali DOT ch>
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] Re: I won't do BGA's
Message-Id: <20111202111730.4dc40e16.attila@kinali.ch>
In-Reply-To: <1322820268.12553.4.camel@localhost>
References: <CA+82U9J4GvssKrnRNOTTMuDc4zHy+PxeWb8OXeWP6NVHfoA0Nw AT mail DOT gmail DOT com>
	<1486241a-88b7-4c8d-8354-ded392eadf96 AT email DOT android DOT com>
	<CAA0yOM6e_raSs_3tBv_+1OTNj+cZdN91cJU3hKkeW90E23z4nA AT mail DOT gmail DOT com>
	<CA+82U9+CzLMdBvyyJxsYWR==BXWjWGrU+zWNXL+-g9tsh7uLbw AT mail DOT gmail DOT com>
	<CAA0yOM5ej1dMOOtcbYYRdc=7yW6hZj=cmpuypYt9c_X_k5NM7A AT mail DOT gmail DOT com>
	<CA+82U9+2pQBscOYsWBbLPtEpb1MyTEKe5dr8wzdJYJnFqCjWgw AT mail DOT gmail DOT com>
	<CAA0yOM5+uj6cHuxVsz18SPqd=ULC_-EbaUb0ffj14wkdj_dHiQ AT mail DOT gmail DOT com>
	<4EC9CE99 DOT 5040303 AT industromatic DOT com>
	<4ED27309 DOT 6030100 AT ecosensory DOT com>
	<20111127231842 DOT 3FD9B81F6262 AT turkos DOT aspodata DOT se>
	<4ED30BB2 DOT 8030301 AT ecosensory DOT com>
	<20111128075947 DOT F0D6681F6266 AT turkos DOT aspodata DOT se>
	<4ED36081 DOT 5080507 AT ecosensory DOT com>
	<CAPYb0EEtYnpYkTNygCJCkYG7bk3jZu3WHx09C023RWXqDCHyrg AT mail DOT gmail DOT com>
	<20111202101147 DOT 04de74dd DOT attila AT kinali DOT ch>
	<1322820268 DOT 12553 DOT 4 DOT camel AT localhost>
Organization: GEHIRN
X-Mailer: Sylpheed 3.1.0 (GTK+ 2.24.7; i686-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-user AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On Fri, 02 Dec 2011 10:04:28 +0000
Peter Clifton <pcjc2 AT cam DOT ac DOT uk> wrote:


> > Beside the USB core of the Atmel SAM7 having silicon bugs that
> > can cause a lock up of the system and the documentation being
> > plain wrong at some points (leading to lock up as well, and
> > the mistakes being obvious if you know how USB works), the USB code
> > provided by Atmel is a bug hole of the likes i have not seen many...
> 
> Do you have any references to the errata, or happen know whether these
> bugs are present in the SAM3U parts?

They never made it into any errata. As i said, i've been completely
ignored. I don't know whether these are present in the SAM3*. I give
them a 50% chance. The USB core on the SAM3 has been redone (supporting
HS now) and it could be that they learned from their mistakes. But
it could also very well be that they just modified the SAM7 USB core
to support HS and stopped there. I cannot say. I haven't had the
chance to work with the USB core of the SAM3 yet.

> I ask, as I'm working on a design with one of these at the moment, and
> getting the USB working well is going to be high on the priority list
> once we get a board up.

As i said: Go for rewriting the USB code. You can use the Atmel code
for the first tests, but if you want to have reliable operation, write
your own. As a side effect of the rewirte we've done, we have now
a USB code that can be used in medical products :-)

 
			Attila Kinali

-- 
The trouble with you, Shev, is you don't say anything until you've saved
up a whole truckload of damned heavy brick arguments and then you dump
them all out and never look at the bleeding body mangled beneath the heap
		-- Tirin, The Dispossessed, U. Le Guin