NuttX + FB device (SAMA5D2) - rendering problem/tearing about lvgl HOT 6 OPEN

It happend to me when I enbled CONFIG_FB_UPDATE with single framebuffer mode. U can try this #6397. it may help you.

from lvgl.

For completeness here is (nearly) the same spinner in LVGL V8.3.3:

from lvgl.

check your lv_port_disp_init function, has a lv_display_set_buffers... function call, wha't the last param? if LV_DISPLAY_RENDER_MODE_FULL or LV_DISPLAY_RENDER_MODE_DIRECT change it to LV_DISPLAY_RENDER_MODE_PARTIAL

from lvgl.

check your lv_port_disp_init function, has a lv_display_set_buffers... function call, wha't the last param? if LV_DISPLAY_RENDER_MODE_FULL or LV_DISPLAY_RENDER_MODE_DIRECT change it to LV_DISPLAY_RENDER_MODE_PARTIAL

@liyang5945 - if I change this, the display does not update at all unfortunately. The spinner is drawn once but there's then no animation of it.

from lvgl.

It happend to me when I enbled CONFIG_FB_UPDATE with single framebuffer mode. U can try this #6397. it may help you.

@jianglianfang The SAMA5D2 NuttX configurations do not set CONFIG_FB_UPDATE as it is not necessary. If I enable it, the app crashes at the FBIO_UPDATE ioctl code as the fb->vtable entries are NULL.

Since LVGL V8 works OK, in my case, it is not to do with FB_UPDATE but is likely more of a mismatch between the LVGL V9 framebuffer driver implementation and the specifics of the SAM5D2 LCDC peripheral and the NuttX driver for it :-(

from lvgl.

Maybe @XuNeo has some ideas.

from lvgl.