u-boot/doc/README.davinci.nand_spl

2 A "make boardname" will compile a u-boot.ubl, with UBL Header, which is
3 needed for the RBL to find the "UBL", which actually is a  UBL-compatible
4 header, nand spl code and u-boot code.
7 As the RBL uses another read function as the "standard" u-boot,
11 (at the moment in board specific code) in the u-boot command
16 between the two NAND read/write modes.
26 On the cam_enc_4xx board we have a NAND flash with blocksize = 0x20000 and
27 pagesize = 0x800, so the u-boot.ubl image (which you get with:
54 After the spl code, there comes the "real" u-boot code
57 ------------------------------------------------------------------------
72 ------------------------------------------------------------------------
74 Burning into NAND:
78 Headers, so you have to burn the UBL header page from the u-boot.ubl
80 !! Don;t forget to switch to rbl nand read/write functions with
94 !! Don;t forget to switch to rbl nand read/write functions with
98 You need to copy the u-boot image to the block/page
100 !! Don;t forget to switch to rbl nand read/write functions with
106 -> this results in following NAND usage on the cam_enc_4xx board:
115 c0000		u-boot code
121 uboot=/tftpboot/cam_enc_4xx/u-boot.ubl
123 writeheader nandrbl rbl;nand erase 80000 ${pagesz};nand write 80000000 80000 ${pagesz};nandrbl uboot
124 writenand_spl nandrbl rbl;nand erase a0000 3000;nand write 80000800 a0000 3000;nandrbl uboot
125 writeuboot nandrbl uboot;nand erase c0000 5d000;nand write 80003800 c0000 5d000
128 If you do a "run load update" u-boot, spl + ubl header
129 are magically updated ;-)
132 - There seem to be a bug in the RBL code (at least on my HW),
137   a page 0 ... :-(
138 - If we make the nand read/write functions in the RBL equal to
139   the functions in u-boot (as I have no RBL code, it is only
140   possible in u-boot), we could burn the complete image in