usrp-users@lists.ettus.com
Discussion and technical support related to USRP, UHD, RFNoC
View all threadsN310 streaming documentation
Tried that but it's not working for either on-board or SFP0, though I can ping both :
uhd_find_devices --args "addr=192.168.1.4,type=n3xx"
[INFO] [UHD] linux; GNU C++ version 8.1.1 20180502 (Red Hat 8.1.1-1); Boost_106600; UHD_3.11.1.0-0-g34c56104
No UHD Devices Found
uhd_find_devices --args "addr=192.168.10.2,type=n3xx"
[INFO] [UHD] linux; GNU C++ version 8.1.1 20180502 (Red Hat 8.1.1-1); Boost_106600; UHD_3.11.1.0-0-g34c56104
No UHD Devices Found
The N310 Ethernet looks OK:
root@ni-n3xx-3145FA0:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:80:2F:18:AF:BD
inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:171 errors:0 dropped:0 overruns:0 frame:0
TX packets:84 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:17223 (16.8 KiB) TX bytes:7577 (7.3 KiB)
Interrupt:145 Base address:0xb000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:86 errors:0 dropped:0 overruns:0 frame:0
TX packets:86 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6542 (6.3 KiB) TX bytes:6542 (6.3 KiB)
sfp0 Link encap:Ethernet HWaddr 00:80:2F:18:AF:BE
inet addr:192.168.10.2 Bcast:192.168.10.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:8000 Metric:1
RX packets:471 errors:0 dropped:22 overruns:0 frame:0
TX packets:454 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:59389 (57.9 KiB) TX bytes:52721 (51.4 KiB)
sfp1 Link encap:Ethernet HWaddr 00:80:2F:18:AF:BF
UP BROADCAST MULTICAST MTU:8000 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
It can find itself on 127.0.0.1
root@ni-n3xx-3145FA0:~# uhd_find_devices
[INFO] [UHD] linux; GNU C++ version 7.2.0; Boost_106400; UHD_3.11.0.1-0-unknown
-- UHD Device 0
Device Address:
serial: 3145FA0
claimed: False
mgmt_addr: 127.0.0.1
product: n310
type: n3xx
But can't find itself on 192.168.10.2:
root@ni-n3xx-3145FA0:~# uhd_find_devices --args "addr=192.168.10.2,type=n3xx"
[INFO] [UHD] linux; GNU C++ version 7.2.0; Boost_106400; UHD_3.11.0.1-0-unknown
No UHD Devices Found
Like on the E310, do I need to start something?
Could it be UHD_3.11.0.1 on the N310 image and UHD_3.11.1.0 on my PC?
Thanks,
Lou
On 05/11/2018 06:14 PM, Brent Stapleton wrote:
The type should be n3xx, not n300.
--args "addr=192.168.10.2,type=n3xx"
Brent
Ah. That's a change from N2xx and B2xx series. Might I suggest putting
in synonyms, so that folks used to previous naming schemes won't become
confused?
On Fri, May 11, 2018 at 3:06 PM, Marcus D. Leech via USRP-users <
usrp-users at lists.ettus.com> wrote:
On 05/11/2018 05:57 PM, Louis Brown via USRP-users wrote:
Is there documentation on getting the N310 streaming interface working?
I'm able to ping the SFP0 port at 192.168.10.2 and the on-board at
192.168.1.4, but uhd_find_devices and uhd_usrp_probe find nothing:
uhd_usrp_probe --args "addr=192.168.10.2"
[INFO] [UHD] linux; GNU C++ version 8.1.1 20180502 (Red Hat 8.1.1-1);
Boost_106600; UHD_3.11.1.0-0-g34c56104
Error: LookupError: KeyError: No devices found for ----->
Device Address:
addr: 192.168.10.2
I did update the SD card image with:
The ASCII art spectrum test works fine, so the hardware seems to be
working.
Thanks,
Lou
COuld you try adding "type=n300" to your --args ??
--args "addr=192.168.10.2,type=n300"
USRP-users mailing list
USRP-users at lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
USRP-users mailing list
USRP-users at lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
Louis,
you don't need to start something, but I'm wondering if MPM is maybe
crashing (it's the service that turns the device into a smart USRP).
Can you try ssh'ing in and running
$ ps | grep usrp
You should see something like this:
root@ni-n3xx-*******:~# ps | grep usrp
1422 root 26492 S python3 /usr/bin/usrp_hwd.py -v
1423 root 58448 S python3 /usr/bin/usrp_hwd.py -v
1424 root 27576 S python3 /usr/bin/usrp_hwd.py -v
1546 root 2732 R grep usrp
If you don't, MPM is not running. You can simply run
$ usrp_hwd.py [-v]
to manually spawn it. However, that's normally not necessary. The
filesystem will auto-launch it and even run a watchdog to make sure it
stays alive.
The only other thing, but it's a long shot, is to check your MTU sizes,
and verify that you're using an HG image if you're using 1GigE (or an XG
image when using 10GigE). You can also run
$ ethtool -p sfp1
on your device to make sure you're using the correct SFP, but that
shouldn't be the issue since you're pinging.
-- M
On 05/14/2018 08:28 AM, Louis Brown via USRP-users wrote:
Tried that but it's not working for either on-board or SFP0, though I can ping both :
uhd_find_devices --args "addr=192.168.1.4,type=n3xx"
[INFO] [UHD] linux; GNU C++ version 8.1.1 20180502 (Red Hat 8.1.1-1); Boost_106600; UHD_3.11.1.0-0-g34c56104
No UHD Devices Found
uhd_find_devices --args "addr=192.168.10.2,type=n3xx"
[INFO] [UHD] linux; GNU C++ version 8.1.1 20180502 (Red Hat 8.1.1-1); Boost_106600; UHD_3.11.1.0-0-g34c56104
No UHD Devices Found
The N310 Ethernet looks OK:
root@ni-n3xx-3145FA0:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:80:2F:18:AF:BD
inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:171 errors:0 dropped:0 overruns:0 frame:0
TX packets:84 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:17223 (16.8 KiB) TX bytes:7577 (7.3 KiB)
Interrupt:145 Base address:0xb000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:86 errors:0 dropped:0 overruns:0 frame:0
TX packets:86 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6542 (6.3 KiB) TX bytes:6542 (6.3 KiB)
sfp0 Link encap:Ethernet HWaddr 00:80:2F:18:AF:BE
inet addr:192.168.10.2 Bcast:192.168.10.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:8000 Metric:1
RX packets:471 errors:0 dropped:22 overruns:0 frame:0
TX packets:454 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:59389 (57.9 KiB) TX bytes:52721 (51.4 KiB)
sfp1 Link encap:Ethernet HWaddr 00:80:2F:18:AF:BF
UP BROADCAST MULTICAST MTU:8000 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
It can find itself on 127.0.0.1
root@ni-n3xx-3145FA0:~# uhd_find_devices
[INFO] [UHD] linux; GNU C++ version 7.2.0; Boost_106400; UHD_3.11.0.1-0-unknown
-- UHD Device 0
Device Address:
serial: 3145FA0
claimed: False
mgmt_addr: 127.0.0.1
product: n310
type: n3xx
But can't find itself on 192.168.10.2:
root@ni-n3xx-3145FA0:~# uhd_find_devices --args "addr=192.168.10.2,type=n3xx"
[INFO] [UHD] linux; GNU C++ version 7.2.0; Boost_106400; UHD_3.11.0.1-0-unknown
No UHD Devices Found
Like on the E310, do I need to start something?
Could it be UHD_3.11.0.1 on the N310 image and UHD_3.11.1.0 on my PC?
Thanks,
Lou
/On 05/11/2018 06:14 PM, Brent Stapleton wrote: />//>/The type should be n3xx, not n300. />//>/--args "addr=192.168.10.2,type=n3xx" />//>/Brent />//>/Ah. That's a change from N2xx and B2xx series. Might I suggest putting />/in synonyms, so that folks used to previous naming schemes won't become />/confused? />//>//>//>/On Fri, May 11, 2018 at 3:06 PM, Marcus D. Leech via USRP-users < />/usrp-users at lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com>
wrote: />//>>/On 05/11/2018 05:57 PM, Louis Brown via USRP-users wrote: />>//>>>//>>>/Is there documentation on getting the N310 streaming interface working? />>>/I'm able to ping the SFP0 port at 192.168.10.2 and the on-board at />>>/192.168.1.4, but uhd_find_devices and uhd_usrp_probe find nothing: />>>//>>>/uhd_usrp_probe --args "addr=192.168.10.2" />>>/[INFO] [UHD] linux; GNU C++ version 8.1.1 20180502 (Red Hat 8.1.1-1); />>>/Boost_106600; UHD_3.11.1.0-0-g34c56104 />>>/Error: LookupError: KeyError: No devices found for -----> />>>/Device Address: />>>/addr: 192.168.10.2 />>>//>>>/I did update the SD card image with: />>>//>>>//>>>/http://files.ettus.com/binaries/cache/n3xx/meta-ettus-v3.11.0.1-20180419/n3xx_common_sdimg_default-v3.11.0.1-20180419.zip
/>>>//>>>//>>>/The ASCII art spectrum test works fine, so the hardware seems to be />>>/working. />>>//>>>/Thanks, />>>/Lou />>>//>>>/COuld you try adding "type=n300" to your --args ?? />>//>>/--args "addr=192.168.10.2,type=n300" />>//>>//>>//>>/_______________________________________________ />>/USRP-users mailing list />>/USRP-users at lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com />>/http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com />>//>//>//>/_______________________________________________ />/USRP-users mailing list />/USRP-users at lists.ettus.com
http://lists.ettus.com/mailman/listinfo/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