Hello, i hava got a problem with full scrren size controls. Sometimes, there will be a flash line end of the controls. What i suppose to do with this problem?

[Dd.21]

Box

 

ContainerButton

[MM..1]

Here is more possible fails. LTDC framebuffer error in config, Porch data for LCD . Source images converting problem when 565 used...

[Dd.21]

Thank you for your answer. Sorry, but this really puzzles me. if it is a framebuffer or porch data problem, shouldn't all similar scenarios go wrong? And, I used RGB888 configuration in TouchGFX Designer.

[MM..1]

As i write source images format no screen, then when you use png 565 for screen 888. But you have this on color box too then format isnt source.

Have your LCD internal framebuffer or you use video mode? single or double buffer?...? Get full info about your config help solve your trouble...

[Dd.21]

This is my LTDC init code. The problem is not always here. Once this problem occurs next to a control that has had a problem, then all the control that has the problem will have this problem again. Is it possible that something is wrong with the screen itself？

[MM..1]

320x360x3=345600 and your FBStartAddr is 300k in SRAM , you dont get info how STM you use, Where is your FB ???

[Dd.21]

I used RAM for FB. Start Addr = 0x2004b000, len = 0x200a000 (340k). How STM I used? Sorry, I dont understand.:face_with_tears_of_joy:

When I touch the screen in a certain way, this line will go out, so I think there may be something wrong with the screen.

[MM..1]

WTF  len = 0x200a000 (340k) ???

STM32XXXX ??? internal ram over 600k ???

[Dd.21]

https://www.st.com/en/microcontrollers-microprocessors/stm32l4r9-s9.html

[MM..1]

OK SRAM3, but len = 0x200a000 is bad

How method you use to reserve framebuffer memory?

Now seems stack or heap data overwrites your end bytes in FB