Difference between revisions of "Ettus USRP E300 Embedded Family Hardware Resources"

Revision as of 14:56, 27 April 2017

Device Overview

The USRP E31x offers a portable stand-alone SDR platform designed for field deployment. The flexible 2x2 MIMO AD9361 transceiver from Analog Devices provides up to 56 MHz of instantaneous bandwidth and spans frequencies from 70 MHz – 6 GHz to cover multiple bands of interest.

Key Features

E310

Xilinx Zynq 7020 SoC: 7 Series FPGA with ARM Cortex A9 667 MHz (SG1) or 866 MHz (SG3) dual-core processor Analog Devices AD9361 RFIC direct-conversion transceiver Frequency range: 70 MHz - 6 GHz Up to 56 MHz of instantaneous bandwidth 2x2 MIMO transceiver Up to 10 MS/s sample data transfer rate to ARM processor RX, TX filter banks Integrated GPS receiver 9-axis inertial measurement unit RF Network on Chip (RFNoC™) FPGA development framework support

E312

Battery Operated Xilinx Zynq 7020 SoC: 7 Series FPGA with ARM Cortex A9 866 MHz dual-core processor

E313

Rugged and weatherproof for outdoor deployment Fully assembled IP67-rated enclosure with USRP E310 inside Extensive environmental testing Power over Ethernet (PoE) with surge and lightning protection Xilinx Zynq 7020 SoC: 7 Series FPGA with ARM Cortex A9 866 MHz dual-core processor

Daughterboard Specifications

E31x MIMO XCVR board

The USRP E31x MIMO XCVR daughterboard features an integrated MIMO capable RF frontend.

Tuning

The RF frontend has individually tunable receive and transmit chains. Both transmit and receive can be used in a MIMO configuration. For the MIMO case, both receive frontends share the RX LO, and both transmit frontends share the TX LO. Each LO is tunable between 50 MHz and 6 GHz.

Gains

All frontends have individual analog gain controls. The receive frontends have 76 dB of available gain; and the transmit frontends have 89.5 dB of available gain. Gain settings are application specific, but it is recommended that users consider using at least half of the available gain to get reasonable dynamic range.

LO lock status

The frontends provide a lo-locked sensor that can be queried through the UHD API.

// assumes 'usrp' is a valid uhd::usrp::multi_usrp::sptr instance
// get status for rx frontend
usrp->get_rx_sensor("lo-locked");
// get status for tx frontend
usrp->get_tx_sensor("lo-locked");

Filter and Antenna Switches

The transmit and receive filter banks uses switches to select between the available filters. These paths are also dependent on the antenna switch settings. Incorrectly setting the switches generally results in attenuated input / output power. Receive filters are band pass (series high & low pass filters), transmit filters are low pass.

Source code related to controlling the filter band and antenna switches resides in e300_impl.c. Specifically, refer to methods e300_impl::_update_bandsel, e300_impl::_update_atrs, e300_impl::_update_gpio, and e300_impl::_update_enables. Generally, these methods set the switches depending on the state of transmit and receive streams.

The following sections provide switch setting tables for antenna and filter selection for frontends A & B receive and transmit paths. For futher details refer to the schematics.

Side A Filter and Antenna Switches

Note: X = don't care, T = If full duplex, set bits according to transmit table, otherwise don't care. Filter range A – B will be selected if A <= freq < B.

Receive

Transmit

Note: Although the transmit filters are low pass, this table describes UHD's tuning range for selecting each filter path. The table also includes the required transmit enable state.

Side B Filter and Antenna Switches

Note: X = don't care, T = If full duplex, set bits according to transmit table, otherwise don't care. Filter range A – B will be selected if A <= freq < B.

Receive

Transmit

Note: Although the transmit filters are low pass, the following table describes UHD's tuning range for selecting each filter path. The table also includes the required transmit enable states.

RF Specifications

RF Performance

• SSB/LO Suppression -35/50 dBc
• Phase Noise 3.5 GHz 1.0 deg RMS
• Phase Noise 6 GHz 1.5 deg RMS
• Power Output >10dBm
• IIP3 (@ typ NF) -20dBm
• Typical Noise Figure <8dB

Hardware Specifications

• Ettus Research recommends to always use the latest stable version of UHD

E310

• Current Hardware Revision: 1
• Minimum version of UHD required: 3.8.0
• Required version on the host computer must match what is running on the E310

E312

• Current Hardware Revision: 1
• Minimum version of UHD required: 3.8.5
• Required version on the host computer must match what is running on the E312

E313

• Current Hardware Revision: 1
• Minimum version of UHD required: 3.8.0
• Required version on the host computer must match what is running on the E313

Physical Specifications

Dimensions

E310

• 133 x 68 x 26.4 mm

E312

• 133 x 68.2 x 31.8 mm

E313

• 186 x 280 x 106 mm

Battery Specifications (E312 Only)

Battery Specifications: File:E312 Battery Spec Sheet 20170426.pdf

Environmental Specifications

Operating Temperature Range

• E310 0-40 °C
• E312 0-40 °C
• E313 -40-71 °C

Operating Humidity Range

• 10% to 90% non-condensing

Schematics

E310

E310 Schematics

E310 DB

E310 Architecture

Key Component Datasheets

Request a detailed whitepaper covering features and components from info@ettus.com

Mechanical Information

Weight

E310

• 375 g

E312

• 446 g

E313

• 1.8 kg

Drawings

E310

• File:E310 Dimensional Sketches.pdf
• File:cu e310 motherboard cca.pdf
• File:cu E310 daughtercard cca.pdf
• File:cu usrp-e310.pdf

E312

• File:cu e312 motherboard cca.pdf
• File:cu e312 daughtercard cca.pdf
• File:cu ettus-e312.pdf

E313

• File:USRP E313 Dimension Pole Mount.pdf
• File:USRP E313 Dimension Surface Mount.pdf
• File:USRP E313 Mounting Accessory Assembly Guide.pdf
• Media:USRP E313 USB conduit interface.png

FPGA

• Utilization statistics are subject to change between UHD releases. This information is current as of UHD 3.9.4 and was taken directly from Xilinx Vivado 2014.4.

E310/E312/E313

1. Slice Logic
--------------

+----------------------------+-------+-----------+-------+
|          Site Type         |  Used | Available | Util% |
+----------------------------+-------+-----------+-------+
| Slice LUTs                 | 36203 |     53200 | 68.05 |
|   LUT as Logic             | 28108 |     53200 | 52.83 |
|   LUT as Memory            |  8095 |     17400 | 46.52 |
|     LUT as Distributed RAM |   870 |           |       |
|     LUT as Shift Register  |  7225 |           |       |
| Slice Registers            | 36562 |    106400 | 34.36 |
|   Register as Flip Flop    | 36562 |    106400 | 34.36 |
|   Register as Latch        |     0 |    106400 |  0.00 |
| F7 Muxes                   |   376 |     26600 |  1.41 |
| F8 Muxes                   |   125 |     13300 |  0.93 |
+----------------------------+-------+-----------+-------+

3. Memory
---------

+-------------------+------+-----------+-------+
|     Site Type     | Used | Available | Util% |
+-------------------+------+-----------+-------+
| Block RAM Tile    |   97 |       140 | 69.28 |
|   RAMB36/FIFO*    |   90 |       140 | 64.28 |
|     RAMB36E1 only |   90 |           |       |
|   RAMB18          |   14 |       280 |  5.00 |
|     RAMB18E1 only |   14 |           |       |
+-------------------+------+-----------+-------+
* Note: Each Block RAM Tile only has one FIFO logic available and therefore can accommodate only one FIFO36E1 or one FIFO18E1. However, if a FIFO18E1 occupies a Block RAM Tile, that tile can still accommodate a RAMB18E1


4. DSP
------

+----------------+------+-----------+-------+
|    Site Type   | Used | Available | Util% |
+----------------+------+-----------+-------+
| DSPs           |  120 |       220 | 54.54 |
|   DSP48E1 only |  120 |           |       |
+----------------+------+-----------+-------+

