Hi Samuel, 1) Block ports are considered independent of each other. That is why each one has dedicated sink/source sample streams, settings register bus, noc shell registers, etc. 2) Set INPUT_PORTS and OUTPUT_PORTS to the number of each you want (up to 16 per direction). See noc_block_ddc.v and noc_block_duc.v for examples on using a parameterized number of block ports. 3) Take a look at the RFNoC Getting Started Guide ( https://kb.ettus.com/Getting_Started_with_RFNoC_Development) and the RFNoC Virginia Tech video starting at 01:05:00 ( https://www.youtube.com/watch?v=8cPd3t88djE).
Jonathon On Sat, Feb 9, 2019 at 12:06 AM Kranz Samuel Josef via USRP-users < usrp-users@lists.ettus.com> wrote: > Hey > > > > The last few days I was working on a multi-port rfnoc block (2 inputs, 2 > outputs). By analyzing the ADD/SUB (noc_block_addsub.v) and the NOC Shell > modules, I understood how packet handling works. > > However, I’m not quite sure why the control ports (especially the control > sink – set_data, set_addr, … ) also scale with the number of BLOCK_PORTS > (noc_shell). > > To my understanding parameters configured in gr are provided through > these. > > > > So I came up with these questions. > > 1) Why does every stream has their own set of signals? > > 2) How are these ports properly used in multi stream blocks? > > 3) Is there any useful information (documentation, code file) which > explains the functionality of these ports? > > > > Thanks in advance. > > > > Samuel > _______________________________________________ > USRP-users mailing list > USRP-users@lists.ettus.com > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com >
_______________________________________________ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
