PS CAN TX/RX is from the MPC2515. I2C is pulled to 3.3V. PHY design is reference EVB LAN8710A. The corruption pattern is regular though and not shown on bus. This is ESP. If related to I2C 'stuck issue' what am I to do? Am using 4.1 IDF (need DHCP on Ethernet) which actually is worse than 4.0. IMHO ...

EDIT: CAN maybe not, I have no causal on CAN (just CAN corruptions so implicated because it is being naughty). Ethernet is fairly clear causal. Not checked why yet. Cool, thanks, will do tommorrow. Some recent facts: 1) I2C corruptions are absent/significatly reduced when I do not start Ethernet (4....

Please let me know how investigations are progressing & how to support or check progress. We were moments away from launch & whilst possibly could recover by dropping to 4.0 would loose some significant functionality. As is it is bust. I2C corruptions is a project killer. Just won't fly now without ...

A fault tolerant CAN implementation. Maybe even option for a couple of channels but mainly fault tolerant & functional.

Hi, Any further thoughts on latency, CAN overruns, Ethernet & especially I2C corruption seemingly arising from 4.0 to 4.1 IDF? Or frame corruption arising from termination issues which preceeds IDF 4.1? plajjd: Please note that you will receive corrupt CAN frames when using stock IDF. Overrun efects...

Would be interested in your IDF version. You are right, you will have a finite bandwidth to share among the DMA functions. I have found that it is very expensive to setup DMA on short transfers. You can pre configure but that is extra code. 1 mS is a long time though. Guessing 160Mhz internal RAM so...

Looks a bit buggy to me. Was hard to work with the code. Anyway - where is recvbuf initialised at the length you send? recvbuf is an empty character array and & so printf won't print anything. When doing binary streams best print the RX length and then the data received raw, rather than printf(). ES...

Thanks, interesting. Couple of points: 1) Frame corruptions are possible even without overrun 2) Not all overruns cause a frame corruption 3) Enabling Ethernet increases the overrun rate Wiggling the termination resistor causes the corrupt frames I mentioned. I do not always see overruns when I get ...

Hi, See my other posts. There do seem to be significant & long standing issues with CAN & related issues with other driver in 4.1. To summarise: (1) IDF does not process overrun errors despite overrun causing a 0x88 byte corruption in frame. There is a crypic comment about overrun recovery & hardwar...

I have receieved reports that our ESP32 product's CAN fault tolerence is significantly worse than other devices. I have performed some basic tests & find that when faced with a marginal CAN bus the ESP is likely to reject more frames (refuses frames which other devices accept) but also allows frames...