2026-01-05 12:48 PM - last edited on 2026-01-06 2:09 AM by Andrew Neil
Hello Forum,
I’m working with a custom display that uses an ST7789V controller (GRAM) connected via FMC and MDMA.
The single framebuffer is located in .RAM2.
The microcontroller is an STM32H750.
The application (the .text section) runs from QSPI flash, while the internal flash contains only the bootloader.
Some widgets (such as TextArea) are rendered correctly, but others (like ToggleButton) appear corrupted.
Additionally, the background image shows horizontal line artifacts.
Please compare the two pictures:
Has anyone experienced similar issues or has suggestions on what might be causing this behavior?
2026-01-05 1:19 PM
The same behavior occurs when using a partial framebuffer located in .RAM2.
Also, L8 compression has no effect on the graphical artifacts — the distortions and horizontal lines remain unchanged.
2026-01-06 2:08 AM
Hello @Andi ,
Could you share your linker file and the map file of your application?
2026-01-06 11:59 AM
2026-01-06 1:33 PM
Hi Osman,
I previously shared the linker script used for the single framebuffer configuration. For the partial framebuffer setup, the linker script might need to be different.
The partial framebuffer is actually my preferred solution, but I also implemented the single framebuffer to compare the behavior and experiment with the graphical artifacts.
Could you please provide example linker scripts for both variants (single framebuffer and partial framebuffer)?
Thanks,
Andi