NebraHat won't work unless CS pin line is uncommented

[turnrye]

The nebrahat config says Newer version of MeshtasticD do not need this? If issues uncomment this line. Well, with my nebra, rpi os lite, meshtasticd 2.6.10 running native, and the 1 watt nebrahat, I need this.

Environment

• Nebra HNT Outdoor Hotspot Miner mainboard
• Raspberry Pi Compute Module 3 Rev 1.0
• raspios lite, Debian GNU/Linux 12 (bookworm)
• meshtasticd raspbian, version 2.6.10.23~obs9ce4455~beta arm64

Repro steps

• Assemble a nebrahat 1W and install it on the pi headers on the nebra
• Flash rpios bookworm lite
• Install meshtasticd per docs
• Follow meshtastic doc guidelines for setting interfaces properly in raspi-config (or using their commands)
• Follow the readme steps for copying in the config.d file
• Check journalctl logs

Actual result

sx1262 failed to init

Logs

Jun 17 12:18:05 raspberrypi-nebra-2 systemd[1]: Started meshtasticd.service - Meshtastic Native Daemon.
Jun 17 12:18:06 raspberrypi-nebra-2 meshtasticd[569]: Portduino is starting, VFS root at /var/lib/meshtasticd/.portduino/default
Jun 17 12:18:06 raspberrypi-nebra-2 meshtasticd[569]: Set up Meshtastic on Portduino...
Jun 17 12:18:06 raspberrypi-nebra-2 meshtasticd[569]: Using /etc/meshtasticd/config.yaml as config file
Jun 17 12:18:06 raspberrypi-nebra-2 meshtasticd[569]: Also using "/etc/meshtasticd/config.d/NebraHat_1W.yaml" as additional config file
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: MAC ADDRESS: F0:4C:D5:5A:57:41
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: DEBUG | ??:??:?? 0 Upgrade time to quality NTP
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: DEBUG | 12:18:06 0 Read RTC time as 1750180686
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: INFO  | 12:18:06 0
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: 
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: //\ E S H T /\ S T / C
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: 
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: DEBUG | 12:18:06 0 Filesystem files:
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: DEBUG | 12:18:06 0  /.. (0 Bytes)
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: DEBUG | 12:18:06 0  /prefs/.. (0 Bytes)
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: DEBUG | 12:18:06 0  /prefs/config.proto (168 Bytes)
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: DEBUG | 12:18:06 0  /prefs/. (0 Bytes)
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: DEBUG | 12:18:06 0  /prefs/channels.proto (57 Bytes)
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: DEBUG | 12:18:06 0  /prefs/nodes.proto (479 Bytes)
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: DEBUG | 12:18:06 0  /prefs/device.proto (96 Bytes)
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: DEBUG | 12:18:06 0  /. (0 Bytes)
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: INFO  | 12:18:06 0 No I2C device configured, Skip
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: INFO  | 12:18:06 0 Running without TFT display!
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: INFO  | 12:18:06 0 No I2C devices found
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: DEBUG | 12:18:06 0 acc_info = 0
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: INFO  | 12:18:06 0 S:B:37,2.6.10
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: INFO  | 12:18:06 0 Init NodeDB
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: INFO  | 12:18:06 0 Load /prefs/nodes.proto
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: INFO  | 12:18:06 0 Loaded /prefs/nodes.proto successfully
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: INFO  | 12:18:06 0 Loaded saved nodedatabase version 24, with nodes count: 1
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: INFO  | 12:18:06 0 Load /prefs/device.proto
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: INFO  | 12:18:06 0 Loaded /prefs/device.proto successfully
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: INFO  | 12:18:06 0 Loaded saved devicestate version 24
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: INFO  | 12:18:06 0 Load /prefs/config.proto
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: INFO  | 12:18:06 0 Loaded /prefs/config.proto successfully
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: INFO  | 12:18:06 0 Loaded saved config version 24
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: /var/lib/meshtasticd/.portduino/default/prefs/module.proto does not exist
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: ERROR | 12:18:06 0 Could not open / read /prefs/module.proto
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: INFO  | 12:18:06 0 Install default ModuleConfig
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: INFO  | 12:18:06 0 Load /prefs/channels.proto
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: INFO  | 12:18:06 0 Loaded /prefs/channels.proto successfully
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: INFO  | 12:18:06 0 Loaded saved channelFile version 24
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: /var/lib/meshtasticd/.portduino/default/prefs/uiconfig.proto does not exist
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: ERROR | 12:18:06 0 Could not open / read /prefs/uiconfig.proto
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: DEBUG | 12:18:06 0 cleanupMeshDB purged 0 entries
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: DEBUG | 12:18:06 0 Use nodenum 0xd55a5741
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: DEBUG | 12:18:06 0 Expand short PSK #1
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: INFO  | 12:18:06 0 Wanted region 0, using UNSET
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: DEBUG | 12:18:06 0 Coerce telemetry to min of 30 minutes on defaults
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: DEBUG | 12:18:06 0 Save to disk 0
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: DEBUG | 12:18:06 0 Use compiled/slipstreamed tzplaceholder
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: DEBUG | 17:18:06 0 Set Timezone to GMT0
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: DEBUG | 17:18:06 0 Read RTC time as 1750180686
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: DEBUG | 17:18:06 0 Start multicast thread
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: DEBUG | 17:18:06 0 UDP Listening
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: DEBUG | 17:18:06 0 NeighborInfoModule is disabled
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: INFO  | 17:18:06 0 External Notification Module Disabled
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: DEBUG | 17:18:06 0 Activate sx1262 radio on SPI port /dev/spidev0.0
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: DEBUG | 17:18:06 0 SX126xInterface(cs=-1, irq=22, rst=18, busy=4)
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: DEBUG | 17:18:06 0 SX126X_DIO3_TCXO_VOLTAGE defined, using DIO3 as TCXO reference voltage at 1.800000 V
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: INFO  | 17:18:06 0 Start meshradio init
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: INFO  | 17:18:06 0 Radio freq=906.875, config.lora.frequency_offset=0.000
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: INFO  | 17:18:06 0 Set radio: region=UNSET, name=LongFast, config=0, ch=19, power=30
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: INFO  | 17:18:06 0 myRegion->freqStart -> myRegion->freqEnd: 902.000000 -> 928.000000 (26.000000 MHz)
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: INFO  | 17:18:06 0 numChannels: 104 x 250.000kHz
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: INFO  | 17:18:06 0 channel_num: 20
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: INFO  | 17:18:06 0 frequency: 906.875000
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: INFO  | 17:18:06 0 Slot time: 28 msec
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: INFO  | 17:18:06 0 Final Tx power: 30 dBm
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: INFO  | 17:18:16 10 SX126x init result -2
Jun 17 12:18:16 raspberrypi-nebra-2 meshtasticd[569]: WARN  | 17:18:16 10 No sx1262 radio

