The sarcasm and derogatory attitude are not appreciated. Claiming C and C++ are not related any more than C and COBOL is outright offensive (and `extern "C" {}` doesn't save the day, but code would need to be placed into .c file). On top of that, explicitly not supporting C++ can not possibly be a "...

The examples/peripherals/i2s/main/i2s_example_main.c contains invalid code; i2s_config_t i2s_config = { .mode = I2S_MODE_MASTER | I2S_MODE_TX, // Only TX .sample_rate = SAMPLE_RATE, .bits_per_sample = 16, .channel_format = I2S_CHANNEL_FMT_RIGHT_LEFT, //2-channels .communication_format = I2S_COMM_FOR...

Long thread, and can't say I have read every suggestion, but mine are about fixing the "broken" parts in ESP32, before adding "more stuff" (possibly with the exception of more usable GPIOs on the physical chip) * Interrupt latency is quite poor. I don't understand why, but if 8bit microcontrollers c...

Nope. The compiler/linking still affects the delays that happens inside the silicon somewhere... We have decided to abandon the hardware solution at hand and go with something else, where we don't depend on reliable CPU execution cycles.

Second problem found; It was a ESP_LOGI inside the portDISABLE_INTERRUPTS block. Newer esp-idf/ detected that and pointed me in the right direction. Original problem; I can live with my work around.

Thanks for taking an interest. Between my post and "me giving up", I gave up for a different reason... More about that below. First answer your questions; SCLK is generated by the SPI module. CS is generated from MCPWM. MCPWM resolution is 4 clk cycles per SCLK cycle, so I can set the CS pulse exact...

I have had a similar problem before, and it was due to too much solder paste on the GND under the chip. Using a "checkered" pad resolved the problem. I.e. add solder mask on top of the pad so that you get 9 "islands" of solder paste, or even just make the solder paste layer into such pattern. A good...

Hi, This issue is driving me bonkers. I am reading an ADC128S102 (A/D converter) in endless mode. So, I set up VSPI with a descriptor to point back to itself, syncing up a CS via MCPWM Timer1 (should not be needed, but primarily to get stable oscilloscope readings). The data that is sent out is very...