LitexCNC: firmware and driver for 5A-75B and 5A-75E

h
How can flash the firmware to 5A-75E?

litexcnc flash_firmware <filename-with-extension-svf>
How to create <filename-with-extension-svf> file?
Do I have to download it from somewhere?

I think this one has been answered on GitHub, but for future reference. If you have a configuration file (some examples are available here ), lets say 5a-75b_v8.0_i24o32.json, you can compile this file with:
When the compilation is successful, a new directory with the compiled firmware will be created. The name of this directory is equal to the name of the configuration file. The .svf-file required for flashing can be found in the gateware sub-directory. For this example you can change the directory and then flash the firmware with the following commands:
The above command is valid when you use a RaspberryPi in combination with the HUB75HAT as a programmer. If you have a different programmer, such as the FT232R, you have to provide the name of the configuration file for OpenOCD, i.e.:
These commands will flash the firmware only in this session. When you power-cycle the FPGA, the previous program will be loaded again. To make the firmware permanent, one has to flash the NAND-flash on the board. One can use the --permanent flag:

Build firmware fails on 64bit os because needs some software depedency
that is available only for 32 bit.
Any workaround for this error?

Can you post the error?

At this moment there is a known bug with the detection of the correct architecture. Therefore I would recommend to use the -a flag for the command install_toolchain. For example, for installing on a Raspberry Pi:
Or for a 64-bit Desktop:

That was the problem..
Because i don't have raspberry pi how can flash the firmware?
I have xgecu flash memory programmer but to program the flash chip (unsolder-program-resolder) needs BIN firmware file not BIT.
Where can i find BIN file for 5A-75E v8.0 ?

The open-source toolchain does not create a .bin-file, only a .svf-file. I cannot help you with converting it to a .bin-file, as I didn't to that before or have the means to test it.

A tool which can possibly do it is bootgen from Xilinx: stackoverflow.com/questions/70701643/how...vert-bit-file-to-bin

An easier path for flashing is to pick-up a FT232R based programmer for a few dollars/Euros. With that you can program using the JTAG headers and it is supported by LitexCNC.

Hello,

have the JOSON examples on the instructions page ever been fully tested?
I have compiled and flashed the example V8.0 12/14 on my 5A-75B V8.2 FPGA board with my Raspberry pi4 according to the described instructions. I have a small gantry milling machine with 2 Y-axes and an additional rotary axis (XYYZA).
To test my Linuxcnc configuration, I made a small test setup with 5 stepper motors.
The first 4 stepper motor outputs on the FPGA board
stepgen.00.... j7:0 with j7:1
stepgen.01.... j7:2 with j7:4
stepgen.02.... j7:5 with j7:6
stepgen.03.... j8:0 with j8:1
work perfectly. The home movement also works without any problems.

The last two stepper motor outputs:
stepgen.04.... j8:2 with j8:4
stepgen.05.... j8:5 with j8:6

show a strange behavior. As soon as a movement (e.g. home movement) is initiated,
the connected stepper motor starts to turn in a certain direction and can only be stopped,
the FPGA board is disconnected from the power supply.
The stepper motor continues to rotate even when the Raspberry is no longer connected to the board.
It doesn't matter which axis I assign this output to in Linuxcnc.
The stepper motor connected to these outputs shows this behavior.
Has anyone ever tested a 5A-75B V8.x with more than 4 axes?

Best regards
Uwe

raspberry pi5 works for flashing or only pi4 works?

vre wrote:

raspberry pi5 works for flashing or only pi4 works?

Pi5 is fully supported and working, also for programming. When using the Pi5 for running LinuxCNC, it is required to select spidev as connection.

Explanation: for Pi4 the pigpio connection is recommended, as the communication is slightly faster. However, the pigpio module is not yet ported to the Pi5 because it has a complete new GPIO chipset.