From 50b2f582db0490c4ed71b1848c884685d78c8f7b Mon Sep 17 00:00:00 2001 From: rcarteraz Date: Mon, 29 May 2023 00:45:43 -0700 Subject: [PATCH 1/3] remove gui flasher card, update bleeding edge link --- src/pages/downloads/index.tsx | 21 ++------------------- 1 file changed, 2 insertions(+), 19 deletions(-) diff --git a/src/pages/downloads/index.tsx b/src/pages/downloads/index.tsx index 9bd76d8c..e7e41893 100644 --- a/src/pages/downloads/index.tsx +++ b/src/pages/downloads/index.tsx @@ -36,24 +36,7 @@ const Firmware = (): JSX.Element => {
-
-
-
-

Meshtastic Flasher

-
-
-

Desktop application to flash fimware to your devices.

-
-
- - Download - - -
-
+

ESP32 Web Flasher

@@ -214,7 +197,7 @@ const Firmware = (): JSX.Element => {
Download Bleeding From 627c3ce7b596ef1a5ee72bc49e6e7e6fbac6f5aa Mon Sep 17 00:00:00 2001 From: rcarteraz Date: Mon, 29 May 2023 00:56:19 -0700 Subject: [PATCH 2/3] fix width --- src/pages/downloads/index.tsx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/pages/downloads/index.tsx b/src/pages/downloads/index.tsx index e7e41893..a45e439b 100644 --- a/src/pages/downloads/index.tsx +++ b/src/pages/downloads/index.tsx @@ -36,7 +36,7 @@ const Firmware = (): JSX.Element => {
-
+
-
+

nRF52 Drag & Drop

From e43ab6ac371c589a2e8a0fb38384d63ab114512c Mon Sep 17 00:00:00 2001 From: rcarteraz Date: Fri, 26 May 2023 12:11:12 -0700 Subject: [PATCH 3/3] fix broken links --- docs/development/device/client-api.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/development/device/client-api.mdx b/docs/development/device/client-api.mdx index 5dc992c0..0f225e57 100644 --- a/docs/development/device/client-api.mdx +++ b/docs/development/device/client-api.mdx @@ -31,7 +31,7 @@ The receiver will validate length and if >512 it will assume the packet is corru This is the main Bluetooth service for the device and provides the API your app should use to get information about the mesh, send packets, or provision the radio. -For a reference implementation of a client that uses this service see [RadioInterfaceService](https://github.com/meshtastic/Meshtastic-Android/blob/master/app/src/main/java/com/geeksville/mesh/service/RadioInterfaceService.kt). +For a reference implementation of a client that uses this service see [RadioInterfaceService](https://github.com/meshtastic/Meshtastic-Android/blob/master/app/src/main/java/com/geeksville/mesh/repository/radio/RadioInterfaceService.kt). Typical flow when a phone connects to the device should be the following (if you want to watch this flow from the python app just run `meshtastic --debug --info` - the flow over BLE is identical): @@ -53,7 +53,7 @@ Expected sequence for initial download: - Read a endConfig packet that indicates that the entire state you need has been sent - Read a series of MeshPackets until it returns empty to get any messages that arrived for this node while the phone was away -For definitions (and documentation) on FromRadio, ToRadio, MyNodeInfo, NodeInfo and User protocol buffers see [mesh.proto](https://github.com/meshtastic/protobufs/blob/master/mesh.proto) +For definitions (and documentation) on FromRadio, ToRadio, MyNodeInfo, NodeInfo and User protocol buffers see [mesh.proto](https://github.com/meshtastic/protobufs/blob/master/meshtastic/mesh.proto) UUID for the service: 6ba1b218-15a8-461f-9fa8-5dcae273eafd