Tiva C PinMux Utility 1.0.4 TM4C1294NCPDT Missing GPIO Pins?

Mon ami - are you sure that those you list are indeed, "GPIO?"  (truth in advertising - our group has no interest in this specific MCU - have neither time/interest to "wade thru" errata laden manual)

Should those pins be, "other than gpio" - might they be located with or by their "other" function?  Again - we don't use pinmux - know not the import of, "far left column."  Holiday's near presence may delay factory - thus this swag in your behalf...  (bit more heavy in swag's "wa" than those past...)

Pins are actually called (Port IO) in the column header. Assumed most pins start out that why (Px0-Px7) whether analog, digital or special function AFSEL peripheral pins.  Actually the PinMux utility made if far easier to migrate SW onto the EX-TM4C1492xl  than it would have been without it. Finally down to 35 errors starting from 542 this morning.

 "other" function? Tend to believe any GPIO port not being used by other peripherals should show up in he port IO column but luck has it they don't. Appears like the chip template is muffed up.

BP101 said:

PinMux utility made if far easier to migrate SW onto the EX-TM4C1492xl  than..without it.

Should state that your admitted, "542 errors" seems (somehow) not to qualify as, "far easier!"

Now we migrated from M3 to M4 nearly 3 years past - there was no pin mux for LX4F (@ that time) and iirc we had fewer than 20 errors, certainly no more than 25.  Note we had extensively read MCU manuals of both original M3 and new M4 - knew precisely what we were after...

Note that the pin mux cannot know our mandated board layout - nor targeted, total functional harvest, from a 64 pin MCU.  Thus tried, true import of each pin from MCU's column based, data manual directly into Excel.  And then we tried different combinations of PWM, ADC, Ana Comp, GPIO for Halls & command inputs, serial I/O via UART, SPI & I2C. 

Each functional area was color coded w/in Excel - and gradually, systematically we developed the means to extract all of our needed peripheral functions.  This was aided greatly - and speeded - via Excel's color coding. 

Once the pin mux made its appearance for LX4F we had a team engineer try it - she reported some value but it could not harvest & configure all the peripherals to our desire w/out key intervention.  And we'd never consider it to be, "far easier" to migrate nor as effective & powerful as our use of Excel...

I'd conclude that pin mux may be most useful for new user to discern correct pin coding & usage - again emphasis upon, "new user."  But - to extract the best match of MCU's peripheral capability to user's design objective - a solid review of MCU manual - followed by direct copy/paste of MCU's columnar data into Excel - proved optimal.  Excel is extremely powerful - there exist indirect means by which Excel may, "problem solve" and perform automated, "what if" scenarios - both overpowering any known pin mux...

PinMux utility is helpful with launch pad expansion using the Booster Pack connectors or when using the X11 edge connector especially when several of the GPIO ports are being used. Albeit one has to verify every GPIO pin assignment with the schematic prior to selecting or enabling other GPIO port peripherals and associated pins.

PinMux utility can export pin assignments into an CSV spread sheet worthy of the posted method above. However will agree the more automated things are made more is the need for inspecting all aspects of any such utility.