nRF54L15 DK + nRF7002 EB2 official Wi-Fi shell example problems



Hardware
--------
- nRF54L15 DK
  - PCA10156
  - nRF54L15_xxAA_REV2
- nRF7002 EB2
  - pca63571 rev1

NCS version
-----------
- nRF Connect SDK v3.3.1
- Zephyr v4.3.99

Build
-----
Clean, unmodified NCS v3.3.1 tree.

Exact build command:


  --sysbuild -- \
  -DSHIELD=nrf7002eb2 \
  -DSNIPPET=nrf70-wifi

Generated DTS confirmation
--------------------------
The generated DTS matches the documented nRF54L15 DK + nRF7002 EB2 mapping:

- nRF7002 node: okay
- SPI controller: spi22 / spi@c8000
- SCK: P1.11
- MOSI: P1.06
- MISO: P1.07
- CS: P1.10
- BUCKEN: P1.04
- IOVDDEN: P1.05
- HOST_IRQ: P1.14

Generated config confirms:

- CONFIG_NRF70_SCAN_ONLY is not set
- CONFIG_NRF70_SYSTEM_MODE=y
- CONFIG_NRF70_STA_MODE=y
- CONFIG_WIFI_NRF70=y
- CONFIG_WIFI_NRF7002=y

Observed behaviour
------------------
With the official build flashed, the board is not reaching a usable Wi-Fi shell state reliably.

At the current stage, the board appears to reset or lose the console when the nRF7002 EB2 is fitted.

I do not yet have a clean current UART log from the latest state. An earlier run of the same clean official build reached the Wi-Fi shell but failed nRF7002 bring-up with:

- RPU wakeup write ACK failed even after 10 ms
- RDSR2 failed
- Wi-Fi shell commands present, but `wifi version`, `wifi status`, and `wifi scan` failed

Current question
----------------
Before I continue debugging, I want to confirm whether the setup/build is obviously wrong or whether there is a known nRF54L15 DK + nRF7002 EB2 requirement that is easy to miss.

Questions
---------
Is there anything obviously wrong with this setup?

Is there a known requirement for the nRF54L15 DK + nRF7002 EB2 combination that is easy to miss?

Based on the build command and generated DTS/config above, what would you check next?

Here is the AI questions and responses

1. VCOM1 disabled?

Yes. VCOM1 is disabled in the nRF54L15 DK Board Configurator. Only VCOM0 is connected.

2. Console on VCOM0 / UART30?

Yes. The generated DTS routes the console and shell to UART30 (VCOM0).

3. Pin assignments correct?

Yes. The generated DTS matches the documented nRF7002 EB II pin mapping:

  • BUCKEN = P1.04
  • IOVDDEN = P1.05
  • MOSI = P1.06
  • MISO = P1.07
  • CS = P1.10
  • SCK = P1.11
  • IRQ = P1.14

4. Firmware blobs installed?

Yes. The nRF70 firmware blobs are present and the build is configured to use them.

5. Build command correct?

Yes. The build targets nrf54l15dk/nrf54l15/cpuapp with the nrf7002eb2 shield and nrf70-wifi snippet.

6. shell_SHIELD vs SHIELD?

Not an issue. The unscoped SHIELD and SNIPPET options resolve correctly, as confirmed by the generated DTS and configuration.

7. SHEL:2372 applicable?

No evidence found. I cannot find this issue in the local NCS v3.3.1 documentation or source, so I have not considered it relevant.

Related