delorie.com/archives/browse.cgi   search  
Mail Archives: geda-user/2011/12/02/04:12:06

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 10:11:47 +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: <20111202101147.04de74dd.attila@kinali.ch>
In-Reply-To: <CAPYb0EEtYnpYkTNygCJCkYG7bk3jZu3WHx09C023RWXqDCHyrg@mail.gmail.com>
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>
Organization: GEHIRN
X-Mailer: Sylpheed 3.1.0 (GTK+ 2.24.7; i686-pc-linux-gnu)
Mime-Version: 1.0
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id pB29BwaA013087
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

On Tue, 29 Nov 2011 20:10:08 -0500
Bob Paddock <bob DOT paddock AT gmail DOT com> wrote:

> On Mon, Nov 28, 2011 at 5:20 AM, John Griessen <john AT ecosensory DOT com> wrote:
> 
> > AT91SAM  is one I've heard of that might do and has a flat pack package.
> 
> Personally I avoid the Atmel ARM parts.  When they first came out with
> USB parts I ran them through many Due Diligence tests.
> I found that the USB part worked just fine if your PC had an Intel
> host controller, but they didn't work if you had an NEC host
> controller.
> 
> When I reported that back to Atmel, the answer came back from Atmel
> France (now closed) the originator of the Atmel ARM, as "You are to
> stupid to use our part".
> Maybe I'm not the smartest person in the world, but how much brain
> power does it take to move the USB cable between two ports on the same
> PC?

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...
It works in the most simple cases with only a specific windows
version as host. Any change in the device behaviour or windows
driver will lead to unpredictable results (ok, with windows it's
quite predictable: blue screen).

My recomendation, if you want to work with the SAM7's USB, write your
own USB code using the Atmel code as an (bad) example on how to do it.

Oh yes.. reporting those bugs to Atmel lead to being ignored...

			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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019