Send USRP-users mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of USRP-users digest..."


Today's Topics:

   1. Replaying a recording made with specrec in grc (Wouter Jan Ubbels)
   2. Re: Replaying a recording made with specrec in grc (Marcus M?ller)
   3. Inputting data into FPGA (Rohit Dilip)
   4. Re: Replaying a recording made with specrec in grc
      (Wouter Jan Ubbels)
   5. Re: Replaying a recording made with specrec in grc (Marcus M?ller)
   6. Re: RFNoC: Vivado environment variables not persisting during
      make (Nicolas Cuervo)


----------------------------------------------------------------------

Message: 1
Date: Sat, 15 Apr 2017 17:11:48 +0200
From: Wouter Jan Ubbels <[email protected]>
To: [email protected]
Subject: [USRP-users] Replaying a recording made with specrec in grc
Message-ID:
        <CABmbpx57y_eYhqqCK0R2W9zZOeTZVYRa=wucxPjYzmV=b3n...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi all,

Can anyone point me to a simple tutorial on how to replay a file recorded
with specrec from gr-analysis in grc? I can record a file just fine using
the following syntax:

specrec --freq 98e6 --rate 1e6 --gain 60 usrp_samples.dat

And it seems to record fine at higher sample rates as well without any
overflows (contrary to rx_samples_to_file which does not work well here),
so that?s good!

However, I have not succeeded to replay this file in grc using the file
source block. Any help is appreciated!

Thanks in advance,

Wouter Jan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20170415/cd0b6ffe/attachment-0001.html>

------------------------------

Message: 2
Date: Sat, 15 Apr 2017 20:25:50 +0200
From: Marcus M?ller <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] Replaying a recording made with specrec in
        grc
Message-ID: <[email protected]>
Content-Type: text/plain; charset="windows-1252"

Hi Wouter Jan,

If I remember correctly, specrec is basically a modified
rx_samples_to_file (a recording example from UHD itself), which supports
different --type arguments. Which one did you use? What's the default?
(--help)

Best regards,

Marcus


On 15.04.2017 17:11, Wouter Jan Ubbels via USRP-users wrote:
> Hi all,
>
> Can anyone point me to a simple tutorial on how to replay a file
> recorded with specrec from gr-analysis in grc? I can record a file
> just fine using the following syntax:
>
> specrec --freq 98e6 --rate 1e6 --gain 60 usrp_samples.dat
>
> And it seems to record fine at higher sample rates as well without any
> overflows (contrary to rx_samples_to_file which does not work well
> here), so that?s good!
>
> However, I have not succeeded to replay this file in grc using the
> file source block. Any help is appreciated!
>
> Thanks in advance,
>
> Wouter Jan
>
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> 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/20170415/3c06720c/attachment-0001.html>

------------------------------

Message: 3
Date: Sun, 16 Apr 2017 01:42:11 -0400
From: Rohit Dilip <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [USRP-users] Inputting data into FPGA
Message-ID:
        <calumccejcxo9k9zn5omi2hjb9bu18qfesb8t-odxcavw0b7...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hey all,

Two questions I was hoping for assistance with. I'm using a USRP B200, and
have programmed the FPGA with a routine that responds to externally
acquired data. Similar to how I can set radio_clk by setting the
master_clock_rate through gnuradio (or through the terminal), I was
wondering how to declare pass a parameter from software into the fpga
without having to hard code it and recompile each time?

My second question, how do I use the DSP slices to perform multiplication
on the FPGA? I haven't been able to find too many resources online on this
subject.

Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20170416/5984020e/attachment-0001.html>

------------------------------

Message: 4
Date: Sun, 16 Apr 2017 08:49:14 +0200
From: Wouter Jan Ubbels <[email protected]>
To: Marcus M?ller <[email protected]>
Cc: [email protected]
Subject: Re: [USRP-users] Replaying a recording made with specrec in
        grc
Message-ID:
        <CABmbpx5tV5hSQX18vQXfbMJWQuQ+4frMtOwjNY+3PeW=w3l...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi Marcus,

Thanks for your reply. I found out that specrec uses the sc16 format by
default, using gr_fileman to convert the file to fc32 solved the problem!

Regards,

Wouter Jan


Op 15 apr. 2017 8:27 p.m. schreef "Marcus M?ller via USRP-users" <
[email protected]>:

Hi Wouter Jan,

If I remember correctly, specrec is basically a modified rx_samples_to_file
(a recording example from UHD itself), which supports different --type
arguments. Which one did you use? What's the default? (--help)

Best regards,

Marcus

On 15.04.2017 17:11, Wouter Jan Ubbels via USRP-users wrote:

Hi all,

Can anyone point me to a simple tutorial on how to replay a file recorded
with specrec from gr-analysis in grc? I can record a file just fine using
the following syntax:

specrec --freq 98e6 --rate 1e6 --gain 60 usrp_samples.dat

And it seems to record fine at higher sample rates as well without any
overflows (contrary to rx_samples_to_file which does not work well here),
so that?s good!

However, I have not succeeded to replay this file in grc using the file
source block. Any help is appreciated!

Thanks in advance,

Wouter Jan


_______________________________________________
USRP-users mailing
[email protected]http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com



_______________________________________________
USRP-users mailing list
[email protected]
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/20170416/d65fc58d/attachment-0001.html>

------------------------------

Message: 5
Date: Sun, 16 Apr 2017 14:08:23 +0200
From: Marcus M?ller <[email protected]>
To: Wouter Jan Ubbels <[email protected]>
Cc: [email protected]
Subject: Re: [USRP-users] Replaying a recording made with specrec in
        grc
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"

You could also simply read the file with GNU Radio's file source set to
"short", and then convert to complex using GR's "short to float" block.
Set both the file source and the short to float to vlen=2.

Explanation: GNU Radio's default "complex" type is really just one 32bit
float I followed by one 32bit float Q. You can convert the shorts to
floating point numbers individually. The vlen=2 is just a handy option
to avoid having to then copy the single floats just to "relabel" the
item size from 4 Byte to 8 Byte. Really, a GR complex is just "vector"
of 2 floats.

Best regards,

Marcus


On 16.04.2017 08:49, Wouter Jan Ubbels wrote:
> Hi Marcus,
>
> Thanks for your reply. I found out that specrec uses the sc16 format
> by default, using gr_fileman to convert the file to fc32 solved the
> problem!
>
> Regards,
>
> Wouter Jan
>
>
> Op 15 apr. 2017 8:27 p.m. schreef "Marcus M?ller via USRP-users"
> <[email protected] <mailto:[email protected]>>:
>
>     Hi Wouter Jan,
>
>     If I remember correctly, specrec is basically a modified
>     rx_samples_to_file (a recording example from UHD itself), which
>     supports different --type arguments. Which one did you use? What's
>     the default? (--help)
>
>     Best regards,
>
>     Marcus
>
>
>     On 15.04.2017 17:11, Wouter Jan Ubbels via USRP-users wrote:
>>     Hi all,
>>
>>     Can anyone point me to a simple tutorial on how to replay a file
>>     recorded with specrec from gr-analysis in grc? I can record a
>>     file just fine using the following syntax:
>>
>>     specrec --freq 98e6 --rate 1e6 --gain 60 usrp_samples.dat
>>
>>     And it seems to record fine at higher sample rates as well
>>     without any overflows (contrary to rx_samples_to_file which does
>>     not work well here), so that?s good!
>>
>>     However, I have not succeeded to replay this file in grc using
>>     the file source block. Any help is appreciated!
>>
>>     Thanks in advance,
>>
>>     Wouter Jan
>>
>>
>>     _______________________________________________
>>     USRP-users mailing list
>>     [email protected] <mailto:[email protected]>
>>     http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>>     <http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com>
>     _______________________________________________ USRP-users mailing
>     list [email protected]
>     <mailto:[email protected]>
>     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/20170416/1a37c5a0/attachment-0001.html>

------------------------------

Message: 6
Date: Sun, 16 Apr 2017 14:26:56 +0200
From: Nicolas Cuervo <[email protected]>
To: [email protected]
Cc: "[email protected]" <[email protected]>
Subject: Re: [USRP-users] RFNoC: Vivado environment variables not
        persisting during make
Message-ID:
        <CAOuPCvgRKR_0zWQxbW3Xp8arkGgPKLzy9OqpP=buqaednpf...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hello James,

Sorry for taking so much time getting back to you. Your email seems to have
fallen through the cracks. This is very interesting, and for now I can't
reproduce your issue. Could you please tell us what OS are you using?

When you manually source the vivado environment, can you confirm that the
vivado tools are available thereafter? To check this, please set up your
vivado environment, which by your email I see it is located at
[/rfnoc/src/uhd-fpga/usrp3/top/x300/setupenv.sh]. So please run:

    $ source ~/rfnoc/src/uhd-fpga/usrp3/top/x300/setupenv.sh

and then run:
    $ vivado -version

