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

[HELP] <title> lvgl demo use fb failed #15466

Open
1 task done
MaigoW opened this issue Jan 8, 2025 · 0 comments
Open
1 task done

[HELP] <title> lvgl demo use fb failed #15466

MaigoW opened this issue Jan 8, 2025 · 0 comments
Labels
Community: Question Further information is requested

Comments

@MaigoW
Copy link

MaigoW commented Jan 8, 2025

Description

task_spawn: name=lvgldemo entry=0x802a5950 file_actions=0x8050f498 attr=0x8050f4a0 argv=0x8050f5b0
spawn_execattrs: Setting policy=2 priority=100 for pid=6
PlaneInfo (plane 0):
fbmem: 0x80310b80
fblen: 960000
stride: 1600
PlaneInfo (plane 0):
fbmem: 0x80310b80
fblen: 960000
stride: 1600
arm64_fatal_error: reason = 0
arm64_fatal_error: CurrentEL: MODE_EL1
arm64_fatal_error: ESR_ELn: 0x96000004
arm64_fatal_error: FAR_ELn: 0xc002011785c181af
arm64_fatal_error: ELR_ELn: 0x802d6e6c
print_ec_cause: Data Abort taken without a change in Exception level
_assert: Current Version: NuttX 0.0.0 f6c51d11c8-dirty Jan 8 2025 16:02:47 arm64
_assert: Assertion failed panic: at file: common/arm64_fatal.c:375 task: lvgldemo process: lvgldemo 0x802a5950
up_dump_register: stack = 0x804fcfd0
up_dump_register: x0: 0xc002011785c18193 x1: 0x804e6998
up_dump_register: x2: 0x3 x3: 0x804e7d80
up_dump_register: x4: 0x804fd0bc x5: 0x804fd0b8
up_dump_register: x6: 0x38 x7: 0x804e5dd8
up_dump_register: x8: 0x0 x9: 0x130
up_dump_register: x10: 0x10 x11: 0xf0
up_dump_register: x12: 0x0 x13: 0x0
up_dump_register: x14: 0x0 x15: 0x0
up_dump_register: x16: 0x802c5e50 x17: 0x0
up_dump_register: x18: 0x0 x19: 0x0
up_dump_register: x20: 0x804e5000 x21: 0x802eaa18
up_dump_register: x22: 0x804e5840 x23: 0x804e5000
up_dump_register: x24: 0x804e88d0 x25: 0x804f03f0
up_dump_register: x26: 0x804f0308 x27: 0x804f0220
up_dump_register: x28: 0x804f00e0 x29: 0x0
up_dump_register: x30: 0x802c8ba4
up_dump_register:
up_dump_register: STATUS Registers:
up_dump_register: SPSR: 0x60000005
up_dump_register: ELR: 0x802d6e6c
up_dump_register: SP_EL0: 0x804fd160
up_dump_register: SP_ELX: 0x804fd100
up_dump_register: TPIDR_EL0: 0x804f8e40
up_dump_register: TPIDR_EL1: 0x804f8e40
up_dump_register: EXE_DEPTH: 0x0
dump_tasks: PID GROUP PRI POLICY TYPE NPX STATE EVENT SIGMASK STACKBASE STACKSIZE COMMAND
dump_tasks: ---- --- --- -------- ------- --- ------- ---------- ---------------- 0x804f2000 4096 irq
dump_task: 0 0 0 FIFO Kthread - Ready 0000000000000000 0x804f3010 8176 Idle_Task
dump_task: 1 1 192 RR Kthread - Waiting Semaphore 0000000000000000 0x804f6b30 8112 hpwork 0x8030f760 0x8030f788
dump_task: 6 6 100 RR Task - Running 0000000000000000 0x804f94d0 16336 lvgldemo
dump_task: 3 3 100 RR Task - Waiting Semaphore 0000000000000000 0x8050d980 8144 nsh_main

When I use the LVGL example with fb0, the fb0 device is found and initialized in /dev, but the error mentioned above occurs. I checked with dis and found that the specific address is 0x802d6e6c and the function is lv_timer_resume, but the error message is a data abort. How should I locate and resolve this issue?

Verification

  • I have verified before submitting the report.
@MaigoW MaigoW added the Community: Question Further information is requested label Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Community: Question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant