Hi David, Am 27.04.2015 um 23:22 schrieb gerrit: > commit af683ccd96dd575aa41f1d8051dce154186f411b > Author: David Ung <[email protected]> > Date: Mon Apr 20 13:14:43 2015 -0700 > > aarch64: Correct target state for hardware step [snip]
I have tried your aarch64 patches up to http://openocd.zylin.com/#/c/2747/1 (af683ccd96dd575aa41f1d8051dce154186f411b) - hoping that's the latest. What I'm missing is some example target configs or documentation to test this. Is your --enable-target64 code able to handle, e.g., a Cortex-A5 (spotted in dap info 1) at all? Creating a target with cortex_a, I have seen -rc1 and --enable-target64 differ in the number of breakpoints (more) and watchpoints (less). In case we do need two different builds to access 32-bit and 64-bit cores, is there some variable that can be checked from target configs to figure out which build it's being run from, to decide which targets to create? More generally, for a multi-core scenario, how do I figure out the -dbgbase address? Is this visible somewhere in the romtable? Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton; HRB 21284 (AG Nürnberg) ------------------------------------------------------------------------------ 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
