Hi,
We are using nRF5340 and we are migrating to v2.0.2 NCS sdk from v1.9.1.
In our design, the SPI MISO pin is P0.10. From the dev zone tickets, I found that this P0.10 pin is used by Network core's UART as well.
In v1.9.1, I manually changed the UART pins in /zephyr/boards/arm/nrf5340dk_nrf5340_cpunet.dts file I also had to do the same change in the /zephyr/boards/arm/nrf5340_cpunet_reset.c. This fixed the issue and we were able to use P0.10 for SPI.
But now when we migrated to v2.0.2, we are seeing the same issue.
I have modified the pin definitions in the nrf5340dk_nrf5340_cpuapp.overlay (this overlay is in our source folder) required for Pinctrl. I also did the change for UART pins in the /zephyr/boards/arm/nrf5340dk_nrf5340_cpunet-pinctrl.dtsi. I do not see a cpunet_reset.c file in v2.0.2.
Observations on debugging:
1. When MISO is configured as P0.10, SPI communication functions with the peripheral. I was able to see data output in MISO pin through the oscilloscope which means the SPI communication is functional. But the SPI driver's receiver buffer is empty. This was the reason why I think P0.10 pin is still used by network core.
2. Also, I tried out another pin, P0.4 using the nRF5340 devkit, everything works perfectly. I could see the SPI driver functioning. We were able to read data from the SPI peripheral as expected.
Below is the nrf5340dk_nrf5340_cpuapp.overlay added to our source folder,
Could you please let me know what I am missing here and how to fix this issue?
Regards,
Regie