mudhorn/meshtastic
1
0
Fork 0
mirror of https://github.com/meshtastic/meshtastic.git synced 2024-12-26 22:19:46 -08:00
Code Issues Actions Packages Projects Releases Wiki Activity

upgrade iss. w/ prev. vers. and formatting nRF52.

Browse source
This commit is contained in:
rcarteraz 2023-01-15 21:40:43 -07:00 committed by Thomas Göttgens
parent f924461192
commit 48d61e2cfe
4 changed files with 22 additions and 17 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/getting-started/flashing-firmware/nrf52/convert-rak4631r.mdx
View file

@ -7,7 +7,7 @@ sidebar_position: 4
The only difference between the _RAK4631-R_ (RUI3) and the _RAK4631_ (Arduino) is the bootloader it is shipped with - the hardware is the same.
Meshtastic requires the Arduino bootloader on RAK WisBlock NRF52-based boards. The process of converting the bootloader only needs to be performed once.
Meshtastic requires the Arduino bootloader on RAK WisBlock nRF52-based boards. The process of converting the bootloader only needs to be performed once.
This conversion requires the use of either a [DAPLink](https://daplink.io/) or [J-Link](https://www.segger.com/products/debug-probes/j-link/). The most reasonably priced and available is the [RAKDAP1](https://store.rakwireless.com/products/daplink-tool).

19
docs/getting-started/flashing-firmware/nrf52/drag-n-drop.mdx
View file

@ -9,16 +9,11 @@ import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';
:::info
Before flashing confirm that you have [RAK4631](https://docs.rakwireless.com/Product-Categories/WisBlock/RAK4631/) and not a [RAK4631-R](https://docs.rakwireless.com/Product-Categories/WisBlock/RAK4631-R/) If this is not the case, fear not. The hardware is identical but requires changing the bootloader. Instructions on how to do this are located [here](/docs/getting-started/flashing-firmware/nrf52/convert-rak4631r).
:::
## Upgrading from a previous version of Meshtastic
If you are upgrading your NRF52 device from a previous version of Meshtastic rather than starting from scratch, you may need to do a full factory reset of the internal flash memory. Stale data saved by previous versions of the Meshtastic firmware can cause devices to get stuck in a crash loop at startup.
Follow the guide to [factory erase your NRF52](/docs/getting-started/flashing-firmware/nrf52/nrf52-erase) device before continuing to [flash firmware](#flash-firmware).
## Flash Firmware
Download and unzip the latest firmware from [Meshtastic Downloads](https://meshtastic.org/downloads).
@ -30,3 +25,13 @@ Download and unzip the latest firmware from [Meshtastic Downloads](https://mesht
5. Drop the appropriate firmware file (`firmware-DEVICE_NAME-vx.x.x-xxxxxxx.uf2`) from the release onto this drive.
Once the file has finished copying onto the drive, the device will reboot and install the Meshtastic firmware.
### Issues When Upgrading from A Previous Version of Meshtastic
:::info
Previous versions of the Meshtastic firmware may save stale data, causing devices to get stuck in a crash loop during startup. If you experience issues when upgrading your nRF52 device from a previous version of Meshtastic, you may need to perform a full factory reset of the internal flash memory.
Follow the guide to [factory erase your nRF52](/docs/getting-started/flashing-firmware/nrf52/nrf52-erase) device before continuing to [flash firmware](#flash-firmware).
:::

8
docs/getting-started/flashing-firmware/nrf52/index.mdx
View file

@ -1,13 +1,13 @@
---
id: flashing-nrf52-devices
title: Flash NRF52 Devices
sidebar_label: NRF52 Device
title: Flash nRF52 Devices
sidebar_label: nRF52 Device
sidebar_position: 2
---
## Flashing Methods for NRF52 Devices
## Flashing Methods for nRF52 Devices
The NRF52 based devices have the easiest firmware upgrade process. No driver or software install is required on any platform.
The nRF52 based devices have the easiest firmware upgrade process. No driver or software install is required on any platform.
1. The [drag and drop](/docs/getting-started/flashing-firmware/nrf52/drag-n-drop) firmware installation is considered the "manual process" and recommended as the easiest solution.
2. The [Python Flasher](/docs/software/python/flasher) application does a lot under the hood to prevent you from needing to use the terminal. It also allows you to configure your device.

8
docs/getting-started/flashing-firmware/nrf52/nrf52-erase.mdx
View file

@ -1,13 +1,13 @@
---
id: nrf52-erase
title: Flash NRF52 Factory Erase
sidebar_label: Factory Erase NRF52
title: Flash nRF52 Factory Erase
sidebar_label: Factory Erase nRF52
sidebar_position: 3
---
Meshtastic uses the [littlefs](https://github.com/littlefs-project/littlefs) library to store configuration, logs, and other data in the internal flash of NRF52 devices. Updating the firmware does _not_ erase this additional data, which can cause issues when the format and location of data changes between releases.
Meshtastic uses the [littlefs](https://github.com/littlefs-project/littlefs) library to store configuration, logs, and other data in the internal flash of nRF52 devices. Updating the firmware does _not_ erase this additional data, which can cause issues when the format and location of data changes between releases.
To reset the flash storage on your NRF52 board:
To reset the flash storage on your nRF52 board:
Download and unzip the latest firmware from [Meshtastic Downloads](https://meshtastic.org/downloads).