Interfaces and Connectivity

• 10/100/1000 BASE-T Ethernet
• Stereo audio out, mono mic in
• Integrated GPS receiver
• Host USB support
• 9-axis IMU

Front Panel

RF A Group TX/RX LED: Indicates that data is streaming on the TX/RX channel on frontend side A RX2 LED: Indicates that data is streaming on the RX2 channel on frontend side A RF B Group TX/RX LED: Indicates that data is streaming on the TX/RX channel on frontend B RX2 LED: Indicates that data is streaming on the RX2 channel on frontend B PWR: Power switch with integrated status LED, for status description see below. SYNC: Input port for external PPS signal GPS: Connection for the GPS antenna AUDIO: Audio input / output The status LED in the power switch indicates the power and charge status. It's behavior is firmware version dependent. Version 1 (original E310) Off: Indicates device is off and not charging Solid Red: Indicates device is charging Solid Green: Indicates device is on Fast Blinking Red: Indicates an error code 1 - Low voltage error 2 - Regulator low voltage error 3 - FPGA power error 4 - DRAM power error 5 - 1.8V rail power error 6 - 3.3V rail power error 7 - Daughterboard / TX power error 9 - Temperature error Version 2 (E312 and upgraded E310) Off: Indicates device is off and not charging Slow Blinking Green: Indicates device is off and charging Fast Blinking Green: Indicates device is on and charging Solid Green: Indicates device is on (and not charging, if E312) Solid Orange: Indicates device is on and discharging Fast Blinking Orange: Indicates device is on, discharging, and charge is below 10% charge Fast Blinking Red: Indicates an error code 1 - Low voltage error 2 - Regulator low voltage error 3 - FPGA power error 4 - DRAM power error 5 - 1.8V rail power error 6 - 3.3V rail power error 7 - Daughterboard / TX power error 8 - Charger error 9 - Charger temperature error 10 - Battery low error 11 - Fuel Gauge temperature error 12 - Global (case) temperature error

Rear Panel

PWR: Locking connector (Kycon KLDHCX-0202-A-LT) for the USRP-E Series power supply 1G ETH: RJ45 port for Ethernet interfaces USB: USB 2.0 Port SERIAL: Micro USB connection for serial uart console

GPIO

Pin Mapping Pin 1: +3.3V Pin 2: Reserved Pin 3: Data[5] Pin 4: Reserved Pin 5: Data[4] Pin 6: Data[0] Pin 7: Data[3] Pin 8: Data[1] Pin 9: 0V Pin 10: Data[2]

Power on state

The hardware power on state and UHD initial state for the front-panel GPIOs is high-Z. For the E3xx, there are no external pull-ups/pull-downs for the GPIO pins, but the FPGAs do have them and they are configured as follows: E3xx: pull-down.

• Please see the E3x0/X3x0 GPIO API for information on configuring and using the GPIO bus.

Audio

The E3x0 2.5 mm Audio Jack TRRS pins are assigned as follows: Tip=Mic, Ring1=Right, Ring2=Left, Sleeve=GND. The Left/Right audio outputs are compatible with typical low-impedance headphones (16 to 32 Ohms). The Microphone pin provides approximately 2 mA bias at 2.2 V when not suspended. A variety of pin configurations can be found on commonly available headsets, so an adapter may be required.

Certifications

RoHS

As of December 1st, 2010 all Ettus Research products are RoHS compliant unless otherwise noted. More information can be found at http://ettus.com/legal/rohs-information

China RoHS

Management Methods for Controlling Pollution Caused by Electronic Information Products Regulation

Chinese Customers

National Instruments is in compliance with the Chinese policy on the Restriction of Hazardous Substances (RoHS) used in Electronic Information Products. For more information about the National Instruments China RoHS compliance, visit ni.com/environment/rohs_china.

Certificate of Volatility

E310

• Media:volatility USRP E310 r1.pdf

E312

• Media:USRP E31x CoV.pdf

