LinuxCNC + Orange Pi (allwincnc)

Are you not updating packages? They don't need to be updated!

I have tried both ways, updating and not updating. So far no luck. I pretty much gave up until my new Orange Pi board arrives. I had the O-Pi in the house to do the backup, but when I couldn't get it to work I just restored the image I already had and put it back to work on the mill. Once the new board comes I'll try again.

Hello, I bought a Orange PI 5 16Gb and I successfully installed (thanks to some users of this forum..) Armbian RT and linuxcnc.
Well, last step missing is connect GPIO to a interface board I self made and it's currently used with a RPI4.
Orange PI5 is much more performant so I would like to use in place of RPI.
With RPI I used the specific driver included in Linuxcnc 2.9 but I don't have an idea on how to do for OPI5.
I read about ARISC driver but seems not updated for OPI5.
Any hints? ARISC seems not included in default Linuxcnc installation, in order to try, what I have to do?

I've tried to install ARISC on OrangePi prime, with newest Armbian and RT-patched kernel, but failed. In fact I also tried to load any program to RISC core (even very simple test program), and that also did not worked - every time I've had a system freeze on boot. I'm afraid, that old methods will not work on new system, and it will require some work to get ARISC driver running again.

ARISC driver is a rather deep hack to a OrangePi, that uses more or less undocumented features of the processor. I don't think it will ever be included to mainline. To install it manually You need a compiled binary for a RISC core and u-boot script both placed in a /boot/ directory on SD card. I can help if You wish to try (I gave up and bought mesa ).

Why not to try?!
I know it takes time..
Well, I investigated these days and now I have doubts on which way to try (as first image missing /media/kunena/emoticons/wink.png)
1. Edit and try ARISC driver
2. Implement a new driver based on WiringOP

The first is a driver that works but sure with wrong addresses, references etc.. not sure I'm able to find a good reference and exchange what is wrong for new hardware.
The second way, maybe is more promising because I tested WiringOP and with OPI5 works to read and write IO, and it's in C, so if I will find a way to clean a C driver in a way I can use functions in HAL file, I'm pretty sure we can use functions from WiringOP classes..

I'm now searching on web or trying to clean an existing driver and get a good starting point.
I try to consider the Raspberry driver and ARISC and try the best base.
Can you help me on this?
Do you know where I can find documentation for create a C driver from scratch and build it?
By the way I was able to build a first prototype using HALCOMPILE and it generated a "so" file.
It was not working but most probably it should be cleaned more that I did...
 

The author wrote that it was a u-boot problem. And every time a new version of Armbian comes out, the u-boot changes!
The author wrote about it on the forum www.cnc-club.ru/forum/viewtopic.php?t=16788 .
That's it!