Sorry to bring it up again, but this is really becoming an issue for us, in 
that we can't seem to use our N320 radios reliably with this TDC measurement 
error issue. When the TDC error occurs, our program or even uhd_usrp_probe 
immediately errors out and exits. If anyone has seen this or has any thoughts 
on why this might be happening or how to fix it, that would be greatly 
appreciated.

Thanks,
Jim

________________________________
From: Jim Palladino <j...@gardettoengineering.com>
Sent: Monday, May 2, 2022 12:59 PM
To: USRP-users@lists.ettus.com <usrp-users@lists.ettus.com>
Subject: [USRP-users] N320 TDC measurement errors

Hello,

Ever since updating to UHD 4.1.0.5 (including updating the filesystem and FPGA 
image on our six N320 USRPs), we occasionally get TDC measurement errors when 
trying to interact with the radio via UHD. It isn't easily reproducible, but it 
does happen on different radios maybe once a day or so. I've seen it when using 
either external time and clock sources or internal (doesn't seem to matter 
which).

Here is an example of the output of a uhd_usrp_probe when this occurs.
----------------------
[INFO] [UHD] linux; GNU C++ version 7.5.0; Boost_106501; 
UHD_4.1.0.HEAD-0-g6bd0be9c
[DEBUG] [MPMD] Discovering MPM devices on port 49600
[DEBUG] [MPMD] Discovering MPM devices on port 49600
[DEBUG] [MPMD] Discovering MPM devices on port 49600
[DEBUG] [MPMD] Discovering MPM devices on port 49600
[INFO] [MPMD] Initializing 1 device(s) in parallel with args: 
mgmt_addr=192.168.40.2,type=n3xx,product=n320,serial=31EDED4,fpga=XG,claimed=False,addr=192.168.40.2
[DEBUG] [MPMD] Claiming mboard 0
[DEBUG] [MPMD] Device args: 
`mgmt_addr=192.168.40.2,type=n3xx,product=n320,serial=31EDED4,fpga=XG,claimed=False,addr=192.168.40.2'.
 RPC address: 192.168.40.2
[DEBUG] [MPMD] MPM reports device info: 
addr=192.168.30.2,claimed=True,connection=remote,dboard_0_pid=338,dboard_0_serial=31EBB6F,dboard_1_pid=338,dboard_1_serial=31EBB94,description=N300-Series
 
Device,eeprom_version=3,fpga=XG,fpga_version=8.0,fpga_version_hash=6bd0be9.clean,fs_version=20211215135436,mender_artifact=v4.1.0.5_n3xx,mpm_sw_version=4.1.0.5-g6bd0be9c,mpm_version=4.0,name=ni-n3xx-31EDED4,pid=16962,product=n320,rev=10,rpc_connection=remote,second_addr=192.168.40.2,serial=31EDED4,type=n3xx
[DEBUG] [MPMD] Found 8 motherboard sensors.
[DEBUG] [MPMD] Initializing mboard 0
[INFO] [MPM.PeriphManager] init() called with device args 
`fpga=XG,mgmt_addr=192.168.40.2,product=n320,clock_source=internal,time_source=internal'.
[INFO] [MPM.Rhodium-0] init() called with args 
`fpga=XG,mgmt_addr=192.168.40.2,product=n320,clock_source=internal,time_source=internal'
[INFO] [MPM.Rhodium-1] init() called with args 
`fpga=XG,mgmt_addr=192.168.40.2,product=n320,clock_source=internal,time_source=internal'
[INFO] [MPM.Rhodium-0.init.LMK04828] LMK initialized and locked!
[ERROR] [MPM.Sync-0] TDC measurements show a wide range of values! Check your 
clock rates for incompatibilities.
[INFO] [MPM.Rhodium-1.init.LMK04828] LMK initialized and locked!
[ERROR] [RPC] TDC measurement out of expected range!
[INFO] [MPM.Rhodium-1.DAC37J82] DAC PLL Locked!
[INFO] [MPM.Rhodium-1.AD9695] ADC PLL Locked!
[INFO] [MPM.Rhodium-1.init] JESD204B Link Initialization & Training Complete
[ERROR] [MPM.RPCServer] init() failed with error: TDC measurement out of 
expected range!
Error: RuntimeError: Error during RPC call to `init'. Error message: TDC 
measurement out of expected range!
----------------------

If I run uhd_usrp_probe again immediately, it always seems to work fine. I 
don't think this is specific to any of the 3 valid master clock rates, but I've 
seen this happen after a fresh reboot of an N320 with a uhd_usrp_probe -- so it 
should have been set to default parameters. I also feel like it happens after a 
radio hasn't been in use for a while, but I'm not sure if that is always the 
case.

Does anyone have any idea what might cause this?

Thanks,
Jim

_______________________________________________
USRP-users mailing list -- usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-le...@lists.ettus.com

Reply via email to