Open capricorn-one opened 6 months ago
Maybe a helpful update... and apologies if you don't want this here, maybe an issue in the lvgl library instead?
I found that by removing sytem performance monitor, I was able to get things running without the LV_LOG_LEVEL_TRACE condition. Still having some other hiccups, but maybe there's something there to look at...
Also.. an obvious fix was turning off EVE_DMA for the SPI transactions in the EVE_cpp_target.cpp file... would be nice to use DMA.. but for the time being I'll see if things work the normal way for now, still seems like there's a chip select missing somewhere though
Thank you very much for considering my work, it has taken me many hours to make it work properly. I'll take a look at what you mentioned. Again, thank you for your interest. Please wait a bit for the new version, and we will correct the necessary details.
Hey man, really appreciate all this work, great job!
Been trying to get this to work with a Teensy 4.1 and an EVE4 display.
I've gotten pretty far but have noticed that ultimately I can only get the LVGL to run without crashing when I have the LV_LOG_LEVEL_TRACE set for logging.
My guess is the printing to the console is causing enough of a delay to keep things moving, but obviously there's a small issue buried somewhere.
One change that moved things along was to add a EVE_execute_cmd() after the inital EVE_end_cmd_burst() in the flush callback function. This seems to indicate that reading from the REG_CMD_DL maybe isn't possible until the cmd_burst has finished, which makes sense.
Obviously this could also be an issue with the Teensy 4.1 driver and perhaps how it's handling the SPI transactions, possibly not waiting until the DMA has completed transfer yet.
Any thoughts on this would be appreciated, thanks again for all the effort here, drawing looks so much smoother on the test cases I've run so far!