aboutsummaryrefslogtreecommitdiffstats
path: root/host/docs/usrp_x4xx.dox
diff options
context:
space:
mode:
Diffstat (limited to 'host/docs/usrp_x4xx.dox')
-rw-r--r--host/docs/usrp_x4xx.dox11
1 files changed, 11 insertions, 0 deletions
diff --git a/host/docs/usrp_x4xx.dox b/host/docs/usrp_x4xx.dox
index 8078734c5..23a560d7d 100644
--- a/host/docs/usrp_x4xx.dox
+++ b/host/docs/usrp_x4xx.dox
@@ -539,11 +539,22 @@ Otherwise, let the boot continue as normal.
<b>Caution! Updating the motherboard CPLD has the potential to brick your
device if done improperly.</b>
+After updating the filesystem, you may have to update your motherboard CPLD. If
+you forget to update the CPLD, MPM will fail to fully initialize and emit a
+warning. This is not critical, and the CPLD update can be performed later by
+following these same steps, but the device will not be usable until then.
+
+Even though the CPLD may not require updating, it is recommended to always run
+these steps for a consistent update procedure.
+
You can update the motherboard (MB) CPLD by running the following command on
the X410:
x4xx_update_cpld --file=<path to cpld-x410.rpd>
+Note: Old filesystems may not contain this command. If you are performing a
+mender update, simply run these commands after the update.
+
Filesystems will usually contain a compatible `cpld-x410.rpd` file at
`/lib/firmware/ni/cpld-x410.rpd`. If you're installing a new filesystem via
mender, you may have to mount the new filesystem (before you boot into it) in