Repository navigation
LVGL: a failed assert raises RuntimeError instead of hanging the board - #294
Merged
Merged
Conversation
Moves omnipython-lvgl from 00bfbab to 2206123. A failed LVGL assert used to spin forever with the scheduler locked, so the board needed a power cycle; now it raises RuntimeError and LVGL carries on. The range also brings the opt-in TLSF memory pools (-DLVMP_POOL_TLSF=1); no board here sets the flag.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Moves the omnipython-lvgl pin from 00bfbab to 2206123 (PyDevices/omnipython-lvgl#13).
A failed LVGL assert used to spin in the assert handler with the scheduler locked: the board stopped answering on USB and WebREPL and needed a power cycle. With this pin it raises
RuntimeError("LVGL assert failed in ..."), clears LVGL's rendering flags, and the next refresh draws. That was proven on the unix port with an invalidate during a flush and with an allocation failure mid-render; both hung before.The range also brings the opt-in TLSF memory pools (
-DLVMP_POOL_TLSF=1). No board in this repository sets the flag, so nothing changes for them.Not yet run on a board; CI's builds are the check here.