SD Card Images

• http://files.ettus.com/e3xx_images/

This folder linked above contains SD card images and the SDK (OE cross-compiler build environment) for the USRP E31x. There is a manifest file that shows which packages, and which versions, are included in the OE build within each folder.

The "alpha", "beta", "e3xx-release-001", "e310-release-002", "e3xx-release-3" folders contain older versions which are currently obsolete. We do not suggest that customers use these files. These versions are no longer supported. They are provided here for archival purposes only.

The current version is Release 4, which located in the "e3xx-release-4" folder. We recommend the customers use this version. It is fine if you are already successfully using an older version, but at some point it is recommended that you upgrade to this current version so that you benefit from the latest bug fixes, new features, stability improvements, and other enhancements.

The Release 4 image includes UHD 3.9.2 and GNU Radio 3.7.9, and also includes the corresponding FPGA image file.

Note: An 8 GB SD card is required for the Release 4 image.

The SD card image contains both the FPGA image and the OS for the E31x. The FPGA images are located in the file system of the E31x in the /usr/local/share/uhd/images folder.

There are two SD card image files for each version of the image, which include the text "-dev" and "-demo" in the filename. The "-dev" flavor lacks some graphical packages, such as X Windows and QT, which the "-demo" flavor includes. The two flavors are otherwise functionally equivalent, although the "-demo" flavor takes some additional space on the SD card and some additional memory to run.

The Release 4 image comes in two varieties. The variety that you will need depends on the product number of your E31x, which is printed on the bottom of the device.

For the E310, the product number will be 156333X-01L, where X is a letter from A to Z. For devices where X is A, B, C, D, the images under the "ettus-e3xx-sg1" folder should be used. For devices where X is E or later, the images under the "ettus-e3xx-sg3" folder should be used. You must use the appropriate image for your specific device. The incorrect image will not work, and will only boot as far as the U-Boot boot loader before stopping.

For the E312, the product number will be 140605X-01L, where X is a letter from A to Z. The images under the "ettus-e3xx-sg3" folder should be used for all E312 devices.

You can burn the image to an SD card using either the "dd" or the "bmaptool" tool. Instructions on how to use these tools are at the links below.

• http://files.ettus.com/manual/page_usrp_e3x0.html#e3x0_upgrade_sd_card

• https://gnuradio.org/redmine/projects/gnuradio/wiki/Copy_an_image_file_to_the_SD_card

The SD image files have an *.xz extension, as they are compressed using the LZMA/LZMA2 compression algorithms. You can uncompress these files with tools such as 7-Zip and the XZ Utils. Please see the links below for further information.

7-Zip

• http://www.7-zip.org/
• https://en.wikipedia.org/wiki/7-Zip

XZ Utils

• http://tukaani.org/xz/
• https://en.wikipedia.org/wiki/XZ_Utils

The folder structure is listed below.

