Error in head-common.S file while ARM Linux booting

Nicolas Pitre nico at
Thu Apr 21 16:22:48 EDT 2011

On Thu, 21 Apr 2011, Madhavi Manchala wrote:

> Dear All,
> I have developed machine code for my Samsung S3C2510A MCU under Linux
> kernel 2.6.36. The code exists at arch/arm/mach-s3c2510a. I developed
> only CPU, UART and Clocks initialization code, especially. For
> developing the S3C2510A HAL code, I have gone through the existing
> mach-s3c2410 code.
> I build vmlinux image on a Linux box in the ELF format for my Samsung
> MCU. Then, I am trying to load the build vmlinux image on to my
> device’s (targets) RAM area using J-link J-TAG and J-LinkGDBServer
> tool with a gdbinit script file from Cygwin on a Windows XP system.
> The gdb init script file initializes the CPU system configuration
> registers, RAM, Flash and UART registers and then loads ELF image.
> I am able to put break points in the developed HAL code. However, when
> I run (continue) from gdb prompt, I did not see any break points in
> the GDB server tool, but, when I press “Ctrl+C”, I am seeing the
> following messages.
> <gdb> break s3c2510a_init
> Breakpoint 1 at 0x3000b648: file arch/arm/mach-s3c2510a/s3c2510a.c, line 59.
> <gdb> c
> Continuing.
> Pressing “control+c”, then the statements are as follows.
> Program received signal SIGTRAP, Trace/Breakpoint trap.
> __error_p () at head-common.S:142
> <gdb>bt
> #0 __error_p () at head-common.S:142
> Why am I seeing these errors? Am I missing any CPU configuration, still?

Did you look at the actual code below __error_p in 
arch/arm/kernel/head-common.S?  The code even shows what could be 
displayed on your serial port when you have CONFIG_DEBUG_LL enabled.


More information about the linux-arm-kernel mailing list