Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LVGL Version #2461

Closed
TimJTi opened this issue Aug 5, 2024 · 6 comments · Fixed by #2592
Closed

LVGL Version #2461

TimJTi opened this issue Aug 5, 2024 · 6 comments · Fixed by #2592

Comments

@TimJTi
Copy link
Contributor

TimJTi commented Aug 5, 2024

Summary

NuttX Apps needs to be upgraded to the newly released V9.2 to solve framebuffer render issues.

Background

As discussed here the LVGL version "bundled" with NuttX apps (v9.1) has issues with what I perceive as its misuse of the NuttX framebuffer; it makes multiple partial renders direct to the framebuffer, resulting in visible artefacts. It is deemed OK as there are some architectures/boards where this is OK because it seems they natively have two framebuffers. But - to me - it is the exception not the rule.

V9.2 now auto-detects the presence of that second native framebuffer and if its not there creates its own render buffer. It works but is perhaps a bit arcane.

NB - there is no support for an LVGL partial render buffer in the LVGL NuttX framebuffer driver, so there will be two whole frame buffers present: the /dev/fb0 buffer and LVGLs render buffer.

Other

While investigating this I needed to work with other versions of LVGL and found the following.

  1. NuttX "fixes" the LVGL version.
  2. If you clone LVGL direct to the appropriate NuttX apps directory you can use any version you like. This could perhaps be added to documentation, or:
    1a. Enable Kconfig configuration of the wanted LVGL version. Not sure this works if you need to work with LVGL master as there will be no release archive that can be downloaded.
  3. BUT the side effect of this that NuttX apps takes a direct copy of LVGLs Kconfig from the "fixed"/"approved" version of a given NuttX apps release and this requires a manual copy if the non-approved version's Kconfig file. This has been discussed before but surely there's a way to work around this - perhaps a warning if the version is edited to something other than the "supported" version?

Discuss :-)

@acassis
Copy link
Contributor

acassis commented Sep 19, 2024

maybe @XuNeo could help us here!

@xiaoxiang781216 what should be the next approach for this case?

@xiaoxiang781216
Copy link
Contributor

is lvgl 9.2 released?

@cederom
Copy link

cederom commented Sep 19, 2024

is lvgl 9.2 released?

Yes official release is ready :-) https://github.com/lvgl/lvgl/releases/tag/v9.2.0

@XuNeo
Copy link
Contributor

XuNeo commented Sep 20, 2024

perhaps a warning if the version is edited to something other than the "supported" version?

Will add in lvgl/lvgl#6789

@cederom
Copy link

cederom commented Oct 6, 2024

Okay lets wait for LVGL 9.2.1 release, verify it, and add to NuttX 12.7.0 release, so far testing on 12.7.0-RC0 failed see apache/nuttx#13825 and apache/nuttx#13839.

@cederom
Copy link

cederom commented Oct 18, 2024

Okay the LVGL release/v9.2 branch is here and this will contain 9.2.1 release code that is 99% ready we can proceed :-)

https://github.com/lvgl/lvgl/tree/release/v9.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants