add text for disabling firmware safety checks (#246)

* add text for disabling firmware safety checks * add dangerous upgrade examples
aredn · Mar 17, 2023 · 839787b · 839787b
1 parent 32b870d
commit 839787b
Show file tree

Hide file tree

Showing 4 changed files with 7 additions and 3 deletions.
diff --git a/arednGettingStarted/_images/advConfig-downloads.png b/arednGettingStarted/_images/advConfig-downloads.png
diff --git a/arednGettingStarted/_images/advConfig-firmware.png b/arednGettingStarted/_images/advConfig-firmware.png
diff --git a/arednGettingStarted/advanced_config.rst b/arednGettingStarted/advanced_config.rst
@@ -549,13 +549,15 @@ These fields contain the external URLs for map tiles and `leafletjs <https://lea
 Firmware and Package Download Paths
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-.. image:: _images/advConfig-downloads.png
+.. image:: _images/advConfig-firmware.png
   :alt: Advanced Configuration - downloads
   :align: center
 
-These fields contain the URLs used by the node for downloading firmware and package files during upgrades. By default they point to the AREDN |trade| downloads server available across the Internet. You can change these paths to point to a local mesh package server in order to upgrade nodes that do not have Internet access.
+|
+
+These fields contain the URLs used by the node for downloading firmware and package files during upgrades. By default they point to the AREDN |trade| downloads server available across the Internet. You can change these paths to point to a local mesh package server in order to upgrade nodes that do not have Internet access. If you plan to create a local software repository for your mesh network, review **Creating a Local Package Server** in the **How-To Guide** section.
 
-.. note:: If you plan to create a local software repository for your mesh network, review **Creating a Local Package Server** in the **How-To Guide** section.
+The **Dangerous Upgrade** setting allows you to disable the normal firmware compatibility safety checks that typically prevent you from loading the wrong firmware image on your node. The default setting is *OFF* which means that the safety checks remain enabled, and this setting should not be changed unless you have a specific reason to disable the firmware compatibility checks. One example for using this setting would be if you mistakenly installed an incorrect firmware image and would like to correct that mistake by installing the correct firmware image (e.g., you installed the Mikrotik LHG version when you meant to install the LHG XL version).
 
 AREDN |trade| Alert Messages
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^

diff --git a/arednHow-toGuides/firmware_tips.rst b/arednHow-toGuides/firmware_tips.rst
@@ -81,4 +81,6 @@ However, there is a difference if you are downgrading the firmware on a node whi
   - For Mikrotik models you will boot using the *vmlinux-initramfs.elf* file (which you rename to *rb.elf*) and then immediately apply the *sysupgrade.bin* firmware image.
   - For GL.iNet models you will use the `recovery procedure <https://docs.gl-inet.com/en/3/tutorials/debrick/>`_ to upload the *sysupgrade.bin* firmware image.
 
+Another possible way to downgrade firmware between architectures is to enable **Dangerous Upgrade** under the *Advanced Configuration* settings. Setting this to *ON* will disable the normal firmware compatibility checks that are done automatically during the firmware install process. This should allow your node to install a firmware image that uses a legacy architecture.
+
 After downgrading your node's firmware you will then continue the process for entering your callsign and configuring the node's settings, as explained in the **Basic Setup** section.