Forum: GNU Radio USRP2 &DBSRX testing

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
RH200 (Guest)
on 2009-02-22 16:17
(Received via mailing list)
We have got a new USRP2 and TVRX and DBSRX recievers. Though the system
seems
to work when the TVRX daughter board is installed using the USRP2 fft
script, it does not seem to work with the DBSRX board installed.

That is there seems to be just noise coming in regardless of what
frequency
or bandwidth setting you are using. Does any one know of any special
tricks
when using the DBSRX board?


Regards
--
View this message in context:
http://www.nabble.com/USRP2--DBSRX-testing-tp22116...
Sent from the GnuRadio mailing list archive at Nabble.com.
Eric B. (Guest)
on 2009-02-22 20:09
(Received via mailing list)
On Sun, Feb 22, 2009 at 06:16:28AM -0800, RH200 wrote:
> Regards
Attention everybody!

When asking questions, it _really helps us help you_ if you tell us
some basic information about your situation.  At a minimum, tell us
what version of GNU Radio you are running: tarball (which one) or
trunk (which rev), your OS/version/distribution and architecture.

In your specific case, which firmware are you running?  Did you build
it from source, or did you download it?  Off the top of my head, I'm
not sure when the support for the DBSRX went into the trunk, but it's
there.

What daughterboard_id does usrp2_fft report?

Eric
Bruce Stansby (Guest)
on 2009-02-23 03:12
(Received via mailing list)
My apologies, newbie hoping it was a common newbie problem, details as
follows.

Hardware:
         Twin Xeon quadcore X5355 processors.
         Supermicro X7DBE motherboard
         8 GB of ram

Software:
         Ubuntu 8.04 Kernal 2.6.2-16-generic

I didn't install the software my supervisor did (he knows what he's
doing) but he used the latest from the trunk a few days ago, as the
tarball he originally used didn't show any USRP2 items.

If these a way to find a version number of the installed software please
let me know.

The memory card had the original version software on it and after it
didn't work he upgrade it with UR2_rev3 & txrx.bin.

Not sure about the where the daughter board_id shows up but I'm
presuming its the hex type number after the FS@Gbe sequence.

if so with the dbrx installed then its returning 0X001 also we are
getting Analog BB:0 and DDC:0, also there is no gain slider. When the
tvrx is installed we are getting 0X0040 anolog BB:756M  DDC: 44M, and
the gain slider is present.

At a uninformed guess I am wondering if the dbrx is talking to the
usrp2?

At the moment I'm trying to install the grc package but unfortunitly I
can't seem to get python lxml 2.00 to install.

Regards


----- Original Message -----
From: Eric B. <removed_email_address@domain.invalid>
Date: Monday, February 23, 2009 3:08 am
Subject: Re: [Discuss-gnuradio] USRP2 &DBSRX testing
To: RH200 <removed_email_address@domain.invalid>
Cc: removed_email_address@domain.invalid
Johnathan C. (Guest)
on 2009-02-23 16:40
(Received via mailing list)
On Sun, Feb 22, 2009 at 5:11 PM, Bruce Stansby
<removed_email_address@domain.invalid> wrote:

> The memory card had the original version software on it and after it
> didn't work he upgrade it with UR2_rev3 & txrx.bin.

The code for the DBSRX board in the USRP2 has been written and is in
the trunk firmware as of r10392.  However, we have not made a
pre-compiled firmware image available yet that has this in it.  You
can get the compile included in the GNU Radio compilation by having
the mb-gcc compiler installed.  See the section:

"How do I compile the firmware for the aeMB RISC processor?"

in:

http://gnuradio.org/trac/wiki/USRP2UserFAQ

Alternatively, I'll be posting an updated firmware image in the next few
days.

Johnathan
Matt E. (Guest)
on 2009-02-25 00:05
(Received via mailing list)
There are some minor mods necessary to work with the DBSRX.  I will get
you instructions and working code in a day or two.

Thanks for your patience,
Matt
Matt E. (Guest)
on 2009-03-04 14:18
(Received via mailing list)
Bob Taylor wrote:
> Matt,
>
> I'm also attempting to get a DBSRX working in a USRP2, and am looking
> forward to obtaining the instructions and code. Any chance they're already
> available somewhere and I missed them?

Sorry for the delay.

This will only work if you have a DBSRX which says "Rev 2.2".  This
should be most units from 2007, and everything from 2008 or 2009.  It
will not work with older DBSRX boards.  For those, there is no way to
use them with the USRP2.

There are 2 steps to the process:

1 - Put the DBSRX on a USRP1 on Side A, connect it to a computer, and
run the command:

  burn-db-eeprom -A --force -t dbsrx2


2 - Remove R193 (which is 10 ohms, 0603 size) and put it on R194, which
is empty.  This is made somewhat more complicated by the fact that the
silkscreen is not clear in that area.  R193 is on the back, immediately
below the large beige connector, J2.  R194 is just below, and to the
left of R193.  The silkscreen for R193 is ok, but for R194, it is upside
down, and partially cut off.

If you lose R193, you can use anything from 0 to 10 ohms there.

Matt
Johnathan C. (Guest)
on 2009-03-04 18:52
(Received via mailing list)
I put the DBSRX modification instructions up at:

http://gnuradio.org/trac/wiki/USRP2/DBSRXModification

Johnathan
karim (Guest)
on 2009-03-04 19:14
(Received via mailing list)
Hi everyone,
I am new to gnuradio, so this may be basic. Searching online, I couldn't
find a solution (other than advising to ditch the PC I am using :) )

I am running the usrp_siggen.py script to generate a sin wave using the
2.4GHz board and I get the following error when running the script:
uUuU == USRP underrun (not enough sample ready to send to USRP sink)

The documentation on: http://gnuradio.org/trac/wiki/UsrpFAQ/Gen

says to avoid cache crippled PC :) (is there another solution to this?)

I have an HP laptop and am running Ubuntu:
Description:    Ubuntu 8.04.2
Release:        8.04
Codename:       hardy

with the following CPU specs:
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 15
model name      : Intel(R) Core(TM)2 Duo CPU     T7500  @ 2.20GHz
stepping        : 11
cpu MHz         : 800.000
cache size      : 4096 KB
physical id     : 0
siblings        : 2
core id         : 0
cpu cores       : 2
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 10
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm
constant_tsc arch_perfmon pebs bts pni monitor ds_cpl vmx est tm2 ssse3
cx16 xtpr lahf_lm ida
bogomips        : 4393.71
clflush size    : 64

processor       : 1
vendor_id       : GenuineIntel
cpu family      : 6
model           : 15
model name      : Intel(R) Core(TM)2 Duo CPU     T7500  @ 2.20GHz
stepping        : 11
cpu MHz         : 800.000
cache size      : 4096 KB
physical id     : 0
siblings        : 2
core id         : 1
cpu cores       : 2
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 10
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm
constant_tsc arch_perfmon pebs bts pni monitor ds_cpl vmx est tm2 ssse3
cx16 xtpr lahf_lm ida
bogomips        : 4388.83
clflush size    : 64




Cheers,
Karim
Johnathan C. (Guest)
on 2009-03-04 19:27
(Received via mailing list)
On Wed, 2009-03-04 at 09:04 -0800, karim wrote:

> model name      : Intel(R) Core(TM)2 Duo CPU     T7500  @ 2.20GHz

This is fine.

> cpu MHz         : 800.000

This is not.  You need to set your power settings to "performance" mode
to keep your clock at 2.2GHz.

Johnathan
This topic is locked and can not be replied to.