Re: [OpenOCD-devel] apq8064 target

[Paul F. <fer...@gm...>]

Hi,

On Tue, May 27, 2014 at 01:40:59PM +0000, Jiri Kastner wrote:
> jtag newtap apq8064 dap -expected-id 0x4ba00477 -irlen 4
> jtag newtap apq8064 cpu -expected-id 0x207100e1 -irlen 11
> 
> target create apq8064.cpu cortex_a -chain-position apq8064.dap -coreid 0
> 
> jtag_rclk 8

Please try without RCLK first.

> Info : JTAG tap: apq8064.dap tap/device found: 0x4ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x4)
> Info : JTAG tap: apq8064.cpu tap/device found: 0x207100e1 (mfg: 0x070, part: 0x0710, ver: 0x2)
> Info : apq8064.cpu: hardware has 6 breakpoints, 4 watchpoints

Hm, the config says target is apq8064.dap but here we see apq8064.cpu
is examined, how comes? Were you trying both taps actually, was the
result the same?

> even i'm not able to get state of target, i can get output from dap info:
...

That looks good to me.

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fer...@gm...