eclipse and OpenOCD

Harold R. OP #1173432 
I have been attempting to get Yagarto set up to perform the way I like
it. One thing I have noticed is that when I want to debug I first run
openocd as an external tool. Afterwords if I want to reprogram my mcu it
also makes a call to openocd but with a different config file for
burning the flash.

The problem is that if I first debug. Then make edits and want to
reprogram the mcu I must first exit eclipse to kill the openocd that is
currently running. If I try to reprogram the mcu (runs openocd) while
openocd is already running the process fails.

So my question is this. Is there a way to kill the openocd process that
is currently running from inside eclipse and without exiting Eclipse?
Reply Quote Edit Move Thread sperren Slow mode Anmeldepflicht aktivieren Anpinnen Delete topic Thread mit anderem zusammenführen Report Thanks
Michael F. #1173433 
Hello Harold,

which CPU you are using? The latest version of OpenOCD r278 and
a GDB which is compiled with the expat feature could write the
flash of the CPU from inside the Eclipse too.

It is a feature of the GDB, here the load command will flash the
CPU. Unfortunately I have not create a YAGARTO Version up to now
which will support it. I have here only a test version.

If you send me your eMail address, I could send you a patch for
YAGARTO and the latest OpenOCD for testing.

Best regards,

Michael
Reply Quote Edit Delete Report Thanks
Harold R. OP #1173434 
Michael Fischer wrote:
> Hello Harold,
>
> which CPU you are using? The latest version of OpenOCD r278 and
> a GDB which is compiled with the expat feature could write the
> flash of the CPU from inside the Eclipse too.
>
> It is a feature of the GDB, here the load command will flash the
> CPU. Unfortunately I have not create a YAGARTO Version up to now
> which will support it. I have here only a test version.
>
> If you send me your eMail address, I could send you a patch for
> YAGARTO and the latest OpenOCD for testing.
>
> Best regards,
>
> Michael

Thanks Michael!

hl_ritter@hotmail.com

My environment:

WinXP SP2
Yagarto
Xverve Signalyzer
AT91SAM7S256

I have been using a combination of your How To articles and James
Lynch's tutorial Rev C. I modified the .script file to erase the flash
prior to programming it.

Also the JPL tutorial says to check the box that says "Stop on startup
at:" while creating the debug launch. My eclipse did not have this box
so I modified the run commands to the GDB to creat a break point at
main, then continue, then clear the breakpoint at main. This got me the
desired effect that when I launch the debugger the start up code runs
and the program is halted at the first line of code in the main
function.
Reply Quote Edit Delete Report Thanks
Watch this topic

Reply

A question of your own? This thread is over 18 years old. Ask it in a thread of its own – more people read along there, and it gets answered more often and sooner.

Start a new thread

A fix, an addition or feedback on this thread? Then reply here.

Formatting
  • [c]C-Code[/c]
  • [code]code in other languages, ASCII drawings[/code]
  • [math]formula (LaTeX syntax)[/math]
  • [[Title]] – link to an article
  • Link to another post: right-click its post ID (#8078628), copy the address, paste it into the text

More about formatting

Post long source code as an attachment, not in the text.

Your name and e-mail address

Already registered? Log in

Not shown to anyone. We send you a link; your post appears once you confirm it there.

By submitting you create a free account and accept the terms of use.