Re: [USRP-users] USRP2r4 \w RFX2400 fails with UHD3.14
On 08/14/2018 02:14 PM, Marcus D. Leech via USRP-users wrote: On 08/10/2018 02:58 PM, Johannes Demel via USRP-users wrote: Hi Marcus, with UHD 3.10 we could run GR flowgraphs for hours. It recognizes the daughterboardand everything. I hope R can help. Cheers Johannes I was able to reproduce this locally (at least, the network parts of it--I don't have an RFX2400 to test with). Falling-back to 3.10.3 fixes it. It starts showing up in release_003_011_000_001 ___ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
Re: [USRP-users] USRP2r4 \w RFX2400 fails with UHD3.14
On 08/10/2018 02:58 PM, Johannes Demel via USRP-users wrote: Hi Marcus, with UHD 3.10 we could run GR flowgraphs for hours. It recognizes the daughterboardand everything. I hope R can help. Cheers Johannes I was able to reproduce this locally (at least, the network parts of it--I don't have an RFX2400 to test with). Falling-back to 3.10.3 fixes it. Von: USRP-users im Auftrag von Marcus D. Leech via USRP-users Gesendet: Freitag, 10. August 2018 18:28 An: usrp-users@lists.ettus.com Betreff: Re: [USRP-users] USRP2r4 \w RFX2400 fails with UHD3.14 On 08/10/2018 04:24 AM, Johannes Demel via USRP-users wrote: Hi Marcus, I put my answer on top. I hope that doesn't lead to confusion. Regarding (A): I hope it should work. How would I proceed to debug it? Does the same "unknown daughter-board" error show up with an earlier UHD (like the UHD 3.10 you mention below)?? Regarding (B): We have a laptop with a 1G NIC, a 1G switch and a USRP2 on the other end. This setup works with UHD3.10 (see my initial email on the topic). We could run GR flowgraphs etc. Those USRPs are pretty old but since they still work, we'd like to use them. Also, they do a pretty good job for what they are intended for. How would we proceed here? We may be dealing with a regression in the code-base here. Hopefully someone from R will chime in here. The USRP2 code hasn't changed in a very long time, but there have been improvements made to generic parts of the UHD codebase that could affect the USRP2. ___ 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 ___ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
Re: [USRP-users] USRP2r4 \w RFX2400 fails with UHD3.14
Hi Marcus, with UHD 3.10 we could run GR flowgraphs for hours. It recognizes the daughterboardand everything. I hope R can help. Cheers Johannes Von: USRP-users im Auftrag von Marcus D. Leech via USRP-users Gesendet: Freitag, 10. August 2018 18:28 An: usrp-users@lists.ettus.com Betreff: Re: [USRP-users] USRP2r4 \w RFX2400 fails with UHD3.14 On 08/10/2018 04:24 AM, Johannes Demel via USRP-users wrote: > Hi Marcus, > > I put my answer on top. I hope that doesn't lead to confusion. > > Regarding (A): I hope it should work. How would I proceed to debug it? Does the same "unknown daughter-board" error show up with an earlier UHD (like the UHD 3.10 you mention below)?? > > Regarding (B): We have a laptop with a 1G NIC, a 1G switch and a USRP2 > on the other end. > This setup works with UHD3.10 (see my initial email on the topic). We > could run GR flowgraphs etc. Those USRPs are pretty old but since they > still work, we'd like to use them. Also, they do a pretty good job for > what they are intended for. > How would we proceed here? > We may be dealing with a regression in the code-base here. Hopefully someone from R will chime in here. The USRP2 code hasn't changed in a very long time, but there have been improvements made to generic parts of the UHD codebase that could affect the USRP2. ___ 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
Re: [USRP-users] USRP2r4 \w RFX2400 fails with UHD3.14
Hi Marcus, I put my answer on top. I hope that doesn't lead to confusion. Regarding (A): I hope it should work. How would I proceed to debug it? Regarding (B): We have a laptop with a 1G NIC, a 1G switch and a USRP2 on the other end. This setup works with UHD3.10 (see my initial email on the topic). We could run GR flowgraphs etc. Those USRPs are pretty old but since they still work, we'd like to use them. Also, they do a pretty good job for what they are intended for. How would we proceed here? Cheers Johannes On 09.08.2018 20:30, Marcus D. Leech via USRP-users wrote: On 08/09/2018 06:03 AM, Johannes Demel via USRP-users wrote: Hi! Thanks for your reply. We didn't update because there was no Warning that suggested to do so. Anyways, now we updated the FPGA and Firmware. As a summary we had 'FW Version: 12.3' and 'FPGA Version: 10.0'. Now it is 'FW Version: 12.4' and 'FPGA Version: 10.1'. I hope these are the latest versions for both. Now we get some output. Though, the actual error persists. Here is a summary with only the errors. [ERROR] [DBMGR] The daughterboard manager encountered a recoverable error in init. Loading the "unknown" daughterboard implementations to continue. The daughterboard cannot operate until this error is resolved. LookupError: KeyError: key "0" not found in dict(i, N14adf4360_regs_t17prescaler_value_tE) | Device: USRP2 / N-Series Device [] | | Mboard: USRP2 r4 | | hardware: 1024 [] | | FW Version: 12.4 | | FPGA Version: 10.1 [] | | | RX Dboard: A | | | ID: RFX2400 (0x0027) | | | _ | | | / | | | | RX Frontend: 0 | | | | Name: Unknown (0x) - 0 | | | | Antennas: | | | | Sensors: | | | | Freq range: 0.000 to 0.000 MHz | | | | Gain Elements: None | | | | Bandwidth range: 0.0 to 0.0 step 0.0 Hz | | | | Connection Type: IQ | | | | Uses LO offset: No [ERROR] [UHD] Exception caught in safe-call. in virtual usrp2_fifo_ctrl_impl::~usrp2_fifo_ctrl_impl() at /usr/local/src/uhd/host/lib/usrp/usrp2/usrp2_fifo_ctrl.cpp:54 this->peek32(0); -> RuntimeError: fifo ctrl timed out looking for acks - What should we do next for debugging? Cheers Johannes This is the complete output: - [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.0.0-31-g98057752 [INFO] [USRP2] Opening a USRP2/N-Series device... [INFO] [USRP2] Current recv frame size: 1472 bytes [INFO] [USRP2] Current send frame size: 1472 bytes [ERROR] [DBMGR] The daughterboard manager encountered a recoverable error in init. Loading the "unknown" daughterboard implementations to continue. The daughterboard cannot operate until this error is resolved. LookupError: KeyError: key "0" not found in dict(i, N14adf4360_regs_t17prescaler_value_tE) _ / | Device: USRP2 / N-Series Device | _ | / | | Mboard: USRP2 r4 | | hardware: 1024 [] | | FW Version: 12.4 | | FPGA Version: 10.1 | | | | Time sources: none, external, _external_, mimo | | Clock sources: internal, external, mimo | | Sensors: mimo_locked, ref_locked | | _ | | / | | | RX DSP: 0 | | | | | | Freq range: -50.000 to 50.000 MHz | | _ | | / | | | RX DSP: 1 | | | | | | Freq range: -50.000 to 50.000 MHz | | _ | | / | | | RX Dboard: A | | | ID: RFX2400 (0x0027) | | | _ | | | / | | | | RX Frontend: 0 | | | | Name: Unknown (0x) - 0 | | | | Antennas: | | | | Sensors: | | | | Freq range: 0.000 to 0.000 MHz | | | | Gain Elements: None | | | | Bandwidth range: 0.0 to 0.0 step 0.0 Hz | | | | Connection Type: IQ | | | | Uses LO offset: No | | | _ | | | / | | | | RX Codec: A | | | | Name: ltc2284 | | | | Gain Elements: None | | _ | | / | | | TX DSP: 0 | | | | | | Freq range: -200.000 to 200.000 MHz | | _ | | / | | | TX Dboard: A | | | ID: RFX2400 (0x002b) | | | _ | | | / | | | | TX Frontend: 0 | | | | Name: Unknown (0x) - 0 | | | | Antennas: | | | | Sensors: | | | | Freq range: 0.000 to 0.000 MHz | | | |
Re: [USRP-users] USRP2r4 \w RFX2400 fails with UHD3.14
On 08/09/2018 06:03 AM, Johannes Demel via USRP-users wrote: Hi! Thanks for your reply. We didn't update because there was no Warning that suggested to do so. Anyways, now we updated the FPGA and Firmware. As a summary we had 'FW Version: 12.3' and 'FPGA Version: 10.0'. Now it is 'FW Version: 12.4' and 'FPGA Version: 10.1'. I hope these are the latest versions for both. Now we get some output. Though, the actual error persists. Here is a summary with only the errors. [ERROR] [DBMGR] The daughterboard manager encountered a recoverable error in init. Loading the "unknown" daughterboard implementations to continue. The daughterboard cannot operate until this error is resolved. LookupError: KeyError: key "0" not found in dict(i, N14adf4360_regs_t17prescaler_value_tE) | Device: USRP2 / N-Series Device [] | | Mboard: USRP2 r4 | | hardware: 1024 [] | | FW Version: 12.4 | | FPGA Version: 10.1 [] | | | RX Dboard: A | | | ID: RFX2400 (0x0027) | | | _ | | |/ | | | | RX Frontend: 0 | | | | Name: Unknown (0x) - 0 | | | | Antennas: | | | | Sensors: | | | | Freq range: 0.000 to 0.000 MHz | | | | Gain Elements: None | | | | Bandwidth range: 0.0 to 0.0 step 0.0 Hz | | | | Connection Type: IQ | | | | Uses LO offset: No [ERROR] [UHD] Exception caught in safe-call. in virtual usrp2_fifo_ctrl_impl::~usrp2_fifo_ctrl_impl() at /usr/local/src/uhd/host/lib/usrp/usrp2/usrp2_fifo_ctrl.cpp:54 this->peek32(0); -> RuntimeError: fifo ctrl timed out looking for acks - What should we do next for debugging? Cheers Johannes This is the complete output: - [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.0.0-31-g98057752 [INFO] [USRP2] Opening a USRP2/N-Series device... [INFO] [USRP2] Current recv frame size: 1472 bytes [INFO] [USRP2] Current send frame size: 1472 bytes [ERROR] [DBMGR] The daughterboard manager encountered a recoverable error in init. Loading the "unknown" daughterboard implementations to continue. The daughterboard cannot operate until this error is resolved. LookupError: KeyError: key "0" not found in dict(i, N14adf4360_regs_t17prescaler_value_tE) _ / | Device: USRP2 / N-Series Device | _ |/ | | Mboard: USRP2 r4 | | hardware: 1024 [] | | FW Version: 12.4 | | FPGA Version: 10.1 | | | | Time sources: none, external, _external_, mimo | | Clock sources: internal, external, mimo | | Sensors: mimo_locked, ref_locked | | _ | |/ | | | RX DSP: 0 | | | | | | Freq range: -50.000 to 50.000 MHz | | _ | |/ | | | RX DSP: 1 | | | | | | Freq range: -50.000 to 50.000 MHz | | _ | |/ | | | RX Dboard: A | | | ID: RFX2400 (0x0027) | | | _ | | |/ | | | | RX Frontend: 0 | | | | Name: Unknown (0x) - 0 | | | | Antennas: | | | | Sensors: | | | | Freq range: 0.000 to 0.000 MHz | | | | Gain Elements: None | | | | Bandwidth range: 0.0 to 0.0 step 0.0 Hz | | | | Connection Type: IQ | | | | Uses LO offset: No | | | _ | | |/ | | | | RX Codec: A | | | | Name: ltc2284 | | | | Gain Elements: None | | _ | |/ | | | TX DSP: 0 | | | | | | Freq range: -200.000 to 200.000 MHz | | _ | |/ | | | TX Dboard: A | | | ID: RFX2400 (0x002b) | | | _ | | |/ | | | | TX Frontend: 0 | | | | Name: Unknown (0x) - 0 | | | | Antennas: | | | | Sensors: | | | | Freq range: 0.000 to 0.000 MHz | | | | Gain Elements: None | | | | Bandwidth range: 0.0 to 0.0 step 0.0 Hz | | | | Connection Type: IQ | | | | Uses LO offset: No | | | _ | | |/ | | | | TX Codec: A | | | | Name: ad9777 | | | | Gain Elements: None [ERROR] [UHD] Exception caught in safe-call. in virtual usrp2_fifo_ctrl_impl::~usrp2_fifo_ctrl_impl() at /usr/local/src/uhd/host/lib/usrp/usrp2/usrp2_fifo_ctrl.cpp:54 this->peek32(0); -> RuntimeError: fifo ctrl timed out looking for acks
Re: [USRP-users] USRP2r4 \w RFX2400 fails with UHD3.14
-- On 06.08.2018 14:53, Brophy, William wrote: Have you updated the firmware on the radio(s) after updating UHD? Will -Original Message- From: USRP-users On Behalf Of Johannes Demel via USRP-users Sent: Friday, August 3, 2018 10:02 AM To: usrp-users@lists.ettus.com Subject: [USRP-users] USRP2r4 \w RFX2400 fails with UHD3.14 Hi all, we just got new X310s and wanted to use them with the latest UHD version. They work. That's great. But we have some old USRP2s as well. And we want to use them with the same driver version. We ran 'uhd_usrp_probe' for all of them. The output is below. Essentially, there seems to be a problem with the daughterboard manager. We had the same experience with UHD3.12 --- [ERROR] [DBMGR] The daughterboard manager encountered a recoverable error in init. Loading the "unknown" daughterboard implementations to continue. The daughterboard cannot operate until this error is resolved. LookupError: KeyError: key "0" not found in dict(i, N14adf4360_regs_t17prescaler_value_tE) --- Also, with the latest UHD3.14 we have this new problem - [ERROR] [UHD] Exception caught in safe-call. in virtual usrp2_fifo_ctrl_impl::~usrp2_fifo_ctrl_impl() at /usr/local/src/uhd/host/lib/usrp/usrp2/usrp2_fifo_ctrl.cpp:54 this->peek32(0); -> RuntimeError: fifo ctrl timed out looking for acks - Let me know if you need any more info. So far we couldn't find a solution to our problems here. I hope someone can point us in the correct direction to fix these errors. Cheers Johannes Error for USRP2 with UHD3.14 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.0.0-31-g98057752 [INFO] [USRP2] Opening a USRP2/N-Series device... [INFO] [USRP2] Current recv frame size: 1472 bytes [INFO] [USRP2] Current send frame size: 1472 bytes [ERROR] [DBMGR] The daughterboard manager encountered a recoverable error in init. Loading the "unknown" daughterboard implementations to continue. The daughterboard cannot operate until this error is resolved. LookupError: KeyError: key "0" not found in dict(i, N14adf4360_regs_t17prescaler_value_tE) EnvironmentError: OSError: error in pthread_setschedparam [ERROR] [UHD] Exception caught in safe-call. in virtual usrp2_fifo_ctrl_impl::~usrp2_fifo_ctrl_impl() at /usr/local/src/uhd/host/lib/usrp/usrp2/usrp2_fifo_ctrl.cpp:54 this->peek32(0); -> RuntimeError: fifo ctrl timed out looking for acks - As a reference. Here is the output for other setups that work. Working USRP2 with UHD3.10 -- linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_003.010.001.HEAD-0-gc705922a -- Opening a USRP2/N-Series device... -- Current recv frame size: 1472 bytes -- Current send frame size: 1472 bytes EnvironmentError: OSError: error in pthread_setschedparam _ / | Device: USRP2 / N-Series Device | _ |/ | | Mboard: USRP2 r4 | | hardware: 1024 [] | | FW Version: 12.3 | | FPGA Version: 10.0 | | | | Time sources: none, external, _external_, mimo | | Clock sources: internal, external, mimo | | Sensors: mimo_locked, ref_locked [] | | _ | |/ | | | RX Dboard: A | | | ID: RFX2400 (0x0027) | | | _ | | |/ | | | | RX Frontend: 0 | | | | Name: RFX2400 RX | | | | Antennas: TX/RX, RX2, CAL | | | | Sensors: lo_locked | | | | Freq range: 2300.000 to 2900.000 MHz | | | | Gain range PGA0: 0.0 to 70.0 step 0.0 dB | | | | Bandwidth range: 4000.0 to 4000.0 step 0.0 Hz | | | | Connection Type: QI | | | | Uses LO offset: No | | | _ | | |/ | | | | RX Codec: A | | | | Name: ltc2284 | | | | Gain Elements: None [] Working X310 -- [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.0.0-31-g98057752 [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] No GPSDO found [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1306 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] In
[USRP-users] USRP2r4 \w RFX2400 fails with UHD3.14
Hi all, we just got new X310s and wanted to use them with the latest UHD version. They work. That's great. But we have some old USRP2s as well. And we want to use them with the same driver version. We ran 'uhd_usrp_probe' for all of them. The output is below. Essentially, there seems to be a problem with the daughterboard manager. We had the same experience with UHD3.12 --- [ERROR] [DBMGR] The daughterboard manager encountered a recoverable error in init. Loading the "unknown" daughterboard implementations to continue. The daughterboard cannot operate until this error is resolved. LookupError: KeyError: key "0" not found in dict(i, N14adf4360_regs_t17prescaler_value_tE) --- Also, with the latest UHD3.14 we have this new problem - [ERROR] [UHD] Exception caught in safe-call. in virtual usrp2_fifo_ctrl_impl::~usrp2_fifo_ctrl_impl() at /usr/local/src/uhd/host/lib/usrp/usrp2/usrp2_fifo_ctrl.cpp:54 this->peek32(0); -> RuntimeError: fifo ctrl timed out looking for acks - Let me know if you need any more info. So far we couldn't find a solution to our problems here. I hope someone can point us in the correct direction to fix these errors. Cheers Johannes Error for USRP2 with UHD3.14 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.0.0-31-g98057752 [INFO] [USRP2] Opening a USRP2/N-Series device... [INFO] [USRP2] Current recv frame size: 1472 bytes [INFO] [USRP2] Current send frame size: 1472 bytes [ERROR] [DBMGR] The daughterboard manager encountered a recoverable error in init. Loading the "unknown" daughterboard implementations to continue. The daughterboard cannot operate until this error is resolved. LookupError: KeyError: key "0" not found in dict(i, N14adf4360_regs_t17prescaler_value_tE) EnvironmentError: OSError: error in pthread_setschedparam [ERROR] [UHD] Exception caught in safe-call. in virtual usrp2_fifo_ctrl_impl::~usrp2_fifo_ctrl_impl() at /usr/local/src/uhd/host/lib/usrp/usrp2/usrp2_fifo_ctrl.cpp:54 this->peek32(0); -> RuntimeError: fifo ctrl timed out looking for acks - As a reference. Here is the output for other setups that work. Working USRP2 with UHD3.10 -- linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_003.010.001.HEAD-0-gc705922a -- Opening a USRP2/N-Series device... -- Current recv frame size: 1472 bytes -- Current send frame size: 1472 bytes EnvironmentError: OSError: error in pthread_setschedparam _ / | Device: USRP2 / N-Series Device | _ |/ | | Mboard: USRP2 r4 | | hardware: 1024 [] | | FW Version: 12.3 | | FPGA Version: 10.0 | | | | Time sources: none, external, _external_, mimo | | Clock sources: internal, external, mimo | | Sensors: mimo_locked, ref_locked [] | | _ | |/ | | | RX Dboard: A | | | ID: RFX2400 (0x0027) | | | _ | | |/ | | | | RX Frontend: 0 | | | | Name: RFX2400 RX | | | | Antennas: TX/RX, RX2, CAL | | | | Sensors: lo_locked | | | | Freq range: 2300.000 to 2900.000 MHz | | | | Gain range PGA0: 0.0 to 70.0 step 0.0 dB | | | | Bandwidth range: 4000.0 to 4000.0 step 0.0 Hz | | | | Connection Type: QI | | | | Uses LO offset: No | | | _ | | |/ | | | | RX Codec: A | | | | Name: ltc2284 | | | | Gain Elements: None [] Working X310 -- [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.0.0-31-g98057752 [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] No GPSDO found [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1306 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) _ / | Device: X-Series Device | _ |/ | | Mboard: X310 | | revision: 11
