On Feb 17, 2009, at 7:57 AM, Holger Schurig wrote:
On Tuesday 17 February 2009 14:34:02 Holger Schurig wrote:jtag newtap $_CHIPNAME cpu \ -irlen 5 \ -ircapture 0x1 \ -irmask 0xf \ -expected-id $_CPUTAPIDI found the bsdl file: http://www.avr32.ru/AP7000.bsdl In this file I find "attribute INSTRUCTION_LENGTH of AP7000: entity is 5;", so I guess I should use "-irlen 5".
Yes.
However, the openocd.pdf file is confusing while describing -ircapture and -irmask. Is -ircapture the JTAG opcode for the IDCODE command? Then 0x01 would be correct. However, openocd.pdf says "the ID code capture command". Not sure what this means.
Yes -ircapture is the value to scan into the IR to make the DR be the IDCODE.
The same for "-irmask". openocd.pdf says "the corresponding mask for the ir register". That's quite elaborate. A mask for what? For what will it be used? Is it a mask for the result of the IDCODE command? Then probably it will used to mask away silicon version, right?
It's a mask for the IR. If the size of the IR is 5, then the maximum value for this is 0x1f. For some devices, there are bits in the IR that aren't used. This lets you mask them off when doing comparisons. In general, this should just be all 1s for the size of the IR.
The next thing that puzzles me is the boundary len. The BSDL file says "attribute BOUNDARY_LENGTH of AP7000: entity is 388", but I don't really know where to specify this.
OpenOCD doesn't directly support boundary scans. You can manually do IR and DR scans, but the internals have no knowledge of boundary scans.
_______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
-- Rick Altherr kc8...@kc8apf.net"He said he hadn't had a byte in three days. I had a short, so I split it with him."
-- Unsigned
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
