17/09/2004 11:02:18, Wookey <
wookey@aleph1.co.uk> wrote:
>An alarm rings...
Uh-oh...
>but the 'frippery' like the NAND is where all the code is going to
be
>running from, and that code needs to do the 'reprogram the
FPGA on wake-up',
>which sounds like a problem. Or is the point that this code will
be living
>in the bootloader which will have to remain in nor precisely
because you
>can't talk to the NAND on boot.
Yep.
If people later want to do cunning things with FPGA images and
keep them in RAM, that's fine, too. Care is needed, but it's no
showstopper. Basically, the safe way to resume is to just copy a
chunk of the boot rom to the FPGA, however you like. Should take
a couple of milliseconds.
>Hmm - and are you considering moving to 2K page/16bit nand
(which needs
>YAFFS2 for best effect).
Yes, definitely. It would be nice to see this tested on Balloon2
before releasing Balloon3, but, since it will be soft FPGA
functionaily, it's no great worry.
>YAFFS2 is underway again, after something of a pause whilst
Chalres had other
>stuff on his mind. Hopefully it'll be ready before balloon3.
Super. If you need a 16-bit NAND chip soldering onto a balloon2,
let me know.
Steve
(text/plain)