A HINT ABOUT ENVIRONMENTAL VARIABLES IDENTIFIES ONE CAUSE
I had previously installed the 22.0 version of Quartus Prime (the current one), then deinstalled it in order to install 17.0. The uninstaller failed to remove the old environmental variables pointing at 22.0 locations. The installer for 17.0 failed to correct that, leaving me with variables pointing to a nonexistent directory.
Repairing those directories improved things, in that the behavior of the second TCL script which appeared to work earlier now generates many more messages about actions it has taken, indicating that it works better. Alas, the third (pin map) script still fails and the TCL installation still is missing the relevant packages necessary to proceed further.
DOING AN UNINSTALL WITH CLOSE INSPECTION AFTERWARDS
Did an uninstall of Quartus and found I still had two other related products. I kept hunting for uninstallers until the directory was empty. I was left with the Arm design studio after exhausting all the Intel provided uninstallers. I used the Windows control panel to do that uninstall. The last step was to locate and delete the environmental variables that were left in the system.
RERUN THE SCRIPT
Completely clean, the Quartus toolkit exhibited EXACTLY the same error as before. It is possible that this is a consequence of the inevitable screwing around that vendors do with every release of their software, causing something that worked fine, say, in release 16.0 to fail in 17.0 because of the changes.
Sadly, Intel has pulled 16.0 such that, even though there are still devices (Cyclone V and the Terasic boards) which are supported by the release, they won't even offer it for 'as is' download. If this is the problem, I am not seeing signs of it from web searches.
No comments:
Post a Comment