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. Re: Thread AssertionError and Libc++abi.dylib on Mac
Transmissions (Tor Andre Myrvoll)
2. is it possible to transmit and receive a constant signal via
USRP? (gang li)
3. Re: is it possible to transmit and receive a constant signal
via USRP? (Josh Blum)
4. Re: is it possible to transmit and receive a constant signal
via USRP? (gang li)
5. Re: Thread AssertionError and Libc++abi.dylib on Mac
Transmissions (Josh Blum)
6. B100 no longer detected (James Balnaves)
7. Re: B100 no longer detected (Nick Foster)
8. Re: B100 no longer detected (James Balnaves)
9. Re: B100 no longer detected (Marcus D. Leech)
10. Re: B100 no longer detected (James Balnaves)
11. Re: B100 no longer detected (James Balnaves)
12. Re: B100 no longer detected (Michael Ossmann)
13. Re: Thread AssertionError and Libc++abi.dylib on Mac
Transmissions (David Greene)
----------------------------------------------------------------------
Message: 1
Date: Mon, 14 Jan 2013 18:40:29 +0100
From: Tor Andre Myrvoll <[email protected]>
To: David Greene <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [USRP-users] Thread AssertionError and Libc++abi.dylib on
Mac Transmissions
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
14. jan. 2013 kl. 17:47 skrev David Greene <[email protected]>:
> Hey Folks,
>
> I've installed the latest version of GNURadio (3.6.3) using MacPorts on a
> fresh Macbook Pro running 10.8.2 using,
>
[snip]
> Mac OS; GNU C++ version 4.2.1 (Based on Apple Inc. build 5658) (LLVM build
> 2336.11.00); Boost_105100; UHD_003.005.000-0-unknown
>
> -- Opening a USRP2/N-Series device...
> -- Current recv frame size: 1472 bytes
> -- Current send frame size: 1472 bytes
> Uthread[thread-per-block[1]: <gr_block gr uhd usrp sink (1)>]:
> AssertionError: ::send(_sock_fd, (const char *)_mem, size(), 0) ==
> ssize_t(size())
> in virtual void udp_zero_copy_asio_msb::release()
> at
> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports
> .org_release_tarballs_ports_science_uhd/uhd/work/UHD-Mirror-release_003_005_
> 000/host/lib/transport/udp_zero_copy.cpp:115
I get this behaviour when using a single N210 as well. Josh indicated in a post
that quite a few users are on OS X and that this issue hasn't been raised
before, but I see that you use the same release of OS X as me, 10.8.2. If
someone can confirm that using e.g. examples/tx_waveforms on a 10.7 or 10.6
version of OS X has no problems, a case can be made that Mountain Lion is
somehow the culprit here.
--
- Tor Andre
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/attachments/20130114/ebc501d7/attachment-0001.html>
------------------------------
Message: 2
Date: Mon, 14 Jan 2013 15:49:11 -0500
From: gang li <[email protected]>
To: [email protected]
Subject: [USRP-users] is it possible to transmit and receive a
constant signal via USRP?
Message-ID:
<CAKro2L3uB2euHyyFG7LAa+yi+_Wf0e7h-Nw1_Gv61tz0A=8...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Hi, all,
I am now working on USRP N210 with SBX. I am wondering whether i can
transmit and receive a constant signal by usrp. So the carrier wave
is not modulated. But usrp will treat this signal as a DC and try to
remove it. So is it possible to cancel the DC offset removal? And will
it bring some bad effects? Any reply will be appreciated!
Best,
Gang
------------------------------
Message: 3
Date: Mon, 14 Jan 2013 14:59:16 -0600
From: Josh Blum <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] is it possible to transmit and receive a
constant signal via USRP?
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
On 01/14/2013 02:49 PM, gang li wrote:
> Hi, all,
>
> I am now working on USRP N210 with SBX. I am wondering whether i can
> transmit and receive a constant signal by usrp. So the carrier wave
> is not modulated. But usrp will treat this signal as a DC and try to
> remove it. So is it possible to cancel the DC offset removal? And will
> it bring some bad effects? Any reply will be appreciated!
There is a way to disable dc offset removal. However, you will see your
signal + the DC level of the RF frontend:
http://files.ettus.com/uhd_docs/doxygen/html/classuhd_1_1usrp_1_1multi__usrp.html#a7beb49c1a04a81b3e7569db482453746
Now, in the real world of course, things are not so perfect and there is
some frequency offset between two devices, so your tone may not show up
exactly at DC.
You can also tune with an LO offset to place the DC removal out of your
band of interest:
http://files.ettus.com/uhd_docs/manual/html/general.html#tuning-notes
-josh
>
> Best,
> Gang
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
------------------------------
Message: 4
Date: Mon, 14 Jan 2013 16:08:26 -0500
From: gang li <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: Re: [USRP-users] is it possible to transmit and receive a
constant signal via USRP?
Message-ID:
<CAKro2L17Pf0AzQYKd88cQt4RjLgL0fe1Qq_FXjea8A6Ud1=z...@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Thanks a lot! I will try it and see what happens. Currently i am using
one USRP N210 to do the full duplex considering the frequency offset
on two USRPs. Later I will use two USRPs.
Best,
Gang
On Mon, Jan 14, 2013 at 3:59 PM, Josh Blum <[email protected]> wrote:
>
>
> On 01/14/2013 02:49 PM, gang li wrote:
>> Hi, all,
>>
>> I am now working on USRP N210 with SBX. I am wondering whether i can
>> transmit and receive a constant signal by usrp. So the carrier wave
>> is not modulated. But usrp will treat this signal as a DC and try to
>> remove it. So is it possible to cancel the DC offset removal? And will
>> it bring some bad effects? Any reply will be appreciated!
>
> There is a way to disable dc offset removal. However, you will see your
> signal + the DC level of the RF frontend:
>
> http://files.ettus.com/uhd_docs/doxygen/html/classuhd_1_1usrp_1_1multi__usrp.html#a7beb49c1a04a81b3e7569db482453746
>
> Now, in the real world of course, things are not so perfect and there is
> some frequency offset between two devices, so your tone may not show up
> exactly at DC.
>
> You can also tune with an LO offset to place the DC removal out of your
> band of interest:
> http://files.ettus.com/uhd_docs/manual/html/general.html#tuning-notes
>
> -josh
>
>>
>> Best,
>> Gang
>>
>> _______________________________________________
>> 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: Mon, 14 Jan 2013 16:08:16 -0600
From: Josh Blum <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] Thread AssertionError and Libc++abi.dylib on
Mac Transmissions
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
> I get this behaviour when using a single N210 as well. Josh indicated
> in a post that quite a few users are on OS X and that this issue
> hasn't been raised before, but I see that you use the same release of
> OS X as me, 10.8.2. If someone can confirm that using e.g.
> examples/tx_waveforms on a 10.7 or 10.6 version of OS X has no
> problems, a case can be made that Mountain Lion is somehow the
> culprit here.
>
I was hesitant to change the socket code which was working for so long
as it was. So, I was trying to get to the bottom of the issue w/ OSX.
Perhaps its newer OSX. Still not sure... Anyway, the send/retry logic
should be OK to have for all platforms.
So here is my updated patch. I am going to test that this hasn't broke
anything under linux, and then I can get it into mainline and a patch
release.
http://pastebin.com/YtMu0xj5
-josh
------------------------------
Message: 6
Date: Mon, 14 Jan 2013 17:59:35 -0800
From: James Balnaves <[email protected]>
To: [email protected]
Subject: [USRP-users] B100 no longer detected
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
I'm wondering if my B100 might have stopped working. I had it all set up and
working fine on Ubuntu. I've since been using Windows a bit and tried
installing USB drivers, but it could not detect the device. I figured it was a
64-bit driver issue and gave up. Now that I'm back on Linux I can't find the
device with 'lsusb'. I also tried connecting it to a Mac with 'system_profiler
SPUSBDataType', it's simply not showing up. Is it possible that I've messed up
the hardware?
Any insights appreciated.
James.
------------------------------
Message: 7
Date: Mon, 14 Jan 2013 18:08:56 -0800
From: Nick Foster <[email protected]>
To: James Balnaves <[email protected]>
Cc: [email protected]
Subject: Re: [USRP-users] B100 no longer detected
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 01/14/2013 05:59 PM, James Balnaves wrote:
> I'm wondering if my B100 might have stopped working. I had it all set up and
> working fine on Ubuntu. I've since been using Windows a bit and tried
> installing USB drivers, but it could not detect the device. I figured it was
> a 64-bit driver issue and gave up. Now that I'm back on Linux I can't find
> the device with 'lsusb'. I also tried connecting it to a Mac with
> 'system_profiler SPUSBDataType', it's simply not showing up. Is it possible
> that I've messed up the hardware?
> Any insights appreciated.
I don't think the hardware's messed up, but I guess it's possible. You
sure your USB cable is OK and the power supply is working? You sure you
didn't accidentally plug in the wrong power supply?
--n
>
> James.
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>
------------------------------
Message: 8
Date: Mon, 14 Jan 2013 18:17:43 -0800
From: James Balnaves <[email protected]>
To: Nick Foster <[email protected]>
Cc: [email protected]
Subject: Re: [USRP-users] B100 no longer detected
Message-ID: <[email protected]>
Content-Type: text/plain; charset=iso-8859-1
The power supply is the original one, no changes there. All lights are
illuminated on the front panel except for the D LED, and the internal fan is
whirring. I've tried connecting it to 3 different machines and I've tried both
the original cable that came with the hardware that was working and a
replacement cable. It doesn't show up as a USB device in any case.
Is there an internal reset or something else to try?
James.
On Jan 14, 2013, at 6:08 PM, Nick Foster wrote:
> On 01/14/2013 05:59 PM, James Balnaves wrote:
>> I'm wondering if my B100 might have stopped working. I had it all set up and
>> working fine on Ubuntu. I've since been using Windows a bit and tried
>> installing USB drivers, but it could not detect the device. I figured it was
>> a 64-bit driver issue and gave up. Now that I'm back on Linux I can't find
>> the device with 'lsusb'. I also tried connecting it to a Mac with
>> 'system_profiler SPUSBDataType', it's simply not showing up. Is it possible
>> that I've messed up the hardware?
>> Any insights appreciated.
> I don't think the hardware's messed up, but I guess it's possible. You sure
> your USB cable is OK and the power supply is working? You sure you didn't
> accidentally plug in the wrong power supply?
>
> --n
>
>>
>> James.
>> _______________________________________________
>> USRP-users mailing list
>> [email protected]
>> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
>>
>
------------------------------
Message: 9
Date: Mon, 14 Jan 2013 21:32:06 -0500
From: "Marcus D. Leech" <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] B100 no longer detected
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
On 14/01/13 09:17 PM, James Balnaves wrote:
> The power supply is the original one, no changes there. All lights are
> illuminated on the front panel except for the D LED, and the internal fan is
> whirring. I've tried connecting it to 3 different machines and I've tried
> both the original cable that came with the hardware that was working and a
> replacement cable. It doesn't show up as a USB device in any case.
> Is there an internal reset or something else to try?
>
> James.
Does "dmesg" output make any comment when you plug it into USB on your
Linux machine?
--
Principal Investigator
Shirleys Bay Radio Astronomy Consortium
http://www.sbrac.org
------------------------------
Message: 10
Date: Mon, 14 Jan 2013 18:59:09 -0800
From: James Balnaves <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] B100 no longer detected
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
dmesg responds with "usb 3-1: new high-speed USB device number 2 using
xhci_hcd" when I plug in the B100. Then shortly after I get "usb 3-1: device
descriptor read/8, error -110" a couple of times followed by the "new
high-speed USB device" message with an incremented device number.
James.
On Jan 14, 2013, at 6:32 PM, Marcus D. Leech wrote:
> On 14/01/13 09:17 PM, James Balnaves wrote:
>> The power supply is the original one, no changes there. All lights are
>> illuminated on the front panel except for the D LED, and the internal fan is
>> whirring. I've tried connecting it to 3 different machines and I've tried
>> both the original cable that came with the hardware that was working and a
>> replacement cable. It doesn't show up as a USB device in any case.
>> Is there an internal reset or something else to try?
>>
>> James.
> Does "dmesg" output make any comment when you plug it into USB on your
> Linux machine?
>
>
> --
> Principal Investigator
> Shirleys Bay Radio Astronomy Consortium
> http://www.sbrac.org
>
>
>
> _______________________________________________
> USRP-users mailing list
> [email protected]
> http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
------------------------------
Message: 11
Date: Mon, 14 Jan 2013 21:07:25 -0800
From: James Balnaves <[email protected]>
To: Michael Ossmann <[email protected]>
Cc: [email protected]
Subject: Re: [USRP-users] B100 no longer detected
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
I tried it in another port that I'm sure is USB 2.0 and I get exactly the same
behavior, except that the error message now refers to ehci_hcd.
I wonder if it's possible that the EEPROM got corrupted somehow when I tried to
install the windows USB driver?
On Jan 14, 2013, at 8:24 PM, Michael Ossmann <[email protected]> wrote:
> On Mon, Jan 14, 2013 at 06:59:09PM -0800, James Balnaves wrote:
>>
>> dmesg responds with "usb 3-1: new high-speed USB device number 2
>> using xhci_hcd" when I plug in the B100. Then shortly after I get "usb
>> 3-1: device descriptor read/8, error -110" a couple of times followed
>> by the "new high-speed USB device" message with an incremented device
>> number.
>
> Has it ever worked on that particular port? The xhci_hcd is the USB 3.0
> driver which is probably less stable than the ehci_hcd USB 2.0 (high
> speed) driver.
------------------------------
Message: 12
Date: Mon, 14 Jan 2013 21:24:56 -0700
From: Michael Ossmann <[email protected]>
To: James Balnaves <[email protected]>
Cc: [email protected]
Subject: Re: [USRP-users] B100 no longer detected
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
On Mon, Jan 14, 2013 at 06:59:09PM -0800, James Balnaves wrote:
>
> dmesg responds with "usb 3-1: new high-speed USB device number 2
> using xhci_hcd" when I plug in the B100. Then shortly after I get "usb
> 3-1: device descriptor read/8, error -110" a couple of times followed
> by the "new high-speed USB device" message with an incremented device
> number.
Has it ever worked on that particular port? The xhci_hcd is the USB 3.0
driver which is probably less stable than the ehci_hcd USB 2.0 (high
speed) driver.
------------------------------
Message: 13
Date: Tue, 15 Jan 2013 09:38:26 -0500
From: David Greene <[email protected]>
To: [email protected]
Subject: Re: [USRP-users] Thread AssertionError and Libc++abi.dylib on
Mac Transmissions
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
"
> but I see that you use the same release of OS X as me, 10.8.2
"
Tor, what version of boost and compiler are you using for UHD? Could you
send me the startup info when you begin a UHD application, say uhd_fft
for example:
Mac OS; GNU C++ version 4.2.1 (Based on Apple Inc. build 5658) (LLVM
build 2336.11.00); Boost_105100; UHD_003.005.000-0-unkown
I've eliminated the AssertionError by performing a fresh install and but
changing the build order. The only errors I'm getting now are
"libc++abi.dylib: terminate called without an active exception" and
OpenGL. If you could try this out and let me know your results, that
would help out a lot.
Here's what I've done:
// 1. Remove all current ports & update MacPorts
sudo port -f uninstall installed
sudo port selfupdate
// 2. Install Subversion
sudo port install subversion
// 3. Install boost 1.51 following MLD's instructions
cd .. // down to the root directory
sudo mkdir tmp_boost
cd tmp_boost
sudo svn co -r 98466
http://svn.macports.org/repository/macports/trunk/dports/devel/boost
cd boost
sudo port install +python27 configure.compiler=llvm-gcc-4.2
// 4. Install GNURadio
sudo port install gnuradio +full configure.compiler=llvm-gcc-4.2
// 5. Switch back to Boost 1.51
sudo port activate boost @1.51.0_1+no_single+no_static+python27
// 6. Uninstall & Reinstall UHD using Boost 1.51
sudo port -f uninstall uhd
sudo port install uhd configure.compiler=llvm-gcc-4.2
Let me know what you get. Good luck,
-David
------------------------------
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 29, Issue 15
******************************************
