Thanks for all the info Paul. Very insightfull.
One last question. (I think I was poking in the wrong direction referring
to coreidx as a candidate for the ap passed to dap_get_debugbase, and
dap_lookup_cs_component)
Preceding the ROM table lookup functions there are two dap_find_ap
functions that try to find the APB and AHB APs for the target. These
functions would then put the ap number in armv7a->debug_ap and
armv7a->memory_ap variables respectively. Would it help solve the dbgbase
lookup by passing one of these values to the dap_get_debugbase, and
dap_lookup_cs_component? (I suspect ROM table lookups on targets with
multiple DAPs might become the issue?)
Regards
Olivier
On Fri, Jan 9, 2015 at 12:49 PM, Paul Fertser <[email protected]> wrote:
> On Fri, Jan 09, 2015 at 01:30:40PM +0300, Paul Fertser wrote:
> > Additionally, this whole thread worth reading if you're interested to
> > hear about more exotic combinations (e.g. two different non-SMP cores
> > on same DAP, additional JTAG AP etc):
> > http://thread.gmane.org/gmane.comp.debugging.openocd.devel/24915
>
> And this is also relevant:
> http://thread.gmane.org/gmane.comp.debugging.openocd.devel/24913
>
> --
> Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
> mailto:[email protected]
>
------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
