discuss-gnuradio
[Top][All Lists]
Advanced

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

Re: [Discuss-gnuradio] Can't set center frequency of USRP2 w/DBSRX


From: Jason Abele
Subject: Re: [Discuss-gnuradio] Can't set center frequency of USRP2 w/DBSRX
Date: Wed, 11 Aug 2010 15:10:30 -0700

On Wed, Aug 11, 2010 at 11:37 AM, Moeller <address@hidden> wrote:
> Call "usrp2_probe" to check if the board ID is 13 now. If it is still 2, the 
> burning had no effect.

Moeller has a very good tip here, we use different daughterboard id's
to let the software know if the resistor modification has been
performed.  So here is a list of things to try:

If you are using the raw-ethernet host code included with gnuradio 3.3
or earlier:

Testing the id number of your DBSRX on USRP2:

1. Insert an SD Card which has been programmed with the raw ethernet
(Raw Ethernet, No WBX or XCVR) txrx.bin and u2_rev3.bin firmwares.
You can get the latest here:
http://ettus-apps.sourcerepo.com/redmine/ettus/projects/public/wiki/U2binaries

2. Apply power and you should see the "D" and "F" leds light up
     if not, your SD Card is incorrectly programmed, try 1 again

3. Use the "find_usrps" command to ensure your USRP2 can be discovered.
     If you get permissions errors, make sure you are the root user or
set the suid bit on
     usrp2_socket_opener as described here:
http://gnuradio.org/redmine/wiki/1/USRP2UserFAQ#Can-the-USRP2-be-used-by-a-non-root-user

4. Run the "usrp2_probe" command to list daughterboard information,
for DBSRX these are the ids you care about:
    2 (0x02) = DBSRXs for USRP1, R193 populated, R194 unpopulated
(factory default)
   13 (0x0D) = DBSRXs for USRP2, R193 unpopulated, R194 populated


If the ID you find is incorrect, you can change it using the following
procedure:

On USRP2, changing to ID 13 (0xD)

1. Program an SD card with burn_dbsrx_eeprom.bin firmware and the raw
ethernet fpga (u2_rev3.bin) and insert it in your USRP2

2. Apply power and you should see all LEDs except "E" light up
    if not, your SD Card is incorrectly programmed, try 1 again

3. Power-off and use the steps above to check that the id is now 13 (0x0D)


On USRP1, changing the ID can be handled by installing the DBSRX on
Side A and using the following command:
<SRCDIR>/usrp/host/apps/burn-db-eeprom -f -A -t [dbsrx|dbsrx_clkmod]
     Choose dbsrx for ID = 2 USRP1, choose dbsrx_clkmod for ID = 13
(0x0D) for USRP2

You can check the daughterboard IDs on a USRP1 using the usrp_probe command


The good news is, the UHD works with USRP2 more like a USRP1 in this
regard, so daughterboard IDs can be changed via the host, no need for
changing SD cards.  You can find out how to do the DBSRX modification
for USRP2 with UHD here:
http://www.ettus.com/uhd_docs/manual/html/dboards.html#daughterboard-modifications

And UHD offers the uhd_usrp_probe command to see what daughterboards
are installed and their ids.

Amee,

I know you have worked on this for a while now, I hope that helps
clear things up for you and please do let me know if you get it
working or which step above fails for you.

Thanks
Jason



reply via email to

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