RAK833: failed to start the concentrator

SimonBoonstra
Sat, 13 Apr 2024 01:21:11 +0000
Raspberry Pi Gateways

Hello

I have currently the issue that the packet-forwarder won’t start.

This is my setup

Raspberry Pi Zero 2W
OS: Raspberry Pi OS Lite- Bookworm 64bit

LoRa Gateway
Brand: PiSupply
Model: RAK833 SPI
Chip: SX1301
Reset Pin: GPIO22

Initial configuration
SPI enabled
I2C enabled
Serial login shell disabled
Serial port hardware enabled

Description
My gateway has already worked before. I have not used it for a while and wanted to upgrade today to the Bookworm debian version (respectively the Rasperry Pi OS - Bookworm version). I did a fresh install to have everything clean.

Unfortunately, I run now into the error:

ERROR: [main] failed to start the concentrator

I followed the installation and configuration instructions from the manufacturer’s git repository:

github.com

IoTLoRaRange/IoT Lora Gateway HAT at master · PiSupply/IoTLoRaRange

Repository for all of the IoT LoRa Range of Products - PiSupply/IoTLoRaRange

I believe, the issue is, that the start script can’t toggle the reset pin, because of this error: “kernel: export_store: invalid GPIO 22”

I tried also to do it manually with following commands:

SX1301_RESET_BCM_PIN=22
echo "$SX1301_RESET_BCM_PIN"  > /sys/class/gpio/export

This leads to following error message:
echo: write error: invalid argument

Also the the output of the ./start.sh script with error messages like
/sys/class/gpio/gpio22/direction: No such file or directory are maybe pointing to an issue with the GPIO pins?

Now I’m not sure what the reason of the issue could be.
It looks to me like somehow the GPIO pin can’t be accessed?
On the other hand, the Gateway and Raspberry were for a few months outside on my balcony.
The place is protected from rain, but maybe humidity etc. could be damaged the Gateway module?

Also the LED’s on the Gateway module doesn’t light up.
I think there is a red LED which is illuminated as soon as the gateway is configured correctly.

Maybe someone has an idea, what I can check or test to find out the exact issue?
Help is much apprechiated. Thanks.

This are my configuration files:
start.sh (click for more details) global_conf.json (click for more details)
And here is my logfile
journalctl log (click for more details)
This is the output when I start ./start.sh
Output from start.sh (click for more details)
10 posts - 4 participants