From 70960da8dd1f50cb6904d98a37096123b332c59f Mon Sep 17 00:00:00 2001 From: rcarteraz Date: Mon, 18 Dec 2023 09:47:02 -0700 Subject: [PATCH 1/3] add note about display not being implemented --- docs/hardware/devices/heltec/index.mdx | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/docs/hardware/devices/heltec/index.mdx b/docs/hardware/devices/heltec/index.mdx index 10d9429d..a9167196 100644 --- a/docs/hardware/devices/heltec/index.mdx +++ b/docs/hardware/devices/heltec/index.mdx @@ -194,10 +194,15 @@ Image Source: [Heltec](https://heltec.org/project/wireless-tracker/) -:::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:** From fbf1638c6c875396397f923c92183cdbb381a489 Mon Sep 17 00:00:00 2001 From: GUVWAF Date: Tue, 19 Dec 2023 19:36:49 +0100 Subject: [PATCH 2/3] Add some missing references to RP2040 --- docs/about/contributing.mdx | 2 +- docs/configuration/radio/power.mdx | 2 +- docs/getting-started/index.mdx | 8 ++++---- .../serial-drivers/serial-drivers-nrf52.mdx | 10 +++++----- .../serial-drivers/test-serial-driver-installation.mdx | 2 +- 5 files changed, 12 insertions(+), 12 deletions(-) diff --git a/docs/about/contributing.mdx b/docs/about/contributing.mdx index cd4cd29d..fa23d48d 100644 --- a/docs/about/contributing.mdx +++ b/docs/about/contributing.mdx @@ -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 diff --git a/docs/configuration/radio/power.mdx b/docs/configuration/radio/power.mdx index 000b990f..6af55f9e 100644 --- a/docs/configuration/radio/power.mdx +++ b/docs/configuration/radio/power.mdx @@ -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 diff --git a/docs/getting-started/index.mdx b/docs/getting-started/index.mdx index 46d2a00f..6290e63c 100644 --- a/docs/getting-started/index.mdx +++ b/docs/getting-started/index.mdx @@ -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 @@ -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 diff --git a/docs/getting-started/serial-drivers/serial-drivers-nrf52.mdx b/docs/getting-started/serial-drivers/serial-drivers-nrf52.mdx index fd85b48a..5d2dc7e1 100644 --- a/docs/getting-started/serial-drivers/serial-drivers-nrf52.mdx +++ b/docs/getting-started/serial-drivers/serial-drivers-nrf52.mdx @@ -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 diff --git a/docs/getting-started/serial-drivers/test-serial-driver-installation.mdx b/docs/getting-started/serial-drivers/test-serial-driver-installation.mdx index 6fa58938..7e5ebb4d 100644 --- a/docs/getting-started/serial-drivers/test-serial-driver-installation.mdx +++ b/docs/getting-started/serial-drivers/test-serial-driver-installation.mdx @@ -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 From d0a26be0ce18b7830f5983748df5d13d27bea3d3 Mon Sep 17 00:00:00 2001 From: GUVWAF Date: Fri, 22 Dec 2023 21:06:08 +0100 Subject: [PATCH 3/3] Add notes about public server having a lot of traffic --- docs/configuration/module/mqtt.mdx | 4 ++++ docs/software/mqtt/index.mdx | 2 ++ 2 files changed, 6 insertions(+) diff --git a/docs/configuration/module/mqtt.mdx b/docs/configuration/module/mqtt.mdx index a7699448..675713e6 100644 --- a/docs/configuration/module/mqtt.mdx +++ b/docs/configuration/module/mqtt.mdx @@ -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. +::: +