t;>>>>>> See the transport application notes on buffer resizing.
>>>>>>>>>>>>> Please run: sudo sysctl -w net.core.wmem_max=250
>>>>>>>>>>>>> [WARNING] [UDP] The send buffer could not be resized
>
>>>>>>> [WARNING] [UDP] The send buffer could not be resized
>>>>>>>>>>>> sufficiently.
>>>>>>>>>>>> Target sock buff size: 250 bytes.
>>>>>>>>>>>> Actual sock buff size: 104857
ort application notes on buffer resizing.
>>>>>>>>>>> Please run: sudo sysctl -w net.core.wmem_max=250
>>>>>>>>>>> [WARNING] [UDP] The send buffer could not be resized
>>>>>>>>>>> s
t;> may be negatively affected.
>>>>>>>>>> Please see the general application notes in the manual for
>>>>>>>>>> instructions.
>>>>>>>>>> EnvironmentError: OSError: error in pthread_setschedparam
>>&g
your PC?
*From:* Sumit Kumar
mailto:cog...@gmail.com>>
*Se
.
>>>>>>>>> EEPROM ["hardware"] is "2576"
>>>>>>>>> EEPROM ["revision"] is ""
>>>>>>>>> EEPROM ["product"] is ""
>>>>>>>>> EEPROM ["mac-addr"] is "a0:36:fa:26:34:44&
"
>>>>>>>> EEPROM ["serial"] is "E4R14V4UN"
>>>>>>>> EEPROM ["name"] is ""
>>>>>>>>
>>>>>>>> Power-cycle the USRP device for the changes to take effect
hd/host/build/utils$
>>>>>>> ./usrp_burn_mb_eeprom --read-all --args "addr=192.168.10.3"
>>>>>>> Creating USRP device from address: addr=192.168.10.3
>>>>>>> [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800;
>>&g
ombs/src/uhd/host/build/utils$
>>>>>>> ./usrp_burn_mb_eeprom --read-all --args "addr=192.168.10.3"
>>>>>>> Creating USRP device from address: addr=192.168.10.3
>>>>>>> [INFO] [UHD] linux; GNU C++ version 5.4.0
-
*From:* USRP-users
mailto:usrp-users-boun...@lists.ettus.com>>
on behalf of Sumit Kumar via
USRP-users
frame size: 1472 bytes
>>>>>> [INFO] [USRP2] Current send frame size: 1472 bytes
>>>>>> [WARNING] [UDP] The send buffer could not be resized sufficiently.
>>>>>> Target sock buff size: 250 bytes.
>>>>>> Actual sock buff size:
zed sufficiently.
>>>>> Target sock buff size: 250 bytes.
>>>>> Actual sock buff size: 1048576 bytes.
>>>>> See the transport application notes on buffer resizing.
>>>>> Please run: sudo sysctl -w net.core.wmem_max=250
>>>&
gt;>> [WARNING] [UHD] 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
>&g
m EEPROM...
>>> EEPROM ["hardware"] is "2576"
>>> EEPROM ["revision"] is ""
>>> EEPROM ["product"] is ""
>>> EEPROM ["mac-addr"] is "a0:36:fa:26:34:42"
>>> EEPROM
-all
>>>
>>> don't quote me on the type portion, I don't have a board in front of me
>>> to see if it is n200 or something else. I //think// that will report the
>>> major and minor revision values (I am grasping at straws here, just trying
>>> to
eering.com> wrote:
>
>> You are right, the table of revisions was for the X-series
>>
>> try running the command from your prefix:
>> src/uhd/host/build/utils/usrp_burn_mb_eeprom --args="type=n200" --read-all
>>
>> don't quote me on the type po
---
> *From:* USRP-users on behalf of
> Sumit Kumar via USRP-users
> *Sent:* Wednesday, July 17, 2019 7:06 AM
> *To:* Jason Matusiak
> *Cc:* usrp-users@lists.ettus.com
> *Subject:* Re: [USRP-users] Sequence Errors N200
>
> Following is what I am getting after
ils/usrp_burn_mb_eeprom --args="type=n200" --read-all
>
> don't quote me on the type portion, I don't have a board in front of me to
> see if it is n200 or something else. I //think// that will report the
> major and minor revision values (I am grasping at straws he
d doing a uhd_usrp_probe on both devices and seen that the
>> responses are consistent?
>>
>> --
>> *From:* USRP-users on behalf of
>> Sumit Kumar via USRP-users
>> *Sent:* Wednesday, July 17, 2019 7:15 AM
>> *To:* usrp-users@lists.ettus.com
>&
___
From: Sumit Kumar
Sent: Wednesday, July 17, 2019 8:24 AM
To: Jason Matusiak
Cc: usrp-users@lists.ettus.com
Subject: Re: [USRP-users] Sequence Errors N200
The sticker for sbx shows F33612 and F33814.
How will this help ?
On Wed, Jul 17, 2019 at 1:50 PM Jason
s@lists.ettus.com>>
*Sent:* Wednesday, July 17, 2019 7:15 AM
*To:* usrp-users@lists.ettus.com
<mailto:usrp-users@lists.ettus.com> mailto:usrp-users@lists.ettus.com>>
*Subject:* [USRP-users] Sequence Errors N200
Hi,
I am trying transmit using Ettus N200 (call it A)
7:45 AM
> *To:* Jason Matusiak
> *Cc:* usrp-users@lists.ettus.com
> *Subject:* Re: [USRP-users] Sequence Errors N200
>
> Hi Jason,
>
> Yes they are consistent, I mean the output of uhd_usrp_probe for both N200
> is exactly the same (except the ip, serial and mac addr).
&
?
From: Sumit Kumar
Sent: Wednesday, July 17, 2019 7:45 AM
To: Jason Matusiak
Cc: usrp-users@lists.ettus.com
Subject: Re: [USRP-users] Sequence Errors N200
Hi Jason,
Yes they are consistent, I mean the output of uhd_usrp_probe for both N200 is
exactly the same (except the ip
USRP-users
> *Sent:* Wednesday, July 17, 2019 7:15 AM
> *To:* usrp-users@lists.ettus.com
> *Subject:* [USRP-users] Sequence Errors N200
>
> Hi,
> I am trying transmit using Ettus N200 (call it
7:15 AM
To: usrp-users@lists.ettus.com
Subject: [USRP-users] Sequence Errors N200
Hi,
I am trying transmit using Ettus N200 (call it A) but getting this error
message on the co
Hi,
I am trying transmit using Ettus N200 (call it A) but getting this error
message on the console
SSU...
26 matches
Mail list logo
