Quartus 14.1 pollutes 13.0 project

[Altera_Forum]

I'm targeting an EPM3064ATC44-10N. I updated to Quartus 14.1 and it said this part is no longer supported. 

 I opened the project with the 13.0 version that has been working. I can no longer program my part.  Clicking 'Start' in the programmer yields:"Unable to scan device chain..."  Running 'Test JTAG Chain' in the JTAG Chain Debugger yields:!Error: JTAG chain problem detected !Error: The TDI connection to the first detected device EPM(3064A|7064AE) might be shorted to VCC or is an open circuit !Error: The TCK and TMS connections to the device before the first detected device EPM(3064A|7064AE) might have a problem !Info: Detected 1 device(s) !Info: Device 1: EPM(3064A|7064AE)   Device name UNKNOWN_170640DD already exists  If I google the 'Device name UNKNOWN...', I get:    CAUSE:  You attempted to define a user-defined device; however, the device name is used by an existing device. Each user-defined device must have a unique device name.    ACTION:  Click ok to close the message dialog box, and then change the device name.     I think opening the project with Quartus 14.1 changed something in my project. I can't be sure, but it sure looks like it. I need to do something to make Quartus 13.0 work again with my project since this is the last version that supports my target. If I delete everything but the RTL and the .qpf, the project does not compile.  Thanks! Todd

[Altera_Forum]

You need to keep the '.qsf' (Quartus Settins File) as well as the rtl and '.qpf'. Then you should be able to re-compile the project. 

 I'm surprised trying to simply open it in Q14.1 broke the project. In Quartus 13.0, can you 'Auto Detect' the JTAG chain from the programmer? This should report what devices the programmer can find. You can do this without even opening your project - which is why I'm a little surprised...  Cheers, Alex

[Altera_Forum]

The error you are receiving is more directly related to the USB blaster driver than the Quartus II Project. I'm wondering if the USB Blaster driver was updated when you install 14.1 and now there is something incompatible with 13.0 when it tries to talk to it? 

 I'm assuming you are running the Windows version of Quartus?  Pete

[Altera_Forum]

Thanks Alex! 

 I am running the Windows version. Pete, I think you are right.  The project recompiled after deleting all but the .qsf, .qpf, and the RTL. I still can't program the device.  I can run it all around JTAG states in the 'JTAG Chain Debugging'. (At least the the icons light up blue in the 'TAP state' pane. Clicking on 'Test JTAG Chain' still yields: Device name UNKNOWN_170640DD already exists.  I looked at all the JTAG signals with a scope. They all look reasonable - able to go up and down at the chip. The TDI signal looks a little funny. It goes low quickly and meanders high slowly. I stuck another pull-up on it temporarily and it still didn't pull up any faster.   I tried multiple target boards. They all do the same thing.  In 'Hardware Setup', it finds my USB-Blaster [USB-0].  I tried another USB-Blaster. I rebooted my computer.   Assuming it's the USB-Blaster driver update for 14.1, how can I downgrade the driver to the 13.0 version?

[Altera_Forum]

I'm running the Linux version of Quartus, so I can't give you the exact path, or instructions, but if you go to your device manager, you should be able to find the USB blaster under USB devices, then modify the driver by pointing it to the one in the quartus 13.0 installation directory. 

 I think it's in the ../13.0/quartus/drivers directory. But again it's been awhile.  For Windows 7.0 just right click on "Computer" and select "Properties", "Device Manager".  Then under USB devices, expand it and find the USB Blaster, Right Click on it, select "Properties" and hit the "Drivers" Tab, then click on "Update Driver" and follow the prompts. Make sure you direct it to the 13.0 installation driver directory.  For Windows 8.x you need to search for "Device Manager" But I avoid 8.x, so your are more on your own there..   Pete

[Altera_Forum]

You might also try installing the latest Quartus and use it only for programming. That might be quicker than trying to debug what is going on with your setup.

[Altera_Forum]

I had four bad boards in a row. That led me down the path of thinking the problem was with Quartus. All's well now! 

 I appreciate the help very much