Hello,
Please ensure the
VNC2 Debugger/Programmer Module drivers have installed correctly.
This can be checked in device manager.
You might want to try a driver uninstall/reinstall. See
FTDI_Driver_Uninstall_with_2-12-28_Install.pdf.
The other thing to do would be to disable the COM port, because the VNC2 uses the D2XX drivers rather than VCP drivers.
This would stop any other software program claiming the COM port without you knowing, which means that the D2XX interface wouldn’t be available.
This can be changed in the EEPROM using
FT_Prog which would make this change permanent.
It can also be done at Windows device manager level, but the option would only exist for that particular installation.
Then ensure that the VNC2 Debugger/Programmer Module is connected to the VNC2 module/device correctly.
Can you also try programming directly within the IDE?
Vinculum/Vinculum-II are very mature products and are no longer supported by R&D and has been superseded by FT9xx.
The best solution we have is our
FT90x MCU.
There are lots of other examples available:
AN_360 FT9xx Example ApplicationsFT90x Software ExamplesFT9xx Software ExamplesThere are significant benefits of FT90x:
-Eclipse based IDE
-Source code for API drivers is provided
-Significant performance improvement
-Actively in development by R&D
-Improved documentation and software examples
We provide
FT9xx Development Modules and a free
FT9xx Toolchain for custom application development.
If you need any further information, please email your local support team:
https://www.ftdichip.com/FTContact.htmBest Regards,
FTDI Community