Hi Oliver, On Fri, Jan 09, 2015 at 10:58:42AM +0200, Olivier Schonken wrote: > These functions are only called when no dbgbase is specified in the > target tcl script, to try and get the debugbase from the ROM table.
I'm aware of it, please see ec9ccaa288491a5ec09da96e07d7cba3aee981c9 . > But, the fact that more than half of the boards specify dbgbase tells me that > there is an issue with looking up the dbgbase from the ROM table There certainly was a problem regarding nested tables (not supported at all) and multicore (all the cores were assigned the same dbgbase). The mentioned commit is known to help on all of the targets it was tested on. So far all the targets we were told about had all the cores specified in the single ROM table (including its subtables) on a single DAP. I've seen "dap info 1" for several of them and it was convincing enough that it can't be common to have different SMP cores on different DAPs. Please also see the review comments on http://openocd.zylin.com/#/c/1920/ . 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 To sum up: I agree that hardcoding DAP 1 is utterly wrong. The whole DAP handling as is done in OpenOCD currently is wrong. If there's a _proper_ and non-intrusive way to fix at least DAP selection for the common cases, I'm all ears. -- 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
