We have an app using RFNoC Radio blocks running on the e310 that uses a TX
frequency hopping at ~70Hz and a non-hopping RX that is intermittently
re-tuned every few seconds.
We are experiencing an intermittent, but ultimately unrecoverable IO error
when sending tuning commands to our RFNoC radio blocks. After a few minutes
of running time we will see a command timeout exception caused by an
exception caused by a mismatch between the sequence number in the command
and the response:
*** RuntimeError: EnvironmentError: IOError: [0/Radio_0]
user_reg_read32() failed:
EnvironmentError: IOError: [0/Radio_0] sr_read32() failed:
EnvironmentError: IOError: Block ctrl (CE_00_Port_10) packet parse
error -
EnvironmentError: IOError: Expected packet index: 3261 Received index:
3262
All subsequent commands to either of our RX/TX RFNoC blocks trigger a this
exception so we are unable to recover from this error without restarting
the flowgraph.
Has anyone experienced this behavior or could suggest a troubleshooting
strategy?
Note: I think the values of “Expected packet index” and “Received index”
should be switched around in the exception message [1] (so we are expecting
3262 and receiving 3261)
[1] uhd/host/lib/rfnoc/ctrl_iface.cpp:282
[2] https://kb.ettus.com/RFNoC#Why_do_I_have_a_command_timeout_error.3F
_______________________________________________
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
