@mobhuyan: I'm saying it because from experience, a bad power supply can lead to lots of unexpected weirdnesses in the startup procedure (where sumesh's problem was) and is very easy to check (just use a different USB cable and a powered hub, or an external power supply or something). It stops peopl...

I get your gripe with the GPIOs. While we will not have direct GPIO <-> pad mappings (because it means we'd only be able to make one form factor chip - using the same silicon between e.g. the Pico and the 'bare' ESP32 chip would be impossible without messing up the pad numbering), we do get the weir...

You need to log out and log in for the change to take effect if you did the adduser thing earlier in the session.

Yes, there is. Exactly to make porting easier, there's no hard dependency on FreeRTOS per se as the multithreading handler; the WiFi and BT layers have a 'shim' that should make them able to adapt to any OS that provides the relevant APIs; see e.g. components/esp32/include/esp_wifi_os_adapter.h ; if...

The answer to that would be a very enthousiastic 'probably'; we can't really say without knowing the signals and what is on the other hand, but you'll most likely be fine, especially for prototyping purposes. I'd personally go for four-layer anyway, I've designed my share of two- and four-layer PCBs...

Moved to the Arduino subforum. What makes you so sure the sketch is gone, and not, for example, fails to start?

Actually, that's not entirely true. In the current master, the I2S peripheral can be configured to automatically take samples from the ADC and DMA these to memory. See e.g. the i2s_adc_enable function in the i2s driver.

Nothing wrong with just enabling and disabling interrupts; we do that using the interrupt matrix which is shared between CPUs and as such that can be done from any CPU. If you however de-allocate an interrupt, the code needs to touch registers that are only in the CPU where the interrupt was allocat...

The backtrace numbers are bits of information about the call stack, as you may know: each function call creates a so-called stack frame (the location on the stack where it stores its own temporary data) on entry and cleans it up on return. If you have a function calling a function calling a function...

Should be doable. However, you're relying on merely some solder mask to do the separation. If any, you may want to use the silkscreen to toughen that up a bit: effectively, make a silkscreen square under the pad to provide some extra thickness. Also, you may not want to do this with sensitive (ADC) ...