Expected result

sx1262 initializes successfully and the application launches

Workaround

This was solved by uncommenting /etc/meshtasticd/config.d/NebraHat_1W.yaml:L8 (the CS line). This essentially un-does 122a981

[jp-bennett]

If you're using one of the set CS pins (pin 7 or 8 on the Pi), you can do this either way. If the kernel is controlling this pins, then don't define CS in config.yaml, and just pick the right Spidevice. But if you've disabled the kernel control of the CS pins, or your LoRa device is using other pins, you'll need to specify the CS pins in config.yaml so meshtasticd can manage them.

To put it another way, either the kernel or Meshtasticd must manage the CS pins, but not both.

[wehooper4]

If you're using one of the set CS pins (pin 7 or 8 on the Pi), you can do this either way. If the kernel is controlling this pins, then don't define CS in config.yaml, and just pick the right Spidevice. But if you've disabled the kernel control of the CS pins, or your LoRa device is using other pins, you'll need to specify the CS pins in config.yaml so meshtasticd can manage them.

To put it another way, either the kernel or Meshtasticd must manage the CS pins, but not both.

The issue is somehow end users or ending up in the state where ether the kernal or meshtastic is controlling it, and it's not consistent.

I need it every time, Meshtastic is controlling it. But somehow about half the end users end up with it blowing up. I suspect there is something in the setup instruction on the meshtastic page that can lead to them enabling the SPI interface in a different way that causes this?

[turnrye]

@wehooper4 you mean like this? https://meshtastic.org/docs/hardware/devices/linux-native-hardware/#spi-raspberry-pi

Also, I'd consider not only what those docs say, but what they don't say. For folks who don't know much about raspberry pi hardware interfaces (✋), or have used other pi peripherals with other customs, one may be accustomed to going into raspi-config and just slamming through the interface menu making some elections by word association.

I wonder if a way to better handle the end user is for there to be a step to verify the state of the CS pin, or even somehow bake that check in to the error messaging / debugging?

[wehooper4]

When it’s turned on in the YAML and the OS is trying to control it there is a GPIO error and Meshtastic blows up. But at least it tells you vs just “oh hey, I can’t find the radio” because it never actually enabled it.

But my hypothesis is it’s related to raspi-config vs dumping in the commands from the page you linked above. That said I haven’t tried to set one up that way to verify.