* Unable to boot a kernel on a MPC8560
@ 2006-05-16 15:12 CORVELLER Mickael
2006-05-16 18:09 ` Greg Weeks
` (2 more replies)
0 siblings, 3 replies; 5+ messages in thread
From: CORVELLER Mickael @ 2006-05-16 15:12 UTC (permalink / raw)
To: linuxppc-embedded
Hello,
first of all, I am a newbie in embedded linux systems.
I'm trying to boot a board based on a MPC8560 (with a e500 core).
I'm using a RS232 console via a debug module connected to the SCC1 port of
the 8560.
The boot loader is U-Boot.
It appears that the transfert of the kernel from the host to target is OK
(I'm using TFTP).
Problems begin when I try to execute the kernel. The system appears to be
frozen.
I don't know if the board is really frozen or if I have "only" lost the
console.
I suspect that my error is situated in the load/execution addresses.
I've tried different couples of values : 0/0, 100000/100000, 10000/10000,
200000/200000, etc...
I've also tried different file format (uImage, zImage.elf, zImage.s ...)
I've tried two distributions : ELINOS and DENX.
I don't know what's happened because I lose the console .
Here is the result of one of my tests :
-> niot 0
Client IP Address (0 for unknown) = 192.168.001.126 ?
Client address mask (0 for unknown) = 255.255.255.000 ?
Server IP Address (0 for unknown) = 192.168.001.127 ?
File Format S(rec)/I(ntel)/B(in)/E(lf) = B ? e
Boot File Name (NULL for unknown) = pimage ? zimage.elf
Boot File Load address = 80000 ? 0
Boot File Execution address = 80000 ? 100000
Data update in progress...
-> nbo 0
Initialize ETH 0 in progress...
Physical link is up at 100f.
TFTP parameters :
Client IP Address 192.168.001.126
Server IP Address 192.168.001.127
Boot File Format E
Boot File Name zimage.elf
Boot File Load address 0
Boot File Execution address 100000
TFTP load in progress...
Packets : 2065
ELF information :
Loading .text @ 0x00800000 : 18620 bytes
Loading .data @ 0x00805000 : 966656 bytes
Clearing .bss @ 0x008F1000 : 8500 bytes
Bytes received = 1057082, Bytes loaded = 0
Low address = 800000, High address = 7FFFFF
After that, the console is died !
I could use some help in trying to understand what's going on.
Regards,
Mickaël
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Unable to boot a kernel on a MPC8560
2006-05-16 15:12 Unable to boot a kernel on a MPC8560 CORVELLER Mickael
@ 2006-05-16 18:09 ` Greg Weeks
2006-05-16 18:39 ` Walter L. Wimer III
2006-05-16 20:26 ` Wolfgang Denk
2 siblings, 0 replies; 5+ messages in thread
From: Greg Weeks @ 2006-05-16 18:09 UTC (permalink / raw)
To: pito50; +Cc: linuxppc-embedded
CORVELLER Mickael wrote:
> Hello,
>
> first of all, I am a newbie in embedded linux systems.
>
> I'm trying to boot a board based on a MPC8560 (with a e500 core).
>
> I'm using a RS232 console via a debug module connected to the SCC1 port of
> the 8560.
>
> The boot loader is U-Boot.
>
>
What version of u-boot do you have? At some point I had a u-boot with
the value of CCSRBAR set different from what the current kernels use. It
caused a failure like this.
Greg Weeks
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Unable to boot a kernel on a MPC8560
2006-05-16 15:12 Unable to boot a kernel on a MPC8560 CORVELLER Mickael
2006-05-16 18:09 ` Greg Weeks
@ 2006-05-16 18:39 ` Walter L. Wimer III
2006-05-16 20:26 ` Wolfgang Denk
2 siblings, 0 replies; 5+ messages in thread
From: Walter L. Wimer III @ 2006-05-16 18:39 UTC (permalink / raw)
To: pito50; +Cc: linuxppc-embedded
On Tue, 2006-05-16 at 15:12 +0000, CORVELLER Mickael wrote:
> The boot loader is U-Boot.
>
[...]
>
> Here is the result of one of my tests :
> -> niot 0
> Client IP Address (0 for unknown) = 192.168.001.126 ?
> Client address mask (0 for unknown) = 255.255.255.000 ?
> Server IP Address (0 for unknown) = 192.168.001.127 ?
> File Format S(rec)/I(ntel)/B(in)/E(lf) = B ? e
> Boot File Name (NULL for unknown) = pimage ? zimage.elf
> Boot File Load address = 80000 ? 0
> Boot File Execution address = 80000 ? 100000
> Data update in progress...
> -> nbo 0
> Initialize ETH 0 in progress...
> Physical link is up at 100f.
>
> TFTP parameters :
> Client IP Address 192.168.001.126
> Server IP Address 192.168.001.127
> Boot File Format E
> Boot File Name zimage.elf
> Boot File Load address 0
> Boot File Execution address 100000
> TFTP load in progress...
> Packets : 2065
> ELF information :
> Loading .text @ 0x00800000 : 18620 bytes
> Loading .data @ 0x00805000 : 966656 bytes
> Clearing .bss @ 0x008F1000 : 8500 bytes
> Bytes received = 1057082, Bytes loaded = 0
> Low address = 800000, High address = 7FFFFF
>
> After that, the console is died !
Um, this doesn't look like U-Boot. This looks like an old Motorola
bootloader like MOTLoad....
Walt Wimer
TimeSys Corporation
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Unable to boot a kernel on a MPC8560
2006-05-16 15:12 Unable to boot a kernel on a MPC8560 CORVELLER Mickael
2006-05-16 18:09 ` Greg Weeks
2006-05-16 18:39 ` Walter L. Wimer III
@ 2006-05-16 20:26 ` Wolfgang Denk
2006-05-17 11:13 ` CORVELLER Mickael
2 siblings, 1 reply; 5+ messages in thread
From: Wolfgang Denk @ 2006-05-16 20:26 UTC (permalink / raw)
To: pito50; +Cc: linuxppc-embedded
In message <BAY105-F10857BC9DB3B958AC19C8D8EA00@phx•gbl> you wrote:
>
> first of all, I am a newbie in embedded linux systems.
Seems you are also a newbie when it comes to posting to mailing lists
in general. Posting the same question several times to several
mailing lists is not a good idea. Please read
http://www.catb.org/%7eesr/faqs/smart-questions.html
> The boot loader is U-Boot.
...
> Here is the result of one of my tests :
> -> niot 0
...
> -> nbo 0
These are definitely no U-Boot commands.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx•de
He's dead, Jim
-- McCoy, "The Devil in the Dark", stardate 3196.1
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Unable to boot a kernel on a MPC8560
2006-05-16 20:26 ` Wolfgang Denk
@ 2006-05-17 11:13 ` CORVELLER Mickael
0 siblings, 0 replies; 5+ messages in thread
From: CORVELLER Mickael @ 2006-05-17 11:13 UTC (permalink / raw)
To: wd; +Cc: linuxppc-embedded
> >
> > first of all, I am a newbie in embedded linux systems.
>
>Seems you are also a newbie when it comes to posting to mailing lists
>in general. Posting the same question several times to several
>mailing lists is not a good idea. Please read
>http://www.catb.org/%7eesr/faqs/smart-questions.html
Indeed, I'm not used to write in mailing lists.
>
>
> > The boot loader is U-Boot.
>...
> > Here is the result of one of my tests :
> > -> niot 0
>...
> > -> nbo 0
>
>These are definitely no U-Boot commands.
>
OK, now I know that my boot loader is not U-Boot, now the question is :
what is the boot loader used by my board ?
I have supposed (certainly wrongly) that the firmware provides on the card
was based on U-Boot...mea-culpa.
According to you, is it the boot loader the cause of my problem ?
>Best regards,
>
>Wolfgang Denk
>
>--
>Software Engineering: Embedded and Realtime Systems, Embedded Linux
>Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx•de
>He's dead, Jim
> -- McCoy, "The Devil in the Dark", stardate 3196.1
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2006-05-17 11:13 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-05-16 15:12 Unable to boot a kernel on a MPC8560 CORVELLER Mickael
2006-05-16 18:09 ` Greg Weeks
2006-05-16 18:39 ` Walter L. Wimer III
2006-05-16 20:26 ` Wolfgang Denk
2006-05-17 11:13 ` CORVELLER Mickael
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox