RE: I2S TXPTRUPD and STOP timing

loquat — Thu, 07 Sep 2017 16:17:09 GMT

Thanks very much!!

I try it.

Sigurd — Thu, 07 Sep 2017 11:16:52 GMT

Hi,

Yes, if you don’t update the TXD pointer after a TXPTRUPD event, the next transfer will continue to use address A.
See this figure here. You can set the TXD.PTR for the 2nd transfer, before the first transfer have started. ( TXD.PTR = C in the figure)
The transfer stops close to immediately after you call TASKS_STOP. It will not wait for the block to finish.
Yes, that should be possible. I recommend using the I2S drivers, and use the data_handler to keep track of the numbers of block you are sending. The data_handler is called for every TXPTRUPD/RXPTRUPD event, and you will get a TXPTRUPD event for every RXTXD.MAXCNT words that are sent on the SDOUT pin. You can then use nrf_drv_i2s_stop() to stop after you have sent the number of blocks you want.