=20

-----Original Message-----
From: Anatolij Gustschin [mailto:agust@denx.de]=20
Sent: marted=EC 2 settembre 2008 23.28
To: SETTE AGOSTINO - technolabs
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: MPC8568MDS RAMDISK Problem
=20
Hi Agostino,
=20
SETTE AGOSTINO - technolabs wrote:
=20

quoted

I updated my u-boot
=20
U-Boot 1.3.4-00253-g33aa4ea (Sep  2 2008 - 13:04:22)
=20
CPU:   8568E, Version: 1.1, (0x807d0011)
Core:  E500, Version: 2.2, (0x80210022)
Clock Configuration:
       CPU:1320 MHz, CCB: 528 MHz,
       DDR: 264 MHz (528 MT/s data rate), LBC: 132 MHz
L1:    D-cache 32 kB enabled
       I-cache 32 kB enabled
Board: 8568 MDS
I2C:   ready
DRAM:  Initializing
    SDRAM: 64 MB
    DDR: 512 MB
FLASH: 32 MB
L2:    512 KB enabled
    PCI: 32 bit, 66 MHz, async, host, arbiter
               Scanning PCI bus 00
PCI on bus 00 - 00
=20
    PCIE connected to slot as Root Complex (base address e000a000)
PCIE on bus 01 - 01
In:    serial
Out:   serial
Err:   serial
Net:   eTSEC0, eTSEC1, FSL UEC0, FSL UEC1
=20
But now I have the following problem:
=20
## Checking Image at 02000100 ...
   Legacy image found
   Image Name:   Linux-2.6.25.5
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    1354587 Bytes =3D  1.3 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Booting kernel from Legacy Image at 02000100 ...
   Image Name:   Linux-2.6.25.5
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    1354587 Bytes =3D  1.3 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 02200100 ...
   Image Name:   initrd
   Image Type:   PowerPC Linux RAMDisk Image (gzip compressed)
   Data Size:    3658157 Bytes =3D  3.5 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 021f0100
   Booting using the fdt blob at 0x21f0100
   Uncompressing Kernel Image ... OK
   Loading Device Tree to 007fa000, end 007fffff ... OK
WARNING: could not set linux,stdout-path FDT_ERR_NOTFOUND.
ERROR: /chosen node create failed - must RESET the board to recover.

=20
Does your "arch/powerpc/boot/dts/mpc8568mds.dts" file contain
aliases node with "serial0 =3D &serial0;" in it?

Yes, it does:

        aliases {
                ethernet0 =3D &enet0;
                ethernet1 =3D &enet1;
                ethernet2 =3D &enet2;
                ethernet3 =3D &enet3;
                serial0 =3D &serial0;
                serial1 =3D &serial1;
                pci0 =3D &pci0;
                pci1 =3D &pci1;
        };
                serial0: serial@4500 {
                        cell-index =3D <0>;
                        device_type =3D "serial";
                        compatible =3D "ns16550";
                        reg =3D <4500 100>;
                        clock-frequency =3D <0>;
                        interrupts =3D <2a 2>;
                        interrupt-parent =3D <&mpic>;
                };

                serial1: serial@4600 {
                        cell-index =3D <1>;
                        device_type =3D "serial";
                        compatible =3D "ns16550";
                        reg =3D <4600 100>;
                        clock-frequency =3D <0>;
                        interrupts =3D <2a 2>;
                        interrupt-parent =3D <&mpic>;
                };

How do you compile your mpc8568mds.dtb DTB and which dtc version
are you using to compile it?

./dtc -o results/mpc8568mds.dtb -O dtb =
linux/arch/powerpc/boot/dts/mpc8568mds.dts -S 0x2000 -R 4
Version: DTC 1.0.0-gd6f9b62f

=20

quoted

Do I need to add some environment variables or set some fdt=20

commands before booting the board?
=20
The mpc8568mds.dts from 2.6.25.5 kernel seems to be Ok. Booting
should work if you use this mpc8568mds.dts file. The problem
could also be somewhere in U-Boot environment setup.
=20

quoted

Here are the env variables
=20
=3D> printenv
ramboot=3Drun ramargs;tftp $ramdiskaddr $ramdiskfile;tftp=20

$loadaddr $bootfile;bootm $loadaddr $ramdiskaddr

quoted

nfsboot=3Drun nfsargs;tftp $loadaddr $bootfile;tftp $fdtaddr=20

$fdtfile;bootm $loadaddr - $fdtaddr

quoted

bootdelay=3D10
baudrate=3D115200
loads_echo=3D1
ethaddr=3D00:E0:0C:00:00:FD
eth1addr=3D00:E0:0C:00:01:FD
eth2addr=3D00:E0:0C:00:02:FD
eth3addr=3D00:E0:0C:00:03:FD
rootpath=3D/nfsroot
gatewayip=3D192.168.1.1
netmask=3D255.255.255.0
bootfile=3Dyour.uImage
netdev=3Deth0
consoledev=3DttyS0
ramdiskaddr=3D600000
ramdiskfile=3Dyour.ramdisk.u-boot
fdtaddr=3D400000
fdtfile=3Dyour.fdt.dtb
nfsargs=3Dsetenv bootargs root=3D/dev/nfs rw=20

nfsroot=3D$serverip:$rootpath=20
ip=3D$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netdev:off
 console=3D$consoledev,$bau

quoted

