Wifi initialisation fails nrf7002-nrf5340

In our custom board we checked WIFI, facing below issues,

1. We flashed sta sample project to our custom board facing the issue below. Is there any configuration needed to address in the config file? Please provide debugging steps to resolve this issue?


2. Also tried provisioning samples in our custom board, no log response detected from the device. 
For both samples, 1.build configuration is set as nrf7002dk_nrf5340_cpuapp and 
                               2.include clock config CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y in the proj.conf file 
For sta we are able to get log but no log response for provisioning samples. How to resolve this issue?
And we can't build the samples with the nrf7002dk_nrf5340_cpuapp_ns configuration facing the issue .Why?

Parents Reply Children
  • Hi Dejan,

    It might be that your nrf7002 may not have been powered up correctly.

    Yes, Dejan. We also suspect this point. so we tested voltage at pin wise (QSPI, BUCK en and power points).

    As you mentioned that 2 points have no voltage. here I share the measured voltage at corresponding points. please check the table.

    we are looking for suggestions on how to properly power up the nrf7002 module. We are currently using a sample project with the pin configuration identical to the Development Kit (DK).

    1. Is there any specific pin configuration or additional settings that we might be missing to properly power up the nrf7002?
    2. Are there any specific sequences or initialization steps required in the firmware to ensure proper power-up of the nrf7002?
    3. Are there any external components or connections, such as capacitors or voltage regulators, that we need to double-check or verify?
    4. Could you suggest any diagnostic steps or tools we can use to further isolate the issue and confirm if it’s indeed a power-up problem?


  • Hi,

    You could look at the power state operation in the nrf7002 product specification which shows transitioning steps to Active state.

    Best regards,
    Dejan

  • Hi,

    I will check on that. However, these transitioning steps are performed on the Wi-Fi code before initialization, which takes place in the sample code itself and is also needed for the DK.

    So, how could it be different from our custom board?

  • Hi,

    Looking at your 4 questions asked previously, it seems that your problem might be hardware related. I suggest that you open a new private ticket where you would provide your schematic and PCB layout files and ask for a hardware review. After this is done and it is verified that the hardware is functional, you can return here with additional questions if you still have them.

    Best regards,
    Dejan  

  • After some changes in our custom board, we are now able to initialize WiFi, and it works fine. However, we are facing the following issues:

    1. WiFi Provisioning Not Working: The sample provisioning code is not working.Not even seeing the log. 

    2. MAC Address Not Programmed in OTP: In all our WiFi modules, we are encountering the "MAC addr not programmed in OTP" issue. For testing purposes, we use the CONFIG_WIFI_FIXED_MAC_ADDRESS="22:22:22:44:44:44" configuration. However, we need to use the actual MAC addresses of the modules for production.
    It is essential for all modules to have unique MAC addresses. How can we include the MAC address into the module?
    Do we want to create builds by config mac addr locally for all wifi modules individually?

    It would be helpful if the modules had the MAC addresses programmed into their OTP instead of using a fixed MAC address configuration.

    [00:00:00.068,908] <inf> wifi_nrf: nrf_wifi_fmac_otp_mac_addr_get: MAC addr not programmed in OTP
    [00:00:00.068,939] <err> wifi_nrf: nrf_wifi_get_mac_addr: Invalid MAC address: 00:00:00:00:00:00
    [00:00:00.068,969] <err> wifi_nrf: nrf_wifi_if_start_zep: Failed to get MAC address

    Please provide your suggestions on these issues.

Related