Discussion and technical support related to USRP, UHD, RFNoC
View all threadsHello,
I am currently trying to build an image with a 500 Mhz sampling rate with a custom block. However, I get the following error.
[ERROR] [RFNOC::GRAPH] Caught exception while initializing graph: RfnocError: OpTimeout: Control operation timed out waiting for ACK.
I do “tamper” with the chdr data before it goes into the noc_shell, and with the chdr data that comes out of the noc_shell.
Specifically, I only take 64 bits out of the 128 bits coming into the block itself(currently 4 SPC is used) and feed it into the noc_shell, which is set to work with a CHDR_W of 64.
I do something similar for the chdr output of the noc_shell, except I expand it from 64 to 128.
Could this have an effect on ACK? It seems all acknowledgement protocol is does using the ctrl_data, not the chdr_data, but maybe I am missing something.
Thanks,
Joe
Hi Joe,
This error message usually means that the host did a register read/write
request but never got a response from the USRP. This might happen, for
example, if a clock wasn't properly connected to the NoC shell. It could
also be some kind of network issue (swapped cables, firewall, improperly
configured IP addresses, etc.).
Thanks,
Wade
On Tue, Jun 20, 2023 at 2:10 PM jmaloyan@umass.edu wrote:
Hello,
I am currently trying to build an image with a 500 Mhz sampling rate with
a custom block. However, I get the following error.
[ERROR] [RFNOC::GRAPH] Caught exception while initializing graph:
RfnocError: OpTimeout: Control operation timed out waiting for ACK.
I do “tamper” with the chdr data before it goes into the noc_shell, and
with the chdr data that comes out of the noc_shell.
Specifically, I only take 64 bits out of the 128 bits coming into the
block itself(currently 4 SPC is used) and feed it into the noc_shell, which
is set to work with a CHDR_W of 64.
I do something similar for the chdr output of the noc_shell, except I
expand it from 64 to 128.
Could this have an effect on ACK? It seems all acknowledgement protocol is
does using the ctrl_data, not the chdr_data, but maybe I am missing
something.
Thanks,
Joe
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-leave@lists.ettus.com
It ended up being the case that the project was being built with wrong file, and the ACK wire was set exclusively to 0.
Hi! I am facing similar issue. Can you please be more specific on how did you manage to fix it? Thanks!
du | Error: failed receiving packet. RfnocError: OpTimeout: Control operation timed out waiting for ACK.
du | Error: failed receiving packet. RfnocError: OpTimeout: Control operation timed out waiting for ACK.
du | Error: failed receiving packet. RfnocError: OpTimeout: Control operation timed out waiting for ACK.
du | Error: failed receiving packet. RfnocError: OpTimeout: Control operation timed out waiting for ACK.
du | Error: failed receiving packet. RfnocError: OpTimeout: Control operation timed out waiting for ACK.
du | Error: failed receiving packet. RfnocError: OpTimeout: Control operation timed out waiting for ACK.
du | Error: failed receiving packet. RfnocError: OpTimeout: Control operation timed out waiting for ACK.
du | Error: failed receiving packet. RfnocError: OpTimeout: Control operation timed out waiting for ACK.
du | Error: failed receiving packet. RfnocError: OpTimeout: Control operation timed out waiting for ACK.
du | Error: failed receiving packet. RfnocError: OpTimeout: Control operation timed out waiting for ACK.
du | Error: failed receiving packet. RfnocError: OpTimeout: Control operation timed out waiting for ACK.