Send USRP-users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of USRP-users digest..."
Today's Topics:
1. Synchronizing Data Streams from multiple N210 boards on FPGA
(Yasir Javed)
2. USRP1 o USRP B100 (paco paquito)
3. Windows 7 64 bit build issues : bin folder is not copied by
INSTALL build, USRP not found (Bastien Auneau)
4. Windows 7 64 bit build issues (Stan Gamla)
5. Re: Windows 7 64 bit build issues (Simon HB9DRV)
6. Re: Windows 7 64 bit build issues (Simon HB9DRV)
7. Re: USRP1 o USRP B100 (Dan CaJacob)
8. Re: USRP1 o USRP B100 (Nick Foster)
9. Re: does ubuntu 12.04 works for USRP N210? (Gerardo Moreno)
10. FW: Config N210 with Microblaze (Huldi Michael)
11. DSBRX with N210 (Alexander Olihovik)
12. Re: DSBRX with N210 (Jason Abele)
13. Re: DSBRX with N210 ([email protected])
14. Re: does ubuntu 12.04 works for USRP N210? (Josh Blum)
----------------------------------------------------------------------
Message: 1
Date: Mon, 11 Jun 2012 03:01:22 +0500
From: Yasir Javed <[email protected]>
To: [email protected]
Subject: [USRP-users] Synchronizing Data Streams from multiple N210
boards on FPGA
Message-ID:
<cajfaspxwqfkmbejk4gdzdgrmjqusz4vpjtoxw5mygo905my...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
We are working on a MIMO-OFDM system using two USRP N210s. We want our
Synchronization algorithm to be implemented on FPGA instead of Software.
The algorithm needs to process coherent DDC data samples from both boards.
Is it possible to forward data from one N210 to another where I can
implement the Synchronization logic?
If so, how can I make one FPGA logic wait until I get samples at almost
exactly the same time instant from the other board?
At what points in the verilog code would you suggest to make changes?
My understanding so far is that I can modify dsp_rx_glue.v to add custom
processing on DDC out samples (bb_sample and bb_strobe). What I am not
clear is where would I get samples from the other N210 board. My initial
guess was to use MIMO cable. But it seems that MIMO cable is used for
sharing timing information to synchronize capturing time, its not used for
data transfers (Is my understanding right?). So the next solution I could
think of was to send packets from one N210 to other. I am so far unable to
figure out where I would be able to intercept data in that case. Secondly
by the time one N210 is waiting for samples from other N210, the DDC out
samples have to be saved somewhere (in a FIFO).. Is the network delay
deterministic to decide a safe FIFO size? Thirdly, My understanding is that
timing information is added in vita_rx_chain.v which comes after
dsp_rx_glue.v where I can get DDC out samples, how can I figure out the
timing information of DDC samples from both boards in dsp_rx_glue.v?
Am I missing some simpler way to do this?
Regards,
Yasir Javed
IQRA University
Islamabad
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120611/37240b0c/attachment-0001.html>
------------------------------
Message: 2
Date: Mon, 11 Jun 2012 11:18:30 +0100 (BST)
From: paco paquito <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [USRP-users] USRP1 o USRP B100
Message-ID:
<[email protected]>
Content-Type: text/plain; charset=utf-8
Hi,
I'm thinking in buy a USRP, USRP1 or USRP B100, for educational purposes.
I would like to put in practice what I have learnt theoretically.
A think I would like to do is work with RFID (13.56 MHz). In this case I need
to emit and receive the signal, so I need BasicTX and BasicRX, or LFTX and LFRX.
I would like to know if in B100 I can use BasicTX and BasicRX (or the other
ones) at the same time or I need USRP1 that permit two daughterboards.
Thanks.
------------------------------
Message: 3
Date: Mon, 11 Jun 2012 11:30:24 +0000
From: Bastien Auneau <[email protected]>
To: [email protected], [email protected]
Subject: [USRP-users] Windows 7 64 bit build issues : bin folder is
not copied by INSTALL build, USRP not found
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hi Josh
You said :
You should tell CMake configure to use the MSVC 64 bit compiler. You
shouldnt need to change or set any flags. It will just work (tm)
But if I do that, it complains about mismatch architecture
But maybe it is only due to the additional flags set to /Machine:X86
I will try to build using
DevEnv uhd.sln /build Debug /project ALL_BUILD
Best Regards
Bastien
------------------------------
Message: 4
Date: Mon, 11 Jun 2012 13:55:08 +0200
From: Stan Gamla <[email protected]>
To: <[email protected]>
Cc: 'Bastien Auneau' <[email protected]>
Subject: [USRP-users] Windows 7 64 bit build issues
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
Simon,
Building under Windows 7 is quite an effort but to do so with full 64-bit
support is an outstanding achievement (at least in my humble opinion and
based on my own failures). As it took you two weeks to "bring it all
together", could you please share any tricks and tips that you might have
discovered or developed along the way (and that perhaps are not documented
elsewhere). For example, which dependencies were needed and which in turn
were built from source (and with with special options).
Thanks in advance,
Stan
_____
From: [email protected]
[mailto:[email protected]] On Behalf Of Simon HB9DRV
Sent: 07 June 2012 18:20
To: 'Bastien Auneau'; [email protected]
Subject: Re: [USRP-users] Windows 7 64 bit build issues : bin folder is
notcopied by INSTALL build, USRP not found
Hi,
Over the last two weeks I've been through the Windows 64-bit integration
process. In my case I'm using the latest unstable Debug and Release builds.
I used VS2010
I built Boost from source
I have to use shared CTRL and MFC in the executable because UHD.dll can only
be used this way
I am now able to use UHD.dll and ship to my software commercial customers
without worrying about the USRP support issues. I'm able to get a reliable
20MHz bandwidth using complex floats from a WBX board with a 2.8GHz CPU
(i7).
Simon Brown, HB9DRV
<http://dit-dit-dit.com/> http://dit-dit-dit.com
You are standing at the end of a road before a small brick building. Around
you is a forest.
A small stream flows out of the building and down a gully. The sunspot count
is 285.
From: [email protected]
[mailto:[email protected]] On Behalf Of Bastien Auneau
Sent: 07 June 2012 16:14
To: [email protected]
Subject: [USRP-users] Windows 7 64 bit build issues : bin folder is not
copied by INSTALL build, USRP not found
Hi All
I am building UHD 3.4.2 from last stable release, under Windows 7 64bit, VS
2008, using boost 1.49.0 (compiled it myself)
To get UHD 64 bit debug, I've done :
_ applied patch described here :
http://comments.gmane.org/gmane.comp.hardware.usrp.e100/3420
(without this patch, there are some DLL load problems)
_ in Cmake
- Release to Debug
- set path to boost lib
- changed /machine:X86 to /machine:X64 (3 rows)
- changed /Dwin32 flags to /Dwin64 (2 rows)
_ changed active platform from win32 to x64 in VS (and this for all
sub-projects)
_ ALL_BUILD -> build UHD compiles and link fine
_ INSTALL -> build, the bin folder is not copied to the target
_ I copy uhd.dll manually, and uhd_find_devices.exe
running uhd_find_devices.exe gives :
__________________
C:\Program Files\UHD>uhd_find_devices.exe
Win32; Microsoft Visual C++ version 9.0; Boost_104900;
UHD_003.004.002-0-unknown
No UHD Devices Found
C:\Program Files\UHD>pause
Press any key to continue . . .
___________________
while when I'm trying with an older build, 32 bits, the device is found :
___________________
C:\Program Files (x86)\UHD_3_3_1_vc9_debug\bin>uhd_find_devices.exe
Win32; Microsoft Visual C++ version 9.0; Boost_104700;
UHD_003.003.001-unknown
--------------------------------------------------
-- UHD Device 0
--------------------------------------------------
Device Address:
type: usrp2
addr: 192.168.10.3
name:
serial:
C:\Program Files (x86)\UHD_3_3_1_vc9_debug\bin>pause
Press any key to continue . . .
_________________________
My questions are :
_ why device is not found with 64 bit version ?
_ How can I avoid setting manually x64 for each sub-project in VS 2008 ?
_ Why 64 bit version still prints Win32 on the command line ? Should I just
ignore that ?
_ What is the patch applied really doing ?
Thanks and Regards
Bastien
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120611/d39fd93f/attachment-0001.html>
------------------------------
Message: 5
Date: Mon, 11 Jun 2012 14:12:50 +0200
From: "Simon HB9DRV" <[email protected]>
To: <[email protected]>
Subject: Re: [USRP-users] Windows 7 64 bit build issues
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
Hi,
Will do. BTW - two weeks included work on my own software. For a Windows
purist the UHD.dll architecture is 'unusual', the steps needed to use it in
a major project just aren't documented. In my case I have many DLLs (one per
manufacturer/radio model) with a common set of exported functions, these
DLLs are loaded dynamically. This caused some nice problems to be overcome.
What I'll do is update a blog on my dit-dit-dit.com website, but it's clear
that Windows support s weak when compared to the many other interface
libraries I use (CodeJock, Intel IPP, .). Ideally Ettus would provide
interface documentation so that a lean, clean and well-written interface can
be created. (If you browse the source you will find some unpleasant
eye-openers. As a developer of 30+ years I would reject the source.)
But - now that I have been through the hoops I'm prepared to release my code
for in-house testing, but am still unhappy with UHD.dll and the lack of
low-level documentation. Ettus does describe the hardware as test equipment,
with better documentation it could be used well in the real world.
I'll update now, will report back.
Simon Brown, HB9DRV
<http://dit-dit-dit.com/> http://dit-dit-dit.com
You are standing at the end of a road before a small brick building. Around
you is a forest.
A small stream flows out of the building and down a gully. The sunspot count
is 285.
From: Stan Gamla [mailto:[email protected]]
Building under Windows 7 is quite an effort but to do so with full 64-bit
support is an outstanding achievement (at least in my humble opinion and
based on my own failures). As it took you two weeks to "bring it all
together", could you please share any tricks and tips that you might have
discovered or developed along the way (and that perhaps are not documented
elsewhere). For example, which dependencies were needed and which in turn
were built from source (and with with special options).
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120611/27caaf76/attachment-0001.html>
------------------------------
Message: 6
Date: Mon, 11 Jun 2012 15:30:28 +0200
From: "Simon HB9DRV" <[email protected]>
To: "'Stan Gamla'" <[email protected]>, <[email protected]>
Cc: 'Bastien Auneau' <[email protected]>
Subject: Re: [USRP-users] Windows 7 64 bit build issues
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
Hi Stan,
My notes are here:
http://dev.dit-dit-dit.com/Blog/tabid/88/post/ettus-research-notes/Default.a
spx
If you need help let me know. I think I have addressed all the issues you
will can come across.
Simon Brown, HB9DRV
<http://dit-dit-dit.com/> http://dit-dit-dit.com
You are standing at the end of a road before a small brick building. Around
you is a forest.
A small stream flows out of the building and down a gully. The sunspot count
is 285.
From: Stan Gamla [mailto:[email protected]]
Building under Windows 7 is quite an effort but to do so with full 64-bit
support is an outstanding achievement (at least in my humble opinion and
based on my own failures). As it took you two weeks to "bring it all
together", could you please share any tricks and tips that you might have
discovered or developed along the way (and that perhaps are not documented
elsewhere). For example, which dependencies were needed and which in turn
were built from source (and with with special options).
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120611/7a0769f2/attachment-0001.html>
------------------------------
Message: 7
Date: Mon, 11 Jun 2012 09:36:29 -0400
From: Dan CaJacob <[email protected]>
To: paco paquito <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [USRP-users] USRP1 o USRP B100
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
The B100 only takes one daughter card.
But if you use a WBX daughter card, you can RX and TX with a single card.
On 06/11/2012 06:18 AM, paco paquito wrote:
> Hi,
>
> I'm thinking in buy a USRP, USRP1 or USRP B100, for educational purposes.
> I would like to put in practice what I have learnt theoretically.
>
> A think I would like to do is work with RFID (13.56 MHz). In this case I need
> to emit and receive the signal, so I need BasicTX and BasicRX, or LFTX and
> LFRX.
>
> I would like to know if in B100 I can use BasicTX and BasicRX (or the other
> ones) at the same time or I need USRP1 that permit two daughterboards.
>
>
> Thanks.
>
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
------------------------------
Message: 8
Date: Mon, 11 Jun 2012 06:41:45 -0700
From: Nick Foster <[email protected]>
To: paco paquito <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [USRP-users] USRP1 o USRP B100
Message-ID:
<CALALHJX2EfafxZaFv6OaF2BWFu0=tyyxzp0ssreqyhewi63...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
The USRP N2x0, B100, E1x0 will all take separate TX and RX daughterboards
which can be used simultaneously, or a single combined TX/RX daughterboard
like WBX, SBX, etc.
HTH,
--n
On Mon, Jun 11, 2012 at 3:18 AM, paco paquito <[email protected]> wrote:
> Hi,
>
> I'm thinking in buy a USRP, USRP1 or USRP B100, for educational purposes.
> I would like to put in practice what I have learnt theoretically.
>
> A think I would like to do is work with RFID (13.56 MHz). In this case I
> need to emit and receive the signal, so I need BasicTX and BasicRX, or LFTX
> and LFRX.
>
> I would like to know if in B100 I can use BasicTX and BasicRX (or the
> other ones) at the same time or I need USRP1 that permit two daughterboards.
>
>
> Thanks.
>
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120611/c2afcfe4/attachment-0001.html>
------------------------------
Message: 9
Date: Mon, 11 Jun 2012 14:02:37 +0000 (UTC)
From: Gerardo Moreno <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] does ubuntu 12.04 works for USRP N210?
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Josh Blum <josh@...> writes:
>
>
> On 05/16/2012 12:21 PM, Weixian Zhou wrote:
> > I tried to build gnuradio and setup USRP N210 on ubuntu 12.04. When I ran
> > uhd_usrp_probe it always said:
> > * linux; GNU C++ version 4.6.3; Boost_104601;
> > UHD_003.004.001-129-g23344268*
> > * -- Opening a USRP2/N-Series device...*
> > * Error: RuntimeError:*
> > * Please update the firmware and FPAG images for your device.*
> > * See the application notes for USRP2/N-Series for instructions.*
> > * Expected FPGA compatibility number 10, but got 9:*
> > * The FPGA build is not compatible with the host code build.*
> > Is there a version of firmware and FPAG that compatible with Ubuntu 12.04?
> >
> >
>
> The firmware and FPGA images are agnostic to the OS.
>
> It looks like you built UHD from the master branch?
>
> Follow the post install instructions to get the correct images:
>
http://code.ettus.com/redmine/ettus/projects/uhd/wiki/UHD_Build#Firmware-and-FPGA-images
>
> and burn to the device:
>
http://files.ettus.com/uhd_docs/manual/html/usrp2.html#load-the-images-onto-the-on-board-flash-usrp-n-series-only
>
> The good news is that this will be more automated in the near future.
>
> -josh
>
> >
> >
> > _______________________________________________
> > USRP-users mailing list
> > USRP-users@...
> > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
Hello there,
I'm facing similar issues with the uhd drivers UHD_OO3.004.002.
I,ve downloaded and installed these drivers
uhd_003.004.002-150-unstable_Ubuntu-11.10-x86_64.deb from
http://files.ettus.com/binaries/uhd_unstable/latest/
also,
I've loaded the following images to my USRP N200 box:
uhd-images_003.004.002-release.tar.gz
from the same URL listed above and when I try to run ./tx_samples_from_file from
../uhd/host/build/examples, I get the following error
Error: RuntimeError:
Please update the firmware and FPGA images for your device.
See the application notes for USRP2/N-Series for instructions.
Expected FPGA compatibility number 10, but got 9:
The FPGA build is not compatible with the host code build.
Please run:
"/usr/local/share/uhd/utils/usrp_n2xx_net_burner_gui.py" \
--fpga="/usr/local/share/uhd/images/usrp_n200_r2_fpga.bin" \
--fw="/usr/local/share/uhd/images/usrp_n200_fw.bin" \
--addr="192.168.10.3"
It seems like the latest uhd FPGA images available are lagging the current uhd
driver version.
Please advice,
BR,
Gerardo
------------------------------
Message: 10
Date: Mon, 11 Jun 2012 16:38:35 +0200
From: Huldi Michael <[email protected]>
To: "'[email protected]'" <[email protected]>
Subject: [USRP-users] FW: Config N210 with Microblaze
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
Hi,
I give you right that the problems with the tools of Xilinx not your issue is.
But fact is if I add a elf-file from microblaze to a ise-project and generate
the .bit file for an other hardware than USRP N210 so I can download the
generated download.bit file via Jtag and it works.
But if I generate the download.bit file on the same way and convert the
generated download.bit file with the command "promgen -u 0x0 download.bit -p
bin -w " to a .bin file, the net-burner doesn't accept the file.
Do you have an idea how I can solve this problem on a simple way. Because to
write some extra zpu-firmware is too complex.
Thanks Michael
From: Ian Buckley [mailto:[email protected]]
Sent: Donnerstag, 7. Juni 2012 18:54
To: Huldi Michael
Cc: '[email protected]'
Subject: Re: [USRP-users] Config N210 with Microblaze
Michael, I'm a little confused by what your actual question is? It seems your
having fundamental tactical problems loading a new FPGA image onto the N210,
but the question you pose is architectural: "Is it possible to program the fpga
with impact via JTAG? How could I insert the zpu firmware file in this case?"
I'm not going to address your problems with using the Xilinx Microblaze SDK,
that's a Xilinx proprietary flow and not something I, nor anyone at Ettus uses.
But I'll try to give you some architectural guidelines how to add a new
microprocessor to the N210:
First, yes it's entirely possible to use impact to program the FPGA, this is
how all new H/W is initially brought up. However note that unless you design
the H/W to have an attached FLASH RAM in a way supported by impact for JTAG
programming then you are only to directly configure the FPGA and that
configuration will be lost every power cycle/reset. The USRP SPI flash is not
programable via impact, so all non-volatile FPGA images and firmware images
have to be burned under firmware & FPGA control.
Now to boot an embedded microprocessor there are generally 2 different
approaches:
1) The boot vector (PC after reset) directly addresses a discrete FLASH RAM
that you can program externally (normally via JTAG)...this option doesn't exist
for unmodified N210 H/W.
2) The boot vector addresses an internal stable boot ROM (a pre-initialized
BRAM in a Xilinx) and the microcode in there performs a second stage boot,
getting more firmware from elsewhere (FLASH RAM, network etc). This is how the
stock N210 works with the ZPU and the attached SPI flash, which contains
multiple FPGA and firmware images. In this case the ZPU boot's with the bootrom
code in one BRAM, and uses this code to load the production firmware ware image
from SPI FLASH to the other at which point it does a quick FPGA logic trick,
swaps the MSB of the 2 BRAM's so that the boot vector now points to the other
BRAM and toggles the ZPU reset line to cause a new (ZPU not FPGA) boot.
Since you already have a working bootable and upgradable system in the stock
N210, I strongly suggest the following approach:
1) Add your second microprocessor (I suggest reusing the ZPU, firmware
libraries and tools..but you may have a compelling reason to learn and use
Xilinx microblaze SDK) to the existing FPGA build methodology and continue to
use the Ettus Makefile driven scripts to build and upload a new FPGA image via
the network.
2) Make the BRAM(s) that contain the firmware for your new microprocessor exist
also in the existing ZPU memory map. You can do this either by multiplexing
them or making use of the dual port nature of BRAM.
3) Write some extra firmware for the existing ZPU so that it handles the
download of your new microprocessors firmware from network to SPI flash and
from SPI flash to BRAM exploiting all the TCP/IP based updater code that
already exists. Boot your second microprocessor after and under the control of
the original ZPU.
This will be less work than you imagine since you will essentially be able to
re-use all Josh's existing firmware code and the H/W design idea's behind the
N210. You'll have a system quickly where you will not have to rebuild the FPGA
every time you change firmware.
Hope this helps,
-Ian
On Jun 7, 2012, at 5:53 AM, Huldi Michael wrote:
Hello,
I need help to get a simple microblaze configuration with bram-memory working
with the USRP N210 release_003_004_001.
I removed the tx chain and insert the microblaze in the top and connect 2 of
the leds from the front to the microblaze gpio. Run a software with a blinking
led function.
I tried different ways to program the fpga without success:
1. add the elf-file from the microblaze to the ise-project and generate a .bin
File with double click to "generate programming file" in ise, then download
with net burner.
2. combine the bitstream with the elf file, which resides in the bram in SDK
with "Programm FPGA" to a .bit file, then convert the generated file
download.bit to a .bin file with "promgen -u 0x0 download.bit -p bin -w " and
try to download with net burner. But the net burner says "Invalid FPGA image
file".
3. Download with Platform Cable and with SDK, JTAG connected to the FPGA. But
here it doesn't load the new configuration, since the leds I disconnect still
light up in startup.
I also changed the StartUpClk in the bitgen.ut from JTAGCLK to CCLK.
Someone have an idea, how to make my configuration working? Is it possible to
program the fpga with impact via JTAG? How could I insert the zpu firmware file
in this case?
Thanks for your help!
Huldi
_______________________________________________
USRP-users mailing list
[email protected]<mailto:[email protected]>
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120611/78ad9cf9/attachment-0001.html>
------------------------------
Message: 11
Date: Mon, 11 Jun 2012 11:08:07 -0400
From: Alexander Olihovik <[email protected]>
To: [email protected]
Subject: [USRP-users] DSBRX with N210
Message-ID:
<CAFkrSAeYi0QPm_K2cuMs2oxWWG+qF6ZtToOqGYVWnOxWHx=y...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Does anyone have helpful information as to whether the DSBRX is compatible
with the USRP N210?
All I've found thusfar is schematics of the DSBRX.
The specific output of the program (and the problem) I'm trying to run is:
-----------------------------------------------------------------------------
linux; GNU C++ version 4.6.3; Boost_104601; UHD_003.004.002-133-gb61a1103
Using Volk machine: sse4_1_64
-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
UHD Warning:
DBSRX: incorrect dbid
Expected dbid 0x000D and R194
found dbid == DBSRX (0x0002)
Please see the daughterboard app notes
UHD Warning:
DBSRX: Tuning exceeded vco range, _max2118_write_regs.osc_band == 0
UHD Error:
The daughterboard manager encountered a recoverable error in init.
Loading the "unknown" daughterboard implementations to continue.
The daughterboard cannot operate until this error is resolved.
AssertionError: _max2118_read_regs.adc != 0
in double dbsrx::set_lo_freq(double)
at /home/aolihovik/GNU_Radio/uhd/host/lib/usrp/dboard/db_dbsrx.cpp:382
-----------------------------------------------------------------------------
Any help is greatly appreciated!
Best regards,
Alex
--
*Alex Olihovik
University of Virginia 2013
BS Electrical Engineering
BS Computer Engineering
[email protected]*
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120611/562f0074/attachment-0001.html>
------------------------------
Message: 12
Date: Mon, 11 Jun 2012 08:13:37 -0700
From: Jason Abele <[email protected]>
To: Alexander Olihovik <[email protected]>
Cc: [email protected]
Subject: Re: [USRP-users] DSBRX with N210
Message-ID:
<cadspesvgas5xrqyjkp_vtbjmo0u-fs7mwxops2dttca0emf...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On Mon, Jun 11, 2012 at 8:08 AM, Alexander Olihovik <[email protected]> wrote:
> Does anyone have helpful information as to whether the DSBRX is compatible
> with the USRP N210?
> All I've found thusfar is schematics of the DSBRX.
You need to configure the DBSRX clocking (requires soldering) .. they
shipped configured for USRP1
http://files.ettus.com/uhd_docs/manual/html/dboards.html#dbsrx-mod
Jason
------------------------------
Message: 13
Date: Mon, 11 Jun 2012 11:15:22 -0400
From: [email protected]
To: <[email protected]>
Subject: Re: [USRP-users] DSBRX with N210
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
On 11 Jun 2012 11:08, Alexander Olihovik wrote:
> Does anyone have
helpful information as to whether the DSBRX is compatible with the USRP
N210?
> All I've found thusfar is schematics of the DSBRX.
>
> The
specific output of the program (and the problem) I'm trying to run is:
>
-----------------------------------------------------------------------------
>
linux; GNU C++ version 4.6.3; Boost_104601;
UHD_003.004.002-133-gb61a1103
>
> Using Volk machine: sse4_1_64
> --
Opening a USRP2/N-Series device...
> -- Current recv frame size: 1472
bytes
> -- Current send frame size: 1472 bytes
>
> UHD Warning:
>
DBSRX: incorrect dbid
> Expected dbid 0x000D and R194
> found dbid ==
DBSRX (0x0002)
> Please see the daughterboard app notes
>
> UHD
Warning:
> DBSRX: Tuning exceeded vco range,
_max2118_write_regs.osc_band == 0
>
> UHD Error:
> The daughterboard
manager encountered a recoverable error in init.
> Loading the "unknown"
daughterboard implementations to continue.
> The daughterboard cannot
operate until this error is resolved.
> AssertionError:
_max2118_read_regs.adc != 0
> in double dbsrx::set_lo_freq(double)
> at
/home/aolihovik/GNU_Radio/uhd/host/lib/usrp/dboard/db_dbsrx.cpp:382
>
-----------------------------------------------------------------------------
>
> Any help is greatly appreciated!
>
> Best regards,
> Alex
>
> --
> Alex Olihovik
> University of Virginia 2013
> BS Electrical
Engineering
> BS Computer Engineering
> [email protected] [1]
See:
http://files.ettus.com/uhd_docs/manual/html/dboards.html#dbsrx-mod
Links:
------
[1] mailto:[email protected]
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20120611/676306ad/attachment-0001.html>
------------------------------
Message: 14
Date: Mon, 11 Jun 2012 08:52:35 -0700
From: Josh Blum <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] does ubuntu 12.04 works for USRP N210?
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
>
> Hello there,
>
> I'm facing similar issues with the uhd drivers UHD_OO3.004.002.
>
> I,ve downloaded and installed these drivers
> uhd_003.004.002-150-unstable_Ubuntu-11.10-x86_64.deb from
> http://files.ettus.com/binaries/uhd_unstable/latest/
>
The debian package should be installed to /usr, but the error message is
from /usr/local I think you have multiple installs, one from source, one
from debian. Would that be a correct assumption?
> also,
>
> I've loaded the following images to my USRP N200 box:
>
> uhd-images_003.004.002-release.tar.gz
>
> from the same URL listed above and when I try to run ./tx_samples_from_file
> from
> ../uhd/host/build/examples, I get the following error
>
> Error: RuntimeError:
> Please update the firmware and FPGA images for your device.
> See the application notes for USRP2/N-Series for instructions.
> Expected FPGA compatibility number 10, but got 9:
> The FPGA build is not compatible with the host code build.
> Please run:
> "/usr/local/share/uhd/utils/usrp_n2xx_net_burner_gui.py" \
> --fpga="/usr/local/share/uhd/images/usrp_n200_r2_fpga.bin" \
> --fw="/usr/local/share/uhd/images/usrp_n200_fw.bin" \
> --addr="192.168.10.3"
>
> It seems like the latest uhd FPGA images available are lagging the current uhd
> driver version.
>
Does the error go away when you run that command?
If not and this was a source build, see:
http://code.ettus.com/redmine/ettus/projects/uhd/wiki/UHD_Build#Firmware-and-FPGA-images
-josh
------------------------------
_______________________________________________
USRP-users mailing list
[email protected]
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
End of USRP-users Digest, Vol 22, Issue 11
******************************************
