X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Cam-AntiVirus: no malware found
X-Cam-SpamDetails: not scanned
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Message-ID: <1322820268.12553.4.camel@localhost>
Subject: Re: [geda-user] Re: I won't do BGA's
From: Peter Clifton <pcjc2 AT cam DOT ac DOT uk>
To: geda-user AT delorie DOT com
Date: Fri, 02 Dec 2011 10:04:28 +0000
In-Reply-To: <20111202101147.04de74dd.attila@kinali.ch>
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>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature";
	boundary="=-lPdmK3PEeClinznyBtf4"
X-Mailer: Evolution 3.2.2- 
Mime-Version: 1.0
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


--=-lPdmK3PEeClinznyBtf4
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, 2011-12-02 at 10:11 +0100, Attila Kinali wrote:
> On Tue, 29 Nov 2011 20:10:08 -0500
> Bob Paddock <bob DOT paddock AT gmail DOT com> wrote:
>=20
> > On Mon, Nov 28, 2011 at 5:20 AM, John Griessen <john AT ecosensory DOT com> wr=
ote:
> >=20
> > > AT91SAM  is one I've heard of that might do and has a flat pack packa=
ge.
> >=20
> > 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.
> >=20
> > 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?
>=20
> 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?

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.

> 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).
>=20
> 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.
>=20
> Oh yes.. reporting those bugs to Atmel lead to being ignored...

Oh joy.

Best wishes,

Peter Clifton

--=-lPdmK3PEeClinznyBtf4
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAABAgAGBQJO2KKsAAoJEOo4D/b1x+QVySIH/i9JYi2kwgqY0ZagiYDQhMKy
Qzn4X2IVlwZq41j8G6W5ERHZlxsuucadwFsjYgIV2D0RbOd5LAADZdNc04kPehY/
OgM8ZBlnddbS3wYRdL5hxnrLpYY0qH6s3srImLHaAOQcx9cSmXeQKMukO4MU0Upp
Wv7ty4EtojPOjAqErxG1v/+rUTJwCL1RYgt7UUNV+u8ULDQBI05D98lgbTNTjxIX
8d8NROGkA7Y9aorP5YKlBUezqvR+Sxfp/MzKCXpZ0I5GpIGaWuGLJ9yJY5ZxXEtL
/SI6yGQzCAHcGKQCyQTQCEGM5vGPmOK/J42BleCNk0QzWYiYSMP7D1/S7iUc5WU=
=vBxE
-----END PGP SIGNATURE-----

--=-lPdmK3PEeClinznyBtf4--