Re: u-boot for the RX-51 (N900)
 

I pushed new (rebased) patches to git repository on gitorious.
* deleted ali patch which relocated u-boot in reset function (I moved and rewritted code to rx51.c)
* added patch which enable appending atags to existing (based on mirakels patch)
* rebased on top of u-boot master again

In this build I see problem with eMMC again :( - not working. But I did not change anything with eMMC, so problem must be in upstream code...

===

Two things missing for sending patches to upstream:
1. fix eMMC support again
2. correct display brightness support

Re: u-boot for the RX-51 (N900)
 

Problem with eMMC was found :)
Caused by commit:
02f3029f1810b99869254d0cf0a71946a008a728 mmc: retry the cmd8 to meet 74 clocks requirement in the spec:
http://git.denx.de/?p=u-boot/u-boot-...a71946a008a728

After reverting this commit eMMC working again...

Re: u-boot for the RX-51 (N900)
 

Quick question: u-boot+kp 49 does not work with the default meego ce image out of the box. Is there a boot.scr for that configuration and where should I put it? (I think that the default Meego CE image has a fat /boot partition so that it works with uboot-pr13)

uboot-pr13 and uboot from the shr website confirmed to work with the same Meego CE sd card.

Re: u-boot for the RX-51 (N900)
 

ive got the same problem as above. yet when i flashed to stock and stock uboot, i had an error still.

Re: u-boot for the RX-51 (N900)
 

You need to create bootmenu configuration file (bootmenu.scr in MyDocs)

Re: u-boot for the RX-51 (N900)
 

thank you soo much :D this is how i boot into it now


setenv bootmenu_4 'MeegoBoot (External SD card, partition 3, fat, uImage)=setenv mmcnum 0; setenv mmcpart 3; setenv mmctype fat; setenv mmcfile uImage; run trymmcuimage';

Re: u-boot for the RX-51 (N900)
 

You can also specify only 3 entires (if you want):
bootmenu_0 for Maemo5 kernel
bootmenu_1 for Meego
bootmenu_2 for end of bootmenu

last entry must always exists and must be empty!

Re: u-boot for the RX-51 (N900)
 

i dont really have a last entry? is it required? since everything seems to run fine

Re: u-boot for the RX-51 (N900)
 

if you are sure that variable after last entry is not defined it should be ok (I checked u-boot code), but it could not be always true.

if you add command "setenv bootmenu_<last+1>" you will delete <last+1> entry so <last> will be always last

Re: u-boot for the RX-51 (N900)
 

Thank you all for your help,

I created the bootmenu.scr with m4r0v3r's
and now u-boot finds the meego ce kernel (it shows size, name and all) sticks at Starting Kernel for a few seconds and then the device turns off. Any ideas?

Re: u-boot for the RX-51 (N900)
 

Try if working old u-boot build

Re: u-boot for the RX-51 (N900)
 

Yes this works fine both with Meego CE and Maemo.

On the other hand, I got the dreaded wifi is not available with this device again and I don't know why is that. I always was getting that on my other N900. On this one it worked fine. The difference was that this one was stock uboot + kernel and the other was kp+custom uboot. Now that I installed kp here, it popped up again. I hope a reboot with maemo between fixes it.

Re: u-boot for the RX-51 (N900)
 

If old version booting meego kernel and new not, I think problem with atag structure in bootm...

wait, I will try to check it again (or disable) and create new build

Re: u-boot for the RX-51 (N900)
 

am using kp 49v qwazix if that helps and am using the Mer release.

also ill try that new uboot image soon

edit: so far everything works fine

Re: u-boot for the RX-51 (N900)
 

So which version is working?
* u-boot+kp49.bin
* u-boot+kp49.bin.new

Re: u-boot for the RX-51 (N900)
 

I am syncing my N900 documents over the air and it's going to take some time so I can't test right now. The .old works but there is no wifi in meego, don't know if it has to do with uboot or kp. I will definitely report back in a few hours though.

Re: u-boot for the RX-51 (N900)
 

wifi works fine for me in both uboots, they always have. there is no indicator, but you can still connect, my wifi doesnt have any protection, it works on mac addresses and ive heard people have had trouble with wpa on nitdroid can be the same case here

both uboots work fine

Re: u-boot for the RX-51 (N900)
 

Hi pali! Please upload a "u-boot only" version please...

Re: u-boot for the RX-51 (N900)
 

uploaded

u-boot.bin --> version from git branch pali
u-boot.bin.new --> version from git branch pali + patch for atags bootm.c

Re: u-boot for the RX-51 (N900)
 

I can confirm that both u-boot's work (.old + .new) but I still have that "No wifi available on this device".
It does not have something to do with wpa because the device does not even turn the wifi on (and obviously does not even search for networks). I am sure it wasn't there with uboot-pr13 and nokia kernel.

