Acceptance filter configuration is described here

Please try this new patch. Added an extra test condition for Errata No.5

I assume that the patch also contains the overrun fix? Unfortunately this patch allows corrupt frames through using the described test pattern. I can seed CAN frames & so dump registers on fault should that help you. Yes, the new patch includes the overrun fix. The CAN frames and register dumps wou...

@PeterR
Here is the patch that includes a fix for errata 3.13.5.

@Peter R,
I suspect it could due to 3.13.5 as well. I'll send you another patch with the 3.13.5 workaround shortly.

@PeterR
I've attached the patch. Please run git apply fifo_overrun.patch on a branch based off release/v4.1. Note that because these changes are still under review, the final changes on master branch may be different.

Will I need to re-initialise & re-program the device? Yes. The registers will reset to their default power-on values. Do you know when the IDF CAN driver will be updated to address the errata issues? We are currently reviewing the bugfix and will be merged into master shortly, after which we will b...

Hi, I am trying to work around some CAN issues. I have not been able to recover the CAN issue using can_initiate_recovery() is supposed to recover from Bus-Off, it won't help recover from corrupt frames Entering and Exiting reset mode doesn't really reset the peripheral. It's more of a start/stop b...

@PeterR It doesn't make sense that the CAN driver would cause a 2ms block as the CAN driver ISR doesn't infinite loop anywhere. The only loop that occurs is the clearing of the CAN RX FIFO. In the worst case scenario where the CAN RX FIFO as completely overrun, the driver would simply clear the CAN ...

(1) Other devices receiving and functioning whilst the ESP is BUS OFF. I note that the bus does have a high rate of errors but the ESP is solid fail (driver does not pass on RX frames, TX may happen but I need to confirm), whilst other devices muck on. Is the ESP CAN actually attempting to transmit...