| eclipse 3.2 ARM debug [message #236255] |
Wed, 22 July 2009 07:58  |
Eclipse User |
|
|
|
Hi,
I am using eclipse 3.2 for debugging an ARM based platform, AT91SAM9263.
The tool chain used is YAGARTO. I am doing the target debugging with ATMEL
SAM ICE, which is connected to the target(AT91SAM9263) via JTAG interface.
While going through the C code step by step, each 'stepping' is taking
around 7-8 seconds and also, often, the debugger is getting hanged. Also,
processor the frequency displayed in the Jlink GDB Server is 5KHz.
Why is it that the debugger is performing slow, or is it the maximum that
I can get out of a debugger using Eclipse. Please give me some
documentations which will help me do a better debugging in Eclipse 3.2,
using SAM ICE. I have also made sure that the hardware connections(JTAG
interface) are correct.
I am getting a better performance (in terms of debugging speed) when I use
a ARM7 based evaluation board from ATMEL. In the latter case, the
frequency displayed in JLink GDB Server is 1000 KHz.
|
|
|
| Re: eclipse 3.2 ARM debug [message #236263 is a reply to message #236255] |
Wed, 22 July 2009 08:14  |
| Eclipse User |
|
|
|
Not sure this could help since I did not play with 3.2 for a long time.
Nevertheless, let me try..
I had some impression that some slowness is caused by source directory
configuration that CDT provides for GDB. You can try to remove all default
source directories (usually it is a list of all directories of your
project) in debug configuration.
Also, i would recommend to use "hardware debugger", but not sure it is
available on 3.2. If not, you can try zylin plugin
http://opensource.zylin.com/embeddedcdt.html
GIGIN JOSE wrote:
> Hi,
> I am using eclipse 3.2 for debugging an ARM based platform, AT91SAM9263.
> The tool chain used is YAGARTO. I am doing the target debugging with ATMEL
> SAM ICE, which is connected to the target(AT91SAM9263) via JTAG interface.
> While going through the C code step by step, each 'stepping' is taking
> around 7-8 seconds and also, often, the debugger is getting hanged. Also,
> processor the frequency displayed in the Jlink GDB Server is 5KHz.
> Why is it that the debugger is performing slow, or is it the maximum that
> I can get out of a debugger using Eclipse. Please give me some
> documentations which will help me do a better debugging in Eclipse 3.2,
> using SAM ICE. I have also made sure that the hardware connections(JTAG
> interface) are correct.
> I am getting a better performance (in terms of debugging speed) when I use
> a ARM7 based evaluation board from ATMEL. In the latter case, the
> frequency displayed in JLink GDB Server is 1000 KHz.
|
|
|
Powered by
FUDForum. Page generated in 0.03047 seconds
Home