Problem with kernel loading in PPC IBM405 based board

Hi all,
I am working on PPC IBM 405 based processor board. I have kernel from
"montavista" 2.4.17-mv121 version. I have tried to put the vmlinux image in
the "SDRAM" after doing the all initialization (in boot level).

We are loading the vmlinux in SDRAM at 0x00020000. I am not able to see any
debug message on the serial port. I am not sure about the kernel jump
location. Is there any way to find out the exact location to load the kernel
and jump to proper location.



Thanks & Regards,

Rakesh


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

On Thu, Nov 06, 2003 at 08:05:59PM +0530, Rakesh jagota wrote:

Hi all,
I am working on PPC IBM 405 based processor board. I have kernel from
"montavista" 2.4.17-mv121 version. I have tried to put the vmlinux image in
the "SDRAM" after doing the all initialization (in boot level).

We are loading the vmlinux in SDRAM at 0x00020000. I am not able to see any
debug message on the serial port. I am not sure about the kernel jump
location. Is there any way to find out the exact location to load the kernel
and jump to proper location.

You can't just boot vmlinux directly -- depending on which boot monitor you're
using (eg. OSOpen, PPC/UBoot) you need to be using a different kernel
image.  If you're using OSOpen, you need zImage.treeboot.  If you're
using PPCBoot/UBoot, you need pImage.

--Chris

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

On Fri, 7 Nov 2003, Rakesh jagota wrote:
        ^^^^^^^^^^
You really should fix your date settings or apply for a role on Star
Trek. :-)

I am using openBios code, but i m not able to load the zImage.treeboot using
tftp or serial port. I am directly loading the zImage.treeboot using JTAG
(RISCWATCH). But I am not able to find out the exact loaction where we should
load the image and then from where should be start running the kernel. I have
seen the stext loaction (0xc0000000). Can you guide me exactly where should I
load this image.

0xc0000000 is the virtual address where the _kernel_ is linked and supposed
to run after the MMU has been turned on.

The image you are trying to load is a preloader with a compressed kernel
image attached to it. The preloader is an ELF file that runs at an entirely
different address. It will uncompress and run the kernel (@ address 0x0).

To answer your question: the zImage is linked to 0x00400000 (check
arch/ppc/boot/simple/Makefile, LD_ARGS). The OpenBIOS can load ELF images,
so just use it. I don't recommend direct downloading with RISCWATCH,
although this may work.

Regards,
Marius

--
Marius Groeger [off-list ref]
Software Engineering

SYSGO Real-Time Solutions AG | Embedded and Real-Time Software
Am Pfaffenstein 14
55270 Klein-Winternheim, Germany

Voice: +49-6136-9948-0 | FAX: +49-6136-9948-10
www.sysgo.de | www.elinos.com | www.osek.de

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Hi all,

I am using openBios code, but i m not able to load the zImage.treeboot using
tftp or serial port. I am directly loading the zImage.treeboot using JTAG
(RISCWATCH). But I am not able to find out the exact loaction where we should
load the image and then from where should be start running the kernel. I have
seen the stext loaction (0xc0000000). Can you guide me exactly where should I
load this image.

Thanks & Regards,

Rakesh

On Wednesday 11 June 2003 08:43 pm, Chris Zimman wrote:

On Thu, Nov 06, 2003 at 08:05:59PM +0530, Rakesh jagota wrote:

quoted

Hi all,
I am working on PPC IBM 405 based processor board. I have kernel from
"montavista" 2.4.17-mv121 version. I have tried to put the vmlinux image
in the "SDRAM" after doing the all initialization (in boot level).

We are loading the vmlinux in SDRAM at 0x00020000. I am not able to see
any debug message on the serial port. I am not sure about the kernel jump
location. Is there any way to find out the exact location to load the
kernel and jump to proper location.

You can't just boot vmlinux directly -- depending on which boot monitor
you're using (eg. OSOpen, PPC/UBoot) you need to be using a different
kernel image.  If you're using OSOpen, you need zImage.treeboot.  If you're
using PPCBoot/UBoot, you need pImage.

--Chris

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/