FTDI Community

Please login or register.

Login with username, password and session length.
Advanced Search  

News:

Welcome to the FTDI Community!

Please read our Welcome Note

Technical Support enquires
please contact the team
@ FTDI Support


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

Pages: 1 2 [3] 4 5 ... 10
 21 
 on: May 29, 2019, 07:37:12 PM 
Started by daboomdigity - Last Post by daboomdigity
Hi,

I am working on evaluating the FT260 for the dual purpose of UART and I2C.  I am currently having issues with with having the device show up in device manager as a COM Port.  The device does show up as a "HID Compliant Device". 

I have installed the latest drivers (v2.12.28) from the FTDI website.  Does the FT260 show up on host as a COM Port?  I have tried the connecting the UMFT260EV1A to both a windows 7 and windows 10 system.


Thanks,


 22 
 on: May 20, 2019, 10:15:26 AM 
Started by SHS - Last Post by FTDI Community
Hello,

I’m not familiar with the product that you are using.  Since this is not one of our products, although it may utilise our device, It is difficult to offer any support on it as FTDI cannot control how the USB ICs are used and has no knowledge of the entire product.

Product Manufacturers are responsible for supporting end-users of their products, so you will need to contact the manufacturer directly.  Please see the following document for reference:
http://www.ftdichip.com/Support/Documents/TechnicalNotes/TN_102_OEM_Technical_Support_Requirements_for_FTDI_Products.pdf.

With that said however, if they are using our default driver then you may want to try using our latest driver v2.12.28, which is available on our website here:

http://www.ftdichip.com/Drivers/D2XX.htm

You can download the setup executable by clicking on this link. Once installed you should be able to plug in your device and the driver will install. Have a look at our Installation guides here http://www.ftdichip.com/Support/Documents/InstallGuides.htm for further information.

I’m sorry I could not be of further assistance.

Regards,
FTDI Community

 23 
 on: May 20, 2019, 12:47:04 AM 
Started by SHS - Last Post by SHS
Hello,

We are using the Windows Multipoint Server 2016 OS and the zero client system.
It is using a board called COEDino on the zero client station.
Repeating the process of connecting and removing a codeino to the Zero Client station results in a "blue screen" on the server.
Can I get Windows Multipoint Server 2016 OS software(driver)?

Thanks.
Best Regards,
Hyunseop Shin

 24 
 on: May 16, 2019, 11:36:54 AM 
Started by Whiffy - Last Post by Whiffy
I am working on a Windows PC based application and having some issues. I have a RS485 cable from FTDI based on the FT232 IC.

In my UWP applications (written in VS 2017) I have the following:

// Create new instance of the FTDI device class
            FTDI myFtdiDevice = new FTDI();

            // Determine the number of FTDI devices connected to the machine
            FTDI_Status = myFtdiDevice.GetNumberOfDevices(ref ftdiDeviceCount);

            if (FTDI_Status == FTDI.FT_STATUS.FT_OK)
            {
                //Check of FTDI cables worked OK

                TxtDisplayTopRow.Text = "FTDI cable check OK";
                TxtDisplayBottomRow.Text = ftdiDeviceCount + " connected";

                // Allocate storage for device info list
                FTDI.FT_DEVICE_INFO_NODE[] ftdiDeviceList = new FTDI.FT_DEVICE_INFO_NODE[ftdiDeviceCount];

                // Populate our device list
                FTDI_Status = myFtdiDevice.GetDeviceList(ftdiDeviceList);
               
                if (FTDI_Status == FTDI.FT_STATUS.FT_OK)
                {
                    // Open first device in our list by serial number
                    FTDI_Status = myFtdiDevice.OpenBySerialNumber(ftdiDeviceList[0].SerialNumber);

                    if (FTDI_Status == FTDI.FT_STATUS.FT_OK)
                    {
                        // Set up device data parameters
                        // Set Baud rate to 9600
                        FTDI_Status = myFtdiDevice.SetBaudRate(9600);
                        if (FTDI_Status == FTDI.FT_STATUS.FT_OK)
                        {
                            // Set data characteristics - Data bits, Stop bits, Parity
                            FTDI_Status = myFtdiDevice.SetDataCharacteristics(FTDI.FT_DATA_BITS.FT_BITS_8, FTDI.FT_STOP_BITS.FT_STOP_BITS_1, FTDI.FT_PARITY.FT_PARITY_NONE);
                            if (FTDI_Status == FTDI.FT_STATUS.FT_OK)
                            {
                                TxtDisplayTopRow.Text = "FTDI cable setup";
                            }
                        }
                    }

                }
            }
            else
            {
                //FTDI check failed
            }

