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:
    // 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

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

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

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.

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

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.

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