drate $othbootargs
ramargs=3Dsetenv bootargs root=3D/dev/ram rw=20

console=3D$consoledev,$baudrate $othbootargs

quoted

ethact=3DeTSEC0
serverip=3D192.168.0.33
ipaddr=3D192.168.0.126
bootcmdFREE=3Drun ramargs;cp.b fff00000 400000 3500;bootm=20

ff800000 ffa00000 400000

quoted

myaps=3DMPC8568MDS/aps
=20

=

mtdargs=3Dmtdparts=3Dphysmap-flash.0:1M(boot),7M(aps0),7M(aps1),1M(optusr=
)

quoted

pram=3D0x100000
mem=3D0x3f00000
pram_start=3D0x3f00000
loadaddr=3D0x2000000
aps0_fl_start=3D0xfe100000
aps0_fl_size=3D0x00700000
aps1_fl_start=3D0xfe800000
aps1_fl_end=3D0xfeefffff
aps1_fl_size=3D0x00700000
aps_ram_start=3D0x2000000
aps_ram_kernel_start=3D0x2000100
aps_ram_dtb_start=3D0x21f0100
aps_ram_rootfs_start=3D0x2200100
aps=3D0
dl_boot=3Dtftp ${aps_ram_start} "u-boot.bin" && protect off=20

0xfe000000 0xfe07ffff && cp.b ${aps_ram_start} 0xfe000000=20
${filesize} && protect on 0xfe000000 0xf

quoted

e07ffff && saveenv
bootcmd=3Dif itest ${aps} =3D=3D 0; then run dl_ram0; else run =

dl_ram1;fi

quoted

altbootcmd=3Dmw.b ${pram_start} 0 ${pram} && if itest ${aps}=20

=3D=3D 0; then setenv aps 1; else setenv aps 0; fi; saveenv; run =

bootcmd

quoted

dl_ram0=3Dcp.b ${aps0_fl_start} ${aps_ram_start}=20

${aps0_fl_size};if imi ${aps_ram_kernel_start}; then run=20
bargs;bootm ${aps_ram_kernel_start} ${aps_ram_rootfs

quoted

_start} ${aps_ram_dtb_start}; else reset; fi
dl_ram1=3Dcp.b ${aps1_fl_start} ${aps_ram_start}=20

${aps1_fl_size};if imi ${aps_ram_kernel_start}; then run=20
bargs;bootm ${aps_ram_kernel_start} ${aps_ram_rootfs

quoted

_start} ${aps_ram_dtb_start}; else reset; fi
bootlimit=3D5
initrd_high=3Dno
hostname=3DMPC8568MDS
aps0_fl_end=3D0xfe7fffff
dl_aps0=3Dtftp ${aps_ram_start} ${myaps};erase=20

${aps0_fl_start} ${aps0_fl_end};cp.b ${aps_ram_start}=20
${aps0_fl_start} ${filesize};boot

quoted

dl_aps1=3Dtftp ${aps_ram_start} ${myaps};erase=20

${aps1_fl_start} ${aps1_fl_end};cp.b ${aps_ram_start}=20
${aps1_fl_start} ${filesize};boot

quoted

bargs=3Dsetenv bootargs ${mtdargs} console=3DttyS0,$baudrate=20

root=3D/dev/ram ramdisk_size=3D500000 rw=20
ip=3D${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}:e

quoted

th0:off panic=3D1 mem=3D${mem} aps=3D${aps} ${misc} ${slram}
dl_mykernel=3Dtftp 1000000 MPC8568MDS/uImage; erase ff800000=20

ff9fffff; cp.b 1000000 ff800000 ${filesize}

quoted

dl_myrootfs=3Dtftp 2000000 MPC8568MDS/RamDisk.ext2; erase=20

ffa00000 ffefffff; cp.b 2000000 ffa00000 ${filesize}

quoted

dl_mydtb=3Dtftp 400000 MPC8568MDS/mpc8568mds.dtb; erase=20

fff00000 fff7ffff; cp.b 400000 fff00000 ${filesize}

quoted

fdt_file=3DMPC8568MDS/mpc8568mds.dtb
fdt_addr_r=3D0x21f0100
stdin=3Dserial
stdout=3Dserial
stderr=3Dserial
=20
With previous u-boot I was able to load the images=20

separately, with this u-boot I have the error.
=20
What commands do you use to load kernel, ramdisk and dtb files?=20

run dl_aps0

But to load the images separately I do the following

run dl_mykernel
run dl_myrootfs
run dl_mydtb
run ramargs
bootm ff800000 ffa00000 400000

It is not obvious from the environment above.
=20
Best regargs,
Anatolij

I am taking a look at the U-Boot files and I made the following =
modification (at the moment I am using U-Boot received by Freescale =
U-Boot 1.3.0-rc3, quite old) on the file common/cmd.bootm.c
diff Mycmd_bootm.c u-boot-1.3.0-rc3/common/cmd_bootm.c
955c955
< 		of_start  =3D (ulong)kbd - of_len;
---

		of_start  =3D (ulong)kbd - of_len - len;

1017c1017
< 		of_start  =3D (ulong)kbd - of_len - 8192;
---

		of_start  =3D (ulong)kbd - of_len - len - 8192;

I added len to avoid that Ramdisk area is overwritten when loading the =
Device Tree. With this modification I am now able to load kernel, rootfs =
and dtb correctly and all as one image file


Best Regards
Agostino

=20
--=20
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office@denx.de
=20