Forum Discussion

Altera_Forum's avatar
Altera_Forum
Icon for Honored Contributor rankHonored Contributor
11 years ago

DE1 FPGA FTDI conflict with other devices

I'm doing remote communication of the Altera DE1 FPGA board and another instrument (Thor Labs TDC001 controller for motorized stages). I'm using MATLAB for the remote communication. When either the DE1 or the TDC001 is connected to the computer alone (in the absence of the other device), all my communication works great and I'm able to do remote communication.

However, when both devices are connected to the computer, there seems to be a conflict and I am no longer able to do communication for either device. Both the DE1 and TDC001 use FTDI protocols for their communication, and I've noted some previous discussion of conflict with Altera FPGA boards with other devices that use FTDI (see, for instance, point 1 here http://www.taoli.ece.ufl.edu/teaching/4744/labs/lab2/driver-conflict.pdf (https://ucmail.uc.edu/owa/redir.aspx?c=pooiyksxsuuneyjfx4imfvd7wk0j89ei7_oyixcfmeo0zzslazcej3awdnsvrkixctdw9gags1s.&url=http%3a%2f%2fwww.taoli.ece.ufl.edu%2fteaching%2f4744%2flabs%2flab2%2fdriver-conflict.pdf) or from the Altera forum http://www.alteraforum.com/forum/showthread.php?t=2015 ). These problems are solved by altering the 'ftdibus.sys' file, but I don't seem to have that file in my drivers. I am able to locate the usbblst.inf file, although it is in a folder labeled 'altera' and not 'quartus' (I was only able to load the usb-blast drivers from disc for some reason).

I was wondering if there was a similar hack that I could use to resolve the FTDI conflict for the DE1, and what file equivalent to ftdibus.sys would I need to rename? Any help would be most appreciated.

2 Replies

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    11 years ago

    You don't mention what software tools you're trying to use as part of your 'communication'. However, the Altera tools support multiple 'USB-Blasters' (this includes dev kits such as yours) allowing you to specify which one to use for each application. On the command line you'd typically add a "--cable" option to do so. E.g. 

    nios2-terminal.exe --cable="USB-Blaster "

    The USB-Blaster on the DE1-SoC kit I currently have connected appears as "DE-SoC [USB-1]" - your board may appear as something similar.

    Failing that there is a utility that FTDI offer that allows you to reprogram the EEPROM inside an FTDI device. note: this carries risks in that, if not careful, you could render your hardware unreachable.

    Read about and download the utility from here: ftdi - ft_prog (http://www.ftdichip.com/support/utilities.htm#ft_prog)

    This could allow you to change the identity of one of your FTDI devices such that whatever software you're using doesn't consider it a valid device to use. You may well (almost certainly) have to make a complementary change to whatever software you're using to communicate with this FTDI device with the altered ID. disclaimer - I've not done this part myself but have successfully used the FT_PROG utility to reprogram and use FTDI devices for communications.

    Happy New Year,

    Alex