I found the culprit!

Apparently, the customized component that handles the SPI communication with the customized remora-spi firmware is not compatible with trixie.

This is the part in the code that breaks it.

The soc ranges path is different in trixie.

I modified the component so, that when the path does not exist, I just consider it as a Raspberry Pi 5 with RP1 chip, and now it works!

I know it's just a quick and dirty workaround, but works for me.

Finally, after a long wait, the boards have arrived! Now I'm looking to buy the PC to control the machine. Checking all the models you shared before, I couldn't find any of them available in my country for under $700 USD.

However, I found two options: a Dell Optiplex 790 with an i5-2400, and another refurbished PC with an i5-4400 (the seller didn't specify the exact model, just that it could be an Optiplex, HP, Lenovo, or Bangho).

Which one would recommend? Both rely on integrated graphics. Is that going to be an issue in my case? From what I've read, a dedicated GPU is usually recommended, but I'm not sure if that's only for software pulse generation or if it's recommended for hardware-assisted setups too.

Thanks in advance!

I was looking at one of my "bigger ones" and it has a measly 2kB.
About 80 000 lines of G-code. ,
A bit of 2.5D surfacing nothing really exciting.

While gmoccapy.program.progress does display the current progress of the job, it reports the value as whole percent rather that fractional percent. Unfortunately, the HBar widget requires fractional percent between 0.0 and 1.0.

Is there a way to convert the output of program.progress in the HAL file when connecting the signal or will I have to use an on_changed handler to do the conversion?

My background:
 i am working as electrical panel maker for cnc machines for wood routers since 2 years for a company near me as a part timer, or you can say whenever they have a new order. they have been using cheap parallel port card with mach3. Now the computers with parallel ports being scarce they wanted me to find them something that is cheap, reliable, and something somewhat latest in technology.
 This is how I came across linuxcnc. although i knew about it long ago, but never had the chance to work on it. also i couldn't acquire mesa cards till today. so i decided to work on ethercat instead of going for specific hardware.

Hardware i am using:
XINJE DS5C1                                             Drives for axis
EK1100, EL1008, EL2008, EL4002            Beckhoff ethercat modules for input output.

I am not. I just read trivkins and it also supports xyzabc. so ill have a go at that.

Since I had the flexi-pi image on the SSD, I booted it, started linuxcnc in debug mode and saved the output.
I then booted the new LinuxCNC image from, the SD card, and did the same. Started linuxcnc in debug mode and saved the output.
Since the SSD is always connected, I mounted it, and so I could compare the debug output. The only difference was these lines. I don't know where to get this ;library from, I thought it would be part of the "flexi" component that comes withe flexi-pi image.

Searching Google for an answer to this issue it suggested to put a system command in the shutdown.hal file and set the .ini parameter:

SHUTDOWN = shutdown.hal

which I have done.

I've created a bash command script, killglade, which if run from the command line kills the orphaned glade panel.  In my shutdown.hal file I have the following command:

system killglade

However, the panel is not stopped upon shutdown of gmoccapy. The documentation from the web mentioned that the bash script should be in the configuration directory. While not technically in the configuration directory I created a soft link to the actual file which is in my ~/bin directory which in turn is in my search path so the file can be executed from anywhere.

Does anyone have an idea what I may be missing or any insight into running bash scripts with the system command in the shutdown.hal file?

I've attached my killglade script and my shutdown.hal file for your reference. 

Yes, there is an ESTOP input on the board, but it is not triggered.

The communication between the RPi5 and the board is SPI. The firmware flashed is a customized version of remora-spi, tailored for the Flexi-HAL board by Expatria ( github.com/Expatria-Technologies/remora-flexi-hal ).

I don't think there is anything is wrong with the board. As I said, I have multiboot set up with an SSD and an SD card, and I have the customized linuxcnc image on the SSD from Expatria ( github.com/Expatria-Technologies/Flexi-Pi ). If I boot that, everything works.

My best guess is that it is the communication between the board and the Pi through SPI that isn't working for some reason.

Can you check the output of the module with an ohmmeter?

If the PC817 module needs 5V drive you would have to connect it in sinking
mode to the 7I92. ( +5V to PC817 module IN+ 7I92 output to
PC817 module IN-  and active low output )

Is there some other issue with reverse in the hal file
( like PWM connections if you have spindle speed control )