Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unrecoverable Code crash x310, Fpga exceptio while rx capture - uhd 3.15.0 - IOError: Block ctrl (CE_01_Port_40) no response packet - #321

Closed
ilayni opened this issue Jan 13, 2020 · 12 comments

Comments

@ilayni
Copy link

ilayni commented Jan 13, 2020

Issue Description

running
linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.15.0.HEAD-0-gaea0e2de
and doing rx capture with 4 channels with timed command i get the following
Exception EnvironmentError: IOError: Block ctrl (CE_01_Port_40) no response packet - AssertionError: bool(buff)
in uint64_t ctrl_iface_impl<_endianness>::wait_for_ack(bool, double) [with uhd::endianness_t _endianness = (uhd::endianness_t)0u; uint64_t = long unsigned int]
at /home/gig/uhd/host/lib/rfnoc/ctrl_iface.cpp:151

Setup Details

linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.15.0.HEAD-0-gaea0e2de
and doing rx capture with 4 channels 2 twinrx

Expected Behavior

capture with no isssue

Actual Behaviour

FPGA exception

Steps to reproduce the problem

recv with 4 channels with time commands

Additional Information

@Same-Writer
Copy link

Do you have any code that reproduces this behavior? Does it happen in v3.14.1.1?

@ilayni
Copy link
Author

ilayni commented Jan 15, 2020 via email

@ilayni
Copy link
Author

ilayni commented Jan 15, 2020

This happens if i create and destroy an rx_streamer
what is need in the case of changing rates in version 3.15.0

@ccera-astro
Copy link

http://www.ccera.ca/files/rx_multi_samples.cpp easily reproduces this issue -- this is a variant of the standard version that takes an --iters parameter. I've found that the number of iterations required isn't consistent. But what IS necessary is that the number of channels requested needs to be varying between streaming sessions. If the channel count remains fixed, it will run to completion every time.

@ilayni
Copy link
Author

ilayni commented Apr 21, 2020

Hi,
My channel number is always 4 and i still get this issue.

@atrnati
Copy link
Contributor

atrnati commented Sep 24, 2020

Are you able to try to reproduce this issue with UHD 4.0.0?

@michaelld
Copy link
Collaborator

I'm working with the customer via Ettus Support email. I'll test things out on UHD 4.0 when I get a chance soon. We're slowly working on getting UHD4 build for the customer. This issue certainly seems relevant to UHD 3.15. Let's leave this open until we get UHD4.0 tested.

@Anplus
Copy link

Anplus commented Sep 29, 2020

My UHD version is 3.15.0. I didn't have such a problem when I use two x310 to implement 4 Rx or 4 Tx. But when I simultaneously use Tx and Rx, the UHD report the following errors:

thread[thread-per-block[1]: <block gr uhd usrp sink (2)>]: EnvironmentError: IOError: Failed to sync DACs! EnvironmentError: IOError: 1/Radio_0 user_reg_read64() failed: EnvironmentError: IOError: [1/Radio_0] sr_read64() failed: EnvironmentError: IOError: Block ctrl (CE_01_Port_40) packet parse error - EnvironmentError: IOError: Expected SID: 03:40>00:06 Received SID: 02:40>00:06
thread[thread-per-block[2]: <block gr uhd usrp source (1)>]: EnvironmentError: IOError: Block ctrl (CE_01_Port_40) no response packet - AssertionError: bool(buff)
in uint64_t ctrl_iface_impl<_endianness>::wait_for_ack(bool, double) [with uhd::endianness_t _endianness = (uhd::endianness_t)0; uint64_t = long unsigned int]

@cclamb
Copy link

cclamb commented Dec 6, 2020

Guys has this issue been resolved?

@michaelld
Copy link
Collaborator

@cclamb not resolved to the best of my knowledge ... maybe the OP can re-test & report back anything related to UHD 3.15 .. or UHD 4.0 even better?

@cclamb
Copy link

cclamb commented Dec 9, 2020 via email

@mbr0wn
Copy link
Contributor

mbr0wn commented Mar 19, 2024

As this no longer appears on 4.x, and we are not fixing 3.15 anymore, I'm closing this.

@mbr0wn mbr0wn closed this as not planned Won't fix, can't repro, duplicate, stale Mar 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants