Yes, I'm sure they are, but that's not what I'm referring to. You should look at A. the bandwidth of your PSRAM (which is the frequency it runs at, divided by 2 if the PSRAM does not run in octal mode), and B. the maximum bandwidth of your LCD (the pixel clock times the amount of bytes you send out ...

No. Internal flash still occupies some GPIOs. See the datasheet for more info.

They're the same.

Are you sure you are staying within the limits of the psram throughput? If GDMA can't fetch data fast enough it leads to corruption. Also keep in mind that worst case scenario, the gdma can only use half of the bandwidth of the psram peripheral (as it's round-robin shared with the CPUs).

No clue, sorry. Perhaps take a look at components/hal/esp32s3/include/hal/clk_gate_ll.h to see how that does it?

It's actually not incorrect. What the documentation describes is the 'hardware default' pin for that function, the pin where you can use the IOMUX to get that signal out with the absolute lowest latency. Disregarding latency, however, it's acceptable to use the GPIO matrix to route the function to a...

You likely want to fill the buffer afterwards with a load of silence. If you don't fill the buffer and the I2S hardware runs out of samples, I think it will simply repeat what's still in its buffers.

Ooh, that is a very good catch, that points in the direction of perhaps the ROM subsystem not being configured correctly for the flash available. I'll look into this; I'm decently sure this is a bug in our DFU builder or ROM assumptions.

1. I'm not sure. You should be able to get the frequency limits from the TRM, but there is also a bandwidth limit if you want to access PSRAM using the CPU as well, and I'm looking for docs with those calculations. If you use internal memory as a buffer, you can probably use any frequency the hardwa...

I'll see if I can dig a bit deeper, but one answer I have from the digital team is that the thing distributing PSRAM access permissions seems to be a non-configurable round-robin arbiter, so at this point I'm not sure if there's an easy hardware tweak to fix this. I'm still holding out hope for a co...