I am trying to connect, but I can do it only via Moxa converter (https://www.moxa.com/product/IMC-101.htm) and host doesn't see X310. I think it is because : The USRP-X Series only supports Gigabit and Ten Gigabit Ethernet and will not work with a 10/100 Mbps interface. Am I right? I was able to run NI Utilities, whish I found in USRP examples in LabVIEW. In the Windows 7 uhd_usrp_probe.exe works fine and gives all the information. Ubuntu and Windows share the same computer. -- Отправлено из Mail.Ru для Android понедельник, 02 апреля 2018г., 18:09 +03:00 от Marcus D. Leech via USRP-users usrp-users@lists.ettus.com :
>On 04/02/2018 03:18 AM, Антон > Заболотский via USRP-users wrote: >> >>Hi >> everyone, >> >>I have USRP >> 2955 and it >> works under >> Labview 2017 >> Windows 7. >>Now I need to >> convert it to >> X310. I can >> use only PCIe. >>But >> unfortunately >> I have the >> following >> errors: >> >> >>I used default >> image burned >> by National >> Instruments >> and I was >> trying to load >> HG image(by >> JTAG) but I >> have the same >> errors: >>$ uhd_usrp_probe --args "type=x300,resource=RIO0" >>[INFO] [UHD] linux; GNU C++ version 4.8.4; Boost_105400; UHD_3.11.0.0-release >>[INFO] [NIRIO] rpc_client stopping... >>[INFO] [NIRIO] rpc_client stopped. >>[ERROR] [UHD] Device discovery error: RuntimeError: x300_find_pcie: Error >>enumerating NI-RIO devices. >> Unknown error. (Error code -52012) >>Error: LookupError: KeyError: No devices found for -----> >>Device Address: >> type: x300 >> resource: RIO0 >> >>$ uhd_find_devices >>[INFO] [UHD] linux; GNU C++ version 4.8.4; Boost_105400; UHD_3.11.0.0-release >>[INFO] [NIRIO] rpc_client stopping... >>[INFO] [NIRIO] rpc_client stopped. >>No UHD Devices Found >> >>To check if there is some compatibility issue with my PC and the >>USRP RIO here is my info about PC: >>$ sudo /usr/local/bin/niusrprio_pcie status >>Modules Loaded: nikal nibds nistreamk NiRioSrv niusrpriok >>Server: niusrpriorpc >> >>$ lsmod | grep -i '^ni' >>niusrpriok 405504 0 >>NiRioSrv 897024 0 >>nistreamk 135168 2 niusrpriok,NiRioSrv >>nibds 57344 2 niusrpriok,NiRioSrv >>nikal 114688 4 niusrpriok,nibds,NiRioSrv,nistreamk >> >>$ lspci -k -nn -d 1093:c4c4 >>03:00.0 Signal processing controller [1180]: National Instruments PXIe/PCIe >>Device [1093:c4c4] >> Subsystem: National Instruments Device [1093:78f0] >> >>$ ps -A | grep niusrp >> 2376 pts/6 00:00:00 niusrpriorpc >> >>$ ss -ltpn | grep 5444 >>LISTEN 0 128 *:5444 *:* >> >>$ uname -a >>Linux finder 3.19.0-80-generic #88~14.04.1-Ubuntu SMP Fri Jan 13 14:54:07 >>UTC 2017 x86_64 x86_64 x86_64 GNU/Linux >> >>$ sudo ls /dev/ni/ >>nistreamk:0\nistreamk\0 >> >> >> >>I found the following in the mails below: >>_____________________________________________ >>>lspci -k -nn -d 1093:c4c4 >>05:00.0 Signal processing controller [1180]: National Instruments >>PXIe/PCIe Device [1093:c4c4] >> Subsystem: National Instruments Device [1093:76ca] >> Kernel driver in use: niusrpriok <<--- >><<--- THIS IS NOT IN MY OUTPUT >> >> >>If the device is properly detected by the driver then the output >>should look something like this: >>$ sudo ls /dev/ni/ >>NiRioSrv:fpga:00040000\nirio_transport\0 pci:0000:04:00.0\niflexrio_rio\2 >>nistreamk:0\nistreamk\ pci:0000:04:00.0\niflexrio_usrp\1 >>pci:0000:04:00.0\niflexrio_readwrite\3 pci:0000:04:00.0\niflexrio_usrprio\0 >><<--- THIS IS NOT IN MY OUTPUT >>_____________________________________________ >> >>Do you have any advices what can i try? >>Does it mean that NI-RIO driver can't detect my device? >> >> >> >>I found some >> similar >> topics, but I >> wasn't able to >> find a >> solution for >> my problem >> >>http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/2016-June/020801.html >> >>http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/2016-August/021381.html >> >>http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/2014-June/009977.html >> >>http://lists.ettus.com/pipermail/usrp-users_lists.ettus.com/2015-November/016927.html >> >> >> >> >>-- >>Thanks for >> help >>Anton >> Zabolotsky >> >Are you able to temporarily connect it via gigabit ethernet, and > then ping it at 192.168.10.2 ? > > > >_______________________________________________ >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