![]() Slave application has to set the buffer size during initialization by the recv_buffer_size member of Receiving buffer size: The buffer size is pre-defined between the host and the slave before communication starts. Part will be filled with 0 (sending) or discard (receiving). ![]() The transfer length should be no shorter than the requested length, and the rest ESP32 slave DMA base on the requested length rather ![]() ![]() Requested length is different from the transfer length. Transfer length: The length requested in one transfer determined by the CMD53 byte/block count field. Requested length: The length requested in one transfer determined by the FIFO address. The application writes to a buffer owned by a sending driver, the data sent may be corrupted. If the application reads from a buffer owned by a receiving driver, the data read can be random if The application should not read/write the buffer until the ownership is returned to theĪpplication. Ownership: When the driver takes ownership of a buffer, it means the driver can randomly read/write the buffer Related to the length requested to read from/write to the slave in a single transfer: We’re not using tx or rx in the driver toįIFO: specific address in Function 1 that can be access by CMD53 to read/write large amount of data. Registers refer to sending, while ‘tx’ registers refer to receiving. are oriented from the point of view of the host, i.e. Register names in ESP32 Technical Reference Manual > SDIO Slave Controller
0 Comments
Leave a Reply. |