RE: GPIO configuration issues AFTER moving to NCS 1.6.1

Hakon — Tue, 05 Oct 2021 16:45:13 GMT

Read my reply to this case. P1.00 and P1.01 is used by the network core for UART0, and that is probably the reason why it fails.

RE: GPIO configuration issues AFTER moving to NCS 1.6.1

sshenoy105 — Thu, 30 Sep 2021 01:49:56 GMT

I tried editing v1.6.1\zephyr\boards\arm\nrf5340dk_nrf5340\nrf5340_cpunet_reset.c (I use secure build).. i saw the code uses the pins 0 and 1 (of port 1) so i commented the usage.. I HAVE NO IDEA what's the side effect of this is (yet) but if i do this, i can get interrupts on my configured pin..
can you please consider helping me understand what might be going on given this is Nordic's code ?

Like I mentioned, this issue happens only if you use BLE.. if you have a simple application without BLE (and hence no netcore), life is good.. but who would need nrf5340 if that's the use case :-)

static void remoteproc_mgr_config(void)
{
/* UARTE */
/* Assign specific GPIOs that will be used to get UARTE from
* nRF5340 Network MCU.
*/
#if 0 ///---------------------- commented these lines
CPUNET_UARTE_PORT_TRX->PIN_CNF[CPUNET_UARTE_PIN_TX] =
GPIO_PIN_CNF_MCUSEL_NetworkMCU << GPIO_PIN_CNF_MCUSEL_Pos;
CPUNET_UARTE_PORT_TRX->PIN_CNF[CPUNET_UARTE_PIN_RX] =
GPIO_PIN_CNF_MCUSEL_NetworkMCU << GPIO_PIN_CNF_MCUSEL_Pos;
NRF_P0->PIN_CNF[CPUNET_UARTE_PIN_RTS] =
GPIO_PIN_CNF_MCUSEL_NetworkMCU << GPIO_PIN_CNF_MCUSEL_Pos;
NRF_P0->PIN_CNF[CPUNET_UARTE_PIN_CTS] =
GPIO_PIN_CNF_MCUSEL_NetworkMCU << GPIO_PIN_CNF_MCUSEL_Pos;
#endif
/* Route Bluetooth Controller Debug Pins */
DEBUG_SETUP();

/* Retain nRF5340 Network MCU in Secure domain (bus
* accesses by Network MCU will have Secure attribute set).
*/
NRF_SPU->EXTDOMAIN[0].PERM = 1 << 4;
}
#endif /* !CONFIG_TRUSTED_EXECUTION_NONSECURE */

RE: GPIO configuration issues AFTER moving to NCS 1.6.1

Hakon — Fri, 17 Sep 2021 13:35:19 GMT

Hello,

can I have the full code, or some other sample code that can be used to reproduce the same issue?