Re: [USRP-users] Problems getting started with N310 (Could not find MAC address for IP address 192.168.20.1)
Hi Ettus Users, I wanted to friendly bump up this topic again. It’s really blocking me from working with the N310 if this error persists. I’m a bit lost with finding out why the MAC address of the network interfaces cannot be looked up, looked through the implementation of commit_xport, hover having zero python knowledge and not much in-depth networking knowledge I can’t really figure out what could be the source of the error. So, any pointers are greatly appreciated! Thanks again Janos > Am 01.03.2019 um 13:15 schrieb Janos Buttgereit via USRP-users > : > > Hi, > > I’m about to port an application that was working with a setup of two X300 > devices to a new N310 device. > > For a first step the N310 should simply be used to stream four RF channels to > a host. However before using it for streaming I wanted to perform some simple > operations like getting the device tree through the uhd_usrp_probe command, > which fails at the moment. I installed a current version of the SD card image > a few days ago and my host is running an UHD version compiled from the tip of > the UHD repo a few days ago. I suspect this is a network config error, > however I’m not sure and sadly I’m no networking expert. > > A brief overview of my setup: > A host PC, running Ubuntu equipped with a 2x10Gbit Ethernet card and two > usual Gbit Ethernernet cards. One 1Gbit ethernet port is used for internet > connection, the other one is connected to a Wifi Router, running a DHCP > server in the address space 192.167.1.x. The N310 is connected to this > router, the DHCP server assigns the address 192.167.1.100 to the N310. > Pinging the device works as well as establishing an SSH connection to it. The > two SFP ports are connected to the 10Gbit card of the host, on the host side > those ports have the IP address 192.168.10.1 and 192.168.20.1. I loaded an XG > FPGA image to use both SFP ports at 10Gbit speed and they respond to pings. > To summarize, this is the current network config as reported by the system: > > sdr@NTLabDSP:~$ ip addr > 1: lo: 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: enp4s0: mtu 1500 qdisc mq state UP group > default qlen 1000 > link/ether 00:0a:f7:81:d5:26 brd ff:ff:ff:ff:ff:ff > inet 192.167.1.102/24 brd 192.167.1.255 scope global dynamic enp4s0 >valid_lft 4745sec preferred_lft 4745sec > inet6 fe80::2ddf:29cd:ab15:aa68/64 scope link >valid_lft forever preferred_lft forever > 3: eno1: mtu 1500 qdisc pfifo_fast state UP > group default qlen 1000 > link/ether 98:90:96:c6:92:3c brd ff:ff:ff:ff:ff:ff > inet 10.211.21.102/23 brd 10.211.21.255 scope global dynamic eno1 >valid_lft 3812sec preferred_lft 3812sec > inet6 2a02:c6a0:3071:53fc:f1:1e14:9cf0:3521/128 scope global dynamic >valid_lft 904sec preferred_lft 604sec > inet6 fe80::58d:8415:1a20:604e/64 scope link >valid_lft forever preferred_lft forever > 4: enp5s0f0: mtu 8000 qdisc mq state UP > group default qlen 1000 > link/ether 00:1b:21:bc:19:96 brd ff:ff:ff:ff:ff:ff > inet 192.168.10.1/24 scope global enp5s0f0 >valid_lft forever preferred_lft forever > inet6 fe80::21b:21ff:febc:1996/64 scope link >valid_lft forever preferred_lft forever > 5: enp5s0f1: mtu 8000 qdisc mq state UP > group default qlen 1000 > link/ether 00:1b:21:bc:19:97 brd ff:ff:ff:ff:ff:ff > inet 192.168.20.1/24 scope global enp5s0f1 >valid_lft forever preferred_lft forever > inet6 fe80::21b:21ff:febc:1997/64 scope link >valid_lft forever preferred_lft forever > > This host setup used to work flawlessly with the two X300 units. > > Now when trying to run uhd_usrp_probe I think I got that I need to specify > all three addresses, the primary and secondary address of the SFP ports that > handle streaming as well as the management port address. So I pass those > three parameters as args to uhd_usrp_probe. However when doing so, I get the > error "Could not find MAC address for IP address 192.168.20.1“ which seems a > bit weird to me, as to my knowledge a MAC address is a hardware property of > the network interface and therefore cannot be misconfigured. So is this a > network configuration error or am I doing something different wrong? For the > sake of completeness, here is the complete output of uhd_usrp_probe: > > sdr@NTLabDSP:~$ uhd_usrp_probe > --args="addr=192.168.10.2,second_addr=192.168.20.2,mgmt_addr=192.167.1.100" > [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; > UHD_3.15.0.git-13-g52138314 > [INFO] [MPMD] Initializing 1 device(s) in parallel with args: > mgmt_addr=192.167.1.100,type=n3xx,product=n310,serial=316CD18,claimed=False,addr=192.168.10.2
[USRP-users] x310 brick no ethernet link after fpga burn - urgent
Hi I am using x310 and after upgrading 13.01 to 13.3.1 I have an urgent issue My FPGA burn was stoppend in the beginning and now it seems there is a brick No eth connection on either port Is there a golden image for the FPGA? And advice? Regards Regards, Ilay Nissim RT Embedded Team Leader Netline Communications Technologies Ltd Tel: + (972) 36068171 Fax: + (972) 36068101 http://www.netlinetech.com/ Azrieli Circular Tower , Menachem Begin 132, Tel-Aviv 67021, ISRAEL This email and the associated attachments may contain information that is proprietary, privileged, confidential or otherwise protected from disclosure. If you are not the intended recipient or otherwise have received this message in error, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you are not the intended recipient or otherwise have received this message in error, please notify me immediately, destroy any paper copies and delete all electronic files of the message. ___ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
Re: [USRP-users] Problems getting started with N310 (Could not find MAC address for IP address 192.168.20.1)
On 03/15/2019 06:49 AM, Janos Buttgereit via USRP-users wrote: Hi Ettus Users, I wanted to friendly bump up this topic again. It’s really blocking me from working with the N310 if this error persists. I’m a bit lost with finding out why the MAC address of the network interfaces cannot be looked up, looked through the implementation of commit_xport, hover having zero python knowledge and not much in-depth networking knowledge I can’t really figure out what could be the source of the error. So, any pointers are greatly appreciated! Thanks again Janos What happens if you just: uhd_usrp_probe or uhd_usrp_probe --args "addr=192.167.1.100" or uhd_usrp_probe --args "addr=192.168.10.2" Am 01.03.2019 um 13:15 schrieb Janos Buttgereit via USRP-users mailto:usrp-users@lists.ettus.com>>: Hi, I’m about to port an application that was working with a setup of two X300 devices to a new N310 device. For a first step the N310 should simply be used to stream four RF channels to a host. However before using it for streaming I wanted to perform some simple operations like getting the device tree through the uhd_usrp_probe command, which fails at the moment. I installed a current version of the SD card image a few days ago and my host is running an UHD version compiled from the tip of the UHD repo a few days ago. I suspect this is a network config error, however I’m not sure and sadly I’m no networking expert. A brief overview of my setup: A host PC, running Ubuntu equipped with a 2x10Gbit Ethernet card and two usual Gbit Ethernernet cards. One 1Gbit ethernet port is used for internet connection, the other one is connected to a Wifi Router, running a DHCP server in the address space 192.167.1.x. The N310 is connected to this router, the DHCP server assigns the address 192.167.1.100 to the N310. Pinging the device works as well as establishing an SSH connection to it. The two SFP ports are connected to the 10Gbit card of the host, on the host side those ports have the IP address 192.168.10.1 and 192.168.20.1. I loaded an XG FPGA image to use both SFP ports at 10Gbit speed and they respond to pings. To summarize, this is the current network config as reported by the system: sdr@NTLabDSP:~$ ip addr 1: lo: 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: enp4s0: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:0a:f7:81:d5:26 brd ff:ff:ff:ff:ff:ff inet 192.167.1.102/24 brd 192.167.1.255 scope global dynamic enp4s0 valid_lft 4745sec preferred_lft 4745sec inet6 fe80::2ddf:29cd:ab15:aa68/64 scope link valid_lft forever preferred_lft forever 3: eno1: mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 98:90:96:c6:92:3c brd ff:ff:ff:ff:ff:ff inet 10.211.21.102/23 brd 10.211.21.255 scope global dynamic eno1 valid_lft 3812sec preferred_lft 3812sec inet6 2a02:c6a0:3071:53fc:f1:1e14:9cf0:3521/128 scope global dynamic valid_lft 904sec preferred_lft 604sec inet6 fe80::58d:8415:1a20:604e/64 scope link valid_lft forever preferred_lft forever 4: enp5s0f0: mtu 8000 qdisc mq state UP group default qlen 1000 link/ether 00:1b:21:bc:19:96 brd ff:ff:ff:ff:ff:ff inet 192.168.10.1/24 scope global enp5s0f0 valid_lft forever preferred_lft forever inet6 fe80::21b:21ff:febc:1996/64 scope link valid_lft forever preferred_lft forever 5: enp5s0f1: mtu 8000 qdisc mq state UP group default qlen 1000 link/ether 00:1b:21:bc:19:97 brd ff:ff:ff:ff:ff:ff inet 192.168.20.1/24 scope global enp5s0f1 valid_lft forever preferred_lft forever inet6 fe80::21b:21ff:febc:1997/64 scope link valid_lft forever preferred_lft forever This host setup used to work flawlessly with the two X300 units. Now when trying to run uhd_usrp_probe I think I got that I need to specify all three addresses, the primary and secondary address of the SFP ports that handle streaming as well as the management port address. So I pass those three parameters as args to uhd_usrp_probe. However when doing so, I get the error "Could not find MAC address for IP address 192.168.20.1“ which seems a bit weird to me, as to my knowledge a MAC address is a hardware property of the network interface and therefore cannot be misconfigured. So is this a network configuration error or am I doing something different wrong? For the sake of completeness, here is the complete output of uhd_usrp_probe: sdr@NTLabDSP:~$ uhd_usrp_probe --args="addr=192.168.10.2,second_addr=192.168.20.2,mgmt_addr=192.167.1.100" [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.15.0.git-13-g52138314 [INFO] [MPMD] Initializing 1 device(s) in parallel with args: mgmt_addr=192.167.1.100,type=n3xx,product=n310,serial=316CD18,claimed=False,addr=192.168.10.2,second
Re: [USRP-users] x310 brick no ethernet link after fpga burn - urgent
Hi, Same happened to me once before. You need to follow this: https://kb.ettus.com/X300/X310_Device_Recovery Good luck. Regards, Xavier On Fri, 15 Mar 2019 at 12:57, Ilay Nissim via USRP-users < usrp-users@lists.ettus.com> wrote: > Hi > > I am using x310 and after upgrading 13.01 to 13.3.1 > > I have an urgent issue > > My FPGA burn was stoppend in the beginning and now it seems there is a > brick > > No eth connection on either port > > Is there a golden image for the FPGA? > > And advice? > > Regards > > > > Regards, > Ilay Nissim > RT Embedded Team Leader > > Netline Communications Technologies Ltd > Tel: + (972) 36068171 <+972%203-606-8161> > Fax: + (972) 36068101 <+972%203-606-8101> > http://www.netlinetech.com/ > Azrieli Circular Tower , Menachem Begin 132, Tel-Aviv 67021, ISRAEL > > > > This email and the associated attachments may contain information that is > proprietary, privileged, confidential or otherwise protected from > disclosure. If you are not the intended recipient or otherwise have > received this message in error, you are not authorized to read, print, > retain, copy or disseminate this message or any part of it. If you are not > the intended recipient or otherwise have received this message in error, > please notify me immediately, destroy any paper copies and delete all > electronic files of the message. > ___ > USRP-users mailing list > USRP-users@lists.ettus.com > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com > ___ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
Re: [USRP-users] Phase after Freq Hopping
W dniu 12.03.2019 o 17:49, Patscheider, Dominik via USRP-users pisze: > > Hello , > > > > For a Radar I´m transmitting and receiving with the USRP X310 samples > on different frequency steps. > > > > For instance, after 4 frames I´m coming back to the first center freq > and continue this a few times. Hope the following description helps… > > > > f3 |phase4| |…| > > f2 |phase3| |…| > > f1 |phase2| |phase6| … > > f0 |phase1| |phase5| > > t --> > > According to the freq adjust every frame starts with a new phase. > > Phase 1 ≠Phase 5 > > > > Is there any possibility to get the same phase after returning to the > same center freq? Phase 1=Phase 5, Phase 2 = Phase 6,… > > > > Hi Dominik, Can you describe what you want to achieve exactly? Probably you need to know phase relations because you want to do coherent processing of the signal. But from your description I don't know: -why on your ASCII art the signals transmitted on different frequencies seems to be overlapped? -which you part of it you want to process coherently? I also often use USRPs for radar transmissions. Issues with predicting initial phase difference of the received signal, in relation to digital waveform that is being transmitted, are much easier to overcome when you use timed commands to set the frequencies on Rx and Tx side synchronously (if you use UBX or SBX daughter-boards). Best Regards, Piotr Krysik ___ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
Re: [USRP-users] Phase drift issue of N310
On 03/14/2019 04:37 PM, Damon wrote: Hi Marcus, The UHD Version is v3.14.0.0-rc1. Best regards, Damon I don't see this issue at all, using v3.14.0.0-rc3 How are you measuring phase, what does you flow-graph look like? Have you increased the gain enough to assure that the inherent system noise is not dominating your phase measurements? Hi Ali, The daughterboards have their own clock generators, but they are not exactly 'independent'. At least they don't have to be, as they share the same reference clock. Look at the block diagram: https://kb.ettus.com/images/9/9d/USRP_N310_N300_DB_Schematic.pdf and "Ref Clock" block. I don't have N310 and I know that reality can be a bit far from expectations (i.e. look at my "What makes sense and what doesn't in the way carrier frequency is set for TwinRX currently?" post). But maybe the daughterboards can be configured to use that reference clock. Best Regards, Piotr Krysik The LMK clock generator uses the reference clock from the mainboard, so there should not be any mutual phase-jitter/drift issues. I can test this on my N310 in the coming day or two. What version of UHD is in use? ___ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
