Merge branch 'master' into nodered-update-1

This commit is contained in:
Sacha Weatherstone 2023-12-26 21:23:46 +10:00 committed by GitHub
commit 12667a0a36
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
8 changed files with 25 additions and 14 deletions

View file

@ -29,7 +29,7 @@ Most communication and interactions happen with protocol buffers. The [Meshtasti
### Device Firmware
The [firmware repo](https://github.com/meshtastic/firmware) is where all of the device firmware development happens. This is where the code for the ESP32 and nRF52 based devices is developed. It is mainly C and C++ code. Think Arduino. It is where the first level of hardware interaction begins and ends.
The [firmware repo](https://github.com/meshtastic/firmware) is where all of the device firmware development happens. This is where the code for the ESP32, nRF52 and RP2040 based devices is developed. It is mainly C and C++ code. Think Arduino. It is where the first level of hardware interaction begins and ends.
### Firmware Modules

View file

@ -131,6 +131,10 @@ All MQTT module config options are available for the Web UI.
## Connect to the Default Public Server
:::important
The default channel (LongFast) on the public server usually has a lot of traffic. Your device may get overloaded and may no longer function properly anymore. It is recommended to use a different channel or to use your own MQTT server if you experience issues.
:::
<Tabs
defaultValue="apple"
values={[

View file

@ -15,7 +15,7 @@ Power settings are advanced configuration, most users should choose a role under
The power config options are: Power Saving, Shutdown after losing power, ADC Multiplier Override, Wait Bluetooth Interval, Light Sleep Interval, Minimum Wake Interval, and Device Battery INA2xx Address. Power config uses an admin message sending a `Config.Power` protobuf.
:::info
ADC Multiplier, The Light Sleep setting only applies to ESP32-based boards. This settings will have no effect on nRF52 modules.
ADC Multiplier, The Light Sleep setting only applies to ESP32-based boards. This settings will have no effect on nRF52/RP2040 modules.
:::
## Power Config Values

View file

@ -42,7 +42,7 @@ The nRF52 chip is much more power efficient than the ESP32 chip and easier to up
The RP2040 is a dual-core ARM chip developed by Raspberry Pi. Supported RP2040 devices include:
- Raspberry Pi Pico + Waveshare LoRa Module (Note: **Bluetooth and Wi-Fi on the Pico W is not yet supported by Meshtastic**)
- Raspberry Pi Pico + Waveshare LoRa Module (Note: **Bluetooth on the Pico W is not yet supported by Meshtastic**)
- RAK11310 Core module for RAK WisBlock modular boards
:::info
@ -67,7 +67,7 @@ Some cables only provide _charging_, verify that your cable is also capable of _
:::caution
nRF52 devices typically do not require serial drivers. They use the UF2 bootloader which makes the devices appear as flash drives. Do _NOT_ download the USB device drivers unless required to install UF2 support.
nRF52/RP2040 devices typically do not require serial drivers. They use the UF2 bootloader which makes the devices appear as flash drives. Do _NOT_ download the USB device drivers unless required to install UF2 support.
:::
@ -89,7 +89,7 @@ If you require serial drivers installed on your computer, please choose one of t
className={'button button--outline button--lg cta--button'}
to={'/docs/getting-started/serial-drivers/nrf52'}
>
Install NRF52 Drivers
Install nRF52/RP2040 Drivers
</Link>
</div>
</div>
@ -115,7 +115,7 @@ After completing the previous steps, you can now flash the Meshtastic firmware o
className={"button button--outline button--lg cta--button"}
to={"/docs/getting-started/flashing-firmware/nrf52/"}
>
Flash nRF52 Firmware
Flash nRF52/RP2040 Firmware
</Link>
</div>
</div>

View file

@ -1,7 +1,7 @@
---
id: nrf52
title: nRF52 Serial Drivers
sidebar_label: nRF52 Drivers
title: nRF52/RP2040 Serial Drivers
sidebar_label: nRF52/RP2040 Drivers
sidebar_position: 2
---
@ -9,11 +9,11 @@ import Tabs from "@theme/Tabs";
import TabItem from "@theme/TabItem";
import Link from "@docusaurus/Link";
## Install nRF52 USB to Serial Drivers
## Install nRF52/RP2040 USB to Serial Drivers
:::caution
nRF52 devices typically do not require serial drivers. They use the UF2 bootloader which makes the devices appear as flash drives. Do _NOT_ download the USB device drivers unless required to install UF2 support.
nRF52/RP2040 devices typically do not require serial drivers. They use the UF2 bootloader which makes the devices appear as flash drives. Do _NOT_ download the USB device drivers unless required to install UF2 support.
:::
@ -86,6 +86,6 @@ After installing the serial drivers, you can now flash the Meshtastic firmware o
className={"button button--outline button--lg cta--button"}
to={"/docs/getting-started/flashing-firmware/nrf52/"}
>
Flash nRF52 Firmware
Flash nRF52/RP2040 Firmware
</Link>
</div>

View file

@ -94,7 +94,7 @@ After completing the previous steps, you can now flash the Meshtastic firmware o
className={"button button--outline button--lg cta--button"}
to={"/docs/getting-started/flashing-firmware/nrf52/"}
>
Flash nRF52 Firmware
Flash nRF52/RP2040 Firmware
</Link>
</div>
</div>

View file

@ -194,10 +194,15 @@ Image Source: [Heltec](https://heltec.org/project/wireless-tracker/)
</TabItem>
<TabItem value="paper">
:::info
This device may have issues charging a connected battery if utilizing a USB-C to USB-C cable. It's recommended to use a USB-A to USB-C cable.
:::caution
Please note, this device is only partially supported. The display is not currently implemented in the firmware.
Additionally, this device may have issues charging a connected battery if utilizing a USB-C to USB-C cable. It's recommended to use a USB-A to USB-C cable.
:::
- **MCU:**
- ESP32-S3FN8 (WiFi & Bluetooth)
- **LoRa Transceiver:**

View file

@ -17,6 +17,8 @@ You can find the settings available for MQTT [here](/docs/configuration/module/m
:::important
When MQTT is turned on, you are potentially broadcasting your entire mesh's traffic onto the public internet. This includes messages and position information.
The default channel (LongFast) on the public MQTT server usually has a lot of traffic. Your device may get overloaded and may no longer function properly anymore. It is recommended to use a different channel or to use your own MQTT server if you experience issues.
:::
## Software Integrations