Hey EJ, On Tue, May 29, 2018 at 11:10 AM EJ Kreinar <[email protected]> wrote:
> Hi Brian, > > Fascinating question! I'm not sure many have considered this possibility > (1-input, 4-output RFNoC block), though I agree I'd like to see RFNoC > support this use-case... > > Looks to me like this for loop in device3_io_impl could be getting in the > way: > https://github.com/EttusResearch/uhd/blob/rfnoc-devel/host/lib/usrp/device3/device3_io_impl.cpp#L569 > > Correct me if I'm wrong here, but it appears to be looping through all > upstream nodes and writing the response destination using the block port of > the *terminator* node, rather than the block port that's connected in the > RFNoC graph. This suggests to me there's an assumption that each block port > is always connected to the corresponding block port number of all upstream > nodes-- which is probably how the blocks are used in the majority of > configurations (2-channel radio -> 2-channel DDC -> 2-channel DMA FIFO), > but may not be sufficient for the arbitrary case... > > Is my interpretation correct?? > That looks correct to me. I noticed in the same file, the function generate_channel_list() which apparently looks for the following keys: - block_id%d - radio_id%d - radio_port%d But it looks like maybe that is only used on the TX side, and not the RX side? By changing the for loop to use "radio_port" in the channel arguments, I can get past the KeyError exception. I have other issues, but at least I am not stuck on this part. It does look like a bug, though. In a different thought, the XML file defines the output/input ports with names, but I can't find those names anywhere. For the Ettus folks, would it be difficult to use a fully named port as the streamer arguments, for example: 0/MYBLOCK_0/out_psd 0/MYBLOCK_0/out_symbols Does the C++ know the names of the ports and have it in a list somewhere to reference? This would seem much more readable than block port numbers. Thanks, Brian
_______________________________________________ USRP-users mailing list [email protected] http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
