forked from micropython/micropython
-
Notifications
You must be signed in to change notification settings - Fork 169
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Support some LVGL external libs. Related: lvgl/lv_binding_micropython#180 ESP32: Freeze lv_spi.py and sdcard.py. Related: lvgl/lv_binding_micropython#186, lvgl/lv_binding_micropython#69
- Loading branch information
Showing
3 changed files
with
3 additions
and
1 deletion.
There are no files selected for viewing
Submodule lv_bindings
updated
6 files
+1 −1 | driver/esp32/ili9XXX.py | |
+185 −0 | driver/esp32/lv_spi.py | |
+1 −0 | gen/gen_mpy.py | |
+6 −0 | lib/lv_utils.py | |
+178 −143 | lv_conf.h | |
+1 −1 | lvgl |
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
../../../lib/lv_bindings/driver/esp32/lv_spi.py |
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
../../../drivers/sdcard/sdcard.py |
c96e610
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@embeddedt @eudoxos - Any idea why RPi CI is failing?
c96e610
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it may have been a spurious failure, since STM32 uses the exact same action for setting up GCC and it succeeded.
c96e610
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@embeddedt stm32 fails too but with a different error:
c96e610
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The rp2 build is failing in JS (node.js), as I am reading the error, that must be some action setup not directly related to the port (unlike the stm32 which is an error from the linker).
c96e610
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you have an idea how to fix these problems?
c96e610
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The same action error seems to be already reported here: fiam/arm-none-eabi-gcc#17, the warning is probably unrelated (but also reported here: fiam/arm-none-eabi-gcc#24). This is perhaps the most pertinent? fiam/arm-none-eabi-gcc#11: github actions occasionally fail due to stalls/timout. Can you just try to re-run the CI to see if it fails again?
c96e610
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, I just restarted the RPi CI and it passed.
Now only the stm32 failure remains. @embeddedt - I don't think this is Micropython related. It would probably fail on an stm32 C project as well.
c96e610
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's caused by an
fprintf
call. I'm guessing this was an oversight as the other error messages in that file all use LVGL logging, so I've changed this one to use the same.