I assembled a makeshift cable and tried it out. Everything is working 100%, things are a bit faster than usual but I suppose I will have to get used to that :D
Thank you very much for getting to the bottom of this, it is very much appreciated!
I finally got some time to look at this issue again.
In order to verify my setup I invested in a Flyswatter.
. Linux 64 bit, 12.04 LTS . Latest SVN of urjtag . Make sure usbserial.ko will not load. . Configured urjtag: ./configure --without-ftd2xx . Connected to my target using the Flyswatter all good, chain detected.
Note: I could not get the urjtag to properly detect my target if I used the official ftd2xx (1.2) library.
Started investigating the Bus Blaster again.
. Compiled some libftdi examples, verified that I could read out the correct chip type on the BB V3 . Created a cable suitable for my target . Connected all together still get:
> cable ft2232 pid=0x6010 vid=0x403 interface=0 > detect warning: TDO seems to be stuck at 1
. Installed the SVF file (bbv3.zip) that Will posted in the previous thread, same result.
Questions: . Is the BB V3 compatible with the V2 ? . What is the correct bitstream to use for the V3 board ? . If the BB is JTAGKey or KT-Link compatible why does it have to be detected as a generic ft2232 ? . When will you create a proper package for BB V3 like the one which exists for V2 ?
[quote author="tayken"]I thought the only difference was board placement but after checking out the schematics, I saw that some connections have changed. There should be a bitstream in the forum that Ian published. I'll have to check it out later as it's getting pretty late here.[/quote]
Thank you very much, I'll wait for Ian's reply to make sure I program the correct bitstream.