RISC-V: Portduino critical error: Failed to open posix file

Development
1

Hi there!

I’ve compiled meshtasticd successful on a VisionFive2 RISC-V board. But when I start the daemon I get:

Portduino critical error: Failed to open posix file %s, errno=%d
No hardware spi chip found...

My config.yaml is correct:

### Specify the SPI device to use in /dev/. Defaults to spidev0.0
### Some devices, like the pinedio, may require spidev0.1 as a workaround.
  spidev: spidev1.0

Which exists:

user@starfive:~/development/meshtastic/firmware$ ls -l /dev/spidev1.0 
crw------- 1 root root 153, 0 Feb 18 20:05 /dev/spidev1.0

SPI has been tested and is working.

Maybe someone already build for the RISC-V arch and found a solution for this?

Bye,

Martin

2

20240225_175946
20240225_1759461920×2560 696 KB

Well, the SX1262 works now with my Vision Five 2 :v:

3

Did you end up using a diffirent CS pin or modifying dtb/s at all?

I have received my Milk-V Mars board but already working with the cheapest MilkV Duo ($5 vs $99) currently

image-4
image-41041×775 148 KB

image-5
image-51041×775 96.4 KB

I made a breakout pcb Raspberry Pi Zero size to accept the Waveshare Pi Lora HAt

I also have color tftp dispkay working also
But will modify my v1 board below to accept tft or possible eink

20240224_164018
20240224_1640181920×865 191 KB

1 Like
4

Hi Mark!

I’ve not changed the device tree blob but found a good documentation about the default GPIO pin layout of the VisionFive2. With this I’ve changed the config.yaml to this:

Lora:
  Module: sx1262  # Waveshare SX126X XXXM
  DIO2_AS_RF_SWITCH: true
  CS: 49
  IRQ: 36
  Busy: 44
  Reset: 61

and

spidev: spidev1.0

of course. Also enabling this is a must for the Core SX1262:

DIO3_TCXO_VOLTAGE: true # the Waveshare Core1262 and others are known to need this setting

Currently I’m using the Waveshare Core SX1262 as it is inexpensive and I don’t need GPS.

The custom boards are very cool! As soon I’m done fiddling around with another available development board I’ll also try to make things right! :smiley:

The error message I’ve asked about in the original post is gone when I start the daemon with the absolute path instead of the relative.

Cheers!

1 Like
5

Yes, i might also just make a breakout for the Waveshare sx1262 core,

Currently testing this module directly connected to Milk-V Duo but will look at diy borad with 3V3 LDO