Hi,
On 31 July 2014 02:24, Duxiaoqiang <duxiaoqi...@huawei.com> wrote: > Hi Simon > > > >> This problem has confused me several days, I will appreciated if you > can give me susggestions. > > >You could try 'setenv verify n' to turn off verification. That will make > sure that the problem is actually related to verified boot. Does the image > boot OK without verified boot? > > ################Added by Jason############## > I tried "setenv verify n", but boot the image is not OK. So the problem > should not related verified boot. > > >It says: > > >> Loading Device Tree to 000000009fe00000, end 000000009fe04a91 ... > >> fdt_rsv_mem_addr = 00000000c32b2540 > > >Is that a valid address? What addresses are the kernel, FDT and ramdisk > loaded to when you use the legacy image? > > I think the address is normal, I run on foundation platform, the physical > memory space is up to 4G. > I used to load legacy image as bellow: > Kernel Image load/entry: 0x90000000 > Fdt blod address:0xa0000000 > Ramdisk : 0xa1000000 > Uboot code section: 0x88000000 > > The address space for now new FIT image > Kernel Image load/entry: 0x89000000 > Fdt blob: It is relocated by uboot, speculate from debug information, it > is 0x9fe00000 > RAM disk: It is set to 0xaa000000 at FIT file, but relocated by uboot. > Speculate from debug information, the address is 0xe7c83000 > Uboot code section:0x88000000 > FIT image to be load:0xc3000004 > Well then I'm not sure what is going on, but it is probably worth debugging into the kernel and asking on the kernel mailing list. Perhaps with a debugger attached you might figure out where it goes into the weeds? - Simon
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
