All content and materials on this
site are provided "as is". TI and its respective suppliers and providers of content make no representations about
the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these
materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a
particular purpose, title and non-infringement of any third party intellectual property right. No license, either
express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a
license from a third party, or a license from TI.
When using the I2S driver in callback mode, the read/write callback should invoke when the passed buffer is done transferring data. Instead, the callback was invoked right as the passed buffer is about to start transferring data. This is a problem as this means the buffer pointer given by the callback is not safe to manipulate.
When using the I2S driver in callback mode, the read/write callback should invoke when the passed buffer is done transferring data. Instead, the callback was invoked right as the passed buffer is about to start transferring data. This is a problem as this means the buffer pointer given by the callback is not safe to manipulate.