From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754978Ab0IMMlJ (ORCPT ); Mon, 13 Sep 2010 08:41:09 -0400 Received: from caramon.arm.linux.org.uk ([78.32.30.218]:56815 "EHLO caramon.arm.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751518Ab0IMMlI (ORCPT ); Mon, 13 Sep 2010 08:41:08 -0400 Date: Mon, 13 Sep 2010 13:40:49 +0100 From: Russell King - ARM Linux To: Mike Rapoport Cc: Robin Theunis , LAKML , Linux Kernel Mailing List , linux-embedded mailing list Subject: Re: ARM target not boot after remap memory Message-ID: <20100913124049.GG30787@n2100.arm.linux.org.uk> References: <4C8E1417.4060204@compulab.co.il> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4C8E1417.4060204@compulab.co.il> User-Agent: Mutt/1.5.19 (2009-01-05) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Sep 13, 2010 at 02:07:51PM +0200, Mike Rapoport wrote: > (add LAKLM to CC) >> The problem is now when linux kernel is booting, nothing happens. >> >> --- >> U-Boot> bootm >> ## Booting kernel from Legacy Image at 21000000 ... >> Image Name: Linux-2.6.34.1robin9200v1.0 >> Image Type: ARM Linux Kernel Image (uncompressed) >> Data Size: 1811796 Bytes = 1.7 MiB >> Load Address: 20008000 >> Entry Point: 20008000 >> Verifying Checksum ... OK >> Loading Kernel Image ... OK >> OK >> >> Starting kernel ... >> >> Uncompressing Linux... done, booting the kernel. >> --- >> >> Here is stalls. With my jtag probe I can locate the problem. >> >> --- >>> halt >> target state: halted >> target halted in ARM state due to debug-request, current mode: Supervisor >> cpsr: 0x600000d3 pc: 0xc000af3c >> MMU: enabled, D-Cache: enabled, I-Cache: enabled >>> arm disassemble 0xc000af3c >> 0xc000af3c 0xeafffffe B 0xc000af3c Probably __error. Either your machine isn't supported, or the kernel doesn't recognise your processor. Is your version of uboot sufficiently recent that it passes the correct machine ID in r1 ? From mboxrd@z Thu Jan 1 00:00:00 1970 From: linux@arm.linux.org.uk (Russell King - ARM Linux) Date: Mon, 13 Sep 2010 13:40:49 +0100 Subject: ARM target not boot after remap memory In-Reply-To: <4C8E1417.4060204@compulab.co.il> References: <4C8E1417.4060204@compulab.co.il> Message-ID: <20100913124049.GG30787@n2100.arm.linux.org.uk> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Mon, Sep 13, 2010 at 02:07:51PM +0200, Mike Rapoport wrote: > (add LAKLM to CC) >> The problem is now when linux kernel is booting, nothing happens. >> >> --- >> U-Boot> bootm >> ## Booting kernel from Legacy Image at 21000000 ... >> Image Name: Linux-2.6.34.1robin9200v1.0 >> Image Type: ARM Linux Kernel Image (uncompressed) >> Data Size: 1811796 Bytes = 1.7 MiB >> Load Address: 20008000 >> Entry Point: 20008000 >> Verifying Checksum ... OK >> Loading Kernel Image ... OK >> OK >> >> Starting kernel ... >> >> Uncompressing Linux... done, booting the kernel. >> --- >> >> Here is stalls. With my jtag probe I can locate the problem. >> >> --- >>> halt >> target state: halted >> target halted in ARM state due to debug-request, current mode: Supervisor >> cpsr: 0x600000d3 pc: 0xc000af3c >> MMU: enabled, D-Cache: enabled, I-Cache: enabled >>> arm disassemble 0xc000af3c >> 0xc000af3c 0xeafffffe B 0xc000af3c Probably __error. Either your machine isn't supported, or the kernel doesn't recognise your processor. Is your version of uboot sufficiently recent that it passes the correct machine ID in r1 ?