7i92TM pings but not recognised by mesaflash

Robbin wrote:

yesterday i installed a fresh debian bookworm with 2.9 suplied form the downloads section

Mesaflash is s seperate install to linuxcnc and it will not be up to date in Debian 12. It does exist in the Linuxcnc repository

So...
i updated mesaflash to version 3.5

still able to ping, but no board found...
could there be a problem in my network settings?

What is the exact mesaflash command you used and what was the exact response?

I would try:

mesaflash --device 7i92t --addr 10.10.10.10 --readhmid

That did the trick!
thank you so much!

I think there's a bug in mesaflash, it really should belly-ache
if you don't supply an IP address with an Ethernet card.

Thanks PCW!!!

I had Same issue with the same 7i92TM Mesa card (Debian 10, linuxcnc-2.8.2-buster).
i tried to go forward but i had the below

SITUATION:

When trying to load the firmware for generical parallel break board cards to the mesa card 7i92 the init red led (CR6) turned on and remained steady 30 minutes after starting the mesaflash --write process.

Furthermore, the mesaflash process seems never ends in the computer screen.

The order i executed was:

mesaflash --device 7i92t --addr 192.168.1.121 --write 7i92_PROB_RFx2D.bit

The CR1, CR2, CR3 and CR4 yellow leds turn on and off since the very begining and never stop doing it.

Find pleaase below a link showing a picture of the 7i92 card having the CR6 init led on

snipboard.io/W7YH4P.jpg
 

QUESTIONS:

1/3 What does the CR6 red INIT led means if it remains steady all the time?
Let me remark the system prompt (root@host:route#) is not shown after 2 hours. So it seems the writing process is still in progress in the computer.
Is that a sofware bug??
Is CRTL+C the best option to stop this process?

2/3: How long should it take to load a .pin file of 337.2KiB to the 7i92 mesa card?

3/3 Where can i get uncorrupted .pin files??

In the 7i92 manual there is a paragraph saying:

FALLBACK INDICATION
Mesa’s supplied fallback configurations blink the red INIT LED on the top right hand side of the card if the primary configuration fails and the fallback configuration loaded successfully. If this happens it means the user configuration is corrupted or not a proper configuration for the 7I92s FPGA. This can be fixed by running the configuration utility and re-writing the user configuration.

But In my case the red CR6 init led remains steady, not blinking.

Does it mean i must repeat the same process executing the same command?

mesaflash --device 7i92t --addr 192.168.1.121 --write 7i92_PROB_RFx2D.pin

In case the file 7i92_PROB_RFx2D.bit i used is corrupted is there any safe place to get this file in good contitions?

I downloaded it from www.mesanet.com/software/parallel/7i92.zip


Find please below another manual paragraf refering to failure situation. But in this case the CR2 red led should be on, not the init CR6 led...so i think it should not be necessary to load the fallback bit file

mesaflash --device 7I92 --fallback --write FALLBACK.BIT

FAILURE TO CONFIGURE
The 7I92 should configure its FPGA within a fraction of a second of powerapplication. If the FPGA card fails to configure, the red /DONE LED CR2 will remain illuminated. If this happens the 7I92s EEPROM must be re-programmed via the JTAG connector or (faster) JTAG FPGA load followed by Ethernet EEPROM update.

Thanks in advance for all your assistance.