headers
MAUSSIRE Cedric | 1 Jun 2012 14:31

ELDK 4.2 : Cannot boot an kernel version other than 2.6.35 on P2020RDB-PCA

Hello all,

I am currently working on the Freescale P2020RDB-PCA Board, which has been delivred with the linux-2.6.35
kernel. I succeed in re-generating my own uImage in 2.6.35 thanks to ELDK, but when I want to move on to a
newer or older version of linux, the processor is stuck just after the boot whith the nfsboot command, the
logs are :

## Booting kernel from Legacy Image at 01000000 ...
   Image Name:   Linux-2.6.39
   Created:      2012-05-29   8:24:54 UTC
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    3514882 Bytes = 3.4 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 00c00000
   Booting using the fdt blob at 0xc00000
   Uncompressing Kernel Image ... OK
   Loading Device Tree to 00ffa000, end 00fffd4a ... OK

NB : nfsboot=setenv bootargs root=/dev/nfs rw nfsroot=192.168.1.1:$rootpath
ip=192.168.1.2:192.168.1.1:192.168.1.1:255.255.255.0:P2020RDB-PC:eth0:off
console=ttyS0,115200 

My systems seems to be linux-2.6.35 dependent, I do not known how it can be possible, because I can use the
kernel.org source of the 2.6.35 whith no problems but when I use the 2.6.39, for example, with the same
configuration but it does not work. 

Best regards,
(Continue reading)

Permalink | Reply |
headers
Wolfgang Denk | 3 Jun 2012 20:36
Picon
Picon
Favicon

Re: ELDK 4.2 : Cannot boot an kernel version other than 2.6.35 on P2020RDB-PCA

Dear Cedric,

In message
<2A5271086BF5EA4A891F3804135DEA820795A3AE@...>
you wrote:
> 
> I am currently working on the Freescale P2020RDB-PCA Board, which has
> been delivred with the linux-2.6.35 kernel. I succeed in re-generating
> my own uImage in 2.6.35 thanks to ELDK, but when I want to move on to a
> newer or older version of linux, the processor is stuck just after the
> boot whith the nfsboot command, the logs are :

You write "processor is stuck" - this is about impossible.  How
exactly did you determine that the processor was "stuck"?  Dd you use
any specific hardware toold to get such information from the CPU?

Or do you just mean that the _system_ does not respond any longer?
Note that this is a fundamentally different thing - the processe may
well be still executing code, and only the communication link is
broken somewhere (say, the console drvier not working correctly).

> ## Booting kernel from Legacy Image at 01000000 ...
>    Image Name:   Linux-2.6.39

Where exactly is this 2.6.39 kernel code coming from - and why are you
using such ancient code?   Why don;t you just run a recent (v3.4 or
so) mainline kernel?

> My systems seems to be linux-2.6.35 dependent, I do not known how it can
> be possible, because I can use the kernel.org source of the 2.6.35 whith
(Continue reading)

Permalink | Reply |
headers
MAUSSIRE Cedric | 4 Jun 2012 09:24

Re: ELDK 4.2 : Cannot boot an kernel version other than 2.6.35 on P2020RDB-PCA

Dear Wolfgang,

Thanks for the tips, I will contact the Yiu team for more informations.

Best regards,

Cedric MAUSSIRE

-----Original Message-----
From: Wolfgang Denk [mailto:wd@...]
Sent: Sun 6/3/2012 8:36 PM
To: MAUSSIRE Cedric
Cc: eldk@...
Subject: Re: [ELDK] ELDK 4.2 : Cannot boot an kernel version other than 2.6.35 on P2020RDB-PCA

Dear Cedric,

In message
<2A5271086BF5EA4A891F3804135DEA820795A3AE@...>
you wrote:
> 
> I am currently working on the Freescale P2020RDB-PCA Board, which has
> been delivred with the linux-2.6.35 kernel. I succeed in re-generating
> my own uImage in 2.6.35 thanks to ELDK, but when I want to move on to a
> newer or older version of linux, the processor is stuck just after the
> boot whith the nfsboot command, the logs are :

You write "processor is stuck" - this is about impossible.  How
exactly did you determine that the processor was "stuck"?  Dd you use
any specific hardware toold to get such information from the CPU?
(Continue reading)

Permalink | Reply |

Gmane