7i95t firmware brick because i flashed a 7i95 bitfile in the fallback

Hi PCW,

I managed to brick the firmware as well while following your instructions above.

I downloaded the Efinity software, along with the flashing utility from the link you provided. When I attempted to compile the project, I received the error:

“Project contains some invalid configuration. Please see details in console.”

It appears that some files may be missing.

I then tried using files from Mesa and was able to compile successfully. However, when I attempted to flash the board, I encountered the following error:

“ERROR: The FPGA given in the bitstream file does not match the FPGA you are trying to program. Check that you are using the correct bitstream file.”

Thank you in advance for your help.

Best regards,

What program  printed the error message?

Are you using the latest mesaflash?

Could you JTAG program the FPGA chip and get Ethernet access?

If so what does

mesaflash --device Ethernet --addr [card_ip_addr] --verbose

print?



 

Efinity software reported an error. After reviewing my wiring, I was able to make progress.

I can now connect via JTAG using the Efinity Programmer tool. When I click Start Program, it appears to detect the board, and I receive the message “Device is in user mode.”

At this point, I’m not sure what the next step should be.

I have jumpers W15 and W16 set to UP,UP position so I can attempt an Ethernet connection to 192.168.1.121 However, when I run the following command:

mesaflash --device Ethernet --addr 192.168.1.121 --verbose

No ETHERNET board found

Did you manage to program the FPGA via JTAG?

This would be shown by the green LEDs flashing in sequence
and the link and speed LEDs lighting up on the 7I95T's RJ-45
jack.

I do not think that I was able to program the FPGA.

I am stuck where programmer says "Device is in user mode!"

I do not know what is the next step

Our initialization script does the programming from the command line:

efx_run.py seveni95t.xml --flow program --pgm_opts mode=jtag

Pretty sure use this uses a .hex or .bit file (in the outflow directory)