From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.183]) by ozlabs.org (Postfix) with ESMTP id E3C6DDDEBA for ; Tue, 29 Jan 2008 09:53:21 +1100 (EST) Received: by py-out-1112.google.com with SMTP id z59so2533827pyg.27 for ; Mon, 28 Jan 2008 14:53:19 -0800 (PST) Message-ID: <5ee408090801281453l3e6fe3e5x2f8f1b0b130ad163@mail.gmail.com> Date: Mon, 28 Jan 2008 20:53:19 -0200 From: "Ricardo Ayres Severo" Subject: Re: Linux boot on a ppc 405 Cc: linuxppc-embedded@ozlabs.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 References: <479CAF56.30306@gmail.com> List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Grant, my output is the following: loaded at: 00400000 004E919C board data at: 00000000 0000007C relocated to: 00404040 004040BC zimage at: 00404E2C 004E620A avail ram: 004EA000 8DA05119 Linux/PPC load: console=ttyUL0,9600 Uncompressing Linux...done. Now booting the kernel 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? Thanks, 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. > -- Ricardo Ayres Severo