- Silicon Labs Community
- Welcome and Announcements
- Silicon Labs Knowledge Base
- 8-bit MCU
- 32-bit MCU
- Bluetooth / Wi-Fi
- Other Products Category
- Optical/RH/Temp Sensor
- Other Products
- Hardware and Software Tools
- Simplicity Studio and Software
- General Discussions and Suggestions
- Chinese Forum
- Software Libraries
- Development Kits
- Reference Designs
- Third Party Tools
- White Papers
- Official Blog of Silicon Labs
- Chinese Blog
修改时间 09-18-2017 10:35 AM
You could have a look at the AN792 to see how the ReadWithRTR works.
In AN792, you can find more information on the ReadWithRTR command. Basically, the CP2130 will read data from the MISO line as long as RTR is asserted. When RTR is de-asserted, the SPI won't clock any additional reads once the current read byte is finished (SPI reads are suspended). When RTR is re-asserted, the SPI will continue its read transfer.
In ReadWithRTR mode, the CP2130 will continue reading until the specified number of bytes are finished being read (this can take an indefinite amount of time if RTR is not asserted). Or, you can abort the ReadWithRTR command using the Set_RTR_Stop command.
RTR logic level can be configured using the Set_Pin_Config command for GPIO.3 to be RTR (active high) or /RTR (active low).
My views are my own and do not necessarily represent the views of Silicon Labs
修改时间 09-18-2017 09:21 PM
Thanks for the detailed explanation, delu!
Your descriptions match to what I observed from CP2130 Evaluation Tool. With CP2130 Evaluation Tool, I could read small amount bytes (less than 64 bytes) after the first RTR was asserted only. But there was no read after the second RTR was asserted. If I set RTR block size higher than 64 bytes with large size of total samples, I could continuously read during several RTRs.
However what we are looking for is that CP2130 reads small amount bytes when the RTR is asserted every time. So we would like to have the RTR triggered CP2130 reading rather than paused CP2130 reading.