Re: [Ltib] LPC31xx rootfs for U-Boot

[Stuart Hughes]

Hi Daniel,

I think you can safely ignore this output.  This comes from the u-boot envelope created by mkimage and purely reflects whether you passed the -a (load address) an/or the (-e) entry address.  From what I recall what matters is the address you download to (with tftp) and pass as the argument when you run bootm.

I'm not crystal clear on this, so it's worth checking.

Regards, Stuart

On 02/03/11 01:45, Daniel Widyanto wrote:

Hi,

 

It seems like the rootfs that's generated by LTIB for u-boot image is invalid:

----------------------------------------

creating a uboot ramdisk image: rootfs.ext2.gz.uboot

Image Name:   uboot ext2 ramdisk rootfs

Created:      Wed Mar  2 09:40:04 2011

Image Type:   ARM Linux RAMDisk Image (gzip compressed)

Data Size:    5181265 Bytes = 5059.83 kB = 4.94 MB

Load Address: 0x00000000

Entry Point:  0x00000000

 

Started: Wed Mar  2 09:34:46 2011

Ended:   Wed Mar  2 09:40:04 2011

Elapsed: 318 seconds

 

Build Succeeded

----------------------------------------

Its load address and entry point is 0x0.

 

Tested for EA3131 (LPC3131) platform. I'm not sure whether it happens for other platform too.

 

Regards,

-daniel

_______________________________________________
LTIB home page: http://ltib.org

Ltib mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/ltib