[USRP-users] RFNoC Signal Source

Jonathon Pendlum jonathon.pendlum at ettus.com
Wed Mar 30 13:33:44 EDT 2016


Hi Sam,

Does the configuration RFNoC SigSource -> Multtiply Const (Const = 1) ->
RFNoC Radio work?


Jonathon

On Tue, Mar 29, 2016 at 10:33 AM, Sam Carey via USRP-users <
usrp-users at lists.ettus.com> wrote:

> Thanks for the suggestions! I’ve made a lot of progress but now I’m stuck.
>
> For this first attempt, I hardcoded the samples of my waveform into my own
> version of null_source.v. I generated a lookup table using MATLAB, pasted
> it into null_source.v, and set the output so that it cycles through the
> samples. I instantiated it in my own version
> of noc_block_null_source_sink.v and made my own versions of
> null_block_ctrl_iml.cpp, null_block_ctrl.hpp, and nullblock.xml. I also
> added an xml file to let it appear in GRC.
>
> From GRC, I tested my new source block:
> RFNoC SigSource —> UHD: USRP Sink; UHD: USRP Source —> WX GUI FFT Sink
> And I was able to see my expected signal.
>
> I also tested the RFNoC radio blocks with a GNURadio source block:
> Signal Source —> RFNoC: Radio; RFNoC Radio —> WX GUI FFT Sink
> And I was able to see my expected signal.
>
> However, if I try to use the RFNoC Radio blocks with my new source block:
> RFNoC SigSource —> RFNoC: Radio; RFNoC Radio —> WX GUI FFT Sink
> I see only noise.
>
> I noticed that this mixed configuration works fine:
> RFNoC SigSource —> UHD: USRP Sink; RFNoC Radio —> WX GUI FFT Sink
>
> But this one does not:
> RFNoC SigSource —> RFNoC: Radio; UHD: USRP Source —> WX GUI FFT Sink
>
> So this leads me to believe there is a problem with generating and
> directly transmitting a signal on the FPGA.
>
> I noticed a recent post, “ [USRP-users] RFNoc. Cant have TX & RX on same
> flow diagram,” in which it was said, "The reason it doesn't work right now
> is there's no entity managing/owning the stream, and the control
> communication to the blocks doesn't happen.” Does this apply to my block as
> well? If so, is there any way I can make “RFNoC SigSource —> RFNoC: Radio”
> work before it is fixed in the official branch?
>
> I’ve attached my code.
>
>
> Thanks,
> Sam Carey
>
> On Mar 14, 2016, at 12:53 PM, Jonathon Pendlum <jonathon.pendlum at ettus.com>
> wrote:
>
> Hi Sam,
>
> That block does not exist yet, although it is scheduled to be made. If you
> need in soon though, I would suggest writing your own. It would not too
> difficult, you could use an approach similar to the window RFNoC block and
> load up a block RAM with your samples.
>
>
>
> Jonathon
>
> On Sun, Mar 13, 2016 at 11:35 AM, Sam Carey via USRP-users <
> usrp-users at lists.ettus.com> wrote:
>
>> Hello,
>>
>> I need to repeatedly transmit a 128-sample long, static signal at 200
>> MS/s (I’m using an X310 with UBX). This static, repeating signal has to
>> originate from the X310 itself because I don’t have the hardware to send
>> that sample rate from the host.
>> I suppose I need something like a "signal source” block to be implemented
>> on the FPGA, but I can’t find such a block in the RFNoC libraries. Does
>> this functionality already exist somewhere, or do I need to create it
>> myself?
>>
>> Thanks,
>> Sam Carey
>>
>>
>> _______________________________________________
>> USRP-users mailing list
>> USRP-users at lists.ettus.com
>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>>
>>
>
> Thanks and Gig 'em,
> Sam Carey '15
>
>
> _______________________________________________
> USRP-users mailing list
> USRP-users at 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/20160330/d99f3aa5/attachment-0002.html>


More information about the USRP-users mailing list