So helpful!

That fully answers all of my questions.

Thanks @ESP_Sprite!

After updating all computers and smartphones (Windows, Mac, Linux, iPhone, Android) with the latest updates to address the BlueBorne security vulnerability (everyone should have done this already!), we should ask what to do about IoT chips such as ESP32 that support Bluetooth and may be affected by ...

I see that the DPORT section has been added to the TRM. Meanwhile I have also noticed some code changes in esp-idf master using these registers as well. I cannot seem to find a short explanation about the meaning/purpose of these registers, for example the following questions: What does DPORT stand ...

Also, incidentally, @kolban does your "sorta working" example work for you? My use is different (and working... but v. slow) but the configuration is similar (yours is camera+RX+I2S0, mine is LCD+TX+I2S1), but personally I'm not able to run at this speed: I2S0.clkm_conf.clkm_div_num = 2; (I really w...

Thanks, that does help. This specific comment from the Github issue you mentioned seems to be the most up-to-date info on the matter: size: size of the buffer pointed to by buf member length: number of valid data bytes stored into the buffer. For example, if you create a DMA descriptor with 1024 byt...

Sorry to bump this old thread, but I notice within esp-idf, in the file components/esp32/test/test_ahb_arb.c:130 the following code snippet. As far as I can tell, this is the only occurrence within esp-idf of non-uint8_t data being sent with DMA, and here it appears that length and size are both set...

I think I solved it! I am now using the following settings: I2S1.conf_chan.tx_chan_mod = 0x1; ( NOT 0x0) I2S1.fifo_conf.tx_fifo_mod = 0x1; ( NOT 0x0) I2S1.sample_rate_conf.tx_bck_div_num = 2; ( NOT 1) I2S1.int_ena.out_eof = 1; ( NOT out_done) Only using I2S1.out_link.start = 1; I2S1.conf.tx_start = ...

Well I had tried both WS for clock, as well as using BCK directly. I prefer the waveforms from using BCK, but it doesn't seem to make a significant difference (still seeing 64 samples instead of 32 -- a new sample on each clock level change). When using WS signal in LCD mode, it seems as though the ...

I seem to be experiencing a bug (or configuration error) that leads to incorrect/duplicate I2S data being transmitted. My DMA buffer is transmitted correctly (e.g. in my case 32 clocks edges == 32 16-bit samples in parallel mode) -- however the buffer is being transmitted twice (64 clock edges total...