R70/R71 on debug v3 board ?

Andy Green andy at openmoko.com
Mon Feb 11 11:01:49 CET 2008

Hash: SHA1

Somebody in the thread at some point said:

> Anything that can be done in software is not a sufficient level of
> protection.  We want to reliably claim that this nor flash is read-only,
> and that users can always recover, no matter what they do on the
> software side.

How about if it doesn't ship with flash_unlock?

> In fact, the NOR flash is only for users who don't have a debug board.
> Users that have a debug board can always recover via jtag.  So making
> this dependent on the debug board is a perfect solution.

I can see the logic, but I can also see it puts us in a unique position
with it for the next couple of weeks until RTM, we're not going to be
able to generally update whatever it is we put in there subsequently.

That's annoying because it seems soon we will discard U-Boot and move to
using a kexec-ed kernel directly (thus getting out of this crazy system
of implementing things twice once for kernel and once for U-Boot).  And
we have 2MByte NOR there that can do this.

We can recover a bricked device with the debug board, it seems to me we
take so much care avoiding the one scenario we create a problem along
with definitively fixing the possibility of corruption and that has to
be balanced.

- -Andy
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org


More information about the openmoko-kernel mailing list