Your browser does not allow scripts
Please click here to view a static table of contents without scripts
Problems upgrading to the latest D2XX driver
Return to Introduction  Previous page  Next page
Upgrading the D2XX library can cause problems, such as a reported bug fix does not appear to be fixed. This is most likely related to the application executable pointing to a previous version of the library.

To determine which D2XX library your application is using perform the following steps (examples in brackets assume you have copied all of the files to the desktop and successfully compiled the samples as described in the Samples section):

·Open a Terminal window (Go > Applications > Utilities > Terminal).  

·Change directory to the application executable folder (cd Desktop/D2XX/Samples/Simple)  

·Use otool to determine the library path (otool -L simple). The following text is an example of what is displayed  
   /usr/local/lib/libftd2xx.0.1.0.dylib (compatibility version 0.1.0, current version 0.1.0)  
   /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 88.1.6)  

·As illustrated the, simple application is pointing to libftd2xx.0.1.0.dylib.  

·To alter the library so that the simple sample points to use the install_name_tool (e.g install_name_tool -change /usr/local/lib/libftd2xx.0.1.0.dylib /usr/local/lib/libftd2xx.dylib simple). Please note you may need to change user mode to perform this function depending on the file permissions set on the executable.  

·Run the otool (illustrated in step 3 above) to confirm that the library pointed to by the application has changed and is correct.