Touch initialization problem #425
Replies: 3 comments 2 replies
-
ok so both of those issues are not with the driver but instead what parameters you are passing to the driver. The user is responsible for creating the the SPI bus instance and the device instance which is where the frequency is set. the reset pin I have updated the code in the driver so you can pass an instance of the |
Beta Was this translation helpful? Give feedback.
-
Since I never did either of those things, it's weird that I ever got a working build back in December. I'm guessing a timing issue and I got lucky with a build? |
Beta Was this translation helpful? Give feedback.
-
I added a bunch more print statements and see the exception on the setDirection(). This is occurring fairly early in touch setup and is likely a causing other issues down the line. Perhaps I should re-write the pca9557.py to more closely follow your new methods. Is there a particular IO Expander example that would be best to follow or are all of them up to date with the new coding methods?
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I was attempting to see if the latest tip of tree made any difference in the running size of my binaries, but I ran into a regression with the gt911.py touch initialization. This is with a 7" Crowpanel which uses an ESP32-S3-WROOM-1-N4R8.
7" Crowpanel info
This was working on a Dec 6 2024 build. Mind you, I have not downloaded and rebuilt LVGL-micropython on a regular basis and reflashed the board for all the code updates since then. (I have loaded some of them, but I didn't keep careful track).
I was having exactly the same problem back in Nov of 2024, but a fix in early Dec 2024 fixed it. I was in discussions with @MitchBradley and he had this to say at the time.
Which I verified with clone, build and test with a working build on Dec 6, 2024.
Beta Was this translation helpful? Give feedback.
All reactions