which should just give you the version installed. Just a small sanity check.

In addition, have you tried running any of the other testbenches that are
shipped within the uhd-fpga repository? After setting up your vivado
environment, please go to any of the testbench locations and run the
testbench for the given block. Let's say you run the testbench for the
threshold block, so you go to
~/rfnoc/src/uhd-fpga/usrp3/lib/rfnoc/noc_block_threshold_tb/ (which I chose
randomly, you can choose any of the testbench locations available to run
this test) and within that directory you run:

    $ make xsim

Which will start the testbench. Please let us know if this process finishes
successfully or if it fails with the same error as the one described in
your email.

This is just will check a couple of things: first, if successful, it will
say that the environment is being successfully sourced and that the
environment is not going away unnoticed.  Second, it will determine that
the "sourcing" process and the run of the actual testbench are working as
expected. Third, it will tell us if your Vivado Lab installation is being
accepted by the tools as an acceptable version for running testbenches
(which it should). Basically, it is just sanity checking.

The fact that it initializes the vivado environment and thereafter it says
that it is not found is definitely concerning. After we are certain that
the required software is working as expected, we might dive into the
rfnocmodtool generated block for more specific details.

Regards,
- Nicolas



On Thu, Mar 30, 2017 at 9:19 PM, James Dunn via USRP-users <
[email protected]> wrote:

> Hello,
>
> I am working through the "Creating and running HDL testbenches" section of
> the "Getting Started with RFNoC Development" wiki article, and run into the
> same library problem as this thread describes: http://lists.ettus.com/
> pipermail/usrp-users_lists.ettus.com/2016-February/018671.html
>
> I am able to follow all steps up until make noc_block_gain_tb without
> issue, but when making the block, I see the following:
>
> dunn@bwrcdpt3600-11:~/rfnoc/src/rfnoc-tutorial/build$ make
> noc_block_gain_tb
> Setting up a 64-bit FPGA build environment for the USRP-E3x0...
> - Vivado: Found (/opt/Xilinx/Vivado_Lab/2015.4/bin)
> - Vivado HLS: Found (/opt/Xilinx/Vivado_HLS/2015.4/bin)
>
> Environment successfully initialized.
> BUILDER: Checking tools...
> * GNU bash, version 4.3.46(1)-release (x86_64-pc-linux-gnu)
> * Python 2.7.12
> * ERROR: Vivado not found in environment. Please run setupenv.sh
> /home/dunn/rfnoc/src/uhd-fpga/usrp3/top/../tools/make/viv_preamble.mak:47:
> recipe for target '.check_tool' failed
> make[4]: *** [.check_tool] Error 1
> CMakeFiles/noc_block_gain_tb.dir/build.make:57: recipe for target
> 'CMakeFiles/noc_block_gain_tb' failed
> make[3]: *** [CMakeFiles/noc_block_gain_tb] Error 2
> CMakeFiles/Makefile2:131: recipe for target 
> 'CMakeFiles/noc_block_gain_tb.dir/all'
> failed
> make[2]: *** [CMakeFiles/noc_block_gain_tb.dir/all] Error 2
> CMakeFiles/Makefile2:138: recipe for target 
> 'CMakeFiles/noc_block_gain_tb.dir/rule'
> failed
> make[1]: *** [CMakeFiles/noc_block_gain_tb.dir/rule] Error 2
> Makefile:199: recipe for target 'noc_block_gain_tb' failed
> make: *** [noc_block_gain_tb] Error 2
>
>
> It looks like make is sourcing
> ~/rfnoc/src/uhd-fpga/usrp3/top/x300/setupenv.sh
> and finding the Vivado paths, but immediately afterward is unable to find
> the environment variables. I have tried manually running "source
> ./setupenv.sh" in the above directory, but still get the same error, when
> this seemed to fix the problem in the thread mentioned above. I have also
> sourced ~/rfnoc/setup_env.sh.
>
> We are using an X310 radio, with UHD, GNU Radio, and gr-ettus installed
> per the wiki instructions using PyBOMBS. My login shell is bash, and I have
> pointed sh to bash instead of dash. Our Vivado installation also seems to
> be the correct version. Are there any recommendations on how to get this
> environment variable to persist during make?
>
> Thank you and regards,
> James Dunn
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> 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/20170416/6307650b/attachment-0001.html>

------------------------------

Subject: Digest Footer

_______________________________________________
USRP-users mailing list
[email protected]
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com


------------------------------

End of USRP-users Digest, Vol 80, Issue 16
******************************************

Reply via email to