On Mon, Nov 14, 2011 at 11:46 PM, James Zhao wrote:
> Nvm I think I figured it out, it is just the debug base address was wrong. I
> had two boards which I thought was the exact same, but turns out they are not.
> So when I went from one board to the other it starts to fail.
Good to hear :-) The
: Monday, November 14, 2011 1:30 PM
To: James Zhao
Cc: [email protected]
Subject: Re: [OpenOCD-devel] CoreSight compatibility
On Mon, Nov 14, 2011 at 7:38 PM, James Zhao wrote:
> Thanks for the tips, but the delay and power does not seem to be
> causing the STICKERR.
Hello
On Mon, Nov 14, 2011 at 7:38 PM, James Zhao wrote:
> Thanks for the tips, but the delay and power does not seem to be causing the
> STICKERR.
Hello James :-) Quick greping the sources showed where to look for answers:
target/arm_adi_v5.c: * CoreSight(tm) v1.0 Architecture Specification
Thanks for the tips, but the delay and power does not seem to be causing
the STICKERR.
On Sun, Nov 13, 2011 at 4:16 AM, CeDeROM wrote:
> On Sat, Nov 12, 2011 at 2:17 AM, James Zhao wrote:
> > Just wondering is OpenOCD suppose to be CoreSight compatible, cause I am
> > running it on a chip with
On Sat, Nov 12, 2011 at 2:17 AM, James Zhao wrote:
> Just wondering is OpenOCD suppose to be CoreSight compatible, cause I am
> running it on a chip with CoreSight and getting random STICKYERR.
According to ADIv5.0 specification (ARM IHI 0031A) section 3.1.1.
STICKYERR might set when debug domain
On Sat, Nov 12, 2011 at 2:17 AM, James Zhao wrote:
> Just wondering is OpenOCD suppose to be CoreSight compatible, cause I am
> running it on a chip with CoreSight and getting random STICKYERR.
Might be compatible, but does not support sticky flags handling (yet).
This needs to be done in order t
Just wondering is OpenOCD suppose to be CoreSight compatible, cause I am
running it on a chip with CoreSight and getting random STICKYERR.
--
James H.T. Zhao
--
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http