Re: u-boot for the RX-51 (N900)
 

Is wifi problem on Maemo or Meego?

Re: u-boot for the RX-51 (N900)
 

reflash stock kernel and see whats what tbh

Re: u-boot for the RX-51 (N900)
 

Meego problem. I will do that and report back. But I don't think I changed anything else on the phone except installing one or two apps (nothing lowlevel, wordpress, weight graph and one or two similar apps)

Re: u-boot for the RX-51 (N900)
 

I reverted to nokia kernel in maemo and uboot-pr13 and the wifi problem in MeeGo remains. So it is obviously (it was pretty obvious beforehand too that a different maemo kernel should not have any effect on MeeGo, but it was the only change before and after the problem, and the only serious difference with my other device that already had the wifi problem so I had to give it some thought) not kp nor uboot related problem. I will ask again on the MeeGo CE thread. Thank you anyway for all the efforts.

EDIT: Sorry guys for the false alarm. When I was thinking what extra info I should include on the bug report for the wifi issue, it struck me what the only thing that was the same on the two devices while having the problem. The sim card. I removed the sim-card, and voila! Wifi available. (Funny thing is that with an older sim of the same carrier wifi works fine)

Re: u-boot for the RX-51 (N900)
 

News on power consumption problem ?

Re: u-boot for the RX-51 (N900)
 

ive been using it with no problems with power consumption, ive recently had bad error consumption issues but thats due to me leaving my phone clocked at a 1ghz and bq2700 dicking up

Re: u-boot for the RX-51 (N900)
 

it is problem with u-boot itself, not rx51 code. Somebody must find working version and then find commit which brings power consumption problem. can sombody do it? (al least find last working build of u-boot for rx51?)

Re: u-boot for the RX-51 (N900)
 

Hello guys I am learning making a boot.scr file and while trying to open some of them I saw this part
what does root=/dev/mmcblk0p2 mean? it's n900's home folder right? why is it root= ?

Re: u-boot for the RX-51 (N900)
 

See kernel params: http://www.kernel.org/doc/Documentat...parameters.txt

root command specify rootfs file system

Re: u-boot for the RX-51 (N900)
 

Because Maemo reassigns physical mmc0 (SD) to Linux mmc1, and mmc1 (eMMC) to Linux mmc0.

Re: u-boot for the RX-51 (N900)
 

Yes I know what mmc0 and mmc1 is what I am asking is what does this whole line do? root=/dev/mmcblk0p2 not just part of it. I mean is what will it do if I put it on boot.scr and use with uboot

I got a feeling that it would map /dev/mmcblk0p2 as as root partition for the booted OS but I'm not sure that's why I asked.

Re: u-boot for the RX-51 (N900)
 

it will try to boot system from device /dev/mmcblk0p2 (mmc0, partition 2).

Re: u-boot for the RX-51 (N900)
 

It means "Mount /dev/mmcblk0p2 as root filesystem and boot from it"

Re: u-boot for the RX-51 (N900)
 

Or try less RX51 patches.
For example a lastest version without patch for eMMC support has the high consumption problem ?
If not it is the hw registry manipulation (to activate eMMC) which generates the problem

Re: u-boot for the RX-51 (N900)
 

Got it thanks! Just as I thought. What made me confused about that command is it is used for Kubuntu mobile. The whole image is put on sd card which is an external card and should be /dev/mmcblk1p2 so I wondered why is it pointing on /dev/mmcblk0p2 yet it boots perfectly.

Re: u-boot for the RX-51 (N900)
 

Pali I'm not that accurately sure but it was your first u-boot version that worked for HW 2204 that is stable I think. next update I did was already on kp49 with new uboot and power consumption issue arised. Never documented it since I thought it was some devel apps I installed. But after reflashed never tried reinstalling it again until now

Re: u-boot for the RX-51 (N900)
 

Hi Pali! A friend of mine did lookup on the power consumption issue from her n900, tested every commit from git and said that uboot power consumption was ok before this commit.

https://gitorious.org/u-boot-shr/u-b...21b2046d4e000f

Re: u-boot for the RX-51 (N900)
 

Are you sure if it is this commit?
This commit only add some #define to headers file which are never use in this (and before this) commit.

Re: u-boot for the RX-51 (N900)
 

A supposition :

This header adds value definitions (#define) used by other u-boot sources.

If the #define are missing the source code does nothing (or uses default values) but if the #define are present then they are used during Hw config and some of these #define generate misconfigured Hw

Re: u-boot for the RX-51 (N900)
 

I know twl4030 part of u-boot source code. And this new definitions are not used in u-boot. I added it because in next commits I need use twl4030 regulator for enable eMMC...