From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.179]) by ozlabs.org (Postfix) with ESMTP id 31464DDE0F for ; Tue, 28 Aug 2007 23:50:57 +1000 (EST) Received: by wa-out-1112.google.com with SMTP id m28so2264839wag for ; Tue, 28 Aug 2007 06:50:56 -0700 (PDT) Message-ID: Date: Tue, 28 Aug 2007 07:50:55 -0600 From: "Grant Likely" Sender: glikely@secretlab.ca To: "Miroslaw Dach" Subject: Re: Linux doesn not boot from u-boot on ML403 In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 References: Cc: Leonid , linuxppc-embedded@ozlabs.org List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 8/28/07, Miroslaw Dach wrote: > Hi Grant, > > Thanks for your answer. > I have found in the System.map : > c020f0c4 b __log_buf > > Is the address c020f0c4 relative to the .data segment? 0xc0000000 are virtual kernel addresses; not physical addresses. If the MMU is still on, then you need to use the virtual address to examine memory. If the MMU is off (such as after reloading u-boot), then you need to change 0xCxxxxxxx to 0x0xxxxxxxx. > I understand that when the system hangs I should type in the XMD window > stop. > > Is there anyway to examine the memory from the XMD window? or should I > reload the u-boot and examine the memory from u-boot? I don't know; I've never used XMD. Read the XMD documentation. You can do it from u-boot too. g. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. grant.likely@secretlab.ca (403) 399-0195