>
>
> > >
> > > >
> > > > >
> > > >>> AVR studio up and running in minutes.
>
> > > >> Not bad for FREE !
>
> > > > Not for me. =A0I had trouble with AVR Studio 4 on XP, along with ma=
ny
> > > other programs.
> > > > But I don't care, WinAVR and Makefile work fine for me.
>
> > > >>> At least with printf running I can start debugging
>
> > > >> Glad to hear that you got something working.
>
> > > >> Now you can focus on your project and not worry about the compiler=
.
> > > >> Which ATmega are you using ?
>
> > > > At90USB162/Atmega32u2/At90usb646.
>
> > > I have seen that you (linnix) know about ATmegas.
>
> > Yes, "Anda" and many others are using my boards. =A0See her post above.
>
> I don't have it yet. =A0I hear that people are using this to jail-break
> PS3. =A0Is that right?
>
>
>
> > > I was wondering about what Raveninghorde might be using.
>
> > > It seems that getting a project (product) running gets lost in the
> > > choice of tools.
>
> > There are tons of examples available on Atmel and other sites. =A0Check
> > out the Atmel USBKEY, but with different chips.
>
> > > For as long as WINAVR and AVRstudio have been around, it would seem t=
hat
> > more people would know about it.
>
> > And we do. =A0Most of us are hanging around comp.arch.embedded.
Yes, and there are long stories behind it.
We developed them for a customer's digital security key, similar to the "X.509 thread" in CAE. However, some hackers got hold of it and turn them into PS3 unkey, since Sony stopped supporting Linux. They were trying to re-enable Linux on their PS3, which is still in progress. Other PS3 users start using them to backup their blue-ray disc onto the hard drive. Some are running their games on broken blue- ray drive, which is the most fragile part of the PS3.
The way Sony (QA/QC people) and the hackers do are very interesting. I will follow up with another post with details. I need to go do something else first.