driver-conflict - were made . Solution #2: A quick...

Info iconThis preview shows page 1. Sign up to view the full content.

View Full Document Right Arrow Icon
Windows FTDI USB/Altera Byte Blaster Driver Issue: The problem occurs because both the FTDI chip and the USB Byte Blaster are recognized by Windows as the same USB to serial converter which creates a conflict where Windows will only activate one or the other,whichever happens to be plugged first. Solution #1: Go to the quartus/drivers/usb-blaster/x32 (or x64, according to your OS) directory, and rename the ftdibus.sys to something else (anything.sys). Then open usbblst.inf and change all references to ftdibus.sys with the name of the new file. .. In our case anything.sys. With the USB blaster connected uninstall it and uninstall its driver, then plug out the USB Blaster. Plug the USB Blaster back in and install the driver again from the folder in which the changes
Background image of page 1
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: were made . Solution #2: A quick temporary fix is to plug the ByteBlaster in first so Windows uses the FTDI driver for the ByteBlaster. Then plug in the USB plug to power the board and you should be able to program your CPLD. To run the board, you first have to disconnect the ByteBlaster (and sometimes re-plug the USB) before trying to run your board per the usual manner. Solution #3: Add the power header to the 6812 board and use an external power supply while programming the CPLD. You have to be careful to ensure that USB power and external power are never both applied orit may blow your USB port on your PC. i.e. always program w/external power only and always run yourboard (program execution) with USB power only. Never both at the same time....
View Full Document

This note was uploaded on 11/13/2011 for the course EEL 4744c taught by Professor Staff during the Fall '09 term at University of Florida.

Ask a homework question - tutors are online