On Tue, May 5, 2015 at 12:28 AM, James Murray <[email protected]> wrote:
> New OpenOCD developer here...
>
Welcome! I've answered what I can below.
> 4.
> What's the correct way to live view memory or variables?
> I'm aiming to use Eclipse / Zylin to work on my target code. Watching
> stuff in realtime is very important to me and something I'm used to from
> Freescale/P&E tools. I found some online references about a "live view"
> button, but I'm not seeing it.
>
I have not seen this feature working in Eclipse nor GDB. For memory, I
usually telnet to OpenOCD and dump it manually with mdw etc.
> 5.
> How to use "non-stop" or asynchronous mode? I'm thinking this is needed
> for point 4, but when I try to use it, gdb tells me that the target
> doesn't support it. Not sure how to tell gdb that it does.
>
At the very least, you'll need to use "target extended-remote" instead of
"target remote". Eclipse always chooses the latter but can perhaps be
convinced by using a .gdbinit script to connect instead of the UI. I have
not tried and I'm not sure that will enable point 4 by itself.
> 3.
> I seem to get random register synchronisation. Most times when I connect
> gdb to OpenOCD, gdb shows all the processor registers as zeros even
> though OpenOCD knows what their real contents are. I have to use
> flushregs and then usually the latest values are fetched.
>
> 6.
> Is there a way to "hot-sync" with a running target?
>
The solution to both of these may be the same: "monitor gdb_sync" followed
by "stepi". To attach to a running target, add these to Eclipse's
initialization box. I don't know why gdb does not show the correct
registers right after connect but it may depend on the target state during
connect.
> 7.
> What's needed to let gdb or Eclipse "know" what regions of memory need
> hardware breakpoints?
>
GDB deduces this from the memory map sent by OpenOCD. As long as you have
some flash defined, GDB will use HW breakpoints for those addresses. Also I
think OpenOCD will not try to use SW breakpoints in flash regions even if
asked.
Note that the flash must be probed *before* GDB connects in order for GDB
to receive the updated memory map. This may or may not require the target
to be halted.
Regards,
Andreas
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
