TM4C123G GPIO driving problem

Hello JD

Most probably;y there is a bus fault that is happening in the code. I would suggest using TivaWare instead of DRM style access first of all as it makes the code readable for others on the forum.

DRM - always delightfully - scores AGAIN while insuring user delay, uncertainty, & frustration.   And - that frustration over-flows to vendor staff & humble outsiders - who seek to aid. (community service required under terms of parole...)

That said - as NO Delays reveal w/in users (unfortunate) DRM code scramble - "How would user, "EVEN NOTE" the (very brief) "Turn ON" of PF_1?"

We note that the "most unfortunate, "FORCED USE" of DRM sufficiently EXHAUSTS "compliant DRM users" - so much so - that they (usually) fall victim to (very) simple mistakes!  (i.e. as here!)

Vendor's API guides users, "around, above, safely past" such pitfalls - the case for, "DRM and DRM ONLY" sits atop (very) slim (and unstable/declining) OLD ground!

Nothing w/in API use "PREVENTS" the user from reviewing Register Selection & the various impacts of particular "Bit Settings!"     In fact the GUARANTEE of "user success" should insure, "User Learning!"

Perhaps the INSPIRED BLEND of "API" AND Register Selection & "Bit Drilling" produces a TRUER, FASTER, VASTLY MORE EFFICIENT LEARNING!   Pretending that the hugely advantaged API does NOT exist - or banning its inspection and/or use - proves HIGHLY QUESTIONABLE!