usrp-users@lists.ettus.com

Discussion and technical support related to USRP, UHD, RFNoC

View all threads

X310 RIO Session Initialization Failure (Error code -63150)

HD
Heinz, Dominik
Wed, Jan 29, 2025 9:32 AM

Okay,

So I am having trouble to interface with the X310, despite having set the correct IP addresses for both interfaces..?

gnb@xgoss-host:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp77s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 9c:6b:00:56:a3:a5 brd ff:ff:ff:ff:ff:ff
3: enp1s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether f8:f2:1e:9b:f1:60 brd ff:ff:ff:ff:ff:ff
inet 192.168.30.2/24 brd 192.168.30.255 scope global noprefixroute enp1s0f0
valid_lft forever preferred_lft forever
inet6 fe80::a1a4:f18c:ce2c:bbf1/64 scope link noprefixroute
valid_lft forever preferred_lft forever
4: enp1s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether f8:f2:1e:9b:f1:61 brd ff:ff:ff:ff:ff:ff
inet 192.168.40.2/24 brd 192.168.40.255 scope global noprefixroute enp1s0f1
valid_lft forever preferred_lft forever
inet6 fe80::f167:b030:ddfa:a249/64 scope link noprefixroute
valid_lft forever preferred_lft forever
5: ogstun: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1400 qdisc fq_codel state UP group default qlen 500
link/none
inet 10.45.0.1/16 brd 10.45.255.255 scope global ogstun
valid_lft forever preferred_lft forever
inet6 2001:db8:cafe::1/48 scope global
valid_lft forever preferred_lft forever
inet6 fe80::d4:8229:f90e:9ef8/64 scope link stable-privacy
valid_lft forever preferred_lft forever
6: wlp76s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether f4:46:37:30:ee:5e brd ff:ff:ff:ff:ff:ff
inet 192.168.1.146/24 brd 192.168.1.255 scope global dynamic noprefixroute wlp76s0
valid_lft 6788sec preferred_lft 6788sec
inet6 fe80::ee0a:9d:d428:6cb4/64 scope link noprefixroute
valid_lft forever preferred_lft forever
7: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 52:54:00:6d:72:20 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
valid_lft forever preferred_lft forever
8: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:87:6d:5c:d9 brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
valid_lft forever preferred_lft forever
9: br-add5841a3206: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:9c:fa:66:b5 brd ff:ff:ff:ff:ff:ff
inet 192.168.11.1/24 brd 192.168.11.255 scope global br-add5841a3206
valid_lft forever preferred_lft forever
gnb@xgoss-host:~$ uhd_find_devices
[INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; UHD_4.7.0.0-0ubuntu1~jammy1
No UHD Devices Found
gnb@xgoss-host:~$ uhd_usrp_probe
[INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; UHD_4.7.0.0-0ubuntu1~jammy1
Error: LookupError: KeyError: No devices found for ----->
Empty Device Address

I got the SDR working before but for some reason I can't get this working reliably.

I assigned the IP addresses to the interfaces with the Network GUI in Ubuntu.

But I can't find the device neither via uhd_find_devices, not with uhd_usrp_probe.

The X310 is flashed with the XG image for dual SFP+.

Do you mind guiding me step by step how to configure the IPs for the interfaces correctly and interface with the SDR? I don't see what I am missing?


From: Marcus D. Leech patchvonbraun@gmail.com
Sent: Monday, January 27, 2025 12:32:14 PM
To: Heinz, Dominik; Martin Braun
Cc: usrp-users@lists.ettus.com
Subject: [EXTERN] Re: [EXTERN] [USRP-users] Re: [EXTERN] Re: [EXTERN] Re: Re: [EXTERN] Re: X310 RIO Session Initialization Failure (Error code -63150)

On 27/01/2025 05:29, Heinz, Dominik wrote:

Okay, seems like I had to manually set the IP addresses for the interfaces. Now I can interact perfectly with the device.

Tho, I don't know how to configure it to use both Links simultaneously, like you suggested (to do 2x200 Msps streaming).

Any advice on that would be appreciated :)

Use the second_addr argument:

https://files.ettus.com/manual/page_usrp_x3x0.html#x3x0_usage

So, assuming the XG image, your device arguments would include:

addr=192.168.30.2,second_addr=192.168.40.2


From: Heinz, Dominik dominik.heinz@h-da.demailto:dominik.heinz@h-da.de
Sent: Monday, January 27, 2025 10:32:27 AM
To: Martin Braun
Cc: Marcus D. Leech; usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com
Subject: [EXTERN] [USRP-users] Re: [EXTERN] Re: [EXTERN] Re: Re: [EXTERN] Re: X310 RIO Session Initialization Failure (Error code -63150)

When I run the image loader without the IP address parameter it seems to be flashing the correctly.

uhd_image_loader --args="type=x300"

However, I don't see how I can configure the IP address to be able to interact via the 10GbE links (?)


From: Heinz, Dominik dominik.heinz@h-da.demailto:dominik.heinz@h-da.de
Sent: Monday, January 27, 2025 10:18:41 AM
To: Martin Braun
Cc: Marcus D. Leech; usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com
Subject: [EXTERN] [USRP-users] Re: [EXTERN] Re: Re: [EXTERN] Re: X310 RIO Session Initialization Failure (Error code -63150)

Hello Martin,
Hello Marcus,

The X310 does not show up as a RIO device, but rather like this:

4a:00.0 Signal processing controller: National Instruments PXIe/PCIe Device (rev ff) (prog-if ff)
!!! Unknown header type 7f
Kernel driver in use: niusrpriok
Kernel modules: niusrpriok

This seems already problematic (?)

The nisrpriorpc server seems to be running fine:

gnb@xgoss-host:~$ sudo systemctl status niusrpriorpc
● niusrpriorpc.service - LSB: National Instruments USRP RIO Service
Loaded: loaded (/etc/init.d/niusrpriorpc; generated)
Active: active (running) since Mon 2025-01-27 09:37:21 CET; 23min ago
Docs: man:systemd-sysv-generator(8)
Tasks: 4 (limit: 153252)
Memory: 98.6M
CPU: 13.872s
CGroup: /system.slice/niusrpriorpc.service
└─1631 /usr/sbin/niusrpriorpc --daemon

Jan 27 09:37:21 xgoss-host systemd[1]: Starting LSB: National Instruments USRP RIO Service...
Jan 27 09:37:21 xgoss-host systemd[1]: Started LSB: National Instruments USRP RIO Service.

You also mentioned that the X310 needs to be powered on before the host system.
I have of course done this - since to my knowledge hot plugging is not possible in the case of PCIe.

Running uhd_usrp_probe as root doesn't change anything.

I am okay with trying out the 10GbE instead, but I am not able to interact with the device that way.
I can't seem to specify an IP or load a firmware image this way. I tried:

gnb@xgoss-host:~$ uhd_image_loader --args="type=x300,addr=192.168.10.2,fpga=HG"
[INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; UHD_4.7.0.0-0ubuntu1~jammy1
No applicable UHD devices found

Any idea how to proceed? Can't seem to get the device running via PCIe, and via 10GbE I can't interact with the device either.
I will provide the details in the Github issue shortly.


From: Martin Braun martin.braun@ettus.commailto:martin.braun@ettus.com
Sent: Friday, January 24, 2025 12:19:00 PM
To: Heinz, Dominik
Cc: Marcus D. Leech; usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com
Subject: [EXTERN] Re: [USRP-users] Re: [EXTERN] Re: X310 RIO Session Initialization Failure (Error code -63150)

Dominik,

can you provide as much info as you can here: https://github.com/EttusResearch/uhd/issues/818?

Like Marcus said, the PCIe interface is not used a lot (except by LabView users), so if you can use 10 GbE instead I recommend doing that (that also allows you to do 2x200 Msps streaming, if you have two ports).

--M

On Wed, Jan 22, 2025 at 2:58 PM Heinz, Dominik <dominik.heinz@h-da.demailto:dominik.heinz@h-da.de> wrote:

I followed the steps in the guide you linked, - however, I still have the issue.

The uhd drivers are installed, and the niuspriorpc service is running. However, I still the the RIO session initialization failure.

Anything else I could try? I still don't understand what is the cause for this.


From: Marcus D. Leech <patchvonbraun@gmail.commailto:patchvonbraun@gmail.com>
Sent: Tuesday, January 21, 2025 8:32:39 PM
To: usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com
Subject: [EXTERN] [USRP-users] Re: X310 RIO Session Initialization Failure (Error code -63150)

On 21/01/2025 09:26, Heinz, Dominik wrote:

I'm experiencing an initialization issue with my Ettus X310 USRP device.

My setup consists of an Ettus X310 connected through a PCIe Card using a Molex cable to my Linux machine.

I'm running Ubuntu with kernel version 6.8.0-51-generic and have installed all the necessary UHD packages on the system.

The X310 is properly detected when running uhd_find_devices, but attempting to probe the device with uhd_usrp_probe results in a RIO session initialization error.
I attached the error output below.
What is causing this RIO session initialization failure and how can it be resolved?

gnb@xgoss-host:~/srsRAN_Project/build4ac5300/apps/gnb$ uhd_find_devices
[INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; UHD_4.7.0.0-0ubuntu1~jammy1

-- UHD Device 0

Device Address:
serial:
fpga: HG
name:
product: X310
resource: RIO0
type: x300

gnb@xgoss-host:~/srsRAN_Project/build4ac5300/apps/gnb$ uhd_usrp_probe
[INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; UHD_4.7.0.0-0ubuntu1~jammy1
[INFO] [X300] X300 initialization sequence...
[INFO] [X300] Connecting to niusrpriorpc at localhost:5444...
[INFO] [X300] Using LVBITX bitfile /usr/share/uhd/images/usrp_x310_fpga_HG.lvbitx
Error: RuntimeError: x300_impl: Could not initialize RIO session. Unknown error. (Error code -63150)


USRP-users mailing list -- usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-leave@lists.ettus.commailto:usrp-users-leave@lists.ettus.com

The procedures for making this work are here:

https://files.ettus.com/manual/page_usrp_x3x0.html#x3x0_hw_pcie


USRP-users mailing list -- usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-leave@lists.ettus.commailto:usrp-users-leave@lists.ettus.com

Okay, So I am having trouble to interface with the X310, despite having set the correct IP addresses for both interfaces..? gnb@xgoss-host:~$ ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp77s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 9c:6b:00:56:a3:a5 brd ff:ff:ff:ff:ff:ff 3: enp1s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether f8:f2:1e:9b:f1:60 brd ff:ff:ff:ff:ff:ff inet 192.168.30.2/24 brd 192.168.30.255 scope global noprefixroute enp1s0f0 valid_lft forever preferred_lft forever inet6 fe80::a1a4:f18c:ce2c:bbf1/64 scope link noprefixroute valid_lft forever preferred_lft forever 4: enp1s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether f8:f2:1e:9b:f1:61 brd ff:ff:ff:ff:ff:ff inet 192.168.40.2/24 brd 192.168.40.255 scope global noprefixroute enp1s0f1 valid_lft forever preferred_lft forever inet6 fe80::f167:b030:ddfa:a249/64 scope link noprefixroute valid_lft forever preferred_lft forever 5: ogstun: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1400 qdisc fq_codel state UP group default qlen 500 link/none inet 10.45.0.1/16 brd 10.45.255.255 scope global ogstun valid_lft forever preferred_lft forever inet6 2001:db8:cafe::1/48 scope global valid_lft forever preferred_lft forever inet6 fe80::d4:8229:f90e:9ef8/64 scope link stable-privacy valid_lft forever preferred_lft forever 6: wlp76s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether f4:46:37:30:ee:5e brd ff:ff:ff:ff:ff:ff inet 192.168.1.146/24 brd 192.168.1.255 scope global dynamic noprefixroute wlp76s0 valid_lft 6788sec preferred_lft 6788sec inet6 fe80::ee0a:9d:d428:6cb4/64 scope link noprefixroute valid_lft forever preferred_lft forever 7: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 52:54:00:6d:72:20 brd ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 valid_lft forever preferred_lft forever 8: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default link/ether 02:42:87:6d:5c:d9 brd ff:ff:ff:ff:ff:ff inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0 valid_lft forever preferred_lft forever 9: br-add5841a3206: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default link/ether 02:42:9c:fa:66:b5 brd ff:ff:ff:ff:ff:ff inet 192.168.11.1/24 brd 192.168.11.255 scope global br-add5841a3206 valid_lft forever preferred_lft forever gnb@xgoss-host:~$ uhd_find_devices [INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; UHD_4.7.0.0-0ubuntu1~jammy1 No UHD Devices Found gnb@xgoss-host:~$ uhd_usrp_probe [INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; UHD_4.7.0.0-0ubuntu1~jammy1 Error: LookupError: KeyError: No devices found for -----> Empty Device Address I got the SDR working before but for some reason I can't get this working reliably. I assigned the IP addresses to the interfaces with the Network GUI in Ubuntu. But I can't find the device neither via uhd_find_devices, not with uhd_usrp_probe. The X310 is flashed with the XG image for dual SFP+. Do you mind guiding me step by step how to configure the IPs for the interfaces correctly and interface with the SDR? I don't see what I am missing? ________________________________ From: Marcus D. Leech <patchvonbraun@gmail.com> Sent: Monday, January 27, 2025 12:32:14 PM To: Heinz, Dominik; Martin Braun Cc: usrp-users@lists.ettus.com Subject: [EXTERN] Re: [EXTERN] [USRP-users] Re: [EXTERN] Re: [EXTERN] Re: Re: [EXTERN] Re: X310 RIO Session Initialization Failure (Error code -63150) On 27/01/2025 05:29, Heinz, Dominik wrote: Okay, seems like I had to manually set the IP addresses for the interfaces. Now I can interact perfectly with the device. Tho, I don't know how to configure it to use both Links simultaneously, like you suggested (to do 2x200 Msps streaming). Any advice on that would be appreciated :) Use the second_addr argument: https://files.ettus.com/manual/page_usrp_x3x0.html#x3x0_usage So, assuming the XG image, your device arguments would include: addr=192.168.30.2,second_addr=192.168.40.2 ________________________________ From: Heinz, Dominik <dominik.heinz@h-da.de><mailto:dominik.heinz@h-da.de> Sent: Monday, January 27, 2025 10:32:27 AM To: Martin Braun Cc: Marcus D. Leech; usrp-users@lists.ettus.com<mailto:usrp-users@lists.ettus.com> Subject: [EXTERN] [USRP-users] Re: [EXTERN] Re: [EXTERN] Re: Re: [EXTERN] Re: X310 RIO Session Initialization Failure (Error code -63150) When I run the image loader without the IP address parameter it seems to be flashing the correctly. uhd_image_loader --args="type=x300" However, I don't see how I can configure the IP address to be able to interact via the 10GbE links (?) ________________________________ From: Heinz, Dominik <dominik.heinz@h-da.de><mailto:dominik.heinz@h-da.de> Sent: Monday, January 27, 2025 10:18:41 AM To: Martin Braun Cc: Marcus D. Leech; usrp-users@lists.ettus.com<mailto:usrp-users@lists.ettus.com> Subject: [EXTERN] [USRP-users] Re: [EXTERN] Re: Re: [EXTERN] Re: X310 RIO Session Initialization Failure (Error code -63150) Hello Martin, Hello Marcus, The X310 does not show up as a RIO device, but rather like this: 4a:00.0 Signal processing controller: National Instruments PXIe/PCIe Device (rev ff) (prog-if ff) !!! Unknown header type 7f Kernel driver in use: niusrpriok Kernel modules: niusrpriok This seems already problematic (?) The nisrpriorpc server seems to be running fine: gnb@xgoss-host:~$ sudo systemctl status niusrpriorpc ● niusrpriorpc.service - LSB: National Instruments USRP RIO Service Loaded: loaded (/etc/init.d/niusrpriorpc; generated) Active: active (running) since Mon 2025-01-27 09:37:21 CET; 23min ago Docs: man:systemd-sysv-generator(8) Tasks: 4 (limit: 153252) Memory: 98.6M CPU: 13.872s CGroup: /system.slice/niusrpriorpc.service └─1631 /usr/sbin/niusrpriorpc --daemon Jan 27 09:37:21 xgoss-host systemd[1]: Starting LSB: National Instruments USRP RIO Service... Jan 27 09:37:21 xgoss-host systemd[1]: Started LSB: National Instruments USRP RIO Service. You also mentioned that the X310 needs to be powered on before the host system. I have of course done this - since to my knowledge hot plugging is not possible in the case of PCIe. Running uhd_usrp_probe as root doesn't change anything. I am okay with trying out the 10GbE instead, but I am not able to interact with the device that way. I can't seem to specify an IP or load a firmware image this way. I tried: gnb@xgoss-host:~$ uhd_image_loader --args="type=x300,addr=192.168.10.2,fpga=HG" [INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; UHD_4.7.0.0-0ubuntu1~jammy1 No applicable UHD devices found Any idea how to proceed? Can't seem to get the device running via PCIe, and via 10GbE I can't interact with the device either. I will provide the details in the Github issue shortly. ________________________________ From: Martin Braun <martin.braun@ettus.com><mailto:martin.braun@ettus.com> Sent: Friday, January 24, 2025 12:19:00 PM To: Heinz, Dominik Cc: Marcus D. Leech; usrp-users@lists.ettus.com<mailto:usrp-users@lists.ettus.com> Subject: [EXTERN] Re: [USRP-users] Re: [EXTERN] Re: X310 RIO Session Initialization Failure (Error code -63150) Dominik, can you provide as much info as you can here: https://github.com/EttusResearch/uhd/issues/818? Like Marcus said, the PCIe interface is not used a lot (except by LabView users), so if you can use 10 GbE instead I recommend doing that (that also allows you to do 2x200 Msps streaming, if you have two ports). --M On Wed, Jan 22, 2025 at 2:58 PM Heinz, Dominik <dominik.heinz@h-da.de<mailto:dominik.heinz@h-da.de>> wrote: I followed the steps in the guide you linked, - however, I still have the issue. The uhd drivers are installed, and the niuspriorpc service is running. However, I still the the RIO session initialization failure. Anything else I could try? I still don't understand what is the cause for this. ________________________________ From: Marcus D. Leech <patchvonbraun@gmail.com<mailto:patchvonbraun@gmail.com>> Sent: Tuesday, January 21, 2025 8:32:39 PM To: usrp-users@lists.ettus.com<mailto:usrp-users@lists.ettus.com> Subject: [EXTERN] [USRP-users] Re: X310 RIO Session Initialization Failure (Error code -63150) On 21/01/2025 09:26, Heinz, Dominik wrote: I'm experiencing an initialization issue with my Ettus X310 USRP device. My setup consists of an Ettus X310 connected through a PCIe Card using a Molex cable to my Linux machine. I'm running Ubuntu with kernel version 6.8.0-51-generic and have installed all the necessary UHD packages on the system. The X310 is properly detected when running uhd_find_devices, but attempting to probe the device with uhd_usrp_probe results in a RIO session initialization error. I attached the error output below. What is causing this RIO session initialization failure and how can it be resolved? gnb@xgoss-host:~/srsRAN_Project/build4ac5300/apps/gnb$ uhd_find_devices [INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; UHD_4.7.0.0-0ubuntu1~jammy1 -------------------------------------------------- -- UHD Device 0 -------------------------------------------------- Device Address: serial: fpga: HG name: product: X310 resource: RIO0 type: x300 gnb@xgoss-host:~/srsRAN_Project/build4ac5300/apps/gnb$ uhd_usrp_probe [INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; UHD_4.7.0.0-0ubuntu1~jammy1 [INFO] [X300] X300 initialization sequence... [INFO] [X300] Connecting to niusrpriorpc at localhost:5444... [INFO] [X300] Using LVBITX bitfile /usr/share/uhd/images/usrp_x310_fpga_HG.lvbitx Error: RuntimeError: x300_impl: Could not initialize RIO session. Unknown error. (Error code -63150) _______________________________________________ USRP-users mailing list -- usrp-users@lists.ettus.com<mailto:usrp-users@lists.ettus.com> To unsubscribe send an email to usrp-users-leave@lists.ettus.com<mailto:usrp-users-leave@lists.ettus.com> The procedures for making this work are here: https://files.ettus.com/manual/page_usrp_x3x0.html#x3x0_hw_pcie _______________________________________________ USRP-users mailing list -- usrp-users@lists.ettus.com<mailto:usrp-users@lists.ettus.com> To unsubscribe send an email to usrp-users-leave@lists.ettus.com<mailto:usrp-users-leave@lists.ettus.com>
MD
Marcus D. Leech
Wed, Jan 29, 2025 2:21 PM

On 29/01/2025 04:32, Heinz, Dominik wrote:

Okay,

So I am having trouble to interface with the X310, despite having set
the correct IP addresses for both interfaces..?

gnb@xgoss-host:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp77s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel
state UP group default qlen 1000
    link/ether 9c:6b:00:56:a3:a5 brd ff:ff:ff:ff:ff:ff
3: enp1s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state
UP group default qlen 1000
    link/ether f8:f2:1e:9b:f1:60 brd ff:ff:ff:ff:ff:ff
    inet 192.168.30.2/24 brd 192.168.30.255 scope global noprefixroute
enp1s0f0
       valid_lft forever preferred_lft forever
    inet6 fe80::a1a4:f18c:ce2c:bbf1/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
4: enp1s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state
UP group default qlen 1000
    link/ether f8:f2:1e:9b:f1:61 brd ff:ff:ff:ff:ff:ff
    inet 192.168.40.2/24 brd 192.168.40.255 scope global noprefixroute
enp1s0f1
       valid_lft forever preferred_lft forever
    inet6 fe80::f167:b030:ddfa:a249/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
5: ogstun: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1400 qdisc
fq_codel state UP group default qlen 500
    link/none
    inet 10.45.0.1/16 brd 10.45.255.255 scope global ogstun
       valid_lft forever preferred_lft forever
    inet6 2001:db8:cafe::1/48 scope global
       valid_lft forever preferred_lft forever
    inet6 fe80::d4:8229:f90e:9ef8/64 scope link stable-privacy
       valid_lft forever preferred_lft forever
6: wlp76s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
state UP group default qlen 1000
    link/ether f4:46:37:30:ee:5e brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.146/24 brd 192.168.1.255 scope global dynamic
noprefixroute wlp76s0
       valid_lft 6788sec preferred_lft 6788sec
    inet6 fe80::ee0a:9d:d428:6cb4/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
7: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
state DOWN group default qlen 1000
    link/ether 52:54:00:6d:72:20 brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever
8: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
state DOWN group default
    link/ether 02:42:87:6d:5c:d9 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever
9: br-add5841a3206: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
noqueue state DOWN group default
    link/ether 02:42:9c:fa:66:b5 brd ff:ff:ff:ff:ff:ff
    inet 192.168.11.1/24 brd 192.168.11.255 scope global br-add5841a3206
       valid_lft forever preferred_lft forever
gnb@xgoss-host:~$ uhd_find_devices
[INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400;
UHD_4.7.0.0-0ubuntu1~jammy1
No UHD Devices Found
gnb@xgoss-host:~$ uhd_usrp_probe
[INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400;
UHD_4.7.0.0-0ubuntu1~jammy1
Error: LookupError: KeyError: No devices found for ----->
Empty Device Address

I got the SDR working before but for some reason I can't get this
working reliably.

I assigned the IP addresses to the interfaces with the Network GUI in
Ubuntu.

But I can't find the device neither via uhd_find_devices, not with
uhd_usrp_probe.

The X310 is flashed with the XG image for dual SFP+.

Do you mind guiding me step by step how to configure the IPs for the
interfaces correctly and interface with the SDR? I don't see what I am
missing?

You've given your HOST PC the same addresses as the X310.   Choose some
other address.  Like   .1 or .3


From: Marcus D. Leech patchvonbraun@gmail.com
Sent: Monday, January 27, 2025 12:32:14 PM
To: Heinz, Dominik; Martin Braun
Cc: usrp-users@lists.ettus.com
Subject: [EXTERN] Re: [EXTERN] [USRP-users] Re: [EXTERN] Re:
[EXTERN] Re: Re: [EXTERN] Re: X310 RIO Session Initialization Failure
(Error code -63150)
On 27/01/2025 05:29, Heinz, Dominik wrote:

Okay, seems like I had to manually set the IP addresses for the
interfaces. Now I can interact perfectly with the device.

Tho, I don't know how to configure it to use both Links
simultaneously, like you suggested (to do 2x200 Msps streaming).

Any advice on that would be appreciated :)

Use the second_addr argument:

https://files.ettus.com/manual/page_usrp_x3x0.html#x3x0_usage

So, assuming the XG image, your device arguments would include:

addr=192.168.30.2,second_addr=192.168.40.2


From: Heinz, Dominik dominik.heinz@h-da.de
Sent: Monday, January 27, 2025 10:32:27 AM
To: Martin Braun
Cc: Marcus D. Leech; usrp-users@lists.ettus.com
Subject: [EXTERN] [USRP-users] Re: [EXTERN] Re: [EXTERN] Re: Re:
[EXTERN] Re: X310 RIO Session Initialization Failure (Error code -63150)

When I run the image loader without the IP address parameter it seems
to be flashing the correctly.

uhd_image_loader --args="type=x300"

However, I don't see how I can configure the IP address to be able to
interact via the 10GbE links (?)


From: Heinz, Dominik dominik.heinz@h-da.de
Sent: Monday, January 27, 2025 10:18:41 AM
To: Martin Braun
Cc: Marcus D. Leech; usrp-users@lists.ettus.com
Subject: [EXTERN] [USRP-users] Re: [EXTERN] Re: Re: [EXTERN] Re:
X310 RIO Session Initialization Failure (Error code -63150)
Hello Martin,
Hello Marcus,

The X310 does not show up as a RIO device, but rather like this:

4a:00.0 Signal processing controller: National Instruments PXIe/PCIe
Device (rev ff) (prog-if ff)
    !!! Unknown header type 7f
    Kernel driver in use: niusrpriok
    Kernel modules: niusrpriok

This seems already problematic (?)

The nisrpriorpc server seems to be running fine:

gnb@xgoss-host:~$ sudo systemctl status niusrpriorpc
● niusrpriorpc.service - LSB: National Instruments USRP RIO Service
     Loaded: loaded (/etc/init.d/niusrpriorpc; generated)
     Active: active (running) since Mon 2025-01-27 09:37:21 CET;
23min ago
       Docs: man:systemd-sysv-generator(8)
      Tasks: 4 (limit: 153252)
     Memory: 98.6M
        CPU: 13.872s
     CGroup: /system.slice/niusrpriorpc.service
             └─1631 /usr/sbin/niusrpriorpc --daemon

Jan 27 09:37:21 xgoss-host systemd[1]: Starting LSB: National
Instruments USRP RIO Service...
Jan 27 09:37:21 xgoss-host systemd[1]: Started LSB: National
Instruments USRP RIO Service.

You also mentioned that the X310 needs to be powered on before the
host system.
I have of course done this - since to my knowledge hot plugging is
not possible in the case of PCIe.

Running uhd_usrp_probe as root doesn't change anything.

I am okay with trying out the 10GbE instead, but I am not able to
interact with the device that way.
I can't seem to specify an IP or load a firmware image this way. I tried:

gnb@xgoss-host:~$ uhd_image_loader
--args="type=x300,addr=192.168.10.2,fpga=HG"
[INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400;
UHD_4.7.0.0-0ubuntu1~jammy1
No applicable UHD devices found

Any idea how to proceed? Can't seem to get the device running via
PCIe, and via 10GbE I can't interact with the device either.
I will provide the details in the Github issue shortly.


From: Martin Braun martin.braun@ettus.com
Sent: Friday, January 24, 2025 12:19:00 PM
To: Heinz, Dominik
Cc: Marcus D. Leech; usrp-users@lists.ettus.com
Subject: [EXTERN] Re: [USRP-users] Re: [EXTERN] Re: X310 RIO
Session Initialization Failure (Error code -63150)
Dominik,

can you provide as much info as you can here:
https://github.com/EttusResearch/uhd/issues/818?

Like Marcus said, the PCIe interface is not used a lot (except by
LabView users), so if you can use 10 GbE instead I recommend doing
that (that also allows you to do 2x200 Msps streaming, if you have
two ports).

--M

On Wed, Jan 22, 2025 at 2:58 PM Heinz, Dominik
dominik.heinz@h-da.de wrote:

 I followed the steps in the guide you linked, - however, I still
 have the issue.

 The uhd drivers are installed, and the niuspriorpc service is
 running. However, I still the the RIO session initialization failure.


 Anything else I could try? I still don't understand what is the
 cause for this.

 ------------------------------------------------------------------------
 *From:* Marcus D. Leech <patchvonbraun@gmail.com>
 *Sent:* Tuesday, January 21, 2025 8:32:39 PM
 *To:* usrp-users@lists.ettus.com
 *Subject:* [EXTERN] [USRP-users] Re: X310 RIO Session
 Initialization Failure (Error code -63150)
 On 21/01/2025 09:26, Heinz, Dominik wrote:
 I'm experiencing an initialization issue with my Ettus X310 USRP
 device.

 My setup consists of an Ettus X310 connected through a PCIe Card
 using a Molex cable to my Linux machine.

 I'm running Ubuntu with kernel version 6.8.0-51-generic and have
 installed all the necessary UHD packages on the system.


 The X310 is properly detected when running |uhd_find_devices|,
 but attempting to probe the device with |uhd_usrp_probe| results
 in a RIO session initialization error.
 I attached the error output below.
 What is causing this RIO session initialization failure and how
 can it be resolved?

 gnb@xgoss-host:~/srsRAN_Project/build4ac5300/apps/gnb$
 uhd_find_devices
 [INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400;
 UHD_4.7.0.0-0ubuntu1~jammy1
 --------------------------------------------------
 -- UHD Device 0
 --------------------------------------------------
 Device Address:
     serial:
     fpga: HG
     name:
     product: X310
     resource: RIO0
     type: x300

 gnb@xgoss-host:~/srsRAN_Project/build4ac5300/apps/gnb$
 uhd_usrp_probe
 [INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400;
 UHD_4.7.0.0-0ubuntu1~jammy1
 [INFO] [X300] X300 initialization sequence...
 [INFO] [X300] Connecting to niusrpriorpc at localhost:5444...
 [INFO] [X300] Using LVBITX bitfile
 /usr/share/uhd/images/usrp_x310_fpga_HG.lvbitx
 Error: RuntimeError: x300_impl: Could not initialize RIO
 session. Unknown error. (Error code -63150)



 _______________________________________________
 USRP-users mailing list --usrp-users@lists.ettus.com
 To unsubscribe send an email tousrp-users-leave@lists.ettus.com
 The procedures for making this work are here:

 https://files.ettus.com/manual/page_usrp_x3x0.html#x3x0_hw_pcie


 _______________________________________________
 USRP-users mailing list -- usrp-users@lists.ettus.com
 To unsubscribe send an email to usrp-users-leave@lists.ettus.com
On 29/01/2025 04:32, Heinz, Dominik wrote: > > Okay, > > So I am having trouble to interface with the X310, despite having set > the correct IP addresses for both interfaces..? > > > gnb@xgoss-host:~$ ip a > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN > group default qlen 1000 >     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 >     inet 127.0.0.1/8 scope host lo >        valid_lft forever preferred_lft forever >     inet6 ::1/128 scope host >        valid_lft forever preferred_lft forever > 2: enp77s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel > state UP group default qlen 1000 >     link/ether 9c:6b:00:56:a3:a5 brd ff:ff:ff:ff:ff:ff > 3: enp1s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state > UP group default qlen 1000 >     link/ether f8:f2:1e:9b:f1:60 brd ff:ff:ff:ff:ff:ff >     inet 192.168.30.2/24 brd 192.168.30.255 scope global noprefixroute > enp1s0f0 >        valid_lft forever preferred_lft forever >     inet6 fe80::a1a4:f18c:ce2c:bbf1/64 scope link noprefixroute >        valid_lft forever preferred_lft forever > 4: enp1s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state > UP group default qlen 1000 >     link/ether f8:f2:1e:9b:f1:61 brd ff:ff:ff:ff:ff:ff >     inet 192.168.40.2/24 brd 192.168.40.255 scope global noprefixroute > enp1s0f1 >        valid_lft forever preferred_lft forever >     inet6 fe80::f167:b030:ddfa:a249/64 scope link noprefixroute >        valid_lft forever preferred_lft forever > 5: ogstun: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1400 qdisc > fq_codel state UP group default qlen 500 >     link/none >     inet 10.45.0.1/16 brd 10.45.255.255 scope global ogstun >        valid_lft forever preferred_lft forever >     inet6 2001:db8:cafe::1/48 scope global >        valid_lft forever preferred_lft forever >     inet6 fe80::d4:8229:f90e:9ef8/64 scope link stable-privacy >        valid_lft forever preferred_lft forever > 6: wlp76s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue > state UP group default qlen 1000 >     link/ether f4:46:37:30:ee:5e brd ff:ff:ff:ff:ff:ff >     inet 192.168.1.146/24 brd 192.168.1.255 scope global dynamic > noprefixroute wlp76s0 >        valid_lft 6788sec preferred_lft 6788sec >     inet6 fe80::ee0a:9d:d428:6cb4/64 scope link noprefixroute >        valid_lft forever preferred_lft forever > 7: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue > state DOWN group default qlen 1000 >     link/ether 52:54:00:6d:72:20 brd ff:ff:ff:ff:ff:ff >     inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 >        valid_lft forever preferred_lft forever > 8: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue > state DOWN group default >     link/ether 02:42:87:6d:5c:d9 brd ff:ff:ff:ff:ff:ff >     inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0 >        valid_lft forever preferred_lft forever > 9: br-add5841a3206: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc > noqueue state DOWN group default >     link/ether 02:42:9c:fa:66:b5 brd ff:ff:ff:ff:ff:ff >     inet 192.168.11.1/24 brd 192.168.11.255 scope global br-add5841a3206 >        valid_lft forever preferred_lft forever > gnb@xgoss-host:~$ uhd_find_devices > [INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; > UHD_4.7.0.0-0ubuntu1~jammy1 > No UHD Devices Found > gnb@xgoss-host:~$ uhd_usrp_probe > [INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; > UHD_4.7.0.0-0ubuntu1~jammy1 > Error: LookupError: KeyError: No devices found for -----> > Empty Device Address > > > I got the SDR working before but for some reason I can't get this > working reliably. > > I assigned the IP addresses to the interfaces with the Network GUI in > Ubuntu. > > But I can't find the device neither via uhd_find_devices, not with > uhd_usrp_probe. > > > The X310 is flashed with the XG image for dual SFP+. > > > Do you mind guiding me step by step how to configure the IPs for the > interfaces correctly and interface with the SDR? I don't see what I am > missing? > You've given your HOST PC the same addresses as the X310.   Choose some other address.  Like   .1 or .3 > ------------------------------------------------------------------------ > *From:* Marcus D. Leech <patchvonbraun@gmail.com> > *Sent:* Monday, January 27, 2025 12:32:14 PM > *To:* Heinz, Dominik; Martin Braun > *Cc:* usrp-users@lists.ettus.com > *Subject:* [EXTERN] Re: [EXTERN] [USRP-users] Re: [EXTERN] Re: > [EXTERN] Re: Re: [EXTERN] Re: X310 RIO Session Initialization Failure > (Error code -63150) > On 27/01/2025 05:29, Heinz, Dominik wrote: >> >> Okay, seems like I had to manually set the IP addresses for the >> interfaces. Now I can interact perfectly with the device. >> >> Tho, I don't know how to configure it to use both Links >> simultaneously, like you suggested (to do 2x200 Msps streaming). >> >> >> Any advice on that would be appreciated :) >> > Use the second_addr argument: > > https://files.ettus.com/manual/page_usrp_x3x0.html#x3x0_usage > > So, assuming the XG image, your device arguments would include: > > addr=192.168.30.2,second_addr=192.168.40.2 > > >> ------------------------------------------------------------------------ >> *From:* Heinz, Dominik <dominik.heinz@h-da.de> >> *Sent:* Monday, January 27, 2025 10:32:27 AM >> *To:* Martin Braun >> *Cc:* Marcus D. Leech; usrp-users@lists.ettus.com >> *Subject:* [EXTERN] [USRP-users] Re: [EXTERN] Re: [EXTERN] Re: Re: >> [EXTERN] Re: X310 RIO Session Initialization Failure (Error code -63150) >> >> When I run the image loader without the IP address parameter it seems >> to be flashing the correctly. >> >> >> uhd_image_loader --args="type=x300" >> >> >> However, I don't see how I can configure the IP address to be able to >> interact via the 10GbE links (?) >> >> ------------------------------------------------------------------------ >> *From:* Heinz, Dominik <dominik.heinz@h-da.de> >> *Sent:* Monday, January 27, 2025 10:18:41 AM >> *To:* Martin Braun >> *Cc:* Marcus D. Leech; usrp-users@lists.ettus.com >> *Subject:* [EXTERN] [USRP-users] Re: [EXTERN] Re: Re: [EXTERN] Re: >> X310 RIO Session Initialization Failure (Error code -63150) >> Hello Martin, >> Hello Marcus, >> >> The X310 does not show up as a RIO device, but rather like this: >> >> 4a:00.0 Signal processing controller: National Instruments PXIe/PCIe >> Device (rev ff) (prog-if ff) >>     !!! Unknown header type 7f >>     Kernel driver in use: niusrpriok >>     Kernel modules: niusrpriok >> >> This seems already problematic (?) >> >> The nisrpriorpc server seems to be running fine: >> >> gnb@xgoss-host:~$ sudo systemctl status niusrpriorpc >> ● niusrpriorpc.service - LSB: National Instruments USRP RIO Service >>      Loaded: loaded (/etc/init.d/niusrpriorpc; generated) >>      Active: active (running) since Mon 2025-01-27 09:37:21 CET; >> 23min ago >>        Docs: man:systemd-sysv-generator(8) >>       Tasks: 4 (limit: 153252) >>      Memory: 98.6M >>         CPU: 13.872s >>      CGroup: /system.slice/niusrpriorpc.service >>              └─1631 /usr/sbin/niusrpriorpc --daemon >> >> Jan 27 09:37:21 xgoss-host systemd[1]: Starting LSB: National >> Instruments USRP RIO Service... >> Jan 27 09:37:21 xgoss-host systemd[1]: Started LSB: National >> Instruments USRP RIO Service. >> >> You also mentioned that the X310 needs to be powered on before the >> host system. >> I have of course done this - since to my knowledge hot plugging is >> not possible in the case of PCIe. >> >> Running uhd_usrp_probe as root doesn't change anything. >> >> I am okay with trying out the 10GbE instead, but I am not able to >> interact with the device that way. >> I can't seem to specify an IP or load a firmware image this way. I tried: >> >> gnb@xgoss-host:~$ uhd_image_loader >> --args="type=x300,addr=192.168.10.2,fpga=HG" >> [INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; >> UHD_4.7.0.0-0ubuntu1~jammy1 >> No applicable UHD devices found >> >> Any idea how to proceed? Can't seem to get the device running via >> PCIe, and via 10GbE I can't interact with the device either. >> I will provide the details in the Github issue shortly. >> >> >> ------------------------------------------------------------------------ >> *From:* Martin Braun <martin.braun@ettus.com> >> *Sent:* Friday, January 24, 2025 12:19:00 PM >> *To:* Heinz, Dominik >> *Cc:* Marcus D. Leech; usrp-users@lists.ettus.com >> *Subject:* [EXTERN] Re: [USRP-users] Re: [EXTERN] Re: X310 RIO >> Session Initialization Failure (Error code -63150) >> Dominik, >> >> can you provide as much info as you can here: >> https://github.com/EttusResearch/uhd/issues/818? >> >> Like Marcus said, the PCIe interface is not used a lot (except by >> LabView users), so if you can use 10 GbE instead I recommend doing >> that (that also allows you to do 2x200 Msps streaming, if you have >> two ports). >> >> --M >> >> On Wed, Jan 22, 2025 at 2:58 PM Heinz, Dominik >> <dominik.heinz@h-da.de> wrote: >> >> I followed the steps in the guide you linked, - however, I still >> have the issue. >> >> The uhd drivers are installed, and the niuspriorpc service is >> running. However, I still the the RIO session initialization failure. >> >> >> Anything else I could try? I still don't understand what is the >> cause for this. >> >> ------------------------------------------------------------------------ >> *From:* Marcus D. Leech <patchvonbraun@gmail.com> >> *Sent:* Tuesday, January 21, 2025 8:32:39 PM >> *To:* usrp-users@lists.ettus.com >> *Subject:* [EXTERN] [USRP-users] Re: X310 RIO Session >> Initialization Failure (Error code -63150) >> On 21/01/2025 09:26, Heinz, Dominik wrote: >>> >>> I'm experiencing an initialization issue with my Ettus X310 USRP >>> device. >>> >>> My setup consists of an Ettus X310 connected through a PCIe Card >>> using a Molex cable to my Linux machine. >>> >>> I'm running Ubuntu with kernel version 6.8.0-51-generic and have >>> installed all the necessary UHD packages on the system. >>> >>> >>> The X310 is properly detected when running |uhd_find_devices|, >>> but attempting to probe the device with |uhd_usrp_probe| results >>> in a RIO session initialization error. >>> I attached the error output below. >>> What is causing this RIO session initialization failure and how >>> can it be resolved? >>> >>> gnb@xgoss-host:~/srsRAN_Project/build4ac5300/apps/gnb$ >>> uhd_find_devices >>> [INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; >>> UHD_4.7.0.0-0ubuntu1~jammy1 >>> -------------------------------------------------- >>> -- UHD Device 0 >>> -------------------------------------------------- >>> Device Address: >>>     serial: >>>     fpga: HG >>>     name: >>>     product: X310 >>>     resource: RIO0 >>>     type: x300 >>> >>> gnb@xgoss-host:~/srsRAN_Project/build4ac5300/apps/gnb$ >>> uhd_usrp_probe >>> [INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; >>> UHD_4.7.0.0-0ubuntu1~jammy1 >>> [INFO] [X300] X300 initialization sequence... >>> [INFO] [X300] Connecting to niusrpriorpc at localhost:5444... >>> [INFO] [X300] Using LVBITX bitfile >>> /usr/share/uhd/images/usrp_x310_fpga_HG.lvbitx >>> Error: RuntimeError: x300_impl: Could not initialize RIO >>> session. Unknown error. (Error code -63150) >>> >>> >>> >>> _______________________________________________ >>> USRP-users mailing list --usrp-users@lists.ettus.com >>> To unsubscribe send an email tousrp-users-leave@lists.ettus.com >> The procedures for making this work are here: >> >> https://files.ettus.com/manual/page_usrp_x3x0.html#x3x0_hw_pcie >> >> >> _______________________________________________ >> USRP-users mailing list -- usrp-users@lists.ettus.com >> To unsubscribe send an email to usrp-users-leave@lists.ettus.com >> >
HD
Heinz, Dominik
Wed, Jan 29, 2025 2:37 PM

Thanks for the reply.

I don't see how the host PC has the same IP address.

The subnets are different? I also created a separate thread for discussing this, since it does not have anything to do with the PCIe problems discussed earlier.


From: Marcus D. Leech patchvonbraun@gmail.com
Sent: Wednesday, January 29, 2025 3:21:51 PM
To: Heinz, Dominik; Martin Braun
Cc: usrp-users@lists.ettus.com
Subject: [EXTERN] Re: [EXTERN] Re: [EXTERN] [USRP-users] Re: [EXTERN] Re: [EXTERN] Re: Re: [EXTERN] Re: X310 RIO Session Initialization Failure (Error code -63150)

On 29/01/2025 04:32, Heinz, Dominik wrote:

Okay,

So I am having trouble to interface with the X310, despite having set the correct IP addresses for both interfaces..?

gnb@xgoss-host:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp77s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 9c:6b:00:56:a3:a5 brd ff:ff:ff:ff:ff:ff
3: enp1s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether f8:f2:1e:9b:f1:60 brd ff:ff:ff:ff:ff:ff
inet 192.168.30.2/24 brd 192.168.30.255 scope global noprefixroute enp1s0f0
valid_lft forever preferred_lft forever
inet6 fe80::a1a4:f18c:ce2c:bbf1/64 scope link noprefixroute
valid_lft forever preferred_lft forever
4: enp1s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether f8:f2:1e:9b:f1:61 brd ff:ff:ff:ff:ff:ff
inet 192.168.40.2/24 brd 192.168.40.255 scope global noprefixroute enp1s0f1
valid_lft forever preferred_lft forever
inet6 fe80::f167:b030:ddfa:a249/64 scope link noprefixroute
valid_lft forever preferred_lft forever
5: ogstun: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1400 qdisc fq_codel state UP group default qlen 500
link/none
inet 10.45.0.1/16 brd 10.45.255.255 scope global ogstun
valid_lft forever preferred_lft forever
inet6 2001:db8:cafe::1/48 scope global
valid_lft forever preferred_lft forever
inet6 fe80::d4:8229:f90e:9ef8/64 scope link stable-privacy
valid_lft forever preferred_lft forever
6: wlp76s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether f4:46:37:30:ee:5e brd ff:ff:ff:ff:ff:ff
inet 192.168.1.146/24 brd 192.168.1.255 scope global dynamic noprefixroute wlp76s0
valid_lft 6788sec preferred_lft 6788sec
inet6 fe80::ee0a:9d:d428:6cb4/64 scope link noprefixroute
valid_lft forever preferred_lft forever
7: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 52:54:00:6d:72:20 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
valid_lft forever preferred_lft forever
8: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:87:6d:5c:d9 brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
valid_lft forever preferred_lft forever
9: br-add5841a3206: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:9c:fa:66:b5 brd ff:ff:ff:ff:ff:ff
inet 192.168.11.1/24 brd 192.168.11.255 scope global br-add5841a3206
valid_lft forever preferred_lft forever
gnb@xgoss-host:~$ uhd_find_devices
[INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; UHD_4.7.0.0-0ubuntu1~jammy1
No UHD Devices Found
gnb@xgoss-host:~$ uhd_usrp_probe
[INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; UHD_4.7.0.0-0ubuntu1~jammy1
Error: LookupError: KeyError: No devices found for ----->
Empty Device Address

I got the SDR working before but for some reason I can't get this working reliably.

I assigned the IP addresses to the interfaces with the Network GUI in Ubuntu.

But I can't find the device neither via uhd_find_devices, not with uhd_usrp_probe.

The X310 is flashed with the XG image for dual SFP+.

Do you mind guiding me step by step how to configure the IPs for the interfaces correctly and interface with the SDR? I don't see what I am missing?

You've given your HOST PC the same addresses as the X310.  Choose some other address.  Like  .1 or .3


From: Marcus D. Leech patchvonbraun@gmail.commailto:patchvonbraun@gmail.com
Sent: Monday, January 27, 2025 12:32:14 PM
To: Heinz, Dominik; Martin Braun
Cc: usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com
Subject: [EXTERN] Re: [EXTERN] [USRP-users] Re: [EXTERN] Re: [EXTERN] Re: Re: [EXTERN] Re: X310 RIO Session Initialization Failure (Error code -63150)

On 27/01/2025 05:29, Heinz, Dominik wrote:

Okay, seems like I had to manually set the IP addresses for the interfaces. Now I can interact perfectly with the device.

Tho, I don't know how to configure it to use both Links simultaneously, like you suggested (to do 2x200 Msps streaming).

Any advice on that would be appreciated :)

Use the second_addr argument:

https://files.ettus.com/manual/page_usrp_x3x0.html#x3x0_usage

So, assuming the XG image, your device arguments would include:

addr=192.168.30.2,second_addr=192.168.40.2


From: Heinz, Dominik dominik.heinz@h-da.demailto:dominik.heinz@h-da.de
Sent: Monday, January 27, 2025 10:32:27 AM
To: Martin Braun
Cc: Marcus D. Leech; usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com
Subject: [EXTERN] [USRP-users] Re: [EXTERN] Re: [EXTERN] Re: Re: [EXTERN] Re: X310 RIO Session Initialization Failure (Error code -63150)

When I run the image loader without the IP address parameter it seems to be flashing the correctly.

uhd_image_loader --args="type=x300"

However, I don't see how I can configure the IP address to be able to interact via the 10GbE links (?)


From: Heinz, Dominik dominik.heinz@h-da.demailto:dominik.heinz@h-da.de
Sent: Monday, January 27, 2025 10:18:41 AM
To: Martin Braun
Cc: Marcus D. Leech; usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com
Subject: [EXTERN] [USRP-users] Re: [EXTERN] Re: Re: [EXTERN] Re: X310 RIO Session Initialization Failure (Error code -63150)

Hello Martin,
Hello Marcus,

The X310 does not show up as a RIO device, but rather like this:

4a:00.0 Signal processing controller: National Instruments PXIe/PCIe Device (rev ff) (prog-if ff)
!!! Unknown header type 7f
Kernel driver in use: niusrpriok
Kernel modules: niusrpriok

This seems already problematic (?)

The nisrpriorpc server seems to be running fine:

gnb@xgoss-host:~$ sudo systemctl status niusrpriorpc
● niusrpriorpc.service - LSB: National Instruments USRP RIO Service
Loaded: loaded (/etc/init.d/niusrpriorpc; generated)
Active: active (running) since Mon 2025-01-27 09:37:21 CET; 23min ago
Docs: man:systemd-sysv-generator(8)
Tasks: 4 (limit: 153252)
Memory: 98.6M
CPU: 13.872s
CGroup: /system.slice/niusrpriorpc.service
└─1631 /usr/sbin/niusrpriorpc --daemon

Jan 27 09:37:21 xgoss-host systemd[1]: Starting LSB: National Instruments USRP RIO Service...
Jan 27 09:37:21 xgoss-host systemd[1]: Started LSB: National Instruments USRP RIO Service.

You also mentioned that the X310 needs to be powered on before the host system.
I have of course done this - since to my knowledge hot plugging is not possible in the case of PCIe.

Running uhd_usrp_probe as root doesn't change anything.

I am okay with trying out the 10GbE instead, but I am not able to interact with the device that way.
I can't seem to specify an IP or load a firmware image this way. I tried:

gnb@xgoss-host:~$ uhd_image_loader --args="type=x300,addr=192.168.10.2,fpga=HG"
[INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; UHD_4.7.0.0-0ubuntu1~jammy1
No applicable UHD devices found

Any idea how to proceed? Can't seem to get the device running via PCIe, and via 10GbE I can't interact with the device either.
I will provide the details in the Github issue shortly.


From: Martin Braun martin.braun@ettus.commailto:martin.braun@ettus.com
Sent: Friday, January 24, 2025 12:19:00 PM
To: Heinz, Dominik
Cc: Marcus D. Leech; usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com
Subject: [EXTERN] Re: [USRP-users] Re: [EXTERN] Re: X310 RIO Session Initialization Failure (Error code -63150)

Dominik,

can you provide as much info as you can here: https://github.com/EttusResearch/uhd/issues/818?

Like Marcus said, the PCIe interface is not used a lot (except by LabView users), so if you can use 10 GbE instead I recommend doing that (that also allows you to do 2x200 Msps streaming, if you have two ports).

--M

On Wed, Jan 22, 2025 at 2:58 PM Heinz, Dominik <dominik.heinz@h-da.demailto:dominik.heinz@h-da.de> wrote:

I followed the steps in the guide you linked, - however, I still have the issue.

The uhd drivers are installed, and the niuspriorpc service is running. However, I still the the RIO session initialization failure.

Anything else I could try? I still don't understand what is the cause for this.


From: Marcus D. Leech <patchvonbraun@gmail.commailto:patchvonbraun@gmail.com>
Sent: Tuesday, January 21, 2025 8:32:39 PM
To: usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com
Subject: [EXTERN] [USRP-users] Re: X310 RIO Session Initialization Failure (Error code -63150)

On 21/01/2025 09:26, Heinz, Dominik wrote:

I'm experiencing an initialization issue with my Ettus X310 USRP device.

My setup consists of an Ettus X310 connected through a PCIe Card using a Molex cable to my Linux machine.

I'm running Ubuntu with kernel version 6.8.0-51-generic and have installed all the necessary UHD packages on the system.

The X310 is properly detected when running uhd_find_devices, but attempting to probe the device with uhd_usrp_probe results in a RIO session initialization error.
I attached the error output below.
What is causing this RIO session initialization failure and how can it be resolved?

gnb@xgoss-host:~/srsRAN_Project/build4ac5300/apps/gnb$ uhd_find_devices
[INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; UHD_4.7.0.0-0ubuntu1~jammy1

-- UHD Device 0

Device Address:
serial:
fpga: HG
name:
product: X310
resource: RIO0
type: x300

gnb@xgoss-host:~/srsRAN_Project/build4ac5300/apps/gnb$ uhd_usrp_probe
[INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; UHD_4.7.0.0-0ubuntu1~jammy1
[INFO] [X300] X300 initialization sequence...
[INFO] [X300] Connecting to niusrpriorpc at localhost:5444...
[INFO] [X300] Using LVBITX bitfile /usr/share/uhd/images/usrp_x310_fpga_HG.lvbitx
Error: RuntimeError: x300_impl: Could not initialize RIO session. Unknown error. (Error code -63150)


USRP-users mailing list -- usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-leave@lists.ettus.commailto:usrp-users-leave@lists.ettus.com

The procedures for making this work are here:

https://files.ettus.com/manual/page_usrp_x3x0.html#x3x0_hw_pcie


USRP-users mailing list -- usrp-users@lists.ettus.commailto:usrp-users@lists.ettus.com
To unsubscribe send an email to usrp-users-leave@lists.ettus.commailto:usrp-users-leave@lists.ettus.com

Thanks for the reply. I don't see how the host PC has the same IP address. The subnets are different? I also created a separate thread for discussing this, since it does not have anything to do with the PCIe problems discussed earlier. ________________________________ From: Marcus D. Leech <patchvonbraun@gmail.com> Sent: Wednesday, January 29, 2025 3:21:51 PM To: Heinz, Dominik; Martin Braun Cc: usrp-users@lists.ettus.com Subject: [EXTERN] Re: [EXTERN] Re: [EXTERN] [USRP-users] Re: [EXTERN] Re: [EXTERN] Re: Re: [EXTERN] Re: X310 RIO Session Initialization Failure (Error code -63150) On 29/01/2025 04:32, Heinz, Dominik wrote: Okay, So I am having trouble to interface with the X310, despite having set the correct IP addresses for both interfaces..? gnb@xgoss-host:~$ ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp77s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 9c:6b:00:56:a3:a5 brd ff:ff:ff:ff:ff:ff 3: enp1s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether f8:f2:1e:9b:f1:60 brd ff:ff:ff:ff:ff:ff inet 192.168.30.2/24 brd 192.168.30.255 scope global noprefixroute enp1s0f0 valid_lft forever preferred_lft forever inet6 fe80::a1a4:f18c:ce2c:bbf1/64 scope link noprefixroute valid_lft forever preferred_lft forever 4: enp1s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether f8:f2:1e:9b:f1:61 brd ff:ff:ff:ff:ff:ff inet 192.168.40.2/24 brd 192.168.40.255 scope global noprefixroute enp1s0f1 valid_lft forever preferred_lft forever inet6 fe80::f167:b030:ddfa:a249/64 scope link noprefixroute valid_lft forever preferred_lft forever 5: ogstun: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1400 qdisc fq_codel state UP group default qlen 500 link/none inet 10.45.0.1/16 brd 10.45.255.255 scope global ogstun valid_lft forever preferred_lft forever inet6 2001:db8:cafe::1/48 scope global valid_lft forever preferred_lft forever inet6 fe80::d4:8229:f90e:9ef8/64 scope link stable-privacy valid_lft forever preferred_lft forever 6: wlp76s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether f4:46:37:30:ee:5e brd ff:ff:ff:ff:ff:ff inet 192.168.1.146/24 brd 192.168.1.255 scope global dynamic noprefixroute wlp76s0 valid_lft 6788sec preferred_lft 6788sec inet6 fe80::ee0a:9d:d428:6cb4/64 scope link noprefixroute valid_lft forever preferred_lft forever 7: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 52:54:00:6d:72:20 brd ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 valid_lft forever preferred_lft forever 8: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default link/ether 02:42:87:6d:5c:d9 brd ff:ff:ff:ff:ff:ff inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0 valid_lft forever preferred_lft forever 9: br-add5841a3206: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default link/ether 02:42:9c:fa:66:b5 brd ff:ff:ff:ff:ff:ff inet 192.168.11.1/24 brd 192.168.11.255 scope global br-add5841a3206 valid_lft forever preferred_lft forever gnb@xgoss-host:~$ uhd_find_devices [INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; UHD_4.7.0.0-0ubuntu1~jammy1 No UHD Devices Found gnb@xgoss-host:~$ uhd_usrp_probe [INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; UHD_4.7.0.0-0ubuntu1~jammy1 Error: LookupError: KeyError: No devices found for -----> Empty Device Address I got the SDR working before but for some reason I can't get this working reliably. I assigned the IP addresses to the interfaces with the Network GUI in Ubuntu. But I can't find the device neither via uhd_find_devices, not with uhd_usrp_probe. The X310 is flashed with the XG image for dual SFP+. Do you mind guiding me step by step how to configure the IPs for the interfaces correctly and interface with the SDR? I don't see what I am missing? You've given your HOST PC the same addresses as the X310. Choose some other address. Like .1 or .3 ________________________________ From: Marcus D. Leech <patchvonbraun@gmail.com><mailto:patchvonbraun@gmail.com> Sent: Monday, January 27, 2025 12:32:14 PM To: Heinz, Dominik; Martin Braun Cc: usrp-users@lists.ettus.com<mailto:usrp-users@lists.ettus.com> Subject: [EXTERN] Re: [EXTERN] [USRP-users] Re: [EXTERN] Re: [EXTERN] Re: Re: [EXTERN] Re: X310 RIO Session Initialization Failure (Error code -63150) On 27/01/2025 05:29, Heinz, Dominik wrote: Okay, seems like I had to manually set the IP addresses for the interfaces. Now I can interact perfectly with the device. Tho, I don't know how to configure it to use both Links simultaneously, like you suggested (to do 2x200 Msps streaming). Any advice on that would be appreciated :) Use the second_addr argument: https://files.ettus.com/manual/page_usrp_x3x0.html#x3x0_usage So, assuming the XG image, your device arguments would include: addr=192.168.30.2,second_addr=192.168.40.2 ________________________________ From: Heinz, Dominik <dominik.heinz@h-da.de><mailto:dominik.heinz@h-da.de> Sent: Monday, January 27, 2025 10:32:27 AM To: Martin Braun Cc: Marcus D. Leech; usrp-users@lists.ettus.com<mailto:usrp-users@lists.ettus.com> Subject: [EXTERN] [USRP-users] Re: [EXTERN] Re: [EXTERN] Re: Re: [EXTERN] Re: X310 RIO Session Initialization Failure (Error code -63150) When I run the image loader without the IP address parameter it seems to be flashing the correctly. uhd_image_loader --args="type=x300" However, I don't see how I can configure the IP address to be able to interact via the 10GbE links (?) ________________________________ From: Heinz, Dominik <dominik.heinz@h-da.de><mailto:dominik.heinz@h-da.de> Sent: Monday, January 27, 2025 10:18:41 AM To: Martin Braun Cc: Marcus D. Leech; usrp-users@lists.ettus.com<mailto:usrp-users@lists.ettus.com> Subject: [EXTERN] [USRP-users] Re: [EXTERN] Re: Re: [EXTERN] Re: X310 RIO Session Initialization Failure (Error code -63150) Hello Martin, Hello Marcus, The X310 does not show up as a RIO device, but rather like this: 4a:00.0 Signal processing controller: National Instruments PXIe/PCIe Device (rev ff) (prog-if ff) !!! Unknown header type 7f Kernel driver in use: niusrpriok Kernel modules: niusrpriok This seems already problematic (?) The nisrpriorpc server seems to be running fine: gnb@xgoss-host:~$ sudo systemctl status niusrpriorpc ● niusrpriorpc.service - LSB: National Instruments USRP RIO Service Loaded: loaded (/etc/init.d/niusrpriorpc; generated) Active: active (running) since Mon 2025-01-27 09:37:21 CET; 23min ago Docs: man:systemd-sysv-generator(8) Tasks: 4 (limit: 153252) Memory: 98.6M CPU: 13.872s CGroup: /system.slice/niusrpriorpc.service └─1631 /usr/sbin/niusrpriorpc --daemon Jan 27 09:37:21 xgoss-host systemd[1]: Starting LSB: National Instruments USRP RIO Service... Jan 27 09:37:21 xgoss-host systemd[1]: Started LSB: National Instruments USRP RIO Service. You also mentioned that the X310 needs to be powered on before the host system. I have of course done this - since to my knowledge hot plugging is not possible in the case of PCIe. Running uhd_usrp_probe as root doesn't change anything. I am okay with trying out the 10GbE instead, but I am not able to interact with the device that way. I can't seem to specify an IP or load a firmware image this way. I tried: gnb@xgoss-host:~$ uhd_image_loader --args="type=x300,addr=192.168.10.2,fpga=HG" [INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; UHD_4.7.0.0-0ubuntu1~jammy1 No applicable UHD devices found Any idea how to proceed? Can't seem to get the device running via PCIe, and via 10GbE I can't interact with the device either. I will provide the details in the Github issue shortly. ________________________________ From: Martin Braun <martin.braun@ettus.com><mailto:martin.braun@ettus.com> Sent: Friday, January 24, 2025 12:19:00 PM To: Heinz, Dominik Cc: Marcus D. Leech; usrp-users@lists.ettus.com<mailto:usrp-users@lists.ettus.com> Subject: [EXTERN] Re: [USRP-users] Re: [EXTERN] Re: X310 RIO Session Initialization Failure (Error code -63150) Dominik, can you provide as much info as you can here: https://github.com/EttusResearch/uhd/issues/818? Like Marcus said, the PCIe interface is not used a lot (except by LabView users), so if you can use 10 GbE instead I recommend doing that (that also allows you to do 2x200 Msps streaming, if you have two ports). --M On Wed, Jan 22, 2025 at 2:58 PM Heinz, Dominik <dominik.heinz@h-da.de<mailto:dominik.heinz@h-da.de>> wrote: I followed the steps in the guide you linked, - however, I still have the issue. The uhd drivers are installed, and the niuspriorpc service is running. However, I still the the RIO session initialization failure. Anything else I could try? I still don't understand what is the cause for this. ________________________________ From: Marcus D. Leech <patchvonbraun@gmail.com<mailto:patchvonbraun@gmail.com>> Sent: Tuesday, January 21, 2025 8:32:39 PM To: usrp-users@lists.ettus.com<mailto:usrp-users@lists.ettus.com> Subject: [EXTERN] [USRP-users] Re: X310 RIO Session Initialization Failure (Error code -63150) On 21/01/2025 09:26, Heinz, Dominik wrote: I'm experiencing an initialization issue with my Ettus X310 USRP device. My setup consists of an Ettus X310 connected through a PCIe Card using a Molex cable to my Linux machine. I'm running Ubuntu with kernel version 6.8.0-51-generic and have installed all the necessary UHD packages on the system. The X310 is properly detected when running uhd_find_devices, but attempting to probe the device with uhd_usrp_probe results in a RIO session initialization error. I attached the error output below. What is causing this RIO session initialization failure and how can it be resolved? gnb@xgoss-host:~/srsRAN_Project/build4ac5300/apps/gnb$ uhd_find_devices [INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; UHD_4.7.0.0-0ubuntu1~jammy1 -------------------------------------------------- -- UHD Device 0 -------------------------------------------------- Device Address: serial: fpga: HG name: product: X310 resource: RIO0 type: x300 gnb@xgoss-host:~/srsRAN_Project/build4ac5300/apps/gnb$ uhd_usrp_probe [INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; UHD_4.7.0.0-0ubuntu1~jammy1 [INFO] [X300] X300 initialization sequence... [INFO] [X300] Connecting to niusrpriorpc at localhost:5444... [INFO] [X300] Using LVBITX bitfile /usr/share/uhd/images/usrp_x310_fpga_HG.lvbitx Error: RuntimeError: x300_impl: Could not initialize RIO session. Unknown error. (Error code -63150) _______________________________________________ USRP-users mailing list -- usrp-users@lists.ettus.com<mailto:usrp-users@lists.ettus.com> To unsubscribe send an email to usrp-users-leave@lists.ettus.com<mailto:usrp-users-leave@lists.ettus.com> The procedures for making this work are here: https://files.ettus.com/manual/page_usrp_x3x0.html#x3x0_hw_pcie _______________________________________________ USRP-users mailing list -- usrp-users@lists.ettus.com<mailto:usrp-users@lists.ettus.com> To unsubscribe send an email to usrp-users-leave@lists.ettus.com<mailto:usrp-users-leave@lists.ettus.com>
MD
Marcus D. Leech
Wed, Jan 29, 2025 3:23 PM

On 29/01/2025 09:37, Heinz, Dominik wrote:

Thanks for the reply.

I don't see how the host PC has the same IP address.

The subnets are different? I also created a separate thread for
discussing this, since it does not have anything to do with the PCIe
problems discussed earlier.


From: Marcus D. Leech patchvonbraun@gmail.com
Sent: Wednesday, January 29, 2025 3:21:51 PM
To: Heinz, Dominik; Martin Braun
Cc: usrp-users@lists.ettus.com
Subject: [EXTERN] Re: [EXTERN] Re: [EXTERN] [USRP-users] Re:
[EXTERN] Re: [EXTERN] Re: Re: [EXTERN] Re: X310 RIO Session
Initialization Failure (Error code -63150)
On 29/01/2025 04:32, Heinz, Dominik wrote:

Okay,

So I am having trouble to interface with the X310, despite having set
the correct IP addresses for both interfaces..?

gnb@xgoss-host:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp77s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel
state UP group default qlen 1000
    link/ether 9c:6b:00:56:a3:a5 brd ff:ff:ff:ff:ff:ff
3: enp1s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq
state UP group default qlen 1000
    link/ether f8:f2:1e:9b:f1:60 brd ff:ff:ff:ff:ff:ff
    inet 192.168.30.2/24 brd 192.168.30.255 scope global
noprefixroute enp1s0f0
       valid_lft forever preferred_lft forever
    inet6 fe80::a1a4:f18c:ce2c:bbf1/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
4: enp1s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq
state UP group default qlen 1000
    link/ether f8:f2:1e:9b:f1:61 brd ff:ff:ff:ff:ff:ff
    inet 192.168.40.2/24 brd 192.168.40.255 scope global
noprefixroute enp1s0f1
       valid_lft forever preferred_lft forever
    inet6 fe80::f167:b030:ddfa:a249/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
5: ogstun: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1400 qdisc
fq_codel state UP group default qlen 500
    link/none
    inet 10.45.0.1/16 brd 10.45.255.255 scope global ogstun
       valid_lft forever preferred_lft forever
    inet6 2001:db8:cafe::1/48 scope global
       valid_lft forever preferred_lft forever
    inet6 fe80::d4:8229:f90e:9ef8/64 scope link stable-privacy
       valid_lft forever preferred_lft forever
6: wlp76s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
state UP group default qlen 1000
    link/ether f4:46:37:30:ee:5e brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.146/24 brd 192.168.1.255 scope global dynamic
noprefixroute wlp76s0
       valid_lft 6788sec preferred_lft 6788sec
    inet6 fe80::ee0a:9d:d428:6cb4/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
7: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
state DOWN group default qlen 1000
    link/ether 52:54:00:6d:72:20 brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever
8: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc
noqueue state DOWN group default
    link/ether 02:42:87:6d:5c:d9 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever
9: br-add5841a3206: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500
qdisc noqueue state DOWN group default
    link/ether 02:42:9c:fa:66:b5 brd ff:ff:ff:ff:ff:ff
    inet 192.168.11.1/24 brd 192.168.11.255 scope global br-add5841a3206
       valid_lft forever preferred_lft forever
gnb@xgoss-host:~$ uhd_find_devices
[INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400;
UHD_4.7.0.0-0ubuntu1~jammy1
No UHD Devices Found
gnb@xgoss-host:~$ uhd_usrp_probe
[INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400;
UHD_4.7.0.0-0ubuntu1~jammy1
Error: LookupError: KeyError: No devices found for ----->
Empty Device Address

I got the SDR working before but for some reason I can't get this
working reliably.

I assigned the IP addresses to the interfaces with the Network GUI in
Ubuntu.

But I can't find the device neither via uhd_find_devices, not with
uhd_usrp_probe.

The X310 is flashed with the XG image for dual SFP+.

Do you mind guiding me step by step how to configure the IPs for the
interfaces correctly and interface with the SDR? I don't see what I
am missing?

You've given your HOST PC the same addresses as the X310. Choose some
other address.  Like   .1 or .3


From: Marcus D. Leech patchvonbraun@gmail.com
Sent: Monday, January 27, 2025 12:32:14 PM
To: Heinz, Dominik; Martin Braun
Cc: usrp-users@lists.ettus.com
Subject: [EXTERN] Re: [EXTERN] [USRP-users] Re: [EXTERN] Re:
[EXTERN] Re: Re: [EXTERN] Re: X310 RIO Session Initialization Failure
(Error code -63150)
On 27/01/2025 05:29, Heinz, Dominik wrote:

Okay, seems like I had to manually set the IP addresses for the
interfaces. Now I can interact perfectly with the device.

Tho, I don't know how to configure it to use both Links
simultaneously, like you suggested (to do 2x200 Msps streaming).

Any advice on that would be appreciated :)

Use the second_addr argument:

https://files.ettus.com/manual/page_usrp_x3x0.html#x3x0_usage

So, assuming the XG image, your device arguments would include:

addr=192.168.30.2,second_addr=192.168.40.2


From: Heinz, Dominik dominik.heinz@h-da.de
Sent: Monday, January 27, 2025 10:32:27 AM
To: Martin Braun
Cc: Marcus D. Leech; usrp-users@lists.ettus.com
Subject: [EXTERN] [USRP-users] Re: [EXTERN] Re: [EXTERN] Re: Re:
[EXTERN] Re: X310 RIO Session Initialization Failure (Error code
-63150)

When I run the image loader without the IP address parameter it
seems to be flashing the correctly.

uhd_image_loader --args="type=x300"

However, I don't see how I can configure the IP address to be able
to interact via the 10GbE links (?)


From: Heinz, Dominik dominik.heinz@h-da.de
Sent: Monday, January 27, 2025 10:18:41 AM
To: Martin Braun
Cc: Marcus D. Leech; usrp-users@lists.ettus.com
Subject: [EXTERN] [USRP-users] Re: [EXTERN] Re: Re: [EXTERN] Re:
X310 RIO Session Initialization Failure (Error code -63150)
Hello Martin,
Hello Marcus,

The X310 does not show up as a RIO device, but rather like this:

4a:00.0 Signal processing controller: National Instruments PXIe/PCIe
Device (rev ff) (prog-if ff)
    !!! Unknown header type 7f
    Kernel driver in use: niusrpriok
    Kernel modules: niusrpriok

This seems already problematic (?)

The nisrpriorpc server seems to be running fine:

gnb@xgoss-host:~$ sudo systemctl status niusrpriorpc
● niusrpriorpc.service - LSB: National Instruments USRP RIO Service
     Loaded: loaded (/etc/init.d/niusrpriorpc; generated)
     Active: active (running) since Mon 2025-01-27 09:37:21 CET;
23min ago
       Docs: man:systemd-sysv-generator(8)
      Tasks: 4 (limit: 153252)
     Memory: 98.6M
        CPU: 13.872s
     CGroup: /system.slice/niusrpriorpc.service
             └─1631 /usr/sbin/niusrpriorpc --daemon

Jan 27 09:37:21 xgoss-host systemd[1]: Starting LSB: National
Instruments USRP RIO Service...
Jan 27 09:37:21 xgoss-host systemd[1]: Started LSB: National
Instruments USRP RIO Service.

You also mentioned that the X310 needs to be powered on before the
host system.
I have of course done this - since to my knowledge hot plugging is
not possible in the case of PCIe.

Running uhd_usrp_probe as root doesn't change anything.

I am okay with trying out the 10GbE instead, but I am not able to
interact with the device that way.
I can't seem to specify an IP or load a firmware image this way. I
tried:

gnb@xgoss-host:~$ uhd_image_loader
--args="type=x300,addr=192.168.10.2,fpga=HG"
[INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400;
UHD_4.7.0.0-0ubuntu1~jammy1
No applicable UHD devices found

Any idea how to proceed? Can't seem to get the device running via
PCIe, and via 10GbE I can't interact with the device either.
I will provide the details in the Github issue shortly.


From: Martin Braun martin.braun@ettus.com
Sent: Friday, January 24, 2025 12:19:00 PM
To: Heinz, Dominik
Cc: Marcus D. Leech; usrp-users@lists.ettus.com
Subject: [EXTERN] Re: [USRP-users] Re: [EXTERN] Re: X310 RIO
Session Initialization Failure (Error code -63150)
Dominik,

can you provide as much info as you can here:
https://github.com/EttusResearch/uhd/issues/818?

Like Marcus said, the PCIe interface is not used a lot (except by
LabView users), so if you can use 10 GbE instead I recommend doing
that (that also allows you to do 2x200 Msps streaming, if you have
two ports).

--M

On Wed, Jan 22, 2025 at 2:58 PM Heinz, Dominik
dominik.heinz@h-da.de wrote:

 I followed the steps in the guide you linked, - however, I still
 have the issue.

 The uhd drivers are installed, and the niuspriorpc service is
 running. However, I still the the RIO session initialization
 failure.


 Anything else I could try? I still don't understand what is the
 cause for this.

 ------------------------------------------------------------------------
 *From:* Marcus D. Leech <patchvonbraun@gmail.com>
 *Sent:* Tuesday, January 21, 2025 8:32:39 PM
 *To:* usrp-users@lists.ettus.com
 *Subject:* [EXTERN] [USRP-users] Re: X310 RIO Session
 Initialization Failure (Error code -63150)
 On 21/01/2025 09:26, Heinz, Dominik wrote:
 I'm experiencing an initialization issue with my Ettus X310
 USRP device.

 My setup consists of an Ettus X310 connected through a PCIe
 Card using a Molex cable to my Linux machine.

 I'm running Ubuntu with kernel version 6.8.0-51-generic and
 have installed all the necessary UHD packages on the system.


 The X310 is properly detected when running |uhd_find_devices|,
 but attempting to probe the device with |uhd_usrp_probe|
 results in a RIO session initialization error.
 I attached the error output below.
 What is causing this RIO session initialization failure and how
 can it be resolved?

 gnb@xgoss-host:~/srsRAN_Project/build4ac5300/apps/gnb$
 uhd_find_devices
 [INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400;
 UHD_4.7.0.0-0ubuntu1~jammy1
 --------------------------------------------------
 -- UHD Device 0
 --------------------------------------------------
 Device Address:
     serial:
     fpga: HG
     name:
     product: X310
     resource: RIO0
     type: x300

 gnb@xgoss-host:~/srsRAN_Project/build4ac5300/apps/gnb$
 uhd_usrp_probe
 [INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400;
 UHD_4.7.0.0-0ubuntu1~jammy1
 [INFO] [X300] X300 initialization sequence...
 [INFO] [X300] Connecting to niusrpriorpc at localhost:5444...
 [INFO] [X300] Using LVBITX bitfile
 /usr/share/uhd/images/usrp_x310_fpga_HG.lvbitx
 Error: RuntimeError: x300_impl: Could not initialize RIO
 session. Unknown error. (Error code -63150)



 _______________________________________________
 USRP-users mailing list --usrp-users@lists.ettus.com
 To unsubscribe send an email tousrp-users-leave@lists.ettus.com
 The procedures for making this work are here:

 https://files.ettus.com/manual/page_usrp_x3x0.html#x3x0_hw_pcie


 _______________________________________________
 USRP-users mailing list -- usrp-users@lists.ettus.com
 To unsubscribe send an email to usrp-users-leave@lists.ettus.com
On 29/01/2025 09:37, Heinz, Dominik wrote: > > Thanks for the reply. > > I don't see how the host PC has the same IP address. > > > The subnets are different? I also created a separate thread for > discussing this, since it does not have anything to do with the PCIe > problems discussed earlier. > Please see here. https://files.ettus.com/manual/page_usrp_x3x0.html#x3x0_setup_network_host_interface > > ------------------------------------------------------------------------ > *From:* Marcus D. Leech <patchvonbraun@gmail.com> > *Sent:* Wednesday, January 29, 2025 3:21:51 PM > *To:* Heinz, Dominik; Martin Braun > *Cc:* usrp-users@lists.ettus.com > *Subject:* [EXTERN] Re: [EXTERN] Re: [EXTERN] [USRP-users] Re: > [EXTERN] Re: [EXTERN] Re: Re: [EXTERN] Re: X310 RIO Session > Initialization Failure (Error code -63150) > On 29/01/2025 04:32, Heinz, Dominik wrote: >> >> Okay, >> >> So I am having trouble to interface with the X310, despite having set >> the correct IP addresses for both interfaces..? >> >> >> gnb@xgoss-host:~$ ip a >> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN >> group default qlen 1000 >>     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 >>     inet 127.0.0.1/8 scope host lo >>        valid_lft forever preferred_lft forever >>     inet6 ::1/128 scope host >>        valid_lft forever preferred_lft forever >> 2: enp77s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel >> state UP group default qlen 1000 >>     link/ether 9c:6b:00:56:a3:a5 brd ff:ff:ff:ff:ff:ff >> 3: enp1s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq >> state UP group default qlen 1000 >>     link/ether f8:f2:1e:9b:f1:60 brd ff:ff:ff:ff:ff:ff >>     inet 192.168.30.2/24 brd 192.168.30.255 scope global >> noprefixroute enp1s0f0 >>        valid_lft forever preferred_lft forever >>     inet6 fe80::a1a4:f18c:ce2c:bbf1/64 scope link noprefixroute >>        valid_lft forever preferred_lft forever >> 4: enp1s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq >> state UP group default qlen 1000 >>     link/ether f8:f2:1e:9b:f1:61 brd ff:ff:ff:ff:ff:ff >>     inet 192.168.40.2/24 brd 192.168.40.255 scope global >> noprefixroute enp1s0f1 >>        valid_lft forever preferred_lft forever >>     inet6 fe80::f167:b030:ddfa:a249/64 scope link noprefixroute >>        valid_lft forever preferred_lft forever >> 5: ogstun: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1400 qdisc >> fq_codel state UP group default qlen 500 >>     link/none >>     inet 10.45.0.1/16 brd 10.45.255.255 scope global ogstun >>        valid_lft forever preferred_lft forever >>     inet6 2001:db8:cafe::1/48 scope global >>        valid_lft forever preferred_lft forever >>     inet6 fe80::d4:8229:f90e:9ef8/64 scope link stable-privacy >>        valid_lft forever preferred_lft forever >> 6: wlp76s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue >> state UP group default qlen 1000 >>     link/ether f4:46:37:30:ee:5e brd ff:ff:ff:ff:ff:ff >>     inet 192.168.1.146/24 brd 192.168.1.255 scope global dynamic >> noprefixroute wlp76s0 >>        valid_lft 6788sec preferred_lft 6788sec >>     inet6 fe80::ee0a:9d:d428:6cb4/64 scope link noprefixroute >>        valid_lft forever preferred_lft forever >> 7: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue >> state DOWN group default qlen 1000 >>     link/ether 52:54:00:6d:72:20 brd ff:ff:ff:ff:ff:ff >>     inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 >>        valid_lft forever preferred_lft forever >> 8: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc >> noqueue state DOWN group default >>     link/ether 02:42:87:6d:5c:d9 brd ff:ff:ff:ff:ff:ff >>     inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0 >>        valid_lft forever preferred_lft forever >> 9: br-add5841a3206: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 >> qdisc noqueue state DOWN group default >>     link/ether 02:42:9c:fa:66:b5 brd ff:ff:ff:ff:ff:ff >>     inet 192.168.11.1/24 brd 192.168.11.255 scope global br-add5841a3206 >>        valid_lft forever preferred_lft forever >> gnb@xgoss-host:~$ uhd_find_devices >> [INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; >> UHD_4.7.0.0-0ubuntu1~jammy1 >> No UHD Devices Found >> gnb@xgoss-host:~$ uhd_usrp_probe >> [INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; >> UHD_4.7.0.0-0ubuntu1~jammy1 >> Error: LookupError: KeyError: No devices found for -----> >> Empty Device Address >> >> >> I got the SDR working before but for some reason I can't get this >> working reliably. >> >> I assigned the IP addresses to the interfaces with the Network GUI in >> Ubuntu. >> >> But I can't find the device neither via uhd_find_devices, not with >> uhd_usrp_probe. >> >> >> The X310 is flashed with the XG image for dual SFP+. >> >> >> Do you mind guiding me step by step how to configure the IPs for the >> interfaces correctly and interface with the SDR? I don't see what I >> am missing? >> > You've given your HOST PC the same addresses as the X310. Choose some > other address.  Like   .1 or .3 > > >> ------------------------------------------------------------------------ >> *From:* Marcus D. Leech <patchvonbraun@gmail.com> >> *Sent:* Monday, January 27, 2025 12:32:14 PM >> *To:* Heinz, Dominik; Martin Braun >> *Cc:* usrp-users@lists.ettus.com >> *Subject:* [EXTERN] Re: [EXTERN] [USRP-users] Re: [EXTERN] Re: >> [EXTERN] Re: Re: [EXTERN] Re: X310 RIO Session Initialization Failure >> (Error code -63150) >> On 27/01/2025 05:29, Heinz, Dominik wrote: >>> >>> Okay, seems like I had to manually set the IP addresses for the >>> interfaces. Now I can interact perfectly with the device. >>> >>> Tho, I don't know how to configure it to use both Links >>> simultaneously, like you suggested (to do 2x200 Msps streaming). >>> >>> >>> Any advice on that would be appreciated :) >>> >> Use the second_addr argument: >> >> https://files.ettus.com/manual/page_usrp_x3x0.html#x3x0_usage >> >> So, assuming the XG image, your device arguments would include: >> >> addr=192.168.30.2,second_addr=192.168.40.2 >> >> >>> ------------------------------------------------------------------------ >>> *From:* Heinz, Dominik <dominik.heinz@h-da.de> >>> *Sent:* Monday, January 27, 2025 10:32:27 AM >>> *To:* Martin Braun >>> *Cc:* Marcus D. Leech; usrp-users@lists.ettus.com >>> *Subject:* [EXTERN] [USRP-users] Re: [EXTERN] Re: [EXTERN] Re: Re: >>> [EXTERN] Re: X310 RIO Session Initialization Failure (Error code >>> -63150) >>> >>> When I run the image loader without the IP address parameter it >>> seems to be flashing the correctly. >>> >>> >>> uhd_image_loader --args="type=x300" >>> >>> >>> However, I don't see how I can configure the IP address to be able >>> to interact via the 10GbE links (?) >>> >>> ------------------------------------------------------------------------ >>> *From:* Heinz, Dominik <dominik.heinz@h-da.de> >>> *Sent:* Monday, January 27, 2025 10:18:41 AM >>> *To:* Martin Braun >>> *Cc:* Marcus D. Leech; usrp-users@lists.ettus.com >>> *Subject:* [EXTERN] [USRP-users] Re: [EXTERN] Re: Re: [EXTERN] Re: >>> X310 RIO Session Initialization Failure (Error code -63150) >>> Hello Martin, >>> Hello Marcus, >>> >>> The X310 does not show up as a RIO device, but rather like this: >>> >>> 4a:00.0 Signal processing controller: National Instruments PXIe/PCIe >>> Device (rev ff) (prog-if ff) >>>     !!! Unknown header type 7f >>>     Kernel driver in use: niusrpriok >>>     Kernel modules: niusrpriok >>> >>> This seems already problematic (?) >>> >>> The nisrpriorpc server seems to be running fine: >>> >>> gnb@xgoss-host:~$ sudo systemctl status niusrpriorpc >>> ● niusrpriorpc.service - LSB: National Instruments USRP RIO Service >>>      Loaded: loaded (/etc/init.d/niusrpriorpc; generated) >>>      Active: active (running) since Mon 2025-01-27 09:37:21 CET; >>> 23min ago >>>        Docs: man:systemd-sysv-generator(8) >>>       Tasks: 4 (limit: 153252) >>>      Memory: 98.6M >>>         CPU: 13.872s >>>      CGroup: /system.slice/niusrpriorpc.service >>>              └─1631 /usr/sbin/niusrpriorpc --daemon >>> >>> Jan 27 09:37:21 xgoss-host systemd[1]: Starting LSB: National >>> Instruments USRP RIO Service... >>> Jan 27 09:37:21 xgoss-host systemd[1]: Started LSB: National >>> Instruments USRP RIO Service. >>> >>> You also mentioned that the X310 needs to be powered on before the >>> host system. >>> I have of course done this - since to my knowledge hot plugging is >>> not possible in the case of PCIe. >>> >>> Running uhd_usrp_probe as root doesn't change anything. >>> >>> I am okay with trying out the 10GbE instead, but I am not able to >>> interact with the device that way. >>> I can't seem to specify an IP or load a firmware image this way. I >>> tried: >>> >>> gnb@xgoss-host:~$ uhd_image_loader >>> --args="type=x300,addr=192.168.10.2,fpga=HG" >>> [INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; >>> UHD_4.7.0.0-0ubuntu1~jammy1 >>> No applicable UHD devices found >>> >>> Any idea how to proceed? Can't seem to get the device running via >>> PCIe, and via 10GbE I can't interact with the device either. >>> I will provide the details in the Github issue shortly. >>> >>> >>> ------------------------------------------------------------------------ >>> *From:* Martin Braun <martin.braun@ettus.com> >>> *Sent:* Friday, January 24, 2025 12:19:00 PM >>> *To:* Heinz, Dominik >>> *Cc:* Marcus D. Leech; usrp-users@lists.ettus.com >>> *Subject:* [EXTERN] Re: [USRP-users] Re: [EXTERN] Re: X310 RIO >>> Session Initialization Failure (Error code -63150) >>> Dominik, >>> >>> can you provide as much info as you can here: >>> https://github.com/EttusResearch/uhd/issues/818? >>> >>> Like Marcus said, the PCIe interface is not used a lot (except by >>> LabView users), so if you can use 10 GbE instead I recommend doing >>> that (that also allows you to do 2x200 Msps streaming, if you have >>> two ports). >>> >>> --M >>> >>> On Wed, Jan 22, 2025 at 2:58 PM Heinz, Dominik >>> <dominik.heinz@h-da.de> wrote: >>> >>> I followed the steps in the guide you linked, - however, I still >>> have the issue. >>> >>> The uhd drivers are installed, and the niuspriorpc service is >>> running. However, I still the the RIO session initialization >>> failure. >>> >>> >>> Anything else I could try? I still don't understand what is the >>> cause for this. >>> >>> ------------------------------------------------------------------------ >>> *From:* Marcus D. Leech <patchvonbraun@gmail.com> >>> *Sent:* Tuesday, January 21, 2025 8:32:39 PM >>> *To:* usrp-users@lists.ettus.com >>> *Subject:* [EXTERN] [USRP-users] Re: X310 RIO Session >>> Initialization Failure (Error code -63150) >>> On 21/01/2025 09:26, Heinz, Dominik wrote: >>>> >>>> I'm experiencing an initialization issue with my Ettus X310 >>>> USRP device. >>>> >>>> My setup consists of an Ettus X310 connected through a PCIe >>>> Card using a Molex cable to my Linux machine. >>>> >>>> I'm running Ubuntu with kernel version 6.8.0-51-generic and >>>> have installed all the necessary UHD packages on the system. >>>> >>>> >>>> The X310 is properly detected when running |uhd_find_devices|, >>>> but attempting to probe the device with |uhd_usrp_probe| >>>> results in a RIO session initialization error. >>>> I attached the error output below. >>>> What is causing this RIO session initialization failure and how >>>> can it be resolved? >>>> >>>> gnb@xgoss-host:~/srsRAN_Project/build4ac5300/apps/gnb$ >>>> uhd_find_devices >>>> [INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; >>>> UHD_4.7.0.0-0ubuntu1~jammy1 >>>> -------------------------------------------------- >>>> -- UHD Device 0 >>>> -------------------------------------------------- >>>> Device Address: >>>>     serial: >>>>     fpga: HG >>>>     name: >>>>     product: X310 >>>>     resource: RIO0 >>>>     type: x300 >>>> >>>> gnb@xgoss-host:~/srsRAN_Project/build4ac5300/apps/gnb$ >>>> uhd_usrp_probe >>>> [INFO] [UHD] linux; GNU C++ version 11.4.0; Boost_107400; >>>> UHD_4.7.0.0-0ubuntu1~jammy1 >>>> [INFO] [X300] X300 initialization sequence... >>>> [INFO] [X300] Connecting to niusrpriorpc at localhost:5444... >>>> [INFO] [X300] Using LVBITX bitfile >>>> /usr/share/uhd/images/usrp_x310_fpga_HG.lvbitx >>>> Error: RuntimeError: x300_impl: Could not initialize RIO >>>> session. Unknown error. (Error code -63150) >>>> >>>> >>>> >>>> _______________________________________________ >>>> USRP-users mailing list --usrp-users@lists.ettus.com >>>> To unsubscribe send an email tousrp-users-leave@lists.ettus.com >>> The procedures for making this work are here: >>> >>> https://files.ettus.com/manual/page_usrp_x3x0.html#x3x0_hw_pcie >>> >>> >>> _______________________________________________ >>> USRP-users mailing list -- usrp-users@lists.ettus.com >>> To unsubscribe send an email to usrp-users-leave@lists.ettus.com >>> >> >