Hopefully you have the means to bump frame rates etc and so prove to yourself that overflow is an issue (I am not mongoose so cannot say if they fixed overflow). If overflow is still a mongoose issue then I would bet that the silicon errata issues are also present. Hence my statement; you must upgr...

You must upgrade. No question, none. Oh I'm taking this very seriously. My product will be used, in part, for remote monitoring. Being able to reconfigure and soft reset reliably and remotely is critical. Drivers are outside most of my experience so it's taking me some time. I'm currently looking a...

Thank you Peter this is great information! I'll study the Espressif driver and see if I can use it in my code. I'm very relieved to hear that this issue can be handled. Thanks again.

Also, fwiw, we have a driver in ESP-IDF that is fully supported and maintained by now. You may want to switch to that instead of using 3-year-old unmaintained code. I'll definitely look at that. The driver is part of a bigger CAN library I'm using, but it's OS so I can look at changing it. But may ...

Thanks very much... I have been working on this quite a bit and it seems that what's happening is that the CAN controller is not working correctly after a soft reset. I did see something about this in the eratta but didn't fully understand it. The code I'm using is using a CAN driver by Thomas Barth...

I'm having an odd problem I can't explain. I have a board based on an ESP32-VROOM-32U module with 16MB flash and my FW uses Mongoose OS. My firmware seems to run fine for hours, even days collecting data from CAN bus, until I restart the ESP32 without disconnecting power. This happens after an OTA o...

I am able to use a J-Link JTAG debugger successfully with my board, now I'm trying to use a Flyswatter2. Espressif supplied a config file for this device, but OpenOCD is unable to talk to the Flyswatter2. I can see it on the lac with lsusb and system profiler. I would appreciate any help, thank you....

I think I found it. This board uses the Segger 10 pin needle connector and pin 1 (VTREF) was not connected. I added a hookup wire between V3.3 and that pin and got the results I pasted below. Jims-MacBook-Pro-486:~ jim$ openocd -f interface/jlink.cfg -f board/esp32-wrover.cfg Open On-Chip Debugger v...

I have a board with an ESP32-WROOM-32U and a JTAG circuit, and I have been unable to get OpenOCD to work with the board using a Segger J-link JTAG debugger. When I try, I get this: Jims-MacBook-Pro-486:~ jim$ openocd -f interface/jlink.cfg -f board/esp32-wrover.cfg Open On-Chip Debugger v0.10.0-esp3...

It turned out that I was able to run JLinkExe (I think that's JLink Commander) from Segger to talk to it. As soon as I did, a FW upload was issued to the J-Link and now OpenOCD can talk to it.

Thanks very much for your reply.