Lines Matching +full:step +full:- +full:up

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
19 To set up mkimage you need a config file for mkimage, example:
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 ------------------------------------------------------------------------
58 Setting up spl code:
72 ------------------------------------------------------------------------
76 step 1:
78 Headers, so you have to burn the UBL header page from the u-boot.ubl
83 step 2:
97 step 3:
98 You need to copy the u-boot image to the block/page
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
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),
134   is possible to burn step 1 and step 2 in one step into the
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
141   one step ... that would be nice ...