RE: MPC8568MDS RAMDISK Problem
> -Original Message-
> From: Anatolij Gustschin [mailto:[EMAIL PROTECTED]
> Sent: martedì 2 settembre 2008 23.28
> To: SETTE AGOSTINO - technolabs
> Cc: linuxppc-embedded@ozlabs.org
> Subject: Re: MPC8568MDS RAMDISK Problem
>
> Hi Agostino,
>
> SETTE AGOSTINO - technolabs wrote:
>
> > I updated my u-boot
> >
> > U-Boot 1.3.4-00253-g33aa4ea (Sep 2 2008 - 13:04:22)
> >
> > 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
> >
> > 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
> >
> > But now I have the following problem:
> >
> > ## 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 = 1.3 MB
> >Load Address:
> >Entry Point:
> >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 = 1.3 MB
> >Load Address:
> >Entry Point:
> >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 = 3.5 MB
> >Load Address:
> >Entry Point:
> >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 007f ... OK
> > WARNING: could not set linux,stdout-path FDT_ERR_NOTFOUND.
> > ERROR: /chosen node create failed - must RESET the board to recover.
>
> Does your "arch/powerpc/boot/dts/mpc8568mds.dts" file contain
> aliases node with "serial0 = &serial0;" in it?
Yes, it does:
aliases {
ethernet0 = &enet0;
ethernet1 = &enet1;
ethernet2 = &enet2;
ethernet3 = &enet3;
serial0 = &serial0;
serial1 = &serial1;
pci0 = &pci0;
pci1 = &pci1;
};
serial0: [EMAIL PROTECTED] {
cell-index = <0>;
device_type = "serial";
compatible = "ns16550";
reg = <4500 100>;
clock-frequency = <0>;
interrupts = <2a 2>;
interrupt-parent = <&mpic>;
};
serial1: [EMAIL PROTECTED] {
cell-index = <1>;
device_type = "serial";
compatible = "ns16550";
reg = <4600 100>;
clock-frequency = <0>;
interrupts = <2a 2>;
interrupt-parent = <&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
>
> > Do I need to add some environment variables or set some fdt
> commands before booting the board?
>
> 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.
>
> > Here are the env variables
> >
> > => printenv
> > ramboot=run ramargs;tftp $ramdiskaddr $ramdiskfile;tftp
> $loadaddr $bootfile;bootm $loadaddr $ramdiskaddr
> > nfsboot=run nfsargs;tftp $loadaddr $bootfile;tftp $fdtaddr
>
Re: MPC8568MDS RAMDISK Problem
Hi Agostino,
SETTE AGOSTINO - technolabs wrote:
> I updated my u-boot
>
> U-Boot 1.3.4-00253-g33aa4ea (Sep 2 2008 - 13:04:22)
>
> 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
>
> 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
>
> But now I have the following problem:
>
> ## 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 = 1.3 MB
>Load Address:
>Entry Point:
>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 = 1.3 MB
>Load Address:
>Entry Point:
>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 = 3.5 MB
>Load Address:
>Entry Point:
>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 007f ... OK
> WARNING: could not set linux,stdout-path FDT_ERR_NOTFOUND.
> ERROR: /chosen node create failed - must RESET the board to recover.
Does your "arch/powerpc/boot/dts/mpc8568mds.dts" file contain
aliases node with "serial0 = &serial0;" in it?
How do you compile your mpc8568mds.dtb DTB and which dtc version
are you using to compile it?
> Do I need to add some environment variables or set some fdt commands before
> booting the board?
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.
> Here are the env variables
>
> => printenv
> ramboot=run ramargs;tftp $ramdiskaddr $ramdiskfile;tftp $loadaddr
> $bootfile;bootm $loadaddr $ramdiskaddr
> nfsboot=run nfsargs;tftp $loadaddr $bootfile;tftp $fdtaddr $fdtfile;bootm
> $loadaddr - $fdtaddr
> bootdelay=10
> baudrate=115200
> loads_echo=1
> ethaddr=00:E0:0C:00:00:FD
> eth1addr=00:E0:0C:00:01:FD
> eth2addr=00:E0:0C:00:02:FD
> eth3addr=00:E0:0C:00:03:FD
> rootpath=/nfsroot
> gatewayip=192.168.1.1
> netmask=255.255.255.0
> bootfile=your.uImage
> netdev=eth0
> consoledev=ttyS0
> ramdiskaddr=60
> ramdiskfile=your.ramdisk.u-boot
> fdtaddr=40
> fdtfile=your.fdt.dtb
> nfsargs=setenv bootargs root=/dev/nfs rw nfsroot=$serverip:$rootpath
> ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netdev:off
> console=$consoledev,$bau
> drate $othbootargs
> ramargs=setenv bootargs root=/dev/ram rw console=$consoledev,$baudrate
> $othbootargs
> ethact=eTSEC0
> serverip=192.168.0.33
> ipaddr=192.168.0.126
> bootcmdFREE=run ramargs;cp.b fff0 40 3500;bootm ff80 ffa0
> 40
> myaps=MPC8568MDS/aps
> mtdargs=mtdparts=physmap-flash.0:1M(boot),7M(aps0),7M(aps1),1M(optusr)
> pram=0x10
> mem=0x3f0
> pram_start=0x3f0
> loadaddr=0x200
> aps0_fl_start=0xfe10
> aps0_fl_size=0x0070
> aps1_fl_start=0xfe80
> aps1_fl_end=0xfeef
> aps1_fl_size=0x0070
> aps_ram_start=0x200
> aps_ram_kernel_start=0x2000100
> aps_ram_dtb_start=0x21f0100
> aps_ram_rootfs_start=0x2200100
> aps=0
> dl_boot=tftp ${aps_ram_start} "u-boot.bin" && protect off 0xfe00
> 0xfe07 && cp.b ${aps_ram_start} 0xfe00 ${filesize} && protect on
> 0xfe00 0xf
> e07 && saveenv
> bootcmd=if itest ${aps} == 0; then run dl_ram0; else run dl_ram1;fi
> altbootcmd=mw.b ${pram_start} 0 ${pram} && if itest ${aps} == 0; then setenv
> aps 1; else setenv aps 0; fi; saveenv; run bootcmd
> dl_ram0=cp.b ${aps0_fl_start} ${aps_ram_start} ${aps0_fl_size};if imi
> ${aps_ram_kernel_start}; then run bargs;bootm ${aps_ram_kernel_start}
> ${aps_ram_rootfs
> _start} ${aps_ram_dtb_start}; else reset; fi
> dl_ram1=cp.b ${aps1_fl_start} ${aps_ram_start} ${aps1_fl_size};if imi
> ${aps_ram_kernel_start}; then run bargs;bootm ${aps_ram_kernel_start}
> ${aps_ram_rootfs
> _start} ${aps_ram_dtb_start}; else reset; fi
> bootlimit=5
> initrd_high=no
> hostname=MPC8568MDS
> aps0_fl_end=0xfe7f
> dl_aps0=tftp ${aps_ram_start} ${myaps};erase ${aps0_fl_start}
> ${aps0_fl_end};cp.b ${aps
RE: MPC8568MDS RAMDISK Problem
8568MDS/mpc8568mds.dtb; erase fff0 fff7; cp.b
40 fff0 ${filesize}
fdt_file=MPC8568MDS/mpc8568mds.dtb
fdt_addr_r=0x21f0100
stdin=serial
stdout=serial
stderr=serial
With previous u-boot I was able to load the images separately, with this u-boot
I have the error.
Best Regards
Agostino
> -Original Message-
> From: Anatolij Gustschin [mailto:[EMAIL PROTECTED]
> Sent: martedì 2 settembre 2008 12.11
> To: SETTE AGOSTINO - technolabs
> Cc: linuxppc-embedded@ozlabs.org
> Subject: Re: MPC8568MDS RAMDISK Problem
>
> Hi Agostino,
>
> SETTE AGOSTINO - technolabs wrote:
>
> > First of all thanks for your help. I modified the
> mpc8568mds_defconfig
> >
> >>> cat kernel/linux/arch/powerpc/configs/mpc8568mds_defconfig
> > #
>
>
>
> >
> > But now I face this problem
> >
> > ## Checking Image at 02000100 ...
> >Image Name: Linux-2.6.25.5
> >Image Type: PowerPC Linux Kernel Image (gzip compressed)
> >Data Size:1354578 Bytes = 1.3 MB
> >Load Address:
> >Entry Point:
> >Verifying Checksum ... OK
> > ## Booting image at 02000100 ...
> >Image Name: Linux-2.6.25.5
> >Image Type: PowerPC Linux Kernel Image (gzip compressed)
> >Data Size:1354578 Bytes = 1.3 MB
> >Load Address:
> >Entry Point:
> >Verifying Checksum ... OK
> >Uncompressing Kernel Image ... OK
> > ## Loading RAMDisk Image at 02200100 ...
> >Image Name: initrd
> >Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
> >Data Size:3658110 Bytes = 3.5 MB
> >Load Address:
> >Entry Point:
> >Verifying Checksum ... OK
> >Booting using the fdt at 0x21f0100
> >Loading Ramdisk to 00482000, end 007ff17e ... OK
> >Loading Device Tree to 007fa000, end 007fcfff ... OK
>
> Ramdisk image is partially overwritten while loading the
> Device Tree: Ramdisk ends at 0x007ff17e, Device Tree starts
> at 0x007fa000. You probably need to update U-Boot to recent
> version to solve this issue.
>
> > Using MPC85xx MDS machine description
> > Memory CAM mapping: CAM0=16Mb, CAM1=16Mb, CAM2=16Mb residual: 15Mb
> > Linux version 2.6.25.5 ([EMAIL PROTECTED]) (gcc version
> 4.2.2) #1 Mon Sep 1 10:44:44 CEST 2008
> > Found initrd at 0xc0482000:0xc07ff17e
>
>
>
> > RAMDISK: Compressed image found at block 0
> > invalid compressed format (err=1)
>
> Ramdisk decompression failed, it's expected as ramdisk was
> overwritten by DTB while booting.
>
> Try to update U-Boot to v1.3.4.
>
> Best regards,
> Anatolij
>
> --
> 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: [EMAIL PROTECTED]
>
___
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: MPC8568MDS RAMDISK Problem
Hi Agostino, SETTE AGOSTINO - technolabs wrote: > First of all thanks for your help. I modified the mpc8568mds_defconfig > >>> cat kernel/linux/arch/powerpc/configs/mpc8568mds_defconfig > # > > But now I face this problem > > ## Checking Image at 02000100 ... >Image Name: Linux-2.6.25.5 >Image Type: PowerPC Linux Kernel Image (gzip compressed) >Data Size:1354578 Bytes = 1.3 MB >Load Address: >Entry Point: >Verifying Checksum ... OK > ## Booting image at 02000100 ... >Image Name: Linux-2.6.25.5 >Image Type: PowerPC Linux Kernel Image (gzip compressed) >Data Size:1354578 Bytes = 1.3 MB >Load Address: >Entry Point: >Verifying Checksum ... OK >Uncompressing Kernel Image ... OK > ## Loading RAMDisk Image at 02200100 ... >Image Name: initrd >Image Type: PowerPC Linux RAMDisk Image (gzip compressed) >Data Size:3658110 Bytes = 3.5 MB >Load Address: >Entry Point: >Verifying Checksum ... OK >Booting using the fdt at 0x21f0100 >Loading Ramdisk to 00482000, end 007ff17e ... OK >Loading Device Tree to 007fa000, end 007fcfff ... OK Ramdisk image is partially overwritten while loading the Device Tree: Ramdisk ends at 0x007ff17e, Device Tree starts at 0x007fa000. You probably need to update U-Boot to recent version to solve this issue. > Using MPC85xx MDS machine description > Memory CAM mapping: CAM0=16Mb, CAM1=16Mb, CAM2=16Mb residual: 15Mb > Linux version 2.6.25.5 ([EMAIL PROTECTED]) (gcc version 4.2.2) #1 Mon Sep 1 > 10:44:44 CEST 2008 > Found initrd at 0xc0482000:0xc07ff17e > RAMDISK: Compressed image found at block 0 > invalid compressed format (err=1) Ramdisk decompression failed, it's expected as ramdisk was overwritten by DTB while booting. Try to update U-Boot to v1.3.4. Best regards, Anatolij -- 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: [EMAIL PROTECTED] ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
Re: MPC8568MDS RAMDISK Problem
Hi, > Hi: > ram0: rw=0, want=1345772050, limit=100, this error cause by > Device Drivers->block device-> ramdisk size > make ramdisk size bigger > regards:) > yanlong One can also use the "ramdisk_size" command line parameter (cf. Documentation/kernel-parameters.txt). It is not neccessary to recompile the kernel for that. Cheers Detlev -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: [EMAIL PROTECTED] ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
MPC8568MDS RAMDISK Problem
Hi: ram0: rw=0, want=1345772050, limit=100, this error cause by Device Drivers->block device-> ramdisk size make ramdisk size bigger regards:) yanlong ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
RE: MPC8568MDS RAMDISK Problem
S0 at MMIO 0xe0004500 (irq = 42) is a 16550A console handover: boot [udbg0] -> real [ttyS0] serial8250.0: ttyS1 at MMIO 0xe0004600 (irq = 42) is a 16550A brd: module loaded Gianfar MII Bus: probed eth0: Gianfar Ethernet Controller Version 1.2, 00:e0:0c:00:00:fd eth0: Running with NAPI enabled eth0: 256/256 RX/TX BD ring size eth1: Gianfar Ethernet Controller Version 1.2, 00:e0:0c:00:01:fd eth1: Running with NAPI enabled eth1: 256/256 RX/TX BD ring size physmap platform flash device: 0100 at fe00 physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank NOR chip too large to fit in mapping. Attempting to cope... Support for command set 0002 not present gen_probe: No supported Vendor Command Set found physmap-flash physmap-flash.0: map_probe failed slram: not enough parameters. i2c /dev entries driver rtc-ds1374 0-0068: rtc core: registered rtc-ds1374 as rtc0 TCP cubic registered NET: Registered protocol family 1 NET: Registered protocol family 17 RPC: Registered udp transport module. RPC: Registered tcp transport module. rtc-ds1374 0-0068: setting system clock to 1970-07-21 19:03:21 UTC (17435001) IP-Config: Gateway not on directly connected network. RAMDISK: Compressed image found at block 0 invalid compressed format (err=1) VFS: Mounted root (ext2 filesystem). Freeing unused kernel memory: 144k init attempt to access beyond end of device ram0: rw=0, want=954898082, limit=100 Buffer I/O error on device ram0, logical block 2624932688 attempt to access beyond end of device ram0: rw=0, want=1345772050, limit=100 Buffer I/O error on device ram0, logical block 672886024 attempt to access beyond end of device ram0: rw=0, want=3628727914, limit=100 Buffer I/O error on device ram0, logical block 1814363956 attempt to access beyond end of device ram0: rw=0, want=3401505000, limit=100 Buffer I/O error on device ram0, logical block 1700752499 attempt to access beyond end of device ram0: rw=0, want=954898082, limit=100 Buffer I/O error on device ram0, logical block 2624932688 attempt to access beyond end of device ram0: rw=0, want=1345772050, limit=100 Buffer I/O error on device ram0, logical block 672886024 attempt to access beyond end of device ram0: rw=0, want=3628727914, limit=100 Buffer I/O error on device ram0, logical block 1814363956 attempt to access beyond end of device ram0: rw=0, want=3401505000, limit=100 Buffer I/O error on device ram0, logical block 1700752499 attempt to access beyond end of device ram0: rw=0, want=954898082, limit=100 Buffer I/O error on device ram0, logical block 2624932688 attempt to access beyond end of device ram0: rw=0, want=1345772050, limit=100 Buffer I/O error on device ram0, logical block 672886024 attempt to access beyond end of device ram0: rw=0, want=3628727914, limit=100 attempt to access beyond end of device ram0: rw=0, want=3401505000, limit=100 attempt to access beyond end of device ram0: rw=0, want=954898082, limit=100 attempt to access beyond end of device ram0: rw=0, want=1345772050, limit=100 attempt to access beyond end of device ram0: rw=0, want=3628727914, limit=100 attempt to access beyond end of device ram0: rw=0, want=3401505000, limit=100 attempt to access beyond end of device ram0: rw=0, want=954898082, limit=100 attempt to access beyond end of device ram0: rw=0, want=1345772050, limit=100 attempt to access beyond end of device ram0: rw=0, want=3628727914, limit=100 attempt to access beyond end of device ram0: rw=0, want=3401505000, limit=100 attempt to access beyond end of device ram0: rw=0, want=954898082, limit=100 attempt to access beyond end of device ram0: rw=0, want=1345772050, limit=100 attempt to access beyond end of device ram0: rw=0, want=3628727914, limit=100 attempt to access beyond end of device ram0: rw=0, want=3401505000, limit=100 attempt to access beyond end of device ram0: rw=0, want=954898082, limit=100 attempt to access beyond end of device ram0: rw=0, want=1345772050, limit=100 attempt to access beyond end of device ram0: rw=0, want=3628727914, limit=100 attempt to access beyond end of device Do you have any idea? Thanks Bye Agostino > -Original Message- > From: Anatolij Gustschin [mailto:[EMAIL PROTECTED] > Sent: venerdì 29 agosto 2008 23.45 > To: SETTE AGOSTINO - technolabs > Cc: linuxppc-embedded@ozlabs.org > Subject: Re: MPC8568MDS RAMDISK Problem > > SETTE AGOSTINO - technolabs wrote: > > Hi all, > > > > I am trying to port a RAMDISK Filesystem on the MPC8568MDS > board but I > > have the following problem: > > > > > # > > # General setup > > # > > CONFIG_EXPERIMENTAL=y > > CONFIG_BROKEN_ON_SMP=y > > CONFIG_INIT_ENV_ARG_LIMIT=32 > > CONFIG_LOCALVERSION="" > > CONFIG_LOCALVERSION_AUTO=y > > CONFIG_SW
Re: MPC8568MDS RAMDISK Problem
SETTE AGOSTINO - technolabs wrote: > Hi all, > > I am trying to port a RAMDISK Filesystem on the MPC8568MDS board but I > have the following problem: > # > # General setup > # > CONFIG_EXPERIMENTAL=y > CONFIG_BROKEN_ON_SMP=y > CONFIG_INIT_ENV_ARG_LIMIT=32 > CONFIG_LOCALVERSION="" > CONFIG_LOCALVERSION_AUTO=y > CONFIG_SWAP=y > CONFIG_SYSVIPC=y > CONFIG_SYSVIPC_SYSCTL=y > # CONFIG_POSIX_MQUEUE is not set > # CONFIG_BSD_PROCESS_ACCT is not set > # CONFIG_TASKSTATS is not set > # CONFIG_AUDIT is not set > # CONFIG_IKCONFIG is not set > CONFIG_LOG_BUF_SHIFT=14 > # CONFIG_CGROUPS is not set > CONFIG_GROUP_SCHED=y > # CONFIG_FAIR_GROUP_SCHED is not set > # CONFIG_RT_GROUP_SCHED is not set > CONFIG_USER_SCHED=y > # CONFIG_CGROUP_SCHED is not set > CONFIG_SYSFS_DEPRECATED=y > CONFIG_SYSFS_DEPRECATED_V2=y > # CONFIG_RELAY is not set > # CONFIG_NAMESPACES is not set > # CONFIG_BLK_DEV_INITRD is not set -->^ Your kernel doesn't include RAM disk support. Enable "Initial RAM filesystem and RAM disk" and try again. Best regards, Anatolij ___ Linuxppc-embedded mailing list Linuxppc-embedded@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
MPC8568MDS RAMDISK Problem
Hi all, I am trying to port a RAMDISK Filesystem on the MPC8568MDS board but I have the following problem: U-Boot 1.3.0-rc3 (Nov 23 2007 - 18:17:06) CPU: 8568_E, Version: 1.1, (0x807d0011) Core: E500, Version: 2.2, (0x80210022) Clock Configuration: CPU:1320 MHz, CCB: 528 MHz, DDR: 264 MHz, 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 cache 512KB: enabled PCI: 32 bit, 66 MHz, async, host, arbiter Scanning PCI bus 00 PCI on bus 00 - 00 PCIE connected to slot as Root Complex (base address e000a000) PCIE on bus 01 - 01 In:serial Out: serial Err: serial Net: UEC: PHY is Marvell 88E11x1 (1410cc2) UEC: PHY is Marvell 88E11x1 (1410cc2) eTSEC0, eTSEC1, FSL UEC0, FSL UEC1 Hit any key to stop autoboot: 0 ## Checking Image at 02000100 ... Image Name: Linux-2.6.25.5 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size:1325906 Bytes = 1.3 MB Load Address: Entry Point: Verifying Checksum ... OK ## Booting image at 02000100 ... Image Name: Linux-2.6.25.5 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size:1325906 Bytes = 1.3 MB Load Address: Entry Point: Verifying Checksum ... OK Uncompressing Kernel Image ... OK ## Loading RAMDisk Image at 02200100 ... Image Name: initrd Image Type: PowerPC Linux RAMDisk Image (gzip compressed) Data Size:3658144 Bytes = 3.5 MB Load Address: Entry Point: Verifying Checksum ... OK Booting using the fdt at 0x21f0100 Loading Ramdisk to 00482000, end 007ff1a0 ... OK Loading Device Tree to 007fa000, end 007fcfff ... OK Using MPC85xx MDS machine description Memory CAM mapping: CAM0=16Mb, CAM1=16Mb, CAM2=16Mb residual: 15Mb Linux version 2.6.25.5 ([EMAIL PROTECTED]) (gcc version 4.2.2) #1 Fri Aug 29 16:44:02 CEST 2008 Found legacy serial port 0 for /[EMAIL PROTECTED]/[EMAIL PROTECTED] mem=e0004500, taddr=e0004500, irq=0, clk=52800, speed=0 Found legacy serial port 1 for /[EMAIL PROTECTED]/[EMAIL PROTECTED] mem=e0004600, taddr=e0004600, irq=0, clk=52800, speed=0 console [udbg0] enabled Entering add_active_range(0, 0, 12288) 0 entries of 256 used setup_arch: bootmem mpc85xx_mds_setup_arch() Found FSL PCI host bridge at 0xe0008000. Firmware bus number: 0->0 PCI host bridge /[EMAIL PROTECTED]/[EMAIL PROTECTED] (primary) ranges: Found FSL PCI host bridge at 0xe000a000. Firmware bus number: 0->0 PCI host bridge /[EMAIL PROTECTED]/[EMAIL PROTECTED] ranges: arch: exit Top of RAM: 0x300, Total RAM: 0x300 Memory hole size: 0MB Zone PFN ranges: DMA 0 ->12288 Normal 12288 ->12288 Movable zone start PFN for each node early_node_map[1] active PFN ranges 0:0 ->12288 On node 0 totalpages: 12288 DMA zone: 96 pages used for memmap DMA zone: 0 pages reserved DMA zone: 12192 pages, LIFO batch:1 Normal zone: 0 pages used for memmap Movable zone: 0 pages used for memmap Built 1 zonelists in Zone order, mobility grouping on. Total pages: 12192 Kernel command line: mtdparts=physmap-flash.0:1M(boot),7M(aps0),7M(aps1),1M(optusr) console=ttyS0,115200 root=/dev/ram ramdisk_size=50 rw ip=192.168.0.1 26:192.168.0.33:192.168.1.1:255.255.255.0:MPC8568MDS:eth0:off panic=1 mem=0x3f0 aps=0 mpic: Setting up MPIC " OpenPIC " version 1.2 at e004, max 1 CPUs mpic: ISU size: 80, shift: 7, mask: 7f mpic: Initializing for 80 sources PID hash table entries: 256 (order: 8, 1024 bytes) time_init: decrementer frequency = 66.00 MHz time_init: processor frequency = 1320.00 MHz clocksource: timebase mult[3c9b26d] shift[22] registered clockevent: decrementer mult[10e5] shift[16] cpu[0] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes) Inode-cache hash table entries: 4096 (order: 2, 16384 bytes) Memory: 42240k/49152k available (2632k kernel code, 6892k reserved, 104k data, 96k bss, 128k init) SLUB: Genslabs=12, HWalign=32, Order=0-1, MinObjects=4, CPUs=1, Nodes=1 Calibrating delay loop... 131.58 BogoMIPS (lpj=263168) Mount-cache hash table entries: 512 net_namespace: 152 bytes NET: Registered protocol family 16 PCI: Probing PCI hardware Memory resource not set for host bridge 0 PCI: 0001:01:00.0: class b20 doesn't match header type 01. Ignoring class. Memory resource not set for host bridge 1 PCI: Closing bogus Apple Firmware region 1 on bus 0x02 PCI: Closing bogus Apple Firmware region 2 on bus 0x02 PCI: Bridge: 0001:01:00.0 IO window: - MEM window: 0x-0x PREFETCH window: disabled. PCI: Enabling device 0001:01:00.0 (0106 -> 0107) Registering qe_ic with sysfs... SCSI subsystem initialized NET: Registered protocol family 2 Switched to high resolution mode on CPU 0 IP route cache hash table entries: 1024 (order: 0, 4096 bytes) TCP estab
devfs with ramdisk problem
I've had trouble with ramdisk with devfs. I've used the Linux Linux v.2.4.22 for months on a custom PPC board. I frequently changed the kernel and the content of the ramdisk. Sometimes, booting fails with the following error messages. - error messages --- RAMDISK: Compressed image found at block 0 RAMDISK: nblocks = 0 RAMDISK: crd_load, kmalloc(4096, 496) Freeing initrd memory: 5204k freed VFS: Mounted root (ext2 filesystem). Mounted devfs on /dev VFS: Cannot open root device "rd/0" or 00:00 Please append a correct "root=" boot option Kernel panic: VFS: Unable to mount root fs on 00:00 - end of error messages - When it happens, sometimes I could make it work with the same kernel and ramdisk but with different kernel configuration (esp. turning on/off debugging flags of Kernel hacking menu). However, now it keeps failing. Can anybody help me? The RAMDISK size is 30M, the memory of the system is 128M, and the size of zImage.initrd is about 7M. And the kernel command line is: mem=128M load_ramdisk= 1 ramdisk_size=30720 console=ttyS0,57600 root=/dev/rd/0 init=/bin/sh Thanks, Dong-In ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
ramdisk problem
Hi,hello: I use montavista linux,and I use ramdisk root filesystem.But when I run a simple program (helloworld),I made an error as fellow. I can run the helloworld program successfully in nfs . Any idea? Thank you very much. =>tftp 100 ramdisk =>bootm ff85 100 bash# ls binetclinuxrcmyapplication devliblost+found bash# cd myapplication bash# ls helloworld-8xx bash# ./helloworld-8xx /helloworld-8xx: error in loading shared libraries : undefined symbol: __libc_start_main bash# ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
different ramdisk problem? ramdisk is too big?
Hello everyone: I made my own RAMDISK.the initial filesystem size is 35M,and be 13M after imaged and gziped .and I compiled the linux kernel for RAMDISK SIZE 40M.But the following is the problems found in the ramdisk. ANY superman could give me some adivice ,what wrong with my system? thanks alot!!] u-boot>run flash_self ## Booting image at fc00 ... Image Name: Linux-2.4.18_mvl30-rpxlite Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size:738735 Bytes = 721.4 kB Load Address: Entry Point: Verifying Checksum ... OK Uncompressing Kernel Image ... OK ## Loading RAMDisk Image at fe00 ... Image Name: dmt Image Type: PowerPC Linux RAMDisk Image (gzip compressed) Data Size:13716272 Bytes = 13.1 MB Load Address: Entry Point: Verifying Checksum ... OK Loading Ramdisk to 0322a000, end 03f3eb30 ... OK Linux version 2.4.18_mvl30-rpxlite (root at sgj) (gcc version 3.2.1 20020930 (MontaVista)) #1 Sun Mar 14 19:58:18 CST 2004 USB uCode patch installed rpxfb: allocated 75 pages for frame buffer On node 0 totalpages: 16384 zone(0): 16384 pages. zone(1): 0 pages. zone(2): 0 pages. Kernel command line: console=tty0 console=ttyS0,9600 root=/dev/ram rw ip=172.16.115.12:172.16.115.5:172.16.115.254:255.255.255.0::eth0:off panic=1 Decrementer Frequency = 18000/60 Console: colour dummy device 80x25 Calibrating delay loop... 47.82 BogoMIPS Memory: 49008k available (1268k kernel code, 448k data, 76k init, 0k highmem) Dentry-cache hash table entries: 8192 (order: 4, 65536 bytes) Inode-cache hash table entries: 4096 (order: 3, 32768 bytes) Mount-cache hash table entries: 1024 (order: 1, 8192 bytes) Buffer-cache hash table entries: 4096 (order: 2, 16384 bytes) Page-cache hash table entries: 16384 (order: 4, 65536 bytes) POSIX conformance testing by UNIFIX Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Initializing RT netlink socket Starting kswapd Disabling the Out Of Memory Killer JFFS2 version 2.1. (C) 2001, 2002 Red Hat, Inc., designed by Axis Communications AB. Console: switching to colour frame buffer device 80x30 fb0: RPX LCD frame buffer device CPM UART driver version 0.03 ttyS0 on SMC1 at 0x0280, BRG2 pty: 256 Unix98 ptys configured block: 128 slots per queue, batch=32 RAMDISK driver initialized: 16 RAM disks of 40960K size 1024 blocksize eth0: CPM ENET Version 0.2 on SCC2, 00:10:ec:00:37:5c loop: loaded (max 8 devices) usb.c: registered new driver usbdevfs usb.c: registered new driver hub m8xxhci: initializing controller usb.c: new USB bus registered, assigned bus number 1 m8xxhci: part 24, mask 1 m8xxhci: MPC823eB2 hub.c: USB hub found hub.c: 1 port detected m8xxhci: initializing done usb.c: registered new driver usb_mouse usbmouse.c: v1.6:USB HID Boot Protocol mouse driver usb.c: registered new driver keyboard usbkbd.c: :USB HID Boot Protocol keyboard driver mice: PS/2 mouse device common for all mice NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP, IGMP IP: routing cache hash table of 512 buckets, 4Kbytes TCP: Hash tables configured (established 4096 bind 8192) IP-Config: Complete: device=eth0, addr=172.16.115.12, mask=255.255.255.0, gw=172.16.115.254, host=172.16.115.12, domain=, nis-domain=(none), bootserver=172.16.115.5, rootserver=172.16.115.5, rootpath= NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. RAMDISK: Compressed image found at block 0 Freeing initrd memory: 13394k freed EXT2-fs warning: checktime reached, running e2fsck is recommended VFS: Mounted root (ext2 filesystem). Freeing unused kernel memory: 76k init Usage: ping [-LRUbdfnqrvVaA] [-c count] [-i interval] [-w deadline] hub.c: USB new device connect on bus1/1, assigned device number 2 [-p pattern] [-s packetsize] [-t ttl] [-I interface orhub.c: USB hub found address] [-M mtu discovery hihub.c: 4 ports detected nt] [-S sndbuf] [ -T timestamp option ] [ -Q tos ] [hop1 ...] destination Kernel panic: Attempted to kill init! <0>Rebooting in 1 seconds.. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
RAMDISK problem
In message you wrote: > > My problem is that I dont really know what address the core is trying to > write to when the exception occurs. > As I mentioned in the previous message, the write() calls _syscall3() macro > which will perform the write operation, but early in that macro the assembly > 'sc' instruction is called. > As I cannot step through 'sc', I cannot go further on investigating at what > write access the exception occurs. But you can set a breakpoint in the sc exception handler. > How do I even find out what is the start address of the file associated with > the file descritor? Analyze at which offset the file starts in your filesystem image; find out the load address of the filesystem image in RAM; add the offset. Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de "Love is an ideal thing, marriage a real thing; a confusion of the real with the ideal never goes unpunished." - Goethe ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
RAMDISK problem
Hi Gerald > Dumb questions: > * What memory address is it writing to on the 37th write when > it crashes? My problem is that I dont really know what address the core is trying to write to when the exception occurs. As I mentioned in the previous message, the write() calls _syscall3() macro which will perform the write operation, but early in that macro the assembly 'sc' instruction is called. As I cannot step through 'sc', I cannot go further on investigating at what write access the exception occurs. My question is then: How do I even find out what is the start address of the file associated with the file descritor? > * Can you read and write that memory from the command line? > * If you zero the memory before doing the load, what is in > that memory area > a) Before it crashes (set a breakpoint after say 30 writes) > b) After it crashes? > * Is the memory area close to a power-of-two address -- could you > have a memory map problem where you think you have x Kbytes but > the hardware/MMU is only properly decoding x/2 Kbytes or > x/4 Kbytes? > > Given the repeatability, this sounds like a hardware problem > or a software configuration problem (loading over top of > important information like the stack or the currently > executing program or off the end of real memory, off the end > of the memory that is validly mapped via the BATs, etc.). > > gvb Best regards Joao Vicente > > > > -Original Message- > > From: Joao Vicente [mailto:joao.vicente at spectel.com] > > Sent: Wednesday, November 19, 2003 2:13 PM > > To: Wolfgang Denk > > Cc: linuxppc-embedded at lists.linuxppc.org > > Subject: RE: RAMDISK problem > > > > > > > > Hi > > > > I have gone through the SDRAM initialisation, and the init > > sequence, on u-boot, and I dont seem to find any discrepancies. > > I am using a Micron MTLSDT464HG-10EC3 DIMM, and I have it > > initialised as follows. > > > > #define CFG_BR3_PRELIM ((CFG_SDRAM_BASE & BRx_BA_MSK) |\ > > BRx_PS_64 |\ > > BRx_MS_SDRAM_P |\ > > BRx_V) > > > > #define CFG_OR3_PRELIM ((~(CFG_GLOBAL_SDRAM_LIMIT-1) & > > ORxS_SDAM_MSK) |\ > > ORxS_PMSEL |\ > > ORxS_BPD_4 |\ > > ORxS_ROWST_PBI0_A9 |\ > > ORxS_NUMR_12) > > > > #define CFG_PSDMR_PRELIM (PSDMR_BSMA_A14_A16 |\ > > PSDMR_SDA10_PBI0_A9 |\ > > PSDMR_RFRC_3_CLK |\ > > PSDMR_PRETOACT_1W |\ > > PSDMR_ACTTORW_1W |\ > > PSDMR_LDOTOPRE_1C |\ > > PSDMR_WRC_2C |\ > > PSDMR_CL_2) > > > > On the SDRAM init sequence > > > > *sdmr_ptr = sdmr | PSDMR_OP_PREA; > > *base = c; > > > > *sdmr_ptr = sdmr | PSDMR_OP_CBRR; > > for (i = 0; i < 8; i++) > > *base = c; > > > > *sdmr_ptr = sdmr | PSDMR_OP_MRW; > > *(base + CFG_MRS_OFFS) = c; /* setting MR on > > address lines */ > > > > *sdmr_ptr = sdmr | PSDMR_OP_NORM | PSDMR_RFEN; > > *base = c > > > > I am setting the Mode Register Set Command to > > #define CFG_MRS_OFFS0x0110 > > > > which sets: > > Programmable burst mode > > Burst Length = 4 > > Burst Type = Sequential (also tried interleaved) > > CAS latency = 2 > > > > I have also confirmed that the uP is (Write) bursting from > > the first time write() is called (and even before that) by > > measuring the pulse width on WEx, verifying that it's pulse > > is 4x the width of a normal write sequence. > > > > I have also debugged further, and I got much closer to the > > exception point. > > > > crd_load() (from ./init/do_mounts.c) > > |_ gunzip() > >|_ inflate() > > |_ inflate_block() > > |_ inflate_dynamic() > > |_ inflate_codes() > >|_ flush_output() > > |_ flush_window() > > |_write(crd_outfd, window, outcnt) > > > > The last function call before the exception seems to be > > writing a decompressed 32k'outcount' chunk of data pointed by > > 'window' onto a targey file specified by the crd_outfd file > > descriptor. > > > > Notice the system ALLWAYS crashes after the 37th time the > > write() function is called.
RAMDISK problem
> -Original Message- > From: Wolfgang Denk [mailto:wd at denx.de] > Sent: Thursday, November 20, 2003 11:27 AM > To: Joao Vicente > Cc: linuxppc-embedded at lists.linuxppc.org > Subject: Re: RAMDISK problem > > > > In message > .com> you wrote: > > > > My problem is that I dont really know what address the core > is trying to write to when the exception occurs. > > As I mentioned in the previous message, the write() calls > _syscall3() macro which will perform the write operation, but > early in that macro the assembly 'sc' instruction is called. > > As I cannot step through 'sc', I cannot go further on > investigating at what write access the exception occurs. > > But you can set a breakpoint in the sc exception handler. > > > How do I even find out what is the start address of the > file associated with the file descritor? > > Analyze at which offset the file starts in your filesystem image; > find out the load address of the filesystem image in RAM; add the > offset. > > Best regards, > > Wolfgang Denk Hi Joao, I assume you get a crash dump including the registers when it crashes. If not, you need a better debugger (BDI2000). If so, look at SRR0, SRR1, etc. Please read the PowerPC 603e User's Manual (assuming that is applicable: I forgot which processor you are using). For the 82xx (PPC603e core): SRR0 = effective address for resuming program execution SRR1 = MSR with some error identification bits When you find the failure location, disassemble the memory leading up to the failure. Figure out which registers are being used for a memory access when the crash occurred, and find what those registers contained in the crash dump. That will tell you why the crash occurred (I'm guessing TEA, bit 13 in SRR1) and which address was at fault (load or store into a memory location, said memory location being one of the GPRs). If your tools don't give you this information, you need to buy better tools. gvb ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
RAMDISK problem
Hi I have gone through the SDRAM initialisation, and the init sequence, on u-boot, and I dont seem to find any discrepancies. I am using a Micron MTLSDT464HG-10EC3 DIMM, and I have it initialised as follows. #define CFG_BR3_PRELIM ((CFG_SDRAM_BASE & BRx_BA_MSK) |\ BRx_PS_64 |\ BRx_MS_SDRAM_P |\ BRx_V) #define CFG_OR3_PRELIM ((~(CFG_GLOBAL_SDRAM_LIMIT-1) & ORxS_SDAM_MSK) |\ ORxS_PMSEL |\ ORxS_BPD_4 |\ ORxS_ROWST_PBI0_A9 |\ ORxS_NUMR_12) #define CFG_PSDMR_PRELIM (PSDMR_BSMA_A14_A16 |\ PSDMR_SDA10_PBI0_A9 |\ PSDMR_RFRC_3_CLK |\ PSDMR_PRETOACT_1W |\ PSDMR_ACTTORW_1W |\ PSDMR_LDOTOPRE_1C |\ PSDMR_WRC_2C |\ PSDMR_CL_2) On the SDRAM init sequence *sdmr_ptr = sdmr | PSDMR_OP_PREA; *base = c; *sdmr_ptr = sdmr | PSDMR_OP_CBRR; for (i = 0; i < 8; i++) *base = c; *sdmr_ptr = sdmr | PSDMR_OP_MRW; *(base + CFG_MRS_OFFS) = c; /* setting MR on address lines */ *sdmr_ptr = sdmr | PSDMR_OP_NORM | PSDMR_RFEN; *base = c I am setting the Mode Register Set Command to #define CFG_MRS_OFFS0x0110 which sets: Programmable burst mode Burst Length = 4 Burst Type = Sequential (also tried interleaved) CAS latency = 2 I have also confirmed that the uP is (Write) bursting from the first time write() is called (and even before that) by measuring the pulse width on WEx, verifying that it's pulse is 4x the width of a normal write sequence. I have also debugged further, and I got much closer to the exception point. crd_load() (from ./init/do_mounts.c) |_ gunzip() |_ inflate() |_ inflate_block() |_ inflate_dynamic() |_ inflate_codes() |_ flush_output() |_ flush_window() |_write(crd_outfd, window, outcnt) The last function call before the exception seems to be writing a decompressed 32k'outcount' chunk of data pointed by 'window' onto a targey file specified by the crd_outfd file descriptor. Notice the system ALLWAYS crashes after the 37th time the write() function is called. This also points more onto a software/configuration fault than a burst problem with SDRAM (correct me if I am wrong) Another problem is that write() function will invoke static inline _syscall3(int,write,int,fd,const char *,buf,off_t,count) Early in this call the assembly 'sc' instruction will be executed which prevents me from stepping through the call, and finding out exactly at what point the exception occurs. I would appeciate suggestions onto carrying out debugging from this point, or any other suggestions on how to fix the problem. Thanks in advance Joao Vicente > -Original Message- > From: Wolfgang Denk [mailto:wd at denx.de] > Sent: Wednesday, November 12, 2003 7:46 PM > To: Joao Vicente > Cc: linuxppc-embedded at lists.linuxppc.org > Subject: Re: RAMDISK problem > > > Dear Joao, > > in message > .com> you wrote: > > > > The SDRAM parameters used for initialisation have been > fully verified > > Parameters is one thing, the init sequence is another story. Boith > are required, or you will see strange crashes as soon as the system > starts using burst mode heavily. > > > with this board, as we have used them with another RTOS, without any > > problem. > > That does not mean anything. Really. We have seen boards that used to > run pSOS+ for years without problem, but would crash reliably under > Linux. The problems went away after fixing the RAM initialization. > > Your problem is a FAQ on the PPCboot / U-Boot mailing lists. > > > Aditionaly I ran the u-boot mtest utility on sections of the RAM to > > ensure the configuration was good. > > Again, that doesn't mean anything, as this test performs simple read > / write cycles. It will not cause any accesses in burst mode. > > > I believe that rules out bad SDRAM configuration. > > I disagree. I've seen this too many times before. > > > I thought that could give me an idea if inflate was writing > outside the > > valid > > virtual address range. > > I think you're on the wrong track. But I may be wrong, of course. > > Best regards, > > Wolfgang Denk > > -- > Software Engineering: Embedded and Realtime Systems, Embedded Linux > Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de > "Just Say No." - Nancy Reagan > "No."- Ronald Reagan > ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
RAMDISK problem
Dumb questions: * What memory address is it writing to on the 37th write when it crashes? * Can you read and write that memory from the command line? * If you zero the memory before doing the load, what is in that memory area a) Before it crashes (set a breakpoint after say 30 writes) b) After it crashes? * Is the memory area close to a power-of-two address -- could you have a memory map problem where you think you have x Kbytes but the hardware/MMU is only properly decoding x/2 Kbytes or x/4 Kbytes? Given the repeatability, this sounds like a hardware problem or a software configuration problem (loading over top of important information like the stack or the currently executing program or off the end of real memory, off the end of the memory that is validly mapped via the BATs, etc.). gvb > -Original Message- > From: Joao Vicente [mailto:joao.vicente at spectel.com] > Sent: Wednesday, November 19, 2003 2:13 PM > To: Wolfgang Denk > Cc: linuxppc-embedded at lists.linuxppc.org > Subject: RE: RAMDISK problem > > > > Hi > > I have gone through the SDRAM initialisation, and the init > sequence, on u-boot, and I dont seem to find any discrepancies. > I am using a Micron MTLSDT464HG-10EC3 DIMM, and I have it > initialised as follows. > > #define CFG_BR3_PRELIM ((CFG_SDRAM_BASE & BRx_BA_MSK) |\ >BRx_PS_64 |\ >BRx_MS_SDRAM_P |\ >BRx_V) > > #define CFG_OR3_PRELIM ((~(CFG_GLOBAL_SDRAM_LIMIT-1) & > ORxS_SDAM_MSK) |\ > ORxS_PMSEL |\ > ORxS_BPD_4 |\ > ORxS_ROWST_PBI0_A9 |\ > ORxS_NUMR_12) > > #define CFG_PSDMR_PRELIM (PSDMR_BSMA_A14_A16 |\ > PSDMR_SDA10_PBI0_A9 |\ > PSDMR_RFRC_3_CLK |\ > PSDMR_PRETOACT_1W |\ > PSDMR_ACTTORW_1W |\ > PSDMR_LDOTOPRE_1C |\ > PSDMR_WRC_2C |\ > PSDMR_CL_2) > > On the SDRAM init sequence > > *sdmr_ptr = sdmr | PSDMR_OP_PREA; > *base = c; > > *sdmr_ptr = sdmr | PSDMR_OP_CBRR; > for (i = 0; i < 8; i++) > *base = c; > > *sdmr_ptr = sdmr | PSDMR_OP_MRW; > *(base + CFG_MRS_OFFS) = c; /* setting MR on > address lines */ > > *sdmr_ptr = sdmr | PSDMR_OP_NORM | PSDMR_RFEN; > *base = c > > I am setting the Mode Register Set Command to > #define CFG_MRS_OFFS 0x0110 > > which sets: > Programmable burst mode > Burst Length = 4 > Burst Type = Sequential (also tried interleaved) > CAS latency = 2 > > I have also confirmed that the uP is (Write) bursting from > the first time write() is called (and even before that) by > measuring the pulse width on WEx, verifying that it's pulse > is 4x the width of a normal write sequence. > > I have also debugged further, and I got much closer to the > exception point. > > crd_load()(from ./init/do_mounts.c) > |_ gunzip() >|_ inflate() > |_ inflate_block() > |_ inflate_dynamic() > |_ inflate_codes() >|_ flush_output() > |_ flush_window() > |_write(crd_outfd, window, outcnt) > > The last function call before the exception seems to be > writing a decompressed 32k'outcount' chunk of data pointed by > 'window' onto a targey file specified by the crd_outfd file > descriptor. > > Notice the system ALLWAYS crashes after the 37th time the > write() function is called. > This also points more onto a software/configuration fault > than a burst problem with SDRAM (correct me if I am wrong) > > Another problem is that write() function will invoke > static inline _syscall3(int,write,int,fd,const char *,buf,off_t,count) > > Early in this call the assembly 'sc' instruction will be > executed which prevents me from stepping through the call, > and finding out exactly at what point the exception occurs. > > I would appeciate suggestions onto carrying out debugging > from this point, or any other suggestions on how to fix the problem. > > Thanks in advance > > Joao Vicente > > > -Original Message- > > From: Wolfgang Denk [mailto:wd at denx.de] > > Sent: Wednesday, November 12, 2003 7:46 PM > > To: Joao Vicente > > Cc: linuxppc-embedded at lists.linuxppc.org > > Subject: Re: RAMDISK problem > > > > > > Dear Joao, > > > > in message > > > .com> you wrote: > > > > > > The SDRAM parameters used for initiali
RAMDISK problem
In message you wrote: > > A silly question but... > Why does U-boot report a ramdisk size of about 555kB, He was using the old "simple-ramdisk.PPCBoot" image wich was optimized for size. It is really just 550 kB. > while the original from Denx's ftp server has a size of 1.33MB ? You mean a different image (the SELF based one). Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de "My doctor told me to stop having intimate dinners for four. Unless there are three other people." - Orson Welles ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
RAMDISK problem
Dear Joao, in message you wrote: > > The SDRAM parameters used for initialisation have been fully verified Parameters is one thing, the init sequence is another story. Boith are required, or you will see strange crashes as soon as the system starts using burst mode heavily. > with this board, as we have used them with another RTOS, without any > problem. That does not mean anything. Really. We have seen boards that used to run pSOS+ for years without problem, but would crash reliably under Linux. The problems went away after fixing the RAM initialization. Your problem is a FAQ on the PPCboot / U-Boot mailing lists. > Aditionaly I ran the u-boot mtest utility on sections of the RAM to > ensure the configuration was good. Again, that doesn't mean anything, as this test performs simple read / write cycles. It will not cause any accesses in burst mode. > I believe that rules out bad SDRAM configuration. I disagree. I've seen this too many times before. > I thought that could give me an idea if inflate was writing outside the > valid > virtual address range. I think you're on the wrong track. But I may be wrong, of course. Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de "Just Say No." - Nancy Reagan "No."- Ronald Reagan ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
RAMDISK problem
A silly question but... Why does U-boot report a ramdisk size of about 555kB, while the original from Denx's ftp server has a size of 1.33MB ? Is it possible that the kernel runs out of data while booting ? Or may be you just strip the ramdisk image? If so, what is the expected size once it is uncompressed? Would it be advisable to increase the CONFIG_BLK_DEV_RAM_SIZE? Regards, Jean-Denis Boyer, Eng. M5T Centre d'Excellence en T?l?com Inc. 4283 Garlock Street Sherbrooke (Qu?bec) J1L 2C8 CANADA (819)829-3972 x241 > -Original Message- > From: owner-linuxppc-embedded at lists.linuxppc.org > [mailto:owner-linuxppc-embedded at lists.linuxppc.org]On Behalf Of Joao > Vicente > Sent: 11 novembre, 2003 10:45 > To: linuxppc-embedded at lists.linuxppc.org > Subject: RAMDISK problem > > > > Hi > > I am struggling with a problem where I dont seem to be able > to mount a boot filesystem from a RAMDISK. > I am using the sample RAMDisk root filesystem available from > Denx's ftp://ftp.denx.de/pub/LinuxPPC/usr/src/SELF/images/ppc_82xx/ > [...] > > ## Checking Image at 0300 ... >Image Name: Simple Ramdisk-Image >Image Type: PowerPC Linux RAMDisk Image (gzip compressed) >Data Size:567988 Bytes = 554.7 kB >Load Address: >Entry Point: >Verifying Checksum ... OK > ## Booting image at 0010 ... >Image Name: Linux-2.4.20 >Image Type: PowerPC Linux Kernel Image (gzip compressed) >Data Size:595016 Bytes = 581.1 kB >Load Address: >Entry Point: >Verifying Checksum ... OK >Uncompressing Kernel Image ... OK > [...] ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
RAMDISK problem
Dear Joao, in message you wrote: > > CPU: MPC8260 (HiP3 Rev 01, Mask C.2 6K23A) at 133.333 MHz > Board: Spectel MC3 > DRAM: (60x:?COL - 16 MB, 16 MB -^^^ Are you sure your SDRAM initialization is correct? > RAMDISK: Compressed image found at block 0 > Machine check in kernel mode. > Caused by (from SRR1=41000): Transfer error ack signal > Oops: machine check, sig: 7 > NIP: 113C XER: LR: C0006628 SP: C0FBD4F0 REGS: c0fbd440 TRAP: > 0200 >Not tainted > MSR: 00041000 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 00 > TASK = c0fbc000[59392] '' Last syscall: 3 > last math last altivec > GPR00: C0FBD4F0 C0FBC000 C0FBD540 0120 0005 0005 > GPR08: C0FBD4F8 4E81001B 22004042 950A 003F C011 > GPR16: C015 C0EE4008 C0EE7008 C015 9032 00FBD530 C0006074 > GPR24: C0006610 4E80 0001 C0FBD540 0004 0009 4E81001B > Call backtrace: > 007B C0006628 C0006074 00BB C0006074 C00304D0 C001EA88 > C001EAB4 C000A9D4 C0005EA4 0083 Machine check in kernel mode. Did you bother to decode the cal backtrace? And are you really, really sure that your SDRAM initialization is complete and correct? Remember that there is more to do than to set up the memory controller. Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de Time is a drug. Too much of it kills you. - Terry Pratchett, _Small Gods_ ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
RAMDISK problem
Hi I am struggling with a problem where I dont seem to be able to mount a boot filesystem from a RAMDISK. I am using the sample RAMDisk root filesystem available from Denx's ftp://ftp.denx.de/pub/LinuxPPC/usr/src/SELF/images/ppc_82xx/ On the config file I have the following lines: CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_SIZE=4096 CONFIG_BLK_DEV_INITRD=y CONFIG_CRAMFS=y CONFIG_RAMFS=y CONFIG_PROC_FS=y CONFIG_DEVPTS_FS=y CONFIG_EXT2_FS=y I've browsed through a lot of threads relating to problems mounting the root filsystem from RAM but I failed to see a similar symptom to this, with a response. I would appreciate any suggestion from perhaps somebody that has gone through this problem already. Thanks in advance Joao Vicente U-Boot 0.4.5 (Nov 10 2003 - 18:11:40) MPC8260 Reset Status: External Soft, External Hard MPC8260 Clock Configuration - Bus-to-Core Mult 4x, VCO Div 2, 60x Bus Freq 25-75 , Core Freq 100-300 - dfbrg 1, corecnf 0x0a, busdf 7, cpmdf 1, plldf 0, pllmf 3 - vco_out 26664, scc_clk , brg_clk 1666 - cpu_clk 13332, cpm_clk 13332, bus_clk CPU: MPC8260 (HiP3 Rev 01, Mask C.2 6K23A) at 133.333 MHz Board: Spectel MC3 DRAM: (60x:?COL - 16 MB, 16 MB Top of RAM usable for U-Boot at: 0100 Reserving 170k for U-Boot at: 00fd5000 Reserving 136k for malloc() at: 00fb3000 Reserving 76 Bytes for Board Info at: 00fb2fb4 Reserving 72 Bytes for Global Data at: 00fb2f6c Stack Pointer at: 00fb2f48 New Stack Pointer is: 00fb2f48 Now running in RAM - U-Boot at: 00fd5000 FLASH: 4 MB In:serial Out: serial Err: serial Reset Ethernet PHY miiphy_read(0x4) @ 0x0 = 0x01e1 U-Boot relocated to 00fd5000 Net: FCC1 ETHERNET ### main_loop entered: bootdelay=5 ### main_loop: bootcmd="tftp 0x10 $(bootfile);bootm" Hit any key to stop autoboot: 0 => run ramboot Trying FCC1 ETHERNET TFTP from server 10.121.10.150; our IP address is 10.121.10.23 Filename './spc_mc3/uImage'. Load address: 0x10 Loading: ##T ##T T ## ###T # done Bytes transferred = 595080 (91488 hex) ## Checking Image at 0300 ... Image Name: Simple Ramdisk-Image Image Type: PowerPC Linux RAMDisk Image (gzip compressed) Data Size:567988 Bytes = 554.7 kB Load Address: Entry Point: Verifying Checksum ... OK ## Booting image at 0010 ... Image Name: Linux-2.4.20 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size:595016 Bytes = 581.1 kB Load Address: Entry Point: Verifying Checksum ... OK Uncompressing Kernel Image ... OK ## Current stack ends at 0x00FB2928 => set upper limit to 0x0080 ## cmdline at 0x007FFF00 ... 0x007FFF60 bd address = 0x00FB2FB4 memstart= 0x memsize = 0x0100 flashstart = 0x0300 flashsize = 0x0040 flashoffset = 0x sramstart = 0x sramsize= 0x immr_base = 0xF000 bootflags = 0x0001 vco = 266.666 MHz sccfreq = 66.666 MHz brgfreq = 16.666 MHz intfreq = 133.333 MHz cpmfreq = 133.333 MHz busfreq = 33.333 MHz ethaddr = 00:D0:9B:00:00:F9 IP addr = 10.121.10.23 baudrate= 115200 bps ## Loading RAMDisk Image at 0300 ... Image Name: Simple Ramdisk-Image Image Type: PowerPC Linux RAMDisk Image (gzip compressed) Data Size:567988 Bytes = 554.7 kB Load Address: Entry Point: Verifying Checksum ... OK ## initrd at 0x0340 ... 0x0308AAF3 (len=567988=0x8AAB4) Loading Ramdisk to 00f27000, end 00fb1ab4 ... OK ## Transferring control to Linux (at address ) ... REVISIT - MMU_setup entered Memory BAT mapping: BAT2=16Mb, BAT3=0Mb, residual: 0Mb Linux version 2.4.20 (jvicente at lab00056l.localdomain) (gcc version 2.95.4 20010319 (prerelease/franzo/20011204)) #1 Tue Nov 11 11:29:23 GMT 2003 On node 0 totalpages: 4096 zone(0): 4096 pages. zone(1): 0 pages. zone(2): 0 pages. Kernel command line: root=/dev/ram rw ip=10.121.10.23:10.121.10.150:10.121.10.254:255.255.255.0:mc3_joao::off mem=16M IP-Config: Parameter #0: `10.121.10.23' IP-Config: Parameter #1: `10.121.10.150' IP-Config: Parameter #2: `10.121.10.254' IP-Config: Parameter #3: `255.255.255.0' IP-Config: Parameter #4: `mc3_joao' IP-Config: Parameter #6: `off' Warning: real time clock seems stuck! Calibrating delay loop... 88.67 BogoMIPS Memory: 14096k available (1084k kernel code, 400k data, 52k init, 0k highmem) Dentry cache hash table entries: 2048 (order: 2, 16384 bytes) Inode cache hash table entries: 1024 (order: 1, 8192 bytes) Mount-cache hash table entries: 512 (order: 0, 4096 bytes) Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes) Page-cache hash table entries: 4096 (order: 2, 16384 bytes) POSIX conformance testing by UNIFIX Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Initia
RAMDISK problem
did you add a configuration line command like root=/dev/ram0 -Original Message- From: Joao Vicente [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 11, 2003 10:45 AM Subject: RAMDISK problem I am struggling with a problem where I dont seem to be able to mount a boot filesystem from a RAMDISK. I am using the sample RAMDisk root filesystem available from Denx's ftp://ftp.denx.de/pub/LinuxPPC/usr/src/SELF/images/ppc_82xx/ On the config file I have the following lines: CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_SIZE=4096 CONFIG_BLK_DEV_INITRD=y CONFIG_CRAMFS=y CONFIG_RAMFS=y CONFIG_PROC_FS=y CONFIG_DEVPTS_FS=y CONFIG_EXT2_FS=y I've browsed through a lot of threads relating to problems mounting the root filsystem from RAM but I failed to see a similar symptom to this, with a response. I would appreciate any suggestion from perhaps somebody that has gone through this problem already. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
RAMDISK Problem
hello, I have a problem in booting linux 2.4.1 with RAMDISK on MPC8260ADS using PPCBOOT. After downloading kernel and ramdisk (simple-ramdisk.PPCBoot) image to RAM using TFTP application and giving bootm command, it just hangs. As u people suggested to dump "log_buf" contents, i got dump indicating that it is hanging after reading the command line options in init.c. --- Memory dump starts --- => md 0x127654 0x70 00127654: 3c343e72 343a2030 30656434 3030300a<4>r4: 00ed4000. 00127664: 3c343e54 6f74616c 206d656d 6f727920<4>Total memory 00127674: 3d203136 4d423b20 7573696e 67203634= 16MB; using 64 00127684: 6b422066 6f722068 61736820 7461626ckB for hash tabl 00127694: 65202861 74206330 31353030 3030290ae (at c015). 001276a4: 3c343e4c 696e7578 20766572 73696f6e<4>Linux version 001276b4: 20322e34 2e312028 726f6f74 40736869 2.4.1 (root at shi 001276c4: 76612920 28676363 20766572 73696f6eva) (gcc version 001276d4: 20322e39 352e3320 32303031 30333135 2.95.3 20010315 001276e4: 20287265 6c656173 65292920 23312057 (release)) #1 W 001276f4: 6564204d 61722031 32203135 3a32323aed Mar 12 15:22: 00127704: 31352055 54432032 3030330a 3c343e4f15 UTC 2003.<4>O 00127714: 6e206e6f 64652030 20746f74 616c7061n node 0 totalpa 00127724: 6765733a 20343039 360a3c34 3e7a6f6eges: 4096.<4>zon 00127734: 65283029 3a203430 39362070 61676573e(0): 4096 pages 00127744: 2e0a3c34 3e7a6f6e 65283129 3a203020..<4>zone(1): 0 00127754: 70616765 732e0a3c 343e7a6f pages..<4>zo 00127764: 00127774: 00127784: 00127794: 001277a4: 001277b4: 352e302e5.0. 001277c4: 303a7368 6976613a 6f0a 0:shiva:off. 001277d4: --- Memory dump ends --- Iam stuck at this point. bootargs command passed: root=/dev/ram ip=10.1.40.175:10.1.40.176:10.1.1.1:255.255.0.0:shiva::off Is there any problem with this command? I have selected Ramdisk support during linux configuration settings. Is there any other option i have missed? thanks in advance, with rgds, kamal ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
RAMDISK Problem
hello, As suggested, i downloaded the "simple-ramdisk.PPCBoot" from ftp site and also went thru the dplg.pdf file to know more about PPCBoot. Iam working on MPC8260ADS and trying to boot linux-2.4.1 in a standalone mode without NFS support. I loaded both kernel image which was booting earlier with NFS system and newly downloaded ramdisk at address 10 and 20 respectively. And i also updated the bootargs environment variable as --- setenv bootargs root=/dev/ram ip=10.1.40.176:10.1.40.175:10.1.1.1:255.255.0.0:10.1.40.175::off --- where, target ip = 10.1.40.176 server ip = 10.1.40.175 gateway ip = 10.1.1.1 netmask = 255.255.0.0 host name = 10.1.40.175 I have checked ip addresses for correctness. After all this, i gave bootm 10 20 command. Output: After loading kernel image and ramdisk image, it is hanging!!! --- Messages --- ## Booting Linux kernel at 1010 ... Image Name: Linux-2.4.1 Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 400259 Bytes = 390 kB = 0 MB Load Address: Entry Point: Verifying Checksum ... OK Uncompressing Kernel Image ... OK ## Loading RAMDisk Image at 1020 ... Image Name: Simple Ramdisk Image Image Type: PowerPC Linux RAMDisk Image (gzip compressed) Data Size: 507630 Bytes = 495 kB = 0 MB Load Address: Entry Point: Verifying Checksum ... OK Loading Ramdisk to 00ed4000, end 00f5eab4 ... OK [After this, no messages] --- Messages --- I am stuck at this point and don't know what could be the reason. Can somebody help me? thanks in advance, with rgds, kamal ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
RAMDISK Problem
In message <3E63484A.6340720C at tataelxsi.co.in> you wrote: > > Iam working on MPC8260ADS and trying to boot linux-2.4.1 in a standalone > mode without NFS support. 2.4 1. is very old. Did you make sure that the "clocks_in_mhz" variable is set in your PPCBoot environment? > I loaded both kernel image which was booting earlier with NFS system and I understand the NFS based kernel was working on your system? > newly downloaded ramdisk at address 10 and 20 respectively. And > i also updated the bootargs environment variable as > --- > setenv bootargs root=/dev/ram > ip=10.1.40.176:10.1.40.175:10.1.1.1:255.255.0.0:10.1.40.175::off > --- > > where, > target ip = 10.1.40.176 > server ip = 10.1.40.175 > gateway ip = 10.1.1.1 You should not configure a gateway address when you need none. > netmask = 255.255.0.0 > host name = 10.1.40.175 This is an IP address, but not a host name. [Not that teither of these would cause the boot to fail.] > Verifying Checksum ... OK > Loading Ramdisk to 00ed4000, end 00f5eab4 ... OK > > [After this, no messages] If your NFS based kernel was working correctly, you should at least see the same boot messages until it tires to mount the root filesystem. > I am stuck at this point and don't know what could be the reason. Can > somebody help me? Attach a debugger (BDI2000) and check where it's hanging. As a poor man's solution, try to find out if a post-mortem dump of the log_buf area contains some information: grep the System.map file in your kernel directory for the virtual address of "log_buf" and subtract 0xC000 to get the physical address; when you board hangs press the reset button and use PPCBoot's "md" command to print a memory dump of this area. Best regards, Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de Put your Nose to the Grindstone! -- Amalgamated Plastic Surgeons and Toolmakers, Ltd. ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
ramdisk problem again
An embedded and charset-unspecified text was scrubbed... Name: not available Url: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20020823/a9e0b16d/attachment.txt
ramdisk problem
In message <20020613152000.18777.qmail at webmail22.rediffmail.com> you wrote:
>
> i use kernel provided bootloader to load image,
This is not what I mean. You must have some sort of firmware running
on this board. Obviously it is not PPCBoot, because then things were
very simple.
There are firmware implementations which can load ELF images, but
either load only "conventional" segments (text, data) or those which
have the "LOAD" flag set. The "zImage.initrd" contains non-standard
segments ("image" and "initrd"), which don't have the "LOAD" flag
set. Maybe your firmware does not load all segments...
> i am using binary form of zImage
> i didnt get u denk ,i dont know abt this elf what u have said ,i
> am not sure abt it ,i will check it
Maybe reading the "Linux for PowerPC Embedded Systems HOWTO" gives
some additional information, see
http://penguinppc.org/embedded/howto/PowerPC-Embedded-HOWTO.html
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de
Do not simplify the design of a program if a way can be found to make
it complex and wonderful.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
ramdisk problem
In message <20020613134334.24727.qmail at webmail21.rediffmail.com> you wrote: > > after compiling zImage i give command make zImage.initrd > so that r4,r5 contain initrd offset and size > i am getting initrd offset as 9099b > > initrd_load routine is called ,he is checking at this loaction for > start of ramdisk image ,he is not getting it, so he says couldnt > find valid ramdisk image > > what can be the problem How do you load the image? Linux uses a special segment in the ELF file for the initrd image; maybe your bot loader does not understand this, and drops it? Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de "Have you lived in this village all your life?""No, not yet." ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
ramdisk problem
An embedded and charset-unspecified text was scrubbed... Name: not available Url: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20020613/079ba816/attachment.txt
ramdisk problem
In message <20020613111432.22212.qmail at webmail27.rediffmail.com> you wrote: > > when i am booting its saying ,couldnt find valid ramdisk image ,i > am using pRamdisk from denx site which u have sent me the link As I wrote you have to strip the PPCBoot header if you are not using PPCBoot as boot loader. Did you do this? >he is calling PAGE ALIGN > i dont what it does but i mostly think > it computes the offset after after zImage > as it is given as a parameter I cannot make sense out of this. What exactly did you do? How did you build your zImage.initrd image? Wolfgang Denk -- Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd at denx.de It would seem that evil retreats when forcibly confronted -- Yarnek of Excalbia, "The Savage Curtain", stardate 5906.5 ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
ramdisk problem
An embedded and charset-unspecified text was scrubbed... Name: not available Url: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20020613/602e2b34/attachment.txt
ramdisk problem
An embedded and charset-unspecified text was scrubbed... Name: not available Url: http://ozlabs.org/pipermail/linuxppc-embedded/attachments/20020613/9dc6d4e0/attachment.txt
