BRT Community

Please login or register.

Login with username, password and session length
Advanced search  

News:

Welcome to the Bridgetek Community!

Please read our Welcome Note

Technical Support enquires
please contact the team @ Bridgetek Support

Please refer to our website for detailed information on all our products - Bridgetek - Bridging Technology

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - EnsAltun

Pages: [1]
1
General Discussion / FT810 White Screen Problem
« on: June 28, 2022, 09:57:57 AM »
Hello,
I have a problem with FT810 graphic controller. I am getting white screen problem in every manufacture. Rate is 6%. Also I am checking all other components, solder paste etc. on circuit but everything seems ok. There is only one solution, that is changing FT810 with a new one.
Firstly i thought there is cold solder joints on pad of ft810 or solderless pads. So i desoldered ft810, cleared all pads and soldered again carefully.
But i get white screen again. Seems FT810 is damaged.
I need to find reason of this problem. Have you every seen this problem before? Do you have any idea why this can be happen?




2
Discussion - EVE / FT810 touch calibration problem
« on: February 23, 2022, 12:29:24 PM »
Hi,
I am using FT810 with 7" TFT. But i use it on portrait orientation. But i have a problem with touch orientation. It doesnt happen always but touch orientation of some devices change.  Seems you see TFT screen on portrait orientation but touch system changes to landscape. Thats why you cant use touch screen. Also i calibrate system once after programming process. Flowchart of algorithm is like below;
Run system first time after programming  -> (System goes to calibration mode because calibration values are zero on mcu eeprom) -> Calibrate screen -> read REG_TOUCH_TRANSFORM_X values and save to mcu eeprom -> reboot system
After rebooting system, mcu will see values on eeprom and FT810 wont be calibrated again. I read calibration values and write to REG_TOUCH_TRANSFORM_X again same values. This system was running without problem. But a few devices get this problem. My calibration code is below. Do you have any idea why i have this problem?


ft800memWrite32(RAM_CMD + cmdOffset, (CMD_DLSTART));                                                                                                                                             
cmdOffset = incCMDOffset(cmdOffset, 4);     
ft800memWrite32(RAM_CMD + cmdOffset, CLEAR_COLOR_RGB(0,255,0));
cmdOffset = incCMDOffset(cmdOffset, 4);       
ft800memWrite32(RAM_CMD + cmdOffset, CLEAR(1,1,1));
cmdOffset = incCMDOffset(cmdOffset, 4);       
   
ft800memWrite32(RAM_CMD + cmdOffset, (CMD_SETROTATE));                                                   
cmdOffset = incCMDOffset(cmdOffset, 4);       
ft800memWrite32(RAM_CMD + cmdOffset, (0));   //rotate screen portrait orientation                                 
cmdOffset = incCMDOffset(cmdOffset, 4);       
   
   
ft800memWrite32(RAM_CMD + cmdOffset,CMD_CALIBRATE); // calibrate screen
cmdOffset = incCMDOffset(cmdOffset, 4);   
ft800memWrite32(RAM_CMD + cmdOffset, DISPLAY());
cmdOffset = incCMDOffset(cmdOffset, 4);       
ft800memWrite32(RAM_CMD + cmdOffset, (CMD_SWAP));
cmdOffset = incCMDOffset(cmdOffset, 4);       
ft800memWrite16(REG_CMD_WRITE, (cmdOffset));
do
{
cmdBufferRd = ft800memRead16(REG_CMD_READ);       
cmdBufferWr = ft800memRead16(REG_CMD_WRITE);
}while (cmdBufferWr != cmdBufferRd);

DEVICE_TRANSFORM_A=ft800memRead32(REG_TOUCH_TRANSFORM_A);  // read calibration values
DEVICE_TRANSFORM_B=ft800memRead32(REG_TOUCH_TRANSFORM_B);
DEVICE_TRANSFORM_C=ft800memRead32(REG_TOUCH_TRANSFORM_C);
DEVICE_TRANSFORM_D=ft800memRead32(REG_TOUCH_TRANSFORM_D);
DEVICE_TRANSFORM_E=ft800memRead32(REG_TOUCH_TRANSFORM_E);
DEVICE_TRANSFORM_F=ft800memRead32(REG_TOUCH_TRANSFORM_F);
           
save_eeprom_transform_values();   // save calibration values to eeprom

Pages: [1]