Hi Rex,
I’m working with a ClockworkPi uConsole with Raspberry Pi CM5 (16 GB) and the HackerGadgets AIO V2 board, including the LoRa module.
I have been using a LLM to help me with issue and this is as far as I have gotten.
I’m running a fresh Debian 13 Trixie installation using the current Rex/uConsole image, kernel 7.1.4. The system is now running from a 512 GB NVMe, although the same fresh image was initially tested from SD.
The other AIO V2 hardware is working correctly:
- RTL-SDR — working
- GPS — working
- RTC — working
- Internal USB hub — working
- Ethernet — working
- tar1090/readsb — working when the SDR rail is enabled
The problem is specifically the AIO V2 LoRa/SX1262 with Meshtastic.
AIO V2 configuration
The AIO V2 package is installed:
hackergadgets-uconsole-aio-board 1.41
I also installed the current aiov2_ctl.
The LoRa rail is being controlled correctly and I can turn it on with:
sudo aiov2_ctl lora on
The current AIO V2 status shows:
LORA GPIO16: ON
The CM5 configuration contains:
dtoverlay=clockworkpi-uconsole-cm5
dtoverlay=spi1-1cs
The SPI device exposed by the CM5/RP1 is:
/dev/spidev10.0
The relevant Meshtastic configuration is currently:
Lora:
Module: sx1262
gpiochip: 15
DIO2_AS_RF_SWITCH: true
DIO3_TCXO_VOLTAGE: true
IRQ: 26
Busy: 24
Reset: 25
spidev: spidev10.0
The gpiochip: 15 setting is present because this is the AIO V2/CM5 GPIO configuration.
The meshtasticd service starts, but fails during SX1262 initialization with:
SX126x init result -2
No sx1262 radio
With the original spidev1.0 configuration, Meshtastic reported:
Failed to open posix file /dev/spidev1.0, errno=2
No hardware spi chip found
SX126x init result -2
No sx1262 radio
Changing it to the actual device exposed by the CM5:
spidev: spidev10.0
removed the /dev/spidev1.0 error, but the radio still fails initialization:
SX126x init result -2
No sx1262 radio
free(): invalid pointer
Aborted
The meshtasticd user has the required SPI/GPIO permissions, including membership in the spi and gpio groups.
I also verified that the AIO V2 LoRa rail is powered before starting Meshtastic.
I found the ClockworkPi forum discussion where another AIO V2 + Debian Trixie user had the exact:
SX126x init result -2
No sx1262 radio
error. In that case restoring:
dtoverlay=spi1-1cs
fixed the LoRa module. That overlay is already present on my system, so that particular fix doesn’t resolve my problem.
At this point I’m trying to determine whether there is a CM5/AIO V2-specific Meshtastic configuration, device-tree setting, package/version issue, or GPIO/SPI mapping issue that is different from the documented configuration.
Could you tell me what the known-good Meshtastic configuration for AIO V2 + CM5 + the current Trixie image should be, particularly the expected SPI device name and SX1262 GPIO configuration?
On a CM5 running the current Rex Trixie image, what should spidev: be set to for the AIO V2 LoRa module? My system exposes /dev/spidev10.0, while the AIO V2 documentation specifies spidev1.0.
If you need any specific logs or diagnostics, I’m happy to provide them.
Thanks!
Davkenrem
