[U-Boot-Users] 1.1.4 and 2.6 kernel

[U-Boot-Users] 1.1.4 and 2.6 kernel

[alfred hitch]

Hi All,

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 ......"

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 am new to u-boot and would appreciate some help on issue. any pointers ?

Regards,
Alfred
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20060627/4a50fc06/attachment.htm 

[U-Boot-Users] 1.1.4 and 2.6 kernel

[Wolfgang Denk]

In message <29f916510606270143g5d143086oaa336b93f2225495@mail.gmail.com> you 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.

This is a Linux issue, then, and off topic here.

> I am new to u-boot and would appreciate some help on issue. any pointers ?

This  is  not  a  U-Boot  issue.  [But  check  your  boot  arguments,
especially  any  console=  arguments,  and  your root file system for
corresponding device nodes.]

> ------=_Part_22541_24787346.1151397818795
> Content-Type: text/html; charset=ISO-8859-1
> Content-Transfer-Encoding: 7bit
> Content-Disposition: inline
> 
> Hi All,<br>
> <br>

And *never* again post HTML here.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"There are three principal ways to lose money: wine, women, and engi-
neers. While the first two are more pleasant, the third is by far the
more certain."                           - Baron Rothschild, ca. 1800

[U-Boot-Users] 1.1.4 and 2.6 kernel

[Ilya Yanok]

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.

[U-Boot-Users] 1.1.4 and 2.6 kernel

[alfred hitch]

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 at 0x00000000"

Note the change from default ttyS0 to ttyS1.

And linux bootargs I see xconf as :
console=ttyS1,115200 root=/dev/mtdblock4 mem=64M at 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&dat=121642
> _______________________________________________
> U-Boot-Users mailing list
> U-Boot-Users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/u-boot-users
>

[U-Boot-Users] 1.1.4 and 2.6 kernel

[Ilya Yanok]

alfred hitch wrote:
> I had changed my u-boot configs file to use:
> #define CONFIG_BOOTARGS         "console=ttyS1,115200
> root=/dev/mtdblock4 rw, mem=64M at 0x00000000"
> 
> Note the change from default ttyS0 to ttyS1.
> 
> And linux bootargs I see xconf as :
> console=ttyS1,115200 root=/dev/mtdblock4 mem=64M at 0x00000000
If you have precompiled boot arguments in your kernel then it is surely 
no u-boot issue. Have you enabled support for serial console on 8250 
port? Please, do not answer in this list anymore as your issue is surely 
kernel specific.

[U-Boot-Users] 1.1.4 and 2.6 kernel

[Andreas Schweigstill]

Dear Alfred!

alfred hitch schrieb:
> Note the change from default ttyS0 to ttyS1.

Have you enabled PXA serial ports in your Linux configuration?
And also the "Console on PXA serial port" option?

I have just taken a look into 2.6.15 and have found out
that the PXA serial ports are also named ttyS, so it should
be okay.

Regards
Andreas Schweigstill

-- 
Dipl.-Phys. Andreas Schweigstill
Schweigstill IT | Embedded Systems
Schauenburgerstra?e 116, D-24118 Kiel, Germany
Phone: (+49) 431 5606-435, Fax: (+49) 431 5606-436
Mobile: (+49) 171 6921973, Web: http://www.schweigstill.de/

[U-Boot-Users] 1.1.4 and 2.6 kernel

[Andrea Gimignani]

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 at lists.sourceforge.net] On Behalf Of alfred
hitch
Sent: Tuesday, June 27, 2006 12:47 PM
To: Ilya Yanok
Cc: u-boot-users at 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 at 0x00000000"

Note the change from default ttyS0 to ttyS1.

And linux bootargs I see xconf as :
console=ttyS1,115200 root=/dev/mtdblock4 mem=64M at 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&dat=1216
> 42 _______________________________________________
> U-Boot-Users mailing list
> U-Boot-Users at 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&dat=121642
_______________________________________________
U-Boot-Users mailing list
U-Boot-Users at 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)

[U-Boot-Users] 1.1.4 and 2.6 kernel

[Wolfgang Denk]

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 at 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

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"He was so narrow minded he could see through  a  keyhole  with  both
eyes ..."

