Dear Ronen Shitrit,
In message <309002c0da137042828828fc53d7a9347e13537...@il-mb01.marvell.com> you
wrote:
>
> I'm not sure we are on the same page here, the Kirkwood has an
> internal bootROM which can only boot an image if this image is
> wrapped by a specific header.
There are tons of standards for image formats, and even more commonly
used formats I would not dare to call standard; but this processor
has to invent yet another one?
[Ronen Shitrit] I still think we are not on the same page here.
This isn't another image format...
Why do we need the bootrom?
For example the KW doesn't have HW NAND ECC support :(
But we still want to support boot from NAND and ve protected from upto 4 bit
ECC.
So the CPU wakes up and start running code from the bootROM (embedded ROM in
the Kirkwood) this code read the NAND and verify its ECC, then according to the
binary image header in the NAND it initialize the DRAM for this specific board
and copy the binary image from the NAND to the DRAM and start running from
there.
I hope now its more clear...
> The do_image should take the u-boot bin and wrap it with this header.
>
> How do u suggest we will support this header generation for the U-Boot?
Fix the hardware design?
[Ronen Shitrit] probably won't happen...
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de
"When anyone says `theoretically,' they really mean `not really.'"
- David Parnas
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
