FTDI Community

Please login or register.

Login with username, password and session length.
Advanced Search  


Welcome to the FTDI Community!

Please read our Welcome Note

Technical Support enquires
please contact the team
@ FTDI Support

Pages: [1] 2 3 ... 10
 on: August 17, 2018, 01:29:31 PM 
Started by ilya79 - Last Post by FTDI Community

Please can you contact email support on support1@ftdichip.com and we will look into this, the outcome of which we will post here.

FTDI Community

 on: August 16, 2018, 01:57:18 PM 
Started by alexeiko - Last Post by FTDI Community
Hi Alexei,

I'm afraid that each individual port on the device can only be opened once / with one handle. As you mentioned any further attempts whilst already open will fail.

One thing you could consider is to have a 'routing' process open which talks to the port and then pass any data to this from any other processes and it can send to the device, and vice versa for reading. That way there is only one process opening the port.

Best Regards, FTDI Community

 on: August 16, 2018, 10:51:14 AM 
Started by alexeiko - Last Post by alexeiko
Hi, All!

I'm using FT4232 for JTAG and I2C protocols. I want to ask how is it possible to access same device from a couple of different processes in windows?
I initialize channel A to MPSSE and obtain a handle for it. In another process I want to have the ability to work with this channel (already initialized). The problem is that I can't FT_Open a device which is already opened. Is there any way to obtain a handle in the new process (without first closing the device in the other process) ?

Thanks a lot!


 on: August 16, 2018, 10:50:31 AM 
Started by ilya79 - Last Post by ilya79
Hi!  FT601datasheet (table 4.2 FIFO Bus AC timing) points that in worst case slave drive sata set up time is 3 ns. In AN_421 document (FIFO Bus Master for FT60x application note) on page 19, in timing constraints this parameter is set to 6 ns (TIMEGRP "M_FIFO_IO" OFFSET = IN 6 ns VALID 6.5 ns BEFORE "CLK" RISING).  What value is correct ?     

 on: August 13, 2018, 07:47:59 PM 
Started by Hihilintu - Last Post by Hihilintu

My colleague contacted the FTDI support via email. We are working on the same project.

We would like to program the VNC2 flash using an MCU which is on the same PCB. End users do not have the VNC2 debug module.
What we would like to know is how to make the connection between the MCU and VNC2 and see example code how to program the flash.

Some of our customers have had problems when the VNC2 has "lost" its firmware and they had to send us the PCB for reprogramming. It would be very beneficial for all of us if the MCU could reprogram the VNC2 flash.

In short, we would like to use our MCU as the VNC2 debug module.

 on: August 13, 2018, 05:01:40 PM 
Started by Hihilintu - Last Post by FTDI Community

I believe you also contacted email support with the same issue. Please continue to correspond via that support channel and we will post the resolution here.

FTDI Community.

 on: August 13, 2018, 01:34:02 PM 
Started by Hihilintu - Last Post by Hihilintu

I am currently using Vinculum VNC2 chip to make PC keyboard to command XMEGA controller. With sample code "USB HID to SPI Master Sample Application ROM" it is working very well. But there has been a problem that Vinculum does forget it's firmware sometimes (luckily very rarely).

It would be great to use XMEGA to re-program the chip if the problem persists on field and user has no separate programmer device. I just cant find any documentation how to interface the chip to program it.


 on: August 13, 2018, 01:14:04 PM 
Started by forcetronics - Last Post by FTDI Community

Can you just clarify which product you are using?

Best Regards,
FTDI Community

 on: August 13, 2018, 11:51:42 AM 
Started by White_Fox - Last Post by White_Fox
After several attempts, I got new error messages. The message above does not seems to be triggered by 32/64bit-problem. I appreciated this cause most hints relating to this message suggest this.