[U-Boot-Users] 1.1.4 and 2.6 kernel

[Michael Schwingen]

alfred hitch wrote:
> Hi All,
>
> 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 ......"
>
> 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 ?
Maybe.

I just ran into similar problems. Since I had trouble getting a kernel 
to boot on my custom IXP425 board, I borrowed a IXDP425 board last 
weekend and tried that.

I have:
 - IXDP425 board with redboot in flash
 - a working kernel that can be booted by redboot via tftp.

Replacing redboot by u-boot (pulled from git last week), the kernel is 
started, but the early output (like "uncompressing kernel") does not 
appear on any of the UART ports.

When the kernel finally has the console set up, the messages appear - 
but if it panics before that point, there is no output at all.

Tracing into the kernel startup using gdb + bdi2000, I found no obvious 
reason as to why this happens, but I did not have enough time to really 
dig into the problem - and since I found the reason for my hang, this 
has now moved down in priority a bit. I can boorow the IXDP425 board 
again if absolutely necessary.

My guess would be that u-boot leaves the hardware in some different 
state than redboot, so that the early UART output in the linux kernel 
fails, but this is only a guess. However, since this happens only with 
u-boot and not with redboot, it does not seem to be a pure linux problem.


As a sidenote, the SDRAM config for the IXDP425 seems wrong to me: the 
board has 256MB SDRAM, but config.h shows only 16MB?

cu
Michael

[U-Boot-Users] 1.1.4 and 2.6 kernel

[Dave Hylands]

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/

[U-Boot-Users] 1.1.4 and 2.6 kernel

[Gary Sanders]

Alfred,
 
There was something about new kernels not working with old boot loaders
due to the way clock speeds are passed to the kernel.   And I believe
the error you described below is the one they identified.  Prior to
2.4.5, they expected MHz.  Try changing the envar clocks_in_mhz to 0 to
get it pass Hz instead.
 
Gary


  _____  

	From: u-boot-users-bounces at lists.sourceforge.net
[mailto:u-boot-users-bounces at lists.sourceforge.net] On Behalf Of alfred
hitch
	Sent: Tuesday, June 27, 2006 1:44 AM
	To: u-boot-users at lists.sourceforge.net
	Subject: [U-Boot-Users] 1.1.4 and 2.6 kernel
	
	
	Hi All,
	
	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 ......"
	
	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 am new to u-boot and would appreciate some help on issue. any
pointers ?
	
	Regards,
	Alfred
	

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20060627/b025c3dc/attachment.htm 

[U-Boot-Users] 1.1.4 and 2.6 kernel

[Wolfgang Denk]

In message <A6B3D2F0FED7564699FFE261012FF2AB02FB3EC6@samson.internal.mediabolic.com> you wrote:
> 
> There was something about new kernels not working with old boot loaders
> due to the way clock speeds are passed to the kernel.   And I believe
> the error you described below is the one they identified.  Prior to
> 2.4.5, they expected MHz.  Try changing the envar clocks_in_mhz to 0 to
> get it pass Hz instead.

This is for PowerPC only; no other architecture uses bd_info.

>   _____ 
> 
> 	From: u-boot-users-bounces at lists.sourceforge.net
> [mailto:u-boot-users-bounces at lists.sourceforge.net] On Behalf Of alfred
> hitch
> 	Sent: Tuesday, June 27, 2006 1:44 AM
> 	To: u-boot-users at lists.sourceforge.net
> 	Subject: [U-Boot-Users] 1.1.4 and 2.6 kernel

Please don't top-post / full quote.

Please read the netiquette - see
http://www.netmeister.org/news/learn2quote.html

> ------_=_NextPart_001_01C69A16.2C7CBF2E
> Content-Type: text/html;
> 	charset="us-ascii"
> Content-Transfer-Encoding: quoted-printable

And *NEVER* post HTML here!


Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"I've seen it. It's rubbish."          - Marvin the Paranoid Android

[U-Boot-Users] 1.1.4 and 2.6 kernel

[alfred hitch]

Hi Michael, Everyone,

