This fixed the problem. Thanks to all.
Rob

On Wed, Aug 15, 2018 at 4:16 PM Rob Kossler <rkoss...@nd.edu> wrote:

> Great, thanks!
>
> On Wed, Aug 15, 2018 at 4:15 PM Michael West <michael.w...@ettus.com>
> wrote:
>
>> Rob,
>>
>> The images for 3.13.0.2 are in the process of being posted.  You can
>> either checkout v3.13.0.1 and use those images or continue to use the head
>> of UHD-3.13 and just recompile MPM on the device.
>>
>> Regards,
>> Michael
>>
>>
>> On Wed, Aug 15, 2018 at 1:11 PM, Robin Coxe via USRP-users <
>> usrp-users@lists.ettus.com> wrote:
>>
>>> You should be able to just recompile MPM to get yourself unstuck.
>>>
>>> On Wed, Aug 15, 2018 at 1:08 PM, Rob Kossler <rkoss...@nd.edu> wrote:
>>>
>>>> Oh.  Forgot to ask.  Do I need to re-flash the whole OS or can I just
>>>> recompile MPM on the device?
>>>> Rob
>>>>
>>>> On Wed, Aug 15, 2018 at 4:05 PM Rob Kossler <rkoss...@nd.edu> wrote:
>>>>
>>>>> Ok.  Thanks for the suggestions.  I just tried to download the latest
>>>>> 3.13 image and got an error message.  Any idea why?
>>>>>
>>>>> $ uhd_images_downloader -t n3xx_common
>>>>> [INFO] Images destination: /home/irisheyes9/uhd/3_13/share/uhd/images
>>>>> [ERROR] Downloader raised an unhandled exception: URL does not exist:
>>>>> http://files.ettus.com/binaries/cache//n3xx/meta-ettus-v3.13.0.2/n3xx_common_mender_default-v3.13.0.2.zip
>>>>> You can run this again with the '--verbose' flag to see more
>>>>> information
>>>>> If the problem persists, please email the output to: supp...@ettus.com
>>>>>
>>>>>
>>>>> On Wed, Aug 15, 2018 at 4:01 PM Robin Coxe <robin.c...@ettus.com>
>>>>> wrote:
>>>>>
>>>>>> Hi Rob.   Have you updated MPM on your N310 device?  This particular
>>>>>> issue was an MPM bug that should have been resolved in the UHD v. 
>>>>>> 3.13.0.1
>>>>>> filesystem, so updating the SD card should also resolve the issue.  If 
>>>>>> you
>>>>>> just update UHD on the host PC without updating MPM on the device, it 
>>>>>> will
>>>>>> not fix the problem.
>>>>>>
>>>>>> -Robin
>>>>>>
>>>>>>
>>>>>> On Wed, Aug 15, 2018 at 12:13 PM, Rob Kossler via USRP-users <
>>>>>> usrp-users@lists.ettus.com> wrote:
>>>>>>
>>>>>>> Thanks for the suggestion, but no luck.  Just tried the latest off
>>>>>>> of 3.13 branch.
>>>>>>>
>>>>>>> Given that I've been using this N310 for weeks on the original UHD
>>>>>>> version, I didn't expect that an update would cure it.
>>>>>>>
>>>>>>> It seems that maybe EEPROM has been corrupted for some reason.  I
>>>>>>> hope there is a reset option because my N310 is basically brick-ed now.
>>>>>>>
>>>>>>> Rob
>>>>>>>
>>>>>>> On Wed, Aug 15, 2018 at 2:55 PM Sayyed Dormiani Tabatabaei <
>>>>>>> sdorm...@eng.ucsd.edu> wrote:
>>>>>>>
>>>>>>>> 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
>>>>>>>
>>>>>>>
>>>>>>
>>>
>>> _______________________________________________
>>> 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

Reply via email to