On 10/24/2019 08:38 PM, Karthik Vasudeva wrote:
I tried, did not work.
kvasude2@veneno:~$ uhd_usrp_probe --args
mgmt_addr=192.168.1.103,addr=192.168.10.2,type=n3xx
[INFO] [UHD] linux; GNU C++ version 7.4.0; Boost_106501;
UHD_3.14.1.HEAD-0-g0347a6d8
Error: LookupError: KeyError: No devices found for ----->
Device Address:
mgmt_addr: 192.168.1.103
addr: 192.168.10.2
type: n3xx
Karthik
OK, so, can you ping both of these addresses?
Is port UDP port 49152 port open on your host?
On Thu, Oct 24, 2019 at 7:26 PM Marcus D. Leech
<[email protected] <mailto:[email protected]>> wrote:
On 10/24/2019 03:44 PM, Karthik Vasudeva wrote:
I just tried with that address but still the same problem. Please
find the below error message
kvasude2@veneno:~$ uhd_usrp_probe --args
mgmt_addr=192.168.1.103,addr=192.168.10.2
[INFO] [UHD] linux; GNU C++ version 7.4.0; Boost_106501;
UHD_3.14.1.HEAD-0-g0347a6d8
Error: LookupError: KeyError: No devices found for ----->
Device Address:
mgmt_addr: 192.168.1.103
addr: 192.168.10.2
you'll also need to add:
type=n3xx
to the device args.
I am not sure whether my way of configuring the RJ45 port to
static is correct. Please provide pointers for the static
configuration of RJ45 port.
Karthik
On Thu, Oct 24, 2019 at 2:51 PM Marcus D Leech
<[email protected] <mailto:[email protected]>> wrote:
Use the 192.168.1.103 address
127.0.0.1 is the address that’s used when running on the
embedded platform within the N310.
Sent from my iPhone
On Oct 24, 2019, at 1:29 AM, Karthik Vasudeva
<[email protected] <mailto:[email protected]>> wrote:
Thank you for the pointer. I tried changing the network
configuration of the RJ45 port in the embedded system by
updating the eth0.network file as follows
[Match]
Name = eth0
[Network]
Address=192.168.1.103
[Link]
MTUBytes=1500
But still the uhd_find_devices shows the same mgmt_addr in
the embedded system as shown below
root@ni-n3xx-3198219:~# uhd_find_devices
[INFO] [UHD] linux; GNU C++ version 7.3.0; Boost_106600;
UHD_3.14.1.1-0-g0347a6d8
--------------------------------------------------
-- UHD Device 0
--------------------------------------------------
Device Address:
serial: 3198219
claimed: False
mgmt_addr: 127.0.0.1
product: n310
type: n3xx
Karthik
On Thu, Oct 24, 2019 at 12:04 AM Marcus D. Leech
<[email protected] <mailto:[email protected]>>
wrote:
On 10/24/2019 12:03 AM, Karthik Vasudeva wrote:
Thank you for the clarification. Actually, I am using
the RJ45 connection through a router and tried probuhd
udp ports opening along with mgmt_addr but still the
same problem. Please find the below error message
kvasude2@veneno:~$ uhd_usrp_probe --args
mgmt_addr=127.0.0.1,addr=192.168.10.2
[INFO] [UHD] linux; GNU C++ version 7.4.0;
Boost_106501; UHD_3.14.1.HEAD-0-g0347a6d8
Error: LookupError: KeyError: No devices found for ----->
Device Address:
mgmt_addr: 127.0.0.1
addr: 192.168.10.2
I used mgmt_addr shown below from the embedded system.
Please correct me if I am wrong.
127.0.0.1 is always your local host machine, so not
correct in this case.
If you read through the document I pointed you at,
you'll see that by default, that RJ45 connection uses
DHCP to get an address. The document
talks about changing that to a static address if you
need to.
root@ni-n3xx-3198219:~# uhd_find_devices
[INFO] [UHD] linux; GNU C++ version 7.3.0;
Boost_106600; UHD_3.14.1.1-0-g0347a6d8
--------------------------------------------------
-- UHD Device 0
--------------------------------------------------
Device Address:
serial: 3198219
claimed: False
mgmt_addr: 127.0.0.1
product: n310
type: n3xx
Karthik
On Wed, Oct 23, 2019 at 11:33 PM Marcus D. Leech
<[email protected]
<mailto:[email protected]>> wrote:
On 10/23/2019 11:00 PM, Karthik Vasudeva wrote:
I tried uhd_usrp_probe again but still the same
problem. Please find the below error message
kvasude2@veneno:~$ uhd_usrp_probe --args
addr=192.168.10.2
[INFO] [UHD] linux; GNU C++ version 7.4.0;
Boost_106501; UHD_3.14.1.HEAD-0-g0347a6d8
Error: LookupError: KeyError: No devices found for
----->
Device Address:
addr: 192.168.10.2
https://kb.ettus.com/USRP_N300/N310/N320/N321_Getting_Started_Guide#Connecting_the_Device
Also, find the below message from the embedded
system showing the IP of the SFP0 port for the
reference.
root@ni-n3xx-3198219:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc
noqueue qlen 1000
link/loopback 00:00:00:00:00:00 brd
00:00:00:00:00:00
inet 127.0.0.1/8 <http://127.0.0.1/8> scope
host lo
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu
1500 qdisc pfifo_fast qlen 1000
link/ether 00:80:2f:26:50:f8 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.102/24
<http://192.168.1.102/24> brd 192.168.1.255 scope
global dynamic eth0
valid_lft 86266sec preferred_lft 86266sec
3: *sfp0*: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu
8000 qdisc pfifo_fast qlen 1000
link/ether 00:80:2f:26:50:f9 brd ff:ff:ff:ff:ff:ff
*inet 192.168.10.2/24 <http://192.168.10.2/24>*
brd 192.168.10.255 scope global sfp0
valid_lft forever preferred_lft forever
4: sfp1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu
8000 qdisc pfifo_fast qlen 1000
link/ether 00:80:2f:26:50:fa brd ff:ff:ff:ff:ff:ff
Karthik
So, something you need to understand about the N310
device is that it has an RJ45 port that is used
both for "management and control"
traffic from UHD, and is also an SSH destination,
etc, etc.
The SFP ports are strictly for streaming, so you
need to use
"mgmt_addr=<the-addr-of-that-rj45>,addr=192.168.10.2"
in the device address,
and you need a connection for that RJ45 as well.
HOWEVER, if you're streaming at lower rates (those
that can be supported over the
RJ45), you can simply use that RJ45 connection,
and ignore the SFP connections.
More here:
https://kb.ettus.com/USRP_N300/N310/N320/N321_Getting_Started_Guide#Connecting_the_Device
_______________________________________________
USRP-users mailing list
[email protected]
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
