I’m currently working on a project where I need to use pin 1.02 as a GPIO on the nRF54L15 with TF-M. I’ve encountered some challenges in finding the right configuration. Let me share my journey so far and what I’ve discovered.
First, I explored the Kconfig defines, but unfortunately, they seem to be deprecated or not applicable for my setup. This was a bit frustrating because I was hoping to find a straightforward configuration option. The resources I found either didn’t support non-secure targets or were intended for older SoCs like the nRF5340. It felt like I was going in circles with the information available.
After some trial and error, I discovered that modifying the NFCT PADCONFIG register worked for my use case. While this wasn’t my ideal solution, it got the job done. However, I’m still curious if there’s another method or configuration that I might have missed. Perhaps there’s a workaround or a different approach that could simplify the process without relying on register-level changes.
I’ve started looking into the latest SDK documentation and community discussions to see if anyone else has faced similar issues. It would be incredibly helpful to find a more elegant solution or to learn about any updates or patches that address this configuration challenge.
For now, I’ll continue using the NFCT PADCONFIG register method while keeping an eye out for any new developments or alternative approaches. If anyone has insights or suggestions, I’d greatly appreciate hearing them. Let’s keep the discussion going and explore this further together!