7i80 has been flashed, Still no axis movement.

j@j-OptiPlex-3020:~$ ping 10.10.10.1
PING 10.10.10.1 (10.10.10.1) 56(84) bytes of data.
64 bytes from 10.10.10.1: icmp_seq=1 ttl=64 time=0.013 ms
64 bytes from 10.10.10.1: icmp_seq=2 ttl=64 time=0.018 ms
64 bytes from 10.10.10.1: icmp_seq=3 ttl=64 time=0.029 ms
64 bytes from 10.10.10.1: icmp_seq=4 ttl=64 time=0.016 ms
64 bytes from 10.10.10.1: icmp_seq=5 ttl=64 time=0.024 ms
64 bytes from 10.10.10.1: icmp_seq=6 ttl=64 time=0.023 ms
64 bytes from 10.10.10.1: icmp_seq=7 ttl=64 time=0.025 ms
64 bytes from 10.10.10.1: icmp_seq=8 ttl=64 time=0.021 ms
64 bytes from 10.10.10.1: icmp_seq=9 ttl=64 time=0.024 ms
64 bytes from 10.10.10.1: icmp_seq=10 ttl=64 time=0.027 ms
^C
--- 10.10.10.1 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9122ms
rtt min/avg/max/mdev = 0.013/0.022/0.029/0.004 ms
Is this any better? It looks the same to me.

You are pinging your PC, not the 7I80
The 7I80 should be at 10.10.10.10 the
PC at 10.10.10.X where X is between 1 and 254

All devices on a Ethernet network must have
different addresses (IP and hardware)

If i ping 192.168.1.121 this is the result
j@j-OptiPlex-3020:~$ ping 192.168.1.121
PING 192.168.1.121 (192.168.1.121) 56(84) bytes of data.
From 10.10.10.1 icmp_seq=1 Destination Host Unreachable
From 10.10.10.1 icmp_seq=2 Destination Host Unreachable
From 10.10.10.1 icmp_seq=3 Destination Host Unreachable
From 10.10.10.1 icmp_seq=4 Destination Host Unreachable
From 10.10.10.1 icmp_seq=5 Destination Host Unreachable
From 10.10.10.1 icmp_seq=6 Destination Host Unreachable
From 10.10.10.1 icmp_seq=7 Destination Host Unreachable
From 10.10.10.1 icmp_seq=8 Destination Host Unreachable
From 10.10.10.1 icmp_seq=9 Destination Host Unreachable
From 10.10.10.1 icmp_seq=10 Destination Host Unreachable
From 10.10.10.1 icmp_seq=11 Destination Host Unreachable
From 10.10.10.1 icmp_seq=12 Destination Host Unreachable
From 10.10.10.1 icmp_seq=13 Destination Host Unreachable
From 10.10.10.1 icmp_seq=14 Destination Host Unreachable
^C
--- 192.168.1.121 ping statistics ---
14 packets transmitted, 0 received, +14 errors, 100% packet loss, time 13170ms
pipe 3
Peter, I appreciate your help, but I don't know what exactly I can try next.

Ok if your mesa board is
192.168.1.121 the interface for the pc should be any address in the 192.168.1 range but not 192.168.1.121
There should be no DNS nor Gateway.

If your wireless network is using the 192.168.1 network use the 10.10.10 network for the interface that connects to the Mesa card. Do not give the computer the same address as the Mesa card. Do not add a gateway nor DNS entry for that interface, leave them blank. Not leaving them blank will cause issues when you try to connect to the internet when using wireless.

Its time to stop and walk away for a while. You are going around in circles becasue you have not listened to us. That may be becasue you do not understand how to set up a tcp/ip network.

take a break for now

Yes. I know absolutely nothing about setting up any network. I am going to look into it later.
Thank you all for your help.

I really appreciate everyone here who has taken time to help me sort this out.
I believe that I was able to communicate with the 7i80 and I flashed it with a bit file that Peter suggested that I needed for my requirements and hardware.
I have a fresh install of Buster with with the Preempt-RT kernel. The ethernet cable is wired directly to the 7i80 and the wifi is disabled.
This is the result that I got after flashing the card.

flash --device 7i80hd --write 7i80hd_16_sv12.bit
Checking file... OK
File type: BIT file
Boot sector OK
EEPROM sectors to write: 8, max sectors in area: 16
Erasing EEPROM sectors starting from 0x100000...
|EEEEEEEE
Programming EEPROM sectors starting from 0x100000...
|WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW
Board configuration updated successfully.
Checking file... OK
File type: BIT file
Boot sector OK
Verifying EEPROM sectors starting from 0x100000...
|VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV
Board configuration verified successfully.

You must power cycle the hardware or use the --reload command to load a new firmware.

I am unable to move to an axis in open loop in the Pncconfg wzzard.

I clipped this from the debug information report when I try to run LinuxCNC

Debug file information:
Note: Using POSIX realtime
./my_LinuxCNC_machine.hal:10: parameter or pin 'hm2_7i80hd.0.pwmgen.pwm_frequency' not found
2475
Stopping realtime threads
Unloading hal components
Note: Using POSIX realtime

Does the card look like it was flashed correctly?
If so, what should I check first?
BTW I have been enabling wireless and un-enabling it in order to post here while doing this and not possibly interfere with the communication through the ethernet to the card.
Thanks.

What does:

mesaflash --device 7i80hd --readhmid

report?

Hi, Peter

j@j-OptiPlex-3020:~$ sudo mesaflash --device 7i80hd --readhmid
Configuration Name: HOSTMOT2

General configuration information:

