El 22/10/13 18:41, Jon escribió:
Here is how I generate the ramdisk mkimage -A arm -O linux -T ramdisk -C none -a 0x00000000 -e 0x00000000 -n "ramdisk" -d /boot/initramfs-X.YY.Z-foo.fcNN.armv5.img /tmp/uImage Note the address and entry point are zeros. On your board's u-boot environment just run the 'bdi' command (board info) to findout the start addr and size. You can workout load addr's that make your boot happy. I would advise loading the ramdisk first, in the begining space of the memory... then load the kernel. That way if there is any overlap it will be the ramdisk that is corrupted, not the kernel memory.
How do I peek into the initramfs memory from within the Linux system, in order to check the actual contents to see where the corruption is? Is there any block device to check? _______________________________________________ arm mailing list arm@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/arm
