Hello,
On Wed, Dec 3, 2008 at 8:40 AM, Trent Piepho <[EMAIL PROTECTED]> wrote:
> On Wed, 3 Dec 2008, Sean MacLennan wrote:
>>> Yes, I would recommend to do it this way if possible. A small NOR for
>>> U-Boot and environment and everything else in NAND. This makes things
>>> much easier. But I unde
On Wed, 3 Dec 2008, Sean MacLennan wrote:
>> Yes, I would recommend to do it this way if possible. A small NOR for
>> U-Boot and environment and everything else in NAND. This makes things
>> much easier. But I understand that this is sometimes a problem with
>> space (2 FLASH chips) and costs.
>
>
On Wed, 3 Dec 2008 06:48:57 +0100
"Stefan Roese" <[EMAIL PROTECTED]> wrote:
> Currently you need to define the page-size of the NAND used for
> booting (512 bytes vs. 2k). The 2k 4xx NAND booting support is was
> done about 1/2 a year ago. So perhaps you tested this when this 2k
> support was not
On Wednesday 03 December 2008, Sean MacLennan wrote:
> We use a 256M NAND on the PIKA Warp appliance and where unable to boot
> u-boot from the NAND. It worked on a smaller 64M NAND.
Currently you need to define the page-size of the NAND used for booting (512
bytes vs. 2k). The 2k 4xx NAND bootin
Disclaimer: I'm not running ppc these days
> However, having no NOR flash means:
> - NAND should be programmable via JTAG (BDI3000 doesn't support
> this, Lauterbach/trace32 does)
My personal preference for bringing up a new board is placing u-boot
in RAM using the available information to
