From dff3971c7a67f3d9e881aa95b2aabf34a58702c0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jan=20Grome=C5=A1?= Date: Sun, 3 Nov 2024 11:03:40 +0100 Subject: [PATCH] Updated Porting to non Arduino Platforms (markdown) --- Porting-to-non-Arduino-Platforms.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Porting-to-non-Arduino-Platforms.md b/Porting-to-non-Arduino-Platforms.md index eb56e21..dd55090 100644 --- a/Porting-to-non-Arduino-Platforms.md +++ b/Porting-to-non-Arduino-Platforms.md @@ -19,7 +19,7 @@ NOTE: If you installed RadioLib as a shared library in the previous step, you wi `#include ` 3. **Provide your hardware abstraction layer to RadioLib** -To run on different platforms (e.g., esp-idf for ESP32, stm32hal for STM32, pigpio for Raspberry Pi etc.), RadioLib includes a light abstraction layer class. It's up to the user to add implementation of this abstraction layer - usually this boils down to providing functions that perform GPIO operations, SPI transactions etc. An example for Raspberry Pi using the [lgpio library](https://abyz.me.uk/lg/lgpio.html) can be found here: https://github.com/jgromes/RadioLib/blob/master/examples/NonArduino/Raspberry/PiHal.h +To run on different platforms (e.g., esp-idf for ESP32, stm32hal for STM32, pigpio for Raspberry Pi etc.), RadioLib includes a light-weight Hardware Abstraction Layer (HAL) class. HALs for the most commont platforms are provided here: https://github.com/jgromes/RadioLib/tree/master/src/hal. If adding a new platform, it's up to the user to add implementation of this abstraction layer - usually this boils down to providing functions that perform GPIO operations, SPI transactions etc. 4. **Done!** Congratulations, you have now succesfully ported RadioLib to your platform! \ No newline at end of file