On 06/14/2011 07:10 AM, David Scaperoth wrote:
> On Tue, Oct 19, 2010 at 9:39 PM, Josh Blum wrote:
>
>>
>>
>> On 10/19/2010 06:14 PM, b...@sigmatix.com wrote:
>>
>>>
>>> We're exploring the possibility of monitoring the overrun/underrun
>>> status via the USRP2 UART.
>>>
>>>
>> FYI, the USRP2 u
On Tue, Oct 19, 2010 at 9:39 PM, Josh Blum wrote:
>
>
> On 10/19/2010 06:14 PM, b...@sigmatix.com wrote:
>
>>
>> We're exploring the possibility of monitoring the overrun/underrun
>> status via the USRP2 UART.
>>
>>
> FYI, the USRP2 under UHD reports underflows as async messages to the host
> tha
On 10/19/2010 06:14 PM, b...@sigmatix.com wrote:
We're exploring the possibility of monitoring the overrun/underrun
status via the USRP2 UART.
FYI, the USRP2 under UHD reports underflows as async messages to the
host that can be accessed through the API. There are no true overflows
since
On Tue, Oct 19, 2010 at 8:14 PM, wrote:
>
> We're exploring the possibility of monitoring the overrun/underrun status via
> the USRP2 UART.
>
> I'm curious to learn what approaches people have taken to do this (e.g.,
> connect the UART to a logic analyzer, use a level shifter -> RS232 -> host
We're exploring the possibility of monitoring the overrun/underrun status via
the USRP2 UART.
I'm curious to learn what approaches people have taken to do this (e.g.,
connect the UART to a logic analyzer, use a level shifter -> RS232 -> host
serial/USB port, etc.).
I'd also like to know wha