Hello,

All information on the VNC2 tools can be found in AN_151 Vinculum II User Guide:

https://ftdichip.com/wp-content/uploads/2020/08/AN_151_Vinculum-II_User_Guide.pdf

The asm error is a value of >255 being loaded into an 8 bit register.
The ASM file can have line numbers from the original C code inline.
Please check the command line options for VinC.exe:

VinC.exe
VinC [options] [file ...] [-L linker options]

  -E            Run the pre-processor and stop.
  -S            Stop processing after pre-processing and compilation.
  -c            Pre-process, compile and assemble but do not invoke linker.
  -O level      Specify optimisation for compiler.
  -d level      Specify debug output level for compiler.
  -D macro=defn Defines macro with optional defn in preprocessor.
  -U macro      Undefines macro in preprocessor.
  -I dir        Add a search directory for include files.
  -o file       Specify output filename.
  -l file       Specify log filename.
  --save-temps  Save all temporary files.
  --save-temp   Save temporary files: 'a' assembler, 'i' preprocessor,
                'o' object.
  --combine     Combine source files on command line into single input file
                for compiling.
  --library     Create a single output file for all source files on command
                line.
  -v            Verbose output of command lines for tools.
  -q            Quieten output of command lines for tools.
  --version     Display tool version.
  --all-versions        Display all tool versions.
  --max-warn limit      Limit the number of warnings displayed.
  --max-err limit       Limit the number of errors displayed.
  --help        Display this help message.
  -L            Process all following options as linker options.
The bin file can be up to 256 kB - 4 kB.

Best Regards,
FTDI Community

Hello,

Please post any EVE related stuff onto Bridgetek Community:

New Bridgetek Community is now open.
Please note that we have created the Bridgetek Community to discuss all Bridgetek products e.g. EVE, MCU.
Please follow this link and create a new user account to get started.

Bridgetek Community

Best Regards,
FTDI Community

Hello,

We used USBDeview and observe the same behaviour as you.

Then we used a usb analyzer which shows USB enumeration can get the Manufacturer description and Product description.
So we don’t know why USBDeview can not show these two descriptions correctly.

We also used the API “FT260_OpenByProductDescription” to test if we can access the FT260 device after programming the serial number.
The result is OK.

So maybe “USBDeview” has a minor  display error on these two descriptions.

Best Regards,
FTDI Community

Hi xenon68,

sting.h is not FTDI code. it is a standard C language header file that you can include in your project. https://www.tutorialspoint.com/c_standard_library/string_h.htm

You can find information about the strstr function online, this link can help you https://www.tutorialspoint.com/c_standard_library/c_function_strstr.htm#

Best Regards

FTDI Community

Hello,

I had confirmation from our R&D team:

You are correct.
The correct output is 2.60.2.0

We will update the correct code on the next release which is below for your reference:

// Show version information
    DWORD dwChipVersion = 0;

    ftStatus = FT260_GetChipVersion(ft260Handle, &dwChipVersion);
    if (FT260_OK != ftStatus)
    {
        printf("Get chip version Failed, status: %d\n", ftStatus);
    }
    else
    {
        printf("Get chip version OK dwChipVersion=%ld\n",dwChipVersion);
                               
        printf("Chip version : %x.%x.%x.%x\n",
            ((dwChipVersion >> 24) & MASK_1), //  ((dwChipVersion >> 24) & MASK_1),
            ((dwChipVersion >> 16) & MASK_1), //  ((dwChipVersion >> 16) & MASK_1),
            ((dwChipVersion >> 8) & MASK_1), //   ((dwChipVersion >> 8) & MASK_1)
            (dwChipVersion & MASK_1) ); //  (dwChipVersion & MASK_1) );
    }

    DWORD dwLibVersion = 0;
   
    ftStatus =  FT260_GetLibVersion(&dwLibVersion);
    if (FT260_OK != ftStatus)
    {
        printf("FT260_GetLibVersion Failed, status: %d\n", ftStatus);
    }
    else
    {
        printf("FT260_GetLibVersion OK\n");

        printf("dllVersion:%8x\n", dwLibVersion);
    }
Best Regards,
FTDI Community

Hi
FT260 is a HID class device and does not use the standard VCP/D2xx drivers. LibFT260 can be used (or raw HID class commands. See AN_394 and AN_395.
https://ftdichip.com/wp-content/uploads/2021/02/AN_394_User_Guide_for_FT260.pdf
https://ftdichip.com/wp-content/uploads/2020/07/AN_395_User_Guide_for_LibFT260.pdf

Regards
FTDI Community 

Hi ffred,

You should test using the sample code provided in the library download before you start writing your own. Just to verify it is all working properly. Let me know how it goes.

Best Regards

FTDI Community