I'm still getting the same error with the USB 2.0 for the B200 on my tegra system.
Using lsusb I can see the B200 listed as: Bus 001 Device 031: ID 2500:0020 I can then find /dev/bus/usb/001/031 and verify that it has the correct permissions: crw-rw-rw- 1 root flirimaging 189, 30 Dec 28 18:04 031 Just to test things out, I've even changed the permissions, reloaded the udev rules, and noted that the permissions change back. So in spite of verifying the B200 permissions, I still get the same error listed in my original email. Does anyone have any other suggestions? -Mike On Fri, Dec 22, 2017 at 3:13 PM, Michael Don <miked...@gmail.com> wrote: > Marcus, > > Yes, "sudo udevadm control --reload-rules" is included in the "Setup Udev for > USB" instructions. I also tried replugging in the unit. I'll try debugging > some more and let you know if I come up with anything. > > Philip - thanks for letting me know about the acceleration, once I get things > working I may ask you more about it. > > -Mike > > > On Tue, Dec 19, 2017 at 7:58 PM, Philip Balister via USRP-users < > usrp-users@lists.ettus.com> wrote: > >> On 12/19/2017 06:44 PM, Marcus D. Leech via USRP-users wrote: >> > On 12/19/2017 05:09 PM, Michael Don via USRP-users wrote: >> >> >> >> I've build and installed UHD 3.10.1.1 on a Tegra TX2 (ARM64 >> >> platform). The USB 3.0 is working, but I'm getting errors with the >> >> USB 2.0 on a USRP B200. >> >> I know UHD works on several aarch64 platforms. I do carry a patch in >> meta-sdr that enables neon acceleration for the uhd type convertors. >> >> Philip >> >> >> >> >> uhd_find_devices works, but uhd_usrp_probe, and the uhd application >> >> examples give the error below. Note that I've tried running with >> >> sudo, and have followed the instructions "Setup Udev for USB" about >> >> the uhd-usrp.rules file. Any advice? >> >> >> >> Thanks, -Mike >> >> >> >> >> >> linux; GNU C++ version 5.4.0 20160609; Boost_105800; >> >> UHD_003.010.001.001-0-unknown >> >> >> >> -- Detected Device: B200 >> >> -- Operating over USB 2. >> >> -- Initialize CODEC control... >> >> >> >> UHD Error: >> >> An unexpected exception was caught in a task loop. >> >> The task loop will now exit, things may not work. >> >> EnvironmentError: IOError: usb rx8 transfer status: >> >> LIBUSB_TRANSFER_ERROR >> >> -- Detected bad USB state; resetting. >> >> >> >> UHD Error: >> >> USB open failed: insufficient permissions. >> >> See the application notes for your device. >> >> Error: AssertionError: libusb_open(_dev->get(), &_handle) == 0 >> >> in >> >> libusb_device_handle_impl::libusb_device_handle_impl(uhd:: >> transport::libusb::device::sptr) >> >> >> >> at >> >> /home/nvidia/Documents/USB3/uhd-release_003_010_001_001/host >> /lib/transport/libusb1_base.cpp:261 >> >> >> >> >> >> >> >> >> > >> > Did you: >> > >> > sudo udevadm control --reload-rules >> > >> > After installing the usrp rules file? >> > >> > Did you unplug/replug, after updating the rules? The rules are only >> > *triggered* when a USB device event happens, so if it's still plugged in >> > when you change >> > the rules, nothing will happen until you re-plug. >> > >> > >> > >> > >> > _______________________________________________ >> > 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
