nRF7002DK resets in the shutdown example

Dear All,

I am facing a rather strange issue with the nrf/samples/wifi/shutdown example.

I am working with nRF Connect SDK v3.1.1 and a nRF7002DK board.

I am observing the following:

When the application boots, the device performs a scan request, it shuts down, it enters the while (1) loop and immediately it boots up and performs another scan, followed by the shutdown. Then, the deivce is supposed to wait for 5s and perform another scan followed by a shutdown etc.

But what happens is that after the second scan (first run of the while loop), the device resets. The sample performs as expected only if the k_sleep is removed, meaning that the nRF7002 never actually gets to shutdown.

Could you please verify the described behavior? I am pretty sure this is a problematic situation.

My end goal is an application where I enable the WFi chip, connect do some data transfers and then shut it down in order to start over. I do not want the host to reset.

Thank you in advance.

  • Hi,

     

    Here is a log from when I tested the same:

    *** Booting nRF Connect SDK v3.1.1-e2a97fe2578a ***
    *** Using Zephyr OS v4.1.99-ff8f0c579eeb ***
    [00:00:00.565,551] <inf> shutdown: Starting nrf7002dk with CPU frequency: 64 MHz
    
    [00:00:00.568,847] <inf> shutdown: Scan requested
    
    Num  | SSID                             (len) | Chan | RSSI | Security | BSSID
    ...
    [00:00:05.369,232] <inf> shutdown: Scan request done
    
    [00:00:05.383,056] <inf> shutdown: Interface down
    [00:00:05.549,835] <inf> shutdown: Interface up
    [00:00:05.551,757] <inf> shutdown: Scan requested
    
    Num  | SSID                             (len) | Chan | RSSI | Security | BSSID
    ...
    [00:00:10.270,141] <inf> shutdown: Scan request done
    
    [00:00:10.283,966] <inf> shutdown: Interface down
    [00:00:15.450,439] <inf> shutdown: Interface up
    [00:00:15.452,362] <inf> shutdown: Scan requested
    
    Num  | SSID                             (len) | Chan | RSSI | Security | BSSID
    ...
    [00:00:20.212,799] <inf> shutdown: Scan request done
    
    [00:00:20.226,623] <inf> shutdown: Interface down
    [00:00:25.393,096] <inf> shutdown: Interface up
    [00:00:25.395,019] <inf> shutdown: Scan requested
    
    Num  | SSID                             (len) | Chan | RSSI | Security | BSSID
    ..
    [00:00:30.172,149] <inf> shutdown: Scan request done
    
    [00:00:30.185,974] <inf> shutdown: Interface down
    

     

    Can you please share a log of the issue that you are observing, and if any changes to the sample; post those as well?

     

    Kind regards,

    Håkon

  •  

    Thank you very much for you testing the sample.

    This is a log from my side:

    17:45:47.636 -> *** Booting nRF Connect SDK v3.1.1-e2a97fe2578a ***
    17:45:47.636 -> *** Using Zephyr OS v4.1.99-ff8f0c579eeb ***
    17:45:48.632 -> [00:00:00.567,413] <inf> shutdown: Starting nrf7002dk with CPU frequency: 64 MHz
    17:45:48.632 -> 
    17:45:48.632 -> [00:00:00.570,831] <inf> shutdown: Scan requested
    17:45:48.665 -> 
    17:45:52.249 -> Num  | SSID                             (len) | Chan | RSSI | Security | BSSID
    
    17:45:53.442 -> [00:00:05.376,129] <inf> shutdown: Scan request done
    17:45:53.442 -> 
    17:45:53.442 -> [00:00:05.389,984] <inf> shutdown: Interface down
    17:45:53.442 -> [00:00:05.556,854] <inf> shutdown: Interface up
    17:45:53.476 -> [00:00:05.558,898] <inf> shutdown: Scan requested
    17:45:53.476 -> 
    17:45:57.264 -> Num  | SSID                             (len) | Chan | RSSI | Security | BSSID
    
    17:45:58.425 -> [00:00:10.361,846] <inf> shutdown: Scan request done
    17:45:58.425 -> 
    17:45:58.425 -> [00:00:10.375,701] <inf> shutdown: Interface down
    17:46:03.066 -> *** Booting nRF Connect SDK v3.1.1-e2a97fe2578a ***
    17:46:03.066 -> *** Using Zephyr OS v4.1.99-ff8f0c579eeb ***
    17:46:04.059 -> [00:00:00.428,741] <inf> shutdown: Starting nrf7002dk with CPU frequency: 64 MHz
    17:46:04.093 -> 
    17:46:04.093 -> [00:00:00.432,159] <inf> shutdown: Scan requested
    17:46:04.093 -> 
    17:46:07.706 -> Num  | SSID                             (len) | Chan | RSSI | Security | BSSID
    
    17:46:08.901 -> [00:00:05.253,997] <inf> shutdown: Scan request done
    17:46:08.901 -> 
    17:46:08.901 -> [00:00:05.267,852] <inf> shutdown: Interface down
    17:46:08.901 -> [00:00:05.434,722] <inf> shutdown: Interface up
    17:46:08.901 -> [00:00:05.436,767] <inf> shutdown: Scan requested
    17:46:08.901 -> 
    17:46:12.713 -> Num  | SSID                             (len) | Chan | RSSI | Security | BSSID
    
    17:46:13.906 -> [00:00:10.261,718] <inf> shutdown: Scan request done
    17:46:13.906 -> 
    17:46:13.906 -> [00:00:10.275,573] <inf> shutdown: Interface down


    As you can see on my log the device resets after the second scan.

    Currently I have not made any changes to the shutdown sample.

    The only thing that I have done on my board is following the instructions for the dual PPK current measurement setup is to cut SB 16 and connect SB 17.

    Could you perhaps share with me the hex file you have produced so that I can put it on my device and see what happens?

  •  

    It seems that the issue was with the power supply I was using to feed the host device. I changed my power supply to the PPKII and now the sample works. So this ticket can be closed

Related