It can be done, but it's tricky. Of course, if the decode isn't quite right and the firmware image running isn't what you actually shipped, your customer's device is now a brick, and that's usually considered to be bad. The problems you have to deal with include the compression that's commonly used,...

The UNIX kernel, like a lot of other RTOSes, got away with a single timer source for a long time. I'm not saying that didn't have excuses, but it was workable. Just brush up on having one montonically increasing value of "time" and a list of events scheduled to be serviced in the future. If you have...

Commodity filesystems like LittleFS and SPIFFS are good at wear-leveling. Hand them a partition that's large enough that they're not always on the hunt for fresh sectors and just write a CSV or a file per sample or some other natural case where you can reconstruct missed uploads and retire out old d...

It's up to the host OS. On MacOS, for example, some machine processing of 'ioreg -l' will return the dev node and the serial number of the parts. If [tio](https://github.com/tio/tio) works for you to list the node names with 'tio -l', you could look at the device discovery code and, within license, ...

That works. The hardware provides two different endpoints on the USB interface. One is for JTAG and the other endpoint is either virtual serial CDC/ADM (I can't recall which it is, but "serial port") or whatever you want it to be. So if you create ESP32 software to be an endpoint for a mass storage ...

Bizarre problems on Windows that are never reproducible to anyone else (obviously "blink" is a well-traveled road) are often the result of AntiVirus malware. Disabling that as a test and reinstalling IDF (in case THAT was eaten by your A/V) would be my starting point. Something is interfering with y...

They ARE const in c++. This is one of many footguns removed in the improved language. C89 and 99 have a goofy exemption to allow interop with K&R that's one of those rare cases - beyond sizeof()- where a char[N] and a char* aren't REALLY the same type. Literals decay to a const char* even in C. GCC ...

> - Added "-mfix-esp32-psram-cache-issue" as I do not have the rev3 chip Stop that. That flag is for a different chip. ESP32 and ESP32-S3 are NOT THE SAME CHIP. Did you ever actually call psram_init()? Did you verify that any of the hundreds of other projects successfully working on S3 boards work o...

1) Before you build, prototype. Dev boards are faster and cheaper than the fastest and cheapest PCB house.

2) Reading datasheets is essential, as already answered, but also see. https://github.com/atomic14/esp32-s3-pinouts

> You make a good point, We're engineers. We make data-driven decisions. :-) > Discourse, not Discord Excellent point. I dislike the Arduino discourse forums, but I don't have a raging tate for them like I do the discord groups. > I can't find that setting. I'll admit that my PHPBB experience was, o...