Hello,

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

The intention in this example is to get the refresh rate at or near 60 fps, but if your display can support higher PCLKs then a higher refresh rate should be possible.

Best Regards,
FTDI Community

Hello,

This is because you were looking to obtain the font metric block data, which is obscured when using the compressed option.

Best Regards,
FTDI Community

Hello,

The Car Dashboard Demo Sheet notes that the LCD Display is WVGA:
https://brtchip.com/Brochures/BT815%20Car%20Dashboard%20Demo%20Sheet.pdf

Best Regards,
FTDI Community

Hello,

This sounds like an issue with EVE Screen Editor, I will pass this onto the development team as there is a new release due out soon.

As for the inbuilt fonts:

• 16-19 - CP437 from the FreeBSD distribution's console
• 20-25 - helvR08, etc from X11
• 26-29 - Roboto Regular

Best Regards,
FTDI Community

Hi Tony,

In the output code file, you should see a definition corresponding to the 'address' field of the font properties. We used Consola here and so your definition may be different.


In the code below we set the start address defined as 1000 and so we got:

#define RAM_FONTS_CONSOLA 1000
static ft_uchar8_t fonts_consola[] = {
   /*('file properties: ', 'resolution ', 16, 'x', 22, 'format ', 'L8', 'stride ', 16)*/0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
[remainder of font data]


Then later at the bottom of the code you should see the following where the code is loaded into RAM_G beginning at location 1000
   Ft_Gpu_Hal_WrMem(phost,RAM_FONTS_CONSOLA, fonts_consola, sizeof(fonts_consola));
   Ft_Gpu_CoCmd_SetFont2(phost,0, 1000, 32);

Does this match what you see?

If you have some screenshots or further information you can also send it to our support address support1@ftdichip.com.

Best Regards, FTDI Community

Hello,

The BT81X should be available by the end of the year.

Best Regards,
FTDI Community

Hi,

You can still update via UART in this case.

Have a look at AN_159 - Vinculum-II Firmware Flash Programming for further information:

https://www.ftdichip.com/Support/Documents/AppNotes/AN_159%20Vinculum-II%20Firmware%20Flash%20Programming.pdf

Regards,
FTDI Community

Hello,

The img_cvt.exe cannot produce ASTC files, we have a upcoming asset convertor which will support this.
And yes, in your situation this is not possible with the FT813.

Best Regards,
FTDI Community