Hello,
thanks to your great tutorials I finally could setup Eclipse. That is a bit unintuitive. But there are two problems left when I try to debug.
Eclipse forgets the debug configuration every time I close it. Is it possible to save the configuration of the Zylin plug-in?
Second problem is setting break points. I'm using an Atmel AT91SAM7XC-256. The code in flash memory, so software break points are not possible. How can I set hardware breakpoints? The micro-controller supports two of them.
Thanks in advance.
Frank
Problems debugging with Eclipse
Moderators: utzig, lbednarz, tfAteba, barthess, RoccoMarco
- Giovanni
- Site Admin
- Posts: 14057
- Joined: Wed May 27, 2009 8:48 am
- Location: Salerno, Italy
- Has thanked: 990 times
- Been thanked: 839 times
- Contact:
Re: Problems debugging with Eclipse
Hi Frank,
Eclipse should save the debug configurations, including the Zylin specific configurations, I never experienced that problem. Do you save the configuration by clicking the "Apply" button?
About the breakpoints, this is the configuration I use for the AT91SAM7X.
OpenOCD configuration file (this makes GDB use HW breakpoints):
'Initialize' commands in the debug configuration:
'Run' commands in the debug configuration:
After startup it is better to remove the breakpoint on main() or you will have only one breakpoint left. Note, the above sequences are for OpenOCD 3.1.
Giovanni
Eclipse should save the debug configurations, including the Zylin specific configurations, I never experienced that problem. Do you save the configuration by clicking the "Apply" button?
About the breakpoints, this is the configuration I use for the AT91SAM7X.
OpenOCD configuration file (this makes GDB use HW breakpoints):
Code: Select all
#daemon configuration
telnet_port 4444
gdb_port 3333
# GDB can also flash my flash!
gdb_memory_map enable
gdb_flash_program enable
gdb_breakpoint_override hard
# set WORKAREASIZE 0x5000
source [find interface/olimex-arm-usb-ocd.cfg]
source [find target/sam7x256.cfg]
'Initialize' commands in the debug configuration:
Code: Select all
target remote localhost:3333
'Run' commands in the debug configuration:
Code: Select all
monitor soft_reset_halt
monitor wait_halt
monitor poll
monitor flash probe 0
monitor flash write_bank 0 ch.bin 0
monitor soft_reset_halt
symbol-file ch.elf
thbreak main
continue
After startup it is better to remove the breakpoint on main() or you will have only one breakpoint left. Note, the above sequences are for OpenOCD 3.1.
Giovanni
Re: Problems debugging with Eclipse
Hi,
problem one got solved by an CDT update.
You OpenOCD configuration is almost working with version 0.4.0.
gdb_memory_map enable
gdb_flash_program enable
Give an error message, but both are default any way.
Thank you very much.
Frank
problem one got solved by an CDT update.
You OpenOCD configuration is almost working with version 0.4.0.
gdb_memory_map enable
gdb_flash_program enable
Give an error message, but both are default any way.
Thank you very much.
Frank
Who is online
Users browsing this forum: No registered users and 6 guests