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. X310 register loopback fail ([email protected])
2. Compiling own code in Visual Studio 2010, 64bit
([email protected])
3. Re: Compiling own code in Visual Studio 2010, 64bit
(Marcus M?ller)
4. Re: Compiling own code in Visual Studio 2010, 64bit
(Stefano Speretta)
5. uhd_fft not responding (Richard Bell)
6. Re: USRP2 + XCVR2450 configuration (Ben Hilburn)
7. Xilinx ISE Preprocessor Statements (Jeremy Hershberger)
8. Re: Xilinx ISE Preprocessor Statements (Ian Buckley)
9. Re: [B200 USRP] HDSDR] " Failed to create USRP without device
hint" (Balint Seeber)
10. Re: USRP2 + XCVR2450 configuration (Virag Varga)
11. Re: USRP2 + XCVR2450 configuration ([email protected])
12. Re: USRP2 + XCVR2450 configuration (Virag Varga)
----------------------------------------------------------------------
Message: 1
Date: Thu, 18 Dec 2014 10:40:44 +0000
From: <[email protected]>
To: <[email protected]>
Subject: [USRP-users] X310 register loopback fail
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="us-ascii"
Hi there,
I recently got a X310 and get some weird IOErrors.
The X310 is connected via PCIe to my Win7 64bit workstation. I installed the
latest 64bit UHD release (003.008.001).
The X310 is equipped with two CBX-120 boards and the internal GPSDO.
I tried uhd_find_devices.exe from UHD/bin and it worked fine, showing my X310
as resource RIO0.
Now I tried uhd_usrp_probe.exe: Sometimes this works fine, passing all tests
and showing all details. But sometimes, it gives me an IOError during register
loopback tests. Do you have any idea why? I also get this error sometimes, when
I call usrp make within my C++ program.
Here is the dump from the console:
C:\Program Files (x86)\UHD\bin>uhd_usrp_probe.exe
Win32; Microsoft Visual C++ version 10.0; Boost_105400; UHD_003.008.001-release
-- X300 initialization sequence...
-- Connecting to niusrpriorpc at localhost:5444...
-- Using LVBITX bitfile C:\Program Files
(x86)\UHD\share\uhd\images\usrp_x310_fpga_HGS.lvbitx...
-- Setup basic communication...
-- Loading values from EEPROM...
-- Setup RF frontend clocking...
-- Radio 1x clock:200
-- Detecting internal GPSDO.... Found an internal GPSDO
-- Initialize Radio control...
-- Performing register loopback test... Error: EnvironmentError: IOError: Radio
ctrl (A) no response packet - AssertionError: bool
(buff)
in unsigned __int64 __cdecl radio_ctrl_core_3000_impl::wait_for_ack(const
bool)
at ..\..\..\..\uhd\host\lib\usrp\cores\radio_ctrl_core_3000.cpp:192
Best regards,
Emanuel
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20141218/0a422697/attachment-0001.html>
------------------------------
Message: 2
Date: Thu, 18 Dec 2014 14:19:48 +0000
From: <[email protected]>
To: <[email protected]>
Subject: [USRP-users] Compiling own code in Visual Studio 2010, 64bit
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="us-ascii"
Hi all,
I read through so many different pages and approaches how to build your own
code using the UHD API, but I did not manage to run everything successfully.
Maybe somebody has a hint :)
That's what I have right now:
* USRP X310 connected via GigE or PCIe
* Installed the lates UHD 64bit release, installed visual studio
professional 2010
* Boost library is installed as binary with the correct Visual Studio
2010 64bit Version (as I'm using Win7 64bit)
I tested the uhd_find_device and the uhd_usrp_probe exe-files provided in the
UHD installation directory: both worked fine and showed correct results.
I wanted a simple program: Starting with the thread safe uhd main, and then
simply calling ....multi_usrp::make("192.168.10.2"); as the USRP is currently
connected via Ethernet.
I set up Visual Studio as follows:
* Starting with an empty Win32 console project and changing
configuration to X64 (Debug)
* In the C++ configuration I add the UHD and Boost include directories
* In the Linker configuration I add the UHD lib and the Boost lib as
additional library directories
* I also add uhd.lib in the "Additional Dependencies" tab
Everything compiles fine without errors. The Linker also does not through any
errors. So far so good. Next, I copied the uhd.dll from the UHD installation
directory (bin folder) to where by generated exe lies.
I start my program and when I reach the ::make statement in my C++ code, I get
an access violation. The uhd.dll is found, otherwise my program complains about
not finding the dll right at startup.
Why do I get an access violation? Is it the wrong uhd.dll?
Best regards,
Emanuel
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20141218/584a395f/attachment-0001.html>
------------------------------
Message: 3
Date: Thu, 18 Dec 2014 18:34:05 +0100
From: Marcus M?ller <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] Compiling own code in Visual Studio 2010,
64bit
Message-ID: <[email protected]>
Content-Type: text/plain; charset="windows-1252"
Hi Emanuel,
just throwing guesses at you:
- Visual Studio sometimes is awesome. Other times, you can't (or at
least, I can't) mix debug and release binaries. This doesn't manifest as
a linker error, but as a runtime error the first time you call into the
library of the different build type. No hint what goes wrong whatsoever.
- Have you tried executing that executable with the debugger attached?
Greetings,
Marcus
On 12/18/2014 03:19 PM, Emanuel via USRP-users wrote:
>
> Hi all,
>
>
>
> I read through so many different pages and approaches how to build
> your own code using the UHD API, but I did not manage to run
> everything successfully. Maybe somebody has a hint J
>
> That?s what I have right now:
>
> ? USRP X310 connected via GigE or PCIe
>
> ? Installed the lates UHD 64bit release, installed visual
> studio professional 2010
>
> ? Boost library is installed as binary with the correct Visual
> Studio 2010 64bit Version (as I?m using Win7 64bit)
>
> I tested the uhd_find_device and the uhd_usrp_probe exe-files provided
> in the UHD installation directory: both worked fine and showed correct
> results.
>
>
>
> I wanted a simple program: Starting with the thread safe uhd main, and
> then simply calling ?.multi_usrp::make(?192.168.10.2?); as the USRP is
> currently connected via Ethernet.
>
> I set up Visual Studio as follows:
>
> ? Starting with an empty Win32 console project and changing
> configuration to X64 (Debug)
>
> ? In the C++ configuration I add the UHD and Boost include
> directories
>
> ? In the Linker configuration I add the UHD lib and the Boost
> lib as additional library directories
>
> ? I also add uhd.lib in the ?Additional Dependencies? tab
>
> Everything compiles fine without errors. The Linker also does not
> through any errors. So far so good. Next, I copied the uhd.dll from
> the UHD installation directory (bin folder) to where by generated exe
> lies.
>
> I start my program and when I reach the ::make statement in my C++
> code, I get an access violation. The uhd.dll is found, otherwise my
> program complains about not finding the dll right at startup.
>
>
>
> Why do I get an access violation? Is it the wrong uhd.dll?
>
>
>
> Best regards,
>
> Emanuel
>
>
>
>
>
> _______________________________________________
> 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/20141218/de590e87/attachment-0001.html>
------------------------------
Message: 4
Date: Thu, 18 Dec 2014 18:50:05 +0100
From: Stefano Speretta <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] Compiling own code in Visual Studio 2010,
64bit
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
I am not sure if it is completely related, but I was also trying to
initialize make with a static char array like you did (but under Linux
with GCC) and I get this compile error:
no known conversion for argument 1 from ?const char [12]? to ?const
uhd::device_addr_t&?
while everything works fine if I do:
std:string args = "192.168.1.1";
multi_usrp::make(args);
If you check the prototype of make
(http://files.ettus.com/manual/classuhd_1_1usrp_1_1multi__usrp.html), it
expects a device_addt_t type which is created from an std:string and not
an unsigned char*. In the end, GCC is generally more strict but does not
convert anything automatically while I've seen Visual Studio doing it
with positive and sometimes negative results.
Cheers,
Stefano
> Hi all,
>
> I read through so many different pages and approaches how to build
> your own code using the UHD API, but I did not manage to run
> everything successfully. Maybe somebody has a hint J
>
> That's what I have right now:
>
> ?USRP X310 connected via GigE or PCIe
>
> ?Installed the lates UHD 64bit release, installed visual studio
> professional 2010
>
> ?Boost library is installed as binary with the correct Visual Studio
> 2010 64bit Version (as I'm using Win7 64bit)
>
> I tested the uhd_find_device and the uhd_usrp_probe exe-files provided
> in the UHD installation directory: both worked fine and showed correct
> results.
>
> I wanted a simple program: Starting with the thread safe uhd main, and
> then simply calling ....multi_usrp::make("192.168.10.2"); as the USRP
> is currently connected via Ethernet.
>
> I set up Visual Studio as follows:
>
> ?Starting with an empty Win32 console project and changing
> configuration to X64 (Debug)
>
> ?In the C++ configuration I add the UHD and Boost include directories
>
> ?In the Linker configuration I add the UHD lib and the Boost lib as
> additional library directories
>
> ?I also add uhd.lib in the "Additional Dependencies" tab
>
> Everything compiles fine without errors. The Linker also does not
> through any errors. So far so good. Next, I copied the uhd.dll from
> the UHD installation directory (bin folder) to where by generated exe
> lies.
>
> I start my program and when I reach the ::make statement in my C++
> code, I get an access violation. The uhd.dll is found, otherwise my
> program complains about not finding the dll right at startup.
>
> Why do I get an access violation? Is it the wrong uhd.dll?
>
> Best regards,
>
> Emanuel
>
>
>
> _______________________________________________
> 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/20141218/df1b51b4/attachment-0001.html>
------------------------------
Message: 5
Date: Thu, 18 Dec 2014 10:39:51 -0800
From: Richard Bell <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [USRP-users] uhd_fft not responding
Message-ID:
<CAMMoi3sfyeexytxtDb+upTBTC-sNJGZR79DEBoQuULecK=7...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
I'm using Ubuntu 14.04, UHD_003.008.00-18-g864f84b5 and GNU Radio 3.7.6
Whenever I start uhd_fft from a command line, the window opens and starts
to plot. After about a second, the window goes into not responding mode,
where it greys out and you can't click anything. Does anyone know what
could be causing this behaviour? Is it a local setting of mine?
Rich
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20141218/5568b429/attachment-0001.html>
------------------------------
Message: 6
Date: Thu, 18 Dec 2014 10:52:16 -0800
From: Ben Hilburn <[email protected]>
To: Virag Varga <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [USRP-users] USRP2 + XCVR2450 configuration
Message-ID:
<caoevzkl_o83dywwk9fafz1xr1s2habgtrig2jvqyd57stdg...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Virag -
Please refer to the USRP manual:
http://files.ettus.com/manual/page_general.html#general_threading
It is not a critical error, but you may be able to improve performance.
Cheers,
Ben
On Tue, Dec 16, 2014 at 3:15 AM, Virag Varga via USRP-users <
[email protected]> wrote:
>
> Hi,
>
> I'm quite new to the SDR world. I started with an USRP2 (r4) +
> XCVR2450 dboard. I tried some examples with gnuradio, but I'm still
> not sure, if everything is setup correctly (mostly it seems I'm only
> getting noise)..
>
> For start, I don't think I should get this output (no sign that my
> daughterboard is recognized correctly) for uhd_usrp_probe (check down
> below).
>
> Do I miss some installation/configuration steps?
>
> Thanks for any help!
> Bests,
> Virag
>
>
>
> $ uhd_usrp_probe
> linux; GNU C++ version 4.8.2; Boost_105400; UHD_003.008.000-release
>
> -- Opening a USRP2/N-Series device...
> -- Current recv frame size: 1472 bytes
> -- Current send frame size: 1472 bytes
>
> UHD Warning:
> Unable to set the thread priority. Performance may be negatively
> affected.
> Please see the general application notes in the manual for
> instructions.
> EnvironmentError: OSError: error in pthread_setschedparam
> _____________________________________________________
> /
> | Device: USRP2 / N-Series Device
> | _____________________________________________________
> | /
> | | Mboard: USRP2 r4
> | | hardware: 1024
> | | mac-addr: 00:50:c2:85:39:47
> | | ip-addr: 255.255.255.255
> | | subnet: 255.255.255.255
> | | gateway: 255.255.255.255
> | | gpsdo: none
> | | serial: 2375
> | | FW Version: 12.4
> | | FPGA Version: 10.0
> | |
> | | Time sources: none, external, _external_, mimo
> | | Clock sources: internal, external, mimo
> | | Sensors: mimo_locked, ref_locked
> | | _____________________________________________________
> | | /
> | | | RX DSP: 0
> | | | Freq range: -50.000 to 50.000 MHz
> | | _____________________________________________________
> | | /
> | | | RX DSP: 1
> | | | Freq range: -50.000 to 50.000 MHz
> | | _____________________________________________________
> | | /
> | | | RX Dboard: A
> | | | _____________________________________________________
> | | | /
> | | | | RX Frontend: 0
> | | | | Name: Unknown (0xffff) - 0
> | | | | Antennas:
> | | | | Sensors:
> | | | | Freq range: 0.000 to 0.000 MHz
> | | | | Gain Elements: None
> | | | | Connection Type: IQ
> | | | | Uses LO offset: No
> | | | _____________________________________________________
> | | | /
> | | | | RX Codec: A
> | | | | Name: ltc2284
> | | | | Gain Elements: None
> | | _____________________________________________________
> | | /
> | | | TX DSP: 0
> | | | Freq range: -50.000 to 50.000 MHz
> | | _____________________________________________________
> | | /
> | | | TX Dboard: A
> | | | _____________________________________________________
> | | | /
> | | | | TX Frontend: 0
> | | | | Name: Unknown (0xffff) - 0
> | | | | Antennas:
> | | | | Sensors:
> | | | | Freq range: 0.000 to 0.000 MHz
> | | | | Gain Elements: None
> | | | | Connection Type: IQ
> | | | | Uses LO offset: No
> | | | _____________________________________________________
> | | | /
> | | | | TX Codec: A
> | | | | Name: ad9777
> | | | | Gain Elements: None
>
> _______________________________________________
> 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/20141218/64e79e31/attachment-0001.html>
------------------------------
Message: 7
Date: Thu, 18 Dec 2014 14:05:53 -0500
From: Jeremy Hershberger <[email protected]>
To: [email protected]
Subject: [USRP-users] Xilinx ISE Preprocessor Statements
Message-ID:
<camziklqd5v8on2hjxeetexqu2-4ufp2p9year7nw0jdm7oy...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
When using the B210 makefile with the "PROJECT_ONLY=1" option, the
generated Xilinx ISE Project fails to instantiate radio1.
If I examine b200_core.v, I notice that there is an "ifdef B200_CAN_HAZ_R1"
statement which is supposed to allow instantiation of radio1 but fails to
do so. The B210 makefile passes B200_CAN_HAZ_R1=1 into project creation,
but yet radio1 remains uninstantiated.
Are preprocessor statements, like ifdef, recognized by ISE? Is there some
way to hard-code variables from the makefile into my ISE project, or am I
forced to search through all of the verilog files deleting the ifdef
statements?
-Jeremy
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20141218/cd272b58/attachment-0001.html>
------------------------------
Message: 8
Date: Thu, 18 Dec 2014 12:41:36 -0800
From: Ian Buckley <[email protected]>
To: Jeremy Hershberger <[email protected]>
Cc: [email protected]
Subject: Re: [USRP-users] Xilinx ISE Preprocessor Statements
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-1252
Jeremy,
The PROJECT_ONLY option has been added since I last worked on that makefile but
I can give you some pointers here that should allow you to solve your problem
with less work than you envisage.
First of all, ISE's Verilog parser interprets pre-processor directives
correctly, what is happening here is something different.
When you run the Makefile normally the ISE property "Verilog Macros" is set to
"SPARTAN6=1 B200_CAN_HAZ_R1=1 " as ISE is invoked and this cause the Verilog
parser to behave as if it had already read lines defining these pre-processor
definitions.
When you run with the PROJECT_ONLY=1 option, then an XML record cottoning this
property is generated:
<property xil_pn:name="Verilog Macros" xil_pn:value="SPARTAN6=1
B200_CAN_HAZ_R1=1 " xil_pn:valueState="non-default"/>
?but for reasons unknown it seems that when you some time later invoke ISE it
isn't applied in the same way as when its passed via the command line. This
might for example be and ordering problem?that property has to be in place
before the verilog file that is sensitive to it (b200_core.v) is read. I'm
afraid there will be little to no support for the internal quirks of ISE (and
it has many!)?it's not used at Ettus in an interactive way, only called as a
batch processor form Make.
Your simplest course of action is I think to edit b200_core.v and add as the
first line:
`define B200_CAN_HAZ_R1
I have no idea where/when in the code `SPARTAN6 was expected to be defined?that
may be completely obsolete?all the current code uses the definition of DEVICE
to make FPGA dependent code decisions.
I do encourage you to try to work in a batch oriented methodology though, its a
better way to do things in a quality way.
-Ian
On Dec 18, 2014, at 11:05 AM, Jeremy Hershberger via USRP-users
<[email protected]> wrote:
> When using the B210 makefile with the "PROJECT_ONLY=1" option, the generated
> Xilinx ISE Project fails to instantiate radio1.
>
> If I examine b200_core.v, I notice that there is an "ifdef B200_CAN_HAZ_R1"
> statement which is supposed to allow instantiation of radio1 but fails to do
> so. The B210 makefile passes B200_CAN_HAZ_R1=1 into project creation, but
> yet radio1 remains uninstantiated.
>
> Are preprocessor statements, like ifdef, recognized by ISE? Is there some
> way to hard-code variables from the makefile into my ISE project, or am I
> forced to search through all of the verilog files deleting the ifdef
> statements?
>
> -Jeremy
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
------------------------------
Message: 9
Date: Thu, 18 Dec 2014 21:47:54 -0800
From: Balint Seeber <[email protected]>
To: numeric <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [USRP-users] [B200 USRP] HDSDR] " Failed to create USRP
without device hint"
Message-ID:
<capcb_2r8grgajmccr7mxjww2jfrvp4eu6y9ndjswtq-722h...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi Rob,
The device changing after uhd_find_devices is a good sign. Please run
uhd_usrp_probe as well to ensure the FPGA is loaded correctly.
Zadig is always launched regardless of the state of your installation, so
if you've already installed the INFs for your USRP then you should be fine
and can close it.
The package with HDSDR/ExtIO_USRP actually already contains UHD, so it's
actually not necessary to install the official binary distribution from the
Ettus package. Of course you can do this too if you like, just be aware
about potential DLL loading conflicts. If you're not having success, and
you're able, use something like the Profile feature in Dependency Walker to
check which UHD.dll is being loaded-it should be the same one that is in
HDSDR's directory.
Kind regards,
Balint
On Monday, December 15, 2014, numeric via USRP-users <
[email protected]> wrote:
> Hello group,
>
> I just received my USRP b200 circuit board:-) . I thought that I would
> start with known software for Windows 8.1 64 bit. I downloaded
> uhd_003.008.000-release_Win64_VS2013.exe from the ETTUS website and ran
> the installation. It installed to "Program files (x86)\UHD". When I tried
> to set the file path to "all users or current users" I get an error
> "Warning! PATH too long installer unable to modify PATH!". The [path
> >path.txt] from the command prompt, is 639 Hex characters long or 1593 in
> decimal. Excluding 0xd 0xa (EOL). Ignored the error. Next installed
> "ExtIO_USRP+FCD+BorIP_Setup.zip". It installed to "Program files
> (x86)\hdsdr". The program HDSDR was previously installed and used with the
> QS1R receiver using it's own EXTIO dll file. The QS1R extio dll was deleted
> before installing EXTIO_USRP to avoid potential conflicts. During the
> installation, zadaig.exe activated.
> Question:
> Since UHD.dll is already a driver do I need to use zadaig? The device
> manager indicated "Westbridge" when the USPR B200 is plugged in, it changes
> to B200 after running "uhd_find_devices.exe". I get the same device hint
> problem if zidaig is run or not.
> What files is EXTIO_USRP looking for?
>
> Question:
> What am I doing wrong?
>
> Any help is greatly appreciated,
> Rob
>
>
> _______________________________________________
> 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/20141218/5577b074/attachment-0001.html>
------------------------------
Message: 10
Date: Fri, 19 Dec 2014 16:43:49 +0100
From: Virag Varga <[email protected]>
To: Ben Hilburn <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [USRP-users] USRP2 + XCVR2450 configuration
Message-ID:
<CABPEh2LDaMWvR0fqQawVXnk5foVHhAkgwjAr2fchaiXAu_=d...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Hi Ben,
thanks for the advice, it really fixes the thread priority warning.
But my main concern is still that the daughterboards don't seem to be
recognized.. Or is it normal, not to have any information about their
type in the uhd_usrp_probe output (see below)?
Thanks again,
Virag
$ uhd_usrp_probe
linux; GNU C++ version 4.8.2; Boost_105400; UHD_003.008.001-0-g2474ac32
-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
_____________________________________________________
/
| Device: USRP2 / N-Series Device
| _____________________________________________________
| /
| | Mboard: USRP2 r4
| | hardware: 1024
| | mac-addr: 00:50:c2:85:39:44
| | ip-addr: 255.255.255.255
| | subnet: 255.255.255.255
| | gateway: 255.255.255.255
| | gpsdo: none
| | serial: 2372
| | FW Version: 12.4
| | FPGA Version: 10.1
| |
| | Time sources: none, external, _external_, mimo
| | Clock sources: internal, external, mimo
| | Sensors: mimo_locked, ref_locked
| | _____________________________________________________
| | /
| | | RX DSP: 0
| | | Freq range: -50.000 to 50.000 MHz
| | _____________________________________________________
| | /
| | | RX DSP: 1
| | | Freq range: -50.000 to 50.000 MHz
| | _____________________________________________________
| | /
| | | RX Dboard: A
| | | _____________________________________________________
| | | /
| | | | RX Frontend: 0
| | | | Name: Unknown (0xffff) - 0
| | | | Antennas:
| | | | Sensors:
| | | | Freq range: 0.000 to 0.000 MHz
| | | | Gain Elements: None
| | | | Connection Type: IQ
| | | | Uses LO offset: No
| | | _____________________________________________________
| | | /
| | | | RX Codec: A
| | | | Name: ltc2284
| | | | Gain Elements: None
| | _____________________________________________________
| | /
| | | TX DSP: 0
| | | Freq range: -50.000 to 50.000 MHz
| | _____________________________________________________
| | /
| | | TX Dboard: A
| | | _____________________________________________________
| | | /
| | | | TX Frontend: 0
| | | | Name: Unknown (0xffff) - 0
| | | | Antennas:
| | | | Sensors:
| | | | Freq range: 0.000 to 0.000 MHz
| | | | Gain Elements: None
| | | | Connection Type: IQ
| | | | Uses LO offset: No
| | | _____________________________________________________
| | | /
| | | | TX Codec: A
| | | | Name: ad9777
| | | | Gain Elements: None
On Thu, Dec 18, 2014 at 7:52 PM, Ben Hilburn <[email protected]> wrote:
> Virag -
>
> Please refer to the USRP manual:
> http://files.ettus.com/manual/page_general.html#general_threading
>
> It is not a critical error, but you may be able to improve performance.
>
> Cheers,
> Ben
>
> On Tue, Dec 16, 2014 at 3:15 AM, Virag Varga via USRP-users
> <[email protected]> wrote:
>>
>> Hi,
>>
>> I'm quite new to the SDR world. I started with an USRP2 (r4) +
>> XCVR2450 dboard. I tried some examples with gnuradio, but I'm still
>> not sure, if everything is setup correctly (mostly it seems I'm only
>> getting noise)..
>>
>> For start, I don't think I should get this output (no sign that my
>> daughterboard is recognized correctly) for uhd_usrp_probe (check down
>> below).
>>
>> Do I miss some installation/configuration steps?
>>
>> Thanks for any help!
>> Bests,
>> Virag
>>
>>
>>
>> $ uhd_usrp_probe
>> linux; GNU C++ version 4.8.2; Boost_105400; UHD_003.008.000-release
>>
>> -- Opening a USRP2/N-Series device...
>> -- Current recv frame size: 1472 bytes
>> -- Current send frame size: 1472 bytes
>>
>> UHD Warning:
>> Unable to set the thread priority. Performance may be negatively
>> affected.
>> Please see the general application notes in the manual for
>> instructions.
>> EnvironmentError: OSError: error in pthread_setschedparam
>> _____________________________________________________
>> /
>> | Device: USRP2 / N-Series Device
>> | _____________________________________________________
>> | /
>> | | Mboard: USRP2 r4
>> | | hardware: 1024
>> | | mac-addr: 00:50:c2:85:39:47
>> | | ip-addr: 255.255.255.255
>> | | subnet: 255.255.255.255
>> | | gateway: 255.255.255.255
>> | | gpsdo: none
>> | | serial: 2375
>> | | FW Version: 12.4
>> | | FPGA Version: 10.0
>> | |
>> | | Time sources: none, external, _external_, mimo
>> | | Clock sources: internal, external, mimo
>> | | Sensors: mimo_locked, ref_locked
>> | | _____________________________________________________
>> | | /
>> | | | RX DSP: 0
>> | | | Freq range: -50.000 to 50.000 MHz
>> | | _____________________________________________________
>> | | /
>> | | | RX DSP: 1
>> | | | Freq range: -50.000 to 50.000 MHz
>> | | _____________________________________________________
>> | | /
>> | | | RX Dboard: A
>> | | | _____________________________________________________
>> | | | /
>> | | | | RX Frontend: 0
>> | | | | Name: Unknown (0xffff) - 0
>> | | | | Antennas:
>> | | | | Sensors:
>> | | | | Freq range: 0.000 to 0.000 MHz
>> | | | | Gain Elements: None
>> | | | | Connection Type: IQ
>> | | | | Uses LO offset: No
>> | | | _____________________________________________________
>> | | | /
>> | | | | RX Codec: A
>> | | | | Name: ltc2284
>> | | | | Gain Elements: None
>> | | _____________________________________________________
>> | | /
>> | | | TX DSP: 0
>> | | | Freq range: -50.000 to 50.000 MHz
>> | | _____________________________________________________
>> | | /
>> | | | TX Dboard: A
>> | | | _____________________________________________________
>> | | | /
>> | | | | TX Frontend: 0
>> | | | | Name: Unknown (0xffff) - 0
>> | | | | Antennas:
>> | | | | Sensors:
>> | | | | Freq range: 0.000 to 0.000 MHz
>> | | | | Gain Elements: None
>> | | | | Connection Type: IQ
>> | | | | Uses LO offset: No
>> | | | _____________________________________________________
>> | | | /
>> | | | | TX Codec: A
>> | | | | Name: ad9777
>> | | | | Gain Elements: None
>>
>> _______________________________________________
>> USRP-users mailing list
>> [email protected]
>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
------------------------------
Message: 11
Date: Fri, 19 Dec 2014 10:47:47 -0500
From: [email protected]
To: Virag Varga <[email protected]>
Cc: [email protected]
Subject: Re: [USRP-users] USRP2 + XCVR2450 configuration
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
No, that isn't normal.
Could you make certain that the XCVR2450 is properly seated?
On 2014-12-19 10:43, Virag Varga via USRP-users wrote:
> Hi Ben,
>
> thanks for the advice, it really fixes the thread priority warning.
> But my main concern is still that the daughterboards don't seem to be
> recognized.. Or is it normal, not to have any information about their
> type in the uhd_usrp_probe output (see below)?
>
> Thanks again,
> Virag
>
> $ uhd_usrp_probe
> linux; GNU C++ version 4.8.2; Boost_105400; UHD_003.008.001-0-g2474ac32
>
> -- Opening a USRP2/N-Series device...
> -- Current recv frame size: 1472 bytes
> -- Current send frame size: 1472 bytes
> _____________________________________________________
> /
> | Device: USRP2 / N-Series Device
> | _____________________________________________________
> | /
> | | Mboard: USRP2 r4
> | | hardware: 1024
> | | mac-addr: 00:50:c2:85:39:44
> | | ip-addr: 255.255.255.255
> | | subnet: 255.255.255.255
> | | gateway: 255.255.255.255
> | | gpsdo: none
> | | serial: 2372
> | | FW Version: 12.4
> | | FPGA Version: 10.1
> | |
> | | Time sources: none, external, _external_, mimo
> | | Clock sources: internal, external, mimo
> | | Sensors: mimo_locked, ref_locked
> | | _____________________________________________________
> | | /
> | | | RX DSP: 0
> | | | Freq range: -50.000 to 50.000 MHz
> | | _____________________________________________________
> | | /
> | | | RX DSP: 1
> | | | Freq range: -50.000 to 50.000 MHz
> | | _____________________________________________________
> | | /
> | | | RX Dboard: A
> | | | _____________________________________________________
> | | | /
> | | | | RX Frontend: 0
> | | | | Name: Unknown (0xffff) - 0
> | | | | Antennas:
> | | | | Sensors:
> | | | | Freq range: 0.000 to 0.000 MHz
> | | | | Gain Elements: None
> | | | | Connection Type: IQ
> | | | | Uses LO offset: No
> | | | _____________________________________________________
> | | | /
> | | | | RX Codec: A
> | | | | Name: ltc2284
> | | | | Gain Elements: None
> | | _____________________________________________________
> | | /
> | | | TX DSP: 0
> | | | Freq range: -50.000 to 50.000 MHz
> | | _____________________________________________________
> | | /
> | | | TX Dboard: A
> | | | _____________________________________________________
> | | | /
> | | | | TX Frontend: 0
> | | | | Name: Unknown (0xffff) - 0
> | | | | Antennas:
> | | | | Sensors:
> | | | | Freq range: 0.000 to 0.000 MHz
> | | | | Gain Elements: None
> | | | | Connection Type: IQ
> | | | | Uses LO offset: No
> | | | _____________________________________________________
> | | | /
> | | | | TX Codec: A
> | | | | Name: ad9777
> | | | | Gain Elements: None
>
> On Thu, Dec 18, 2014 at 7:52 PM, Ben Hilburn <[email protected]> wrote:
> Virag - Please refer to the USRP manual:
> http://files.ettus.com/manual/page_general.html#general_threading [1] It is
> not a critical error, but you may be able to improve performance. Cheers, Ben
> On Tue, Dec 16, 2014 at 3:15 AM, Virag Varga via USRP-users
> <[email protected]> wrote: Hi, I'm quite new to the SDR world. I
> started with an USRP2 (r4) + XCVR2450 dboard. I tried some examples with
> gnuradio, but I'm still not sure, if everything is setup correctly (mostly it
> seems I'm only getting noise).. For start, I don't think I should get this
> output (no sign that my daughterboard is recognized correctly) for
> uhd_usrp_probe (check down below). Do I miss some installation/configuration
> steps? Thanks for any help! Bests, Virag $ uhd_usrp_probe linux; GNU C++
> version 4.8.2; Boost_105400; UHD_003.008.000-release -- Opening a
> USRP2/N-Series device... -- Current recv frame size: 1472 bytes -- Current
> send frame size: 1472 bytes UHD Warning: Unable to set the thread priority.
Performance may be negatively affected. Please see the general application
notes in the manual for instructions. EnvironmentError: OSError: error in
pthread_setschedparam _____________________________________________________ / |
Device: USRP2 / N-Series Device |
_____________________________________________________ | / | | Mboard: USRP2 r4
| | hardware: 1024 | | mac-addr: 00:50:c2:85:39:47 | | ip-addr: 255.255.255.255
| | subnet: 255.255.255.255 | | gateway: 255.255.255.255 | | gpsdo: none | |
serial: 2375 | | FW Version: 12.4 | | FPGA Version: 10.0 | | | | Time sources:
none, external, _external_, mimo | | Clock sources: internal, external, mimo |
| Sensors: mimo_locked, ref_locked | |
_____________________________________________________ | | / | | | RX DSP: 0 | |
| Freq range: -50.000 to 50.000 MHz | |
_____________________________________________________ | | / | | | RX DSP: 1 | |
| Freq range: -50.000 to 50.000 MHz | |
_____________________________________________________ | | / |
| | RX Dboard: A | | | _____________________________________________________ |
| | / | | | | RX Frontend: 0 | | | | Name: Unknown (0xffff) - 0 | | | |
Antennas: | | | | Sensors: | | | | Freq range: 0.000 to 0.000 MHz | | | | Gain
Elements: None | | | | Connection Type: IQ | | | | Uses LO offset: No | | |
_____________________________________________________ | | | / | | | | RX Codec:
A | | | | Name: ltc2284 | | | | Gain Elements: None | |
_____________________________________________________ | | / | | | TX DSP: 0 | |
| Freq range: -50.000 to 50.000 MHz | |
_____________________________________________________ | | / | | | TX Dboard: A
| | | _____________________________________________________ | | | / | | | | TX
Frontend: 0 | | | | Name: Unknown (0xffff) - 0 | | | | Antennas: | | | |
Sensors: | | | | Freq range: 0.000 to 0.000 MHz | | | | Gain Elements: None | |
| | Connection Type: IQ | | | | Uses LO offset: No | | |
_____________________________________________________ | | | / | | |
| TX Codec: A | | | | Name: ad9777 | | | | Gain Elements: None
_______________________________________________ USRP-users mailing list
[email protected]
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com [2]
_______________________________________________
USRP-users mailing list
[email protected]
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com [2]
Links:
------
[1] http://files.ettus.com/manual/page_general.html#general_threading
[2] 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/20141219/eb1f5135/attachment-0001.html>
------------------------------
Message: 12
Date: Fri, 19 Dec 2014 17:02:02 +0100
From: Virag Varga <[email protected]>
To: [email protected]
Cc: "[email protected]" <[email protected]>
Subject: Re: [USRP-users] USRP2 + XCVR2450 configuration
Message-ID:
<cabpeh2jn6w2qt57m9wgal_8tqkc8h1xbcpxf3k5oagwhtyu...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Hi Markus,
thank you for confirming that it's not normal! Until now it seemed
that the XCVR2450 fits properly (I got it this way), so I wanted a fix
in the software layer, but I've just disassembled/reassembled it, and
finally everything started to work.. Sorry for the PEBKAC though.
Bests,
Virag
On Fri, Dec 19, 2014 at 4:47 PM, <[email protected]> wrote:
> No, that isn't normal.
>
> Could you make certain that the XCVR2450 is properly seated?
>
>
>
>
>
> On 2014-12-19 10:43, Virag Varga via USRP-users wrote:
>
> Hi Ben,
>
> thanks for the advice, it really fixes the thread priority warning.
> But my main concern is still that the daughterboards don't seem to be
> recognized.. Or is it normal, not to have any information about their
> type in the uhd_usrp_probe output (see below)?
>
> Thanks again,
> Virag
>
>
> $ uhd_usrp_probe
> linux; GNU C++ version 4.8.2; Boost_105400; UHD_003.008.001-0-g2474ac32
>
> -- Opening a USRP2/N-Series device...
> -- Current recv frame size: 1472 bytes
> -- Current send frame size: 1472 bytes
> _____________________________________________________
> /
> | Device: USRP2 / N-Series Device
> | _____________________________________________________
> | /
> | | Mboard: USRP2 r4
> | | hardware: 1024
> | | mac-addr: 00:50:c2:85:39:44
> | | ip-addr: 255.255.255.255
> | | subnet: 255.255.255.255
> | | gateway: 255.255.255.255
> | | gpsdo: none
> | | serial: 2372
> | | FW Version: 12.4
> | | FPGA Version: 10.1
> | |
> | | Time sources: none, external, _external_, mimo
> | | Clock sources: internal, external, mimo
> | | Sensors: mimo_locked, ref_locked
> | | _____________________________________________________
> | | /
> | | | RX DSP: 0
> | | | Freq range: -50.000 to 50.000 MHz
> | | _____________________________________________________
> | | /
> | | | RX DSP: 1
> | | | Freq range: -50.000 to 50.000 MHz
> | | _____________________________________________________
> | | /
> | | | RX Dboard: A
> | | | _____________________________________________________
> | | | /
> | | | | RX Frontend: 0
> | | | | Name: Unknown (0xffff) - 0
> | | | | Antennas:
> | | | | Sensors:
> | | | | Freq range: 0.000 to 0.000 MHz
> | | | | Gain Elements: None
> | | | | Connection Type: IQ
> | | | | Uses LO offset: No
> | | | _____________________________________________________
> | | | /
> | | | | RX Codec: A
> | | | | Name: ltc2284
> | | | | Gain Elements: None
> | | _____________________________________________________
> | | /
> | | | TX DSP: 0
> | | | Freq range: -50.000 to 50.000 MHz
> | | _____________________________________________________
> | | /
> | | | TX Dboard: A
> | | | _____________________________________________________
> | | | /
> | | | | TX Frontend: 0
> | | | | Name: Unknown (0xffff) - 0
> | | | | Antennas:
> | | | | Sensors:
> | | | | Freq range: 0.000 to 0.000 MHz
> | | | | Gain Elements: None
> | | | | Connection Type: IQ
> | | | | Uses LO offset: No
> | | | _____________________________________________________
> | | | /
> | | | | TX Codec: A
> | | | | Name: ad9777
> | | | | Gain Elements: None
>
> On Thu, Dec 18, 2014 at 7:52 PM, Ben Hilburn <[email protected]> wrote:
>
> Virag - Please refer to the USRP manual:
> http://files.ettus.com/manual/page_general.html#general_threading It is not
> a critical error, but you may be able to improve performance. Cheers, Ben On
> Tue, Dec 16, 2014 at 3:15 AM, Virag Varga via USRP-users
> <[email protected]> wrote:
>
> Hi, I'm quite new to the SDR world. I started with an USRP2 (r4) + XCVR2450
> dboard. I tried some examples with gnuradio, but I'm still not sure, if
> everything is setup correctly (mostly it seems I'm only getting noise).. For
> start, I don't think I should get this output (no sign that my daughterboard
> is recognized correctly) for uhd_usrp_probe (check down below). Do I miss
> some installation/configuration steps? Thanks for any help! Bests, Virag $
> uhd_usrp_probe linux; GNU C++ version 4.8.2; Boost_105400;
> UHD_003.008.000-release -- Opening a USRP2/N-Series device... -- Current
> recv frame size: 1472 bytes -- Current send frame size: 1472 bytes UHD
> Warning: Unable to set the thread priority. Performance may be negatively
> affected. Please see the general application notes in the manual for
> instructions. EnvironmentError: OSError: error in pthread_setschedparam
> _____________________________________________________ / | Device: USRP2 /
> N-Series Device | _____________________________________________________ | /
> | | Mboard: USRP2 r4 | | hardware: 1024 | | mac-addr: 00:50:c2:85:39:47 | |
> ip-addr: 255.255.255.255 | | subnet: 255.255.255.255 | | gateway:
> 255.255.255.255 | | gpsdo: none | | serial: 2375 | | FW Version: 12.4 | |
> FPGA Version: 10.0 | | | | Time sources: none, external, _external_, mimo |
> | Clock sources: internal, external, mimo | | Sensors: mimo_locked,
> ref_locked | | _____________________________________________________ | | / |
> | | RX DSP: 0 | | | Freq range: -50.000 to 50.000 MHz | |
> _____________________________________________________ | | / | | | RX DSP: 1
> | | | Freq range: -50.000 to 50.000 MHz | |
> _____________________________________________________ | | / | | | RX Dboard:
> A | | | _____________________________________________________ | | | / | | |
> | RX Frontend: 0 | | | | Name: Unknown (0xffff) - 0 | | | | Antennas: | | |
> | Sensors: | | | | Freq range: 0.000 to 0.000 MHz | | | | Gain Elements:
> None | | | | Connection Type: IQ | | | | Uses LO offset: No | | |
> _____________________________________________________ | | | / | | | | RX
> Codec: A | | | | Name: ltc2284 | | | | Gain Elements: None | |
> _____________________________________________________ | | / | | | TX DSP: 0
> | | | Freq range: -50.000 to 50.000 MHz | |
> _____________________________________________________ | | / | | | TX Dboard:
> A | | | _____________________________________________________ | | | / | | |
> | TX Frontend: 0 | | | | Name: Unknown (0xffff) - 0 | | | | Antennas: | | |
> | Sensors: | | | | Freq range: 0.000 to 0.000 MHz | | | | Gain Elements:
> None | | | | Connection Type: IQ | | | | Uses LO offset: No | | |
> _____________________________________________________ | | | / | | | | TX
> Codec: A | | | | Name: ad9777 | | | | Gain Elements: None
> _______________________________________________ USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
------------------------------
Subject: Digest Footer
_______________________________________________
USRP-users mailing list
[email protected]
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
------------------------------
End of USRP-users Digest, Vol 52, Issue 21
******************************************
