EP8548e - unable to boot linux

[acolyte]

Hi,

I am using an Embedded Planet board  based on the 8548E PowerQuic III processor.

Using the "vmlinux.gz.uboot" and "rootfs.ext2.gz.uboot" from the CDROM "/cdrom/files/", I am unable to boot the kernel on the 8548e.

I'm pretty sure I'm missing something basic, but I'm not too sure what.  Can anybody help?

- Brandon

U-Boot 1.1.4 EKB-22022006 (Apr 28 2006 - 16:02:51)
CPU: 8548_E, Version: 2.0, (0x80390020)
Core: E500, Version: 2.0, (0x80210020)
Clock Configuration:
CPU:1066 MHz, CCB: 533 MHz,
DDR: 266 MHz, LBC: 66 MHz
L1: D-cache 32 kB enabled
I-cache 32 kB enabled
Board: MPC8548AMC.
I2C: ready
DRAM: Initializing
MODULE: HITR28UFA 256MB
DDR: 256 MB
FLASH: 16 MB
L2 cache 512KB: enabled
In: serial
Out: serial
Err: serial
Net: eTSEC0, eTSEC1, eTSEC2, eTSEC3
AMC=>
AMC=>
AMC=>
AMC=> ping 157.165.28.220
Speed: 100, full duplex
Using eTSEC0 device
host 157.165.28.220 is alive
AMC=> tftp 1000000 vmlinux.gz.uboot
Speed: 100, full duplex
Using eTSEC0 device
TFTP from server 157.165.28.220; our IP address is 157.165.29.36
Filename 'vmlinux.gz.uboot'.
Load address: 0x1000000
Loading: #################################################################
#################################################################
##############################################################
done
Bytes transferred = 980940 (ef7cc hex)
AMC=> tftp 2000000 rootfs.ext2.gz.uboot
Speed: 100, full duplex
Using eTSEC0 device
TFTP from server 157.165.28.220; our IP address is 157.165.29.36
Filename 'rootfs.ext2.gz.uboot'.
Load address: 0x2000000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################
done
Bytes transferred = 4908634 (4ae65a hex)
AMC=>
AMC=> bootm 1000000 2000000
## Booting image at 01000000 ...
Image Name: Linux for ep8548
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 980876 Bytes = 957.9 kB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
## Loading RAMDisk Image at 02000000 ...
Image Name: uboot ext2 ramdisk rootfs
Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
Data Size: 4908570 Bytes = 4.7 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Ramdisk to 0fafe000, end 0ffac61a ... OK

[PaoloTreffilett]

Hi all,
   I have found the same problem using the EP8548rev2.
It seems that, once the Linux image is loaded into the RAM, it doesn't start.
My configuration is quite different, I'm using a rImage.gz that contains both the kernel image and the RAM disk image. This compressed image is stored in FLASH at the address 0xFF000000
I have tried to boot the same kernel via NFS and it works fine, and I have tried to use the same rImage.gz on the EP8548rev1 and it also works. I think there is a problem when the kernel must boot once it is placed in the RAM probably  due to a misconfigurations of the rev2 board.
Does anyone have any suggestions?

Thanks, Paolo

Here my u-boot onfiguration:

bootdelay=5
baudrate=115200
loads_echo=1
bootfile="u-boot.amc.rev4"
loadaddr=1000000
ethact=eTSEC0
ethaddr=00:10:ec:00:df:0e
eth1addr=00:10:ec:80:df:0e
eth2addr=00:10:ec:40:df:0e
eth3addr=00:10:ec:c0:df:0e
serverip.orig=10.0.0.58
serverip=172.16.0.1
ipaddr.orig=10.0.0.252
ipaddr=172.16.0.5
bootargs.orig=root=/dev/ram rw console=ttyS0,115200 riohdid=0
bootargs=root=/dev/ram rw console=ttyS0,115200 ip=172.16.0.5:::255.255.255.0::eth0
bootcmd=bootm 0xFF000000
pram=131072k
mem=2097152k
stdin=serial
stdout=serial
stderr=serial


Here my output:

U-Boot 1.1.4 EKB-22022006 (Apr 28 2006 - 16:02:51)

CPU:   8548_E, Version: 2.0, (0x80390020)
Core:  E500, Version: 2.0, (0x80210020)
Clock Configuration:
       CPU: 999 MHz, CCB: 333 MHz,
       DDR: 166 MHz, LBC:  41 MHz
L1:    D-cache 32 kB enabled
       I-cache 32 kB enabled
Board: MPC8548AMC.
I2C:   ready
DRAM:  Initializing
MODULE:
    DDR: 256 MB
FLASH: 16 MB
L2 cache 512KB: enabled
In:    serial
Out:   serial
Err:   serial
Net:   eTSEC0, eTSEC1, eTSEC2, eTSEC3
Hit any key to stop autoboot:  0
## Booting image at ff000000 ...
   Image Name:   Kernel and Ramdisk
   Image Type:   PowerPC Linux Multi-File Image (gzip compressed)
   Data Size:    3402792 Bytes =  3.2 MB
   Load Address: 00000000
   Entry Point:  00000000
   Contents:
   Image 0:  1012171 Bytes = 988.4 kB
   Image 1:  2390608 Bytes =  2.3 MB
   Verifying Checksum ... OK
   Uncompressing Multi-File Image ... OK
   Loading Ramdisk to 0fd65000, end 0ffaca50 ... OK



Message Edited by Paolo Treffiletti on 2007-07-09 02:52 PM

[PaoloTreffilett · Accepted solution]

Just an update:
I tried to used the BSP for the EP8548v1.1 on the EP8548v1.2 and it didn't work.
The "solution" that I have found is to use the BSP for the EP8548v1.2 mezzanine.

Best regards
Paolo