Ugh... I'm not sure how it happened, or why, but in the Eagle files I modified, pin 15 of the XC2C32A was _labeled_ 1.8V, but the net's name was +5V, which of course doesn't exist anywhere else on this PCB. I bet if I jumper pin 15 to the 1.8V coming from the FT2232H, all will be well... (trying to program the CPLD, when doing a detect I'd get a War ning: TDO seems to be stuck at 1, and if I'd short it to ground, I'd get the same warning, but stuck at 0).
<sigh...> I _swear_ I tried interface=0, interface=1, and interface=2, and concluded that it's looking for 1 and 2, not 0 and 1.... Thanks for the quick reply!
Hello! For various reasons, I made my own version of the bus blaster, and I'm about 95% sure I started with 2v7. I think I started with that because at the time it was the most recent version... Anyway, I'm having trouble figuring out how to properly configure my FT2232H chip. I'm not exactly sure how I did it, but by using FTDI's FT_PROG I was able to configure it in such a way that I can use the modified version of UrJTAG (v11) to recognize interface=2. I can type "cable ft2232 interface=1", but that doesn't help me for programming the on board xylinx CPLD. If I type "cable ft2232 interface=2" I get "Error: usbconn/libftd2xx.c:406 usbconn_ftd2xx_common_open() ftdi/ftd2xx error: Unable to open TFDI device: device not found"
Any suggestions? I think I might have to assemble a second board minus the CPLD, and jumper port 1 of the 'other' board to port 2 of the first board, just so I can get the CPLD programmed...