Thanks for your replies.
Michael: Looks like we do have something in common. This is a very
serious observation. So, correct me if I a wrong. Did the same kernel
give you traces with redboot but not u-boot. (We are together)

Did same kernel crash later on with u-boot and not redboot ? As in I
am curious to know that did change in boot loader cause some other
issue apart from crash also ?

Hey guys, looks there is more to it than just saying linux issue.

Is someone else out there running u-boot 1.1.4 successfully with 2.6 kernel ??

What could be going wrong ??

Cheers,
Alfred

On 6/27/06, Michael Schwingen <rincewind@discworld.dascon.de> wrote:
> alfred hitch wrote:
> > Hi All,
> >
> > 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 ......"
> >
> > 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 ?
> Maybe.
>
> I just ran into similar problems. Since I had trouble getting a kernel
> to boot on my custom IXP425 board, I borrowed a IXDP425 board last
> weekend and tried that.
>
> I have:
>  - IXDP425 board with redboot in flash
>  - a working kernel that can be booted by redboot via tftp.
>
> Replacing redboot by u-boot (pulled from git last week), the kernel is
> started, but the early output (like "uncompressing kernel") does not
> appear on any of the UART ports.
>
> When the kernel finally has the console set up, the messages appear -
> but if it panics before that point, there is no output at all.
>
> Tracing into the kernel startup using gdb + bdi2000, I found no obvious
> reason as to why this happens, but I did not have enough time to really
> dig into the problem - and since I found the reason for my hang, this
> has now moved down in priority a bit. I can boorow the IXDP425 board
> again if absolutely necessary.
>
> My guess would be that u-boot leaves the hardware in some different
> state than redboot, so that the early UART output in the linux kernel
> fails, but this is only a guess. However, since this happens only with
> u-boot and not with redboot, it does not seem to be a pure linux problem.
>
>
> As a sidenote, the SDRAM config for the IXDP425 seems wrong to me: the
> board has 256MB SDRAM, but config.h shows only 16MB?
>
> cu
> Michael
>
>
> 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&dat=121642
> _______________________________________________
> U-Boot-Users mailing list
> U-Boot-Users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/u-boot-users
>

[U-Boot-Users] 1.1.4 and 2.6 kernel

[Wolfgang Denk]

In message <29f916510606271919t6a3f40c7t4013d4591a09e6be@mail.gmail.com> you wrote:
> 
> Hey guys, looks there is more to it than just saying linux issue.

Maybe. Maybe not.

> Is someone else out there running u-boot 1.1.4 successfully with 2.6 kernel ??

Of course. We run 2.6 on many, many PowerPC, some  ARM,  and  a  few
ColdFire and MIPS systems. No problems.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Voodoo Programming: Things programmers do that  they  know  shouldn't
work  but they try anyway, and which sometimes actually work, such as
recompiling everything.                             - Karl Lehenbauer

[U-Boot-Users] 1.1.4 and 2.6 kernel

[Marc Leeman]

> Hey guys, looks there is more to it than just saying linux issue.
> Is someone else out there running u-boot 1.1.4 successfully with 2.6 kernel ??

Running all 2.4 and 2.6 kernels since the release of 1.1.4 without
problems.

-- 
  greetz, marc
I haven't heard of anything like anything happening before. My planet
doesn't even go to the moon anymore.
	Crichton - Through the Looking Glass
scorpius.homelinux.org 2.6.17 #2 PREEMPT Thu Jun 22 07:18:33 CEST 2006 GNU/Linux
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.denx.de/pipermail/u-boot/attachments/20060628/5dcdfb49/attachment.pgp 

[U-Boot-Users] 1.1.4 and 2.6 kernel

[Michael Schwingen]

alfred hitch wrote:
> Hi Michael, Everyone,
>
> Thanks for your replies.
> Michael: Looks like we do have something in common. This is a very
> serious observation. So, correct me if I a wrong. Did the same kernel
> give you traces with redboot but not u-boot. (We are together)
>   
Correct. I could change between redboot and u-boot and observe this 
behaviour.

