](/img/rak4631-rakdap1.png)
5. Flash the bootloader
-
-```shell
-pyocd flash -t nrf52840 .\WisCore_RAK4631_Board_Bootloader.hex
-```
-
-6. Continue with the [normal instructions](/docs/getting-started/flashing-firmware/nrf52/flashing-nrf52)
+ ```shell
+ pyocd flash -t nrf52840 .\WisCore_RAK4631_Board_Bootloader.hex
+ ```
+6. Continue with the normal [flashing instructions](/docs/getting-started/flashing-firmware/nrf52/drag-n-drop)
Alternate methods of flashing are outlined [here](https://github.com/RAKWireless/WisBlock/tree/master/bootloader/RAK4630).
\ No newline at end of file
diff --git a/docs/getting-started/flashing-firmware/nrf52/python-flasher.mdx b/docs/getting-started/flashing-firmware/nrf52/python-flasher.mdx
index 02776928..669150f2 100644
--- a/docs/getting-started/flashing-firmware/nrf52/python-flasher.mdx
+++ b/docs/getting-started/flashing-firmware/nrf52/python-flasher.mdx
@@ -2,7 +2,7 @@
id: meshtastic-flasher-nrf52
title: Using Python Meshtastic Flasher
sidebar_label: Python Flasher
-sidebar_position: 1
+sidebar_position: 2
---
import MFlasher from '../../../software/python/meshtastic-flasher.mdx'
diff --git a/docs/getting-started/serial-drivers/index.mdx b/docs/getting-started/serial-drivers/index.mdx
index 329ff078..43d44365 100644
--- a/docs/getting-started/serial-drivers/index.mdx
+++ b/docs/getting-started/serial-drivers/index.mdx
@@ -8,27 +8,25 @@ sidebar_position: 1
import Tabs from '@theme/Tabs';
import TabItem from '@theme/TabItem';
+:::caution
+Make sure not to power the radio on without first attaching the antenna! You could damage the radio chip!
+:::
+
+Prior to connecting your Meshtastic device to the computer, you should perform the following basic checks.
## Verify data cable
-Verify you have a data cable (not a charging only cable) before proceeding. There's no definitive way to determine the difference in cables if you aren't willing to pull it apart. Trying out a few cables will be the best way to verify.
+Verify that you have a **data cable** and _not_ a **charging _only_ cable** before proceeding. There is no definitive way to determine the difference in cables if you aren't willing to pull it apart. Trying out a few cables will be the best way to verify.
-Once you've located a data cable, check the following to see if you need to install a driver to communicate with your device.
+Once you've located a working data cable, [test for driver installation](/docs/getting-started/serial-drivers/#test-for-driver-installation) to see if you need to install a driver to communicate with your device.
-:::tip
-If you know you have installed the correct driver, the following step can be used to check if your cable is a data cable.
-:::
+If you know you have installed the correct driver, the following step can be used to check if you have a proper data cable.
## Test for driver installation
-You can verify that you have a proper data cable (rather than a charge-only type cable) and that the appropriate drivers for your system are installed by performing the following test. Select your operating system below.
+You can verify that you have a proper data cable (rather than a charge-only type cable) and that the appropriate drivers for your system are installed by performing the following test:
-If you can see your device, you are ready to flash the firmware. Skip to the [Choose Firmware Flashing Method section](#choose-firmware-flashing-method).
-
-If you do not see your device in the following test, you either:
-
-1. Need to [install a driver](#install-appropriate-drivers).
-2. Are currently using a charging only cable.
+_select your operating system below_
-
+
Flasher
+
+
-
+
+
+
+
- pip,
- ' follow ',
-
- these instructions
- ,
- '.',
- ]}
- />
+ {/* */}
+
Apps
+
+
-
+
+
+
+
+
+
+
+
+
+
+ Apple
+ + App Store +
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Web
+ + meshtastic.org +
-
- -
-
-
-
+ {/* */}
+
Firmware
+
+
Date: Tue, 1 Nov 2022 22:52:50 +1000
Subject: [PATCH 5/5] update llc in footer
---
docusaurus.config.js | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docusaurus.config.js b/docusaurus.config.js
index a373fc44..1c4ca954 100644
--- a/docusaurus.config.js
+++ b/docusaurus.config.js
@@ -69,7 +69,7 @@ const config = {
],
},
footer: {
- copyright: `Powered by ▲ Vercel | Meshtastic® is a registered trademark of Geeksville Industries LLC. | Legal Information.`,
+ copyright: `Powered by ▲ Vercel | Meshtastic® is a registered trademark of Meshtastic LLC. | Legal Information.`,
},
algolia: {
appId: 'IG2GQB8L3V',
+
+
{data && !error ? (
<>
{
description="Upcoming changes for testing. For those who want new features."
release={alpha}
/>
-
);
};
From 30dfe9f720bb39e790e59fff42ec7b58b37353ea Mon Sep 17 00:00:00 2001
From: Sacha Weatherstone
+
@@ -148,39 +178,9 @@ const Firmware = (): JSX.Element => {
- Bleeding
-
- Google Play and the Google Play logo are trademarks of Google LLC.
-
-
-
+