Well I had this problem with UHD 3.12 but 3.13 fixed it. Do not know why it is back.
The github has 13.0.0.2 now and it seems some N310 related things are in that mini patch. Last commit was 20 hours ago so that may be it? ## 003.013.000.002 * N3xx: Fix issue where changing the clock/time source could result in clocks becoming unlocked * N3xx: Improve error messages for invalid clock/time settings * N3xx: Add support for Rev G mboard * MPM: Add function parameter to support holding AD9371 in reset * Docs: Add section on building fs/SD images for N3xx * Docs: Fix Doxygen warnings On Wed, Aug 15, 2018 at 11:46 AM, Rob Kossler via USRP-users < usrp-users@lists.ettus.com> wrote: > Anyone know the cause & solution to the following startup error? This > just started today after a cascade of problems which ultimately required me > to reflash the SD card. > > $ uhd_usrp_probe --args="addr=192.168.61.2" > [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; > UHD_3.13.0.1-0-g5b236772 > [INFO] [MPMD] Initializing 1 device(s) in parallel with args: > mgmt_addr=192.168.61.2,type=n3xx,product=n310,serial= > 315A34B,claimed=False,addr=192.168.61.2 > [INFO] [MPM.PeriphManager] init() called with device args > `mgmt_addr=192.168.61.2,product=n310'. > [ERROR] [RPC] RuntimeError: AD9371 product ID does not match expected ID! > Read: 1 Expected: 3 > [ERROR] [MPM.RPCServer] init() failed with error: RuntimeError: AD9371 > product ID does not match expected ID! Read: 1 Expected: 3 > Error: RuntimeError: Error during RPC call to `init'. Error message: > RuntimeError: AD9371 product ID does not match expected ID! Read: 1 > Expected: 3 > > > _______________________________________________ > 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
