It's based on AXI4-Stream, so you might look into that protocol for a deeper understanding. Here's a link to the relevant section of the spec (Section 2.2.1: Handshake process)
HTML Doc: https://developer.arm.com/documentation/ihi0051/a/Interface-Signals/Transfer-signaling/Handshake-process PDF Link: https://documentation-service.arm.com/static/5f914c33f86e16515cdc2b26?token= Thanks, Wade On Tue, Mar 30, 2021 at 4:57 PM Brian Padalino <bpadal...@gmail.com> wrote: > The producer should always be producing when it can so push tvalid as > often as you want. > > The data is only accepted by the other side by tready. Don't wait for > tready to push tvalid. > > Brian > > On Tue, Mar 30, 2021 at 5:51 PM Hodges, Jeff via USRP-users < > usrp-users@lists.ettus.com> wrote: > >> On the AXI Bus, what is the the behavior of data_tready? Does it go low >> at the conclusion of each packet? If not, how long after de-asserting >> data_tvalid is it allowable to re-assert data_tvalid and begin another >> packet? >> >> >> Thanks, >> >> >> Jeff >> _______________________________________________ >> USRP-users mailing list -- usrp-users@lists.ettus.com >> To unsubscribe send an email to usrp-users-le...@lists.ettus.com >> > _______________________________________________ > USRP-users mailing list -- usrp-users@lists.ettus.com > To unsubscribe send an email to usrp-users-le...@lists.ettus.com >
_______________________________________________ USRP-users mailing list -- usrp-users@lists.ettus.com To unsubscribe send an email to usrp-users-le...@lists.ettus.com
