[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Discuss-gnuradio] Booting a new USRP
From: |
Eric Blossom |
Subject: |
Re: [Discuss-gnuradio] Booting a new USRP |
Date: |
Fri, 11 Feb 2005 13:20:11 -0800 |
User-agent: |
Mutt/1.5.6i |
On Fri, Feb 11, 2005 at 01:15:54PM -0500, Rahul Dhar wrote:
> Charles,
>
> On Fri, Feb 11, 2005 at 09:57:04AM -0800, cfk wrote:
> > Dear Rahul
> > The program test_fusb is not installed in the computer's path. I can be
> > found
> > in ../usrp/host/apps along with several others such as
> > test_usrp_standard_tx
> > and test_usrp_standard_rx. In all three cases these programs are invoked by
> > navigating to the ../usrp/host/apps directory and typing:
> >
> > ./test_usrp_standard_tx
> >
> > The "./" means execute the program in the current directory and not to
> > search
> > the computer's path. You can see your path with the command "echo $PATH"
> > from
> > a terminal prompt.
>
> As I said, test_fusb isn't anywhere on my hard disk (or find was lying
> to me). Anyways, I ran test_usrp_standard_tx and got the following:
> TX d'board A: <none>
> TX d'board B: <none>
> tx_underrun
> tx_underrun
> tx_underrun
> tx_underrun
> tx_underrun
> xfered 5.37e+08 bytes in 16.8 seconds. 3.2e+07 bytes/sec. cpu time =
> 1.93
> 5 underruns
This looks fine.
> I'm assuming this means the firmware was uploaded properly.. LED0's
> blinking rate slowed to about 1 Hz, as expected. However, LED1 doesn't
> seem to work. "usrper led1 on" doesn't do anything. "usrper led0 on",
> however, makes LED0 turn back on sooner than it should, and it then
> resumes blinking at 1 Hz. led0 off does the opposite.
> "./usrper 9862a_read 1" also works as expected.
>
> Is there something additional I need to do to get LED1 working?
No. Don't worry about it.
The usrper command twiddles some very low level stuff.
It's not a tool for everyday use.
Take a look at the examples in gnuradio-example/python/usrp*
usrp_siggen.py is a siggen with no gui.
usrp_fft.py plots the FFT of whatever's connected to the input.
$ usrp_siggen.py --help
$ usrp_fft.py --help
Using usrp_siggen.py you should be able to see your waveform with a
scope attached to the SMA connectors.
Eric
- Re: [Discuss-gnuradio] Booting a new USRP, (continued)
- Re: [Discuss-gnuradio] Booting a new USRP, cfk, 2005/02/05
- Re: [Discuss-gnuradio] Booting a new USRP, Matt Ettus, 2005/02/05
- Re: [Discuss-gnuradio] Booting a new USRP, cfk, 2005/02/05
- [Discuss-gnuradio] Bug in usrper.cc, Berndt Josef Wulf, 2005/02/08
- Re: [Discuss-gnuradio] Bug in usrper.cc, Eric Blossom, 2005/02/08
- Re: [Discuss-gnuradio] Booting a new USRP, Rahul Dhar, 2005/02/11
- Re: [Discuss-gnuradio] Booting a new USRP, cfk, 2005/02/11
- Re: [Discuss-gnuradio] Booting a new USRP, Rahul Dhar, 2005/02/11
- [Discuss-gnuradio] usrp_oscope.py, cfk, 2005/02/11
- Re: [Discuss-gnuradio] usrp_oscope.py, Eric Blossom, 2005/02/11
- Re: [Discuss-gnuradio] Booting a new USRP,
Eric Blossom <=
- Re: [Discuss-gnuradio] Booting a new USRP, John Gilmore, 2005/02/18
- Re: [Discuss-gnuradio] Booting a new USRP, Eric Blossom, 2005/02/18
- Re: [Discuss-gnuradio] Booting a new USRP, John Gilmore, 2005/02/19
- Re: [Discuss-gnuradio] Booting a new USRP, Matt Ettus, 2005/02/19
- Re: [Discuss-gnuradio] Booting a new USRP, Eric Blossom, 2005/02/19
- Re: [Discuss-gnuradio] Booting a new USRP, Eric Blossom, 2005/02/11
Re: [Discuss-gnuradio] FC3 build problems, Chris, 2005/02/04