Bricked 7i92 :-( SOLVED THANK YOU)

Hi all,

I'm hoping someone can help me out ?..

I was playing around with pathpilot and it some how wrote the wrong bitfile to my 7i92...
Thinking it was an electrical fault I grabbed my second 7i92 and promptly bricked that as well.

Now,


I can download a bitfile to jt using xilinx impact tool and jtag (DLC10) ...and can happily ping it on192.168.1.121
UNTIL I REMOVE THE POWER then it looses it's memory.

I have used setname to call it 7I92 and that seems to work fine.

but if I try to use mesaflash (on windows) then all I get is device name invalid..if I move over to my Linux machine I cannot get passed network unreachable,...I was hoping I could use mesaflash to totally restore its memory...should this even work?

and if I remove the power its back to square one

Can someone give me a bit more info on where I need to shoot the bitfile?...
There are prom regions available but I have no idea if this is the right thing to do or what the details are..prom type size, width..etc...

So yeah, I seem to be up against it and could really use a bit of guidance....

Thank you in advance for a great service...and Mesa for a great product too....shame I'm the
Weak part in the equation!

Cheers

Ian.

You should be able to recover using either the ancient windows mesaflash
(which doesn't know about the 7I92) or the current Linux mesaflash
by programming the FPGA via JTAG and them using mesaflash
to write the EEPROM

The ancient windows mesaflash will work if you tell it that the card is a 7i80
and set these environment variables:
set protocol=direct
set interface=elbp16
set ipaddr=192.168.1.121

Hi PCW

Thank you for your advice.

i have carried out the instructions as you suggested....
both jumpers are at the bottom

I can ping the device and the four leds will change state

if I use scaneth i get device 7I92..

but if i enter setname 7i80 i get the following...
Old Name:

connection timed out.

my ip settings in windows are

tcp /ipv4

192.168.1.1
255.255.255.0


I could set the name earlier but ipconfig is not my strong suit..but if i can ping it and get a reply that should be it


i am trying not to get on your nerves but i'm a bit lost as to what;s up.

Thank you so far.....

Ian

Not sure why you would use setname at all
(Did path pilot change the card name?)
In any case the card name should be 7I92

I was just saying that the old windows mesaflash
doesn't care about the card name
so:

mesaflash --device 7i80 --write new7I92bitfile.bit

will work on a 7I92 (or 7I76E or 7I96 etc)

Thank you PCW

I sent a connection req.

Nothing sinister but any chance of a P.M.?

NOW I SEE!...

I now have at least one functional 7I92!

Sorry to be a pita!

my previous post still stands by the way

But if not then thank you anyway, I know you do this for free and your time is valuable..I wanted to buy you a beer!.......

Best

Ian

I try to avoid PMs because in general posts may
be valuable to many viewers. No beer required, its
a Sunday and I would rather do this than yard work...

lol..


"Not sure why you would use setname at all
(Did path pilot change the card name?)
In any case the card name should be 7I92"

No i did that, i tried 5I25 in case mesaflash didn't know 7I92

Then changed it back to 7I92 when it made no difference..

now i cant change it at all BUT it reboots just fine after a power cycle so i think can work with that..

Sorry to sound like a dumb@ss but .......I'm still learning.

Thank you for your help, and a great product (despite my best efforts at sabotage)...

Ian

"I try to avoid PMs because in general posts may
be valuable to many viewers. No beer required, its
a Sunday and I would rather do this than yard work... "

Hell yeah!

But it's your Sunday not mine!

I greatly appreciate your help,. next time I'm in town the beers are on me!...covid permitting of course!