6i24-25 and 7i52S

Your github link gets me mesaflash version 3.4.0; thanks. I got the code to compile with no errors, and the help text now includes a 6i24 and 6i25 for the --recover option! However, I still can't get mesaflash to find my board.

I have tried changing the clock speed from 33 to 66 MHz. I tried using the bridge EEPROM jumper in both EEPROM and default states, with both 33 and 66 MHz PCI clocks. I keep getting board not found errors for 5i24 and 6i24 options to mesaflash, with or without --recover.

The init and done LEDs on the board are constantly lit from power up to power off.

Oddly, changing the jumper for pull-up resistors on the FPGA causes the computer to not boot with a video card. All the other jumpers are in the default (5V) settings for the IO ports, etc.

Going to try the same card in a different computer, just to see if the linux install or PCI-E bus is the problem.

So, anyone have ideas on why the board stopped showing up at all? Any ideas on something to try to get the board back talking to the CPU?

Thanks.

Tried the card in another machine, with no better luck. Still have both LEDs turned on, no board detected with or without the --recover option. Is there something simple I am missing?

Thanks.

If you wrote an incorrect bitfile, the stuck on LEDs and no normal card access
are pretty much guaranteed.

It look like even Mesaflash 3.4 doesnt know that 6I24s are recoverable, I will try and add that to the program tomorrow when I have access to a 6I24.

Did you try lying and telling mesaflash the board was a 6I25?

I have fixed the board, by telling mesaflash 3.4 that I have a 6i25 with the --recover option. That found the board, and I was able to write the 5i24_16....7i52s.bit file to the EEPROM. A power cycle and the board responds as a 5i24, with the expected pin assignments!

Thanks for all the help, and I hope anyone with a similar problem can get right to the end with this thread!

i'll try to fix mesaflash but the trick is that when doing recovery you cannot
identify the board. I suspect The easiest patch around would be to have a
"recover" card name

p.gettings@gmail.com wrote: I have fixed the board

It's probably not a great idea to use an actual email address as your forum ID.