5A-75E

[LisovR]

I apologize in advance, English is not my native language and I use an online translator.

Many thanks to the great specialist @Peter-van-Tol !!!

I used the 5A-75E board. Removed the U19, 20, 21, 22, 38, 39 chips that had an output on Pin 8-15 of the J9-16 connectors. Changed the supply voltage of the buffer microcircuits and their direction.
Initially, I powered the input chips from the J33 contact. But when the connection was broken during the firmware, apparently the FPGA inputs began to work as an output and shorted out with the buffer chips. The FPGA burned out.
A 3.3V additional power supply board was made. It is connected to any J9-16 connector and supplies power to Pin 13,15 and to the buffer chips. Now for security reasons you can disable inputs when reflashing. The input opto-isolator is connected to Pin 13,15 - 3.3V and 4,16 - GND.
The electronic part of the machine is powered by two 5VDC power supplies: a 5A-75E board and 24VDC (reduced to 20V) sensors and encoders.

Power board 3.3v

Stepper motor output board

Relay and other consumer output board up to 150mA and 30v.

PNP sensor input board 24VDC (I had these)

NPN encoder input board 24VDC

It turned out like this

FT232RL firmware interface converter

The jumper for selecting the output supply voltage has been removed, they are powered from contact J33,34

The firmware method is taken from here

openFPGALoader [options] -cft23XXX --pins=TDI:TDO:TCK:TMS /path/to/bitstream.ext

value | ID | JTAG

TXD | 0 | J27 TCK
RXD | 1 | J32 TDI
RTS | 2 |
CTS | 3 | J31 TMS
DTR | 4 | J30 TDO
DSR | 5 |
DCD | 6 |
RI | 7 |
Vcc | | J33 (3.3в)
GND | | J34 (GND)

We use the command

openFPGALoader --unprotect-flash --cable ft232RL --pins=RXD:DTR:TXD:CTS -f FoXCNC_5a-75e_v8.2_v1.3/gateware/colorlight_5a_75e.bit

To compile the firmware, it is better to use the command with the -a parameter

litexcnc build_firmware FoXCNC_5a-75e_v8.2_v1.3.json --build -a

We will additionally receive the alias.hal file which, when used in LinuxCNC, will give us aliases for the module elements and when changing the firmware, there will be no need to change the hal files.
To use aliases in the ini file, you must first specify the hal file with the litexcnc driver connection, then alias.hal and then the hal file with module processing. Only in this case will everything work!!!
I am attaching all the files of my 4-axis machine with the ability to work depending on the selected hal file: only with stepper motors, motors and an ecoder and in ClosedLoop mode. Spindle control via RS485 with a frequency converter. Additionally, the xhc-hb04 remote control is connected.

FoXCNC.zip

For fun, I did a test, I knew the result in advance.
LinuxCNC 2.9.4
LitexCNC 1.3.4
The same file was used for the machine operation.

Debian 10 (Buster)

Debian 12 (Bookworm)

In Debian 12, the jitter is several times higher and this is very noticeable in the operation of the engines in ClosedLoop mode