RE: Image booted by custom child image cannot control GPIOs

Michal — Mon, 12 Dec 2022 03:47:36 GMT

Thank you for the information.

Best regards,

Michal

RE: Image booted by custom child image cannot control GPIOs

devincmurphy7 — Thu, 08 Dec 2022 19:34:38 GMT

I was finally able to dig into this some more. It turns out that I was incorrect in stating that my application image could not control GPIOs, truly my application image could not control 4 specific GPIOs where two of those happen to be on LEDs on my custom board. The issue was actually with UART1 being a secure peripheral used by TF-M and the default pinctrl settings using two of my LED GPIOs for RTS and CTS. My application cannot use those GPIOs because they have been assigned to a secure peripheral.... even though it seems like TF-M doesn't even use flow control since there is not a corresponding CONFIG_TFM_UART1_CTS_PIN or CONFIG_TFM_UART1_RTS_PIN...

Anyways, the solutions to my problem appear to include:

Custom overlay changes
- Add new pinctrl definitions for uart1 and uart1_sleep which do not define RTS and CTS pins or defines them as pins I am not using
- Add uart1 configuration which re-defines pinctrl-0 and pinctrl-1 with the definitions from above
Simply building with CONFIG_TFM_LOG_LEVEL_SILENCE=y in the prj.conf or config fragment seems to release all GPIOs that would otherwise be assigned to UART1

RE: Image booted by custom child image cannot control GPIOs

Michal — Thu, 01 Dec 2022 12:52:47 GMT

Hello,

Do you know what have you configured differently from the default sample?

Do you have any logs or anything?

Best regards,

Michal