Hi Rob, Martin meant that the product ID issue was fixed in 3.12.0.1 (current head of UHD-3.12) and 3.13.0.0. We are currently trying to reproduce the TX corruption issue using the head of UHD-3.13.
Regards, Michael On Wed, Aug 15, 2018 at 2:55 PM, Martin Braun via USRP-users < usrp-users@lists.ettus.com> wrote: > On 08/15/2018 11:46 AM, Rob Kossler via USRP-users 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 > > This particular issue was fixed in 3.12.0.1. > > -- M > > _______________________________________________ > 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
