Active Topics
-
The N900 is now 15 years old! (9)
to Nokia N900 by Arno_11 - 50 mins ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 5 days, 13 hrs ago - more...
|
2011-09-18
, 03:14
|
|
Posts: 1,042 |
Thanked: 430 times |
Joined on May 2010
|
#62
|
omg! Pali's uboot won't work on me. Same situation I had with matan's modified uboot. An infinite reboot loop. 
It just won't load noloboot. don't know about others.
Coul you by chance provide a diff file for the master of uboot? or at least the source, would like to see what's wrong
or at least could someone with more knowledge with this look into it? Matan said this is a problem with different hardware revisions.
Last edited by Radicalz38; 2011-09-18 at 03:22.
It just won't load noloboot. don't know about others.
Coul you by chance provide a diff file for the master of uboot? or at least the source, would like to see what's wrong
or at least could someone with more knowledge with this look into it? Matan said this is a problem with different hardware revisions.
Last edited by Radicalz38; 2011-09-18 at 03:22.
|
|
2011-09-18
, 06:53
|
|
Posts: 2,154 |
Thanked: 8,464 times |
Joined on May 2010
|
#63
|
Source code are on gitorious: https://gitorious.org/u-boot-shr/u-b...ts/pali-master
@mirakels:
mmcnum for SD card was in ali's patch 0 and for eMMC 2. I used ali's patch, so ask ali if it is correct, I'm not sure.
Booting from SD or eMMC is done in this order:
1. try to load boot script /boot.scr from first FAT partition
2. try to load kernel image /uImage from fisrt FAT partition
3. try to load boot script /boot.scr from second FAT partition
4. try to load kernel image /uImage from second FAT partition
5. same for 3. and 4. FAT partition
... same as 1-5 but try partition type Ext
boot script is U-Boot language Hush text script converted by mkimage
uImage is kernel image generated from zImage/uImage by mkimage
@Radicalz38:
maybe it is really problem with different HW revisions. First try to only load image, not flashing!!! This prevent infinite reboot loop.
If you have a problem with booting glued kernel image, choose "U-Boot console" in menu and write "run noloboot". Then if you can write output.
Also use pr1.3 kernel image with framebuffer support (u-boot+pr1.3+fb.bin), maybe you will see some more errors in console.
Last edited by pali; 2013-04-20 at 12:41.
@mirakels:
mmcnum for SD card was in ali's patch 0 and for eMMC 2. I used ali's patch, so ask ali if it is correct, I'm not sure.
Booting from SD or eMMC is done in this order:
1. try to load boot script /boot.scr from first FAT partition
2. try to load kernel image /uImage from fisrt FAT partition
3. try to load boot script /boot.scr from second FAT partition
4. try to load kernel image /uImage from second FAT partition
5. same for 3. and 4. FAT partition
... same as 1-5 but try partition type Ext
boot script is U-Boot language Hush text script converted by mkimage
uImage is kernel image generated from zImage/uImage by mkimage
@Radicalz38:
maybe it is really problem with different HW revisions. First try to only load image, not flashing!!! This prevent infinite reboot loop.
Code:
sudo flasher flasher-3.5 -k image.bin -l -b
Also use pr1.3 kernel image with framebuffer support (u-boot+pr1.3+fb.bin), maybe you will see some more errors in console.
Last edited by pali; 2013-04-20 at 12:41.
| The Following 5 Users Say Thank You to pali For This Useful Post: | ||
|
|
2011-09-18
, 09:13
|
|
Posts: 197 |
Thanked: 101 times |
Joined on Dec 2009
@ Netherlands
|
#64
|
Paili Radicalz38,
I still run power kernel 45. It has u-boot working fine (although with some older u-boot version:U-Boot 2010.06-00697-g61ab171-dirty (Oct 29 2010 - 04:14:37)). But If I escape the boot sequence in this u-boot I can type a few commands and then the device shuts down.
(I is not a matter of what commands I use. even without commands it shuts down after 10 seconds or so). This is not enough time to enter all the commands to specify a kernel on the sdcard manually :-(
From the kernel-power debian rules I notice that a kernel image is also run through the fiasco-gen command. Has that been done with the image.bin files you supplied Pali? maybe this is the reason for Radicalz38 reboot loop?
I still run power kernel 45. It has u-boot working fine (although with some older u-boot version:U-Boot 2010.06-00697-g61ab171-dirty (Oct 29 2010 - 04:14:37)). But If I escape the boot sequence in this u-boot I can type a few commands and then the device shuts down.
(I is not a matter of what commands I use. even without commands it shuts down after 10 seconds or so). This is not enough time to enter all the commands to specify a kernel on the sdcard manually :-(
From the kernel-power debian rules I notice that a kernel image is also run through the fiasco-gen command. Has that been done with the image.bin files you supplied Pali? maybe this is the reason for Radicalz38 reboot loop?
|
|
2011-09-18
, 09:28
|
|
Posts: 2,154 |
Thanked: 8,464 times |
Joined on May 2010
|
#65
|
If you running old version of U-Boot without R&D mode, it should reboot your device after few seconds. It is because old version does not have implemented watchdog kicker and when device is not in R&D mode with disabled watchdog, hw reset device. New version, of cource, has this problem fixed.
fiasco-gen is program which generate fiasco images. Flasing kernel (or other part) can be done also in device without PC. But it needs to be in fiasco format. So this is reason why kernel(-power) generate fiasco image.
Last edited by pali; 2012-06-06 at 14:17.
fiasco-gen is program which generate fiasco images. Flasing kernel (or other part) can be done also in device without PC. But it needs to be in fiasco format. So this is reason why kernel(-power) generate fiasco image.
Last edited by pali; 2012-06-06 at 14:17.
| The Following User Says Thank You to pali For This Useful Post: | ||
|
|
2011-09-18
, 11:41
|
|
Posts: 197 |
Thanked: 101 times |
Joined on Dec 2009
@ Netherlands
|
#66
|
Thanks Pali for the exlanations!
I installed the power48 modules manually and the started the u-boot+kp48.bin using the flasher-3.5 on my laptop.
Runs fine now! So I probalby can flash the .bin without problems now
Only noticed I lost the /sys/class/power_supply/bq27200-0/uevent
file to get battery status info. Is this because of the I2C issues I read about in other threads/irc?
With your u-boot I probably would be able to play around booting kernels from other (sdcard) partitions. I'll play with that in the next weeks...
I installed the power48 modules manually and the started the u-boot+kp48.bin using the flasher-3.5 on my laptop.
Runs fine now! So I probalby can flash the .bin without problems now
Only noticed I lost the /sys/class/power_supply/bq27200-0/uevent
file to get battery status info. Is this because of the I2C issues I read about in other threads/irc?
With your u-boot I probably would be able to play around booting kernels from other (sdcard) partitions. I'll play with that in the next weeks...
|
|
2011-09-18
, 11:50
|
|
Posts: 2,154 |
Thanked: 8,464 times |
Joined on May 2010
|
#67
|
Originally Posted by mirakels
Problem between BME and bq27x00_battery kernel module. For more info read kernel-power thread.
Only noticed I lost the /sys/class/power_supply/bq27200-0/uevent
file to get battery status info. Is this because of the I2C issues I read about in other threads/irc?
|
|
2011-09-18
, 12:41
|
|
Posts: 197 |
Thanked: 101 times |
Joined on Dec 2009
@ Netherlands
|
#68
|
hm played a bit with the new u-boot image and got into u-boot console
when i give the command 'mmc init' it says 'No MMC card found'.
I'm sure there is one... when let it boot with noloboot it do have access to the sdcard when when the system is u and running...
bit lost again.
when i give the command 'mmc init' it says 'No MMC card found'.
I'm sure there is one... when let it boot with noloboot it do have access to the sdcard when when the system is u and running...
bit lost again.
|
|
2011-09-19
, 19:29
|
|
Posts: 197 |
Thanked: 101 times |
Joined on Dec 2009
@ Netherlands
|
#69
|
apperantly it looses mmc sometimes but today it did see the sdcards again.
I was able to start an sdcard containing meego (but installed a dev version so only got a xterm).
But starting an sdcard containing nitdroid failed. It starts the kernel, but then says it cannot find any filesystem for root. It shows a list of tried filesystem (types) but the list is emty. Apperantly it needs some sort of initrd image with filesystem drivers. Also tried flasher-3.5 -l -b to boot the nitdroid kernel passing the bootargs like defined in the multiboot nitdroid entry but this also failed with the same message.
Wonder how multiboot does this....
I was able to start an sdcard containing meego (but installed a dev version so only got a xterm).
But starting an sdcard containing nitdroid failed. It starts the kernel, but then says it cannot find any filesystem for root. It shows a list of tried filesystem (types) but the list is emty. Apperantly it needs some sort of initrd image with filesystem drivers. Also tried flasher-3.5 -l -b to boot the nitdroid kernel passing the bootargs like defined in the multiboot nitdroid entry but this also failed with the same message.
Wonder how multiboot does this....
|
|
2011-09-21
, 11:15
|
|
Posts: 1,042 |
Thanked: 430 times |
Joined on May 2010
|
#70
|
Originally Posted by pali
Hi pali! Yes I did load only the image and it's still stuck. Also tried booting it manually through console with run noloboot but it just shows that it's loading then reboot(like matan's uboot again) no errors whatsoever. Although stskeep's uboot worked fine for me.
Source code are on gitorious: https://gitorious.org/u-boot-shr/u-b...ts/pali-master
@mirakels:
mmcnum for SD card was in ali's patch 0 and for eMMC 2. I used ali's patch, so ask ali if it is correct, I'm not sure.
Booting from SD or eMMC is done in this order:
1. try to load boot script /boot.scr from first FAT partition
2. try to load kernel image /uImage from fisrt FAT partition
3. try to load boot script /boot.scr from second FAT partition
4. try to load kernel image /uImage from second FAT partition
5. same for 3. and 4. FAT partition
... same as 1-5 but try partition type Ext
boot script is U-Boot language Hush text script converted by mkimage
uImage is kernel image generated from zImage/uImage by mkimage
@Radicalz38:
maybe it is really problem with different HW revisions. First try to only load image, not flashing!!! This prevent infinite reboot loop.
If you have a problem with booting glued kernel image, choose "U-Boot console" in menu and write "run noloboot". Then if you can write output.Code:wget http://atrey.karlin.mff.cuni.cz/~pali/u-boot+pr1.3+fb.bin -O image.bin sudo flasher flasher-3.5 -k image.bin -l -b
Also use pr1.3 kernel image with framebuffer support (u-boot+pr1.3+fb.bin), maybe you will see some more errors in console.
By the way I flashed the bin file on device using softupd command. Do you have a diff file there? somehow i can't access gitorous now I don't know why lol! *sigh* only wanted that iemmc command
I noticed the bootmenu allows to boot from Internal eMMC or SDcard.
For eMMC it chooses mmcnum 2and for SDcard mmcnum 0. Is this correct?
Looking on the n900 I see eMMC on mmcblk0 and SDcard on mmcblk1.
So I would expect mmcnum 0 for eMMC boot and mmcnum 1 for SDcard.
Or am i Missing something?
I like to setup a sdcard with nitdroid and start it using u-boot SDcard...
Do you know how the nitdroid kernel should be 'formatted' te bea ble to boot it roperly. I expect I need to pass some kernel perms to select rootfs etc, but
I am a bit confused on how to do that...
Thanks for any help!