I think I know what happened here, my bootloader was not loading the whole binary and the romfs part got truncated.
Bin On 4/16/07, Bin Liu <[EMAIL PROTECTED]> wrote:
Hi, After ported uClinux 2.4.17 to a 5272 custom board, elf image was built with romfs and up and running fine, then I converted the image to binary format, with: #m68k-elf-objcopy -O binary images/image.elf image.bin the binary was loaded and booted with error message: Kernel panic: No init found. Try passing init= option to kernel This seems to me the romfs issue, since at the end of init, it was "Warning: unable to open an initial console." and then can not execute /bin/init and finally fell through to Kernel panic. then I looked into the init message, the ROMFS was actually there: 0: 8020000-80203FF [VIRTUAL 8020000-80203FF] (RO) <NONE> 1: 400F6E70-40180A6F [VIRTUAL 400F6E70-40180A6F] (RO) <ROMFS> and I tried to dump the first couple bytes of romfs, looks ok too: +++++++++++++++++++++ Dump buffer [400f6e70/32] +++++++++++++++++++ 0000: 2d 72 6f 6d 31 66 73 2d 00 08 98 30 f4 ed 0e e5 0000: - r o m 1 f s - . . . 0 . . . . 0010: 52 4f 4d 64 69 73 6b 00 00 00 00 00 00 00 00 00 0010: R O M d i s k . . . . . . . . . exactly the same as the working elf image. anybody could shed some light on this for me would be much appreciated. Thanks, Bin
_______________________________________________ uClinux-dev mailing list [email protected] http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by [email protected] To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
