On 10/31/2017 08:05 PM, Kevin McGuire wrote:
On Tue, Oct 31, 2017 at 11:53 PM, Marcus D. Leech > wrote:
The N200 will ONLY run at 1GiGe rates--so if your computer cannot
support 1GiGe, no communication will be possible at all--it won't
On 10/31/2017 07:31 PM, Kevin McGuire via USRP-users wrote:
Hey,
I am used to the B200 over USB3. So with the N200 and uhd_rx_cfile
utility I /finally/ realized that it reports dropped packets as the
letter D to the terminal output. I guess I was thinking it was D for
data and yes the
Make this question fairly low priority.
Just realized the N200 supports gigabit ethernet. I think that might be
what happened. I calculated it in my pre-planning phase then did not
realize my network here is limited to 100MBit, but that is an easy fix so
not worries.
On Tue, Oct 31, 2017 at
On 10/31/2017 04:21 PM, Mark Koenig via USRP-users wrote:
Again,
Looking to see if anyone can help on this.
One more detail is that I am unable to reboot the N210 into safe mode,
thus no green lights come on.
Thanks
Mark
OK, so you've followed the JTAG-based procedures here
That does not work. Here is an excerpt from dmesg followed by the commands:
[2.591180] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[2.633612] IPv6: ADDRCONF(NETDEV_UP): wlp58s0: link is not ready
[2.899173] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[2.899175] Bluetooth:
Again,
Looking to see if anyone can help on this.
One more detail is that I am unable to reboot the N210 into safe mode, thus no
green lights come on.
Thanks
Mark
From: Mark Koenig
Date: Thursday, October 26, 2017 at 1:25 PM
To:
Hi,
This might work for our setup as well, since pressing the S700 after boot does
make our machine recognize the B210! At least testing with one machine, the
S700 switch seems to help after a cold boot.
Thanks
T
> Original Message
> Subject: RE: [USRP-users] Problems with
Hi Neel,
1. Indeed that is right. It seems that the newer NUCs with latest firmware
consistently do not recognize B210s from cold boots.
2. That is correct.
Thanks
TM
> Original Message
> Subject: Re: [USRP-users] Problems with Ettus B210 and Intel Nuk
> Local Time: October
Hi Tathagata,
After you boot, if you run: $UHD_INSTALL_PREFIX/utils/b2xx_fx3_utils
--reset-device
Are you able to then initialize the USRP by running uhd_usrp_probe?
Regards,
Nate Temple
> On Oct 31, 2017, at 11:11 AM, Neel Pandeya via USRP-users
> wrote:
>
>
On 10/31/2017 02:14 PM, Oliver Wayne wrote:
I run into the same issue while reading from the file. Even if I put
in a higher sample rate while inputting to the File Sink (so I get the
frequencies that I want), the device hits underflows while reading
from the File Source because it can't
I run into the same issue while reading from the file. Even if I put in a
higher sample rate while inputting to the File Sink (so I get the
frequencies that I want), the device hits underflows while reading from the
File Source because it can't sustain that sample rate. Are there any other
ways to
Hello Tathagata:
If I recall from a separate conversation, after you upgraded the BIOS on
this Intel NUC, the system would no longer recognize the B210, right?
Before the BIOS upgrade, the B210 would still be recognized, but only after
a long 30- or 60-second delay, right?
--Neel Pandeya
On
Hey T,
I encountered a problem similar to this in the past with a Minnowboard Max. If
you press the reset switch (S700 I believe), is the NUC able to see the B210
(instead of unplugging USB)? I had to do this if I had a B200 plugged into the
Minnowboard while it booted.
The solution we came
Another thought I had -- because I don't anticipate my waveform changing
much, is there a way to pre-record my waveform and transmit it
continuously, which if I understand the problem correctly would avoid the
underruns?
On Mon, Oct 30, 2017 at 3:28 PM, Oliver Wayne
Hi all,
I have been working with the X300 for a while now and just recently started
getting UHD this error back:
>>>
UHD Error:
x300 fw communication failure #1
EnvironmentError: IOError: x300 fw poke32 - reply timed out
>>>
At which point I (obviously) can no longer get any sort of
I am trying to set "spp" parameter for rx stream to match some time period
but attached test program fails as following:
$ sudo ./test1
linux; GNU C++ version 4.8.4; Boost_105400; UHD_003.010.002.000-5-g4bbf0c20
-- X300 initialization sequence...
-- Connecting to niusrpriorpc at
Hello
I have made a grc with the chanmux and the poly_channelizer . The problem is
when I connect the poly_channelizer I don't get any output from it , but if
remove it and connect the QT GUI sink to the chanmux it gives me output. I have
attached the grc file for your reference. Please help
30 okt. 2017 kl. 20:53 skrev Torbjörn Olsson :
Hello,
I am trying to make my E312 identify nearby transmitters by using the
gr-inspector toolbox. So far I have managed to get the E312 to ”pipe” complex
data to the host through ZMQ (based on the excellent instruction
Those issues have been fixed lately, so please pull the latest changes at
fpga:rfnoc-devel and try again.
Additionally, please point the image builder to the top OOT directory as
follows:
$./uhd_image_builder.py chanmux -I ~/OMessenger/Receivedfiles/
rfnoc-pfb-channelizer-master/ -d x310 -t
Hello Nicolas
When I use uhd_image_builder_gui.py to generate an image, on selecting
X310_RFNOC_HG as target, it automatically adds the parameter I without setting
any argument to it and also doesn't allow us to set it manually. On using
uhd_image_builder.py and setting I to
20 matches
Mail list logo