> -----Original Message----- > From: Andreas Färber [mailto:[email protected]] > Sent: Wednesday, April 29, 2015 11:39 AM > To: David Ung; [email protected] > Cc: Ellis, Duane > Subject: AArch64 testing (Re: [OpenOCD-devel] [PATCH]: af683cc aarch64: > Correct target state for hardware step) > > 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?
I believe that should work, did you try that other dap - ie dap info 0? All the processor should show up as "Type is 0x15, Debug Logic, Processor" > Creating a target with cortex_a, I have seen -rc1 and --enable-target64 differ > in the number of breakpoints (more) and watchpoints (less). For now the print out on number of breakpoint from arm_dpm_setup() is wrong for a 64bit target. But that's just the print, running openocd with -d, I can see it get configured properly. Info : 262 608 arm_dpm.c:1165 arm_dpm_setup(): cpu0: hardware has 1 breakpoints, 2 watchpoints Debug: 263 608 aarch64.c:2308 aarch64_examine_first(): Configured 6 hw breakpoints > 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? I am hoping we won't need this. If we do, there must be a bug and should be fixed. The 64bit builds with --enable-target64 should ideally work for 32bits. I don't think there is such a variable, though one can introduce it if needed. > > More generally, for a multi-core scenario, how do I figure out the -dbgbase > address? Is this visible somewhere in the romtable? See comment above about David ----------------------------------------------------------------------------------- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. ----------------------------------------------------------------------------------- ------------------------------------------------------------------------------ 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
