* ARM target not boot after remap memory
@ 2010-09-13 11:25 Robin Theunis
2010-09-13 12:07 ` Mike Rapoport
` (2 more replies)
0 siblings, 3 replies; 17+ messages in thread
From: Robin Theunis @ 2010-09-13 11:25 UTC (permalink / raw)
To: Linux Kernel Mailing List, linux-embedded
Dear (Embedded)-Kernel-Devs,
I'm trying to build linux 2.6.34.1 for a AT91RM9200 target. The whole
build process is successful because I get correct kernel images and
also a uImage for U-boot.
The U-boot version is 2010.08. I have build the whole system on a
64bit ubuntu machine. I use the latest buildroot to make the toolchain
and etc. At this moment I have a
openocd jtag dongle connected to my target for debug sessions.
I have check that the machine id/type are correct. I have gotten those
error messages of a unsupported target. I have resolved those errors.
The target is self is a AT91RM9200 with 64MiB ram and 16MiB cfi flash.
The boot args of u-boot are "console=ttyS0,115200n8
root=/dev/mtdblock0 rootfstype=jffs2 mem=64M".
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
---
This just loops at that address. Why does it that?
You see that the mmu is enabled and the cpu has remapped the memory.
Does someone have a clue what goes wrong?
Here is the .config and board file.
http://www.on8rth.be/wp-content/uploads/2010/09/dotconfig.txt
http://www.on8rth.be/wp-content/uploads/2010/09/board-robin9200.c
Thank you
Robin Theunis
ON8RTH
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: ARM target not boot after remap memory
2010-09-13 11:25 ARM target not boot after remap memory Robin Theunis
@ 2010-09-13 12:07 ` Mike Rapoport
2010-09-13 12:12 ` Johannes Stezenbach
2010-09-13 21:41 ` Wolfgang Denk
2 siblings, 0 replies; 17+ messages in thread
From: Mike Rapoport @ 2010-09-13 12:07 UTC (permalink / raw)
To: Robin Theunis
Cc: Linux Kernel Mailing List, linux-embedded mailing list, LAKML
(add LAKLM to CC)
Robin Theunis wrote:
> Dear (Embedded)-Kernel-Devs,
>
> I'm trying to build linux 2.6.34.1 for a AT91RM9200 target. The whole
> build process is successful because I get correct kernel images and
> also a uImage for U-boot.
> The U-boot version is 2010.08. I have build the whole system on a
> 64bit ubuntu machine. I use the latest buildroot to make the toolchain
> and etc. At this moment I have a
> openocd jtag dongle connected to my target for debug sessions.
> I have check that the machine id/type are correct. I have gotten those
> error messages of a unsupported target. I have resolved those errors.
> The target is self is a AT91RM9200 with 64MiB ram and 16MiB cfi flash.
> The boot args of u-boot are "console=ttyS0,115200n8
> root=/dev/mtdblock0 rootfstype=jffs2 mem=64M".
>
> 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
> ---
>
> This just loops at that address. Why does it that?
> You see that the mmu is enabled and the cpu has remapped the memory.
> Does someone have a clue what goes wrong?
>
> Here is the .config and board file.
> http://www.on8rth.be/wp-content/uploads/2010/09/dotconfig.txt
> http://www.on8rth.be/wp-content/uploads/2010/09/board-robin9200.c
>
> Thank you
>
> Robin Theunis
> ON8RTH
> --
> 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/
--
Sincerely yours,
Mike.
^ permalink raw reply [flat|nested] 17+ messages in thread
* ARM target not boot after remap memory
@ 2010-09-13 12:07 ` Mike Rapoport
0 siblings, 0 replies; 17+ messages in thread
From: Mike Rapoport @ 2010-09-13 12:07 UTC (permalink / raw)
To: linux-arm-kernel
(add LAKLM to CC)
Robin Theunis wrote:
> Dear (Embedded)-Kernel-Devs,
>
> I'm trying to build linux 2.6.34.1 for a AT91RM9200 target. The whole
> build process is successful because I get correct kernel images and
> also a uImage for U-boot.
> The U-boot version is 2010.08. I have build the whole system on a
> 64bit ubuntu machine. I use the latest buildroot to make the toolchain
> and etc. At this moment I have a
> openocd jtag dongle connected to my target for debug sessions.
> I have check that the machine id/type are correct. I have gotten those
> error messages of a unsupported target. I have resolved those errors.
> The target is self is a AT91RM9200 with 64MiB ram and 16MiB cfi flash.
> The boot args of u-boot are "console=ttyS0,115200n8
> root=/dev/mtdblock0 rootfstype=jffs2 mem=64M".
>
> 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
> ---
>
> This just loops at that address. Why does it that?
> You see that the mmu is enabled and the cpu has remapped the memory.
> Does someone have a clue what goes wrong?
>
> Here is the .config and board file.
> http://www.on8rth.be/wp-content/uploads/2010/09/dotconfig.txt
> http://www.on8rth.be/wp-content/uploads/2010/09/board-robin9200.c
>
> Thank you
>
> Robin Theunis
> ON8RTH
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Sincerely yours,
Mike.
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: ARM target not boot after remap memory
2010-09-13 11:25 ARM target not boot after remap memory Robin Theunis
2010-09-13 12:07 ` Mike Rapoport
@ 2010-09-13 12:12 ` Johannes Stezenbach
[not found] ` <AANLkTiksacwuOwqJGZ0F3M1jhZ6Srr88wbfBQodOGOAt@mail.gmail.com>
2010-09-13 21:41 ` Wolfgang Denk
2 siblings, 1 reply; 17+ messages in thread
From: Johannes Stezenbach @ 2010-09-13 12:12 UTC (permalink / raw)
To: Robin Theunis; +Cc: Linux Kernel Mailing List, linux-embedded
On Mon, Sep 13, 2010 at 01:25:26PM +0200, Robin Theunis wrote:
>
> 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
> ---
>
> This just loops at that address. Why does it that?
Maybe it panicked but you can't see the message since
you have not enabled EARLY_PRINTK.
Since you have JTAG, you could also dump the printk
buffer __log_buf to see the message.
HTH
Johannes
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: ARM target not boot after remap memory
2010-09-13 12:07 ` Mike Rapoport
@ 2010-09-13 12:40 ` Russell King - ARM Linux
-1 siblings, 0 replies; 17+ messages in thread
From: Russell King - ARM Linux @ 2010-09-13 12:40 UTC (permalink / raw)
To: Mike Rapoport
Cc: Robin Theunis, LAKML, Linux Kernel Mailing List,
linux-embedded mailing list
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 ?
^ permalink raw reply [flat|nested] 17+ messages in thread
* ARM target not boot after remap memory
@ 2010-09-13 12:40 ` Russell King - ARM Linux
0 siblings, 0 replies; 17+ messages in thread
From: Russell King - ARM Linux @ 2010-09-13 12:40 UTC (permalink / raw)
To: linux-arm-kernel
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 ?
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: ARM target not boot after remap memory
2010-09-13 12:40 ` Russell King - ARM Linux
(?)
@ 2010-09-13 12:48 ` Robin Theunis
2010-09-13 12:51 ` Russell King - ARM Linux
2010-09-13 12:53 ` Russell King - ARM Linux
-1 siblings, 2 replies; 17+ messages in thread
From: Robin Theunis @ 2010-09-13 12:48 UTC (permalink / raw)
To: Russell King - ARM Linux; +Cc: linux-kernel
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 ?
>
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: ARM target not boot after remap memory
2010-09-13 12:48 ` Robin Theunis
@ 2010-09-13 12:51 ` Russell King - ARM Linux
2010-09-13 13:11 ` Robin Theunis
2010-09-13 12:53 ` Russell King - ARM Linux
1 sibling, 1 reply; 17+ messages in thread
From: Russell King - ARM Linux @ 2010-09-13 12:51 UTC (permalink / raw)
To: Robin Theunis; +Cc: linux-kernel
On Mon, Sep 13, 2010 at 02:48:18PM +0200, Robin Theunis wrote:
> 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.
Ensure that CONFIG_DEBUG_LL is enabled, and that it outputs to the correct
UART. The kernel will produce some messages via the DEBUG_LL stuff prior
to entering the __error loop.
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: ARM target not boot after remap memory
2010-09-13 12:48 ` Robin Theunis
@ 2010-09-13 12:53 ` Russell King - ARM Linux
2010-09-13 12:53 ` Russell King - ARM Linux
1 sibling, 0 replies; 17+ messages in thread
From: Russell King - ARM Linux @ 2010-09-13 12:53 UTC (permalink / raw)
To: Robin Theunis; +Cc: linux-kernel, linux-arm-kernel, linux-embedded mailing list
BTW, Please do not drop CCs.
On Mon, Sep 13, 2010 at 02:48:18PM +0200, Robin Theunis wrote:
> 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 ?
> >
^ permalink raw reply [flat|nested] 17+ messages in thread
* ARM target not boot after remap memory
@ 2010-09-13 12:53 ` Russell King - ARM Linux
0 siblings, 0 replies; 17+ messages in thread
From: Russell King - ARM Linux @ 2010-09-13 12:53 UTC (permalink / raw)
To: linux-arm-kernel
BTW, Please do not drop CCs.
On Mon, Sep 13, 2010 at 02:48:18PM +0200, Robin Theunis wrote:
> 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 ?
> >
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: ARM target not boot after remap memory
2010-09-13 12:51 ` Russell King - ARM Linux
@ 2010-09-13 13:11 ` Robin Theunis
0 siblings, 0 replies; 17+ messages in thread
From: Robin Theunis @ 2010-09-13 13:11 UTC (permalink / raw)
To: Russell King - ARM Linux; +Cc: linux-kernel, linux-embedded
I have tested it.
When I compiled the kernel with debug_LL on the and triggered such an
error by changing r1 to
something different. And then I got an error of unsupport machine.
2010/9/13 Russell King - ARM Linux <linux@arm.linux.org.uk>
> On Mon, Sep 13, 2010 at 02:48:18PM +0200, Robin Theunis wrote:
>> 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.
>
> Ensure that CONFIG_DEBUG_LL is enabled, and that it outputs to the correct
> UART. The kernel will produce some messages via the DEBUG_LL stuff prior
> to entering the __error loop.
>
^ permalink raw reply [flat|nested] 17+ messages in thread
* Fwd: ARM target not boot after remap memory
[not found] ` <AANLkTiksacwuOwqJGZ0F3M1jhZ6Srr88wbfBQodOGOAt@mail.gmail.com>
@ 2010-09-13 14:31 ` Robin Theunis
2010-09-13 17:26 ` Johannes Stezenbach
1 sibling, 0 replies; 17+ messages in thread
From: Robin Theunis @ 2010-09-13 14:31 UTC (permalink / raw)
To: linux-kernel, linux-embedded
hi Johannes
I have compiled the kernel with early printk on and debug_LL, It
still doesn't nothing after that line.
Robin
2010/9/13 Johannes Stezenbach <js@sig21.net>:
> On Mon, Sep 13, 2010 at 01:25:26PM +0200, Robin Theunis wrote:
>>
>> 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
>> ---
>>
>> This just loops at that address. Why does it that?
>
> Maybe it panicked but you can't see the message since
> you have not enabled EARLY_PRINTK.
>
> Since you have JTAG, you could also dump the printk
> buffer __log_buf to see the message.
>
>
> HTH
> Johannes
>
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: ARM target not boot after remap memory
[not found] ` <AANLkTiksacwuOwqJGZ0F3M1jhZ6Srr88wbfBQodOGOAt@mail.gmail.com>
2010-09-13 14:31 ` Fwd: " Robin Theunis
@ 2010-09-13 17:26 ` Johannes Stezenbach
2010-09-13 18:28 ` Robin Theunis
1 sibling, 1 reply; 17+ messages in thread
From: Johannes Stezenbach @ 2010-09-13 17:26 UTC (permalink / raw)
To: Robin Theunis; +Cc: linux-kernel, linux-embedded
On Mon, Sep 13, 2010 at 04:30:17PM +0200, Robin Theunis wrote:
>
> I have compiled the kernel with early printk on and debug_LL, It still
> doesn't nothing after that line.
Please don't top-post.
Did you add "earlyprintk" to your kernel command line
like the EARLY_PRINTK menuconfig help text suggests?
arch/arm/mach-at91/include/mach/debug-macro.S also suggests
the LL debug output goes to AT91 debug unit not to normal UART
(not sure about this, I don't know much about AT91).
Did you try to dump __log_buf using JTAG?
HTH
Johannes
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: ARM target not boot after remap memory
2010-09-13 17:26 ` Johannes Stezenbach
@ 2010-09-13 18:28 ` Robin Theunis
2010-09-13 19:12 ` Robin Theunis
0 siblings, 1 reply; 17+ messages in thread
From: Robin Theunis @ 2010-09-13 18:28 UTC (permalink / raw)
To: Johannes Stezenbach; +Cc: linux-kernel, linux-embedded
The __log_buf
<5>Linux version 2.6.34.1robin9200v1.0 (robin@pc-robin) (gcc version
4.3.5 (Buildroot 2010.08) ) #36 Mon Sep 13 15:18:08 CEST 2010
<4>CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177
<4>CPU: VIVT data cache, VIVT instruction cache
<4>Machine configuration botched (nr 251), unable to continue.
I don't understand it. What does it means? I have my mach types setup correctly.
Robin
2010/9/13 Johannes Stezenbach <js@sig21.net>:
> On Mon, Sep 13, 2010 at 04:30:17PM +0200, Robin Theunis wrote:
>>
>> I have compiled the kernel with early printk on and debug_LL, It still
>> doesn't nothing after that line.
>
> Please don't top-post.
>
> Did you add "earlyprintk" to your kernel command line
> like the EARLY_PRINTK menuconfig help text suggests?
>
> arch/arm/mach-at91/include/mach/debug-macro.S also suggests
> the LL debug output goes to AT91 debug unit not to normal UART
> (not sure about this, I don't know much about AT91).
> Did you try to dump __log_buf using JTAG?
>
>
> HTH
> Johannes
>
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: ARM target not boot after remap memory
2010-09-13 18:28 ` Robin Theunis
@ 2010-09-13 19:12 ` Robin Theunis
0 siblings, 0 replies; 17+ messages in thread
From: Robin Theunis @ 2010-09-13 19:12 UTC (permalink / raw)
To: Johannes Stezenbach; +Cc: linux-kernel, linux-embedded
Solved that problem. Typo in my mach types.
Now the next problem:
<5>Linux version 2.6.34.1robin9200v1.0 (robin@pc-robin) (gcc version
4.3.5 (Buildroot 2010.08) ) #37 Mon Sep 13 20:57:43 CEST 2010
<4>CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177
<4>CPU: VIVT data cache, VIVT instruction cache
<4>Machine: Robin9200
<6>bootconsole [earlycon0] enabled
<4>Memory policy: ECC disabled, Data cache writeback
<7>On node 0 totalpages: 16384
<7>free_area_init_node: node 0, pgdat c037f45c, node_mem_map c0394000
<7> Normal zone: 128 pages used for memmap
<7> Normal zone: 0 pages reserved
<7> Normal zone: 16256 pages, LIFO batch:3
<4>Clocks: CPU 179 MHz, master 59 MHz, main 18.432 MHz
<4>Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256
<1>Unable to handle kernel paging request at virtual address fefc4014
<1>pgd = c0004000
<1>[fefc4014] *pgd=20417051, *pte=00000000, *ppte=00000000
<0>Internal error: Oops: 27 [#1]
<0>last sysfs file:
<4>Modules linked in:
<4>CPU: 0 Not tainted (2.6.34.1robin9200v1.0 #37)
<4>PC is at printascii+0x14/0x50
<4>LR is at early_write+0x28/0x5c
<4>pc : [<c0026180>] lr : [<c0026218>] psr: 200000d3
<4>sp : c0361e88 ip : c0361ea4 fp : c0361ea0
<4>r10: fffffd3e r9 : c0366084 r8 : c0366084
<4>r7 : c0366080 r6 : 0000004b r5 : c03806b7 r4 : 00000001
<4>r3 : fefc4000 r2 : 0000004b r1 : 00000042 r0 : 00000000
<4>Flags: nzCv IRQs off FIQs off Mode SVC_32 ISA ARM Segment kernel
<4>Control: c000717f Table: 20004000 DAC: 00000017
<0>Process swapper (pid: 0, stack limit = 0xc03
What does it mean?
Robin
2010/9/13 Robin Theunis <robint91@gmail.com>:
> The __log_buf
>
> <5>Linux version 2.6.34.1robin9200v1.0 (robin@pc-robin) (gcc version
> 4.3.5 (Buildroot 2010.08) ) #36 Mon Sep 13 15:18:08 CEST 2010
> <4>CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177
> <4>CPU: VIVT data cache, VIVT instruction cache
> <4>Machine configuration botched (nr 251), unable to continue.
>
> I don't understand it. What does it means? I have my mach types setup correctly.
>
> Robin
>
> 2010/9/13 Johannes Stezenbach <js@sig21.net>:
>> On Mon, Sep 13, 2010 at 04:30:17PM +0200, Robin Theunis wrote:
>>>
>>> I have compiled the kernel with early printk on and debug_LL, It still
>>> doesn't nothing after that line.
>>
>> Please don't top-post.
>>
>> Did you add "earlyprintk" to your kernel command line
>> like the EARLY_PRINTK menuconfig help text suggests?
>>
>> arch/arm/mach-at91/include/mach/debug-macro.S also suggests
>> the LL debug output goes to AT91 debug unit not to normal UART
>> (not sure about this, I don't know much about AT91).
>> Did you try to dump __log_buf using JTAG?
>>
>>
>> HTH
>> Johannes
>>
>
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: ARM target not boot after remap memory
2010-09-13 11:25 ARM target not boot after remap memory Robin Theunis
2010-09-13 12:07 ` Mike Rapoport
2010-09-13 12:12 ` Johannes Stezenbach
@ 2010-09-13 21:41 ` Wolfgang Denk
2010-09-14 5:32 ` Robin Theunis
2 siblings, 1 reply; 17+ messages in thread
From: Wolfgang Denk @ 2010-09-13 21:41 UTC (permalink / raw)
To: Robin Theunis; +Cc: Linux Kernel Mailing List, linux-embedded
Dear Robin Theunis,
In message <AANLkTi=tWwaFHB0DY=j0UaqbYdYJpGJpmWdGC4aMufSw@mail.gmail.com> you wrote:
>
> The U-boot version is 2010.08. I have build the whole system on a
There is no such version of U-Boot.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
What is tolerance? -- it is the consequence of humanity. We are all
formed of frailty and error; let us pardon reciprocally each other's
folly -- that is the first law of nature. - Voltaire
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: ARM target not boot after remap memory
2010-09-13 21:41 ` Wolfgang Denk
@ 2010-09-14 5:32 ` Robin Theunis
0 siblings, 0 replies; 17+ messages in thread
From: Robin Theunis @ 2010-09-14 5:32 UTC (permalink / raw)
To: Wolfgang Denk; +Cc: linux-kernel, linux-embedded
Dear Wolfgang,
I messed up the buildroot and u-boot version!
u-boot = 2010.06
and
buildroot = 2010.08
Sorry all, my fault.
Best regards,
Robin Theunis
2010/9/13 Wolfgang Denk <wd@denx.de>:
> Dear Robin Theunis,
>
> In message <AANLkTi=tWwaFHB0DY=j0UaqbYdYJpGJpmWdGC4aMufSw@mail.gmail.com> you wrote:
>>
>> The U-boot version is 2010.08. I have build the whole system on a
>
> There is no such version of U-Boot.
>
> Best regards,
>
> Wolfgang Denk
>
> --
> DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
> What is tolerance? -- it is the consequence of humanity. We are all
> formed of frailty and error; let us pardon reciprocally each other's
> folly -- that is the first law of nature. - Voltaire
>
^ permalink raw reply [flat|nested] 17+ messages in thread
end of thread, other threads:[~2010-09-14 5:32 UTC | newest]
Thread overview: 17+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-09-13 11:25 ARM target not boot after remap memory Robin Theunis
2010-09-13 12:07 ` Mike Rapoport
2010-09-13 12:07 ` Mike Rapoport
2010-09-13 12:40 ` Russell King - ARM Linux
2010-09-13 12:40 ` Russell King - ARM Linux
2010-09-13 12:48 ` Robin Theunis
2010-09-13 12:51 ` Russell King - ARM Linux
2010-09-13 13:11 ` Robin Theunis
2010-09-13 12:53 ` Russell King - ARM Linux
2010-09-13 12:53 ` Russell King - ARM Linux
2010-09-13 12:12 ` Johannes Stezenbach
[not found] ` <AANLkTiksacwuOwqJGZ0F3M1jhZ6Srr88wbfBQodOGOAt@mail.gmail.com>
2010-09-13 14:31 ` Fwd: " Robin Theunis
2010-09-13 17:26 ` Johannes Stezenbach
2010-09-13 18:28 ` Robin Theunis
2010-09-13 19:12 ` Robin Theunis
2010-09-13 21:41 ` Wolfgang Denk
2010-09-14 5:32 ` Robin Theunis
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.