We have a python script that worked before I pulled down the latest UHD. A uhd_usrp_probe works fine, but when we run our command in our script using: usrp.get_usrp_info().vals()[0] We get an error of: LookupError: Path not found in tree: /mboards/0/xbar/Radio_0/eeprom partway through the Ettus debug that is scrolling across the screen. When I do a list of the tree, sure enough, I don't see that entry in there anymore. Looking at the commits in UHD master, there is this one in there (which happened after all my other machines were installed and just before this particular machine was installed): multi_usrp: Update get_usrp_?x_info() In MPM devices, daughterboard EEPROMs now use eeprom_map_t instead of dboard_eeprom_t. The eeprom also is under rfnoc path. This change will allow ?x_info() to reach that rfnoc path and pull information from the new eeprom_map_t.
And I think that is what is causing my problem. I believe that something is probing the device (an X300 in this case), and getting tripped up by the change to the tree. For now I commented out the call on our end, but I ran out of time to trace down where exactly UHD is getting tripped up. But I am thinking it has something to do with the device_addrs_t device::find function on line 93 of device.cpp in uhd/host/lib.
_______________________________________________ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