.
|-- alpha
|   |-- dizzy-test
|   |   |-- oecore-x86_64-armv7ahf-vfp-neon-toolchain-nodistro.0.manifest
|   |   |-- oecore-x86_64-armv7ahf-vfp-neon-toolchain-nodistro.0.sh
|   |   |-- sdimage-gnuradio-demo.direct.xz
|   |   `-- sdimage-gnuradio-dev.direct.xz
|   |-- fido-rfnoc-test
|   |   |-- oecore-x86_64-armv7ahf-vfp-neon-toolchain-nodistro.0.manifest
|   |   |-- oecore-x86_64-armv7ahf-vfp-neon-toolchain-nodistro.0.sh
|   |   |-- sdimage-gnuradio-demo.direct.xz
|   |   |-- sdimage-gnuradio-demo.direct.xz.md5
|   |   |-- sdimage-gnuradio-dev.direct.xz
|   |   `-- sdimage-gnuradio-dev.direct.xz.md5
|   |-- fido-test
|   |   |-- ettus-e3xx-sg1
|   |   |   |-- sdimage-gnuradio-demo.direct.xz
|   |   |   |-- sdimage-gnuradio-demo.direct.xz.md5
|   |   |   |-- sdimage-gnuradio-dev.direct.xz
|   |   |   `-- sdimage-gnuradio-dev.direct.xz.md5
|   |   |-- ettus-e3xx-sg3
|   |   |   |-- sdimage-gnuradio-demo.direct.xz
|   |   |   |-- sdimage-gnuradio-demo.direct.xz.md5
|   |   |   |-- sdimage-gnuradio-dev.direct.xz
|   |   |   `-- sdimage-gnuradio-dev.direct.xz.md5
|   |   |-- oecore-x86_64-armv7ahf-vfp-neon-toolchain-nodistro.0.manifest
|   |   `-- oecore-x86_64-armv7ahf-vfp-neon-toolchain-nodistro.0.sh
|   `-- fosphor-testing
|       |-- fosphor.direct.xz
|       |-- oecore-x86_64-armv7ahf-vfp-neon-toolchain-nodistro.0.host.manifest
|       |-- oecore-x86_64-armv7ahf-vfp-neon-toolchain-nodistro.0.sh
|       |-- oecore-x86_64-armv7ahf-vfp-neon-toolchain-nodistro.0.target.manifest
|       |-- sdimage-gnuradio-demo.direct.xz
|       |-- sdimage-gnuradio-demo.direct.xz.md5
|       |-- sdimage-gnuradio-dev.direct.xz
|       `-- sdimage-gnuradio-dev.direct.xz.md5
|-- beta
|   |-- dizzy-test
|   |   |-- oecore-x86_64-armv7ahf-vfp-neon-toolchain-nodistro.0.manifest
|   |   |-- oecore-x86_64-armv7ahf-vfp-neon-toolchain-nodistro.0.sh
|   |   |-- sdimage-gnuradio-demo.direct.xz
|   |   `-- sdimage-gnuradio-dev.direct.xz
|   `-- dizzy-test-wifi
|       `-- sdimage-gnuradio-dev.direct.xz
|-- e310-release-002
|   |-- oecore-x86_64-armv7ahf-vfp-neon-toolchain-nodistro.0.manifest
|   |-- oecore-x86_64-armv7ahf-vfp-neon-toolchain-nodistro.0.sh
|   |-- sdimage-gnuradio-demo.direct.xz
|   |-- sdimage-gnuradio-demo.direct.xz.md5sum
|   |-- sdimage-gnuradio-dev.direct.xz
|   `-- sdimage-gnuradio-dev.direct.xz.md5sum
|-- e3xx-release-001
|   |-- e300-gnuradio-dev-image-release1.bz
|   `-- nodistro-eglibc-x86_64-gnuradio-dev-image-armv7ahf-vfp-neon-toolchain-nodistro.0.sh
|-- e3xx-release-3
|   |-- oecore-x86_64-armv7ahf-vfp-neon-toolchain-nodistro.0.manifest
|   |-- oecore-x86_64-armv7ahf-vfp-neon-toolchain-nodistro.0.sh
|   |-- sdimage-gnuradio-demo.direct.xz
|   `-- sdimage-gnuradio-dev.direct.xz
`-- e3xx-release-4
    |-- ettus-e3xx-sg1
    |   |-- sdimage-gnuradio-demo.direct.xz
    |   |-- sdimage-gnuradio-demo.direct.xz.md5
    |   |-- sdimage-gnuradio-dev.direct.xz
    |   `-- sdimage-gnuradio-dev.direct.xz.md5
    |-- ettus-e3xx-sg3
    |   |-- sdimage-gnuradio-demo.direct.xz
    |   |-- sdimage-gnuradio-demo.direct.xz.md5
    |   |-- sdimage-gnuradio-dev.direct.xz
    |   `-- sdimage-gnuradio-dev.direct.xz.md5
    |-- oecore-x86_64-armv7ahf-vfp-neon-toolchain-nodistro.0.manifest
    `-- oecore-x86_64-armv7ahf-vfp-neon-toolchain-nodistro.0.sh

WiFi Network Connectivity

Below are instructions on setting up a USB WiFi adapter with the E3xx. We have tested the "Edimax EW-7811Un", however many USB based WiFi adapters should be supported.

First verify the USB WiFI adapter is found by running lsusb.

Example output from lsusb for the "Edimax EW-7811Un" WiFi adapter:

Bus 001 Device 003: ID 7392:7811 Edimax Technology Co., Ltd EW-7811Un 802.11n Wireless Adapter [Realtek RTL8188CUS]

If the USB adapter is found, proceed with installation and configuration procedure:

1. Run the command below. Enter the passphrase and hit <Enter>.

   wpa_passphrase <SSID> >> /etc/wpa_supplicant.conf`

