Hello,

The use of an LVDS adapter turns out isn't relevant to your question, it just happened that the demo used an LCD panel with an LVDS interface and not an RGB interface.

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 possible to run the BT81x at higher resolutions, but this will result in a slower refresh rate for the screen.

If we take a working 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 (assuming system clock of 60Mhz).

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


Best Regards,
BRT Community

Hello,

Sorry, what is your question? Are you looking for the HD Demo source or?

Best Regards,
BRT Community

Hello,

You can have a look at section 7 of the following application note which covers loading PNGs and inflating images:
https://brtchip.com/wp-content/uploads/Support/Documentation/Application_Notes/ICs/EVE/BRT_AN_014_FT81X_Simple_PIC_Library_Examples.pdf

Best Regards,
FTDI Community

Hi,

Thanks for your update on the issue and it's great to hear that you resolved it.

Best Regards,
BRT Community

Hi,

You can find an example of a chart with pinch-zoom and scrolling at this link below. The ESD does not currently support this but you can do it in your code as shown:
https://brtchip.com/wp-content/uploads/EVE_Projects/FT_App_Graph.zip

As you mentioned, you can calculate the points to be made visible when displaying and create a line-strip. Reducing the number of points down from 100,000 is necessary both due to the screen having only 800 pixels width and also as the display list is limited in size and you require a vertex instruction per visible point (plus any other items such as titles, scales etc.)

Hopefully this example above will help,

Best Regards, BRT Community

Hello,

You can have a look at the example in section 7.3 of the following application note, this makes use of the GET_PROPS command which can be used to establish the starting point for the next image in RAM_G.
https://brtchip.com/wp-content/uploads/Support/Documentation/Application_Notes/ICs/EVE/BRT_AN_014_FT81X_Simple_PIC_Library_Examples.pdf

Best Regards,
FTDI Community

Hello,


Just to double check are you following the initialization sequence as described in section 2.3 of the datasheet?
https://brtchip.com/wp-content/uploads/Support/Documentation/Programming_Guides/ICs/EVE/FT81X_Series_Programmer_Guide.pdf

Best Regards,
BRT Community

Hi,

We're pleased that you found the issue and have resolved it.

Just a few points to note if anyone else sees colour-dependent issues:

• This is often related to display settings and so check your display's RGB timings/polarity/PCLK rate in the display datasheet
• Check the Swizzle setting in case your board uses the RGB lines in a different order (Swizzle allows you to set various options for bit order and R/G/B colour order on the RGB pins to make PCB layout easier)
  
• If displaying bitmaps/images check that you have set COLOR_RGB to 255/255/255 before displaying the image as other colour settings will have a similar effect to looking at the image through coloured glass.

 Best Regards, BRT Community