Novakon Mill Conversion - Getting Started

The available input pins on the C11 bob are:

DB25  GPIO
10       13
11       14
12       15
13       16
15       03
 

I went to "show hal config" under machine in LCNC but there are no pins listed for anything (see below). Based on what I found on the LCNC website for HAL basics, I expect to see pin assignments listed like the online examples, but that is not the case. What am I missing or misunderstanding? How can I see the pin configuration in LCNC?
 

GPIO input hal pins  would be named:

DB25  GPIO         HAL NAME (True)             HAL NAME (inverted) 
10       13  hm2_5i25.0.gpio.013.in or hm2_5i25.0.gpio.013.in_not
11       14  hm2_5i25.0.gpio.014.in or hm2_5i25.0.gpio.014.in_not
12       15  hm2_5i25.0.gpio.015.in or hm2_5i25.0.gpio.015.in_not
13       16  hm2_5i25.0.gpio.016.in or hm2_5i25.0.gpio.016.in_not
15       03  hm2_5i25.0.gpio.003.in or hm2_5i25.0.gpio.003.in_not

So I was able to read the hal show under hm2_5i25 saw my pin assignments for 13 (Z home) and 15 (probe) but beyond that it looks like there is no assignment to pin 14 which should have been assigned by the c11gx2 firmware, right?

I guess I still don't understand how to read the hal file to confirm motor set-up (the step-gens), E stop and X & Y home (QCounts?)

Pin 14 is a PWMgen for compatiblity with the C11G breakout
(it would be PWMgen 0 in the hal file)

The stepgens are addressed as stepgen 0,1,2 etc in hal
These go to appropriate C11G pins (look at the pinout file
or the results of a readhmid command)
For example, Stepgen 0 is connected to DB25 pins 2 and 3 (step and dir respectively)

The optional qcount can be ignored, just use the GPIO inputs

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

 1      0   IOPort       None
14      1   IOPort       PWMGen           0        PWM             (Out)
 2      2   IOPort       StepGen          0        Step            (Out)
15      3   IOPort       None
 3      4   IOPort       StepGen          0        Dir             (Out)
16      5   IOPort       None
 4      6   IOPort       StepGen          1        Step            (Out)
17      7   IOPort       StepGen          4        Step            (Out)
 5      8   IOPort       StepGen          1        Dir             (Out)
 6      9   IOPort       StepGen          2        Step            (Out)
 7     10   IOPort       StepGen          2        Dir             (Out)
 8     11   IOPort       StepGen          3        Step            (Out)
 9     12   IOPort       StepGen          3        Dir             (Out)
10     13   IOPort       QCount           0        Quad-A          (In)
11     14   IOPort       QCount           0        Quad-B          (In)
12     15   IOPort       QCount           0        Quad-IDX        (In)
13     16   IOPort       None

I should add that if you are creating a hal/ini file set from scratch with pncconf
you should use pncconfs discover option and set:

encoders=0
stepgens=4
pwmgens=0

and then all the required GPIO will be available to setup in pncconf

I am going to first start this off with a huge thank you for the consistent feedback and answers. And secondly an apology for so many basic and somewhat repetitive questions.

I understand the motor setups and stepgens and can follow those in the hal file (mostly). But I am still a bit confused on things.

My C11G board is currently wired to my Novakon and is fully functional with MACH3. My goal is to plug into the C11G board as is already wired to the mill; so when I read the pin assignments from the C11gx2 pin file and the hal file, I have concerns on the functionality of the Axis homes and E Stop. My X, Y homes and E Stop are are physically wired to the pins that are listed as optional QCount in the pin file and when in PNC config I don't have enough GPIO options to assign these otherwise. What I am trying to understand is how to account for X home, Y home and my E stop when they are wired into the board already to pins I can't assign but are also not the correct function....

Do I need to create a hal/ini file from scratch ?