Hi Jason, Could you try reverting gr-ettus back one commit to 4980cbef and let me know if that works?
Jonathon On Tue, Sep 10, 2019 at 5:23 AM Jason Matusiak via USRP-users < usrp-users@lists.ettus.com> wrote: > I have an RFNoC flowgraph and bitfile combo that used to work but is > erroring out now. I've been using the code successfully on the E320 and > E310 and decided to re-build for the X310 (and XG flowgraph). When I run > my flowgraph, I am see a lot of addition debug that I am not used to seeing > (which is fine) and then my block in particular seems to cause problems and > I get the error in the subject. I am guessing that since I just rebuilt > everything, some change needs to be made in my impl for my block due to > some UHD update, but I can't quite figure out anywhere where something > changes. The beginning of the output when I run my flowgraph is: > > [INFO] [UHD] linux; GNU C++ version 4.8.5 20150623 (Red Hat 4.8.5-36); > Boost_105300; UHD_3.14.1.1-0-g98c7c986 > [INFO] [X300] X300 initialization sequence... > [INFO] [X300] Maximum frame size: 8000 bytes. > [INFO] [X300] Radio 1x clock: 200 MHz > [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: > 0xF1F0D00000000000) > [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1317 MB/s) > [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1323 MB/s) > [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD100000000001) > [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD100000000001) > [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0000000000001) > [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0000000000001) > [INFO] [0/DDC_2] Initializing block control (NOC ID: 0xDDC0000000000001) > [INFO] [0/DDC_3] Initializing block control (NOC ID: 0xDDC0000000000001) > [INFO] [0/keepMinN_0] Initializing block control (NOC ID: > 0x229C30C919275220) > [INFO] [0/keepMinN_1] Initializing block control (NOC ID: > 0x229C30C919275220) > [WARNING] [RFNOC] Can't find a block controller for key SplitStream, using > default block controller! > [INFO] [0/SplitStream_0] Initializing block control (NOC ID: > 0x5757000000000000) > [WARNING] [RFNOC] Can't find a block controller for key SplitStream, using > default block controller! > [INFO] [0/SplitStream_1] Initializing block control (NOC ID: > 0x5757000000000000) > Finding block for: Radio_1 > Mapped external port 0 to 0 > Mapped port 0 to 0/Radio_1 > Mapped external port 1 to 1 > Mapped port 1 to 0/Radio_1 > TX args: > RX args: > 0/Radio_1 has 1 input ports > 0/Radio_1 has 2 output ports > getting block control for port 0 > Finding block for: DDC_0 > Mapped external port 0 to 0 > Mapped port 0 to 0/DDC_0 > TX args: > getting block control for port 0 > getting block control for port 0 > > > And the ehnd of that blob shows: > > getting block control for port 0 > getting block control for port 0 > thread[thread-per-block[2]: <block keepMinN (10)>]: RuntimeError: Cannot > create streamers: No block_id specified for channel 0. > > > And finally, if I let it sit there, the X310 must get into a wonky state > because I start to get: > > [ERROR] [X300] 192.168.80.2: x300 fw communication failure #1 > EnvironmentError: IOError: x300 fw poke32 - reply timed out > [ERROR] [X300] 192.168.80.2: x300 fw communication failure #2 > EnvironmentError: IOError: x300 fw poke32 - reply timed out > [ERROR] [X300] 192.168.80.2: x300 fw communication failure #1 > EnvironmentError: IOError: x300 fw poke32 - reply timed out > [ERROR] [X300] 192.168.80.2: x300 fw communication failure #1 > EnvironmentError: IOError: x300 fw poke32 - reply timed out > [ERROR] [X300] 192.168.80.2: x300 fw communication failure #2 > EnvironmentError: IOError: x300 fw poke32 - reply timed out > [ERROR] [X300] 192.168.80.2: x300 fw communication failure #3 > EnvironmentError: IOError: x300 fw poke32 - reply timed out > [ERROR] [UHD] An unexpected exception was caught in a task loop.The task > loop will now exit, things may not work.EnvironmentError: IOError: > 192.168.80.2: x300 fw communication failure #3 > EnvironmentError: IOError: x300 fw poke32 - reply timed out > > > > What am I missing here? > _______________________________________________ > USRP-users mailing list > USRP-users@lists.ettus.com > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com >
_______________________________________________ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