BoardName : MESA7I80
FPGA Size: 16 KGates
FPGA Pins: 256
Number of IO Ports: 3
Width of one I/O port: 24
Clock Low frequency: 100.0000 MHz
Clock High frequency: 200.0000 MHz
IDROM Type: 3
Instance Stride 0: 4
Instance Stride 1: 64
Register Stride 0: 256
Register Stride 1: 256

Modules in configuration:

Module: WatchDog
There are 1 of WatchDog in configuration
Version: 0
Registers: 3
BaseAddress: 0C00
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Module: IOPort
There are 3 of IOPort in configuration
Version: 0
Registers: 5
BaseAddress: 1000
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Module: QCount
There are 12 of QCount in configuration
Version: 2
Registers: 5
BaseAddress: 3000
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Module: PWM
There are 12 of PWM in configuration
Version: 0
Registers: 5
BaseAddress: 4000
ClockFrequency: 200.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Module: LED
There are 1 of LED in configuration
Version: 0
Registers: 1
BaseAddress: 0200
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Configuration pin-out:

IO Connections for P1
Pin# I/O Pri. func Sec. func Chan Pin func Pin Dir

1 0 IOPort QCount 1 Quad-B (In)
3 1 IOPort QCount 1 Quad-A (In)
5 2 IOPort QCount 0 Quad-B (In)
7 3 IOPort QCount 0 Quad-A (In)
9 4 IOPort QCount 1 Quad-IDX (In)
11 5 IOPort QCount 0 Quad-IDX (In)
13 6 IOPort PWM 1 PWM (Out)
15 7 IOPort PWM 0 PWM (Out)
17 8 IOPort PWM 1 Dir (Out)
19 9 IOPort PWM 0 Dir (Out)
21 10 IOPort PWM 1 /Enable (Out)
23 11 IOPort PWM 0 /Enable (Out)
25 12 IOPort QCount 3 Quad-B (In)
27 13 IOPort QCount 3 Quad-A (In)
29 14 IOPort QCount 2 Quad-B (In)
31 15 IOPort QCount 2 Quad-A (In)
33 16 IOPort QCount 3 Quad-IDX (In)
35 17 IOPort QCount 2 Quad-IDX (In)
37 18 IOPort PWM 3 PWM (Out)
39 19 IOPort PWM 2 PWM (Out)
41 20 IOPort PWM 3 Dir (Out)
43 21 IOPort PWM 2 Dir (Out)
45 22 IOPort PWM 3 /Enable (Out)
47 23 IOPort PWM 2 /Enable (Out)

IO Connections for P2
Pin# I/O Pri. func Sec. func Chan Pin func Pin Dir

1 24 IOPort QCount 5 Quad-B (In)
3 25 IOPort QCount 5 Quad-A (In)
5 26 IOPort QCount 4 Quad-B (In)
7 27 IOPort QCount 4 Quad-A (In)
9 28 IOPort QCount 5 Quad-IDX (In)
11 29 IOPort QCount 4 Quad-IDX (In)
13 30 IOPort PWM 5 PWM (Out)
15 31 IOPort PWM 4 PWM (Out)
17 32 IOPort PWM 5 Dir (Out)
19 33 IOPort PWM 4 Dir (Out)
21 34 IOPort PWM 5 /Enable (Out)
23 35 IOPort PWM 4 /Enable (Out)
25 36 IOPort QCount 7 Quad-B (In)
27 37 IOPort QCount 7 Quad-A (In)
29 38 IOPort QCount 6 Quad-B (In)
31 39 IOPort QCount 6 Quad-A (In)
33 40 IOPort QCount 7 Quad-IDX (In)
35 41 IOPort QCount 6 Quad-IDX (In)
37 42 IOPort PWM 7 PWM (Out)
39 43 IOPort PWM 6 PWM (Out)
41 44 IOPort PWM 7 Dir (Out)
43 45 IOPort PWM 6 Dir (Out)
45 46 IOPort PWM 7 /Enable (Out)
47 47 IOPort PWM 6 /Enable (Out)

IO Connections for P3
Pin# I/O Pri. func Sec. func Chan Pin func Pin Dir

1 48 IOPort QCount 9 Quad-B (In)
3 49 IOPort QCount 9 Quad-A (In)
5 50 IOPort QCount 8 Quad-B (In)
7 51 IOPort QCount 8 Quad-A (In)
9 52 IOPort QCount 9 Quad-IDX (In)
11 53 IOPort QCount 8 Quad-IDX (In)
13 54 IOPort PWM 9 PWM (Out)
15 55 IOPort PWM 8 PWM (Out)
17 56 IOPort PWM 9 Dir (Out)
19 57 IOPort PWM 8 Dir (Out)
21 58 IOPort PWM 9 /Enable (Out)
23 59 IOPort PWM 8 /Enable (Out)
25 60 IOPort QCount 11 Quad-B (In)
27 61 IOPort QCount 11 Quad-A (In)
29 62 IOPort QCount 10 Quad-B (In)
31 63 IOPort QCount 10 Quad-A (In)
33 64 IOPort QCount 11 Quad-IDX (In)
35 65 IOPort QCount 10 Quad-IDX (In)
37 66 IOPort PWM 11 PWM (Out)
39 67 IOPort PWM 10 PWM (Out)
41 68 IOPort PWM 11 Dir (Out)
43 69 IOPort PWM 10 Dir (Out)
45 70 IOPort PWM 11 /Enable (Out)
47 71 IOPort PWM 10 /Enable (Out)

OK that looks OK (that is a SV12 configuration)

If you had a working 5I20 configuration, you should not need a
pncconf created configuration. It would be much better to copy
your existing 5i20 configuration and change the card name and
loadrt hm2_pci line with a loadrt hm2_eth line with the ip address added