Setting up a Mesa 7i95T

Plan is for a closed loop system
Used the pncconf only havent changed anything yet

So far its working now the rest ill have to do by testing 
Thanks for the help again

Ok got the card running so far, controling a stepper motor is working.
After reading the card via mesaflash well missing a lot of pins
Only have like 57 and there compleatly wrong, was to be expected, it should have in total somewhere around 144 pins.

Unfortunatly i am unable to research what bitfile to load do to lack of documentation from mesa.
Ether im blind ore there is nothing in the docs.(see attachment)

Thanks for helping

Mesaflash shows physical pins, and which firmware modules are included
in the current installed firmware. What you need for hal file creation/editing
are hal pins and parameters.

To show all 7I95T hal pins and parameters:

1. Start LinuxCNC

2. In a terminal window type:

halcmd show all hm2

if you want a file containing these pins and parameters (for use as a copy/paste donor file):

halcmd show all hm2 > 7i95pins.txt

For documentation on the modules and their pins and parameters:

man hostmot2

OK got the file but it tells me a whole lot of nothing i understand.

From what i understand so far is that there are bin files that are pre configured for the board.
Like in the second Picture attached.
In the first picture are what seems to me are such files which are provided by mesa.
Which basicly does nothing for me because i cant look into them or research which does what.

Trying my best to understand and get a hang of things.
 

Unless you have an added parallel daughtercard, it's unlikely you need
to change the installed firmware.

Since you are using pncconf that does not directly support the 7I95/7I95T
the list of pin names is useful since in has the names of the isolated inputs
like:

hm2_7i95.0.inmux.00.input-00

and isolated outputs like:

hm2_7i95.0.ssr.00.out-00

are there.

If you do not want to add these by hand to a pncconf created configuration
you could use mesact instead of pncconf, since mesact supports the 7I95/7i95T
directly

Ok makes sense.
Could you explain to me why mesa flash is showing so little pins, because from what i can read i have the areas TB1-4 but i dont have the rest (TB5+6).
Do those usualy show or is that normal, may ii have made a mistake at some point?

Mesaflash shows only physical pins on the FPGA

The 7I95T uses multiplexing to reduce the number  of external connections,
so there are many more TB pins than FPGA pins. Also much of the I/O
is differential so have 2 TB pins per FPGA pin.

One example of this multiplexing is the isolated inputs. The 7I95T has
24 isolated inputs but these use only 6 FPGA pins to access.

Ah i see ok.
Pins of the FPGA Chip i asume.
So basicly this would be the name of one of the pins ( hm2_7i95.0.inmux.00.input-00  ....input-23)
is there something different to this pin (hm2_7i95.0.inmux.00.raw-input-00) ?


And those are basicly those that i can use as input or output
hm2_7i95.0.gpio.041.in
hm2_7i95.0.gpio.041.in_not (What does that mean)
hm2_7i95.0.gpio.041.out


Sorry for asking so many questions

The GPIO pins/ parameters are not really useful except on the
7I95T's parallel expansion connector (P1)

raw inmux or inm inputs are unfiltered ( not debounced )

man hostmot2 for inmux details ( search for inmux )