Messages in this thread | | | Date | Mon, 13 Sep 2010 14:48:18 +0200 | Subject | Re: ARM target not boot after remap memory | From | Robin Theunis <> |
| |
Hi Russell,
Yes I have tested it. I made a breakpoint at 0x2008000 and viewed that the r1 register and there in I found the correct ID.
Robin
2010/9/13 Russell King - ARM Linux <linux@arm.linux.org.uk>: > 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 ? > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |