Mesa Card: "No 7I92 board found" using mesaflash

I have a 7i92M card and when I try to download a .bit file using mesaflash (or mesaflash3), I get the message "No 7i92 board found". I can ping 192.168.1.121 -- so the ethernet connection is working fine.

Searching through the forum I see the following:

arghh, looks like I sent out some 7I76E cards with the card name not set.

This can be fixed by running these commands in Windows (in a cmd shell)
(maybe mesaflash can be taught to do this eventually)

set protocol=direct
set interface=elbp16
set ipaddr=192.168.1.121
setname 7I76E-16

setname is here:

freeby.mesanet.com/setname.exe

Questions:
[1] Is there a Linux version of setname?
[2] If I substitute "7I92E-16" in place of "7I76E-16", is that the correct name?
[3] Could the problem be something else?

Thanks.

Make sure you use the latest mesaflash
If you have a recent linuxcnc installation do

sudo apt-get install mesaflash

Thanks! That fixed the problem. (previously, I was using the executable that came as part of 7i92.zip).

Hello,

I want to flash my 7i92M ethernet board, which is paired with 7i76 step/dir card.
The problem is the above mentioned error message after mesaflash --device 7i92 --write 7i92_7i76x1D.bit: "No 7i92 board found."

We try everything to solve the problem without success.

- mesaflash is updated (current version: 3.1.0, Linuxcnc version 2.7.0).
- Jumper configuration:
- 7i92M: W5-DN, W6-DN (Fix IP: 192.168.1.121)
- 7i76: W3-RIGHT (Setup Mode)

- The cards has proper +5VDC and +24VDC power.
- In Linux we configured the ethernet interface based on instruction in hm2_eth documentation.
auto eth1
iface eth1 inet static
address 192.168.1.1
hardware-irq-coalesce-rx-usecs 0

- We cant ping the device (ping 192.168.1.121), the answer is: "Network is unreachable".
- We have two identical 7i92 cards with same results.

What to try to solve the problem?

Best regards,
Attila.

- 7i76: W3-RIGHT (Setup Mode)

7I76 W3 must be in the left hand position (setup mode is only upgrading for 7I76 firmware)

- We cant ping the device (ping 192.168.1.121), the answer is: "Network is unreachable".

This error means you have a host network setup problem, not related to the 7I92 at all

In general I do not suggest using the 192.168.1.121 address except for initial testing and error
recovery.

This is because this address is likely to overlap with normal NAT connected internet
access IP address ranges

For working systems I suggest using the 10.10.10.10 7I92 address

HalaszAttila wrote:

- We cant ping the device (ping 192.168.1.121), the answer is: "Network is unreachable".
- We have two identical 7i92 cards with same results.

What to try to solve the problem?

Best regards,
Attila.

One of two things......

1. Your mesa cards are not configured properly re: doesn't have an ip address
2. Your ethernet interface not working on your linux box. Can you ping your eth1?


/EDIT oops. PCW beat me to it.

Thank for quick replay,

i put the 7i76 jumper in left hand position (Operate mode), and 7i92 jumper in W5-DN, W6-UP (Fixed from eeprom). But the result is the same.

The host PC is a new installed from ISO (Linuxcnc 2.7.0). And not connected to the internet yet.
I try: "ping eht1" the result is: Unknown host.
How to configure the ethernet interface to be "eth1"? (I am newbie in linux).

Attila.

HalaszAttila wrote:

Thank for quick replay,

i put the 7i76 jumper in left hand position (Operate mode), and 7i92 jumper in W5-DN, W6-UP (Fixed from eeprom). But the result is the same.

The host PC is a new installed from ISO (Linuxcnc 2.7.0). And not connected to the internet yet.
I try: "ping eht1" the result is: Unknown host.
How to configure the ethernet interface to be "eth1"? (I am newbie in linux).

Attila.

No, ping the IP address of eth1.

what does
ifconfig -a
print?

( The command might be /libexec/ifconfig -a on debian )

ping 10.10.10.1 -> Unknown host.

Here is the etc/network/interfaces file:
auto lo
iface lo inet loopback

auto eth1
iface eth1 inet static
address 10.10.10.1
hardware-irq-coalesce-rx-usecs 0