Sample WiFi scan, 7002DK to custom hardware

RE: Sample WiFi scan, 7002DK to custom hardware

ValentinKunti — Mon, 06 Oct 2025 12:53:03 GMT

Hi thank you for your response, I've actually managed to make a scan with my custom board, I did change the SDK to include the supply / Vbat power on, and now the device is enabling and initialising correctly !

The change is on 2 files of the SDK wifi, on the C:\ncs\v3.1.1\zephyr\dts\bindings\wifi\nordic,nrf70.yaml file, I add the supply-gpios option to activate or not an external regulator for the supply as we have on our hardware adding this :

supply-gpios:
  type: phandle-array
  description: |
    Optional GPIO of the SoC controlling an external power supply
    (e.g., 3.3V regulator) that must be enabled before BUCKEN.
    This is for custom boards with an additional power stage.
    If specified, this GPIO will be enabled first, before bucken-gpios.

Then I added the supply in the power sequence here "C:\ncs\v3.1.1\zephyr\modules\nrf_wifi\bus\rpu_hw_if.c", with the following addition :

//GPIO Specification (lines 38-41)
#if DT_NODE_HAS_PROP(NRF7002_NODE, supply_gpios)
static const struct gpio_dt_spec supply_spec =
    GPIO_DT_SPEC_GET(NRF7002_NODE, supply_gpios);
#endif


/* GPIO Configuration (lines 177-232)
- Added supply GPIO configuration in `rpu_gpio_config()`
- Ensures supply GPIO is configured first
- Proper error handling with cleanup*/

// Power-On Sequencing (lines 254-307)
static int rpu_pwron(void)
{
    // Step 1: Enable external supply (if configured)
    #if DT_NODE_HAS_PROP(NRF7002_NODE, supply_gpios)
        gpio_pin_set_dt(&supply_spec, 1);
        k_msleep(10);  // Wait for VBAT stabilization
    #endif

    // Step 2: Enable BUCKEN
    gpio_pin_set_dt(&bucken_spec, 1);
    k_msleep(1);

    // Step 3: Enable IOVDD_CTRL
    gpio_pin_set_dt(&iovdd_ctrl_spec, 1);
    k_msleep(iovdd_power_up_delay_ms);
}

// Power-Off Sequencing (lines 309-334)
- Reverse order: IOVDD → BUCKEN → SUPPLY

/* GPIO Cleanup (lines 234-260)
- Added supply GPIO disconnection in `rpu_gpio_remove() */

With this modification we enable first our 3V3 regulator before enabling the other power GPIO and the initialisation is fine.

best regards, and thank you for your help on this issue !

RE: Sample WiFi scan, 7002DK to custom hardware

Elfving — Mon, 06 Oct 2025 11:55:18 GMT

Another thing is that if you are uncertain about the connections you could test this with the "bustest", which you can find in zephyr/tests/boards/nrf/nrf70/bustest.

What NCS version are you using btw?

Regards,

Elfving

RE: Sample WiFi scan, 7002DK to custom hardware

ValentinKunti — Fri, 03 Oct 2025 07:38:45 GMT

I've know adding the power supply management in my main.c code, to enable the power supply know I get the OTP error but one other problem is that I get a lot of error cause the nRF7002 init is starting before my power supply start (even if it's the first thing I do in my main.c). So the driver does not handle the GPIO of the nRF7002 even if we had those in the .DTS board file ? Is there a way to start the WiFI init later ?