> Did same kernel crash later on with u-boot and not redboot ? As in I
> am curious to know that did change in boot loader cause some other
> issue apart from crash also ?
>   
No. Once I corrected the startup issues (which turned out to be a typo 
in the commandline arguments), the kernel started up fine (I did not 
test further than mounting the root fs).

cu
Michael

[U-Boot-Users] 1.1.4 and 2.6 kernel

[Andrea Gimignani]

>> 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.

Oh, so my mistake.
I was speaking about my experience with the AT91RM9200 I used some time ago;
but maybe I misconfigured MTD on the 2.4 kernel.

PS sorry for my previous top-posting.

Bye,
Andrea Gimignani


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)

[U-Boot-Users] 1.1.4 and 2.6 kernel

[alfred hitch]

Hi All,

I am still at logger heads with this issue.

Michael: What was ur typo ?? And just wondering if kernel default
command line wasn't configured for u ?

Someone else also posted today on mailing list on kernel arg's not
being passed ?
Observations looks similar for now.

Cheers,
Alfred

On 6/28/06, Michael Schwingen <rincewind@discworld.dascon.de> wrote:
> alfred hitch wrote:
> > Hi Michael, Everyone,
> >
> > Thanks for your replies.
> > Michael: Looks like we do have something in common. This is a very
> > serious observation. So, correct me if I a wrong. Did the same kernel
> > give you traces with redboot but not u-boot. (We are together)
> >
> Correct. I could change between redboot and u-boot and observe this
> behaviour.
>
> > Did same kernel crash later on with u-boot and not redboot ? As in I
> > am curious to know that did change in boot loader cause some other
> > issue apart from crash also ?
> >
> No. Once I corrected the startup issues (which turned out to be a typo
> in the commandline arguments), the kernel started up fine (I did not
> test further than mounting the root fs).
>
> cu
> Michael

[U-Boot-Users] 1.1.4 and 2.6 kernel

[alfred hitch]

Hi All,

I am sending dumps of my logs and what I did..
Anyone can give any pointers, I will really appreciate it.

Boot up log:
-----------------------

U-Boot 1.1.1.2 (Nov 17 2004 - 12:54:00)
sB_CONFIG: 32MB_2CHIP
----------------------------
U-Boot code: 00F80000 -> 00F90E64  BSS: -> 00F92374
RAM Configuration:
Bank #0: 00000000 16 MB
Flash: 32 MB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Hit any key to stop autoboot:  0
=> setenv bootargs 'console=ttySAC01,115200 root=/dev/mtdblock4 rw,
mem=64M at 0x00000000'
=> bootm 0x50040000
## Booting image at 50040000 ...
   Image Name:   Linux
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    951276 Bytes = 929 kB
   Load Address: 01600000
   Entry Point:  01600000
   Verifying Checksum ... OK
OK

Starting kernel ...

[And an eternal blank screen after this]

I created uImage using this command:

->> u-boot-mkimage -A arm -O linux -T kernel -C none -a 0x01600000 -e
0x01600000 -n "Linux" -d ./zImage uImage

Image Name:   Linux
Created:      Fri Jun 30 12:16:18 2006
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    951276 Bytes = 928.98 kB = 0.91 MB
Load Address: 0x01600000
Entry Point:  0x01600000


Do we need to change any steps in 2.6 (v/s 2.4) for creating uImage ?
Could / do my load address etc need to be changed ?

Cheers,
Alfred

[U-Boot-Users] 1.1.4 and 2.6 kernel

[Stefan Roese]

Hi Alfred,

On Friday 30 June 2006 08:04, alfred hitch wrote:
> I am sending dumps of my logs and what I did..
> Anyone can give any pointers, I will really appreciate it.
>
> Boot up log:
> -----------------------
>
> U-Boot 1.1.1.2 (Nov 17 2004 - 12:54:00)

Pretty old. A major update of the IXP4xx port was done a few weeks ago. Please 
try to port your board support to the current version.

> sB_CONFIG: 32MB_2CHIP
> ----------------------------
> U-Boot code: 00F80000 -> 00F90E64  BSS: -> 00F92374
> RAM Configuration:
> Bank #0: 00000000 16 MB
> Flash: 32 MB
> *** Warning - bad CRC, using default environment
>
> In:    serial
> Out:   serial
> Err:   serial
> Hit any key to stop autoboot:  0
> => setenv bootargs 'console=ttySAC01,115200 root=/dev/mtdblock4 rw,