2. In the file /etc/wpa_supplicant.conf, edit the entry created above to look like the text below (just add what is missing).

network={
       ssid="YOUR_SSID"
       psk=HASH_VALUE
       key_mgmt=WPA-PSK
       proto=RSN WPA
       pairwise=CCMP TKIP
       group=CCMP TKIP
}

3. Run the command:

   wpa_supplicant -B -D nl80211 -i wlan0 -c /etc/wpa_supplicant.conf

4. Run the command:

   udhcpc -i wlan0

Additional Resources

Application Notes

• Software Development on the E310 and E312
• Resolving Audio Codec Enumeration Issues On The E31x

Third-party Resources

• Compass Heading Using Magnetometers (Honeywell Application Note)

Downloads

FPGA Images

FPGA Images Read Me

FPGA Resources

UHD Stable Binaries

UHD Source Code on Github

USRP Embedded Series FAQ

General USRP E31x Questions

Q: What data rate is supported for continuous sample streaming to a desktop or laptop host-PC? A: Unlike host-based SDRs such as the USRP B, N, and X Series devices, the USRP E Series devices are not intended for continuous streaming of high bandwidth data to a desktop or laptop host-PC. The SDR application runs on an embedded CPU with limited processing capability. Users should leverage the FPGA using tools such as RFNoC to offload compute intensive algorithms that process high bandwidth samples.

Q: What data rate is supported between FPGA to the ARM processor? A: Due to the limited performance of the embedded processor, the maximum data rate from the FPGA to ARM cores is approximately 10 MS/s, and will vary with the processing load on the CPU. The AD9631 RFIC is capable of capturing 56 MHz of bandwidth. Processing signals at full bandwidth requires implementing algorithms on the FPGA.

Q: What is the purpose of the 1 GbE port? A: The E Series can run a DHCP client on the 1 GigE interface to enable connection to a larger network for remote access by another computer. Power over Ethernet is also supported on the E313.

USRP E313 Questions

Q: Which environmental tests were performed? A: The USRP E313 is tested against multiple environmental standards to ensure operation in outdoor conditions. These test include ingress protection, temperature, humidity, mechanical shock, random vibration, and altitude. Detailed specifications are provided in the [link data sheet].

Q: How do I protect external devices connected to the host USB port? 


A: A circular conduit interface is provided in the kit. This component has large and small threaded ends. The small end connects to the USB port on the USRP E313. The user will need to connect their own waterproof structure to the large end to protect the USB device. Since requirements for external devices vary greatly, the conduit interface serves as a flexible starting point for users to build their own solution. See the Media:USRP E313 Dimension Pole Mount.pdf of the conduit interface for details.

Q: How do I protect unused ports? A: All ports come with protective end caps that should be left in place on unused ports.

Q: Why is a DC power supply not included? A: The RJ45 port supports Power over Ethernet and is intended as the primary power supply option. However, users can still use a DC power supply. Since requirements for supplying DC power in outdoor scenarios can vary greatly, a waterproof sleeve for the DC port is provided as a starting point for users to design their own solution. A waterproof sleeve for the RJ45 port is also provided.

Q: Do the RF inputs have lightning protection? A: The DC and PoE power inputs have surge and lightning protection, but the N-type RX/TX inputs and SMA GPS input do not. Users should design antenna lightning protection based on their application requirements.