maemo.org - Talk
Page 64 of 85 « First 546263 64 656674 Last »
Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Alternatives (https://talk.maemo.org/forumdisplay.php?f=36)
-   -   U-Boot for Nokia RX-51 with BootMenu (updated version 2012.10-rc3-1) (https://talk.maemo.org/showthread.php?t=81613)

Estel 2013-04-19 00:19
Re: U-Boot for Nokia RX-51 with BootMenu (updated version 2012.10-rc3-1)
 
Why so? using u-boot tools package, you can easily create u-boot with any attached kernel you like. Not to mention, that attaching kernels to u-boot is pointless - you can always boot from either eMMC or microSD stored kernel image, and this way you can forget flashing, when new KP comes out (only need to flash, when new u-boot appears). kernel is always loaded in RAM, anyway, so it's 0 difference if u-boot load it from NAND (attached), or from kernel image placed anywhere.

Except for fact, that with attached kernel, you need to flash them every time you want to have different one attached (usually, every new stable version of KP) - then it becomes almost equivalent of multiboot, re NAND war. So, attaching kernel is silly thing to do.

/Estel

Sohil876 2013-04-19 09:44
Re: U-Boot for Nokia RX-51 with BootMenu (updated version 2012.10-rc3-1)
 
Quote:
Originally Posted by Estel (Post 1337184)
Why so? using u-boot tools package, you can easily create u-boot with any attached kernel you like. Not to mention, that attaching kernels to u-boot is pointless - you can always boot from either eMMC or microSD stored kernel image, and this way you can forget flashing, when new KP comes out (only need to flash, when new u-boot appears). kernel is always loaded in RAM, anyway, so it's 0 difference if u-boot load it from NAND (attached), or from kernel image placed anywhere.

Except for fact, that with attached kernel, you need to flash them every time you want to have different one attached (usually, every new stable version of KP) - then it becomes almost equivalent of multiboot, re NAND war. So, attaching kernel is silly thing to do.

/Estel
How can i do that with uboot tools? . Btw, if there is a way i can boot into maemo with kp52 without opening keyboard (make kp52 kernel to boot as default instead of attached stock) then i am satisfied enough. The thing is, i have n900 (with cssu thumb) as my main phone now so i just want to be on safe side.

pali 2013-04-19 09:51
Re: U-Boot for Nokia RX-51 with BootMenu (updated version 2012.10-rc3-1)
 
@Sohil876: Read first post, where is writen how to boot some entry as default (also when keyboard is closed).

Sohil876 2013-04-19 09:57
Re: U-Boot for Nokia RX-51 with BootMenu (updated version 2012.10-rc3-1)
 
Quote:
Originally Posted by Estel (Post 1337184)
Why so? using u-boot tools package, you can easily create u-boot with any attached kernel you like. Not to mention, that attaching kernels to u-boot is pointless - you can always boot from either eMMC or microSD stored kernel image, and this way you can forget flashing, when new KP comes out (only need to flash, when new u-boot appears). kernel is always loaded in RAM, anyway, so it's 0 difference if u-boot load it from NAND (attached), or from kernel image placed anywhere.

Except for fact, that with attached kernel, you need to flash them every time you want to have different one attached (usually, every new stable version of KP) - then it becomes almost equivalent of multiboot, re NAND war. So, attaching kernel is silly thing to do.

/Estel

Quote:
Originally Posted by pali (Post 1337238)
@Sohil876: Read first post, where is writen how to boot some entry as default (also when keyboard is closed).
Oh, sorry, i missed it. I did read it some months ago and didnt bothered to re-read it, i will now :) , and thanks for the info.

Estel 2013-04-19 23:02
Re: U-Boot for Nokia RX-51 with BootMenu (updated version 2012.10-rc3-1)
 
Quote:
Originally Posted by Sohil876 (Post 1337234)
How can i do that with uboot tools? . side.
You just flash u-boot image without any kernel attached, either using flasher3.5 from desktop, or - more useful way, as it is independent from other devices - using flasher on device itself, as described here:
http://wiki.maemo.org/Overclocking#F...rom_X_Terminal

(while most info on that wiki page is completely outdated, flashing from terminal section remained actual, to this day).

Just be sure to do *both* commands as root. You can take u-boot image from uboot-booimg package - download it (*not* install, just download), unpack via dpkg-deb -x /path/to/download-u-boot-bootimg.deb /home/user/MyDocs, and you'll find image in one of extracted folders (u-boot.bin, IIRC).

Anegdote - using this method, I was able to remotely migrate device from multiboot to u-boot, without physical access to it (it was many kilometers away), and no one touching it - in addition, device was sitting behind NAT and firewall, that I had no access to. Everything was done via ssh (two sessions for flashing), and automatic reverse-ssh upon device reboots. No local intervention of anyone was required :)

/Estel

