USRP X410 Getting Started Guide - Revision history

MichaelDickens: delete contents & move to REDIRECT since all of this content is now on X410/X440, but we want old search results to still work

2023-09-25T13:46:00Z

delete contents & move to REDIRECT since all of this content is now on X410/X440, but we want old search results to still work

Show changes

DylanCaswell: /* Front-Panel Programmable GPIOs */

2023-07-10T21:11:55Z

‎Front-Panel Programmable GPIOs

DylanCaswell: /* Updating Filesystems */

2023-01-26T18:02:38Z

‎Updating Filesystems

DylanCaswell: /* Updating Filesystems */

2023-01-26T17:51:47Z

‎Updating Filesystems

MichaelDickens: /* Flashing the eMMC */ don't mention which utility up front

2022-09-30T19:32:22Z

‎Flashing the eMMC: don't mention which utility up front

MichaelDickens: /* Flashing the eMMC */ update to include 'dd' and note preference

2022-09-30T18:46:36Z

‎Flashing the eMMC: update to include 'dd' and note preference

MichaelDickens: /* Updating Filesystems */ add mender website

2022-08-01T22:08:19Z

‎Updating Filesystems: add mender website

WadeFife: Updated instructions for flashing eMMC to fix incorrect filename and add copy arg to bmaptool.

2022-05-13T14:27:59Z

Updated instructions for flashing eMMC to fix incorrect filename and add copy arg to bmaptool.

WadeFife at 17:52, 15 April 2022

2022-04-15T17:52:15Z

WadeFife: Change SFP network port config file location

2022-03-22T21:27:30Z

Change SFP network port config file location

@@ Line 520: / Line 520: @@
 The USRP X410 has two HDMI front-panel connectors, which are connected to the FPGA.
