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

[Tang Yuantian-B29983]

Hi  Cedric MAUSSIRE,

P2020RDB-PCA Board gets supported since kernel 3.3 in mainline code.
Are you sure the board works on kernel 2.6.35?

Regards,
Yuantian

From: linuxppc-dev-bounces+b29983=freescale.com at lists.ozlabs.org [mailto:linuxppc-dev-bounces+b29983=freescale.com at lists.ozlabs.org] On Behalf Of MAUSSIRE Cedric
Sent: 2012年6月4日 23:06
To: linuxppc-dev at lists.ozlabs.org
Subject: 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 system does not respond any longer 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

I have unsuccessfully tried to rebuild the device tree blob and use the default kernel configuration "mpc85xx_defconfig" that comes with the mainline code.

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 3.0, for example, with the same configuration but it does not work.


Best regards,


Cedric MAUSSIRE
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/linuxppc-dev/attachments/20120605/901b551f/attachment-0001.html>