I2C SPI USB CAN eSPI Cable Testing View All Videos Quick Start Guides Software Downloads App Notes White Papers User Manuals Knowledge Base Sales Support About Us
Products Blog Sales Support Contact Search
Why do calls to aa i2c slave read aa spi write or aa spi slave read produce errors for large transaction lengths
Why do calls to aa_i2c_slave_read, aa_spi_write, or aa_spi_slave_read produce errors for large transaction lengths?

The asynchronous receive buffer is filling up and thereby causing bytes to be dropped. As explained in the user manual, these functions can only reliably transmit or receive transactions that are less than 4 KB in length.