Closed jiabuda closed 1 year ago
Currently I am playing with lvgl and nimble on arduino and S3. With simple screens I have no problem switching between screens. Another application has more extended screens and transition caused crash. Unlucky to me no UART, so no backtrace. It turned out that simple task to handle lvgl was the problem. Running it on core 1 crashed app, now its running on core 0 and all is fine.
Currently I am playing with lvgl and nimble on arduino and S3. With simple screens I have no problem switching between screens. Another application has more extended screens and transition caused crash. Unlucky to me no UART, so no backtrace. It turned out that simple task to handle lvgl was the problem. Running it on core 1 crashed app, now its running on core 0 and all is fine.
Hi chegewara, i ask this question in lvgl, they reply that need to take the semaphore when you update the screen then give it again. i try this and problem solved.
Answers checklist.
General issue report
IDF: 4.4.2 LVGL: 8.3.3 Chip: ESP32
Hi, I am integrating Nimble and LVGL together to build a IOT device. Screen would be updated after Nimble central role discovery a peripheral device and establish connection. So inside Nimble event
BLE_GAP_EVENT_CONNECT
, I call some lvgl function to switch to another screen and calllv_obj_del
to delete the current screen. But the mcu reset and give a confusing core dump.Here is the code:
and
here is the stack trace