discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] first weekend compiling gnuradio


From: cfk
Subject: Re: [Discuss-gnuradio] first weekend compiling gnuradio
Date: Fri, 6 Feb 2004 17:00:40 -0800

----- Original Message -----
From: "Matt Ettus" <address@hidden>
To: "cfk" <address@hidden>
Cc: "Ettus, Matt" <address@hidden>; <address@hidden>
Sent: Friday, February 06, 2004 4:26 PM
Subject: Re: [Discuss-gnuradio] first weekend compiling gnuradio


> Quoting cfk <address@hidden>:
>
> >     I can now see in /usr/local/gnuradio/python/GnuRadio some files such
as
> > GnuRadioPython.py. It isnt installed as with executable permissions, but
I
> > did a chmod +x on it and then a ./GnuRadioPython.py (it doesnt appear in
the
> > path), and of course the computer just sits there sticking out its
tongue at
> > me.
>
> GnuRadioPython.py is a library, so there's no need to run it.  If you want
to
> test the install, try the files in src/gnu/python and src/gnu/examples,
like
> full_duplex_audio_demo and test_oscope_display
>
> Matt

All right! It runs full_duplex_audio_demo, audio_scope, benchmark_dotprod
(generic 2e8, sse 5e8), chirp_fft and simple_scope. I get a message about
the missing mc4020 driver from adc3_fft, adc_scope, elenco_fm_demo, hifi_fm
and others, but that OK seeing as how I dont have any hardware yet. It also
doesnt slice & dice, but maybe thats not so bad right now.

That segues into the next question, of course, and that is hardware. Which
to obtain and how to obtain it. I am currently reading all of the 2003 posts
on the mailing list archive. At this point, I am struggling with buying a
PCI-4020 or waiting for a usrb to become available so I can work with it.
Either one requires some delicate negotiations with Annie, W1FE. Any
suggestions will be greatly appreciated.

Charles, WA6LWB





reply via email to

[Prev in Thread] Current Thread [Next in Thread]