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

Did you have card access before at 192.168.1.121?

What does

ip a

report?


Also with W5,W6 = UP,UP, the fact that the /INIT led blinks means that
the fallback configuration in the flash EEPROM is valid and still works...
 

I guess I never tried access to 192.168.1.121?
I have always used 10.10.10.11

Jumpers UP,UP

ip a reports

2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether d8:9e:f3:91:96:8a brd ff:ff:ff:ff:ff:ff
altname enxd89ef391968a

Jumpers DN,DN
ip a reports

2: enp1s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
link/ether d8:9e:f3:91:96:8a brd ff:ff:ff:ff:ff:ff
altname enxd89ef391968a

If UP.UP works, stay with that

Then setup you hosts Ethernet interface to a static IP address of say 192.168.1.100

(the current settings will not allow access to the card)

Beautiful!

You are hands down a genius
PING 192.168.1.121 (192.168.1.121) 56(84) bytes of data.
64 bytes from 192.168.1.121: icmp_seq=801 ttl=64 time=0.263 ms
64 bytes from 192.168.1.121: icmp_seq=802 ttl=64 time=0.109 ms

Do I still need to flash the fallback.bin and the .bin file?
if so, how can I point mesaflash to these files?

I remember you mention something about the dpll?

I was trying to create a machine to test the borad

Debug file information:
Note: Using POSIX realtime
./main.hal:37: parameter or pin 'hm2_7i95.0.dpll.01.timer-us' not found
22938
Stopping realtime threads
Unloading hal components
Note: Using POSIX realtime

You need to install a user configuration (the fallback configuration has no modules except GPIO):

mesaflash --device 7i95t --addr 192.168.1.121 --write  7i95t_d.bin 

(7i95t_d.bin  is from the 7i95t.zip file in configs/hostmot2)

Once this is done, you can set the IP select jumpers to DOWN,DOWN (192.168.1.121)
or DOWN,UP (10.10.10.10)