Skip to main content ↑ ↓
Topic: wrong channel on impact for busblaster?! (Read 2090 times) previous topic - next topic

wrong channel on impact for busblaster?!

Hi,
still struggling how to program the FPGA board. Since i wasn't sucessfull using urJTAG, I thought I give Xilinx "impact" and the open source Linux drivers a chance.
It seems the drivers and hence the cable gets recognized. However, performing a "Initialize chain" ends up showing me a single device xc2c32a instead of two devices (one should be xc5vlx30).

I somehow feel the scan used the wrong port of the FTDI FT2232C Dual chip and hence showing me the CPLD used by the busblaster.

Can someone confirm this or tell me how to change the channel?

Re: wrong channel on impact for busblaster?!

Reply #1 –
Ok found it...
in the users home folder should be a file (if not create it)
.libusb-driverrc

Code: [Select]
# Copy this file to ~/.libusb-driverrc if you want to use FTDI2232 cables
# All parallel ports not defined in this file are mapped to real ports on the
# system

# Amontec Jtagkey
LPT2 = FTDI:0403:cff8
# Dangerous Prototypes Bus Blaster v2
LPT3 = FTDI:0403:6010:1

The trick is the last digit 1 stays for channel 1 and hence the external connected JTAG devices use a 2 to address the CPLD on the busblaster.

Re: wrong channel on impact for busblaster?!

Reply #2 –
Real nice torwag! I believe this was easier than urJTAG?

Re: wrong channel on impact for busblaster?!

Reply #3 –
Not exactly easier but more sucessfull..

with urJTAG I had to fight with ftdi_sio vs. ftd2XX drivers... as soon as this was sort out it worked rather nice. However, I was not able to flash the xc16fp memory successful. Something between the conversion of the MCS file from Xilinx to an SVF file and calling it went wrong.
I tried it in many several way.
Also later after installing  the Xilinx drivers I even having the correct chain and everything the converted SVF files failed.

Via impact and the opensource drivers it worked out however as already said here, its very very slow.
Ideally, I want to use urJTAG but still can't get it working.

If there is interest I can write down my findings to far in the wiki... esp. the impact Xilinx part with the open drivers... just to add it here already, its still working with the actual Xilinx webpack (14.2) even the drivers do not claim support for this version.

Re: wrong channel on impact for busblaster?!

Reply #4 –
please share any notes on the alternate driver and impact, it is not a very well developed part of the documentation.

Is it painfully slow?
Got a question? Please ask in the forum for the fastest answers.

Re: wrong channel on impact for busblaster?!

Reply #5 –
Yup ;) As soon as I get it round up I will add it to the wiki....
in sum,
impact 14.2 + open source drivers + busblaster works but is very slow
still struggel with the SVF conversion and usage of urjtag.
urjtag might work under Linux under both ftdi modules need to test this too...