MesaCT 2.1.6 - Out of box 7i95T board not found

Newbie to LinuxCNC and MesaCT here. I just powered up the 7I95T for the first time ever and LED CR 16 FPGA/DONE is ON (Red), which means that there was a problem with configuring the FPGA. I have MesaCT 2.1.6 installed.  It looked for 10.10.10.10 and then 192.168.1.121 and both did not find the board. What do I do now? Is the board defective, it should have responded to 192.168.1.121 since it's the default. My subnet is 192.168.1.x. I can't flash new firmware because it can't communicate with the board.

I switched ports on the router to make sure my cat5 cable and router ports are good, and both of the connection are working.

I can ping 192.168.1.1, but host not reachable for 192.168.1.121.

Thanks so much for all the help

I would first make sure that your 5V supply is adequate
If the DONE LED remains illuminated after power on,
that is either an external  power supply issue or indicates
corrupted flash data.

If the flash is corrupted, you may be able to recover by
setting both IP address select jumpers to the "UP" position
and loading the fallback image. If this make no difference
is more likely a 5V power supply issue.


 

Then how does the PC get Internet connection. There is no wifi on the PC.

The real time Ethernet connection cannot be shared.

For general network access, the typical solution is to add a WIFI or Ethernet
USB dongle (or Ethernet card if you have PCI/PCIE slots)

@PCW, I'm using a regulated desktop ps for this test, so I bumped up the voltage to 5.2 v. It's drawing 536 ma, does that sound about right? So now the light goes off at 5.2v. I had it at 5v and it didn't work. The spec say 4.75v to 5.25V. I wonder if my dvm is not calibrated well.

BTW, still connected via a router to the PC. And now MesaCT finds the board.

Skinny wires or current limit too low?

You can access the card, run mesaflash etc on a standard shared network.
What you cannot do is run LinuxCNC without a dedicated Ethernet connection.

@PCW Yes, I understand now.

My DMM was reading too high, got the battery changed and now all good. The problem was I was setting the voltage using the DMM rather than the display of the regulated PS. After battery change, the reading of the DMM matches the reading on the display of the PS.

Thanks for all your help!

Okay, got me a USB Wifi dongle. Now I have a regular cat 5 ethernet cable directly connected from PC to Mesa. It's not a cross-over cable; not sure if I need to use a cross-over cable or not (the PC is kinda old).

My ip addr command shows...

cnc@FurniturePro:~/Downloads$ ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether d4:85:64:c0:ab:b1 brd ff:ff:ff:ff:ff:ff
3: wlx0014d1ea4e8e: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:14:d1:ea:4e:8e brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.127/24 brd 192.168.1.255 scope global dynamic noprefixroute wlx0014d1ea4e8e
       valid_lft 86269sec preferred_lft 86269sec
    inet6 2600:6c50:6700:a52:eab5:d186:da89:5f58/64 scope global dynamic noprefixroute
       valid_lft 542825sec preferred_lft 542825sec
    inet6 fe80::bfb3:191d:7c0d:d6ef/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

Now MesaCT cannot find the board.  What am I missing?