QSPI Interface Connection issue with NRF7002EB + NRF52840

RE: QSPI Interface Connection issue with NRF7002EB + NRF52840

Simonr — Wed, 06 Aug 2025 10:51:49 GMT

Indeed, the nRF7002 EK is supported by the nRF52840, so that should work. I'm sorry you're having a rough start to your project. If you're new to the nRF7002 series or the nRF Connect SDK as a whole we do have some courses to get started both for the nRF Connect SDK and Wi-Fi fundamentals available on the DevAcademy.

Best regards,

Simon

RE: QSPI Interface Connection issue with NRF7002EB + NRF52840

rsispal — Wed, 06 Aug 2025 10:25:56 GMT

Hey Simon, it’s interesting that there’s no indication or warning of this possible conflict. I’ll have to try disable those peripherals.

I’ve got an Nrf7002-EK so will give that a try, allegedly that should be supported right provided I disable the I2C1 and SPI1?

Funnily enough I’ve tried to get the WiFi scan example built for the thingy53 and I actually receive the same as this thread where the nrf7002 isn’t found. I’ll open a separate thread on that once I’ve tried some more things.

Not a pleasant developer experience I have to say, compared to others

RE: QSPI Interface Connection issue with NRF7002EB + NRF52840

Simonr — Wed, 06 Aug 2025 10:01:57 GMT

Hi Rav

Correct, it doesn't clearly state that it's unusable, but it's not supported, so we don't have anything in terms of support to offer here I'm afraid. It might (and probably will) work if you decide to use the nRF52840 and nRF7002 EB, but then you will be on your own.

I did a brief review of your overlay, and it seems like maybe the I2C1 and SPI1 are both used, which uses the same instances that will cause conflicts if used simultaneously. Nothing obviously wrong with the QSPI/Wi-Fi setup as far as I can tell. Sorry I can't be of more help.

Best regards,

Simon

RE: QSPI Interface Connection issue with NRF7002EB + NRF52840

rsispal — Wed, 30 Jul 2025 01:56:17 GMT

Hi Simon,

Thanks for the reply.

I see your point that the nRF7002 EB is marked deprecated, but that doesn’t and shouldn’t mean it’s non-functional — especially given that the nRF7002 itself is compatible with the nRF52 series, and the merit of Zephyr is the hardware abstraction. Why are the castellated pads an issue?

The documentation and product pages don’t clearly state that EB is unusable with the nRF52840 — just that it’s no longer officially supported — so I’d expect it to at least attempt to function when correctly wired even with past SDK’s (which it still doesn’t).

What’s wrong with the castellated pin connections on this board compared to the nrf7002EK (I’ve obtained one so will also try).

The Thingy:53 works fine with the EB and I’ve even tested the other 2 EB modules. I’ve verified power, SPI lines, and disabled any conflicting flash config I could find in the overlay. I’ve also shared a full code example here:

github.com/.../nrf7002eb-nrf52840-scan

Could you confirm if there’s anything obviously incorrect in the overlay, Kconfig, or logs I’ve provided that would prevent detection? If not, I’ll raise a return with DigiKey as the documentation around compatibility is vague, and I’m now hitting a dead end.

I don’t see a reason why this shouldn’t work and I’m keen to keep trying with targeted advice.

RE: QSPI Interface Connection issue with NRF7002EB + NRF52840

Simonr — Wed, 23 Jul 2025 07:25:52 GMT

Hi Rav

Sorry about the late reply, but we're short on staff during the summer vacation period in Nordic, so bear with us these couple of weeks before things get back to normal.

First off, can you confirm you're working on one of these boards:

Note that as per the Wi-Fi features are supported on the nRF52840: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/software_maturity.html#wi-fi_feature_support Here we can see that the nRF52840 only supports the nRF7002 EK HW. Additionally, as per the "Developing with nRF7002 EB" documentation page, the nRF7002 EB is deprecated for all boards except the Thingy:53.

Best regards,

Simon