[USRP-users] does an RFNoC block HAVE to have an input and an output?

Jason Matusiak jason at gardettoengineering.com
Fri Jul 14 12:14:53 EDT 2017

Good call Jonathon, I forget that you guys wrote up a siggen block, that 
will be great to emulate.  In fact I attempted to make a stripped down 
version that just outputs the sine-wave all the time, but I am not 
getting any output.  Looking at the debug that scrolls across the screen 
while the python script starts running I see this:
[INFO] [RFNOC] Assuming max packet size for 0/dataGenerator_0
[WARNING] [RFNOC] issue_stream_cmd() not implemented for 

Is that something I should be worried about?


On 07/13/2017 05:21 PM, Jonathon Pendlum wrote:
> Hey Jason,
> All blocks have to have at least 1 input and 1 output port. You are 
> correct that you should still setup an input port in Noc Script, but 
> not expose it in the GRC XML. Take a look at the Siggen block's HDL, 
> Noc Script, and GRC XML.
> Jonathon
> On Thu, Jul 13, 2017 at 12:15 PM, Jason Matusiak via USRP-users 
> <usrp-users at lists.ettus.com <mailto:usrp-users at lists.ettus.com>> wrote:
>     I have a block that I want to essentially be a source block in
>     RFNoC (outputting data from a ROM), but when I go to probe, I get
>     this error:
>     RuntimeError: LookupError: Path not found in tree:
>     /mboards/0/xbar/dataGenerator_0/ports/in
>     Is this because I set it up without sink input?  Is there any way
>     around it?  I think the solution is to put a sink in the
>     rfnoc/blocks/ XML file but NOT the grc XML file, is that right?
>     _______________________________________________
>     USRP-users mailing list
>     USRP-users at lists.ettus.com <mailto:USRP-users at lists.ettus.com>
>     http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>     <http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20170714/fba89967/attachment-0002.html>

More information about the USRP-users mailing list