== Summary ==
Installation Instructions for Linux on Bouffalo Lab BL808. Provided by Bouffalo Lab.

Ox64

2022-10-14T23:48:37Z

Lupyuen: Add SDK section

Ox64

2022-10-14T04:27:24Z

Lupyuen: Add article "First thoughts on the (a)symmetery of Bouffalo Labs BL808 as in Pine64’s Ox64"

PineCone

2022-10-14T01:50:39Z

Lupyuen: Add "Visual Programming with Zig and Apache NuttX Sensors (Video)"

[[File:Pine64_BL602_EVB_photo-3-small.jpg|thumb|PineCone BL602 EVB (Evaluation Board)]]

The '''PineCone''' is a BL602 evaluation board, which was developed with the goal to challenge the open source community to achieve blob-free and free and open source WiFi and Bluetooth, see the [https://www.pine64.org/2020/10/28/nutcracker-challenge-blob-free-wifi-ble/ Nutcracker Challenge].

== BL602 Specifications ==
* '''CPU:''' 32-bit RV32IMAFC RISC-V “SiFive E24 Core”
** [https://www.sifive.com/cores/e24 SiFive E24 Core information]
* '''Memory:'''
** 128KB ROM
** 276KB SRAM
** 1Kb eFuse
** 2MB Embedded Flash
* '''Security:'''
** Secure boot
** Secure debug
** AES 128/192/256
** SHA-1/224/256
** TRNG (True Random Number Generator)
** PKA (Public Key Accelerator)
* '''Wireless:'''
** Wi-Fi 802.11 b/g/n
** Bluetooth® Low Energy 5.0
** Wi-Fi Fast connection with BLE assistance
** Wi-Fi and BLE coexistence
** Wi-Fi Security WPS/WEP/WPA/WPA2/WPA3
** STA, SoftAP and sniffer modes
** Multi-Cloud connectivity
** 2.4 GHz RF transceiver
** Integrated RF balun, PA/LNA
* '''Package Type:'''
** 32 pin QFN 4mm x 4mm
* JTAG support (See below for BL602 impact)

[[File:BL602_Block_Diagram.jpg|600px]]

== JTAG ==
{| class="wikitable floatright"
|+ Default JTAG pins
|-
| GPIO Pin || JTAG Pin
|-
| GPIO17 || TDI
|-
| GPIO11 || TDO
|-
| GPIO12 || TMS
|-
| GPIO14 || TCK
|-
|}

BL602 multiplexes four GPIO pins to provide the familiar JTAG lines. See the accompanying table for the default pin mappings.

These are the default JTAG pins in use after a cold boot. However, many pieces of software, including the demo that's installed by default on new PineCones, remap these pins to other functions. You cannot use the default wiring for JTAG while such software is running. This issue is especially prevalent on the PineCone because three of the default JTAG pins are connected to the onboard RGB LED. Nothing about the LED itself interferes with JTAG, but any program that uses the LED will necessarily remap some of the default JTAG pins to be GPIO.

The MaskROM download mode that the BL602 enters when you tie GPIO8 high does '''not''' remap the default JTAG pins, and so you can and should use that mode while checking basic functionality of your JTAG adapter.

Note that, just as software can remap the default JTAG pins to be something else, it can also remap other pins to be JTAG. Control over this is quite granular, with 5-6 candidate pins for each individual JTAG signal that can be mapped independently of one another. LEE Lup Yuen has written some [https://lupyuen.github.io/articles/openocd#free-the-led-from-jtag-port sample code] showing how to remap the JTAG pins so that your software can use the LED without giving up support for debugging.

== Pine64 USB JTAG Adapter information and schematics ==
* [https://files.pine64.org/doc/Pinenut/PINE64%20USB%20JTAG%20Adapter%20Schematic-20201215.pdf PINE64 USB JTAG Adapter Schematic-20201215.pdf (pine64_ft232hl_board-2020-12-14)]
* [[:File:PINE64_USB_JTAG_Adapter_Schematic_ver_1.0a-20210109.pdf|PINE64 USB JTAG Adapter schematic 20210109 1.0a]]

== PineCone BL602 EVB information and schematics ==
* Approximate dimensions: 26mm x 43mm
* Board layout:
[[File:PADI-II_EVB.png]]
* [https://files.pine64.org/doc/Pinenut/Pine64%20BL602%20EVB%20Schematic%20ver%201.1.pdf PineCone BL602 EVB schematic ver 1.1]
** Note: In PineCone revision 1.1 ("BL62B_EVB V1.1" silkscreened on back of board), CC1 and CC2 share one 5.1KΩ resistor. This means the board will fail to power when you use an e-marked USB-C cable like the one that comes with Apple chargers. See [https://medium.com/@leung.benson/how-to-design-a-proper-usb-c-power-sink-hint-not-the-way-raspberry-pi-4-did-it-f470d7a5910 this article] for details of why this happens. The next schematic design will give each line its own 5.1KΩ resistor as per the USB-C specification.
* The board uses a CH340 Serial/USB adapter. This chip is commonly used in Arduino-class development boards. It is a full speed (12Mbps) USB interface and has vendor ID 0x1a86 with product ID 0x7523.
* The GPIO pins (11, 12, 14, 17) plus the nearby RESET, POWER, and GND pins are all located on one side of the board, on J1 to provide JTAG connection.

== Pinenut-01S Module information and schematics ==
[[File:Pinenut-01S_PCB-Front.png|225px]][[File:Pinenut-01S_PCB-Back.png|225px]]
* [https://files.pine64.org/doc/Pinenut/Pinenut-01S%20V1.01%20SCH.pdf Pinenut-01S schematic ver 1.01]
* [https://wiki.pine64.org/images/6/6b/PineNut-01S_v1.01_KiCad.zip PineNut-01S KiCad schematic ver 1.01]
* [https://files.pine64.org/doc/Pinenut/NUT-01S%20GPIO%20Definition%20ver%201.0.pdf Pinenut-01S GPIO Definition ver 1.0]
* [https://files.pine64.org/doc/Pinenut/USB%20Adapter%20for%20Pinenut-01S%20Schematic%20V1.0.pdf USB Programmer adapter for Pinenut-01S schematic ver 1.0]
* The default firmware runs the UART at 2000000 bps. It will accept input whilst regularly outputting:<code> proc_hellow_entry: RISC-V rv32imafc cur key status:1</code>

== Pinenut-12S Module information ==
[[File:NUT-12S_module-front.jpg|200px]][[File:NUT-12S_module-back.jpg|200px]]
* [https://files.pine64.org/doc/Pinenut/NUT-12S%20GPIO%20Definition%20ver%201.0.pdf Pinenut-12S GPIO Definition ver 1.0]
* Onboard LED is connected to IO0

== Datasheets for components and peripherals ==
* Bouffalo BL-602 SoC information:
** [https://github.com/bouffalolab/bl_docs Bouffalo Lab's official bl_docs repository]: should always contain the latest SoC documentation available, in PDF, HTML, and reStructuredText source forms.
** [https://github.com/pine64/bl602-docs/tree/main/mirrored PINE64's bl602-docs repository]: contains an archive of all historical datasheets and reference manual PDFs but may lag behind Bouffalo's official repository. If you notice that it is, please submit a pull request!
* USB/Serial adapter:
** [https://cdn.sparkfun.com/datasheets/Dev/Arduino/Other/CH340DS1.PDF CH340 serial converter]

== Misc notes ==
Planned to be available in at least three form factors:
* NUT-01S -> ESP-01S
* NUT-12S -> ESP-12S
* NUT-15 -> RTL8723/AMPAK

== Loading code ==
To load code, you must move the jumper to the position closest to the edge, press reset, load the code, move the jumper back toward the center of the board, and press reset again.

There are currently a number of loaders in progress, each with differing degrees of completeness and success on various operating systems.
* In the build tree, there is BLFlashCube for Windows, which is a proprietary GUI for flashing images. Linux and macOS binaries are available via [https://dev.bouffalolab.com/download Bouffalo Lab's developer portal].
* [https://github.com/stschake/bl60x-flash bl60x-flash] is in Python and has been reported successful on MacOS catalina (10.15.6) by Punnerud and madushan1000.
* [https://github.com/bouffalolab/BLOpenFlasher BLOpenFlasher] is a WIP, written in go, by Bouffalo Labs to provide source for a flash utility.
* [https://github.com/renzenicolai/bl602tool bl602tool] is a Python utility in development.
* <del>[https://pypi.org/project/bflb-eflash-loader/ Bouffalo's Python Flash Loader] is a new (Dec 20) flash loader by the makers of the chip.</del>
* <del>[https://pypi.org/project/bflb-image-build/ Bouffalo's image build] smooshes code and adds headers for downloads.</del>
* [https://pypi.org/project/bflb-mcu-tool/ Bouffalo's MCU tool] (Mar 2021) Python image tool replaced both of the above. Now combined with eflash loader, deals with partitions, DTS, signing, fuses etc.
* [https://github.com/spacemeowx2/blflash blflash serial flasher] BL602 serial flasher, inspired by BLOpenFlasher

== Development efforts ==
* [https://github.com/pine64/bl_iot_sdk PineCone BL602 GitHub Page (PINE64 fork)] has compilers, linkers, and all the code to build on Windows, Linux (x86_64), and MacOS.
* [https://github.com/bouffalolab/bl_iot_sdk Bouffalo Lab GitHub Page]
* [https://github.com/renzenicolai/bl602-docs/ BL602 Developer organize documentation GitHub Page]
* [https://github.com/renzenicolai/bl602tool BL602 Developer organize tool GitHub Page]
* [https://github.com/stschake/bl60x-flash Programming tool for Bouffalo Labs BL602/BL604 chips]
* [https://github.com/pine64/bl602-re BL602 reverse engineering working group]
* [https://github.com/pine64/bl602-sdio-linux Linux kernel module]
* [https://github.com/tchebb/bl602-docs BL602 Documentation]
* [https://github.com/spacemeowx2/blflash BL602 serial flasher]
* [https://github.com/mkroman/awesome-bouffalo#feature-matrix Awesome Bouffalo]

== Articles and Blogs ==
* [https://lupyuen.github.io/articles/pinecone Quick Peek of PineCone BL602 RISC-V Evaluation Board by Lup Yuen]
* [https://maero.dk/bl602-firmware-image-format/ Documenting the BouffaloLab BL602 firmware image format by MK]
* [https://lupyuen.github.io/articles/openocd Connect PineCone BL602 to OpenOCD by Lup Yuen]
* [https://lupyuen.github.io/articles/debug Debug Rust on PineCone BL602 with VSCode and GDB by Lup Yuen]
* [https://lupyuen.github.io/articles/mynewt Porting Mynewt to PineCone BL602 by Lup Yuen]
* [https://lupyuen.github.io/articles/flash Flashing Firmware to PineCone BL602 by Lup Yuen]
* [https://lupyuen.github.io/articles/led Control PineCone BL602 RGB LED with GPIO and PWM by Lup Yuen]
* [https://lupyuen.github.io/articles/gpio Mynewt GPIO ported to PineCone BL602 RISC-V Board by Lup Yuen]
* [https://lupyuen.github.io/articles/i2c PineCone BL602 talks to I2C Sensors by Lup Yuen]
* [https://lupyuen.github.io/articles/spi PineCone BL602 talks SPI too! by Lup Yuen]
* [https://lupyuen.github.io/articles/display PineCone BL602 Blasting Pixels to ST7789 Display with LVGL Library by Lup Yuen]
* [https://lupyuen.github.io/articles/uart PineCone BL602 Talks UART to Grove E-Ink Display by Lup Yuen]
* [https://lupyuen.github.io/articles/book The RISC-V BL602 Book by Lup Yuen]
* [https://lupyuen.github.io/articles/lora Connect PineCone BL602 to LoRa Transceiver by Lup Yuen]
* [https://lupyuen.github.io/articles/wisblock RAKwireless WisBlock talks LoRa with PineCone BL602 RISC-V Board by Lup Yuen]
* [https://lupyuen.github.io/articles/lora2 PineCone BL602 RISC-V Board Receives LoRa Packets by Lup Yuen]
* [https://lupyuen.github.io/articles/rust Run Rust RISC-V Firmware with BL602 IoT SDK by Lup Yuen]
* [https://lupyuen.github.io/articles/lorawan PineCone BL602 Talks LoRaWAN by Lup Yuen]
* [https://lupyuen.github.io/articles/lisp uLisp and Blockly on PineCone BL602 RISC-V Board by Lup Yuen]
* [https://lupyuen.github.io/articles/wasm Simulate RISC-V BL602 with WebAssembly, uLisp and Blockly by Lup Yuen]
* [https://lupyuen.github.io/articles/boot BL602 Bootloader by Lup Yuen]
* [https://lupyuen.github.io/articles/tflite Machine Learning on RISC-V BL602 with TensorFlow Lite by Lup Yuen]
* [https://lupyuen.github.io/articles/wifi Reverse Engineering WiFi on RISC-V BL602 by Lup Yuen]
* [https://lupyuen.github.io/articles/adc Rust on RISC-V BL602: Is It Sunny? by Lup Yuen]
* [https://lupyuen.github.io/articles/rustsim Rust on RISC-V BL602: Simulated with WebAssembly by Lup Yuen]
* [https://lupyuen.github.io/articles/pinedio PineDio Stack BL604 RISC-V Board: Testing The Prototype by Lup Yuen]
* [https://lupyuen.github.io/articles/rhai Rust on RISC-V BL602: Rhai Scripting by Lup Yuen]
* [https://lupyuen.github.io/articles/lorawan2 LoRaWAN on PineDio Stack BL604 RISC-V Board by Lup Yuen]
* [https://lupyuen.github.io/articles/ttn The Things Network on PineDio Stack BL604 RISC-V Board by Lup Yuen]
* [https://lupyuen.github.io/articles/cbor Encode Sensor Data with CBOR on BL602 by Lup Yuen]
* [https://lupyuen.github.io/articles/roblox IoT Digital Twin with Roblox and The Things Network by Lup Yuen]
* [https://lupyuen.github.io/articles/tsen Internal Temperature Sensor on BL602 by Lup Yuen]
* [https://lupyuen.github.io/articles/payload CBOR Payload Formatter for The Things Network by Lup Yuen]
* [https://lupyuen.github.io/articles/prometheus Monitor IoT Devices in The Things Network with Prometheus and Grafana by Lup Yuen]
* [https://lupyuen.github.io/articles/nuttx Apache NuttX OS on RISC-V BL602 and BL604 by Lup Yuen]
* [https://lupyuen.github.io/articles/spi2 SPI on Apache NuttX OS by Lup Yuen]
* [https://lupyuen.github.io/articles/sx1262 LoRa SX1262 on Apache NuttX OS by Lup Yuen]
* [https://lupyuen.github.io/articles/lorawan3 LoRaWAN on Apache NuttX OS by Lup Yuen]
* [https://lupyuen.github.io/articles/rust2 Rust on Apache NuttX OS by Lup Yuen]
* [https://lupyuen.github.io/articles/auto Auto Flash and Test NuttX on RISC-V BL602 by Lup Yuen]
* [https://lupyuen.github.io/articles/loader BL602 EFlash Loader: Reverse Engineered with Ghidra by Lup Yuen]
* [https://lupyuen.github.io/articles/ikea Connect IKEA Air Quality Sensor to Apache NuttX OS by Lup Yuen]
* [https://lupyuen.github.io/articles/bme280 Apache NuttX Driver for BME280 Sensor: Ported from Zephyr OS by Lup Yuen]
* [https://lupyuen.github.io/articles/rusti2c Rust talks I2C on Apache NuttX RTOS by Lup Yuen]
* [https://lupyuen.github.io/articles/st7789 ST7789 Display with LVGL Graphics on Apache NuttX RTOS by Lup Yuen]
* [https://lupyuen.github.io/articles/pinedio2 PineDio Stack BL604 runs Apache NuttX RTOS by Lup Yuen]
* [https://lupyuen.github.io/articles/touch NuttX Touch Panel Driver for PineDio Stack BL604 by Lup Yuen]
* [https://www.robertlipe.com/buttons-on-bl602-nuttx/ Buttons on BL602 NuttX]
* [https://lupyuen.github.io/articles/expander NuttX GPIO Expander for PineDio Stack BL604 by Lup Yuen]
* [https://lupyuen.github.io/articles/auto2 (Mostly) Automated Testing of Apache NuttX RTOS on PineDio Stack BL604 RISC-V Board by Lup Yuen]
* [https://lupyuen.github.io/articles/zig Zig on RISC-V BL602: Quick Peek with Apache NuttX RTOS by Lup Yuen]
* [https://lupyuen.github.io/articles/iot Build an IoT App with Zig and LoRaWAN by Lup Yuen]
* [https://lupyuen.github.io/articles/lvgl Build an LVGL Touchscreen App with Zig by Lup Yuen]
* [https://lupyuen.github.io/articles/sensor Read NuttX Sensor Data with Zig by Lup Yuen]
* [https://lupyuen.github.io/articles/visual Visual Programming with Zig and NuttX Sensors by Lup Yuen]
* [https://youtu.be/1O5Eb8bKxXA Visual Programming with Zig and Apache NuttX Sensors (Video)]

[[Category:Nutcracker]]

Pinedio

2022-10-14T01:50:17Z

Lupyuen: Add "Apache NuttX RTOS on a RISC-V IoT Gadget: PineDio Stack BL604 (Video)" and "Simpler, safer LVGL Touchscreen Apps with Zig and Apache NuttX RTOS (Video)"

{{under construction}}

The '''Pinedio''' is a device utilizing LoRa. LoRa is a long range, low power wireless platform that is being used by a lot of Internet of Things (IoT) products. Using LoRa and LoRaWAN, devices can communicate across the world using the internet, using various decentralised networks such as [https://www.thethingsnetwork.org/ The Things Network] or [https://www.helium.com/ Helium]. Since, PINE64 believes in openness, the LoRa gateway can connect to any network, per the developer implementation. If Helium Spots open up for PINE64 gateway and developers have implemented the hook for Helium, then this is good thing. The PINE64 LoRa gateway also open connect to The Things Network if developers implement support. The choice is yours!

== Gateway ==

The gateway will be available in two variants - indoor and outdoor. All that is known about the outdoor unit is that it will have "an aluminum, rugged and water resistant case".
The indoor unit consists of a PINE A64-LTS, fitted with a purpose built hat (adapter) which uses a LoRa module by RakWireless. The chipset used is the SX1302, and the module via the SPI interface. There are two external connections on the enclosure for the GPS and loRa antenna.

=== Connections ===
* GPS is connected to UART2 on the A64 board
* SX1302 on SPI0

{| class="wikitable"
|RAK2287 module
|PI-2 connector
|PINE A64-LTS
|-
|SX1302 SPI
|Pin 19 = MOSI / PC0 Pin 21 = MISO/PC1 Pin23 = CLK/PC2 Pin24 = CS/PC3
|SPI0 (/dev/spidev0.0)
|-
|SX1302 RESET
|Pin 11 = GPIO17/PC7
|GPIO71 (/sys/class/gpio/gpio71)
|-
|GPS UART
|Pin 8 = TX/ Pin 10 = RX
|UART2 (/dev/ttyS2)
|-
|GPS RESET
|Pin 33 = GPIO13/PC5
|GPIO69 (/sys/class/gpio/gpio69)
|-
|GPS Standby
|Pin 35 = GPIO19/PC9
|GPIO73 (/sys/class/gpio/gpio73)
|}

=== Pictures ===
<gallery>
File:Blog-april-InsideLoRaGateway.jpg
File:Blog-april-InsideLoRaGateway2.jpeg
File:Discord-lora-gateway-20210413_143615.jpg
File:Discord-lora-gateway-20210413_1435271.jpg
</gallery>

=== Operating System Options===

Pinedio Gateway carries the A64-LTS board. Based on ram specifications SOPINE images are also compatible.

====Armbian====

Gateway Hardware based on Pine64 A64-LTS + RAK2287 + GPS.

Hardware compatible with SOPINE images.

'''PineDio Gateway TTN/Chirpstack Image'''

Debian image with (Default Choices: Chirpstack / TTN) software preinstalled / hardware enabled, available below.

Latest:
(PineDio-RAK-Armbian_09-25-2022.img.xz)

SHA256: 487bbb45ac78a4ee24b80918760673e58222aec60c81251617e932a8265d35b7
SHA512: f21ee4e8b8739f2e0efc269ab158224d6dfc55b3d542118fb67286b5337a2499cda52f3df1f05db6b1202553fe227c6b90509275ec4a411b3972f9aefacc5364

DOWNLOAD LOCATION: https://mega.nz/file/zB4gTLRZ#EUlJh2oYLgkfkphPBmQ8ufzQu9_b3nYFDGoXle4xyAk

'''Switch Between Chirpstack / TTN (TheThingsNetwork)'''

gateway-config

First Select:

Setup RAK Gateway Channel Plan

Next For TTN (TheThingsNetwork) Select:

Server is TTN

'''or'''

Next For Chirpstack Select:

Server is Other server

'''Accessing Chirpstack Admin Page'''

Point web browser to:

http://gatewayIPaddress:8080

'''Default Chirpstack Credentials'''

login: admin
password: admin

'''SSH Credentials'''

Login: pinedio
password: SoPinePass!!!

'''Changing EUI'''

EUI stored in file:

/opt/ttn-gateway/packetforwarder/lorapkt_fwd/local_conf.json

(edit EUI file above if you wish change it, and run: sudo systemctl restart ttn-gateway)

'''Additional Shell Commands'''

'''View Gateway ID/EUI'''

gateway-version

'''Restart Packet Forwarder/Concentrator'''

sudo systemctl restart ttn-gateway

'''Check Status'''

sudo systemctl status ttn-gateway

'''Enabling Concentrator/GPS Steps (Below Already *Completed* For Above Image Download)'''

Inside armbian-config -> system -> Bootenv (edit boot environment), enter the following 2 lines (to create spidev0.0):

overlays=spi-spidev uart2 i2c0
param_spidev_spi_bus=0

Or you may hand edit: /boot/armbianEnv.txt to add the above overlays/param_spidev_spi_bus lines.

Save. Reboot.

After rebooting you should see a new device /dev/spidev0.0. This will be the concentrator device for gateway related setup.

GPS will be /dev/ttyS2 and should work (after editing armbianEnv.txt + reboot).
Make sure to offer GPS antenna a strong signal, preferably by a window (if indoors).

== USB adapter ==
[[File:Pine64-lora-usb-adapter.jpg|500px]]

The Pine64 USB LoRa adapter is based on the Semtech SX1262 LoRa module and the CH341 USB bus converter chip. The '''CH341''' chip can be configured in multiple mode to convert USB to various serial and parallel ports. In this case, it's configured in '''synchronous serial mode''', which allows this chip to convert from USB to the SPI bus needed to talk to the SX1262 LoRa module:

-------- --------------------------
| | | USB LoRa Adapter |
| PC | <--USB--> | CH341 <--SPI--> SX1262 |
| | | <--I/O--> |
-------- --------------------------

=== Pins ===
[[File:Lora-usb-pins.jpg|500px]]

{| class="wikitable"

!SX1262 Pin
!Name
!Description
|-
|1
|ANT
|Antenna
|-
|2
|GND2
|
|-
|3
|VREG
|
|-
|4
|DCC
|
|-
|5
|VCC
|
|-
|6
|DIO1
|Connected on CH341 Pin 7
|-
|7
|DIO2
|Connected on CH341 Pin6
|-
|8
|DIO3
|Connected on CH341 Pin 5
|-
|9
|GND
|
|-
|10
|MISO
|SPI MISO (CH341 Pin 20)
|-
|11
|MOSI
|SPI MOSI (CH341 Pin 22)
|-
|12
|SCK
|SPI clock (CH341 Pin 24)
|-
|13
|NSS
|SPI Chip select
|-
|14
|POR
|Reset pin
|-
|15
|Busy
|Busy pin
|-
|16
|GND
|
|}

=== Kernel module for CH341 ===
We need a driver for the CH341 USB bus converter chip. This driver will allow us to send command to the CH341 (SPI messages and access to the GPIOs). I've successfully build and run [https://github.com/rogerjames99/spi-ch341-usb this driver from '''rogerjames99'''] on my desktop computer (running Manjaro Linux) and on my Pinebook Pro (ARM64, running Manjaro ARM Linux). For any kernel newer than 3.10 but mandatory for kernels newer than 5.15 you need to use the [https://github.com/dimich-dmb/spi-ch341-usb dimich-dmb fork of the the '''spi-ch341-usb driver.'''] This fork has updated documentation for the newer kernel interfaces. If this driver gives you problems please drop by any of the social platforms in the Pine64 LoRa chat and give a holler, and if you are using a 5.15 or older kernel you can use the rogerjames99 fork.

$ git clone https://github.com/rogerjames99/spi-ch341-usb.git
or
$ git clone https://github.com/dimich-dmb/spi-ch341-usb.git
then
$ cd spi-ch341-usb
$ make
$ sudo make install

Once the driver is installed, unload the module ''ch341'' if it has been automatically loaded:

$ lsmod |grep ch341
$ sudo rmmod ch341

On my setup, ''ch341'' would be automatically loaded once I connected my USB adapter. This module drives the CH341 is asynchronous serial mode, which will not work for a SPI bus.

Then load the new module:

$ sudo modprobe spi-ch341-usb

Plug your USB adapter and check that the module is correctly loaded :

$ dmesg
[20141.872107] usb 1-1.1: USB disconnect, device number 4
[20143.820756] usb 1-1.1: new full-speed USB device number 5 using ehci-platform
[20143.973366] usb 1-1.1: New USB device found, idVendor=1a86, idProduct=5512, bcdDevice= 3.04
[20143.973413] usb 1-1.1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[20143.973434] usb 1-1.1: Product: USB UART-LPT
[20143.975137] spi-ch341-usb 1-1.1:1.0: ch341_usb_probe: connect device
[20143.975164] spi-ch341-usb 1-1.1:1.0: ch341_usb_probe: bNumEndpoints=3
[20143.975183] spi-ch341-usb 1-1.1:1.0: ch341_usb_probe: endpoint=0 type=2 dir=1 addr=2
[20143.975206] spi-ch341-usb 1-1.1:1.0: ch341_usb_probe: endpoint=1 type=2 dir=0 addr=2
[20143.975229] spi-ch341-usb 1-1.1:1.0: ch341_usb_probe: endpoint=2 type=3 dir=1 addr=1
[20143.975254] spi-ch341-usb 1-1.1:1.0: ch341_cfg_probe: output cs0 SPI slave with cs=0
[20143.975273] spi-ch341-usb 1-1.1:1.0: ch341_cfg_probe: output cs0 gpio=0 irq=0
[20143.975295] spi-ch341-usb 1-1.1:1.0: ch341_cfg_probe: output cs1 SPI slave with cs=1
[20143.975313] spi-ch341-usb 1-1.1:1.0: ch341_cfg_probe: output cs1 gpio=1 irq=1
[20143.975334] spi-ch341-usb 1-1.1:1.0: ch341_cfg_probe: output cs2 SPI slave with cs=2
[20143.975352] spi-ch341-usb 1-1.1:1.0: ch341_cfg_probe: output cs2 gpio=2 irq=2
[20143.975373] spi-ch341-usb 1-1.1:1.0: ch341_cfg_probe: input gpio4 gpio=3 irq=3
[20143.975394] spi-ch341-usb 1-1.1:1.0: ch341_cfg_probe: input gpio6 gpio=4 irq=4
[20143.975415] spi-ch341-usb 1-1.1:1.0: ch341_cfg_probe: input err gpio=5 irq=5
[20143.975435] spi-ch341-usb 1-1.1:1.0: ch341_cfg_probe: input pemp gpio=6 irq=6
[20143.975456] spi-ch341-usb 1-1.1:1.0: ch341_cfg_probe: input int gpio=7 irq=7 (hwirq)
[20143.975478] spi-ch341-usb 1-1.1:1.0: ch341_cfg_probe: input slct gpio=8 irq=8
[20143.975499] spi-ch341-usb 1-1.1:1.0: ch341_cfg_probe: input wait gpio=9 irq=9
[20143.975520] spi-ch341-usb 1-1.1:1.0: ch341_cfg_probe: input autofd gpio=10 irq=10
[20143.975542] spi-ch341-usb 1-1.1:1.0: ch341_cfg_probe: input addr gpio=11 irq=11
[20143.975564] spi-ch341-usb 1-1.1:1.0: ch341_cfg_probe: output ini gpio=12 irq=12
[20143.975585] spi-ch341-usb 1-1.1:1.0: ch341_cfg_probe: output write gpio=13 irq=13
[20143.975607] spi-ch341-usb 1-1.1:1.0: ch341_cfg_probe: output scl gpio=14 irq=14
[20143.975628] spi-ch341-usb 1-1.1:1.0: ch341_cfg_probe: output sda gpio=15 irq=15
[20143.975650] spi-ch341-usb 1-1.1:1.0: ch341_spi_probe: start
[20143.975677] spi-ch341-usb 1-1.1:1.0: ch341_spi_probe: SPI master connected to SPI bus 1
[20143.977831] spi-ch341-usb 1-1.1:1.0: ch341_spi_probe: SPI device /dev/spidev1.0 created
[20143.978183] spi-ch341-usb 1-1.1:1.0: ch341_spi_probe: SPI device /dev/spidev1.1 created
[20143.978552] spi-ch341-usb 1-1.1:1.0: ch341_spi_probe: SPI device /dev/spidev1.2 created
[20143.978726] spi-ch341-usb 1-1.1:1.0: ch341_spi_probe: done
[20143.978735] spi-ch341-usb 1-1.1:1.0: ch341_irq_probe: start
[20143.979133] spi-ch341-usb 1-1.1:1.0: ch341_irq_probe: irq_base=103
[20143.979154] spi-ch341-usb 1-1.1:1.0: ch341_irq_probe: done
[20143.979162] spi-ch341-usb 1-1.1:1.0: ch341_gpio_probe: start
[20143.979220] spi-ch341-usb 1-1.1:1.0: ch341_gpio_get_direction: gpio=cs0 dir=0
[20143.979229] spi-ch341-usb 1-1.1:1.0: ch341_gpio_get_direction: gpio=cs1 dir=0
[20143.979237] spi-ch341-usb 1-1.1:1.0: ch341_gpio_get_direction: gpio=cs2 dir=0
[20143.979245] spi-ch341-usb 1-1.1:1.0: ch341_gpio_get_direction: gpio=gpio4 dir=1
[20143.979253] spi-ch341-usb 1-1.1:1.0: ch341_gpio_get_direction: gpio=gpio6 dir=1
[20143.979260] spi-ch341-usb 1-1.1:1.0: ch341_gpio_get_direction: gpio=err dir=1
[20143.979268] spi-ch341-usb 1-1.1:1.0: ch341_gpio_get_direction: gpio=pemp dir=1
[20143.979275] spi-ch341-usb 1-1.1:1.0: ch341_gpio_get_direction: gpio=int dir=1
[20143.979283] spi-ch341-usb 1-1.1:1.0: ch341_gpio_get_direction: gpio=slct dir=1
[20143.979290] spi-ch341-usb 1-1.1:1.0: ch341_gpio_get_direction: gpio=wait dir=1
[20143.979298] spi-ch341-usb 1-1.1:1.0: ch341_gpio_get_direction: gpio=autofd dir=1
[20143.979306] spi-ch341-usb 1-1.1:1.0: ch341_gpio_get_direction: gpio=addr dir=1
[20143.979314] spi-ch341-usb 1-1.1:1.0: ch341_gpio_get_direction: gpio=ini dir=0
[20143.979321] spi-ch341-usb 1-1.1:1.0: ch341_gpio_get_direction: gpio=write dir=0
[20143.979329] spi-ch341-usb 1-1.1:1.0: ch341_gpio_get_direction: gpio=scl dir=0
[20143.979337] spi-ch341-usb 1-1.1:1.0: ch341_gpio_get_direction: gpio=sda dir=0
[20143.979831] spi-ch341-usb 1-1.1:1.0: ch341_gpio_probe: registered GPIOs from 496 to 511
[20143.981152] spi-ch341-usb 1-1.1:1.0: ch341_gpio_probe: done
[20143.981212] spi-ch341-usb 1-1.1:1.0: ch341_gpio_poll_function: start
[20143.981291] spi-ch341-usb 1-1.1:1.0: ch341_usb_probe: connected
[20144.756250] usbcore: registered new interface driver ch341
[20144.756334] usbserial: USB Serial support registered for ch341-uart

With kernel 5.16 and newer the output is shorter:

$ dmesg
[ 6744.813564] usb 1-2.1.1: new full-speed USB device number 21 using xhci_hcd
[ 6744.904377] usb 1-2.1.1: New USB device found, idVendor=1a86, idProduct=5512, bcdDevice= 3.04
[ 6744.904383] usb 1-2.1.1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 6744.904385] usb 1-2.1.1: Product: USB UART-LPT
[ 6744.960243] spi-ch341-usb 1-2.1.1:1.0: ch341_cfg_probe: output cs0 SPI slave with cs=0
[ 6744.960246] spi-ch341-usb 1-2.1.1:1.0: ch341_cfg_probe: output cs1 SPI slave with cs=1
[ 6744.960247] spi-ch341-usb 1-2.1.1:1.0: ch341_cfg_probe: output cs2 SPI slave with cs=2
[ 6744.960249] spi-ch341-usb 1-2.1.1:1.0: ch341_cfg_probe: input gpio4 gpio=0 irq=0 (hwirq)
[ 6744.960251] spi-ch341-usb 1-2.1.1:1.0: ch341_cfg_probe: input gpio5 gpio=1 irq=1
[ 6744.960302] spi-ch341-usb 1-2.1.1:1.0: ch341_spi_probe: SPI master connected to SPI bus 0
[ 6744.960350] spi-ch341-usb 1-2.1.1:1.0: ch341_spi_probe: SPI device /dev/spidev0.0 created
[ 6744.960398] spi-ch341-usb 1-2.1.1:1.0: ch341_spi_probe: SPI device /dev/spidev0.1 created
[ 6744.960445] spi-ch341-usb 1-2.1.1:1.0: ch341_spi_probe: SPI device /dev/spidev0.2 created
[ 6744.960583] spi-ch341-usb 1-2.1.1:1.0: ch341_usb_probe: connected

=== Driver development ===
=====Kernels 5.14 and older=====

Once the module ''spi-ch341-usb'' is correctly loaded, here's how you can transfer data on the SPI bus (in C):

/* Open the SPI bus */
int spi = open("/dev/spidev1.0", O_RDWR);
uint8_t mmode = SPI_MODE_0;
uint8_t lsb = 0;
ioctl(spi, SPI_IOC_WR_MODE, &mmode);
ioctl(spi, SPI_IOC_WR_LSB_FIRST, &lsb);

/* Transfer data */
/* TODO: Init buffer_out, buffer_in and size */
const uint8_t *mosi = buffer_out; // output data
uint8_t *miso = buffer_in; // input data

struct spi_ioc_transfer spi_trans;
memset(&spi_trans, 0, sizeof(spi_trans));

spi_trans.tx_buf = (unsigned long) mosi;
spi_trans.rx_buf = (unsigned long) miso;
spi_trans.cs_change = true;
spi_trans.len = size;

int status = ioctl (spi, SPI_IOC_MESSAGE(1), &spi_trans);

To access GPIOs, you first need to export them (to make them accessible via ''/sys/class/gpio''. As you can see in the dmesg output, GPIOs from 496 to 511 were registered, which means we can export 16 GPIOs. The mapping of these I/O is available in the [https://github.com/rogerjames99/spi-ch341-usb/blob/master/spi-ch341-usb.c#L148 source code of the driver]. For example, pin ''slct'' is the 12th, meaning we need to export GPIO 496+12 = 508.

int fd;
if ((fd = open("/sys/class/gpio/export", O_WRONLY)) == -1) {
perror("open ini");
exit(-1);
}

if (write(fd, "508", 3) == -1){
perror ("write export 508");
}

Once exported, the GPIO is available in ''/sys/class/gpio/sclt'' (the naming is specified by the driver). You can read the pin in C:

int fd;
if ((fd = open("/sys/class/gpio/slct/value", O_RDWR)) == -1) {
perror("open");
}

char buf;
if (read(fd, &buf, 1) == -1) {
perror("read");
}

int value = (buf == '0') ? 0 : 1;

You can also write it:

int fd;
if ((fd = open("/sys/class/gpio/ini/value", O_RDWR)) == -1) {
perror("open ini");
}

if (write(fd, value ? "1" : "0", 1) == -1) {
perror ("write");
}

=====Kernel 5.15 and newer=====

We need some help documenting how these interfaces work!

The driver creates these interfaces:
{| class="wikitable"
|Pin ||SPI Function ||GPIO function ||GPIO name ||IRQ
|-
|15||CS0||-||-||-
|-
|16||CS1||-||-||-
|-
|17||CS2||-||-||-
|-
|19||-||Input||gpio4||hardware
|-
|21||-||Input||gpio5||software
|}

The dimich-dmb fork of spi-ch341-usb works with 5.15+ kernels, but as you can see above it is not configured for the needs of the Pinedio-USB by default. I have started a branch in my fork to work on getting the driver pre-configured for our needs. The branch can be [https://github.com/UncleGrumpy/spi-ch341-usb/tree/pinedio found here.] Please feel free to help! And open issues or discussions in the repo if you have problems or ideas how to help. Any improvements to the actual code beyond configuration should be pushed to the temporary [https://github.com/dimich-dmb/spi-ch341-usb/ upstream.]

Since linux-5.15 binding to spidev driver is required to make slave devices available via /dev/, e.g. for slave 1 on bus 0 as real root (not with sudo):

# echo spidev > /sys/class/spi_master/spi0/spi0.1/driver_override
# echo spi0.1 > /sys/bus/spi/drivers/spidev/bind

For all devices handled by spi_ch341_usb driver (again, only as real root):

# for i in /sys/bus/usb/drivers/spi-ch341-usb/*/spi_master/spi*/spi*.*; do echo spidev > $i/driver_override; echo $(basename $i) > /sys/bus/spi/drivers/spidev/bind; done

The documentation found at https://github.com/dimich-dmb/spi-ch341-usb/blob/master/README.md has more information.

The 5.15+ driver is not ready yet. But if you are interested in testing, helping to get the configuration right, or working on application development you can build and test the current driver:

$ git clone -b pinedio https://github.com/UncleGrumpy/spi-ch341-usb.git
$ cd spi-ch341-usb
$ make
$ sudo make install

So far this will automatically set up the SPI slave device /dev/spi0.0. It names the ch341-usb device as "pinedio" this will allow application developers to find the correct gpiochip by name. I need help confirming the correct gpio pins but as of now the driver will setup the following configuration:

The driver uses following CH341A pins for the SPI interface.
{| class="wikitable"
| Pin || Name || Direction || Function SPI (CH341A)
|-
| 18 || D3 || output || SCK (DCK)
|-
| 20 || D5 || output || MOSI (DOUT)
|-
| 22 || D7 || input || MISO (DIN)
|-
| 15 || D0 || output || CS0
|}

The driver uses the following GPIO configuration. I am not at all sure these are the correct pins to use! This is one area that I could really use some help with!!!
{| class="wikitable
| CH341 Pin || CH341A Name || Function || GPIO Name || GPIO Configuration || SX1262 connection
|-
| 7 || INT# || IRQ || dio_irq || Output || DIO1 (IRQ)
|-
| 8 || SLCT || BUSY || dio_busy || Input || BUSY
|-
| 26 || RST# || Hard Reset || dio_reset || Output || NRESET
|}

The function of these pins can be changed from user space by using libgpiod. The command line tools installed with the library (gpioset, gpioget, gpiodetect, gpioinfo...) can be used for bash scripts, etc. and applications should all use the libgpiod interfaces. The /sys/class/gpio interface has been removed from the kernel in 5.15, so any apps using /sys/class/gpio to access gpio pins are broken, or will be as distos update their kernels to 5.15 and beyond.

GPIO pins can be listed with gpioinfo:
$ gpioinfo pinedio

The output should look similar to:
gpiochip1 - 3 lines:
line 0: "dio_irq" unused input active-high
line 1: "dio_busy" unused input active-high
line 2: "dio_reset" unused output active-high

The gpiochip# might be different. The driver exposes the Pinedio with the gpio name "pinedio", developers should use this name to interact with the gpiochip because the gpiochip# of the device is likely to be different from one system to the next, or depending on the order devices are initialized.

=== Driver for the SX1262 LoRa module ===
Now that we can talk to the SX1262 via the CH341 USB converter chip, we need to send actual commands to make it emit or receive LoRa messages. To do this, you can implement the driver yourself using info from the datasheet, or use an existing driver (you can easily find drivers for the Arduino framework, for example.
I found [https://github.com/YukiWorkshop/sx126x_driver this C++ driver]. It's well written, lightweight and easily portable across many platforms. All you have to do is implement 3 HAL function : read GPIO, write GPIO and transfer data on SPI. I wrote a quick'n'dirty app that emits a LoRa frame. It's [https://gist.github.com/JF002/f1af5595874942427eea9d375c18fc73 available here].

As I don't have any 'raw' LoRa device on hands, I check that it was actually transmitting something using my SDR setup (simple TNT usb key and '''Gqrx''' software):

[[File:pine64-lora-usb-adapter-sdr.png|500px]]

== Other end nodes ==

There are several end-node units planned:
* loRa back case for the PinePhone
* standalone USB dongle-type end-node adapter
* PineTab adapter
* as well as a SPI module (which can also be configured as a USB LoRa dongle)
* a LoRa stick powered by a single 18650 battery (using the [https://wiki.pine64.org/wiki/Nutcracker BL602], and can be fitted with GPS, an low-power OLED panel and additional sensors)

All the end-nodes use the SX1262 chip.

=== Pictures ===
<gallery>
File:Blog-april-USB-LoRa-1024x655.jpg
File:Blog-april-LoRa-something-839x1024.jpg
File:Discord_20210421_lora_usb_closeup.jpg
</gallery>

== Datasheets and schematics ==
=== Gateway ===
* [https://www.semtech.com/products/wireless-rf/lora-gateways/sx1302 SX1302 datasheets and resources]
* [https://docs.rakwireless.com/Product-Categories/WisLink/RAK2247/Overview/ RAK2287 datasheets and resources]
* [https://wiki.pine64.org/images/5/54/PINE64_LoRa_Gateway_Module_Adapter_Schematic-v1.0-20210308.pdf Pine64 LoRa Gateway module adapter schematic]

=== End nodes ===
* [https://www.semtech.com/products/wireless-rf/lora-transceivers/sx1262 SX1262 datasheets and resources]

=== Pinephone backplate ===
* [[File:Pinephone_LoRa_BackPanel_Schematic-v1.0-20210402.pdf]]
* [[File:CA-S01_LoRa_Chip_Antenna_in_Chinese.pdf]]
* [https://github.com/zschroeder6212/tiny-i2c-spi I2C SPI Bridge code running on ATtiny84]

=== USB LoRa adapter ===
* [[File:USB_LoRa_adapter-PINE64_RFM90_SCH_2021_04_26.pdf]]
* CH341 datasheet : [[File:CH341DS1.pdf]]
* Semtech SX1262 datasheet : [https://semtech.my.salesforce.com/sfc/p/#E0000000JelG/a/2R000000HT76/7Nka9W5WgugoZe.xwIHJy6ebj1hW8UJ.USO_Pt2CLLo File on Semtech website (file is too big for the wiki)]

=== PineDio Stack ===
* Schematic : [[File:PINEDIO_STACK_V1_0-2021_05_24C.pdf]]

== Other resources ==
* [https://www.youtube.com/watch?v=cJ0wpANpbyc Video: A peek at Pine64's LoRa gateway and modules]
* [https://iotw.io/ IOTW - Blockchain-Enabled IoT Data Platform]
* [https://lupyuen.github.io/articles/pinedio PineDio Stack BL604 RISC-V Board: Testing The Prototype]
* [https://lupyuen.github.io/articles/lorawan2 LoRaWAN on PineDio Stack BL604 RISC-V Board]
* [https://lupyuen.github.io/articles/ttn The Things Network on PineDio Stack BL604 RISC-V Board]
* [https://lupyuen.github.io/articles/prometheus Monitor IoT Devices in The Things Network with Prometheus and Grafana]
* [https://lupyuen.github.io/articles/tsen Internal Temperature Sensor on BL602]
* [https://lupyuen.github.io/articles/roblox IoT Digital Twin with Roblox and The Things Network]
* [https://lupyuen.github.io/articles/gateway PineDio LoRa Gateway: Testing The Prototype]
* [https://lupyuen.github.io/articles/nuttx Apache NuttX OS on RISC-V BL602 and BL604]
* [https://lupyuen.github.io/articles/spi2 SPI on Apache NuttX OS]
* [https://lupyuen.github.io/articles/sx1262 LoRa SX1262 on Apache NuttX OS]
* [https://lupyuen.github.io/articles/lorawan3 LoRaWAN on Apache NuttX OS]
* [https://lupyuen.github.io/articles/rust2 Rust on Apache NuttX OS]
* [https://lupyuen.github.io/articles/ikea Connect IKEA Air Quality Sensor to Apache NuttX OS]
* [https://lupyuen.github.io/articles/pinedio2 PineDio Stack BL604 runs Apache NuttX RTOS]
* [https://lupyuen.github.io/articles/touch NuttX Touch Panel Driver for PineDio Stack BL604]
* [https://www.robertlipe.com/buttons-on-bl602-nuttx/ Buttons on BL602 NuttX]
* [https://lupyuen.github.io/articles/expander NuttX GPIO Expander for PineDio Stack BL604]
* [https://lupyuen.github.io/articles/auto2 (Mostly) Automated Testing of Apache NuttX RTOS on PineDio Stack BL604 RISC-V Board]
* [https://lupyuen.github.io/articles/zig Zig on RISC-V BL602: Quick Peek with Apache NuttX RTOS]
* [https://lupyuen.github.io/articles/iot Build an IoT App with Zig and LoRaWAN]
* [https://lupyuen.github.io/articles/lvgl Build an LVGL Touchscreen App with Zig]
* [https://youtu.be/_vADRu939sI Apache NuttX RTOS on a RISC-V IoT Gadget: PineDio Stack BL604 (Video)]
* [https://youtu.be/-2OIHur8X1E Simpler, safer LVGL Touchscreen Apps with Zig and Apache NuttX RTOS (Video)]

Ox64

2022-10-13T23:45:36Z

Lupyuen: Add Rust PAC and SVD

PineCone

2022-08-18T04:06:17Z

Lupyuen: Add article "Visual Programming with Zig and NuttX Sensors"

PineCone

2022-07-29T02:07:34Z

Lupyuen: Add article "Read NuttX Sensor Data with Zig"

2022-05-02T09:05:39Z

Lupyuen: Add article "NuttX GPIO Expander for PineDio Stack BL604"

{{under construction}}

The '''Pinedio''' is a device utilizing LoRa. LoRa is a long range, low power wireless platform that is being used by a lot of Internet of Things (IoT) products. Using LoRa and LoRaWAN, devices can communicate across the world using the internet, using various decentralised networks such as [https://www.thethingsnetwork.org/ The Things Network] or [https://www.helium.com/ Helium]. Since, PINE64 believes in openness, the LoRa gateway can connect to any network, per the developer implementation. If Helium Spots open up for PINE64 gateway and developers have implemented the hook for Helium, then this is good thing. The PINE64 LoRa gateway also open connect to The Things Network if developers implement support. The choice is yours!

== Gateway ==

The gateway will be available in two variants - indoor and outdoor. All that is known about the outdoor unit is that it will have "an aluminum, rugged and water resistant case".
The indoor unit consists of a PINE A64-LTS, fitted with a purpose built hat (adapter) which uses a LoRa module by RakWireless. The chipset used is the SX1302, and the module via the SPI interface. There are two external connections on the enclosure for the GPS and loRa antenna.

=== Connections ===
* GPS is connected to UART2 on the A64 board
* SX1302 on SPI0

{| class="wikitable"
|RAK2287 module
|PI-2 connector
|PINE A64-LTS
|-
|SX1302 SPI
|Pin 19 = MOSI / PC0 Pin 21 = MISO/PC1 Pin23 = CLK/PC2 Pin24 = CS/PC3
|SPI0 (/dev/spidev0.0)
|-
|SX1302 RESET
|Pin 11 = GPIO17/PC7
|GPIO71 (/sys/class/gpio/gpio71)
|-
|GPS UART
|Pin 8 = TX/ Pin 10 = RX
|UART2 (/dev/ttyS2)
|-
|GPS RESET
|Pin 33 = GPIO13/PC5
|GPIO69 (/sys/class/gpio/gpio69)
|-
|GPS Standby
|Pin 35 = GPIO19/PC9
|GPIO73 (/sys/class/gpio/gpio73)
|}

=== Pictures ===
<gallery>
File:Blog-april-InsideLoRaGateway.jpg
File:Blog-april-InsideLoRaGateway2.jpeg
File:Discord-lora-gateway-20210413_143615.jpg
File:Discord-lora-gateway-20210413_1435271.jpg
</gallery>

=== Operating System Options===

Pinedio Gateway carries the A64-LTS board. Based on ram specifications SOPINE images are also compatible.

====Armbian====

Gateway Hardware based on Pine64 A64-LTS + RAK2287 + GPS.

Hardware compatible with SOPINE images.

'''PineDio Gateway TTN/Chirpstack Image'''

Debian image with (Default Choices: Chirpstack / TTN) software preinstalled / hardware enabled is available below.

Latest:
(PineDio-RAK-Armbian_02-26-2022.img.xz)

SHA256: 83c2fae06579c2101502963289682295b83164d322ae7359c7c584f0b0e57426
SHA512: c5e8cb0b657ee02aa15c60dc7cab7b9e4a7785da548541c6a0eaf4ee7241600c18e339776d94731c5130ccceea4da4aad159af521c4f484c1a550a39fe707d95

DOWNLOAD LOCATION: https://mega.nz/file/CIoykITD#S_NQx9wRG05CTT7TdzBX8u24bGiVzT341VPZakycaw8

'''Switch Between Chirpstack / TTN (TheThingsNetwork)'''

gateway-config

First Select:

Setup RAK Gateway Channel Plan

Next For TTN (TheThingsNetwork) Select:

Server is TTN

'''or'''

Next For Chirpstack Select:

Server is Other server

'''Accessing Chirpstack Admin Page'''

Point web browser to:

http://gatewayIPaddress:8080

'''Default Chirpstack Credentials'''

login: admin
password: admin

'''SSH Credentials'''

Login: pinedio
password: SoPinePass!!!

'''Changing EUI'''

EUI is stored in file:

/opt/ttn-gateway/packetforwarder/lorapkt_fwd/local_conf.json

'''Additional Shell Commands'''

'''View Gateway ID/EUI'''

gateway-version

'''Restart Packet Forwarder/Concentrator'''

sudo systemctl restart ttn-gateway

'''Check Status'''

sudo systemctl status ttn-gateway

'''Enabling Concentrator/GPS Steps (Below Already *Completed* For Above Image Download)'''

Inside armbian-config -> system -> Bootenv (edit boot environment), enter the following 2 lines (to create spidev0.0):

overlays=spi-spidev uart2 i2c0
param_spidev_spi_bus=0

Or you may hand edit: /boot/armbianEnv.txt to add the above overlays/param_spidev_spi_bus lines.

Save. Reboot.

After rebooting you should see a new device /dev/spidev0.0. This will be the concentrator device for gateway related setup.

GPS will be /dev/ttyS2 and should work (after editing armbianEnv.txt + reboot).
Make sure to offer GPS antenna a strong signal, preferably by a window (if indoors).

== USB adapter ==
[[File:Pine64-lora-usb-adapter.jpg|500px]]

The Pine64 USB LoRa adapter is based on the Semtech SX1262 LoRa module and the CH341 USB bus converter chip. The '''CH341''' chip can be configured in multiple mode to convert USB to various serial and parallel ports. In this case, it's configured in '''synchronous serial mode''', which allows this chip to convert from USB to the SPI bus needed to talk to the SX1262 LoRa module:

-------- --------------------------
| | | USB LoRa Adapter |
| PC | <--USB--> | CH341 <--SPI--> SX1262 |
| | | <--I/O--> |
-------- --------------------------

=== Pins ===
[[File:Lora-usb-pins.jpg|500px]]

{| class="wikitable"

!SX1262 Pin
!Name
!Description
|-
|1
|ANT
|Antenna
|-
|2
|GND2
|
|-
|3
|VREG
|
|-
|4
|DCC
|
|-
|5
|VCC
|
|-
|6
|DIO1
|Connected on CH341 Pin 7
|-
|7
|DIO2
|Connected on CH341 Pin6
|-
|8
|DIO3
|Connected on CH341 Pin 5
|-
|9
|GND
|
|-
|10
|MISO
|SPI MISO (CH341 Pin 20)
|-
|11
|MOSI
|SPI MOSI (CH341 Pin 22)
|-
|12
|SCK
|SPI clock (CH341 Pin 24)
|-
|13
|NSS
|SPI Chip select
|-
|14
|POR
|Reset pin
|-
|15
|Busy
|Busy pin
|-
|16
|GND
|
|}

=== Kernel module for CH341 ===
We need a driver for the CH341 USB bus converter chip. This driver will allow us to send command to the CH341 (SPI messages and access to the GPIOs). I've successfully build and run [https://github.com/rogerjames99/spi-ch341-usb this driver from '''rogerjames99'''] on my desktop computer (running Manjaro Linux) and on my Pinebook Pro (ARM64, running Manjaro ARM Linux). For any kernel newer than 3.10 but mandatory for kernels newer than 5.15 you need to use the [https://github.com/dimich-dmb/spi-ch341-usb dimich-dmb fork of the the '''spi-ch341-usb driver.'''] This fork has updated documentation for the newer kernel interfaces. If this driver gives you problems please drop by any of the social platforms in the Pine64 LoRa chat and give a holler, and if you are using a 5.15 or older kernel you can use the rogerjames99 fork.

$ git clone https://github.com/rogerjames99/spi-ch341-usb.git
or
$ git clone https://github.com/dimich-dmb/spi-ch341-usb.git
then
$ cd spi-ch341-usb
$ make
$ sudo make install

Once the driver is installed, unload the module ''ch341'' if it has been automatically loaded:

$ lsmod |grep ch341
$ sudo rmmod ch341

On my setup, ''ch341'' would be automatically loaded once I connected my USB adapter. This module drives the CH341 is asynchronous serial mode, which will not work for a SPI bus.

Then load the new module:

$ sudo modprobe spi-ch341-usb

Plug your USB adapter and check that the module is correctly loaded :

$ dmesg
[20141.872107] usb 1-1.1: USB disconnect, device number 4
[20143.820756] usb 1-1.1: new full-speed USB device number 5 using ehci-platform
[20143.973366] usb 1-1.1: New USB device found, idVendor=1a86, idProduct=5512, bcdDevice= 3.04
[20143.973413] usb 1-1.1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[20143.973434] usb 1-1.1: Product: USB UART-LPT
[20143.975137] spi-ch341-usb 1-1.1:1.0: ch341_usb_probe: connect device
[20143.975164] spi-ch341-usb 1-1.1:1.0: ch341_usb_probe: bNumEndpoints=3
[20143.975183] spi-ch341-usb 1-1.1:1.0: ch341_usb_probe: endpoint=0 type=2 dir=1 addr=2
[20143.975206] spi-ch341-usb 1-1.1:1.0: ch341_usb_probe: endpoint=1 type=2 dir=0 addr=2
[20143.975229] spi-ch341-usb 1-1.1:1.0: ch341_usb_probe: endpoint=2 type=3 dir=1 addr=1
[20143.975254] spi-ch341-usb 1-1.1:1.0: ch341_cfg_probe: output cs0 SPI slave with cs=0
[20143.975273] spi-ch341-usb 1-1.1:1.0: ch341_cfg_probe: output cs0 gpio=0 irq=0
[20143.975295] spi-ch341-usb 1-1.1:1.0: ch341_cfg_probe: output cs1 SPI slave with cs=1
[20143.975313] spi-ch341-usb 1-1.1:1.0: ch341_cfg_probe: output cs1 gpio=1 irq=1
[20143.975334] spi-ch341-usb 1-1.1:1.0: ch341_cfg_probe: output cs2 SPI slave with cs=2
[20143.975352] spi-ch341-usb 1-1.1:1.0: ch341_cfg_probe: output cs2 gpio=2 irq=2
[20143.975373] spi-ch341-usb 1-1.1:1.0: ch341_cfg_probe: input gpio4 gpio=3 irq=3
[20143.975394] spi-ch341-usb 1-1.1:1.0: ch341_cfg_probe: input gpio6 gpio=4 irq=4
[20143.975415] spi-ch341-usb 1-1.1:1.0: ch341_cfg_probe: input err gpio=5 irq=5
[20143.975435] spi-ch341-usb 1-1.1:1.0: ch341_cfg_probe: input pemp gpio=6 irq=6
[20143.975456] spi-ch341-usb 1-1.1:1.0: ch341_cfg_probe: input int gpio=7 irq=7 (hwirq)
[20143.975478] spi-ch341-usb 1-1.1:1.0: ch341_cfg_probe: input slct gpio=8 irq=8
[20143.975499] spi-ch341-usb 1-1.1:1.0: ch341_cfg_probe: input wait gpio=9 irq=9
[20143.975520] spi-ch341-usb 1-1.1:1.0: ch341_cfg_probe: input autofd gpio=10 irq=10
[20143.975542] spi-ch341-usb 1-1.1:1.0: ch341_cfg_probe: input addr gpio=11 irq=11
[20143.975564] spi-ch341-usb 1-1.1:1.0: ch341_cfg_probe: output ini gpio=12 irq=12
[20143.975585] spi-ch341-usb 1-1.1:1.0: ch341_cfg_probe: output write gpio=13 irq=13
[20143.975607] spi-ch341-usb 1-1.1:1.0: ch341_cfg_probe: output scl gpio=14 irq=14
[20143.975628] spi-ch341-usb 1-1.1:1.0: ch341_cfg_probe: output sda gpio=15 irq=15
[20143.975650] spi-ch341-usb 1-1.1:1.0: ch341_spi_probe: start
[20143.975677] spi-ch341-usb 1-1.1:1.0: ch341_spi_probe: SPI master connected to SPI bus 1
[20143.977831] spi-ch341-usb 1-1.1:1.0: ch341_spi_probe: SPI device /dev/spidev1.0 created
[20143.978183] spi-ch341-usb 1-1.1:1.0: ch341_spi_probe: SPI device /dev/spidev1.1 created
[20143.978552] spi-ch341-usb 1-1.1:1.0: ch341_spi_probe: SPI device /dev/spidev1.2 created
[20143.978726] spi-ch341-usb 1-1.1:1.0: ch341_spi_probe: done
[20143.978735] spi-ch341-usb 1-1.1:1.0: ch341_irq_probe: start
[20143.979133] spi-ch341-usb 1-1.1:1.0: ch341_irq_probe: irq_base=103
[20143.979154] spi-ch341-usb 1-1.1:1.0: ch341_irq_probe: done
[20143.979162] spi-ch341-usb 1-1.1:1.0: ch341_gpio_probe: start
[20143.979220] spi-ch341-usb 1-1.1:1.0: ch341_gpio_get_direction: gpio=cs0 dir=0
[20143.979229] spi-ch341-usb 1-1.1:1.0: ch341_gpio_get_direction: gpio=cs1 dir=0
[20143.979237] spi-ch341-usb 1-1.1:1.0: ch341_gpio_get_direction: gpio=cs2 dir=0
[20143.979245] spi-ch341-usb 1-1.1:1.0: ch341_gpio_get_direction: gpio=gpio4 dir=1
[20143.979253] spi-ch341-usb 1-1.1:1.0: ch341_gpio_get_direction: gpio=gpio6 dir=1
[20143.979260] spi-ch341-usb 1-1.1:1.0: ch341_gpio_get_direction: gpio=err dir=1
[20143.979268] spi-ch341-usb 1-1.1:1.0: ch341_gpio_get_direction: gpio=pemp dir=1
[20143.979275] spi-ch341-usb 1-1.1:1.0: ch341_gpio_get_direction: gpio=int dir=1
[20143.979283] spi-ch341-usb 1-1.1:1.0: ch341_gpio_get_direction: gpio=slct dir=1
[20143.979290] spi-ch341-usb 1-1.1:1.0: ch341_gpio_get_direction: gpio=wait dir=1
[20143.979298] spi-ch341-usb 1-1.1:1.0: ch341_gpio_get_direction: gpio=autofd dir=1
[20143.979306] spi-ch341-usb 1-1.1:1.0: ch341_gpio_get_direction: gpio=addr dir=1
[20143.979314] spi-ch341-usb 1-1.1:1.0: ch341_gpio_get_direction: gpio=ini dir=0
[20143.979321] spi-ch341-usb 1-1.1:1.0: ch341_gpio_get_direction: gpio=write dir=0
[20143.979329] spi-ch341-usb 1-1.1:1.0: ch341_gpio_get_direction: gpio=scl dir=0
[20143.979337] spi-ch341-usb 1-1.1:1.0: ch341_gpio_get_direction: gpio=sda dir=0
[20143.979831] spi-ch341-usb 1-1.1:1.0: ch341_gpio_probe: registered GPIOs from 496 to 511
[20143.981152] spi-ch341-usb 1-1.1:1.0: ch341_gpio_probe: done
[20143.981212] spi-ch341-usb 1-1.1:1.0: ch341_gpio_poll_function: start
[20143.981291] spi-ch341-usb 1-1.1:1.0: ch341_usb_probe: connected
[20144.756250] usbcore: registered new interface driver ch341
[20144.756334] usbserial: USB Serial support registered for ch341-uart

With kernel 5.16 and newer the output is shorter:

$ dmesg
[ 6744.813564] usb 1-2.1.1: new full-speed USB device number 21 using xhci_hcd
[ 6744.904377] usb 1-2.1.1: New USB device found, idVendor=1a86, idProduct=5512, bcdDevice= 3.04
[ 6744.904383] usb 1-2.1.1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[ 6744.904385] usb 1-2.1.1: Product: USB UART-LPT
[ 6744.960243] spi-ch341-usb 1-2.1.1:1.0: ch341_cfg_probe: output cs0 SPI slave with cs=0
[ 6744.960246] spi-ch341-usb 1-2.1.1:1.0: ch341_cfg_probe: output cs1 SPI slave with cs=1
[ 6744.960247] spi-ch341-usb 1-2.1.1:1.0: ch341_cfg_probe: output cs2 SPI slave with cs=2
[ 6744.960249] spi-ch341-usb 1-2.1.1:1.0: ch341_cfg_probe: input gpio4 gpio=0 irq=0 (hwirq)
[ 6744.960251] spi-ch341-usb 1-2.1.1:1.0: ch341_cfg_probe: input gpio5 gpio=1 irq=1
[ 6744.960302] spi-ch341-usb 1-2.1.1:1.0: ch341_spi_probe: SPI master connected to SPI bus 0
[ 6744.960350] spi-ch341-usb 1-2.1.1:1.0: ch341_spi_probe: SPI device /dev/spidev0.0 created
[ 6744.960398] spi-ch341-usb 1-2.1.1:1.0: ch341_spi_probe: SPI device /dev/spidev0.1 created
[ 6744.960445] spi-ch341-usb 1-2.1.1:1.0: ch341_spi_probe: SPI device /dev/spidev0.2 created
[ 6744.960583] spi-ch341-usb 1-2.1.1:1.0: ch341_usb_probe: connected

=== Driver development ===
=====Kernels 5.14 and older=====

Once the module ''spi-ch341-usb'' is correctly loaded, here's how you can transfer data on the SPI bus (in C):

/* Open the SPI bus */
int spi = open("/dev/spidev1.0", O_RDWR);
uint8_t mmode = SPI_MODE_0;
uint8_t lsb = 0;
ioctl(spi, SPI_IOC_WR_MODE, &mmode);
ioctl(spi, SPI_IOC_WR_LSB_FIRST, &lsb);

/* Transfer data */
/* TODO: Init buffer_out, buffer_in and size */
const uint8_t *mosi = buffer_out; // output data
uint8_t *miso = buffer_in; // input data

struct spi_ioc_transfer spi_trans;
memset(&spi_trans, 0, sizeof(spi_trans));

spi_trans.tx_buf = (unsigned long) mosi;
spi_trans.rx_buf = (unsigned long) miso;
spi_trans.cs_change = true;
spi_trans.len = size;

int status = ioctl (spi, SPI_IOC_MESSAGE(1), &spi_trans);

To access GPIOs, you first need to export them (to make them accessible via ''/sys/class/gpio''. As you can see in the dmesg output, GPIOs from 496 to 511 were registered, which means we can export 16 GPIOs. The mapping of these I/O is available in the [https://github.com/rogerjames99/spi-ch341-usb/blob/master/spi-ch341-usb.c#L148 source code of the driver]. For example, pin ''slct'' is the 12th, meaning we need to export GPIO 496+12 = 508.

int fd;
if ((fd = open("/sys/class/gpio/export", O_WRONLY)) == -1) {
perror("open ini");
exit(-1);
}

if (write(fd, "508", 3) == -1){
perror ("write export 508");
}

Once exported, the GPIO is available in ''/sys/class/gpio/sclt'' (the naming is specified by the driver). You can read the pin in C:

int fd;
if ((fd = open("/sys/class/gpio/slct/value", O_RDWR)) == -1) {
perror("open");
}

char buf;
if (read(fd, &buf, 1) == -1) {
perror("read");
}

int value = (buf == '0') ? 0 : 1;

You can also write it:

int fd;
if ((fd = open("/sys/class/gpio/ini/value", O_RDWR)) == -1) {
perror("open ini");
}

if (write(fd, value ? "1" : "0", 1) == -1) {
perror ("write");
}

=====Kernel 5.15 and newer=====

We need some help documenting how these interfaces work!

The driver creates these interfaces:
{| class="wikitable"
|Pin ||SPI Function ||GPIO function ||GPIO name ||IRQ
|-
|15||CS0||-||-||-
|-
|16||CS1||-||-||-
|-
|17||CS2||-||-||-
|-
|19||-||Input||gpio4||hardware
|-
|21||-||Input||gpio5||software
|}

The dimich-dmb fork of spi-ch341-usb works with 5.15+ kernels, but as you can see above it is not configured for the needs of the Pinedio-USB by default. I have started a branch in my fork to work on getting the driver pre-configured for our needs. The branch can be [https://github.com/UncleGrumpy/spi-ch341-usb/tree/pinedio found here.] Please feel free to help! And open issues or discussions in the repo if you have problems or ideas how to help. Any improvements to the actual code beyond configuration should be pushed to the temporary [https://github.com/dimich-dmb/spi-ch341-usb/ upstream.]

Since linux-5.15 binding to spidev driver is required to make slave devices available via /dev/, e.g. for slave 1 on bus 0 as real root (not with sudo):

# echo spidev > /sys/class/spi_master/spi0/spi0.1/driver_override
# echo spi0.1 > /sys/bus/spi/drivers/spidev/bind

For all devices handled by spi_ch341_usb driver (again, only as real root):

# for i in /sys/bus/usb/drivers/spi-ch341-usb/*/spi_master/spi*/spi*.*; do echo spidev > $i/driver_override; echo $(basename $i) > /sys/bus/spi/drivers/spidev/bind; done

The documentation found at https://github.com/dimich-dmb/spi-ch341-usb/blob/master/README.md has more information.

The 5.15+ driver is not ready yet. But if you are interested in testing, helping to get the configuration right, or working on application development you can build and test the current driver:

$ git clone -b pinedio https://github.com/UncleGrumpy/spi-ch341-usb.git
$ cd spi-ch341-usb
$ make
$ sudo make install

So far this will automatically set up the SPI slave device /dev/spi0.0. It names the ch341-usb device as "pinedio" this will allow application developers to find the correct gpiochip by name. I need help confirming the correct gpio pins but as of now the driver will setup the following configuration:

The driver uses following CH341A pins for the SPI interface.
{| class="wikitable"
| Pin || Name || Direction || Function SPI (CH341A)
|-
| 18 || D3 || output || SCK (DCK)
|-
| 20 || D5 || output || MOSI (DOUT)
|-
| 22 || D7 || input || MISO (DIN)
|-
| 15 || D0 || output || CS0
|}

The driver uses the following GPIO configuration. I am not at all sure these are the correct pins to use! This is one area that I could really use some help with!!!
{| class="wikitable
| CH341 Pin || CH341A Name || Function || GPIO Name || GPIO Configuration || SX1262 connection
|-
| 7 || INT# || IRQ || dio_irq || Output || DIO1 (IRQ)
|-
| 8 || SLCT || BUSY || dio_busy || Input || BUSY
|-
| 26 || RST# || Hard Reset || dio_reset || Output || NRESET
|}

The function of these pins can be changed from user space by using libgpiod. The command line tools installed with the library (gpioset, gpioget, gpiodetect, gpioinfo...) can be used for bash scripts, etc. and applications should all use the libgpiod interfaces. The /sys/class/gpio interface has been removed from the kernel in 5.15, so any apps using /sys/class/gpio to access gpio pins are broken, or will be as distos update their kernels to 5.15 and beyond.

GPIO pins can be listed with gpioinfo:
$ gpioinfo pinedio

The output should look similar to:
gpiochip1 - 3 lines:
line 0: "dio_irq" unused input active-high
line 1: "dio_busy" unused input active-high
line 2: "dio_reset" unused output active-high

The gpiochip# might be different. The driver exposes the Pinedio with the gpio name "pinedio", developers should use this name to interact with the gpiochip because the gpiochip# of the device is likely to be different from one system to the next, or depending on the order devices are initialized.

=== Driver for the SX1262 LoRa module ===
Now that we can talk to the SX1262 via the CH341 USB converter chip, we need to send actual commands to make it emit or receive LoRa messages. To do this, you can implement the driver yourself using info from the datasheet, or use an existing driver (you can easily find drivers for the Arduino framework, for example.
I found [https://github.com/YukiWorkshop/sx126x_driver this C++ driver]. It's well written, lightweight and easily portable across many platforms. All you have to do is implement 3 HAL function : read GPIO, write GPIO and transfer data on SPI. I wrote a quick'n'dirty app that emits a LoRa frame. It's [https://gist.github.com/JF002/f1af5595874942427eea9d375c18fc73 available here].

As I don't have any 'raw' LoRa device on hands, I check that it was actually transmitting something using my SDR setup (simple TNT usb key and '''Gqrx''' software):

[[File:pine64-lora-usb-adapter-sdr.png|500px]]

== Other end nodes ==

There are several end-node units planned:
* loRa back case for the PinePhone
* standalone USB dongle-type end-node adapter
* PineTab adapter
* as well as a SPI module (which can also be configured as a USB LoRa dongle)
* a LoRa stick powered by a single 18650 battery (using the [https://wiki.pine64.org/wiki/Nutcracker BL602], and can be fitted with GPS, an low-power OLED panel and additional sensors)

All the end-nodes use the SX1262 chip.

=== Pictures ===
<gallery>
File:Blog-april-USB-LoRa-1024x655.jpg
File:Blog-april-LoRa-something-839x1024.jpg
File:Discord_20210421_lora_usb_closeup.jpg
</gallery>

== Datasheets and schematics ==
=== Gateway ===
* [https://www.semtech.com/products/wireless-rf/lora-gateways/sx1302 SX1302 datasheets and resources]
* [https://docs.rakwireless.com/Product-Categories/WisLink/RAK2247/Overview/ RAK2287 datasheets and resources]
* [https://wiki.pine64.org/images/5/54/PINE64_LoRa_Gateway_Module_Adapter_Schematic-v1.0-20210308.pdf Pine64 LoRa Gateway module adapter schematic]

=== End nodes ===
* [https://www.semtech.com/products/wireless-rf/lora-transceivers/sx1262 SX1262 datasheets and resources]

=== Pinephone backplate ===
* [[File:Pinephone_LoRa_BackPanel_Schematic-v1.0-20210402.pdf]]
* [[File:CA-S01_LoRa_Chip_Antenna_in_Chinese.pdf]]
* [https://github.com/zschroeder6212/tiny-i2c-spi I2C SPI Bridge code running on ATtiny84]

=== USB LoRa adapter ===
* [[File:USB_LoRa_adapter-PINE64_RFM90_SCH_2021_04_26.pdf]]
* CH341 datasheet : [[File:CH341DS1.pdf]]
* Semtech SX1262 datasheet : [https://semtech.my.salesforce.com/sfc/p/#E0000000JelG/a/2R000000HT76/7Nka9W5WgugoZe.xwIHJy6ebj1hW8UJ.USO_Pt2CLLo File on Semtech website (file is too big for the wiki)]

=== PineDio Stack ===
* Schematic : [[File:PINEDIO_STACK_V1_0-2021_05_24C.pdf]]

== Other resources ==
* [https://www.youtube.com/watch?v=cJ0wpANpbyc Video: A peek at Pine64's LoRa gateway and modules]
* [https://iotw.io/ IOTW - Blockchain-Enabled IoT Data Platform]
* [https://lupyuen.github.io/articles/pinedio PineDio Stack BL604 RISC-V Board: Testing The Prototype]
* [https://lupyuen.github.io/articles/lorawan2 LoRaWAN on PineDio Stack BL604 RISC-V Board]
* [https://lupyuen.github.io/articles/ttn The Things Network on PineDio Stack BL604 RISC-V Board]
* [https://lupyuen.github.io/articles/prometheus Monitor IoT Devices in The Things Network with Prometheus and Grafana]
* [https://lupyuen.github.io/articles/tsen Internal Temperature Sensor on BL602]
* [https://lupyuen.github.io/articles/roblox IoT Digital Twin with Roblox and The Things Network]
* [https://lupyuen.github.io/articles/gateway PineDio LoRa Gateway: Testing The Prototype]
* [https://lupyuen.github.io/articles/nuttx Apache NuttX OS on RISC-V BL602 and BL604]
* [https://lupyuen.github.io/articles/spi2 SPI on Apache NuttX OS]
* [https://lupyuen.github.io/articles/sx1262 LoRa SX1262 on Apache NuttX OS]
* [https://lupyuen.github.io/articles/lorawan3 LoRaWAN on Apache NuttX OS]
* [https://lupyuen.github.io/articles/rust2 Rust on Apache NuttX OS]
* [https://lupyuen.github.io/articles/ikea Connect IKEA Air Quality Sensor to Apache NuttX OS]
* [https://lupyuen.github.io/articles/pinedio2 PineDio Stack BL604 runs Apache NuttX RTOS]
* [https://lupyuen.github.io/articles/touch NuttX Touch Panel Driver for PineDio Stack BL604]
* [https://www.robertlipe.com/buttons-on-bl602-nuttx/ Buttons on BL602 NuttX]
* [https://lupyuen.github.io/articles/expander NuttX GPIO Expander for PineDio Stack BL604]