Bienvenido a los foros de FT81x Manía. Te invitamos a regístrate totalmente gratis. Disfruta de tu experiencia con un grandes amigos y Staff.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

Thread Contributor: RndMnkIIIRepositorio libreria GD2UB e instrucciones instalación

Please @ raufjay  see this link;

I have attached files modified with FT800 and without external EEPROM for calibration screen.
HOWTO for 1 step
Still it is getting stuck immediate after calibration. Have you tried with STM32F103 ?
For calibration you will need an external eeprom. Have examples of it. I modify in previous link library without calibration code.
Better response on post RE: Repositorio libreria GD2UB e instrucciones instalaciónI understand about the calibration. When I was using Arduino Nano, I used AT328P's eeprom to store the calibration data, and were recalling it on every startup.
The problem is just after calibraiton, the program stuck. Does not move. I have tried two STM32F103C8T6 and STM32F103CBT6. With direct attaching the cable. With new library what you sent in attachement. It still goes for touch calibration, and in FT800 after pressing he first point, the 2nd point does not appear. In FT811, all 3 points appear one by one, but on 3rd point when i touch it stuck there.

Which Arduino IDE you are using? I mean which version ? I have 1.8.2. Which one you have?
Hi @ raufjay   Wink

My IDE Arduino is 1.8.3, windows and Linux working fine. (I'm using the new 1.8.4, no problem)

With Arduino no problem, use the library EEPROM.h, with STM32Fxxx we have to use a special function and the solution to put a simple EEPROM type 24C32, for example using a DS3231 etc. module.

Use only 24 bit our screen, so uncheck this function in the file GD2UB.cpp.

Everything we have controlled and just skip to upload the examples but you have to have this simple EEPROM.

Being in very big steps move forward to put more than 40 examples with images included with microSD or SDIO and animation or video fully working ... You wait and see how beautiful these screens are

You have patience and see in a few days our work for everyone to enjoy.

Angel Angel Angel
Better response on post RE: Repositorio libreria GD2UB e instrucciones instalaciónConnect a DS3231 RTC, in order to get access to the EEPROM onboard

VCC     3V3
SDA     PB7
SCL     PB6

I see that the sketch wait to store inside of the EEPROM all the calibration acquired, for this reason the screen is freeze. 


Another observation, inside of variant.h, located at this path:


The calling of the led on board show it PB1, must be PC13

Function por calibration EEPROM external type 24C32 file GD2UB.cpp;

Better response on post RE: Repositorio libreria GD2UB e instrucciones instalaciónHello again,
Thank you for all your efforts and help.
I tried with the files you attached in your last mail. I got the FT811 5" 800x600 display working now. But unfortunately FT800 4.3" 480x272 display is still not showing up the way it should.
I will try this out with dS3231 module with 4kbyte 24c32 eeprom. I have one module around in one of my boxes.
The PB1 and PC13 mismatch in variant.h is also an important clue. I will try to adjust that as well.
I will try it with 1.8.4 IDE.
Have you got some more examples?
I really appreciate your help.
Great work.

What about using STM32 internal flash in EEPROM simulation module and store the touch calibration data in STM32 Flash?
Better response on post RE: Repositorio libreria GD2UB e instrucciones instalaciónWow! It´s alive!

The vector of calibration has 24 or 25 registers. Those vector is stored inside the external EEPROM. The flash emulation is not a good idea, because it reduce the RAM of the MCU. But you can experiment with that option and tell us about of it.

The EEPROM external of the DS3231 it is a good place to store the calibration vector. In order to use the EEPROm  of the DS3231, only you need install a breakout in PB6/PB7, and feed it with GND/3V3. That's it. Do not change anything inside of the GD2UB library.

The F103C8 it´s a good learning MCU, but it has some instabilities and few pins to grow. In other words "lots of head pains"

My personal suggestion is to get a F407VE MCU, like this:

This MCU it is like "a rock": good stability, lot of pins to grow. 

As we say in my country: "bueno-bonito-barato"

PD: of course we have a lot of examples, give us some time to share those, in order to increase you knowledge about this amazing screens and MCU's. Remember It's a work in progress. In the mean time, try with the attachment example

Attached Files
.zip (Size: 3.21 KB / Downloads: 5)

Forum Jump:

Users browsing this thread: 1 Guest(s)