tvoneicken wrote: ↑

Thu Jan 21, 2021 6:00 pm

RPi PIO peripheral

On a personal note: Not gonna lie, I'm drooling all over that thing as well.

Sorry, at this point we cannot give you a date yet.

Your file is too big. Even disregarding other issues you may run into (wrt partitions, size of your flash memory etc) the memory aperture for flash data is only 4MiB and your file is larger than that. Suggest putting it on a fat or spiffs partition and serving it that way instead.

Where specifically do you read that BCK_IO_NUM is limited wrt pins to choose from?

Could be that the driver services some of the longer requests using interrupts. If so, you may be seeing an instance of interrupt latency that happens to be somewhat longer than your DMA buffer. You can try increasing MAX_DMA_BUFFER, that might solve the issue.

It very much depends on what your firmware is doing. Is it doing an equivalent of e.g. connecting to WiFi to turn on and off a LED depending on what a server tells it to do, is everything properly coded to use the public APIs and are you not using any peripherals that are only available on one of th...

I know that most flash chips have configuration registers that can write-protect some or all of the flash memory. You can read those registers using 'esptoool.py read_flash_status'. Perhaps if you compare the results of that to the datasheet of whatever flash chip you use, that may lead to the reaso...

Just to double-check: what are the actual pins you decided on using?

Hard to say. How did you configure your I2S peripheral? What hardware are you using to measure this?

You would use a mutex for that. If it fits you can also use an atomic variable to store your data (you're limited to 32 bits then, though), in which cases no mutexes are needed.