Timeline for how long should an I2C slave wait for a STOP bit (if at all)?
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 18, 2018 at 23:21 | comment | added | Maple | I think you've missed my point. If ISR only does what it is supposed to do (i.e. almost nothing) then most time is spent in main code, which analyses the packet and ultimately makes a decision. It might have enough time to make it in time for sending something back, in which case it puts data into transmit buffer and raises flag "ready to transmit". Otherwise it activates flag "delay response" and ISR begins clock stretching. | |
| Jun 18, 2018 at 22:45 | comment | added | danmcb | I agree, but see my response to Olin above. You have to send as well as receive, and you don't know which you will be doing until the middle of the overall packet of bytes. | |
| Jun 18, 2018 at 21:26 | history | answered | Maple | CC BY-SA 4.0 |