CENTIPAD boot

[Bernd Walter]

On Wed, Aug 08, 2007 at 09:39:20AM -0600, M. Warner Losh wrote:
> In message: <46B9DD23.70608 at bulinfo.net>
>             Krassimir Slavchev <krassi at bulinfo.net> writes:
> : > Please split BOOT_BWCT and BOOT_CENTIPAD here, since I localy have
> : > 0xAC added as a valid status:
> : > #ifdef BOOT_BWCT
> : >         value = GetFlashStatus();
> : >         if ((value  & 0xFC) != 0xAC
> : >             && (value  & 0xFC) != 0xB4)
> : >                 printf(" Bad SPI status: 0x%x\n", value);
> : > #else
> : > This is because I use AT45DB161D chips in production.
> : > The 0xB4 is from the AT45DB321C, which I'd used in prototypes only.
> : > I might use other SPI types for special purspose as well.
> : 
> : Feel free to change anything you wish!
> 
> I think we need just a little more smarts here.  What this check is
> doing is making sure that the ID is sane, which doesn't make sense for
> a general solution.

It might not be important for the normal use.
I locally use it for post production tests, but I've added memory tests
as well, so I can quickly find out if there is a data or address line
failure, which is active in boot0spi only and won't get shipped.
But I know what I can expect from the SPI, so just printing the value
will have the same effect.
When we do the SPI autoprobing one day and print the result, this is
likely to be even better.
Patching the binary with the correct dataflash parameters should be
easy.

-- 
B.Walter                http://www.bwct.de      http://www.fizon.de
bernd at bwct.de           info at bwct.de            support at fizon.de