Title: NEW White screen information?
Post by: WD8BXS on 25. December 2020, 13:23:37
Hello Everyone!
I had written the Thaoyu people about the white displays. Here is what they said:
Your driver must use a low-speed clock to be fully compatible with HY28B. Otherwise some can work and some can't work.
The A version is the slowest. The D version is the fastest. So the timing of the operation of your LCD driver must be done in accordance with the A version. In addition, the D version must also use the new initialization code. I will attach a new initialization code later.
This is compatible with all 2.8 LCDs. (The timing mentioned above refers to the address setup time/address hold time of the i8080 bus, and the data setup time/data hold time. Different MCU settings are different. You can modify this part of the timing.)
This is not a problem. do not worry. Your initialization code is the earliest. There's an BUG. Please use the new initialization code updates.
DeviceCode = LCD_ReadReg(0x0000); /* read LCD ID */
/* recognition different screen, use different Initialization */
if( DeviceCode == 0x9325 || DeviceCode == 0x9328 )
{
LCD_Code = ILI9325;
LCD_WriteReg(0xE5, 0x78F0); /* set SRAM internal timing */
LCD_WriteReg(0x01, 0x0100); /* set Driver Output Control */
LCD_WriteReg(0x02, 0x0700); /* set 1 line inversion */
LCD_WriteReg(0x03, 0x1030); /* set GRAM write direction and BGR=1 */
LCD_WriteReg(0x04, 0x0000); /* Resize register */
LCD_WriteReg(0x08, 0x0207); /* set the back porch and front porch */
LCD_WriteReg(0x09, 0x0000); /* set non-display area refresh cycle ISC[3:0] */
LCD_WriteReg(0x0A, 0x0000); /* FMARK function */
LCD_WriteReg(0x0C, 0x0000); /* RGB interface setting */
LCD_WriteReg(0x0D, 0x0000); /* Frame marker Position */
LCD_WriteReg(0x0F, 0x0000); /* RGB interface polarity */
/*************Power On sequence ****************/
LCD_WriteReg(0x10, 0x0000); /* SAP, BT[3:0], AP, DSTB, SLP, STB */
LCD_WriteReg(0x11, 0x0007); /* DC1[2:0], DC0[2:0], VC[2:0] */
LCD_WriteReg(0x12, 0x0000); /* VREG1OUT voltage */
LCD_WriteReg(0x13, 0x0000); /* VDV[4:0] for VCOM amplitude */
LCD_WriteReg(0x07, 0x0001);
delay_ms(200);
/* Dis-charge capacitor power voltage */
LCD_WriteReg(0x10, 0x1090); /* SAP, BT[3:0], AP, DSTB, SLP, STB */
LCD_WriteReg(0x11, 0x0227); /* Set DC1[2:0], DC0[2:0], VC[2:0] */
delay_ms(50); /* Delay 50ms */
LCD_WriteReg(0x12, 0x001F);
delay_ms(50); /* Delay 50ms */
LCD_WriteReg(0x13, 0x1500); /* VDV[4:0] for VCOM amplitude */
LCD_WriteReg(0x29, 0x0027); /* 04 VCM[5:0] for VCOMH */
LCD_WriteReg(0x2B, 0x000D); /* Set Frame Rate */
delay_ms(50); /* Delay 50ms */
LCD_WriteReg(0x20, 0x0000); /* GRAM horizontal Address */
LCD_WriteReg(0x21, 0x0000); /* GRAM Vertical Address */
/* ----------- Adjust the Gamma Curve ---------- */
LCD_WriteReg(0x30, 0x0000);
LCD_WriteReg(0x31, 0x0707);
LCD_WriteReg(0x32, 0x0307);
LCD_WriteReg(0x35, 0x0200);
LCD_WriteReg(0x36, 0x0008);
LCD_WriteReg(0x37, 0x0004);
LCD_WriteReg(0x38, 0x0000);
LCD_WriteReg(0x39, 0x0707);
LCD_WriteReg(0x3C, 0x0002);
LCD_WriteReg(0x3D, 0x1D04);
/* ------------------ Set GRAM area --------------- */
LCD_WriteReg(0x50, 0x0000); /* Horizontal GRAM Start Address */
LCD_WriteReg(0x51, 0x00EF); /* Horizontal GRAM End Address */
LCD_WriteReg(0x52, 0x0000); /* Vertical GRAM Start Address */
LCD_WriteReg(0x53, 0x013F); /* Vertical GRAM Start Address */
LCD_WriteReg(0x60, 0xA700); /* Gate Scan Line */
LCD_WriteReg(0x61, 0x0001); /* NDL,VLE, REV */
LCD_WriteReg(0x6A, 0x0000); /* set scrolling line */
/* -------------- Partial Display Control --------- */
LCD_WriteReg(0x80, 0x0000);
LCD_WriteReg(0x81, 0x0000);
LCD_WriteReg(0x82, 0x0000);
LCD_WriteReg(0x83, 0x0000);
LCD_WriteReg(0x84, 0x0000);
LCD_WriteReg(0x85, 0x0000);
/* -------------- Panel Control ------------------- */
LCD_WriteReg(0x90, 0x0010);
LCD_WriteReg(0x92, 0x0600);
LCD_WriteReg(0x07, 0x0133); /* 262K color and display ON */
}
I have no idea what they are talking about but you fellows who know the code might know .
Possibly this is a fix for the issue.
Merry Christmas,
Chuck Vy 73, WD8BXS
|
Title: Re:NEW White screen information?
Post by: DF8OE on 25. December 2020, 13:32:17
Hi Chuck,
are you talking about SPI or parallel mode?
vy 73
Andreas |
Title: Re:NEW White screen information?
Post by: WD8BXS on 25. December 2020, 17:11:23
It is SPI, for the MCHF 6.3 Version.
Thanks
Chuck |
Title: Re:NEW White screen information?
Post by: DF8OE on 25. December 2020, 18:36:53
I know the file you have attached and I have tested it - it was 2...3 years ago. It has not made any (good) difference to the one we use. I have elaborated the best configuration for all modes and all useable speeds.
For using HY28B with mcHF/UHSDR there is a minimum speed from MCU to LCD to transfer all "live data" (waterfall, scope) in realtime. So I think your LCD does fail the neccessary minimum speed limitation. We have noticed that there were more and more LCDs which do not work with speed we must use since around 3 years. So we swapped LCD to a more reliable type (it has 3.2" size)...
vy 73
Andreas |
Title: Re:NEW White screen information?
Post by: WD8BXS on 26. December 2020, 00:47:42
Yes, I am aware of the new larger LCD, but that is not really an option here.
I am just forwarding this information from the manufacturer.
I had a bad display that turns white after an hour or so.
I think it is defective, but they tell me it is me fault for the code error, hihi
What they will go through just so they don't have to replace a display, ihi
Thanks,
Chuck |
Title: Re:NEW White screen information?
Post by: DF8OE on 26. December 2020, 08:16:31
Hi Chuck,
it is defective from your point of view, bcause it does not met the speed grade you must have.
"Only a code fault" it is if you can reduce speed (as you got a "low speed grade" LCD). But that is not easy possible in mcHF... We have worked hard to get waterfall and scope like they are today and this is only possible at a higher speed the lowest versions of the LCD offer.
vy 73
Andreas |
Diskussions- und Newsboard des DARC-Ortsverbandes I40 | Powered by YaBB SE
© 2001-2003, YaBB SE Dev Team. All Rights Reserved.
|