- Hardware & Machines
- Driver Boards
- 7i95t firmware brick because i flashed a 7i95 bitfile in the fallback
7i95t firmware brick because i flashed a 7i95 bitfile in the fallback
- marcom528
- Offline
- New Member
Less
More
- Posts: 2
- Thank you received: 0
13 Jan 2025 10:32 #318862
by marcom528
7i95t firmware brick because i flashed a 7i95 bitfile in the fallback was created by marcom528
hello LinuxCnc Community,
i recently bought a 7i95t with a trion fpga from the company efinix on it, luckily i flashed a 7i95 bitfile to the fallback and now i bricked the firmware so im not able to get a connection to the mesa card over ethernet(CR16 is steady on after powering up the mesa card, which indicates there is something wrong with the fpga config), what makes sense...
After reading the 7i95t datsheet, chapter"Host Interfaces" it says "DO NOT write 7I95 bitfiles to the 7I95T", yeah shit happens...
now i have some questions how to get the 7i95t working again?!
So theres a connector "P2 JTAG" on the 7i95t where you can flash the correct bitfile to the fpga using a hardware interface and the efinity software (there is a free license aviable on their website)
what kind of interface do i need? do i need a development kit from efinty or can i use other brands jtag interfaces like 410-299 | Digilent JTAG-HS3, Xilinx-Werkzeug | RS
what bitfile i have to flash? 7i95td.bin?
how to flash the bitfile to the fpga with the jtag interface adapter using the efinity software?
i hope theres someone out there, whos so deep into this topic, who can help me
thanks in advance!
best regards Marco
i recently bought a 7i95t with a trion fpga from the company efinix on it, luckily i flashed a 7i95 bitfile to the fallback and now i bricked the firmware so im not able to get a connection to the mesa card over ethernet(CR16 is steady on after powering up the mesa card, which indicates there is something wrong with the fpga config), what makes sense...
After reading the 7i95t datsheet, chapter"Host Interfaces" it says "DO NOT write 7I95 bitfiles to the 7I95T", yeah shit happens...
now i have some questions how to get the 7i95t working again?!
So theres a connector "P2 JTAG" on the 7i95t where you can flash the correct bitfile to the fpga using a hardware interface and the efinity software (there is a free license aviable on their website)
what kind of interface do i need? do i need a development kit from efinty or can i use other brands jtag interfaces like 410-299 | Digilent JTAG-HS3, Xilinx-Werkzeug | RS
what bitfile i have to flash? 7i95td.bin?
how to flash the bitfile to the fpga with the jtag interface adapter using the efinity software?
i hope theres someone out there, whos so deep into this topic, who can help me
thanks in advance!
best regards Marco
Please Log in or Create an account to join the conversation.
- PCW
- Away
- Moderator
Less
More
- Posts: 17994
- Thank you received: 4838
13 Jan 2025 15:35 - 13 Jan 2025 15:38 #318870
by PCW
Replied by PCW on topic 7i95t firmware brick because i flashed a 7i95 bitfile in the fallback
Yeah, JTAG is the only easy way out if you flashed the fallback area of a 7I95T
with incorrect firmware. (Really, you should never update the fallback area)
I use a FT4232H USB --> JTAG adapter for programming
The way it's done when manufacturing is to program the FPGA (not the flash)
With the Efinity tool and then use mesaflash to re-write the fallback and user
flash areas.
(This is about 30X faster than writing the flash via JTAG)
I can upload or make available the (linux/bash) initialization scripts/directories
used later today. You may need to edit the paths in the script to match your Efinity
installation.
with incorrect firmware. (Really, you should never update the fallback area)
I use a FT4232H USB --> JTAG adapter for programming
The way it's done when manufacturing is to program the FPGA (not the flash)
With the Efinity tool and then use mesaflash to re-write the fallback and user
flash areas.
(This is about 30X faster than writing the flash via JTAG)
I can upload or make available the (linux/bash) initialization scripts/directories
used later today. You may need to edit the paths in the script to match your Efinity
installation.
Last edit: 13 Jan 2025 15:38 by PCW.
The following user(s) said Thank You: tommylight, besriworld
Please Log in or Create an account to join the conversation.
- PCW
- Away
- Moderator
Less
More
- Posts: 17994
- Thank you received: 4838
13 Jan 2025 21:11 - 14 Jan 2025 00:47 #318881
by PCW
Replied by PCW on topic 7i95t firmware brick because i flashed a 7i95 bitfile in the fallback
freeby.mesanet.com/95tinit.tgz
Not sure about the executables (might be too old a libc version),
but you can get by by just programming the FPGA via JTAG
and running the two mesaflash commands.
Here is the FTDI4232 --> 10 pin header connection:
freeby.mesanet.com/pdf/parallel/4232efin.pdf
Not sure about the executables (might be too old a libc version),
but you can get by by just programming the FPGA via JTAG
and running the two mesaflash commands.
Here is the FTDI4232 --> 10 pin header connection:
freeby.mesanet.com/pdf/parallel/4232efin.pdf
Last edit: 14 Jan 2025 00:47 by PCW.
The following user(s) said Thank You: marcom528
Please Log in or Create an account to join the conversation.
- cornholio
- Away
- Platinum Member
Less
More
- Posts: 1127
- Thank you received: 373
13 Jan 2025 23:24 #318901
by cornholio
Replied by cornholio on topic 7i95t firmware brick because i flashed a 7i95 bitfile in the fallback
I was going to suggest an FT2232 (for more reliable I've found than the USB Blaster clones, and faster under Linux than the Genuine Xilinx PP porgrammer), as that what I use, along with openFPGALoader, but seeing that it doesn't support JTAG for the Efinity FPGAs I decided to let it slide. Plus I was sure if the SPI programming method was usable with the Mesa boards.
The following user(s) said Thank You: marcom528
Please Log in or Create an account to join the conversation.
- marcom528
- Offline
- New Member
Less
More
- Posts: 2
- Thank you received: 0
15 Jan 2025 07:50 #319007
by marcom528
Replied by marcom528 on topic 7i95t firmware brick because i flashed a 7i95 bitfile in the fallback
thanks for the fast response PCW!
for my understanding!?
1)flashing the firmware to the fpga using the infinty software and the ftdi4232 jtag interface.
am i flashing to the fpga ram (Volatile Memory)? after power loss, the firmware is gone right?
2)write the firmware to the fallback and the eeprom (is it a part of the fpga? or is it an external eeprom on the 7i95t?)
mesaflash --device 7I95T --fallback --write FPGAFILE.BIN
mesaflash --device 7I95T --write FPGAFILE.BIN
after writing the .bin file it should be permanently saved to the storage and the 7i95t should work porperly again after power loss?
the ftdi4232 mini should be deliverd on friday, i'll give it some trail and error then
for my understanding!?
1)flashing the firmware to the fpga using the infinty software and the ftdi4232 jtag interface.
am i flashing to the fpga ram (Volatile Memory)? after power loss, the firmware is gone right?
2)write the firmware to the fallback and the eeprom (is it a part of the fpga? or is it an external eeprom on the 7i95t?)
mesaflash --device 7I95T --fallback --write FPGAFILE.BIN
mesaflash --device 7I95T --write FPGAFILE.BIN
after writing the .bin file it should be permanently saved to the storage and the 7i95t should work porperly again after power loss?
the ftdi4232 mini should be deliverd on friday, i'll give it some trail and error then
Please Log in or Create an account to join the conversation.
- PCW
- Away
- Moderator
Less
More
- Posts: 17994
- Thank you received: 4838
15 Jan 2025 15:02 #319030
by PCW
Replied by PCW on topic 7i95t firmware brick because i flashed a 7i95 bitfile in the fallback
Yes, you first write firmware to the FPGA RAM which gives you Ethernet access to the card.
Then you write the user and fallback firmware to the user and fallback areas of the EEPROM
with mesaflash.
(Your example shows the same file written to both, this will not work, you must write a fallback
file to the fallback area and a user file to the user area)
The init95t script in the .tgz file does all this but you can remove all the MAC/Netmask/IP address
writing stuff as these have already been done and are not affected by what you write to the flash memory.
Then you write the user and fallback firmware to the user and fallback areas of the EEPROM
with mesaflash.
(Your example shows the same file written to both, this will not work, you must write a fallback
file to the fallback area and a user file to the user area)
The init95t script in the .tgz file does all this but you can remove all the MAC/Netmask/IP address
writing stuff as these have already been done and are not affected by what you write to the flash memory.
The following user(s) said Thank You: marcom528
Please Log in or Create an account to join the conversation.
Moderators: PCW, jmelson
- Hardware & Machines
- Driver Boards
- 7i95t firmware brick because i flashed a 7i95 bitfile in the fallback
Time to create page: 0.063 seconds