Hi Jonathan, I'm in the process of writing an RFNoC block for some IP and I have a few questions for you. 1. What is the required numbering convention of the NOC_ID parameter? Is this related to the Stream ID discussed in the training slides? I'm assuming the crossbar address has to be the same for all CE's attached to it? 2. Is TLAST required? Looking at some Xilinx IP, if using TLAST, it can use either Vector Framing or Packet Framing; which is required by the AXI Wrapper? Andrew Adams AOS-QWW Applied Physics Laboratory Johns Hopkins University (240) 228-6637 office (240) 328-2899 mobile

Hi Andrew, 1. There is no convention currently. You can use whatever NOD ID you want assuming it does not overlap with one already in use. 2. Yes, AXI Wrapper needs a valid tlast as it affects the packet length calculation. Vector vs packet framing is special to the Xilinx FIR filter core and choosing one over the other depends on your FIR filter configuration. In most cases though, I would suggest packet framing. Jonathon On Mon, Oct 19, 2015 at 6:37 AM, Adams, Andrew L. via USRP-users < usrp-users@lists.ettus.com> wrote: > Hi Jonathan, > > > > I’m in the process of writing an RFNoC block for some IP and I have a few > questions for you. > > 1. What is the required numbering convention of the NOC_ID > parameter? Is this related to the Stream ID discussed in the training > slides? I’m assuming the crossbar address has to be the same for all CE’s > attached to it? > > 2. Is TLAST required? Looking at some Xilinx IP, if using TLAST, it > can use either Vector Framing or Packet Framing; which is required by the > AXI Wrapper? > > > > Andrew Adams > > AOS-QWW > > Applied Physics Laboratory > > Johns Hopkins University > > (240) 228-6637 office > > (240) 328-2899 mobile > > > > _______________________________________________ > USRP-users mailing list > USRP-users@lists.ettus.com > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com > >