From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from outbound2-dub-R.bigfish.com (outbound-dub.frontbridge.com [213.199.154.16]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.bigfish.com", Issuer "*.bigfish.com" (not verified)) by ozlabs.org (Postfix) with ESMTP id 86FB3DDEE7 for ; Tue, 29 Jan 2008 09:55:10 +1100 (EST) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: Linux boot on a ppc 405 Date: Mon, 28 Jan 2008 14:55:04 -0800 In-Reply-To: <5ee408090801281453l3e6fe3e5x2f8f1b0b130ad163@mail.gmail.com> References: <479CAF56.30306@gmail.com> <5ee408090801281453l3e6fe3e5x2f8f1b0b130ad163@mail.gmail.com> From: "Stephen Neuendorffer" To: "Ricardo Ayres Severo" Message-Id: <20080128225505.22226C20071@mail131-dub.bigfish.com> Cc: linuxppc-embedded@ozlabs.org List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , You have to look at the System.map file, find the __log_buf symbol, and then look at the address manually. Steve > -----Original Message----- > From: linuxppc-embedded-bounces+stephen=3Dneuendorffer.name@ozlabs.org [mailto:linuxppc-embedded- > bounces+stephen=3Dneuendorffer.name@ozlabs.org] On Behalf Of Ricardo Ayres Severo > Sent: Monday, January 28, 2008 2:53 PM > Cc: linuxppc-embedded@ozlabs.org > Subject: Re: Linux boot on a ppc 405 >=20 > Grant, >=20 > my output is the following: >=20 > loaded at: 00400000 004E919C >=20 > board data at: 00000000 0000007C >=20 > relocated to: 00404040 004040BC >=20 > zimage at: 00404E2C 004E620A >=20 > avail ram: 004EA000 8DA05119 >=20 >=20 > Linux/PPC load: console=3DttyUL0,9600 >=20 > Uncompressing Linux...done. >=20 > Now booting the kernel >=20 >=20 >=20 > nothing shows up next. > I tried to look at __log_buf but the debugger doesn't recognize it. > The debugger only knows the code of the part that boots the kernel. > I also tried setting ttyUL0 and ttyS0 for the linux console. > Any ideas of how I can get the real position of __log_buf? >=20 > Thanks, >=20 > On Jan 27, 2008 7:15 PM, Grant Likely wrote: > > On 1/27/08, Ricardo Severo wrote: > > > Hi all, > > > > > > I am working with a Xilinx Virtex II Pro evaluation board, wich has two > > > PowerPC 405 and I'm trying to boot a vanilla linux kernel 2.6.23.14. > > > Until now I've manged to make it uncompress the kernel, but it doesn't boot. > > > My question is how the initial execution (the one who uncompresses the > > > kernel image) transfers the processor to the kernel itself. I've looked > > > in the arch/ppc/boot/simple/relocate.S code and it jumps to the position > > > 0x0 after uncompressing, is it right? The kernel is uncompressed at that > > > position? > > > > Post your output log please. > > > > If your getting a message that the kernel is uncompressing, but you > > don't have any output beyond that then most likely your console is not > > setup correctly. If you've got a debugger, look at memory at the > > __log_buf location to see if there are any boot logs there. > > > > Cheers, > > g. > > > > > > -- > > Grant Likely, B.Sc., P.Eng. > > Secret Lab Technologies Ltd. > > >=20 >=20 >=20 > -- > Ricardo Ayres Severo > _______________________________________________ > Linuxppc-embedded mailing list > Linuxppc-embedded@ozlabs.org > https://ozlabs.org/mailman/listinfo/linuxppc-embedded