Standard esp-idf (also fails with Arduino versión) TWAI CANBUS code runs perfectly but if you call display_init(); after or before TWAI init code. Canbus works for a minute or so then fails taking down CANBUS with it!
Using T4-S3 (BoardsConfigure_t BOARD_AMOLED_241)
Using header available PINS 18(TX) and 21(RX) for TWAI
When display is not connected to board no issues arise with CANBUS data. Have not tried with other PINS. Is it possible that pin 18 and/or 21 are being affected somehow? Will try with pins 47 and 48 later.
Only fails if CANBUS data is being received or is being transmitted. You need to test with that in mind.
Other similar LVGL+CANBUS/TWAI software is working with esp32-s3 with similar (but QSPI) AMOLED display and driver code, without issues.
Experienced esp32 display driver/SPI expert should be able to figure this out quickly.
Standard esp-idf (also fails with Arduino versión) TWAI CANBUS code runs perfectly but if you call display_init(); after or before TWAI init code. Canbus works for a minute or so then fails taking down CANBUS with it!
Using T4-S3 (BoardsConfigure_t BOARD_AMOLED_241) Using header available PINS 18(TX) and 21(RX) for TWAI
When display is not connected to board no issues arise with CANBUS data. Have not tried with other PINS. Is it possible that pin 18 and/or 21 are being affected somehow? Will try with pins 47 and 48 later.
Only fails if CANBUS data is being received or is being transmitted. You need to test with that in mind.
Other similar LVGL+CANBUS/TWAI software is working with esp32-s3 with similar (but QSPI) AMOLED display and driver code, without issues.
Experienced esp32 display driver/SPI expert should be able to figure this out quickly.
See https://github.com/nopnop2002/esp-idf-can2socket for excellent CANBUS example code.