[09:27:06.939] uart:~$ [09:27:08.126] [00:00:00.437,164] wifi_nrf_bus: SPIM spi@a000: freq = 8 MHz
[09:27:08.126] uart:~$ [00:00:00.437,164] wifi_nrf_bus: SPIM spi@a000: latency = 0
[09:27:08.126] uart:~$ [00:00:00.448,852] wifi_nrf_bus: RPU wakeup write ACK failed even after 10ms
[09:27:08.126] uart:~$ [00:00:00.448,852] wifi_nrf_bus: Error: RDSR2 failed
[09:27:08.126] uart:~$ [00:00:00.448,883] wifi_nrf: zep_shim_bus_qspi_dev_add: RPU enable failed with error -1
[09:27:08.126] uart:~$ [00:00:00.448,974] wifi_nrf: nrf_wifi_bus_qspi_dev_add: nrf_wifi_osal_bus_qspi_dev_add failed
[09:27:08.126] uart:~$ [00:00:00.449,035] wifi_nrf: nrf_wifi_bal_dev_add: Bus dev_add failed
[09:27:08.126] uart:~$ [00:00:00.449,127] wifi_nrf: nrf_wifi_sys_hal_dev_add: nrf_wifi_bal_dev_add failed
[09:27:08.126] uart:~$ [00:00:00.449,249] wifi_nrf: nrf_wifi_sys_fmac_dev_add: nrf_wifi_sys_hal_dev_add failed
[09:27:08.126] uart:~$ uart:~$ [00:00:00.449,279] wifi_nrf: nrf_wifi_fmac_dev_add_zep: nrf_wifi_fmac_dev_add failed
[09:27:08.126] uart:~$ [00:00:00.449,310] wifi_nrf: nrf_wifi_if_start_zep: nrf_wifi_fmac_dev_add_zep failed
[09:27:08.126] uart:~$ [00:00:00.449,401] scan: === Starting WiFi Power Sequencing ===
[09:27:08.126] uart:~$ [00:00:00.449,432] scan: Step 1: 3V3_ENABLE (P1.12) ON - VBAT supplied
[09:27:08.126] uart:~$ [00:00:00.459,533] scan: Step 2: BUCKEN (P0.12) ON - Buck converter enabled
[09:27:08.126] uart:~$ [00:00:00.461,639] scan: Step 3: WIFI_IO_ENABLE (P1.00) ON via HAL - IOVDD supplied
[09:27:08.126] uart:~$ [00:00:00.466,735] scan: === WiFi Power Sequencing Complete ===
[09:27:08.126] uart:~$ [00:00:01.517,333] wifi_nrf: nrf_wifi_if_stop_zep: rpu_ctx_zep is NULL
[09:27:08.126] uart:~$ [00:00:01.519,989] wifi_nrf_bus: SPIM spi@a000: freq = 8 MHz
[09:27:08.126] uart:~$ [00:00:01.519,989] wifi_nrf_bus: SPIM spi@a000: latency = 0
[09:27:08.126] uart:~$ [00:00:01.722,137] scan: OTP not programmed, proceeding with local MAC: F6:CE:36:00:00:01
[09:27:08.126] uart:~$ uart:~$

Is this only the OTP error or I need to solve the previous issue I think there is some error from the QSPI but I use SPI4 in my board files ?

Cause I've seen this forum question and asking without programming the OTP : samples/wifi/scan broken without programmed OTP.

Best regards, and thank you in advance for your response.

RE: Sample WiFi scan, 7002DK to custom hardware

ValentinKunti — Thu, 02 Oct 2025 09:40:42 GMT

Thank you for the response, I already try the example wifi scan with the DK and it works directly, then I created my custom board files to build with our current GPIO without changing the main.c files, the connection is similar as in the hardware spec. with different GPIOs

The main.c does not have the control of the GPIO so I assume there is a driver that does the handling of the power supply IO VDD bucken pin in the WiFi driver and you send the different GPIO via the device three to be handled by this driver. But maybe if not using the DK, we need to modify the main.c to activate the power supply with the good sequence ?

Nice to know for the OTP ! We have a Raytac module which already have a mac address programmed inside.

For now the big issue is the understanding of how all the GPIOs and device three are handled for the power supply.

RE: Sample WiFi scan, 7002DK to custom hardware

Elfving — Thu, 02 Oct 2025 09:21:13 GMT

Hi,

[quote user=""]I'm currently trying to make a scan with our custom board, I've made a custom board with our GPIO and the use of the SPI4 instead of QSPI for the 7002 -> 5340 communication, we also use the CDC ACM USB to use direct USB connection for debug and terminal print / command.
[/quote]

First of all, I would recommend using a DK first, but you are of course free to do what you want.

[quote user=""]In the scan project we have the main.c, in this main there is no indication of how the device is powered up (supply / IOVDD / BUCK EN), if I'm understanding correctly we are setting those up in the device three with the overlay / board configuration file :
[/quote]

Have a look here for how it needs to be connected, and here for the supply sequencing. You do not do this through dts.

[quote user=""]For now I can build and program my board but I see that the power supply, io vdd and bucken is not enable, do we need to enable this on our side ? Or the device three with device 7002 on SPI4 with the given pin make this automatic, like in the pictures bellow :
[/quote]

So there could be something wrong with both the dts files of the board and the code here. Are you using a default sample? Are you seeing the same thing with DK dts files?

Note that when everything is set up, you also need to write to the OTP of the device for it to work. This is also something that is done already on the DKs.

Regards,

Elfving