On Tue, Apr 8, 2008 at 6:30 AM, Guillaume Dargaud <[EMAIL PROTECTED]> wrote:
> I'm making progress, thanks in no small part to this list, but I still need
> coaching, if you don't mind. The current boot is currently going as such:
>
>
> loaded at: 0040 005A819C
> board data at: 005A6120 0
I'm making progress, thanks in no small part to this list, but I still need
coaching, if you don't mind. The current boot is currently going as such:
loaded at: 0040 005A819C
board data at: 005A6120 005A619C
relocated to: 00404054 004040D0
zimage at: 00404E40 00515AD1
initrd at:
Are you using uartlite? Try console=ttyUL0.
Thanks, I didn't know that.
But Stephen is right, the first thing you should do is look at
__log_buf. You can find its address in the System.map file.
Unfortunately, the installation of the cable driver failed for some reason.
I'll have to work
On Mon, Apr 7, 2008 at 9:33 AM, Guillaume Dargaud <[EMAIL PROTECTED]> wrote:
>
> Linux/PPC load: console=ttyS0,9600 ip=on root=/dev/sysace/disc0/part2 rw
> Uncompressing Linux...done.
> Now booting the kernel
>
> And then it stops.
> I'm sure I've overlooked something obvious...
Are you using
PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Stephen Neuendorffer
Sent: Monday, April 07, 2008 10:44 AM
To: Guillaume Dargaud; linuxppc-dev@ozlabs.org
Subject: RE: Booting a Xilinx board
Generally, speaking the easiest way to debug such errors is to examine
__log_buf using XMD.
Steve
Generally, speaking the easiest way to debug such errors is to examine
__log_buf using XMD.
Steve
> -Original Message-
> From: [EMAIL PROTECTED]
[mailto:linuxppc-dev-
> [EMAIL PROTECTED] On Behalf Of
Guillaume Dargaud
> Sent: Monday, April 07, 2008 8:34 AM
> To: linuxppc-dev@ozlabs.org
>
