From 23b646bda313c230494011dbb54576e9f2748fa9 Mon Sep 17 00:00:00 2001 From: Mark Meserve Date: Tue, 24 Jul 2018 13:14:47 -0500 Subject: lmx2592: fix calibration start during tuning - This bug could cause LO to not lock properly after a set_frequency call --- host/lib/usrp/common/lmx2592.cpp | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/host/lib/usrp/common/lmx2592.cpp b/host/lib/usrp/common/lmx2592.cpp index 9a31f0ec7..ec467acc8 100644 --- a/host/lib/usrp/common/lmx2592.cpp +++ b/host/lib/usrp/common/lmx2592.cpp @@ -240,9 +240,11 @@ public: const auto actual_f_lo = actual_fcore_vco * vco_multiplier / output_divider; UHD_LOGGER_TRACE("LMX2592") << "Tuned to " << actual_f_lo; + + // Toggle fcal field to start calibration + _regs.fcal_enable = 0; commit(); - // Run Frequency Calibration _regs.fcal_enable = 1; commit(); -- cgit v1.2.3