On 11/16/2020 05:38 PM, Lamar Owen wrote:
On 11/16/20 5:26 PM, Marcus D. Leech via USRP-users wrote:
On 11/16/2020 03:32 PM, Lamar Owen via USRP-users wrote:
[TRACE] [DBSRX] DBSRX: trying ref_clock 4000000.000000 and m_divider 4
[TRACE] [DBSRX] DBSRX R:2
[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.
AssertionError: m and ref_clock/m >= 1e6 and ref_clock/m <= 2.5e6
in double dbsrx::set_lo_freq(double)
at
/home/conda/feedstock_root/build_artifacts/uhd_1602712704625/work/host/lib/usrp/dboard/db_dbsrx.cpp:306
If you look at the context of this assertion--it should never be
asserted. ref_clock is 4e6 and m is 4, so the test is satisfied,
and therefore the
assertion shouldn't fail. I wonder if this is a compiler issue, or
an issue with the UHD_ASSERT logic?
Yeah, I saw that; thanks for the pointer (to someone else's question)
about logging at trace level. So I've filed it as an issue in the UHD
github. Could be something similar to issue #304 at the UHD github.
What it does tell me is that 3.15 SHOULD support USRP1 with DBSRX,
just need to fix the issue.
I can confirm that this issue goes back at least as far as UHD 3.13 --
just tried it after digging my USRP1 and DBSRX cards out of storage.
_______________________________________________
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