Everything works great until I get to 'GetDeviceList(ftdiDeviceList);', this does return a list of connected devices but all the important properties are blank


I have added the following capabilities to the manifest

<DeviceCapability Name="usb">
      <!--FT232AM, FT232BM, FT232R and FT245R Devices-->
      <Device Id="vidpid:0403 6001">
        <Function Type="name:vendorSpecific" />
      </Device>
      <!--FT2232D and FT2232H Devices-->
      <Device Id="vidpid:0403 6010">
        <Function Type="name:vendorSpecific" />
      </Device>
      <!--FT4232H Device-->
      <Device Id="vidpid:0403 6011">
        <Function Type="name:vendorSpecific" />
      </Device>
      <!--FT232H Device-->
      <Device Id="vidpid:0403 6014">
        <Function Type="name:vendorSpecific" />
      </Device>
      <!--FT-X-Series Devices-->
      <Device Id="vidpid:0403 6015">
        <Function Type="name:vendorSpecific" />
      </Device>
      <!--My Custom Device-->
      <!--<Device Id="vidpid:1234 4321">
      <Function Type="name:vendorSpecific" />
    </Device>-->
    </DeviceCapability>

The version of FTD2XX_NET is: 1.1.0.0

It would be good to know if anyone has successfully used the FTDI cables with UWP and if so what I need to do?

Many thanks


 25 
 on: May 15, 2019, 04:38:16 PM 
Started by Joshwa - Last Post by FTDI Community
Hello,

The issue sounds most likely with LabVIEW.

Note Microsoft stopped all support for Windows XP from April 2014 however LibFT260 has been tested with XP.

We do have some basic LabVIEW examples, but they are very old. Unfortunately we don’t have access to LabVIEW so it’s no longer supported.

Are the results the same on Windows 7 or Windows 10?

Is the correct HID interface being opened?

This was tested on our test PC in the lab. The FT260 was successfully listed and opened using LibFT260:



Note: FT260 is configured as dual channel mode and are listed as interfaces 0 and 1. The successful line of code opens this interface number:

ftStatus = FT260_Open(0, &ft260Handle);

Other HID interfaces may exist on the PC such as mouse, keyboard, etc.

Can you take LabVIEW out of the question for testing purposes, and run the examples provided with LibFT260?

.\LibFT260-v1.1.1\samples

Best Regards,
FTDI Community

 26 
 on: May 15, 2019, 06:04:52 AM 
Started by techtoys - Last Post by techtoys
Hi Administrator

I was just curious what would happen if single brace is changed to triple brace pairs for Ft_Esd_WidgetSlots initialization in original BridgeTek toolchain, an attempt was made by randomly pick s_App_Screen__Slots in the source file AppScreen__generated.c with src code changed as below:

Code: [Select]
static Ft_Esd_WidgetSlots s_AppScreen__Slots = {{{
(void(*)(void *))Ft_Esd_Widget_Initialize,
(void(*)(void *))AppScreen_Start,
(void(*)(void *))Ft_Esd_Widget_Enable,
(void(*)(void *))AppScreen_Update,
(void(*)(void *))Ft_Esd_Widget_Render,
(void(*)(void *))Ft_Esd_Widget_Idle,
(void(*)(void *))Ft_Esd_Widget_Disable,
(void(*)(void *))AppScreen_End,
}}};


There is another way to do it like
Code: [Select]
.Initialize = (void(*)(void *))Ft_Esd_Widget_Initialize but a triple brace pairs is more simple. After this change the warning message [-Wmissing-braces] removed in FT90x GCC toolchain as well. Unfortunately there is no real FT90x hardware with me so I cannot test.

Nevertheless, having changed all single brace to triple brace pairs for Ft_Esd_WidgetSlots I am able to run the WidgetOpacity example on my hardware with ESP32 as seen in this hyperlink.

https://www.dropbox.com/s/vctfsx5jhgcay5a/IMG_20190515_120950_HDR.jpg?dl=0

Touch screen is supported so the opacity of these two widgets can be adjusted by the scroll bars underneath.

This example was finished with ESD -> export to Eclipse project -> manually modification on individual files.
The next step is to modify /Libraries folder in installation directory of ESD so that it is possible to export Eclipse project from ESD for third party MCU.

