Start community edition project

CONTRIBUTING.md

@@ -0,0 +1,102 @@
+# Board support
+If you wish to add support for a specific board to the project, all you have to do (if it's ESP32 or nRF52), is write an additional entry for `Boards.h`.
+
+This entry should include, at a minimum, the following:
+* whether the device has bluetooth / BLE
+* whether the device has a PMU
+* whether the device has an EEPROM (false in all cases for nRF52, true for ESP32)
+* pin mappings for SPI NSS, SCLK, MOSI, MISO, modem reset and dio0
+* the type of modem on the board (if undefined it defaults to SX127x)
+* whether the modem has a busy pin
+* RX and TX leds (preferably LEDs of different colours)
+
+An example of a minimal entry can be seen below:
+`
+#elif BOARD_MODEL == BOARD_MY_WICKED_BOARD
+  #define HAS_BLUETOOTH true
+  #define HAS_PMU true
+  #define HAS_EEPROM true
+  #define EEPROM_SIZE 296 // minimum EEPROM size
+  #define EEPROM_OFFSET EEPROM_SIZE-EEPROM_RESERVED
+  const int pin_cs = 20;
+  const int pin_reset = 19;
+  // const int pin_cs = 1; not needed here
+  // const int pin_sclk = 2; not needed here
+  // const int pin_mosi = 3; not needed here
+  // const int pin_miso = 4; not needed here
+  const int pin_dio = 18;
+  // const int pin_busy = 0; not present
+  const int pin_led_rx = 5;
+  const int pin_led_tx = 6;
+`
+
+In some cases the SPI pins will not be required, as they will be the default pins for the SPI library supporting the board anyway, and therefore do not need overriding in the config.
+
+If the SX1262 is being used the following should also be considered:
+* whether DIO2 should be used as the RF switch (DIO2_AS_RF_SWITCH)
+* whether an rf on/off switch also has to be operated (through the pin pin_rxen)
+* whether a TCXO is connected to the modem (HAS_TCXO)
+* the enable pin for the TCXO (if present)
+
+An example of an entry using the SX1262 modem can be seen below:
+`
+#elif BOARD_MODEL == BOARD_MY_WICKED_BOARD
+  #define HAS_BLUETOOTH true
+  #define HAS_PMU true
+  #define HAS_EEPROM true
+  #define EEPROM_SIZE 296 // minimum EEPROM size
+  #define EEPROM_OFFSET EEPROM_SIZE-EEPROM_RESERVED
+  #define MODEM SX1262
+  #define DIO2_AS_RF_SWITCH true
+  #define HAS_TCXO true
+  #define HAS_BUSY true
+  const int pin_cs = 20;
+  const int pin_reset = 19;
+  const int pin_rxen = 10;
+  // const int pin_cs = 1; not needed here
+  // const int pin_sclk = 2; not needed here
+  // const int pin_mosi = 3; not needed here
+  // const int pin_miso = 4; not needed here
+  const int pin_dio = 18;
+  const int pin_busy = 7;
+  const int pin_tcxo_enable = -1;
+  const int pin_led_rx = 5;
+  const int pin_led_tx = 6;
+`
+
+If the SX1280 is being used, the following should also be added:
+* the TXEN and RXEN pins
+
+An example of an entry using the SX1280 modem can be seen below:
+`
+#elif BOARD_MODEL == BOARD_MY_WICKED_BOARD
+  #define HAS_BLUETOOTH true
+  #define HAS_PMU true
+  #define HAS_EEPROM true
+  #define EEPROM_SIZE 296 // minimum EEPROM size
+  #define EEPROM_OFFSET EEPROM_SIZE-EEPROM_RESERVED
+  #define MODEM SX1280
+  #define HAS_BUSY true
+  #define HAS_RF_SWITCH_RX_TX true
+  const int pin_cs = 20;
+  const int pin_reset = 19;
+  const int pin_rxen = 10;
+  const int pin_txen = 11;
+  // const int pin_cs = 1; not needed here
+  // const int pin_sclk = 2; not needed here
+  // const int pin_mosi = 3; not needed here
+  // const int pin_miso = 4; not needed here
+  const int pin_dio = 18;
+  const int pin_busy = 7;
+  const int pin_tcxo_enable = -1;
+  const int pin_led_rx = 5;
+  const int pin_led_tx = 6;
+`
+
+Please submit this, and any other support in different areas of the project your board may require, as a PR for my consideration.
+
+# Feature request
+Feature requests are welcomed, given that those requesting it are happy to write it themselves, or a contributor considers it to be important enough to them to write it themselves. They must be written and **properly** tested before being proposed as a pull request for the project on [GitHub](https://github.com/liberatedsystems/RNode_Firmware_CE). **Manufacturers are encouraged to contribute support for their products back to this repository**, and such support will be receieved gladly, given it does not effect support for other products or boards.
+
+# Caveat
+All contributions must not be written using **any** LLM (ChatGPT, etc.), please handwrite them **only**. Any PRs with proposed contributions which have been discovered to be written using an LLM will **NOT** be merged. The contributor concerned may rewrite their entire pull request **by hand** and it may be reconsidered for merging in the future. 

FAQ.md

@@ -0,0 +1,8 @@
+# Frequently asked questions
+## Can I produce and sell my own RNodes using this project? 
+Yes! Feel free to use the firmware in this repository for your produced RNodes. You do not have to pay a license to use this software commercially, as it is licensed under the GPLv3. If you fork it, you must understand your obligation to provide all future users of the system with the same rights that you have been provided by the GPLv3. Please also consider contributing additional features you design to this repository, to allow others to also use them.
+
+It is also likely worth you reading [this material from Mark Qvist](https://unsigned.io/sell_rnodes.html). Do consider donating to him if your venture is successful, without him this project would simply be a schizo fever dream.
+
+## Write a hecking code of conduct!!
+no

README.md

@@ -1,6 +1,6 @@
-# RNode Firmware
+# RNode Firmware - Community Edition
 
-This is the open firmware that powers RNode devices.
+This is the community maintained fork of the open firmware which powers RNode devices. It has been created to continue to expand development and support for more hardware devices, as the upstream repository is no longer accepting PRs for new hardware support. The original repository by Mark Qvist can be found [here](https://github.com/markqvist/RNode_Firmware).
 
 An RNode is an open, free and unrestricted digital radio transceiver. It enables anyone to send and receive any kind of data over both short and very long distances. RNodes can be used with many different kinds of programs and systems, but they are especially well suited for use with [Reticulum](https://reticulum.network).
 
@@ -14,28 +14,47 @@ The RNode system is primarily software, which *transforms* different kinds of av
 
 ## Latest Release
 
-The latest release, installable through `rnodeconf`, is version `1.68`. This release brings the following changes:
+The latest release, installable through `rnodeconf`, is version `1.72`. This release brings the following changes:
 
-- Fixed a bug in high-bandwidth optimisation
+- Added support for flashing T3S3 boards
-- Fixed a potential memory overflow during firmware update
+- Added deep sleep support on T3S3
-- Fixed a bug in LoRa modem status updates
+- Various quality updates for nRF / RAK4631
-- Updated bootstrap console with latest packages
+- Fixed a bug with antenna switch utilisation on RAK4631
+- Updated console image to include latest packages
 
-You must have at least version `2.1.3` of `rnodeconf` installed to update the RNode Firmware to version `1.67`. Get it by updating the `rns` package to at least version `0.6.4`.
+You must have at least version `2.1.3` of `rnodeconf` installed to update the RNode Firmware to version `1.72`. Get it by updating the `rns` package to at least version `0.6.4`.
 
-## A Self-Replicating System
+## Supported products and boards
 
-If you notice the presence of a circularity in the naming of the system as a whole, and the physical devices, it is no coincidence. Every RNode contains the seeds necessary to reproduce the system, the [RNode Bootstrap Console](https://unsigned.io/rnode_bootstrap_console), which is hosted locally on every RNode, and can be activated and accesses at any time - no Internet required.
+### Products
+| Name | Manufacturer | Link | Transceiver | MCU | Description |
+| :---: | :---: | :---: | :---: | :---: | :---: |
+| Handheld v2.x RNodes | [Mark Qvist](https://unsigned.io) | [Buy here](https://unsigned.io/shop/product/handheld-rnode) | SX1276 | ESP32 |
+| Original v1.x RNodes | [Mark Qvist](https://unsigned.io) | [Buy here](https://unsigned.io/shop/product/rnode) | SX1276 | ESP32 | This product is discontinued |
 
-The designs, guides and software stored within allows users to create more RNodes, and even to bootstrap entire communications networks, completely independently of existing infrastructure, or in situations where infrastructure has become unreliable or is broken.
+### Homebrew devices
+| Board name | Link | Transceiver | MCU | Description | 
+| :--- | :---: | :---: | :---: | :---: |
+| LilyGO LoRa32 v1.0 | [Buy here](https://www.lilygo.cc/products/lora32-v1-0) | SX1276/8 | ESP32 |
+| LilyGO T-BEAM v1.1 | [Buy here](https://www.lilygo.cc/products/t-beam-v1-1-esp32-lora-module) | SX1276/8 | ESP32 |
+| LilyGO LoRa32 v2.0 | No link | SX1276/8 | ESP32 | Discontinued? |
+| LilyGO LoRa32 v2.1 |  [Buy here](https://www.lilygo.cc/products/lora3) | SX1276/8 | ESP32 | With and without TCXO |
+| Heltec LoRa32 v2 | No link | SX1276/8 | ESP32 | Discontinued? |
+| Heltec LoRa32 v3 | [Buy here](https://heltec.org/project/wifi-lora-32-v3/) | SX1276/8 | ESP32 | 
+| Homebrew ESP32 boards | | Any supported | ESP32 | This can be any board with an Adafruit Feather (or generic) ESP32 chip |
 
-<img src="Documentation/images/126dcfe92fb7.webp" width="100%"/>
+It's easy to create your own RNodes from one of the supported development boards and devices. If a device or board you want to use is not yet supported, you are welcome to [join the effort](/CONTRIBUTING.md) and help create a board definition and pin mapping for it!
 
-<center><i>Where there is no Internet, RNodes will still communicate</i></center><br/><br/>
+<!--<img src="Documentation/images/devboards_1.webp" width="100%"/>-->
 
-The production of one particular RNode device is not an end, but the potential starting point of a new branch of devices on the tree of the RNode system as a whole.
+## Supported Transceiver Modules
+The RNode Firmware supports all transceiver modules based on the following chips:
+* Semtech SX1262
+* Semtech SX1276
+* Semtech SX1278
+* Semtech SX1280
 
-This tree fits into the larger biome of Free & Open Communications Systems, which I hope that you - by using communications tools like RNode - will help grow and prosper.
+These also must have an **SPI interface** and **DIO_0** pin connected to the MCU directly.
 
 ## One Tool, Many Uses
 
@@ -54,40 +73,29 @@ Depending on configuration, it can be used for local networking purposes, or to
 
 ## Types & Performance
 
-RNodes can be made in many different configurations, and can use many different radio bands, but they will generally operate in the **433 MHz**, **868 MHz**, **915 MHZ** and **2.4 GHz** bands. They will usually offer configurable on-air data speeds between just a **few hundred bits per second**, up to **a couple of megabits per second**. Maximum output power will depend on the transceiver and PA setup used, but will generally lie between **17 dbm** and **27 dBm**.
+RNodes can be made in many different configurations, and can use many different radio bands, but they will generally operate in the **433 MHz**, **868 MHz**, **915 MHZ** and **2.4 GHz** bands. They will usually offer configurable on-air data speeds between just a **few hundred bits per second**, up to **hundreds of kilobits per second**. Maximum output power will depend on the transceiver and PA setup used, but will generally lie between **17 dbm (50mW)** and **27 dBm (500mW)**.
 
 The RNode system has been designed to allow reliable systems for basic human communications, over very wide areas, while using very little power, being cheap to build, free to operate, and near impossible to censor.
 
 While **speeds are lower** than WiFi, typical communication **ranges are many times higher**. Several kilometers can be acheived with usable bitrates, even in urban areas, and over **100 kilometers** can be achieved in line-of-sight conditions.
 
-## Supported Boards & Devices
+## A Self-Replicating System
-It's easy to create your own RNodes from one of the supported development boards and devices. If a device or board you want to use is not yet supported, you are welcome to join the effort and help creating a board definition and pin mapping for it!
 
-<img src="Documentation/images/devboards_1.webp" width="100%"/>
+If you notice the presence of a circularity in the naming of the system as a whole, and the physical devices, it is no coincidence. Every RNode contains the seeds necessary to reproduce the system, the [RNode Bootstrap Console](https://unsigned.io/rnode_bootstrap_console), which is hosted locally on every RNode, and can be activated and accesses at any time - no Internet required.
 
-The RNode Firmware supports the following boards:
+The designs, guides and software stored within allows users to create more RNodes, and even to bootstrap entire communications networks, completely independently of existing infrastructure, or in situations where infrastructure has become unreliable or is broken.
 
-- Handheld v2.x RNodes from [unsigned.io](https://unsigned.io/shop/product/handheld-rnode)
+<img src="Documentation/images/126dcfe92fb7.webp" width="100%"/>
-- Original v1.x RNodes from [unsigned.io](https://unsigned.io/shop/product/rnode)
-- LilyGO T-Beam v1.1 devices with SX1276/8 LoRa chips
-- LilyGO T-Beam v1.1 devices with SX1262/8 LoRa chips
-- LilyGO LoRa32 v1.0 devices
-- LilyGO LoRa32 v2.0 devices
-- LilyGO LoRa32 v2.1 devices (with and without TCXO)
-- Heltec LoRa32 v2 devices
-- Heltec LoRa32 v3 devices
-- Homebrew RNodes based on ATmega1284p boards
-- Homebrew RNodes based on ATmega2560 boards
-- Homebrew RNodes based on Adafruit Feather ESP32 boards
-- Homebrew RNodes based on generic ESP32 boards
 
-## Supported Transceiver Modules
+<center><i>Where there is no Internet, RNodes will still communicate</i></center><br/><br/>
-The RNode Firmware supports all transceiver modules based on **Semtech SX1276** or **Semtech SX1278** chips, that have an **SPI interface** and expose the **DIO_0** interrupt pin from the chip.
+
+The production of one particular RNode device is not an end, but the potential starting point of a new branch of devices on the tree of the RNode system as a whole.
+
+This tree fits into the larger biome of Free & Open Communications Systems, which I hope that you - by using communications tools like RNode - will help grow and prosper.
 
-Support for **SX1262**, **SX1268** and **SX1280** is being implemented. Please support the project with donations if you want this faster!
 
 ## Getting Started Fast
-You can download and flash the firmware to all the supported boards using the [RNode Config Utility](https://github.com/markqvist/rnodeconfigutil). All firmware releases are now handled and installed directly through the `rnodeconf` utility, which is included in the `rns` package. It can be installed via `pip`:
+You can download and flash the firmware to all the supported boards using [rnodeconf](https://github.com/markqvist/Reticulum). All firmware releases are handled and installed directly through the `rnodeconf` utility, which is included in the `rns` package. It can be installed via `pip`:
 
 ```
 # Install rnodeconf via rns package
@@ -104,10 +112,18 @@ For more detailed instruction and in-depth guides, you can have a look at some o
 - Learn the basics on how to [create and build your own RNode designs](https://unsigned.io/guides/2022_01_26_how-to-make-your-own-rnodes.html) from scratch
 - Once you've got the hang of it, start building RNodes for your community, or [even for selling them](https://unsigned.io/sell_rnodes.html)
 
-If you would rather just buy a pre-made unit, you can visit [my shop](https://unsigned.io/shop) and purchase my particular version of the [Handheld RNode](https://unsigned.io/shop/handheld-rnode/), which I can assure you is made to the highest quality, and with a lot of care.
+## Support development
+### Hardware donations
+If you would like to see support added for a board which you possess, you may donate it to myself, Jacob Eva, so that I can implement support for it into this project. There will be no official timescale given for implementation however, but I will try my best when I have time :) Please [contact me (scroll to the bottom)](https://liberatedsystems.co.uk/about) if you wish to donate hardware to the project.
 
-## Support RNode Development
+### Purchasing products
-You can help support the continued development of open, free and private communications systems by donating via one of the following channels:
+You can support the development of the RNode Firmware CE project by purchasing RNodes (to come in the future) and other products from [Liberated Embedded systems](https://liberatedsystems.co.uk), my online business. For more information on my business, please see [here](https://liberatedsystems.co.uk/about/).
+
+From time to time the creator of the [Reticulum](https://reticulum.network) project, Mark Qvist, produces his own RNodes and sells them through his [shop](https://unsigned.io/shop). You may support the development of open, free and private communications systems through purchasing these from him.
+
+### Monetary donations
+I, the maintainer of this fork, am currently not accepting monetary donations. These are instead better directed to [Mark Qvist](https://unsigned.io), who created the original repository this one is based on, and is the core developer of the [Reticulum](https://reticulum.network) project, which is what the RNode Firmware was designed to supplement as a network adapter.
+You can help support the continued development of open, free and private communications systems by donating to him via one of the following channels:
 
 - Monero:
   ```
@@ -124,14 +140,15 @@ You can help support the continued development of open, free and private communi
 - Ko-Fi: https://ko-fi.com/markqvist
 
 ## License & Use
-The RNode Firmware is Copyright © 2024 Mark Qvist / [unsigned.io](https://unsigned.io), and is made available under the **GNU General Public License v3.0**. The source code includes an SX1276 driver that is released under MIT License, and Copyright © 2018 Sandeep Mistry / Mark Qvist.
+The upstream RNode Firmware is Copyright © 2024 Mark Qvist / [unsigned.io](https://unsigned.io).
+The modified RNode Firmware CE (community edition) is Copyright © Jacob Eva / [Liberated Embedded Systems](https://liberatedsystems.co.uk) and is made available under the **GNU General Public License v3.0**. 
 
-You can obtain the source code from [git.unsigned.io](https://git.unsigned.io/markqvist/RNode_Firmware) or [GitHub](https://github.com/markqvist/rnode_firmware).
+The source code includes an SX1276 driver that is released under MIT License, and Copyright © 2018 Sandeep Mistry / Mark Qvist. The SX126x and SX128x drivers are adaptations of this original driver.
 
-Every RNode also includes an internal copy of it's own firmware source code, that can be downloaded through the [RNode Bootstrap Console](https://unsigned.io/rnode_bootstrap_console), by putting the RNode into Console Mode (which can be activated by pressing the reset button two times within two seconds).
+You can obtain the source code from [my business Git instance](https://git.liberatedsystems.co.uk/jacobeva/RNode_Firmware_CE) or [GitHub](https://github.com/liberatedsystems/RNode_Firmware_CE).
+
+Every RNode which supports the console functionality also includes an internal copy of it's own firmware source code, that can be downloaded through the [RNode Bootstrap Console](https://unsigned.io/rnode_bootstrap_console), by putting the RNode into Console Mode (which can be activated by pressing the reset button two times within two seconds).
 
 The RNode Ecosystem is free and non-proprietary, and actively seeks to distribute it's ownership and control. If you want to build RNodes for commercial purposes, including selling them, you must do so adhering to the Open Source licenses that the various parts of the RNode project is released under, and under your own responsibility.
 
 If you distribute or modify this work, you **must** adhere to the terms of the GPLv3, including, but not limited to, providing up-to-date source code upon distribution, displaying appropriate copyright and license notices in prominent positions of all conveyed works, and making users aware of their rights to the software under the GPLv3.
-
-In practice, this means that you can use the firmware commercially, but you must understand your obligation to provide all future users of the system with the same rights, that you have been provided by the GPLv3. If you intend using the RNode Firmware commercially, it is worth reading [this page](https://unsigned.io/sell_rnodes.html).