Problem: JTAG_CLIENT.DLL missing, DE0_Nano_ControlPanel on Windows 8.1, Quartus II 14

Dave:

Your constraints.tcl script is a huge time-saver. It must have taken a few hours to put it together.

Ok, after reviewing your script and the Pin Planner tool I can see how your script defined the pins (because everything matches). However, I have a follow-on question: how do you distinguish in your script the difference between input and output pins? Specifically, I'm looking at the script for the accel_csN and accel_int pins (as an example):

set pin(accel_csN) {PIN = G5, IOSTD = "3.3-V LVTTL", DRIVE = "MAXIMUM CURRENT", SLEW = 2}

set pin(accel_int) {PIN = M2, IOSTD = "3.3-V LVTTL", DRIVE = "MAXIMUM CURRENT", SLEW = 2}

The Pin Planner shows accel_csN as an output, while accel_int is an input, yet your script appears to define them identically. (The adc_xxx pins show a similar trait, for example.)

How is the direction (input, output, or bidir) actually specified in the script? What did I miss?

Thanks,

Dave