John


 27 
 on: May 14, 2019, 12:08:25 PM 
Started by techtoys - Last Post by FTDI Community
Hello,

Thank you for your post, I have passed this on to the development team to see if they wish to add any comments.

Best Regards,
FTDI Community

 28 
 on: May 13, 2019, 01:30:32 PM 
Started by Joshwa - Last Post by Joshwa
Hello,

i have Windows XP as O.S. and i am using LabVIEW as programming environment. I am using the LibFT260.dll to interfacing with the development board UMFT260EV1A.

when try to open the communication (either as by index or by Vid and Pid) the STATUS of the request is "Device not found".
The Device is recognized by my O.S. and if i open an USB RAW communication with device and try to request the chip version, the device answers me correctly.

Can you help me and give support for understand and resolve this problem?

Thank you.
Francesco Mancuso

 29 
 on: May 10, 2019, 06:44:05 PM 
Started by techtoys - Last Post by techtoys
Hi

I am trying to port ESD to ESP32 Wifi SoC in addition to FT9xx MCUs. The HAL part is working with a new directory ESP32 in FT_Eve_Hal/Hdr and FT_Eve_Hal/Src with relevant .c and .h files. New compiling directive added to FT_Platform.h as ESP32_PLATFORM, together with a new LCD model of 480*854.

Toolchain is the development framework base on Cygwin GCC in Eclipse IDE. I also tested Cross GCC and it shows to be working too. Language in pure C.

Now I am proceeding further with FT_Esd_Framework by copying all .c and .h files to project and get them compiled.

There is a problem with Ft_Esd_WidgetSlots structure in Ft_Esd_Widget.h. This structure is initialized in almost each of the .c files under /FT_Esd_Framework with individual function pointers. For example, in Ft_Esd_Layout_Tag.c this structure is initialized as follows:

Code: [Select]
static Ft_Esd_WidgetSlots s_Ft_Esd_Layout_Tag__Slots = {
(void(*)(void *))Ft_Esd_Widget_Initialize,
(void(*)(void *))Ft_Esd_Widget_Start,
(void(*)(void *))Ft_Esd_Widget_Enable,
(void(*)(void *))Ft_Esd_Widget_Update,
(void(*)(void *))Ft_Esd_Layout_Tag_Render,
(void(*)(void *))Ft_Esd_Widget_Idle,
(void(*)(void *))Ft_Esd_Widget_Disable,
(void(*)(void *))Ft_Esd_Widget_End,
};

With official Bridgetek FT9xx GCC, this intialization is giving warning as
Code: [Select]
missing braces around initializer [-Wmissing-braces] Ft_Esd_FixedPointNumericLabel__Generated.c /WidgetOpacity/FT_Esd_Widgets line 26 C/C++ Problem

This is a warning but not error.

Unfortunately, the same code with Cygwin GCC/Cross GCC is giving an error with the same message
Code: [Select]
missing braces around initializer [-Wmissing-braces]
Because Ft_Esd_WidgetSlots is a structure composed of a union of an array of 8 elements, should it be 3 braces in initialization like code snippet below instead of a single brace pair ?

Code: [Select]
static Ft_Esd_WidgetSlots s_Ft_Esd_Layout_Display__Slots = {{{
(void(*)(void *))Ft_Esd_Widget_Initialize,
(void(*)(void *))Ft_Esd_Widget_Start,
(void(*)(void *))Ft_Esd_Widget_Enable,
(void(*)(void *))Ft_Esd_Layout_Display_Update,
(void(*)(void *))Ft_Esd_Layout_Display_Render,
(void(*)(void *))Ft_Esd_Layout_Display_Idle,
(void(*)(void *))Ft_Esd_Widget_Disable,
(void(*)(void *))Ft_Esd_Widget_End,
}}};
I tried three braces with my toolchain and it works OK. Does anybody know why is it so? Is it something with compile options to change it?

Hope it is "legal" to port the ESD to a third party MCU as I notice only FT9xx series MCUs are supported for now. But I do realize that porting guide for ESD 4.5 is on the way. I am not sure if my question here worth an answer.

John

 30 
 on: May 07, 2019, 03:41:58 PM 
Started by vinays - Last Post by FTDI Community
Hello,

Please can you contact email support on support1@ftdichip.com with a screenshot of your Configurator settings and we will investigate further.

Regards,
FTDI Community

Pages: 1 2 [3] 4 5 ... 10