Try "ttyS0" or "ttyS1" as console parameter.

<snip>

> I created uImage using this command:
>
> ->> u-boot-mkimage -A arm -O linux -T kernel -C none -a 0x01600000 -e
> 0x01600000 -n "Linux" -d ./zImage uImage

Why didn't you just type "make uImage"? This result in a proper uImage to boot 
from U-Boot.

BTW: We are using current U-Boot and current Linux 2.6 kernel on different 
IXP4xx boards without any problems (e.g. ixdpg425, pdnb3).

Best regards,
Stefan

[U-Boot-Users] 1.1.4 and 2.6 kernel

[alfred hitch]

Hi,

I have tried 1.1.4 also.
Tried ttyS1

Well only change from ixdp425 is memory related stuff and ttyS1
instead of default ttyS0 for console redirection.

I am really puzzled on this issue.
Can someone please give me any pointers ??

Cheers,,
Alfred

On 6/30/06, Stefan Roese <sr@denx.de> wrote:
> Hi Alfred,
>
> On Friday 30 June 2006 08:04, alfred hitch wrote:
> > I am sending dumps of my logs and what I did..
> > Anyone can give any pointers, I will really appreciate it.
> >
> > Boot up log:
> > -----------------------
> >
> > U-Boot 1.1.1.2 (Nov 17 2004 - 12:54:00)
>
> Pretty old. A major update of the IXP4xx port was done a few weeks ago. Please
> try to port your board support to the current version.
>
> > sB_CONFIG: 32MB_2CHIP
> > ----------------------------
> > U-Boot code: 00F80000 -> 00F90E64  BSS: -> 00F92374
> > RAM Configuration:
> > Bank #0: 00000000 16 MB
> > Flash: 32 MB
> > *** Warning - bad CRC, using default environment
> >
> > In:    serial
> > Out:   serial
> > Err:   serial
> > Hit any key to stop autoboot:  0
> > => setenv bootargs 'console=ttySAC01,115200 root=/dev/mtdblock4 rw,
>
> Try "ttyS0" or "ttyS1" as console parameter.
>
> <snip>
>
> > I created uImage using this command:
> >
> > ->> u-boot-mkimage -A arm -O linux -T kernel -C none -a 0x01600000 -e
> > 0x01600000 -n "Linux" -d ./zImage uImage
>
> Why didn't you just type "make uImage"? This result in a proper uImage to boot
> from U-Boot.
>
> BTW: We are using current U-Boot and current Linux 2.6 kernel on different
> IXP4xx boards without any problems (e.g. ixdpg425, pdnb3).
>
> Best regards,
> Stefan
>

[U-Boot-Users] 1.1.4 and 2.6 kernel - missing startup messages - solved!

[Michael Schwingen]

Michael Schwingen wrote:
>> Did same kernel crash later on with u-boot and not redboot ? As in I
>> am curious to know that did change in boot loader cause some other
>> issue apart from crash also ?
>>   
>>     
> No. Once I corrected the startup issues (which turned out to be a typo 
> in the commandline arguments), the kernel started up fine (I did not 
> test further than mounting the root fs).
>
> cu
> Michael
>   
Just for the record:
my problems have disappeared now. It turns out the problem was caused by 
the LL_DEBUG code in Linux, which expects the UART to be enabled and 
initialized. Now, when u-boot and kernel disagree about which UART is to 
be used for console output, the kernel messages simply disappear.

This was complicated by the fact that the kernel LL_DEBUG code for 
IXP4xx always uses UART1, while my board only has UART2 connected, and I 
configured the IXDP425 board for a similar setup.

I modified my u-boot to always initialize both UARTS - that way, you can 
at least see the messages on boards that have both UARTS connected. As 
long as noone writes to the unused UART, this should not cause any harm.

The reason why I got no "normal" console output was a typo in the 
"mem=..." commandline parameter, which lead to errors early in memory 
management initialization in the kernel.

cu
Michael