Making Neo Brickproof, was comments after reading Wiki

2007-05-18 Thread Simon Matthews
It seems to me as someone who designs and makes embedded devices (mainly using the Freescale MC9S12 processors) that you need another lower level bootstrap loader that is small, can be protected and will either jump to the main bootstrap loader if it is functional or be able to download a new 2nd

Re: Making Neo Brickproof, was comments after reading Wiki

2007-05-17 Thread Simon Matthews
I would have thought it would be nice to avoid an extra chip. I noticed after a quick scan through the documentation on the flash currently being used by the Neo that there is one 16K block of OTP memory. Of course this would only be any good if it could be mapped to the addresses that get

Re: Making Neo Brickproof, was comments after reading Wiki

2007-05-17 Thread Emre Turkay
Hi folks, I would strongly support putting a no-way-writable ROM chip as this first level boot loader. If there is no such option, I really wonder what is my option if somehow it gets screwed up, other than the trash can? Is there an always working solution to reset my moko? Emre Turkay On

Re: Making Neo Brickproof, was comments after reading Wiki

2007-05-17 Thread Simon Matthews
Just had a further thought about what to do if the main bootstrap loader gets trashed that maybe easier to implement. Rather than a stage 1 bootstrap loader looking to the USB interface for a replacement how about looking on the SD card? Simon On Thu, 2007-05-17 at 01:58 -0300, Werner

RE: Making Neo Brickproof, was comments after reading Wiki

2007-05-17 Thread Heilpern, Mark
JTAG, via the debug port. From: [EMAIL PROTECTED] on behalf of Emre TurkaySent: Thu 5/17/2007 5:25 AMTo: community@lists.openmoko.orgSubject: Re: Making Neo Brickproof, was comments after reading Wiki Hi folks,I would strongly support putting a no-way-writable ROM chip as this first level

Re: Making Neo Brickproof, was comments after reading Wiki

2007-05-17 Thread Werner Almesberger
Simon Matthews wrote: I would have thought it would be nice to avoid an extra chip. Yeah, we tried, but it just doesn't seem to be possible :-( There are some alternatives, but they then lead to other problems, such as chips not being available in quantity, etc. (And we've had our number of

Re: Making Neo Brickproof, was comments after reading Wiki

2007-05-17 Thread Simon Matthews
On Thu, 2007-05-17 at 09:19 -0300, Werner Almesberger wrote: Yeah, we tried, but it just doesn't seem to be possible :-( There are some alternatives, but they then lead to other problems, such as chips not being available in quantity, etc. (And we've had our number of surprises with that.

Re: Making Neo Brickproof, was comments after reading Wiki

2007-05-17 Thread Werner Almesberger
Simon Matthews wrote: If you do find a chip with a small protected page i might be interested in writing the loader i have outlined. Thanks ! As long as the bootstrap code reprogramming is bullet proof or you don't see the need for changing the boot code i can't see any problems with one

Making Neo Brickproof, was comments after reading Wiki

2007-05-16 Thread Simon Matthews
It seems to me as someone who designs and makes embedded devices (mainly using the Freescale MC9S12 processors) that you need another lower level bootstrap loader that is small, can be protected and will either jump to the main bootstrap loader if it is functional or be able to download a new 2nd

Re: Making Neo Brickproof, was comments after reading Wiki

2007-05-16 Thread Werner Almesberger
Simon Matthews wrote: It seems to me as someone who designs and makes embedded devices (mainly using the Freescale MC9S12 processors) that you need another lower level bootstrap loader that is small, Ah yes, we've been through that idea as well :-) We rejected it, because we don't want to