You should short DN+ with DN2+ and DN- with DN2- otherwise your USB-C connection only works one way around; have you tried flipping it to see if it works then?

(Btw, according to the USB specs, an USB-C connector should have its shield connected directly to ground; R4/C2 are not needed.)

That should just work. Are you sure there's not something else dragging the pin down? Perhaps using an oscilloscope rather than a LA may help identify the issue?

No, the ESP32-S3/ESP-IDF don't do page faulting; all memory pages are always available.

If you can post the error log (including the backtrace) and/or your code, we may be able to tell you more.

You can't. Interrupt overhead is pretty high on the ESP32 chips; if you're firing too many per second, the rest of the code doesn't get execution time and the watchdogs will reset your chip. Instead, the correct strategy is to try and use the peripherals (LCD interface, SPI, RMT, I2S, ...) to do the...

In general: If you value your sanity, do not use a breadboard for anything high-frequency (with 'high frequency' being anything above like a megahertz or something). In this particular case, your breadboard probably has all sorts of parasitic capacitance/inductance issues leading the crystal to osci...

Most likely cause is you having an interrupt marked as being entirely in IRAM which then accesses flash or psram.

No, and no.

That USB-C power plug just is not going to work. You need one which is properly USB-C compliant (=has those 5.1K resistors internally).

You can; in Menuconfig disable 'Component config → ESP System Settings → Memory protection'.

You could remove your sdkconfig and drop this file in your project directory, then run menuconfig again. (Note you may need to select one of the default partition schemes there as that file uses a custom one.)