I started a new project (now with MinGW) and add the sample-path in libMPSSE "LibMPSSE-SPI\samples\SPI\SPI" to the directory (project property in Netbeans IDE), also the linker path. Headerfiles are included from here.
Now the compiler returns:
cd 'I:\Documents\NetBeansProjects\GettingStartedMPSSE2'
C:\MinGW\msys\1.0\bin\make.exe -f Makefile CONF=Debug
"/C/MinGW/msys/1.0/bin/make.exe" -f nbproject/Makefile-Debug.mk QMAKE= SUBPROJECTS= .build-conf
make.exe[1]: Entering directory `/i/Documents/NetBeansProjects/GettingStartedMPSSE2'
"/C/MinGW/msys/1.0/bin/make.exe"  -f nbproject/Makefile-Debug.mk dist/Debug/MinGW-Windows/gettingstartedmpsse2.exe
make.exe[2]: Entering directory `/i/Documents/NetBeansProjects/GettingStartedMPSSE2'
mkdir -p build/Debug/MinGW-Windows
rm -f "build/Debug/MinGW-Windows/main.o.d"
gcc -m32   -c -g -I/I/C-Bibliotheken/LibMPSSE-SPI/samples/SPI/SPI -include /I/C-Bibliotheken/LibMPSSE-SPI/samples/SPI/SPI/WinTypes.h -include /I/C-Bibliotheken/LibMPSSE-SPI/samples/SPI/SPI/ftd2xx.h -include /I/C-Bibliotheken/LibMPSSE-SPI/samples/SPI/SPI/libMPSSE_spi.h -MMD -MP -MF "build/Debug/MinGW-Windows/main.o.d" -o build/Debug/MinGW-Windows/main.o main.c
In file included from <command-line>:32:0:
i:/C-Bibliotheken/LibMPSSE-SPI/samples/SPI/SPI/ftd2xx.h:259:20: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'FT_Open'
i:/C-Bibliotheken/LibMPSSE-SPI/samples/SPI/SPI/ftd2xx.h:265:20: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'FT_OpenEx'
i:/C-Bibliotheken/LibMPSSE-SPI/samples/SPI/SPI/ftd2xx.h:272:20: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'FT_ListDevices'
i:/C-Bibliotheken/LibMPSSE-SPI/samples/SPI/SPI/ftd2xx.h:279:20: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'FT_Close'
i:/C-Bibliotheken/LibMPSSE-SPI/samples/SPI/SPI/ftd2xx.h:284:20: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'FT_Read'
i:/C-Bibliotheken/LibMPSSE-SPI/samples/SPI/SPI/ftd2xx.h:292:20: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'FT_Write'
i:/C-Bibliotheken/LibMPSSE-SPI/samples/SPI/SPI/ftd2xx.h:300:20: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'FT_IoCtl'
...more errors, deleted cause post lenght

make.exe[2]: *** [build/Debug/MinGW-Windows/main.o] Error 1
make.exe[2]: Leaving directory `/i/Documents/NetBeansProjects/GettingStartedMPSSE2'
make.exe[1]: *** [.build-conf] Error 2
make.exe[1]: Leaving directory `/i/Documents/NetBeansProjects/GettingStartedMPSSE2'
make.exe": *** [.build-impl] Error 2

BUILD FAILED (exit value 2, total time: 20s)

The errors are linked to ftd2xx.h. If I follow the error links, I can find that:
#ifdef __cplusplus //<-- This is line no. 253
extern "C" {

      FT_STATUS WINAPI FT_Open( //<- This is red marked, line no. 259
      int deviceNumber,
      FT_HANDLE *pHandle

      FT_STATUS WINAPI FT_OpenEx( //<- This is red marked, line no. 265
      PVOID pArg1,
      DWORD Flags,
      FT_HANDLE *pHandle

      FT_STATUS WINAPI FT_ListDevices( //<- This is red marked, line no. 271
      PVOID pArg1,
      PVOID pArg2,
      DWORD Flags

Please, has anyone an idea what is missing or why the build fails? I don't think that there is a '=' missing, but what else is going wrong?

 on: August 13, 2018, 05:48:55 AM 
Started by Daniel123 - Last Post by Daniel123
yes I see that. But this doesn't answer my question. How exactly do I set up my C# implementation to run isochronous transfer?
Calling ReadPipe unfortunately will only do Bulk transfers...?

Pages: [1] 2 3 ... 10