From 4d89f8a0e2a4c9cd9118e5ba770a250e8e66f9c3 Mon Sep 17 00:00:00 2001 From: John-Mark Gurney Date: Mon, 3 May 2021 16:10:46 -0700 Subject: [PATCH] explain a bit why Lorawan wasn't used, and clarify compiler issue.. --- README.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 4ced2c1..a8d283b 100644 --- a/README.md +++ b/README.md @@ -12,7 +12,9 @@ While investigating this, the LoraWAN protocol was investigated, but after looking at the code complexity and other operational requirements, if was decided that for this project, it was safer to target a direct Node to Node style communication system. This would allow the -implementation to be more simple, and security to be built in. It +implementation to be more simple, and security to be built in (LoRaWAN +does have a crypto layer, BUT, trusting/auditing it and any library that +implements it would be a larger task than I want to undertake). It could also be used for other projects that need security. One of the other requirements is that the code be 100% open sourced, @@ -29,10 +31,10 @@ make on the BSDs, originally called pmake, but also available as bsdmake for MacOSX, and likely other operating systems as well. It also depends upon ARM's [GNU Arm Embedded -Toolchain](https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm) -which uses gcc as the compiler. It would be good to get it to +Toolchain](https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm), +which uses gcc as the compiler. It would be good to get it cross-compile with clang as well, but that requires finding a libc like -the nano libc that `nano.specs` in the above toolchain provides. +the nano libc that is provided by the toolchain. Once ARM's toolchain is in your path, the following should work: ```