7i95 sserial port as gpio

I flashed 7i95t_5abodd.bin, it succeeded. Then I hit reload, and now the card can't be found. I rebooted the card and restarted MesaCT, still can't find the board. Jumpers still in the same location, NIC settings the same. No red leds.

What to do now?

What is the card address and what does the command

ip a

report?

You can boot the fallback configuration by setting both IP address jumpers UP
(the will also set the card IP address to 192.168.1.121)
 

10.10.10.10

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: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 88:ae:dd:0e:5a:e5 brd ff:ff:ff:ff:ff:ff
    altname enp2s0
    inet 10.10.10.100/24 brd 10.10.10.255 scope global noprefixroute eno1
       valid_lft forever preferred_lft forever
    inet6 fe80::aef9:50aa:d0b3:e84d/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
3: wlp0s20f3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether f8:9e:94:e0:d1:1b brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.101/24 brd 192.168.1.255 scope global dynamic noprefixroute wlp0s20f3
       valid_lft 86188sec preferred_lft 86188sec
    inet6 2600:6c50:6700:a52:6150:dce7:5b4a:82f0/64 scope global temporary dynamic
       valid_lft 570909sec preferred_lft 85782sec
    inet6 2600:6c50:6700:a52:fa9e:94ff:fee0:d11b/64 scope global dynamic mngtmpaddr noprefixroute
       valid_lft 570909sec preferred_lft 570909sec
    inet6 fe80::fa9e:94ff:fee0:d11b/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
 

I powered cycled the board again, and it connected for a few minutes. Then again, "board not found" message.  It's intermittent, so I checked the cabling, and sure enough the ethernet cable was loose.

But I can't select any Pwngen in the Firmware Tab, and the Spindle section is still grayed out.

I've tried two different cables. Ping to 10.10.10.10 would respond after power cycling, but it would stop after a few minutes. HMID read seems to confirm the stepgens and pwn on P1 connector.

Do I need to attach the 5abob card for this firmware to work? I've ordered a 7i75 Breakout/FPGA Protection Card, and it will come in a few days.

Probably the easiest way to add the PWM spindle control
is to hand edit the files, one way to do this is to create a
configuration for some more common hardware with a PWMgen
(say a 5I25 + G540) and copy/paste its spindle
hal and ini file sections into your 7I95 configuration.

The loss of communications is concerning. Is there any indication
of something going wrong on the 7I95T LEDs when this happens?

 

No red leds are lit. With the previous firmware 7i96t_d.bin, using the same cables, there were never any problems. And now, even if I recycle the board there is no response from the board.

I think I will try to reset to 192.169.1.121, and try the backup firmware. If that firmware is stable, then it's not the hardware board and the 7i95t_5abobd.bin firmware is the cause of it.

If the problem persists, then it could be the board.

Note that the backup firmware has no I/O other than GPIO, so if you want
to try going back to the default firmware, the way to do this is start the card
in backup mode, and then write the default firmware: 7i95t_d.bin, then restart
in normal mode
 

okay

I set jumpers w17 and w18 to the up up position, powered up the board and no red flashing lights. Connected the Ethernet port to my home wifi router via cable. I can ping the router at 192.168.1.1. The board should be at 192.168.1.121. But pinging 192.168.1.121 fails and MesaCT can't find the board. These were the same configuration I used when I powered up the board for the first time.

What do you think? Comms on the board is the problem?