Re: [U-Boot-Users] 1.1.4 and 2.6 kernel

If I'm not wrong, the 2.4 MTD driver and the 2.6 MTD driver is slightly different. In fact in 2.4 you have /dev/mtd0 and /dev/mtdblock0 representing the whole flash. In 2.6 /dev/mtd0 and /dev/mtdblock0 represent the first partition.
So maybe you can try with root=/dev/mtdblock3.
No hints regarding the console issue.
Bye, ilGimmy
-----Original Message----- From: u-boot-users-bounces@lists.sourceforge.net [mailto:u-boot-users-bounces@lists.sourceforge.net] On Behalf Of alfred hitch Sent: Tuesday, June 27, 2006 12:47 PM To: Ilya Yanok Cc: u-boot-users@lists.sourceforge.net Subject: Re: [U-Boot-Users] 1.1.4 and 2.6 kernel
Hi Ilya,
Thanks for your reply.
Can you please help me understand what params you are referring to ?
I had changed my u-boot configs file to use: #define CONFIG_BOOTARGS "console=ttyS1,115200 root=/dev/mtdblock4 rw, mem=64M@0x00000000"
Note the change from default ttyS0 to ttyS1.
And linux bootargs I see xconf as : console=ttyS1,115200 root=/dev/mtdblock4 mem=64M@0x00000000
So, they look more or less ok ??
With same u-boot I can get 2.4 working. So, what could I be missing here.
Wolfgang: Apologise for html mail, my mistake. But I do see this issue as falling on the line between u-boot and linux. Not sure if linux guys will also push me to u-boot back again. So, please see if you can offer some advice.
Regards, Alfred
On 6/27/06, Ilya Yanok ilya.yanok@gmail.com wrote:
alfred hitch wrote:
I am trying to get 2.6 kernel boot on a plattfor very similar to
ixdp425.
We already have u-boot 1.1.1 and 2.4 kernel working for us. But, while trying to get the 2.6 working.
I get the Booting image at XXXX XXXX Starting Kernel ...
And after that nothing.
At this stage I am expecting the "Uncompressing Linux ......"
Looks like kernel doesn't use serial console, have you provided correct console= boot argument?
What could be going wrong ? Same board, if I put in 2.4 on a 1.1.4 version u-boot, it boots fine.
Is it some tty redirection issue ?? Only change from IXDP425 board is sdram configuration and ttyS1 for console instead of ttyS0. Suspecting later but then 2.4 shouldnt' have also booted up ?
I'm pretty sure that serial device of your board was renamed from ttyS to something more specific in 2.6 kernel. Check this.
Second possible reason is that you don't have boot arguments support in u-boot (your 2.4 kernel may have precompiled boot arguments, check kernel configuration).
Ilya.
Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&da... 42 _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&da... _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
Le informazioni trasmesse sono intese soltanto per la persona o l'ente cui sono indirizzate e possono avere contenuto confidenziale e/o riservato. La visione, la trasmissione, la diffusione o altro uso delle informazioni di cui sopra e proibita a chiunque ad esclusione del legittimo destinatario. Se avete ricevuto queste informazioni per errore, siete pregati di contattare il mittente e cancellare il materiale ricevuto. (D.Lgs. 196/2003)
The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, disclosure or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. (D.Lgs. 196/2003)

In message 2DE80618CB7CD311A08A00105A40E9D1061FEF76@mail.dasistemi.it you wrote:
If I'm not wrong, the 2.4 MTD driver and the 2.6 MTD driver is slightly different.
There are pretty bif differences between the MTD versions actually, but not on this level.
In fact in 2.4 you have /dev/mtd0 and /dev/mtdblock0 representing the whole flash.
No, this is wrong. For example:
bash-2.05b# cat /proc/version Linux version 2.4.25 (wd@pollux) (gcc version 3.3.3 (DENX ELDK 3.1.1 3.3.3-9)) #1 Sat Jun 11 18:48:30 MEST 2005 bash-2.05b# cat /proc/mtd dev: size erasesize name mtd0: 00060000 00020000 "u-boot" mtd1: 00020000 00020000 "env1" mtd2: 00020000 00020000 "env2" mtd3: 00100000 00020000 "kernel1" mtd4: 00100000 00020000 "kernel2" mtd5: 01d60000 00020000 "user"
In 2.6 /dev/mtd0 and /dev/mtdblock0 represent the first partition.
AFAIR this has always been the case; of course the first partition can be configured such as to cover the whole device, but that is a completely different story.
Best regards,
Wolfgang Denk

Hi Alfred,
Sending to the list this time....
I am trying to get 2.6 kernel boot on a plattfor very similar to ixdp425. We already have u-boot 1.1.1 and 2.4 kernel working for us. But, while trying to get the 2.6 working.
I get the Booting image at XXXX XXXX Starting Kernel ...
And after that nothing.
At this stage I am expecting the "Uncompressing Linux ......"
So, I've looked through all of the replies, and I don't think any of them are applicable. The "Uncompressing linux..." is printed by the linux decompressor, which runs long before the command line is even looked at.
For the ARM, the actual printing routines can be found in the uncompress.h file which should be located in linux-blah/include/asm-arm/arch-whatever/uncompress.h
The putstr function in here is what is called by the decompressor to print the Uncompressing linux and the dots.
Keep in mind that you're typically executing in physical memory space and not virtual memory space when this code runs.
The other likely scenario for not seeing the Uncompressing linux is that the decompressor was not linked to the same address that u-boot copied it to (or is executing from depending on your setup).
To check, run arm-linux-nm on your arch/arm/boot/compressed/vmlinux and make sure that the addresses that are printed coincide with the location that you're actually going to be running the decompressor from.
-- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/
participants (3)
-
Andrea Gimignani
-
Dave Hylands
-
Wolfgang Denk