bootm crash - bad uimage?

[Philippe Leduc]

Hi,

> So if you don't have an initrd, do you need uImage at all? You can boot
a bootable image directly
Well, I do it this way because it was working I guess^^' but I tink
your proposition is the right think to do!

Thank you for the tip and the details, I'll check that and I'll give
you a feedback ASAP :)

Best regards,

--
Philippe LEDUC
ledphilippe at gmail.com


2016-02-25 10:30 GMT+01:00 Holger Schurig <holgerschurig at gmail.com>:
> Philippe Leduc <ledphilippe at gmail.com> writes:
>
>> Note: I am using mkimage to create bootable image of a real-time OS
>> (PikeOS). There is no initrd or dtc at this step for now: I guess it
>> is like loading an old Linux kernel without userspace.
>
> So if you don't have an initrd, do you need uImage at all? You can boot
> a bootable image directly
>
> I use Linux without an initrd and don't bother with an uImage at all. I
> have my kernel on the SD-CARD or eMMC in /boot/vmlinuz, just like on any
> other (x86) Linux box.
>
> Here is my env/boot/emmc script. I use "boot", not "bootm", but AFAIK boot uses
> bootm under the hood.
>
>    global linux.bootargs.dyn.root="root=/dev/mmcblk0p${global.boot.partition} rootwait ro"
>    global bootm.image=/emmc/boot/vmlinuz
>    detect mmc3
>    mkdir -p /emmc
>    mount /dev/mmc3.0 /emmc
>
> I have similar scripts for SD-Card and USB.
>
>
> The kernel is installed using the normal Linux mechanism:
>
> make -C ${KERNEL_DIR} ARCH=arm INSTALL_PATH=${IMAGE_DIR}/boot zinstall
>
> maybe PikeOS has something equivalent. The result is:
>
> $ file image/boot/vmlinuz-4.4.2
> image/boot/vmlinuz-4.4.2: Linux kernel ARM boot executable zImage (little-endian)
>
>
>
> As you see, I boot directly into the vmlinuz ... and I don't use
> Barebox' CONFIG_DEFAULT_ENVIRONMENT_GENERIC_NEW, too.