At 01:32 PM 9/5/10, Spencer Oliver wrote:
On 03/09/2010 20:29, John Hartman (NoICE) wrote:
The STM32 parts have Flash beginning at 0x800, and OpenOCD's
stm32x.c places the Flash there regardless of the address used in the
flash command in the cfg file.
The chips have two pins that can be
On 03/09/2010 20:29, John Hartman (NoICE) wrote:
The STM32 parts have Flash beginning at 0x800, and OpenOCD's
stm32x.c places the Flash there regardless of the address used in the
flash command in the cfg file.
The chips have two pins that can be jumpered to specify what appears at
address
On Fri, Sep 3, 2010 at 11:48 PM, John Hartman (NoICE)
j...@noicedebugger.com wrote:
At 03:30 PM 9/3/10, Øyvind Harboe wrote:
But it does what you need?
Yes.
My hope was to move from possible to configure to easy to use. But it
is certainly possible to use load with an offset.
That's OK.
Ø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.
On Sat, Sep 4, 2010 at 2:57 PM, Peter Stuge pe...@stuge.se 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
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
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.
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
On Sat, Sep 4, 2010 at 7:31 PM, Peter Stuge pe...@stuge.se 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
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 memory map
Shooting from he hip: what about the offset to gdb's load command?
Could that help?
--
Øyvind Harboe
US toll free 1-866-980-3434 / International +47 51 63 25 00
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
The syntax of load with an offset is also a bit annoying:
But it does what you need?
--
Øyvind Harboe
US toll free 1-866-980-3434 / International +47 51 63 25 00
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
On Fri, Sep 3, 2010 at 9:29 PM, John Hartman (NoICE)
j...@noicedebugger.com wrote:
The STM32 parts have Flash beginning at 0x800, and OpenOCD's stm32x.c
places the Flash there regardless of the address used in the flash command
in the cfg file.
The chips have two pins that can be jumpered
At 02:48 PM 9/3/10, Ãyvind Harboe wrote:
Shooting from he hip: what about the offset to gdb's load command?
The short answer is I didn't know that gdb's load HAD an offset.
The longer answer is that gdb may be invoked by
Eclipse, Insight, CodeBlocks etc. In that case,
specifying an offset
At 03:30 PM 9/3/10, Ãyvind Harboe wrote:
But it does what you need?
Yes.
My hope was to move from possible to configure
to easy to use. But it is certainly possible to use load with an offset.
Best regards, John Hartman
NoICE Debugging Tools
http://www.noicedebugger.com
At 03:32 PM 9/3/10, Andreas Fritiofson wrote:
Annoying how? The flash IS at 0x0800. Why would you want to link
your program to 0? That if anything would be relying on the aliasing.
Of course it works, otherwise the chip couldn't start, but does it
alias the entire flash and not just enough
John Hartman (NoICE) wrote:
My intent was to make it easier for people to get gdb and OpenOCD
running. The volume of how do I do it traffic here and on
SparkFun indicates to me that things could be made easier.
This is a good initiative, but I think it's important to consider the
different
17 matches
Mail list logo
