Thread: U-Boot for Nokia RX-51 with BootMenu (updated version 2012.10-rc3-1)
View Single Post
caveman is offline caveman
2012-08-26 , 10:32
Posts: 191 | Thanked: 415 times | Joined on Jan 2012
#483
1- im guessing that u-boot-gen-combined and fiasco-gen is only needed if you want to create a combined image which u dont need if you follow normal u-boot item creation and u-boot-update-bootmenu ?? am i right ?
if i understand it correctly, the combined image is the one attached to u-boot. You only need this if you want to change the default kernel from maemo to kp, for instance.

2- mkimage is used to convert the kernel to u-boot format uImage but do we need to manually copy boot.scr or is this copied by u-boot-update-bootmenu ?
what is the difference between zImage and uImage ?? the tar.gz archive is in zImage format while documentation refers to uImage sometimes..
u-boot-update-bootmenu does the conversion to uImage if necessary, and places the files automagically.

however, if you want to play with several kernels, it may be wise to make the conversion yourself and choose different names for the uImages, since u-boot seems to always use the same name.

3- when is the folder /user/MyDocs/bootmenu.img.d/ used ??
i would love to know that as well :-)

4- the kernel will be placed into /boot/ folder and i want to use p5 in my eMMC.. is this the right variables
ITEM_DEVICE="${INT_CARD}p5"
ITEM_CMDLINE="root=/dev/mmcblk0p5"
you do not need ITEM_DEVICE if your kernel is in /boot. the above variable points to a kernel in the eMMC, not in /boot.

I have been using the following procedure with fair success: manually convert the kernel images to uImages with a name that identifies the kernel, and place them at the root of the device. For instance, to boot from the uSD p2 using kernel vmlinuz-xxx I manually create uImage-xxx in uSD p2, and point u-boot to it.