On 04/28/2012 04:32 AM, Shengzhou Liu wrote: > +2. Burn u-boot.bin into NOR flash > + => tftp 1000000 u-boot.bin > + => protect off all > + => erase eff80000 efffffff > + => cp.b 1000000 eff80000 80000
=> tftp <filename> => protect off all => erase eff80000 +$filesize => cp.b $loadaddr eff80000 $filesize > +Build and burn u-boot to NAND flash > +======================================== > +1. Build u-boot.bin image > + export ARCH=powerpc > + export CROSS_COMPILE=/your_path/powerpc-linux-gnu- > + make P1010RDB_NAND > + > +2. Burn u-boot-nand.bin into NAND flash > + => tftp 1000000 u-boot-nand.bin > + => nand erase 0 80000 > + => nand write 1000000 0 80000 => tftp <filename> => nand erase 0 $filesize => nand write $loadaddr 0 $filesize ...etc. > +Build kernel and dtb for P1010RDB > +================================= > +set proper cross-compile for powerpc > + cp arch/powerpc/configs/mpc85xx_defconfig .config > + make -j 16 > + make p1010rdb.dtb > +then uImage and p1010rdb.dtb will be generated under arch/powerpc/boot/ I doubt most people will want to use -j 16. Why are kernel build instructions in a U-Boot readme? Shouldn't you be building the uImage target? > +Boot Linux from RAM on P1010RDB > +================================== > +Place uImage and p1010rdb.dtb in the TFTP disk area. > + => tftp 1000000 uImage > + => tftp 2000000 p1010rdb.dtb > + => tftp 3000000 rootfs.ext2.gz.uboot.p1010rdb > + => bootm 1000000 3000000 2000000 I'd call that "booting from the network using TFTP" rather than "booting from RAM"... -Scott _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
