So, RFNoC 4 provides three different interfaces as noted in Section 2.3.3 of this <https://files.ettus.com/app_notes/RFNoC_Specification.pdf> doc. The first is a CHDR based interface (2.3.3.1), the second is the payload & context interface (2.3.3.2), and the third is the "axis_data" or "sideband signal" interface (2.3.3.3). Take a look at all of the block yml files for the Ettus blocks and you will find examples of all three.
When you specify a given interface in the block yml, the auto-generated noc_shell will be built based on that interface. So, my point is that if you decide to change interfaces, you need to start over. And, be careful to save anything of value beforehand because the auto-generation will overwrite what you presently have. Let me know if this doesn't make sense. Rob On Wed, Apr 28, 2021 at 11:48 AM <[email protected]> wrote: > Rob, > > > I was following the design based on the RFNoC 4, reason by which I was > using context and payload. Can you point me to the documentation where I > can see the timing diagram of the AXI signals for this fpga “axis_data” > interface?. In the RFNoC specification, I only see the context payload. > > > Thanks > _______________________________________________ > USRP-users mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ USRP-users mailing list -- [email protected] To unsubscribe send an email to [email protected]
