uhd

For these reasons, we recommend that you use the SD card that was supplied with the USRP2.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

::

The list option has been implemented on Linux, Mac OS X, and Windows.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

::

Use this number to select the correct FPGA image for your device.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

::

To boot into the safe image, hold-down the safe-mode button while power-cycling the device.

Continue to hold-down the button until the front-panel LEDs blink and remain solid.

------------------------------------------------------------------------

Setup networking

------------------------------------------------------------------------

and will not work with a 10/100 Mbps interface.

However, a 10/100 Mbps interface can be connected indirectly

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Setup the host interface

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

The USRP2 communicates at the IP/UDP layer over the gigabit ethernet.

The default IP address of the USRP2 is **192.168.10.2**

address to enable communication.  An address of **192.168.10.1** and a subnet

mask of **255.255.255.0** is recommended.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Multiple devices per host

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

and the corresponding USRP2 device should be assigned an address in that subnet.

Example:

**Configuration for USRP2 device 0:**

**Configuration for USRP2 device 1:**

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Change the USRP2's IP address

* to set a known IP address into USRP2 (in case you forgot)

**Method 1:**

you must know the current address of the USRP2,

and the network must be setup properly as described above.

Run the following commands:

------------------------------------------------------------------------

When setting up a development machine for the first time,

you may have various difficulties communicating with the USRP device.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

RuntimeError: no control response

This is a common error that occurs when you have set the subnet of your network

interface to a different subnet than the network interface of the USRP.  For

example, if your network interface is set to 192.168.20.1, and the USRP is

will likely see a 'no control response' error message.

Fixing this is simple - just set the your host PC's IP address to the same

previous section of this documentation.

Firewall issues

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

When the IP address is not specified,

Many firewalls will block the replies to these broadcast packets.

then your firewall may be blocking replies to UDP broadcast packets.

or create a rule to allow all incoming packets with UDP source port 49152.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Ping the device

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

and that it is using the expected IP address.

::

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Monitor the serial output

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

The microcontroller prints useful information about IP addresses,

MAC addresses, control packets, fast-path settings, and bootloading.

Use a standard USB to 3.3v-level serial converter at 230400 baud.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Monitor the host network traffic

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

------------------------------------------------------------------------

Addressing the device

See the application notes on `device identification <./identification.html>`_.

Use this addressing scheme with the *single_usrp* interface.

::

* The order in which devices are indexed corresponds to the indexing of the transmit and receive channels.

* The key indexing provides the same granularity of device identification as in the single device case.

::

    addr0=192.168.10.2, addr1=192.168.20.2

Using the MIMO Cable

------------------------------------------------------------------------

The MIMO cable allows two USRP devices to share reference clocks,

This device will be referred to as the slave, and the other device, the master.

* The slave device acquires the clock and time references from the master device.

* The master and slave may be used individually or in a multi-device configuration.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Shared ethernet mode

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

* Clock reference, time reference, and data are communicated over the MIMO cable.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Dual ethernet mode

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

* Only clock reference and time reference are communicated over the MIMO cable.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Configuring the slave

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Ref Clock - 10MHz

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

* **USRP2** 5 to 15dBm

* **N2XX** 0 to 15dBm

The following sensors are available for the USRP2/N-Series motherboards;

they can be queried through the API.

* other sensors are added when the GPSDO is enabled

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^