NRF7002DK - NRF5340 SPI4M SPI_MISO tristate causing failure to boot (with spi_nor flash defined)

RE: NRF7002DK - NRF5340 SPI4M SPI_MISO tristate causing failure to boot (with spi_nor flash defined)

Simonr — Tue, 07 Apr 2026 08:14:21 GMT

Glad to hear you have found a resolution. Yes, this seems relevant, but please also be aware that the nRF7002 DK uses a lot of the GPIOs for other peripherals by default, so have that in mind while developing.

Best regards,

Simon

RE: NRF7002DK - NRF5340 SPI4M SPI_MISO tristate causing failure to boot (with spi_nor flash defined)

DKC — Wed, 01 Apr 2026 08:20:10 GMT

Thanks, Simon.

This issue seems not related to the confliction of multiple usage on the GPIO pins. I see the same issue when GPIO usage is just for SPIM only.

And I can simply resolve this issue by *internally pull-down* MISO pin by declaring it over .dts. See relevant discussion from nRF5340 QSPI flash , see comment from roshangeoroy.

I just wonder if this is the same root cause as discussed in the thread as I shared, and how do I apply necessary patches for the driver 'spi_nor.c', since I don't use QSPI for flash access, driver 'spi_nor.c' is the one I chose from zephyr instead of 'nrf_qspi_nor.c'. BTW, my current zephyr is from version 'ncs-v3.1.0' repo github.com/.../sdk-zephyr.

RE: NRF7002DK - NRF5340 SPI4M SPI_MISO tristate causing failure to boot (with spi_nor flash defined)

Simonr — Wed, 01 Apr 2026 07:40:59 GMT

The pins you have rerouted the SPI to are used on the DK for the UART interface communicating with the interface MCU, which will cause conflicts when using the DK board file since these are now being used for more than one thing. Please see the nRF7002 DK user guide here for more information on which pins are already used for something else on the DK: https://docs.nordicsemi.com/bundle/ug_nrf7002_dk/page/UG/nrf7002_DK/intro.html

Best regards,

Simon