Sure. I really want to know if there is an unresolved issue with this driver too. I will test more but I only moved to this driver 2 days ago. I did test sending two messages on high resolution timer callbacks, both at 1ms intervals with queue size of 5 and saw about 1000 messages per sec from each ...

If you have a minimal example with the problem I can test. Also have Kvaser.

If you get the Tx interrupt to force a context switch like the Rx interrupt it should solve your problem. Works for me - have just flashed BMW engine control unit at over 2000 frames a second. Half the time waiting for the next WiFi message. static void can_intr_handler_tx(can_status_reg_t *status, ...

My devkit C works for CAN Rx on pin 34 - just tried it.

I think I was mistaken again... and thought it was OK because of how tasks were allocated in that build but the problem reoccurred and only pinning tasks to the same core avoids the problem.

I am hoping the new CAN driver will behave and will not try further to work around the old one.

// ** Set the correct configuration for ESP32-WROVER-KIT v4.1 // -------------------------------------------------------- #define DEFAULT_DISP_TYPE DISP_TYPE_ILI9341 #define DEFAULT_TFT_DISPLAY_WIDTH 240 #define DEFAULT_TFT_DISPLAY_HEIGHT 320 #define DISP_COLOR_BITS_24 0x66 #define DEFAULT_GAMMA_CU...

https://github.com/loboris/ESP32_TFT_library/issues/35

Working as ILI9341 but flipped

Is there any documentation for the above? Particularly looking for any info on the LCD: https://github.com/loboris/ESP32_TFT_library with ESP WROVER KIT preconfig settings doesn't show anything but a white screen even with DIO and 40MHz SPI speed and PSRAM disabled. The application it arrived with j...

Thanks. I think I will keep a separate error task and display at a few Hz instead of a few kHz, but using the new CAN driver I will not need to read the hardware registers directly.