pali 2013-04-20 10:12
Re: U-Boot for Nokia RX-51 with BootMenu (updated version 2012.10-rc3-1)
 
New version of U-Boot 2013.04-1 is in Extras-Devel. There is support for ext2/3/4 MyDocs partition and booting 3.x kernels. Read first post.

Estel 2013-04-20 13:31
Re: U-Boot for Nokia RX-51 with BootMenu (version 2013.04-1)
 
Quote:
Originally Posted by pali (Post 1150740)
* u-boot-update-bootmenu can be configured to use different MyDocs, etc and boot paths (useful for non Maemo systems)
How? In orde to use diferent partition on eMMC, is it just matter of modifying:
Code:
ITEM_DEVICE="${EXT_CARD}p1"
...to contain INT_CARD and correct partition number?

This whole ITEM_DEVICE just tells u-boot on which partition to look for bootmenu.src file and bootmenu.img.d directory, yep? Or is it important for something else, too?

Quote:
Originally Posted by pali (Post 1150740)
How to create bootmenu entry for U-Boot:
copy kernel image zImage-my to /opt/boot/
create config file in /etc/bootmenu.d/ with suffix .item

Bootmeny entry for other system on SD card:

Code:
ITEM_NAME="My name"
ITEM_KERNEL="uImage"
ITEM_INITRD="uInitrd"
ITEM_DEVICE="${EXT_CARD}p1"
ITEM_FSTYPE="ext4"
ITEM_CMDLINE="kernel cmdline"
This means that you have SD card with first partition ext4. On that partition is kernel image with name uImage and initrd/initramfs file with name uInitrd (both generated by mkimage, see below
If I want to have entry for booting uImage of certain name from SD card, as kernel for Maemo (no matter what kernel I actually put there, under that filename), do I still need to use those ITEM_INITRD and ITEM_CMDLINE, just because I'm using SD card? or is it required only for non-Maemo systems?

If yes, what is diferent on non-Maemo systems, that they need it? May it be, that in case of Maemo, ITEM_OMAPATAG make it read all those things from hardcoded place, and it is why we need to specify them manually, in case of non ITEM_OMAPATAG=1?
---

/Estel

pali 2013-04-20 13:49
Re: U-Boot for Nokia RX-51 with BootMenu (version 2013.04-1)
 
Quote:
Originally Posted by Estel (Post 1337553)
How? In orde to use diferent partition on eMMC, is it just matter of modifying:
Code:
ITEM_DEVICE="${EXT_CARD}p1"
...to contain INT_CARD and correct partition number?

This whole ITEM_DEVICE just tells u-boot on which partition to look for bootmenu.src file and bootmenu.img.d directory, yep? Or is it important for something else, too?
No, you can specify different path to first eMMC partition. Maemo using /home/user/MyDocs, but you can mount it to other path... now u-boot-update-bootmenu will work if you change it (by specifing path param).

ITEM_DEVICE will tell u-boot-update-bootmenu where to find kernel and initfs images. bootmenu.img.d must be always on first emmc partition.

Quote:
Originally Posted by Estel (Post 1337553)
If I want to have entry for booting uImage of certain name from SD card, as kernel for Maemo (no matter what kernel I actually put there, under that filename), do I still need to use those ITEM_INITRD and ITEM_CMDLINE, just because I'm using SD card? or is it required only for non-Maemo systems?
ITEM_INITRD tells u-boot what initrd file to use when booting. ITEM_CMDLINE overwrite default cmdline hardcoded in kernel image.

Quote:
Originally Posted by Estel (Post 1337553)
If yes, what is diferent on non-Maemo systems, that they need it? May it be, that in case of Maemo, ITEM_OMAPATAG make it read all those things from hardcoded place, and it is why we need to specify them manually, in case of non ITEM_OMAPATAG=1?
ITEM_OMAPATAG=1 will tell u-boot to add omap atag with n900 data into atag linked-list. omap atag is needed to boot some kernels (e.g maemo kernel)

panjgoori 2013-04-21 11:51
Re: U-Boot for Nokia RX-51 with BootMenu (updated version 2012.10-rc3-1)
 
finally I successfully migrated from multiboot to u-boot without messing with my device. But my phones bootmenu is different than the image attached at first post by pali.
http://i.imgur.com/5HKgggR.jpg

alexporta 2013-04-21 11:58
Re: U-Boot for Nokia RX-51 with BootMenu (updated version 2012.10-rc3-1)
 
Quote:
Originally Posted by panjgoori (Post 1337714)
finally I successfully migrated from multiboot to u-boot without messing with my device. But my phones bootmenu is different than the image attached at first post by pali.
http://i.imgur.com/5HKgggR.jpg

I think u have installed bootmenu and backupmenu


All times are GMT. The time now is 04:58.
Page 64 of 85 « First 546263 64 656674 Last »
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8