| Debugging lpc2138 arm7 through Eclipse [message #143587] |
Tue, 19 April 2005 16:04  |
Eclipse User |
|
|
|
Originally posted by: bluesboys.-remove.me-hotmail.com
Hi everybody
I'm trying to debug a program running on a lpc2138 microprocessor through
the Eclipse CDT 2.1.1 and a OCDRemote/Raven OCDemon combo. Since the lpc2138
is a ARM7 processor, I'm using the GNU ARM toolchain which includes the
arm-elf-gdb debugger.
When running from a console, the gdb works alright, allowing me to load the
program to the the processor, step through the programs source code and
inserting breakpoints. But when running from Eclipse none of this is
possible. It just starts running resulting in the processor to get stuck in
the bootloader (I need to tell GDB that the program starts at address
0x40000000)
Is it possible to tell gdb from CDT which address to start the execution?
I've also tried debugging from the uVision IDE (from Keil) and this program
uses an .ini file to initialise the program counter to 0x40000000 where the
programs startup code is situated. Is it possible to use such a file in CDT?
Finally I would like to know if anyone has any experience in debugging a
ARM7 processor through JTAG from Eclipse?
Best Regards
S
|
|
|
| Re: Debugging lpc2138 arm7 through Eclipse [message #143732 is a reply to message #143587] |
Wed, 20 April 2005 07:49  |
| Eclipse User |
|
|
|
Originally posted by: bluesboys.-remove-this-hotmail.com
"Hansen" <bluesboys@-remove.me-hotmail.com> wrote in message
news:d43o9c$2o1$1@news.eclipse.org...
> Hi everybody
>
> I'm trying to debug a program running on a lpc2138 microprocessor through
> the Eclipse CDT 2.1.1 and a OCDRemote/Raven OCDemon combo. Since the
> lpc2138 is a ARM7 processor, I'm using the GNU ARM toolchain which
> includes the arm-elf-gdb debugger.
>
> When running from a console, the gdb works alright, allowing me to load
> the program to the the processor, step through the programs source code
> and inserting breakpoints. But when running from Eclipse none of this is
> possible. It just starts running resulting in the processor to get stuck
> in the bootloader (I need to tell GDB that the program starts at address
> 0x40000000)
> Is it possible to tell gdb from CDT which address to start the execution?
>
> I've also tried debugging from the uVision IDE (from Keil) and this
> program uses an .ini file to initialise the program counter to 0x40000000
> where the programs startup code is situated. Is it possible to use such a
> file in CDT?
>
> Finally I would like to know if anyone has any experience in debugging a
> ARM7 processor through JTAG from Eclipse?
>
> Best Regards
> S
|
|
|
Powered by
FUDForum. Page generated in 0.03031 seconds
Home