On 2022-10-17 03:41, Mikio Fukushima wrote:
Hi,
I want to use one or two channels on one LFRX on a N210 on Windows.
but fifo ctrl timeout error occured.
uhd_usrp_probe, uhd_find_device and ping are OK.
Why?
- Environment
Windows 10
UHD 4.3.0.0 (x64, VS2019)
LFRX on USRP2(r4)
- error message
C:\Program Files\UHD\lib\uhd\examples>rx_samples_to_file.exe --args
"addr=192.168.1.52" --rate 1e6 --freq 1e6
Creating the usrp device with: addr=192.168.1.52...
[INFO] [UHD] Win32; Microsoft Visual C++ version 1925; Boost_107000;
UHD_4.2.0.0-release
[INFO] [USRP2] Opening a USRP2/N-Series device...
[INFO] [USRP2] Current recv frame size: 1472 bytes
[INFO] [USRP2] Current send frame size: 1472 bytes
Using Device: Single USRP:
Device: USRP2 / N-Series Device
Mboard 0: USRP2 r4
RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: LFRX (AB)
TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: LFTX (AB)
Setting RX Rate: 1.000000 Msps...
[ERROR] [UHD] Exception caught in safe-call.
in usrp2_fifo_ctrl_impl::~usrp2_fifo_ctrl_impl
at
C:\Users\buildbot\worker0\Builder_uhdPackage_Windows_x64_vs2019\work\uhd\host\lib\usrp\usrp2\usrp2_fifo_ctrl.cpp:51
this->peek32(0); -> RuntimeError: fifo ctrl timed out looking for acks
Error: LookupError: IndexError: multi_usrp: RX channel 12 out of range
for configured RX frontends
The "fifo ctrl timed out" message usually happens when the network
buffering is inadequate, and UHD is losing packets--although
at 1Msps, it surely shouldn't be. But this is a windows deployment,
and I'm much less familiar with its quirks.
The MORE concerning thing is the message about RX channel 12 out of
range. I'm not sure what it's trying to convey,
but there's no way to have 12 channels on a single USRP N210.
Could you try dropping back to an older version of UHD (3.15 perhaps?)
to see if this is still present?
_______________________________________________
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com
