FT812 settings and connections

[marke]

Any ideas??

[mynos]

Solved the problem FT812-STM32 ?

[marke]

No, too hard at present with insufficient time.

[uros.cvetinovic]

Hi,

For some reason, FT813 doesn't work with touch panel on internal oscillator.

I have reported this to our software developers.
This will be fixed as soon as possible.

The touch panel actually works with the external oscillator,
so in the meantime you can try to solder 12MHz crystal SMD, along with two 22 pF capacitors.
And change the source of the clock in the VisualTFT to external oscillator, and everything should work.

Best regards,

Uros

[mynos]

Hi Uros,

also for FT812 resistive?

Best regards,
Vadiliano

[mynos]

Hi Uros,

thank you for the help, I confirm that with external 12MHz oscillator and n°2 18pF capacitors the touch works on my Riverdi 5" F812 resistive display. So I think it works with FT813 capacitive display too.
It's a little hard to solder manually smd components (because we should start a production of about 500-600 devices with this display per year, and we are not equipped for smd work).
Hoping MikroE solves the problems with library.

I profit by this thread to ask about RGB output bits on VisualTFT.
Verifying FT81x datasheet, FT810/1 has a RGB output of 6 bits (18 bit total), FT812/3 has a RGB output of 8 bits (24 bit total). Datasheet reports that if used lower RGB output, colors are lowers/differents and drawings/images with less precision.
VisualTFT (in "TFT" tab, "RGB Color" panel of settings) allows "RGB Out bits" from 0 to 6. This "6" corresponds to RGB output bits mentioned in datasheet? Should it be 8, not 6? or it is a different things for example the RGB codify RGB666 or 565 etc etc?
Because I saw that EveButton (that use shading of colors) has corrupted colors on display and not good to see and use.
I solved that modifying manually the xml file of VisualTFT and changing from 6 to 8:

Code: Select all

<TFT_PARAMETERS>
   ...
   <OUT_BITS_RED>8</OUT_BITS_RED>
   <OUT_BITS_GREEN>8</OUT_BITS_GREEN>
   <OUT_BITS_BLUE>8</OUT_BITS_BLUE>
   ...
</TFT_PARAMETERS>

even if in Visual TFT settings the dropdown lists still show 0-6 values.
Is there a correspondance?

And another question, in "...driver.c" file I have this structure, composed by Visual TFT settings:

Code: Select all

const TFT812Display VTFT_FT812_CONFIG_DISPLAY =
{
  30000000,        // Frequency          = main clock frequency
  0,               // OutRenderMode      = 0 normal, 1 write, 2 read
  0,               // RenderReadScanLine = scanline for read render mode
  0,               // RenderWriteTrigger = trigger for write render mode (read only)
  928,             // hCycle             = number if horizontal cycles for display
  88,              // hOffset            = horizontal offset from starting signal
  800,             // hSize              = width resolution
  40,              // hSync0             = hsync falls
  48,              // hSync1             = hsync rise
  525,             // vCycle             = number of vertical cycles for display
  32,              // vOffset            = vertical offset from start signal
  480,             // vSize              = height resolution
  13,              // vSync0             = vsync falls
  3,               // vSync1             = vsync rise
  0,               // Rotate             = rotate display
  0x01B6,          // OutBits            = output bits resolution
  0,               // OutDither          = output number of bits
  0x0000,          // OutSwizzle         = output swizzle
  0,               // OutCSpread         = output clock spread enable
  0,               // PClockPolarity     = clock polarity: 0 - rising edge, 1 - falling edge
  1,               // PClock             = clock prescaler of FT812: - 0 means disable and >0 means 48MHz/pclock
};

"OutBits" parameter is 0x1B6 that corresponds to 110110110 = 666 of RGB ... is it different to 8 that I changed in xml file?
And what are OutDither and OutSwizzle parameters?

Thanks for help.
Vadiliano

[uros.cvetinovic]

Hi Vadiliano,

I am sorry for my late respond.
You are right about FT813/FT813 that has a RGB output of 8 bits, it will be corrected as soon as possible.

You can check table for swizzle register here on page 27., and dither on 41.
http://www.ftdichip.com/Support/Documen ... _FT81x.pdf

Best regards,

Uros

[mynos]

Thank you Uros.
Finally in these days I solved all my problems with FT812/3 ... oscillator/library problem, also the problem of the strange "refresh" effect on display (because by default VisualTFT uses 250Hz as PWM, but in FT81x the range is 250-10000Hz and with low values as 250Hz with dark colors or low backlight the display present an ugly refresh effect).
I also found good values for V/H Sync Offest Cycle.

Now I only hope MikroE update the FT812 library to work with internal oscillator, otherwise I'll need to solder manually SMD components on all display (300-400 each lot)

[uros.cvetinovic]

Hi Vadiliano,

I am glad you managed to solve everything.

As for the internal oscillator issue, Our developers are working on this.
It will be corrected as soon as possible.

Best regards,

Uros

[uros.cvetinovic]

Hi,

We have corrected touch screen + internal oscillator problem,
and updated FT812 libraries on the libstock.
So now FT812 and FT813 should work on internal oscillator without problem.

Best regards,

Uros

[dibor]

Hi mynos.
I see you have big experience with this LCD.
What right setting for FT812???
I have EVE2 800x480 LCD and can not to run it.
Using MikroC for AVR and got only black screen
Please give me print screen of your TFT setting.

Best Wishes.

[dibor]

Hi ALL.
DO not get any answer
So, find some info and as result LCD is works now.
Here my settings, maybe will help to somebody

My_EVE2_settings.PNG (28.2 KiB) Viewed 3937 times

[petar.suknjaja]

Thank you dibor for sharing this.
Kind regards,
Petar