this patch - JTAGBv3.patch - it goes on top of what urJTAG? V0.10 or the head from svn or ?
is this the cumulative patch? (does it contain all the changes from the "other" thread)?
After we patch it with this patch, will BBv2 be able to burn its own cpld? (interface=2?)
attm with 0.10 (no patches) if nothing is connected to the bbv2 I get
jtag> cable jtagkey
Connected to libftd2xx driver.
jtag> detect
Warning: TDO seems to be stuck at 0
jtag>
With latest trunk from SVN (UrJTAG 0.10 #1902) it works without a patch:
jtag> cable jtagkey interface=0
Connected to libftd2xx driver.
jtag> detect
discovery.c:117 urj_tap_detect_register_size() Warning: TDO seems to be stuck at 0
Error: chain.c:182 urj_tap_chain_shift_instructions_mode() no error: Part 0 without active instruction
jtag> cable jtagkey interface=1
Connected to libftd2xx driver.
jtag> detect
IR length: 8
Chain length: 1
Device Id: 00000110111000011100000010010011 (0x06E1C093)
Manufacturer: Xilinx (0x093)
Unknown part! (0110111000011100) (/usr/local/share/urjtag/xilinx/PARTS)
jtag> bsdl path /home/arhimed/Dev/BSDL
jtag> detect
IR length: 8
Chain length: 1
Device Id: 00000110111000011100000010010011 (0x06E1C093)
Filename: /home/arhimed/Dev/BSDL/XC2C32A_VQ44.bsdl
jtag> svf /home/arhimed/Dev/BBv2-JTAGkey-v1.1.svf stop progress
Parsing 1210/1212 ( 99%)
Scanned device output matched expected TDO values.
jtag>
I just received it from seeed and I missed on the communication about it so it's being slow catch up
so the question is - should I svf the BBv2-JTAGkey-v1.1.svf.zip from this thread and is the JTAGBv3.patch still relevant as it seems that latest trunk knows how to parse interface ?