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. Crest factor for A/D (David Campbell)
2. Re: urspn210 help (Josh Blum)
3. Re: small feature request (Josh Blum)
4. Re: USRP E100 (Macre, William R)
5. Libertas driver for the W2CBW003 (Michael Yan)
6. Re: USRP E100 (Macre, William R)
7. Re: Libertas driver for the W2CBW003 (Macre, William R)
----------------------------------------------------------------------
Message: 1
Date: Tue, 26 Feb 2013 12:57:07 -0800 (PST)
From: David Campbell <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [USRP-users] Crest factor for A/D
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="iso-8859-1"
Hi,
??? I am wondering if there is a way to retrieve in realtime A/D loading data
(i.e. crest factor) for the N210 et.al (so the RX path).?? This would be the
loading of the 100 Msps A/D, before it goes into to the tuners.? Otherwise, I
may not be able to tell if my input is overloading the A/D.
Thanks,
David
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20130226/7951a560/attachment-0001.html>
------------------------------
Message: 2
Date: Tue, 26 Feb 2013 16:22:25 -0600
From: Josh Blum <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] urspn210 help
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
On 02/26/2013 02:37 AM, Mohammed Ramadan wrote:
> i am fresh with using USRPn210 Device, and i know python programming
> language. and i want to do RF application using the USRPn210
> (transmit signal then receive it and compare the amplitude change in
> this signal) , so i must use uhd in gnu-radio or i can use python
> language for managing any applications, i need you help and how can i
> start with this device.
>
You might find this link to code examples for the various options useful:
http://code.ettus.com/redmine/ettus/projects/uhd/wiki#Code-Examples
Also this:
http://gnuradio.org/redmine/projects/gnuradio/wiki/BlocksCodingGuide
-josh
>
>
> _______________________________________________ USRP-users mailing
> list [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
------------------------------
Message: 3
Date: Tue, 26 Feb 2013 16:28:28 -0600
From: Josh Blum <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] small feature request
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
On 02/26/2013 08:25 AM, Stefano Speretta wrote:
> Hello,
> I am writing an application using uhd to access a usrp B100 ubnder
> Linux. I noticed that when the user has not the permissions to
> access the usb bus an exception is thrown by uhd::usrp::multi_usrp::make
> stating "KeyError: No devices found for -----> Empty Device Address".
>
> On a command line application there would be a message displayed, as for
> example in uhd_usrp_probe:
>
> UHD Error:
> USB open failed: insufficient permissions.
> See the application notes for your device.
> Error: LookupError: KeyError: No devices found for ----->
> Empty Device Address
>
> but this is difficult to catch in GUI applications. Could it be possible
> to throw a message that points to the insufficient permissions in case
> of error?
>
In a gui, you may want to direct the error messages into a pop up window
of some sort:
http://files.ettus.com/uhd_docs/manual/html/general.html#disabling-or-redirecting-prints-to-stdout
-josh
> Thanks
> Stefano
>
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
------------------------------
Message: 4
Date: Wed, 27 Feb 2013 15:30:06 +0000
From: "Macre, William R" <[email protected]>
To: "McKeever, Kenneth R." <[email protected]>,
"[email protected]" <[email protected]>, "[email protected]"
<[email protected]>
Cc: "Hodge, James E" <[email protected]>, "Miller, Robert David"
<[email protected]>
Subject: Re: [USRP-users] USRP E100
Message-ID:
<5e9bdf6832e57149b46d9becf6ab21510cf19...@rrc-ats-exmb2.ats.atsinnovate.com>
Content-Type: text/plain; charset="us-ascii"
Josh:
I am having the same problem as Ken with the "S"s while transmitting from the
USRP-E110. I thought I would get your latest FPGA fix a try downloading
usrp_e100_fpga_v2.bin to /usr/local/share/uhd/images, saving the original E110
bin file, and renaming it to usrp_e110_fpga.bin. I thought that would be too
easy to fix the problem and it didn't. I got the following error:
linux; GNU C++ version 4.5.3 20110311 (prerelease); Boost_104500;
UHD_003.005.001-25-ge134b863
Creating the usrp device with: ...
-- Loading FPGA image: /usr/local/share/uhd/images/usrp_e110_fpga.bin... done =
1
ERROR: EnvironentError: OSError: INIT_B went high, error occurred.
I am guessing that there are some differences in the FPGA builds between the
E100 and E110. Do you have a version with the fixes for the E110???
Bill Macre
Applied Communication Sciences
-----Original Message-----
From: USRP-users [mailto:[email protected]] On Behalf Of
McKeever, Kenneth R.
Sent: Thursday, February 21, 2013 8:59 AM
To: [email protected]; [email protected]
Subject: Re: [USRP-users] USRP E100
Hi Josh,
I replaced the file and the problem still remained. However, it seemed to take
a bit longer before the sequence errors kicked in.
Thanks,
Ken
On 2/20/13 10:12 PM, "Josh Blum" <[email protected]> wrote:
>
>
>On 02/20/2013 06:37 AM, Leonardo S. Cardoso wrote:
>> Hello all,
>>
>> I've been having "S" (sequence) problems trying to transmit with my
>> USRP e100. I've recently updated all of my GNU Radio (3.6.2) and UHD
>> (UHD_003.005.000) installation, with no luck...
>>
>> Looking for info on the web, I've seen this error reported before for
>>earlier versions of the UHD driver. I've tried all the versions of the
>>UHD driver I could find online with no luck. Is there something I'm
>>missing?
>>
>> Can anyone help?
>
>Sorry guys. Its looks like there is an unconstrained path. Can you try
>this fpga image in place of the one on your system in
>/usr/share/uhd/images (this is where opkg puts it)
>
>http://files.ettus.com/binaries/e100-misc/usrp_e100_fpga_v2.bin
>
>-josh
>
>>
>> Thank you.
>>
>> Best,
>>
>> Leonardo S. Cardoso
>> [email protected]
>>
>>
>>
>> _______________________________________________
>> 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
------------------------------
Message: 5
Date: Wed, 27 Feb 2013 10:32:08 -0500
From: Michael Yan <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: [USRP-users] Libertas driver for the W2CBW003
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hi,
For our application, we wish to decode 802.11 packets on a consumer
grade wifi module. I'm reaching out to anyone who has replaced the
Gumstix Overo board in the E100-series machine with a wifi-enabled
Gumstix board, namely the Overo FireSTORM. I have already replaced the
board in our machine, but have been unable to get the wifi module to
work (Everything else seems to work perfectly).
The FireSTORM has the exact same configuration as the packaged Gumstix
board, but with the addition of a wifi module soldered on. I see no
reason why reason it shouldn't work, and suspect it is a driver problem.
Namely, in my driver log, I found the following error:
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
cfg80211: Calling CRDA to update world regulatory domain
libertas_sdio: Libertas SDIO driver
libertas_sdio: Copyright Pierre Ossman
libertas_sdio: failed to find firmware (-2)
libertas_sdio: probe of mmc1:0001:1 failed with error -2
Has anyone else attempted to do this? I've tried downloading the
relevant linux-firmware files and placing them in /lib/firmware, but
that didn't seem to work (same error).
Regards,
Michael Yan
HCLab, University of Waterloo
------------------------------
Message: 6
Date: Wed, 27 Feb 2013 16:20:09 +0000
From: "Macre, William R" <[email protected]>
To: "Macre, William R" <[email protected]>, "McKeever, Kenneth R."
<[email protected]>, "[email protected]" <[email protected]>,
"[email protected]" <[email protected]>
Cc: "Hodge, James E" <[email protected]>, "Miller, Robert David"
<[email protected]>
Subject: Re: [USRP-users] USRP E100
Message-ID:
<5e9bdf6832e57149b46d9becf6ab21510cf1b...@rrc-ats-exmb2.ats.atsinnovate.com>
Content-Type: text/plain; charset="us-ascii"
Josh:
Correction: I downloaded the tested your second build:
http://files.ettus.com/binaries/e100-misc/usrp_e100_fpga_v2_timing.bin
not the first one:
http://files.ettus.com/binaries/e100-misc/usrp_e100_fpga_v2.bin
bill
-----Original Message-----
From: USRP-users [mailto:[email protected]] On Behalf Of
Macre, William R
Sent: Wednesday, February 27, 2013 10:30 AM
To: McKeever, Kenneth R.; [email protected]; [email protected]
Cc: Hodge, James E; Miller, Robert David
Subject: Re: [USRP-users] USRP E100
Josh:
I am having the same problem as Ken with the "S"s while transmitting from the
USRP-E110. I thought I would get your latest FPGA fix a try downloading
usrp_e100_fpga_v2.bin to /usr/local/share/uhd/images, saving the original E110
bin file, and renaming it to usrp_e110_fpga.bin. I thought that would be too
easy to fix the problem and it didn't. I got the following error:
linux; GNU C++ version 4.5.3 20110311 (prerelease); Boost_104500;
UHD_003.005.001-25-ge134b863 Creating the usrp device with: ...
-- Loading FPGA image: /usr/local/share/uhd/images/usrp_e110_fpga.bin... done =
1
ERROR: EnvironentError: OSError: INIT_B went high, error occurred.
I am guessing that there are some differences in the FPGA builds between the
E100 and E110. Do you have a version with the fixes for the E110???
Bill Macre
Applied Communication Sciences
-----Original Message-----
From: USRP-users [mailto:[email protected]] On Behalf Of
McKeever, Kenneth R.
Sent: Thursday, February 21, 2013 8:59 AM
To: [email protected]; [email protected]
Subject: Re: [USRP-users] USRP E100
Hi Josh,
I replaced the file and the problem still remained. However, it seemed to take
a bit longer before the sequence errors kicked in.
Thanks,
Ken
On 2/20/13 10:12 PM, "Josh Blum" <[email protected]> wrote:
>
>
>On 02/20/2013 06:37 AM, Leonardo S. Cardoso wrote:
>> Hello all,
>>
>> I've been having "S" (sequence) problems trying to transmit with my
>> USRP e100. I've recently updated all of my GNU Radio (3.6.2) and UHD
>> (UHD_003.005.000) installation, with no luck...
>>
>> Looking for info on the web, I've seen this error reported before for
>>earlier versions of the UHD driver. I've tried all the versions of the
>>UHD driver I could find online with no luck. Is there something I'm
>>missing?
>>
>> Can anyone help?
>
>Sorry guys. Its looks like there is an unconstrained path. Can you try
>this fpga image in place of the one on your system in
>/usr/share/uhd/images (this is where opkg puts it)
>
>http://files.ettus.com/binaries/e100-misc/usrp_e100_fpga_v2.bin
>
>-josh
>
>>
>> Thank you.
>>
>> Best,
>>
>> Leonardo S. Cardoso
>> [email protected]
>>
>>
>>
>> _______________________________________________
>> 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
_______________________________________________
USRP-users mailing list
[email protected]
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
------------------------------
Message: 7
Date: Wed, 27 Feb 2013 16:33:46 +0000
From: "Macre, William R" <[email protected]>
To: Michael Yan <[email protected]>, "[email protected]"
<[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [USRP-users] Libertas driver for the W2CBW003
Message-ID:
<5e9bdf6832e57149b46d9becf6ab21510cf1b...@rrc-ats-exmb2.ats.atsinnovate.com>
Content-Type: text/plain; charset="us-ascii"
Michael Yan:
The Overo FireSTORM uses the WI2Wi W2CBW003 - 802.11 b/g +Bluetooth part. using
the Marvell 88W8686 SDIO/GSPI chip. The chip vendor recommends you use their
WIFI driver and not the libertas_sdio driver supplied with the unit. I would
start with sales @ WI2WI:
David Brassfield
Wi2Wi, Inc. WiFi/Bluetooth/GPS
Director of Sales, Americas East
847-566-6630: Chicago Office
847-217-7360: Mobile
[email protected]
If you intend to modify the source code you will need to sign a Non-Disclosure
Agreement (NDA) and a Source License Agreement (SLA) before they will provide
you with the source code.
Wrm
-----Original Message-----
From: USRP-users [mailto:[email protected]] On Behalf Of
Michael Yan
Sent: Wednesday, February 27, 2013 10:32 AM
To: [email protected]
Cc: [email protected]
Subject: [USRP-users] Libertas driver for the W2CBW003
Hi,
For our application, we wish to decode 802.11 packets on a consumer grade wifi
module. I'm reaching out to anyone who has replaced the Gumstix Overo board in
the E100-series machine with a wifi-enabled Gumstix board, namely the Overo
FireSTORM. I have already replaced the board in our machine, but have been
unable to get the wifi module to work (Everything else seems to work perfectly).
The FireSTORM has the exact same configuration as the packaged Gumstix board,
but with the addition of a wifi module soldered on. I see no reason why reason
it shouldn't work, and suspect it is a driver problem.
Namely, in my driver log, I found the following error:
lib80211: common routines for IEEE802.11 drivers
lib80211_crypt: registered algorithm 'NULL'
cfg80211: Calling CRDA to update world regulatory domain
libertas_sdio: Libertas SDIO driver
libertas_sdio: Copyright Pierre Ossman
libertas_sdio: failed to find firmware (-2)
libertas_sdio: probe of mmc1:0001:1 failed with error -2
Has anyone else attempted to do this? I've tried downloading the relevant
linux-firmware files and placing them in /lib/firmware, but that didn't seem to
work (same error).
Regards,
Michael Yan
HCLab, University of Waterloo
_______________________________________________
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 30, Issue 27
******************************************
