Raspberry Pi 4 with Mesa 7c81

Read the current configuration:
sudo mesaflash --device 7c81 --addr /dev/spidev0.0 --spi --readhmid
(I would verify that this works reliably before trying to flash new firmware)

Write new firmware to the flash EEPROM:
sudo mesaflash --device 7c81 --addr /dev/spidev0.0 --spi --write 7c81_g540x2d.bit

Load the FPGA from the current flash EEPROM image:
sudo mesaflash --device 7c81 --addr /dev/spidev0.0 --spi --reload

Thank you so much for the help!

BTW the easiest way to generate a working hal/ini configuration for the 7C81 is to use
pncconf and setup say a 5I25+G540 configuration. Then change the card name in the .ini file
and driver name in the hal file

Can’t thank you guys enough for all of your time and help. I have successfully installed Mesaflash but now when I try read from the 7c81 with these two options here are my results:

sudo mesaflash --device 7c81 --addr /dev/spidev0.0 --spi --readhmid

Results in “unrecognized option ‘—addr/dev/spidev0.0’”

sudo mesaflash --device 7c81 --spi --readhmid

Results in
“open: Bad address
No 7c81 board found”

missing space?

Where? I have looked back over this and tried several times

I don’t think that’s it. Is there anything else you can think would result in it not seeing the 7c81. I thought I had it!

Works for me, the error shows that the --addr token is merged with the spi device name so

sudo mesaflash --device 7c81 --addr/dev/spidev0.0 --spi --readhmid
mesaflash: unrecognized option '--addr/dev/spidev0.0'

but

sudo mesaflash --device 7c81 --addr /dev/spidev0.0 --spi --readhmid
open: No such file or directory
No 7C81 board found

Which is the correct result since this PC has no /dev/spidev0.0

I missed the space after addr. My message is now the same as yours except I have a 7c81 connected...

The connection is working as I am able to manually toggle pins using halcmd. (Turning user leds on and off)

I don’t know what to think. Can’t understand why it won’t read the board but nervous as my ultimate goal is to flash it with the g540_x2d configuration

Do you have the latest Mesaflash and LinuxCNC?

There was a problem with earlier versions where running the hm2_rpspi
driver disabled mesaflash until a reboot.

Also how long is your connecting cable (it should be no longer than ~2 inches)