??: Bad Magic Number when boot linux kernel with ppcboot (PPC860 board)

3 messages, 3 authors, 2005-09-01 · open the first message on its own page

??: Bad Magic Number when boot linux kernel with ppcboot (PPC860 board)

From: FCG WANG Baohua <hidden>
Date: 2005-08-02 07:29:36

Dear Denk:
  The magic number is right when using vmlinux.UBoot instead of vmlinux =
or zImage, Why?
  Another question puzzle me:
  The kernel print the "Transferring control to Linux (at address =
00000000) ... "  then halt ,no any response from serial port.
  I tried ramdiak and nfs, there are the same result.
  So why not print the=20
  "Linux version 2.4.25 (root at FedoraCore2) (gcc version 3.3.3 (DENX =
ELDK 3.1
3.3.3-8)) #94 Tue Jul 5 18:59:08 PDT 2005"=20
 =20
  How to not print the "Transferring control to Linux (at address =
00000000) ... "  ? Is it right ?=20
  Thanks a lot!


-----????-----
???: wd@denx.de [mailto:wd@denx.de]
????: 2005?8?2? 15:13
???: FCG WANG Baohua
??: linuxppc-embedded@ozlabs.org
??: Re: Bad Magic Number when boot linux kernel with ppcboot (PPC860 =
board)=20


In message [off-list ref] =
you wrote:
=20
kernel, after I loaded it print the following messages:
=20
=3D> bootm 0x180000
## Booting image at 00000000 ...
Bad Magic Number
=3D>
Which address did you load the image to?
How to slove it, thanks a lot!
I use:  zImage,=20
vmlinux.UBoot,
 vmlinux=20
 it all print the same messages, How can I do?=20
Please read the documentation. Only uImage =3D vmlinux.UBoot can work.

Best regards,

Wolfgang Denk

--=20
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
"Confound these ancestors.... They've stolen our best ideas!"
- Ben Jonson

AW: Bad Magic Number when boot linux kernel with ppcboot (PPC860 board)

From: David Grab <hidden>
Date: 2005-08-02 08:10:15

Dear Denk:
 The magic number is right when using vmlinux.UBoot instead of vmlinux or
zImage, Why?

u-boot needs an u-boot image. Wolfgang did already say that vmlinux.UBoot is
that image. So use this image and nothing else. Also read the manual
especially this chapter
http://www.denx.de/twiki/bin/view/DULG/BootingEmbeddedLinux
 Another question puzzle me:
 The kernel print the "Transferring control to Linux (at address 00000000)
... "  then halt ,no any response 
from serial port.
Seems for me that the serial configuration did not match. Are you sure you
chosen and cofigured the right UART? If so then debug with BDI2000. 
 I tried ramdiak and nfs, there are the same result.
 So why not print the 
 "Linux version 2.4.25 (root at FedoraCore2) (gcc version 3.3.3 (DENX ELDK
3.1
3.3.3-8)) #94 Tue Jul 5 18:59:08 PDT 2005" 
The console output has nothing to do with ramdisk or nfs. So check your
configuration of the active console. An quick check, if your u-boot did not
pass the console parameters is to set the console parameter in linux. For
that you have to activate command line to yes and set the command line
parameter to 'console=ttySx'. x=0 is UART0 and x=1 is UART1. If this not
help then debug again with BDI.
 How to not print the "Transferring control to Linux (at address 00000000)
... "  ? Is it right ? 
 Thanks a lot!
This print might be ok.

Best regards,

David

Does the console have to be asigned to a serial or video driver ?

From: David H. Lynch Jr <hidden>
Date: 2005-09-01 22:35:58

   
    I am working on a Linux Port to a very minimal Xilinx V4 FPGA card. 
At this point it would be extremely useful for me to assign the console 
to a fairly trivial char device that is little more than a 
bi-directional parallel port.

    Is that possible or do I have to impliment dummy code for all the 
required interfaces for a serial device ?
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help