linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
* VxWorks bootloader & PowerQUICC II, Booting the kernel
@ 2000-09-27 15:11 Ruedi.Hofer
  2000-09-27 17:36 ` Dan Malek
  0 siblings, 1 reply; 3+ messages in thread
From: Ruedi.Hofer @ 2000-09-27 15:11 UTC (permalink / raw)
  To: linuxppc-embedded; +Cc: dan, vanbaren_gerald, kernel

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1582 bytes --]

Hi,

I try to boot the Linux kernel on a SBC8260 evaluation board using
the VxWorks bootloader.

In order to be able to load the whole kernel at address 0x900000,
I had to modify the ELF header of the zImage file. I basically changed
the length and the start address.

Question:

1. Why is the length in the ELF header wrong?

2. Why is the start address set to 0x400000 and not to 0x900000?


After loading the kernel, I try to run it:

Attaching network interface lo0... done.
Loading... 493164
entry = 0x900000
[VxWorks Boot]: g 900000
Starting at 0x900000...

program
Exception current instruction address: 0x00900000
Machine Status Register: 0x00089000
Condition Register: 0x24000082
Task: 0xfd37f8 "tBoot"

r0     =   e02684   sp     =   fd3498   r2     =        0   r3     =        0
r4     =  1000000   r5     =        0   r6     =        0   r7     =        0
r8     = 40000000   r9     =   e60000   r10    =   e5f1dc   r11    =   fd3498
r12    =        0   r13    =        0   r14    =        0   r15    =        0
r16    =        0   r17    =        0   r18    =        0   r19    =        0
r20    =        0   r21    =        0   r22    =        0   r23    =        0
r24    =        0   r25    =        0   r26    =        0   r27    =        0
r28    =   e010b8   r29    =   900000   r30    =        0   r31    =   fd3498
msr    =    89000   lr     =   e02690   ctr    =        0   pc     =   900000

[VxWorks Boot]:


.. but it crashes.

Any ideas? I'm using the kernel from HHL1.2, standard config but initrd disabled!

3. What am I doing wrong?

Thank you

Ruedi


^ permalink raw reply	[flat|nested] 3+ messages in thread
* Re: Re: VxWorks bootloader & PowerQUICC II, Booting the kernel
@ 2000-09-28  7:51 Ruedi.Hofer
  2000-09-28 15:02 ` Dan Malek
  0 siblings, 1 reply; 3+ messages in thread
From: Ruedi.Hofer @ 2000-09-28  7:51 UTC (permalink / raw)
  To: dan, linuxppc-embedded; +Cc: kernel

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1113 bytes --]

Hi Dan

I guess I found the message which points to the tool mentioned in your
answer below:

>I wrote a program that will hack the headers such that the stupid
>VxWorks TFTP loader would load the zImage (like other properly
>written loaders will do without any hacks).  I don't know if this
>will help anyone else.  You can find it on
>       ftp://ftp.embeddededge.com/pub/vxhack.c
>
>
>       -- Dan

Unfortunately, this link doesn't work anymore! Do you mind sending
a copy of this file directly to me?

Thank you, Ruedi






dan@mvista.com on 27.09.2000 19:36:24
An: Ruedi.Hofer@ascom.ch @ MailGate
Kopie: linuxppc-embedded@lists.linuxppc.org @ MailGate, vanbaren_gerald@si.com @ MailGate, kernel@linux01.hasler.ascom.ch @ MailGate
Thema: Re: VxWorks bootloader & PowerQUICC II, Booting the kernel


Ruedi.Hofer@ascom.ch wrote:

> I try to boot the Linux kernel on a SBC8260 evaluation board using
> the VxWorks bootloader.

Somewhere (and you can look through the archives as well as I can :-),
I posted a program that will hack a zImage so the VxWorks boot loader
will properly load and start it.....





^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2000-09-28 15:02 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2000-09-27 15:11 VxWorks bootloader & PowerQUICC II, Booting the kernel Ruedi.Hofer
2000-09-27 17:36 ` Dan Malek
  -- strict thread matches above, loose matches on Subject: below --
2000-09-28  7:51 Ruedi.Hofer
2000-09-28 15:02 ` Dan Malek

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).