-Support for using these with UHD is not yet available.
+[https://files.ettus.com/manual/page_x400_gpio_api.html USRP X410 GPIO UHD Manual Entry]
 ==Subdev Specifications==

@@ Line 159: / Line 159: @@
 Next, you will need to copy this Mender file system image to the USRP X4xx. This can be done with the Linux utility <code>scp</code>.
-     $ scp /usr/local/share/uhd/images/usrp_x3xx_fs.mender root@192.168.1.51:~/.
+     $ scp /usr/local/share/uhd/images/usrp_x4xx_fs.mender root@192.168.1.51:~/.
 Note: The path and IP may different for your configuration, the command above assumes you're using the default installation path of <code>/usr/local</code> and that the X4xx's IP is <code>192.168.1.51</code>.

@@ Line 151: / Line 151: @@
 When updating the file system using Mender, the tool will overwrite the root file system partition that is not currently mounted (note: the onboard flash storage contains two separate root file system partitions, only one is ever used at a single time). Any data stored on that partition will be permanently lost, including the currently loaded FPGA image. After updating that partition, it will reboot into the newly updated partition. Only if the update is confirmed by the user, the update will be made permanent. This means that if an update fails, the device will be always able to reboot into the partition from which the update was originally launched (which presumably is in a working state). Another update can be launched now to correct the previous, failed update, until it works.
-To initiate an update from the device itself, download a Mender artifact containing the update itself. These are files with a .mender suffix. They can be downloaded by using the uhd_images_downloader utility:
+To obtain the file system Mender image (these are files with a <code>.mender</code> suffix), run the following command on the host computer with Internet access:
-<code>$ uhd_images_downloader -t mender -t x4xx</code>
+    $ sudo uhd_images_downloader -t mender -t x4xx --yes
-Append the -l switch to print out the URLs only:
+NOTE: In the output of the command, the folder destination where the images are saved is printed out.
-<code>$ uhd_images_downloader -t mender -t x4xx -l</code>
+Next, you will need to copy this Mender file system image to the USRP X4xx. This can be done with the Linux utility <code>scp</code>.
-Then run mender on the command line:
+    $ scp /usr/local/share/uhd/images/usrp_x3xx_fs.mender root@192.168.1.51:~/.
-<code>$ mender install /path/to/latest.mender</code>
+Note: The path and IP may different for your configuration, the command above assumes you're using the default installation path of <code>/usr/local</code> and that the X4xx's IP is <code>192.168.1.51</code>.
-The artifact can also be stored on a remote server:
+After copying the Mender file system image to the X4xx, connect to the X4xx using either the Serial Console, or via SSH to gain shell access.
-<code>$ mender install http://server.name/path/to/latest.mender</code>
+On the X4xx, run <code>mender install /path/to/latest.mender</code> to update the file system:
-This procedure will take a while. If the new filesystem requires an update to the MB CPLD, see Updating the Motherboard CPLD before proceeding. After mender has logged a successful update, reboot the device:
+    $ mender install /home/root/usrp_x4xx_fs.mender
-<code>$ reboot</code>
+The artifact can also be stored on a remote server:
-If the reboot worked, and the device seems functional, commit the changes so the boot loader knows to permanently boot into this partition:
+This procedure will take a few minutes to complete. After mender has logged a successful update, reboot the device:
-<code>$ mender commit</code>
+If the reboot worked, and the device seems functional, commit the changes so that the boot loader knows to permanently boot into this partition:
-To identify the currently installed Mender artifact from the command line, the following file can be queried:
+To identify the currently installed Mender artifact from the command line, the following file can be queried on the X4xx:
-<code>$ cat /etc/mender/artifact_info</code>
+If you are using a Mender server, the updates can be initiated from a web dashboard. From there, you can start the updates without having to log into the device, and you can update groups of USRPs with a few clicks in a web GUI. The dashboard can also be used to inspect the state of USRPs. This is a simple way to update groups of rack-mounted USRPs with custom file systems.
 If you are running a hosted server, the updates can be initiated from a web dashboard. From there, you can start the updates without having to log into the device, and can update groups of USRPs with a few clicks in a web GUI. The dashboard can also be used to inspect the state of USRPs. This is a simple way to update groups of rack-mounted USRPs with custom file systems.

@@ Line 124: / Line 124: @@
 == Flashing the eMMC ==
-Once the X410's eMMC is accessible over USB, it's possible to write the filesystem image using bmaptool. You can obtain the latest filesystem image by running:
+Once the X410's eMMC is accessible over USB, it's possible to write the filesystem image and thus change the device's filesystem. You can obtain the latest filesystem image by running:
 <code>uhd_images_downloader -t sdimg -t x4xx</code>

@@ Line 122: / Line 122: @@
-==Flashing the eMMC==
+== Flashing the eMMC ==
 Once the X410's eMMC is accessible over USB, it's possible to write the filesystem image using bmaptool. You can obtain the latest filesystem image by running:
@@ Line 130: / Line 130: @@
 The output of this command will indicate where the downloaded images were put, or specify a custom location using using the <code>-i INSTALL_LOCATION</code> argument.
-To write the image to the X410's eMMC, run the following command, replacing <code>/dev/sdX</code> with the block device of the X410's eMMC (found in your kernel log or by running <code>lsblk</code>). Take care to use the correct block device or else you might overwrite the wrong drive!
+There are 2 ways to write the image to the X410's eMMC: using <code>dd</code> and <code>bmaptool</code>. Run one of the following commands, replacing <code>/dev/sdX</code> with the block device of the X410's eMMC (found in the device's kernel log or by running <code>lsblk</code>). Take care to use the correct block device or else you might overwrite the wrong drive!
 <code>sudo bmaptool copy --bmap /path/to/usrp_x4xx_fs.sdimg.bmap /path/to/usrp_x4xx_fs.sdimg /dev/sdX</code>
 ==Using a USRP X4x0 from UHD==

@@ Line 144: / Line 144: @@
 ==Updating Filesystems==
-Mender is a third-party software that enables remote updating of the root file system without physically accessing the device (see also the Mender website). Mender can be executed locally on the device, or a Mender server can be set up which can be used to remotely update an arbitrary number of USRP devices. Mender servers can be self-hosted, or hosted by Mender (see mender.io for pricing and availability).
+Mender is a third-party software that enables remote updating of the root file system without physically accessing the device (see also the [https://mender.io/ Mender website]). Mender can be executed locally on the device, or a Mender server can be set up which can be used to remotely update an arbitrary number of USRP devices. Mender servers can be self-hosted, or hosted by Mender (see mender.io for pricing and availability).
 When updating the file system using Mender, the tool will overwrite the root file system partition that is not currently mounted (note: the onboard flash storage contains two separate root file system partitions, only one is ever used at a single time). Any data stored on that partition will be permanently lost, including the currently loaded FPGA image. After updating that partition, it will reboot into the newly updated partition. Only if the update is confirmed by the user, the update will be made permanent. This means that if an update fails, the device will be always able to reboot into the partition from which the update was originally launched (which presumably is in a working state). Another update can be launched now to correct the previous, failed update, until it works.
@@ Line 177: / Line 177: @@
 If you are running a hosted server, the updates can be initiated from a web dashboard. From there, you can start the updates without having to log into the device, and can update groups of USRPs with a few clicks in a web GUI. The dashboard can also be used to inspect the state of USRPs. This is a simple way to update groups of rack-mounted USRPs with custom file systems.
 ==Network Interfaces==

← Older revision		Revision as of 17:52, 15 April 2022
Line 157:		Line 157:

	<code>$ uhd_images_downloader -t mender -t x4xx -l</code>		<code>$ uhd_images_downloader -t mender -t x4xx -l</code>
		+
	Then run mender on the command line:		Then run mender on the command line:

@@ Line 194: / Line 194: @@
 Each QSFP28 port has four high-speed transceiver lanes. Therefore, depending on the FPGA image flavor, up-to four different network interfaces may exist per QSFP28 port, using the sfpXfor the first lane, and sfpX_1-3 for the other three lanes. Each network interface has a default static IP address. Note that for multi-lane protocols, such as 100 GbE, a single interface is used (sfpX).
-The configuration files for these network interfaces are stored in: <code>/etc/systemd/network/</code>
+The configuration files for these network interfaces are stored in: <code>/data/network/</code>
 {| class="wikitable"