Paolo, Yes, it does sound like we are having slightly different issues here.
I am suppressing my output when data_ready from the AXI_Wrapper goes low. In fact, even if I drop data (rather than queue it up) while data_ready is low, I still get that 'D' message (even when making sure my sequence numbers remain sequential despite the dropped data samples). Thanks, Michael H. Rich Electronic Systems Laboratory Georgia Tech Research Institute® Phone: (404) 407-8358 E-mail: [email protected] -----Original Message----- From: Paolo Palana <[email protected]> Sent: Friday, April 16, 2021 10:03 AM To: [email protected] Subject: [USRP-users] Re: AXI Stream Issue Hi Michael, Probably mine problems and your are not exactly the same, but I think they are related in some way. Mine, for example, was due an error in the logic inside my block that caused a deadlock on the (RFNoC) bus. As far as I can understand the usrp word I think your problem can be quite similar. When you receive an overrun error on the host side, as also Rob said, that means that your block is producing samples at a rate too high for the host. When the data_ready from the axi wrapper, that should be an output from the axi wrapper itself and the should be an input to your logic, goes low is something like someone is telling you "please stop streaming for a while because I'm not ready to receive data". What do you do in your logic when the data_ready signal goes low? Hope this can help you a little Have good day Paolo _______________________________________________ USRP-users mailing list -- [email protected] To unsubscribe send an email to [email protected]
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ USRP-users mailing list -- [email protected] To unsubscribe send an email to [email protected]
