English is currently available.
Raspberry Pi Pico DISCUSSION
One Pico core manages sampling while the other processes completed blocks. What ownership rules keep the CPU from reading a block while DMA is still writing it, especially when processing occasionally takes longer than one block period?
Reference: Raspberry Pi: Pico SDK hardware APIs (https://www.raspberrypi.com/documentation/pico-sdk/hardware.html).
Give each buffer a clear state such as available, filling, ready or processing. Publish a buffer as ready only after the transfer has completed. The processing core must release it before the acquisition side reuses it; a pointer handed to another core is not an ownership protocol by itself.
Use the SDK's suitable synchronization mechanisms and the architecture's memory-ordering requirements. Volatile alone does not provide a complete multicore synchronization scheme. Keep critical sections short and avoid holding a shared lock while doing lengthy signal processing or formatted logging.
Calculate the block deadline: 256 samples at 16 kHz represent 16 ms. Measure worst-case processing time and define what happens if no free block exists. Count overruns and identify dropped blocks with sequence numbers so extra buffering does not hide a sustained throughput deficit.
