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

Show Posts

You can view here all posts made by this member. Note that you can only see posts made in areas to which you currently have access.

Messages - FTDI Community

Pages: [1] 2 3 ... 13
1
Hello,

These functions are specifically for MAC OS and Linux.

You are right, FT_GetVIDPID has been deprecated.

FT_SetVIDPID can be used to set multiple custom VID/PID combinations which need to use the FTDI driver.

Best Regards,
FTDI Community

2
Discussion - Hardware / Re: BT81x to support 1366*768 LCD?
« on: January 17, 2019, 10:42:45 AM »
Hello

Using BT81x @ 72MHz system clock, it is possible to achieve 30Hz refresh rate for a 1366x768 display, less than the standard 60Hz.
 
In case the display supports Adaptive Frame Rate(AFR) operation, then it’s possible to get 60Hz refresh rate by set REG_PCLK=1. If AFR is not supported (for LVDS display), the display list shall be less complicated, similar to the performance achieved by our 10” HD demo at Electronica 2018 (1280x800 60Hz).
 
The EVE series of ICs do not include a frame buffer, they dynamically clock out each computed pixel on the screen. A displays size and what the Pixel Clock is running at will determine the achievable performance. It is also worth noting using larger displays reduces the computational time available for each pixel on the screen.

If we take the example from the following WQVGA settings:
Code: [Select]
    // WQVGA display parameters
   lcdWidth   = 800;                                                            // Active width of LCD display
   lcdHeight  = 480;                                                            // Active height of LCD display
   lcdHcycle  = 928;                                                            // Total number of clocks per line
   lcdHoffset = 88;                                                             // Start of active line
   lcdHsync0  = 0;                                                               // Start of horizontal sync pulse
   lcdHsync1  = 48;                                                            // End of horizontal sync pulse
   lcdVcycle  = 525;                                                           // Total number of lines per screen
   lcdVoffset = 32;                                                            // Start of active screen
   lcdVsync0  = 0;                                                              // Start of vertical sync pulse
   lcdVsync1  = 3;                                                              // End of vertical sync pulse
   lcdPclk    = 2;                                                                  // Pixel Clock
   lcdSwizzle = 0;                                                              // Define RGB output pins
   lcdPclkpol = 1;                                                              // Define active edge of PCLK
 
             

HCYCLE = 928
VCYCLE = 525
VCYCLE * HCYCLE  = 487,200

Note: REG_PCLK is using the value 2 which will divide the clock down to 30Mhz.

Result = 30,000,000/487,200 = ~ 61 fps

Best Regards,
FTDI Community

3
Hello,

There are two status bytes sent at the start of every packet (covered by NDA) when using FT245 Synchronous FIFO mode. Thus each packet only contains 510 data bytes, and two status bytes making up the 512 byte buffer.

Best Regards,
FTDI Community

4
Hello,

All of the available FT312D documentation can be found at the following:
https://www.ftdichip.com/Products/ICs/FT312D.html

Best Regards,
FTDI Community

5
Discussion - Software / Re: FT_Prog on Windows 10
« on: January 08, 2019, 09:59:55 AM »
Hello,

It has been found that some other HID-class devices (some MCU debug and in-circuit emulator pods for MCUs are USB HID class for example) can cause an FT_Prog exception when it scans for HID-class FT260 devices. The development team are currently investigating but in the meantime we would advise to check for other USB devices such as debuggers (a USB keyboard and mouse should be fine) and to try un-plugging these when using FT_Prog.

Best Regards, FTDI Community

6
Discussion - Software / Re: labview programs for ft232h device.
« on: January 07, 2019, 04:14:05 PM »
Hello,

Our LabVIEW examples were created using LabVIEW 7.1.  In order to maximise the number of developers who can run these examples the code has been saved for previous versions using the "Save for Previous" option from the File menu.  However, LabVIEW 7.1 only allows the code to be saved for the last version i.e. LabVIEW 7.0.
FTDI have access only to version 7.1 at this time and so can only provide examples compatible with LabVIEW 7.0 and 7.1.

For support for LABVIEW2018 you will need to create your own VIs.

Regards,
FTDI Community



7
Hello,

Please see our GPIO software examples provided with the library download:

.\LibFT4222-v1.4.2\samples

Unfortunately we don't have any LabVIEW examples for FT4222H.

I would recommend testing out our C programming GPIO example before continuing with LabVIEW.

Please ensure that you are using the latest LibFT4222 version (currently v1.4.2 for Windows).

If you have any further questions, you can contact us on support1@ftdichip.com.

Best Regards,
FTDI Community

8
Discussion - Software / Re: BT815 Image Issue
« on: December 12, 2018, 01:33:16 PM »
Hello,

If you are using a custom hardware design, can I get you to email this into the support channel at support1@ftdichip.com ?
Please also summate the issues being experienced, any applicable code/images and any debugging you may have already carried out.

Best Regards,
FTDI Community.

9
Hello,

Apologies the email address is support1@ftdichip.com.

Thanks,
FTDI Community

10
Discussion - Software / Re: BT815 Image Issue
« on: December 11, 2018, 04:34:51 PM »
Hello,

Can you just clarify which of the two displays you are using is exhibiting this issue? and can you link the datasheet? Also are you using a custom hardware design or our modules?

Best Regards,
FTDI Community

11
Discussion - Software / Re: BT815 Image Issue
« on: December 11, 2018, 11:08:47 AM »
Hello,

Can I get you to use the EVE Asset Builder to convert your images using the BT81X specific functionality:
https://www.ftdichip.com/Support/Utilities.htm#EVE%20Asset%20Manager
Once completed, please let me now if the results are the same.

I don't believe this issue is related to these resistors, although can you clarify if you are using our Development Modules or a custom hardware design?

You should ensure that your display setting for the 4.3" display are correct.

Best Regards,
FTDI Community

12
Hi,

Thanks for getting back. It looks like my previous message was cut short.

What I meant to say was please contact private support with a screenshot of your FT60X chip Configurator Programmer. You can contact private support on suport1@ftdichip.com.

Regards,
FTDI Community.

13
Hello,

Please may I ask you to have a look at AN_379 - D3XX Programmers Guide, which is available here:

https://www.ftdichip.com/Support/Documents/ProgramGuides/AN_379%20D3xx%20Programmers%20Guide.pdf

This should provide some further information on the functions and help with your question.

If you are still having problems please may I ask you to contact email support with a screenshot of your

Regards,
FTDI Community

14
Hello,

You can find details on threads and resources in these application notes below and you can use the Thread Manager to check usage.

https://www.ftdichip.com/Support/Documents/AppNotes/AN_169_Vinculum_II_RTOS_Using_the_Kernel_Diagnostic_Service.pdf

https://www.ftdichip.com/Support/Documents/AppNotes/AN_157_Vinculum%20II%20Memory%20Management.pdf


Best Regards, FTDI Community



15
Hello,

The controllers in some flash drives don't commit a file fully to their flash array correctly unless you do either a dummy open-close operation (i.e. finish data, close, open and close) or call fat_fileFlush(). If you see the file but the content isn't there, then one of these should help.

Best Regards, FTDI Community

Pages: [1] 2 3 ... 13