Implement a secure ICS protocol targeting LoRa Node151 microcontroller for controlling irrigation.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
John-Mark Gurney 0b580fc32b now that we support an OBJDIR, fix up the python tests... 3 years ago
loramac fix up white space, drop board-config.h so it doesn't collide with the 3 years ago
stm32 add framework for properly receiving/handling incoming data.. 3 years ago
strobe update link as the paper has moved... same cert for new domains as parent of old.. 3 years ago
.gitignore add recommended build dir to be ignored.. 3 years ago
LICENSE.txt add license 3 years ago
Makefile now that we support an OBJDIR, fix up the python tests... 3 years ago
README.md add starting readme for the project.. 3 years ago
board-config.h get tx/rx working between two Node151's.. 3 years ago
board.c get tx/rx working between two Node151's.. 3 years ago
lora.py start of the lorenode initiator 3 years ago
main.c fix return to return false, not -1... 3 years ago
misc.c get tx/rx working between two Node151's.. 3 years ago
misc.h get tx/rx working between two Node151's.. 3 years ago
requirements.txt add the required python packages.. 3 years ago
strobe_rng_init.c make the linker information work... add an inline to ignore warning.. 3 years ago
strobe_rng_init.h make the linker information work... add an inline to ignore warning.. 3 years ago
sysIrqHandlers.h get tx/rx working between two Node151's.. 3 years ago

README.md

LoRa Irrigation System

This project is to build an irrigation system from LoRa capable microcontrollers. The Heltec Node151 was chosen due to it’s small size and inexpensive cost.

Design Decisions

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 could also be used for other projects that need security.

One of the other requirements is that the code be 100% open sourced, not GPL licensed, and no propietary components. This ment that using IDE’s like ST’s STM32CubeIDE which is only available in binary form was not a choice, as that would preclude building on an operating system other than Windows/MaxOS/Linux.

Building

The build system uses the BSD flavor of make. This is the default 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 which uses gcc as the compiler. It would be good to get it to cross-compile with clang as well, but that requires finding a libc like the nano libc that nano.specs in the above toolchain provides.

Once ARM’s toolchain is in your path, the following should work:

export MAKEOBJDIR=build
mkdir $MAKEOBJDIR
bsdmake all

And in the directory build, a file lora.irr.elf should be pressent.

Flashing

Flashing can be done via the open source tool OpenOCD. For this, I use a Digilent HS1 JTAG programmer utilizing the resistor hack to allow an FTDI JTAG programmer to control the bi-directional SWIO pin.

One caveat w/ MacOSX, is that it may be necessary to unload the kext com.apple.driver.AppleUSBFTDI via the command:

sudo kextunload -b com.apple.driver.AppleUSBFTDI

as OpenOCD wants direct access to the FTDI driver.

Once that happens, the device can be programmed using the following command:

sudo openocd -f interface/ftdi/digilent-hs1.cfg -f interface/ftdi/swd-resistor-hack.cfg -f target/stm32l1.cfg -c "init" -c "reset init" -c "program build/lora.irr.elf verify reset exit"