> >> If the section addresses does not match the actual
> memory layout of
> >> the target, there's nothing gdb can do about it.
> >
> > I disagree; gdb can certainly discover this has, and must have, the offset.
> > It's
GDB runs by the memory map that OpenOCD feeds it
during startup. That
On Sat, Sep 4, 2010 at 7:31 PM, Peter Stuge wrote:
> Andreas Fritiofson wrote:
>> When gdb is asked to load an image it simply writes all relevant
>> sections in that image to their respective memory locations. If it
>> has knowledge that the location to be written resides in flash, it
>> uses the
I have had some success with Code::Blocks on Windows. On Linux it works fine.
On Windows there are a few annoyances. The main one is how to halt remote
targets. With OpenOCD I do it through the telnet interface. See the
discussion
at http://forums.codeblocks.org/index.php/topic,12412.0.htm
Mike Dunn wrote:
> > i keep getting the following error
> >
> > > flash write_image main.bin.out
> > couldn't open main.bin.out
>
> File not in pwd? Specify the full path to the file.
Clarify: Remember it's pwd of OpenOCD. Also when running monitor
flash ... from gdb.
//Peter
_
John> [st32 flash can be at 0x0 or 0x800, I want to link my code at
0x0...]
Is there a specific technical advantage you are gaining? I can't think
of any. If there is - please explain.
Have you tried the "load address" in the linker? Hence, the code "loads"
at address(fixed location of f
Andreas Fritiofson wrote:
> When gdb is asked to load an image it simply writes all relevant
> sections in that image to their respective memory locations. If it
> has knowledge that the location to be written resides in flash, it
> uses the vFlash* commands, otherwise it uses regular memory writes
Both OpenOCD and GDB work perfectly well with correct files (standard
OpenOCD .cfgs, correctly linked .elf file) so I really don't see any
problem you're trying to fix...
4\/3!!
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
On 2010-09-04 13:04, Duane Ellis wrote:
Q: What are the openocd + gdb + windows users using as their GUI front end?
Me (and many others) use Eclipse + Zylin plug-in + GDB Hardware
Debugging plug-in.
4\/3!!
___
Openocd-development mailing list
Openo
On Sat, Sep 4, 2010 at 2:57 PM, Peter Stuge wrote:
> Øyvind Harboe wrote:
>> Perhaps this is a thing that *should* be a bit hard?
>>
>> Perhaps embedded users *should* learn about the load offset for
>> GDB?
>
> Do you know if gdb always sends an offset in the (binary?) command to
> OpenOCD? If ye
Øyvind Harboe wrote:
> Perhaps this is a thing that *should* be a bit hard?
>
> Perhaps embedded users *should* learn about the load offset for
> GDB?
Do you know if gdb always sends an offset in the (binary?) command to
OpenOCD? If yes, I think gdb should be changed to make 'load' easier
to use.
I've made a small plugin to Eclipse, which essentially allows
one to launch GDB with a short custom sequence like:
target remote xxx:333
monitor reset init
load
stepi
http://opensource.zylin.com/embeddedcdt.html
--
Øyvind Harboe
US toll free 1-866-980-3434 / International +47 51 63 25 00
http
> Q: What are the openocd + gdb + windows users using as their GUI front end?
I'm using Eclipse CDT. I've tried to push the CDT guys in
the direction of supporting launching Eclipse from the command
line just like Insight...
https://bugs.eclipse.org/bugs/show_bug.cgi?id=39640
--
Øyvind Harboe
U
For years, I have used "gdb-insight" - (the Tcl/Tk version of GDB)
http://sourceware.org/insight/
However, it has grown long in the tooth, and cygwin has moved on.
At this point, the changes in Cygwin have broken the private copy of
Tcl/Tk (from 2004),
Some notes:
Insight has always had a
13 matches
Mail list logo
