[BUG] LVGL display demo error
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- c
- Domain
- computer-graphics, embedded-iot
Research direction
Start by reproducing the LVGL demo on Linux with NuttX 12.4 and inspect lv_port_fbdev.c, the fb0 device, and the reported 1024×768 RGB32 configuration. Compare the framebuffer format, stride, length, and displayed output; done means identifying a reproducible cause and documenting or validating the required correction.
Written by the indexing model from the issue text.
Description
Description / Steps to reproduce the issue
When I use the LVGL demo, there is a display issue. The fb0 can be found under the device directory and the screen lights up. In the LVGL configuration, fb0 is correctly set to be enabled by default, and the display works. However, there is an issue where the screen shows a repeated image and the colors are incorrect. I have seen similar issues on other forums, but no correct solution has been provided. What could be the cause of this problem? The version of LVGL being used is 8.3.2.
step1 :
The device is registered under the device directory using the video component, and fb0 can be found and detected.
step2:The parameters passed to lv_port_fbdev.c are exactly the same as I have set. The resolution is 1024 * 768, the color format is FB_FMT_RGB32, the bpp is set to 32, fblen is set to 1024 * 32 / 8 * 768, and the stride is set to 1024 * 32 / 8.
step3: run the demo；
On which OS does this issue occur?
[OS: Linux]
What is the version of your OS?
Ubuntu22.04
NuttX Version
releases/12.4
Issue Architecture
[Arch: arm64]
Issue Area
[Area: Graphics]
Verification
- I have verified before submitting the report.
- Dominant language
- C
- Stars
- 465
- Forks
- 782
- Avg merge
- 3d 11h
- Merged PRs (30d)
- 44
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from apache/nuttx-apps
-
Type: Enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
apache/nuttx-apps#3620 · 5 comments · 1 reaction ·
-
Type: Bug
Difficulty 4/5 3-5 days Newbie friendliness 52/100
apache/nuttx-apps#3634 · 1 comment ·
-
apache/nuttx-apps#3436 · 1 assignee ·
-
[FEATURE/SECURITY/BUG] Add hash key validation to check the files downloaded from external projects OpenType: Bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
apache/nuttx-apps#3418 ·
-
Type: Bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
apache/nuttx-apps#3407 · 14 comments ·
All issues in apache/nuttx-apps
Similar issues
-
level/task module/gcp type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
hapostgres/pg_auto_failover#1190 ·
-
docs
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
P3 sonic-vpp
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sonic-net/sonic-buildimage#29662 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 94/100
spack/spack-packages#6586 ·