usrp-users@lists.ettus.com

Discussion and technical support related to USRP, UHD, RFNoC

View all threads

USRP N210 communication problems !?

JR
John Rohde
Tue, Feb 15, 2011 3:19 PM

I am having great difficulty with basic communication to/from my newly purchased USRP N210.
Any help greatly appreciated since this is rather frustrating - I had hoped to spent my time on debugging GNU RADIO py scripts at this time :(

I have downloaded and built the latest GNU RADIO software.

I have downloaded the latest UHD and done a build according to instructions.

The first step was to do a ping : I experience the same problem as reported by others : checksum failure cause ping to fail

Next step is to issue the command "uhd_find_devices". This results in the following:

Linux; GNU C++ version 4.4.5; Boost_104200; UHD_002.20110202043814.fa35192

Warning:
Ignoring discovered device
Expected protocol compatibility number 8, but got 7:
The firmware build is not compatible with the host code build.
No UHD Devices Found.

I tried to burn the firmware with the usrp_net_burner (./usrp_n2xx_net_burner.py --ip=192.168.10.2
--fw=/usr/share/uhd/images/usrp_n2xx_fw.bin). This results in :

USRP2P found.
Flash size:8388608
Sector size: 65536
Erasing 31744 bytes at 3145728
Writing image
Verifying data
Read back 16383 bytes
Success.

This looks ok, but then I try to burn the fpga image (./usrp_n2xx_net_burner.py --ip=192.168.10.2
--fpga=/usr/share/uhd/images/usrp_n210_fpga.bin). This results in:

USRP2P found.
Flash size: 8388608
Sector size 65536
Erasing 1572864 bytes at 1572864
timed out

What am I doing wrong here? Are there any further test, that I can carry out in order to pinpoint the cause(s) of the problem?

Regards,

John Rohde

I am having great difficulty with basic communication to/from my newly purchased USRP N210. Any help greatly appreciated since this is rather frustrating - I had hoped to spent my time on debugging GNU RADIO py scripts at this time :( I have downloaded and built the latest GNU RADIO software. I have downloaded the latest UHD and done a build according to instructions. The first step was to do a ping : I experience the same problem as reported by others : checksum failure cause ping to fail Next step is to issue the command "uhd_find_devices". This results in the following: ---------------------------------------------------------------------------------------------------------------------- Linux; GNU C++ version 4.4.5; Boost_104200; UHD_002.20110202043814.fa35192 Warning: Ignoring discovered device Expected protocol compatibility number 8, but got 7: The firmware build is not compatible with the host code build. No UHD Devices Found. ----------------------------------------------------------------------------------------------------------------------- I tried to burn the firmware with the usrp_net_burner (./usrp_n2xx_net_burner.py --ip=192.168.10.2 --fw=/usr/share/uhd/images/usrp_n2xx_fw.bin). This results in : ----------------------------------------------------------------------------------------------------------------------- USRP2P found. Flash size:8388608 Sector size: 65536 Erasing 31744 bytes at 3145728 Writing image Verifying data Read back 16383 bytes Success. ---------------------------------------------------------------------------------------------------------------------- This looks ok, but then I try to burn the fpga image (./usrp_n2xx_net_burner.py --ip=192.168.10.2 --fpga=/usr/share/uhd/images/usrp_n210_fpga.bin). This results in: ---------------------------------------------------------------------------------------------------------------------- USRP2P found. Flash size: 8388608 Sector size 65536 Erasing 1572864 bytes at 1572864 timed out --------------------------------------------------------------------------------------------------------------------- What am I doing wrong here? Are there any further test, that I can carry out in order to pinpoint the cause(s) of the problem? Regards, John Rohde
NF
Nick Foster
Tue, Feb 15, 2011 6:18 PM

On Tue, 2011-02-15 at 16:19 +0100, John Rohde wrote:

I am having great difficulty with basic communication to/from my newly
purchased USRP N210.
Any help greatly appreciated since this is rather frustrating - I had
hoped to spent my time on debugging GNU RADIO py scripts at this
time :(

I have downloaded and built the latest GNU RADIO software.

I have downloaded the latest UHD and done a build according to
instructions.

The first step was to do a ping : I experience the same problem as
reported by others : checksum failure cause ping to fail

Next step is to issue the command "uhd_find_devices". This results in
the following:

Linux; GNU C++ version 4.4.5; Boost_104200;
UHD_002.20110202043814.fa35192

Warning:
Ignoring discovered device
Expected protocol compatibility number 8, but got 7:
The firmware build is not compatible with the host code build.
No UHD Devices Found.

You've got the right course of action here -- the firmware/fpga need to
be updated.


I tried to burn the firmware with the usrp_net_burner
(./usrp_n2xx_net_burner.py --ip=192.168.10.2
--fw=/usr/share/uhd/images/usrp_n2xx_fw.bin). This results in :

USRP2P found.
Flash size:8388608
Sector size: 65536
Erasing 31744 bytes at 3145728
Writing image
Verifying data
Read back 16383 bytes
Success.

This looks ok, but then I try to burn the fpga image
(./usrp_n2xx_net_burner.py --ip=192.168.10.2
--fpga=/usr/share/uhd/images/usrp_n210_fpga.bin). This results in:

USRP2P found.
Flash size: 8388608
Sector size 65536
Erasing 1572864 bytes at 1572864
timed out

What am I doing wrong here? Are there any further test, that I can
carry out in order to pinpoint the cause(s) of the problem?

That's a very interesting problem, thank you for the detailed report.
Are you updating the firmware through a switch, or on a public network?
Does the update always fail exactly at this point? If you type "ifconfig
eth0" (or eth1... whichever card your N210 is connected to), does it
show errors, dropped packets, frame errors, or overruns? When the
updater says "Erasing 1572864 bytes at 1572864" but before it times out,
is the orange Ethernet LED on the N210 solidly on?

If you have another PC you can try the update from, that would be a very
helpful data point as well.

Thanks and sorry for the update trouble,
Nick

On Tue, 2011-02-15 at 16:19 +0100, John Rohde wrote: > I am having great difficulty with basic communication to/from my newly > purchased USRP N210. > Any help greatly appreciated since this is rather frustrating - I had > hoped to spent my time on debugging GNU RADIO py scripts at this > time :( > > I have downloaded and built the latest GNU RADIO software. > > I have downloaded the latest UHD and done a build according to > instructions. > > The first step was to do a ping : I experience the same problem as > reported by others : checksum failure cause ping to fail > > Next step is to issue the command "uhd_find_devices". This results in > the following: > ---------------------------------------------------------------------------------------------------------------------- > Linux; GNU C++ version 4.4.5; Boost_104200; > UHD_002.20110202043814.fa35192 > > > Warning: > Ignoring discovered device > Expected protocol compatibility number 8, but got 7: > The firmware build is not compatible with the host code build. > No UHD Devices Found. You've got the right course of action here -- the firmware/fpga need to be updated. > ----------------------------------------------------------------------------------------------------------------------- > > I tried to burn the firmware with the usrp_net_burner > (./usrp_n2xx_net_burner.py --ip=192.168.10.2 > --fw=/usr/share/uhd/images/usrp_n2xx_fw.bin). This results in : > ----------------------------------------------------------------------------------------------------------------------- > USRP2P found. > Flash size:8388608 > Sector size: 65536 > Erasing 31744 bytes at 3145728 > Writing image > Verifying data > Read back 16383 bytes > Success. > ---------------------------------------------------------------------------------------------------------------------- > > This looks ok, but then I try to burn the fpga image > (./usrp_n2xx_net_burner.py --ip=192.168.10.2 > --fpga=/usr/share/uhd/images/usrp_n210_fpga.bin). This results in: > ---------------------------------------------------------------------------------------------------------------------- > USRP2P found. > Flash size: 8388608 > Sector size 65536 > Erasing 1572864 bytes at 1572864 > timed out > --------------------------------------------------------------------------------------------------------------------- > > What am I doing wrong here? Are there any further test, that I can > carry out in order to pinpoint the cause(s) of the problem? That's a very interesting problem, thank you for the detailed report. Are you updating the firmware through a switch, or on a public network? Does the update always fail exactly at this point? If you type "ifconfig eth0" (or eth1... whichever card your N210 is connected to), does it show errors, dropped packets, frame errors, or overruns? When the updater says "Erasing 1572864 bytes at 1572864" but before it times out, is the orange Ethernet LED on the N210 solidly on? If you have another PC you can try the update from, that would be a very helpful data point as well. Thanks and sorry for the update trouble, Nick > > Regards, > > John Rohde > > _______________________________________________ > USRP-users mailing list > USRP-users@lists.ettus.com > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
JR
John Rohde
Tue, Feb 15, 2011 7:36 PM

Hi Nick,

Thank you for the reply. Comments:

  1. I am updating with supplied cable attached directly between PC and USRP N210. I have tried inserting a Gbit switch, but results are identical.
  2. Update fails at exactly the same point every time I try this approach.
  3. ifconfig eth0 -> zero errors, dropped, overruns and frame -> everything looks ok.
  4. The orange LED is solidly "on" for some seconds and then turns off. Then, the time out occurs.
  5. Another PC: I will try to get hold of another PC and test this, but unfortunately, I will have to start from scratch (installing Ubuntu and work my way forward from there...)

Any ideas based on the info above?

Regards,

John

-----Original Message-----
From: Nick Foster [mailto:nick@ettus.com]
Sent: 15. februar 2011 19:18
To: John Rohde
Cc: usrp-users@lists.ettus.com
Subject: Re: [USRP-users] USRP N210 communication problems !?

On Tue, 2011-02-15 at 16:19 +0100, John Rohde wrote:

I am having great difficulty with basic communication to/from my newly
purchased USRP N210.
Any help greatly appreciated since this is rather frustrating - I had
hoped to spent my time on debugging GNU RADIO py scripts at this
time :(

I have downloaded and built the latest GNU RADIO software.

I have downloaded the latest UHD and done a build according to
instructions.

The first step was to do a ping : I experience the same problem as
reported by others : checksum failure cause ping to fail

Next step is to issue the command "uhd_find_devices". This results in
the following:

Linux; GNU C++ version 4.4.5; Boost_104200;
UHD_002.20110202043814.fa35192

Warning:
Ignoring discovered device
Expected protocol compatibility number 8, but got 7:
The firmware build is not compatible with the host code build.
No UHD Devices Found.

You've got the right course of action here -- the firmware/fpga need to
be updated.


I tried to burn the firmware with the usrp_net_burner
(./usrp_n2xx_net_burner.py --ip=192.168.10.2
--fw=/usr/share/uhd/images/usrp_n2xx_fw.bin). This results in :

USRP2P found.
Flash size:8388608
Sector size: 65536
Erasing 31744 bytes at 3145728
Writing image
Verifying data
Read back 16383 bytes
Success.

This looks ok, but then I try to burn the fpga image
(./usrp_n2xx_net_burner.py --ip=192.168.10.2
--fpga=/usr/share/uhd/images/usrp_n210_fpga.bin). This results in:

USRP2P found.
Flash size: 8388608
Sector size 65536
Erasing 1572864 bytes at 1572864
timed out

What am I doing wrong here? Are there any further test, that I can
carry out in order to pinpoint the cause(s) of the problem?

That's a very interesting problem, thank you for the detailed report.
Are you updating the firmware through a switch, or on a public network?
Does the update always fail exactly at this point? If you type "ifconfig
eth0" (or eth1... whichever card your N210 is connected to), does it
show errors, dropped packets, frame errors, or overruns? When the
updater says "Erasing 1572864 bytes at 1572864" but before it times out,
is the orange Ethernet LED on the N210 solidly on?

If you have another PC you can try the update from, that would be a very
helpful data point as well.

Thanks and sorry for the update trouble,
Nick

Hi Nick, Thank you for the reply. Comments: 1. I am updating with supplied cable attached directly between PC and USRP N210. I have tried inserting a Gbit switch, but results are identical. 2. Update fails at exactly the same point every time I try this approach. 3. ifconfig eth0 -> zero errors, dropped, overruns and frame -> everything looks ok. 4. The orange LED is solidly "on" for some seconds and then turns off. Then, the time out occurs. 5. Another PC: I will try to get hold of another PC and test this, but unfortunately, I will have to start from scratch (installing Ubuntu and work my way forward from there...) Any ideas based on the info above? Regards, John -----Original Message----- From: Nick Foster [mailto:nick@ettus.com] Sent: 15. februar 2011 19:18 To: John Rohde Cc: usrp-users@lists.ettus.com Subject: Re: [USRP-users] USRP N210 communication problems !? On Tue, 2011-02-15 at 16:19 +0100, John Rohde wrote: > I am having great difficulty with basic communication to/from my newly > purchased USRP N210. > Any help greatly appreciated since this is rather frustrating - I had > hoped to spent my time on debugging GNU RADIO py scripts at this > time :( > > I have downloaded and built the latest GNU RADIO software. > > I have downloaded the latest UHD and done a build according to > instructions. > > The first step was to do a ping : I experience the same problem as > reported by others : checksum failure cause ping to fail > > Next step is to issue the command "uhd_find_devices". This results in > the following: > ---------------------------------------------------------------------------------------------------------------------- > Linux; GNU C++ version 4.4.5; Boost_104200; > UHD_002.20110202043814.fa35192 > > > Warning: > Ignoring discovered device > Expected protocol compatibility number 8, but got 7: > The firmware build is not compatible with the host code build. > No UHD Devices Found. You've got the right course of action here -- the firmware/fpga need to be updated. > ----------------------------------------------------------------------------------------------------------------------- > > I tried to burn the firmware with the usrp_net_burner > (./usrp_n2xx_net_burner.py --ip=192.168.10.2 > --fw=/usr/share/uhd/images/usrp_n2xx_fw.bin). This results in : > ----------------------------------------------------------------------------------------------------------------------- > USRP2P found. > Flash size:8388608 > Sector size: 65536 > Erasing 31744 bytes at 3145728 > Writing image > Verifying data > Read back 16383 bytes > Success. > ---------------------------------------------------------------------------------------------------------------------- > > This looks ok, but then I try to burn the fpga image > (./usrp_n2xx_net_burner.py --ip=192.168.10.2 > --fpga=/usr/share/uhd/images/usrp_n210_fpga.bin). This results in: > ---------------------------------------------------------------------------------------------------------------------- > USRP2P found. > Flash size: 8388608 > Sector size 65536 > Erasing 1572864 bytes at 1572864 > timed out > --------------------------------------------------------------------------------------------------------------------- > > What am I doing wrong here? Are there any further test, that I can > carry out in order to pinpoint the cause(s) of the problem? That's a very interesting problem, thank you for the detailed report. Are you updating the firmware through a switch, or on a public network? Does the update always fail exactly at this point? If you type "ifconfig eth0" (or eth1... whichever card your N210 is connected to), does it show errors, dropped packets, frame errors, or overruns? When the updater says "Erasing 1572864 bytes at 1572864" but before it times out, is the orange Ethernet LED on the N210 solidly on? If you have another PC you can try the update from, that would be a very helpful data point as well. Thanks and sorry for the update trouble, Nick > > Regards, > > John Rohde > > _______________________________________________ > USRP-users mailing list > USRP-users@lists.ettus.com > http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com