gdb debugging with openocd on codeblocks IDE

Question

I have recently started working on Gdb with openOCD for ARM Development on Codeblocks IDE. There are two commands in gdb like "load ./bin/Debug/ledtest.elf", "file ./bin/Debug/ledtest.elf" which will result in writing the program to flash and debugging.

My problem is whenever I am using these commands, its not writing into flash. I don't know how to make my ecosystem to do that? Whether I have to make relevent changes in gdb or openocd? However when I try to flash_write from openocd, it works fine. Any idea? Any relevant document will be helpful.

If anyone knows, tell me what are the sequence of commands took into the backend on flash when someone wrote "load ./bin/Debug/ledtest.elf". — anandamu16
– anandamu16, Commented Mar 27, 2017 at 12:46

fractalwrench · Accepted Answer · 2017-06-28 08:51:29Z

0

I don't know if you still have this problem, but anyway for completness:

I use this in my gdb debugger startup in codeblocks:

monitor reset halt

file Output/firmware.elf

mon flash write_image erase Output/firmware.elf

monitor halt

the flash command erases only the segments which are necessary for the firmware.

edited Jun 28, 2017 at 8:51

$fractalwrench's user avatar$

fractalwrench

4,0867 gold badges35 silver badges49 bronze badges

answered Jun 28, 2017 at 8:29

duderino65

132 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

anandamu16 Over a year ago

Thanks for reply, But whenever, I uses 'monitor reset halt' it gives me the error 'ocd_bouncer'. Do you have any idea, what could be the reason?

Collectives™ on Stack Overflow

gdb debugging with openocd on codeblocks IDE

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related