Hello David,
I am not so sure about this. Still smells like reset problem to me.
It should be noted that when I let small bootloader execute from the
SPI flash and do the reset (and some other config), I can attach with
OpenOCD, i.e. chain is well scanned. I was able after attachment to
set-up
> > All these zeroes suggest either a TAP which
> > legitimately has no IDCODE instruction support
> > (and thus looks like IDCODE == 0) ...
> >
> > ... OR else hardware problems somewhere in the
> > JTAG chain, possibly in some other TAP.
> >
>
> Hello David,
> I am not so sure about this. Still
On Tue, Aug 24, 2010 at 11:00 PM, David Brownell wrote:
> jtag_examine_chain_display()
>> 74376: JTAG
>> tap: mico_2.cpu tap/device found: 0x01273043 (mfg: 0x021,
>> part:
>> 0x1273, ver: 0x0)
>> Info : 218 293 core.c:949 jtag_examine_chain_display()
>> 74032: JTAG
>> tap: mico_3.cpu tap/device fo
On Mon, 2010-08-23 at 22:38 +0100, Spencer Oliver wrote:
> On 23/08/2010 22:21, Peter Stuge wrote:
> > Spencer Oliver wrote:
> ST sent me the api, it is based on mass storage device.
> They are happy for openocd to support it.
> >>
> >>> Any chance of a copy of the API?
> >>
> >> The actu
jtag_examine_chain_display()
> 74376: JTAG
> tap: mico_2.cpu tap/device found: 0x01273043 (mfg: 0x021,
> part:
> 0x1273, ver: 0x0)
> Info : 218 293 core.c:949 jtag_examine_chain_display()
> 74032: JTAG
> tap: mico_3.cpu tap/device found: 0x01273043 (mfg: 0x021,
> part:
> 0x1273, ver: 0x0)
> Info :
Hi all,
I have super-simple openocd.cfg :
--
source [find ../tcl/interface/jtagkey2.cfg]
# Processor : ARM946e (wb) rev 0 (v4l)
jtag_rclk 300
jtag_khz 0
scan_chain
--
I.e. I just want to scan my chain in order to take configure
parameters. After that I want to make target for one
