On Sat, Jan 18, 2014 at 11:19 AM, Paul Fertser <[email protected]> wrote:

> On Sat, Jan 18, 2014 at 10:56:13AM +0400, Paul Fertser wrote:
> > BTW, can you clarify what targets have you tested on a BE machine? I
> > think those fixes worth mentioning in the news too.
>

I mainly rewrote and tested the MEM-AP routines used by Cortex-M (and in
some cases Cortex-A, depending on the memory access method). Those *should*
be solid now.

IIRC I also tried an ARM7TDMI target which failed miserably.


> On a related note, do I understand it right that
> http://openocd.zylin.com/#/c/1782/ should be abandoned as all the
> issues were already fixed on a higher layer? Can we assume both
> Cortex-A and Cortex-M are now usable on BE hosts?
>

The issues should be/was fixed on *lower* layers, I think (MEM-AP).

I'm pretty sure Cortex-A have issues when using the APB-AP method, since
there are patches that try to fix it. I haven't tried it myself as I have
no Cortex-A hardware readily available.

This patch would be good to merge but currently have issues:
http://openocd.zylin.com/1781


> If you have any suggestions for me about reviewing some particular
> patch, I'm all ears and willing to help.
>
>
I know Salvador Arroyo has quite a few MIPS improvement changes that sadly
haven't got any attention. I have no MIPS knowledge myself so if someone
can check the patches from a MIPS perspective, I can assist with some
general code review.

Other than that I'm not sure. I haven't browsed through the old changes in
a while.

/Andreas
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today. 
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to