Yeah the provided code doesn't function on 7 inch - Wire's default pins are not right. should be 19 and 20. Im using a TPA2016D2 for example. if i do Wire1.begin(19, 20, 100000); everything works. I should also note because the defaults are usually &Wire, i did: boolean result = audioamp.begin(TPA2016_I2CADDR, &Wire1);
Hi, for any technical inquiries or assistance, please feel free to reach out to us at techsupport@elecrow.com. We are here to help and will respond to your request promptly.
@@eliothavila7337 I used free RTOS. Made a process surrounding the screen refresh call, and another process that did stuff with the I2C. Created a mutex lock, such that only one of the two can operate at the same time. Still plenty high enough frequency to be responsive. You can go upwards of 20 milliseconds between screen refresh calls
@@eliothavila7337 see the Digi key freertos series, that guy does all his stuff on an esp32. You should be able to get the background knowledge from there. Outside of that the solution is a mutex created for the I2C bus. Thread A must get it before doing a screen update, and thread B must get it before doing some arbitrary I2C operation.
![[ESP32 + LVGL] Using DHT22 Sensor For Display Temperture and Humidity.](/img/n.gif)
Voiceover is broken @6:11
Yeah the provided code doesn't function on 7 inch - Wire's default pins are not right. should be 19 and 20. Im using a TPA2016D2 for example.
if i do Wire1.begin(19, 20, 100000); everything works. I should also note because the defaults are usually &Wire, i did:
boolean result = audioamp.begin(TPA2016_I2CADDR, &Wire1);
Hi, for any technical inquiries or assistance, please feel free to reach out to us at techsupport@elecrow.com. We are here to help and will respond to your request promptly.
How do I solve the touch problem?
@@eliothavila7337 I used free RTOS. Made a process surrounding the screen refresh call, and another process that did stuff with the I2C. Created a mutex lock, such that only one of the two can operate at the same time. Still plenty high enough frequency to be responsive. You can go upwards of 20 milliseconds between screen refresh calls
@@CooperZuranski How did you do it ? would you have an example to show me ? thank you.
@@eliothavila7337 see the Digi key freertos series, that guy does all his stuff on an esp32. You should be able to get the background knowledge from there. Outside of that the solution is a mutex created for the I2C bus. Thread A must get it before doing a screen update, and thread B must get it before doing some arbitrary I2C operation.