Paul,
I think I found the patch to fix my issue. I had two issues in fact. The
first issue was the wrong -dbgbase <address>. For SAMA5D36 it should be
-dbgbase 0x80010000. The second issue turned out to be off-by-one on
register reads. E.g. reading 0xFFFF_FC24 returned the value in 0xFFFF_FC20,
the real value for 0xFFFF_FC24 shows up when reading 0xFFFF_FC28, and so
on. This patch, http://openocd.zylin.com/#/c/2299/2/src/target/cortex_a.c,cm,
fixed that problem.
Thanks for the help. Much appreciated.
- Mark
On Fri, Jan 2, 2015 at 12:20 PM, Paul Fertser <[email protected]> wrote:
> Hello,
>
> On Fri, Jan 02, 2015 at 12:00:25PM -0500, Mark Odell wrote:
> > I'm having a hard time getting OpenOCD to work with the Atmel SAMA5D36
> (Cortex
> > A5) and I'd like to try the very latest dev. version of OpenOCD since
> there are
> > some cortex_a.c patches I don't have on my pull. How to go about getting
> this?
> > E.g. what do I git clone?
>
> The master branch is the latest and is the one you already have. You
> might want to cherry-pick some of the in-review patches from
>
> http://openocd.zylin.com/#/q/status:open+message:cortex,n,z
>
> Other than that, I'm afraid, there's no code to support Cortex-A5
> better. Volunteers are welcome, of course.
>
> --
> 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
