Greetings. I am trying to understand the usrp programming syntax so that
I can add USRP support into GRC. Below are a few code snippets from the
USRP sample codes. It seems that rx_subdev_spec can be a tuple (0, 0) or
(1, 0). Would this mean that for tx modules, the tx_subdev_spec is (1,
1) or
On Sun, Jan 07, 2007 at 03:13:28AM -0500, Josh Blum wrote:
> Greetings. I am trying to understand the usrp programming syntax so that
> I can add USRP support into GRC.
What's "GRC"?
> Below are a few code snippets from the
> USRP sample codes. It seems that rx_subdev_spec can be a tuple (0, 0)
Hi,
for those interested in DAB and OFDM, I posted the results of my
student project (including data files) to:
http://www.1c3.de/dab/
I noticed that there has been some work on OFDM in the development
branch, too.
A big "thanks you" to everybody on the list, I learnt a lot about
software radi
On Wed, Jan 03, 2007 at 01:01:36AM -0800, Dan Halperin wrote:
> Hi,
>
> I'm trying to get the code together to enable the RFX2400 board from a
> C++ program. I'm mostly looking in usrp.py, usrp1.py, db_base.py, and
> db_flexrf.py and copying commands like write_io and write_oe into their
> C++ ver
On Sun, Jan 07, 2007 at 06:03:53PM -0500, Josh Blum wrote:
> GRC is my little graphical interface for gnu radio.
> http://www.joshknows.com/?key=grc
Thanks.
> I want to add graphical source/sink for the USRP. So, I am trying to
> figure out a generic way to make a USRP source/sink given a bunch
Thanks.
I've been getting problems compiling the resultant *_wrap.c file after
adding %include"std_string.i".
gcc version 3.4.3 says it can't find .
Explicitly including the directory -I/usr/include/c++/3.4.3 in the gcc
command doesn't work.
Neither does changing the *_wrap.c filename to *_w
