It's hard to tell in the pcap file where it gets lost. I'm not using a
dissector for the UHD packets so I can't see whats in the data field, thus
I can't match up commands coming/going. I have confirmed that this issue
does not exist when I'm using 003.004.X firmware and fpga load.
Tim
On Fri,
On 06/21/2013 09:41 AM, Tim Newman wrote:
> Yes, bringing this back up. Back to the original topic. When I get this
> FIFO ctrl error, the host is sending back an icmp port unreachable msg to
> the usrp, I grab this using wireshark.
>
Well if the app shutdown from the error. That could be the
Yes, bringing this back up. Back to the original topic. When I get this
FIFO ctrl error, the host is sending back an icmp port unreachable msg to
the usrp, I grab this using wireshark.
All I'm doing is running "uhd_usrp_probe". I've tried with and without
adding the --args addr= parameter, same
I think 512 is the max value for N on N200/N210 hence 195kSps is minimum sample
rate.
Karan Talasila wrote:
>@sean can you please tell me how you got minimum sampling rate for usrp N210
>as 100*e6/512. I know that the sampling rate should be 100*e6/N where N is an
>integer. So N can be any in
On 06/12/2013 11:07 PM, Karan Talasila wrote:
@sean can you please tell me how you got minimum sampling rate for
usrp N210 as 100*e6/512. I know that the sampling rate should be
100*e6/N where N is an integer. So N can be any integer even greater
than 512 right. In that way, what is the minimum
@sean can you please tell me how you got minimum sampling rate for usrp
N210 as 100*e6/512. I know that the sampling rate should be 100*e6/N where
N is an integer. So N can be any integer even greater than 512 right. In
that way, what is the minimum that the USRP accepts. what is maximum N that
can
On 06/12/2013 08:29 PM, Sean Nowlan wrote:
The minimum "reasonable" sample rate I've used is 2e5 (100e6/2e5 =
500). I think 100e6/512 = 195312.5 is the smallest supported rate.
Yup, sorry, you're right. I tend to pick values that are valid for both
64Msps and 100Msps master clock rates, sin
On 06/12/2013 08:49 PM, Marcus D. Leech wrote:
On 06/12/2013 08:29 PM, Sean Nowlan wrote:
The minimum "reasonable" sample rate I've used is 2e5 (100e6/2e5 =
500). I think 100e6/512 = 195312.5 is the smallest supported rate.
Yup, sorry, you're right. I tend to pick values that are valid for
On 06/12/2013 08:09 PM, Marcus D. Leech wrote:
On 06/12/2013 08:00 PM, Jay Prakash wrote:
Sry,
It's switch but not a dedicated one.
Sample rate 1M.
But error came even at 32k.
Jay Prakash
Well, 32K isn't a valid sample rate, Jay.
Sample rates have to be a proper integer fraction of the maste
On 06/12/2013 07:14 PM, Jay Prakash wrote:
> I am connecting it on LAN using D-Link router.
>
>
Is the dlink router have gigabit ethernet on all ports between USRP and
PC? Sorry to say I have never had good experiences with dlink products,
and that includes outside of the USRP realm. :-(
A lo
On 06/12/2013 08:00 PM, Jay Prakash wrote:
Sry,
It's switch but not a dedicated one.
Sample rate 1M.
But error came even at 32k.
Jay Prakash
Well, 32K isn't a valid sample rate, Jay.
Sample rates have to be a proper integer fraction of the master clock
rate on the USRP device. For the N210,
Sry,
It's switch but not a dedicated one.
Sample rate 1M.
But error came even at 32k.
Jay Prakash
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
On 06/12/2013 07:14 PM, Jay Prakash wrote:
I am connecting it on LAN using D-Link router.
A router, or a switch?
What sample rates?
At higher sample rates, most low-end switch/router fabrics tend to fall
over and start dropping packets.
You shouldn't really think of the N210 1GiGe connecti
I am connecting it on LAN using D-Link router.
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
ender: discuss-gnuradio-bounces+tim.newman=gmail.com@gnu.orgDate: Wed, 12 Jun
2013 19:01:49
To:
Reply-To: j...@joshknows.com
Subject: Re: [Discuss-gnuradio] Run time FIFO error
On 06/12/2013 06:54 PM, Marcus D. Leech wrote:
> On 06/12/2013 06:52 PM, Jay Prakash wrote:
>
On 06/12/2013 06:54 PM, Marcus D. Leech wrote:
> On 06/12/2013 06:52 PM, Jay Prakash wrote:
>> USRP N210
>>
>>
>>
>> ___
>> Discuss-gnuradio mailing list
>> Discuss-gnuradio@gnu.org
>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> This error
On 06/12/2013 06:52 PM, Jay Prakash wrote:
USRP N210
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
This error is usually caused by the network connection dropping packets.
Are you
USRP N210
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
On 06/12/2013 06:25 PM, Jay Prakash wrote:
File
"/usr/local/lib/python2.7/dist-packages/gnuradio/uhd/__init__.py",
line 116, in constructor_interceptor
return old_constructor(*args)
File
"/usr/local/lib/python2.7/dist-packages/gnuradio/uhd/uhd_swig.py",
line 2895, in usrp_sink
return
File "/usr/local/lib/python2.7/dist-packages/gnuradio/uhd/__init__.py",
line 116, in constructor_interceptor
return old_constructor(*args)
File "/usr/local/lib/python2.7/dist-packages/gnuradio/uhd/uhd_swig.py",
line 2895, in usrp_sink
return _uhd_swig.usrp_sink(*args)
RuntimeError: RuntimeE
20 matches
Mail list logo
