Wifi initialisation fails nrf7002-nrf5340

[Lavanya_Manohar]

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?

[Lavanya_Manohar]

I have also tried scan sample but facing below issues.

[dejans]

Hi,

I have tried wi-fi station sample in NCS v2.6.0 and could not reproduce your issue on nrf7002dk even after adding CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y to the prj.conf file.

Which NCS version do you use?

Could you provide a full log of the station sample from the moment you restart the device after flashing?

Best regards,
Dejan

[Lavanya_Manohar]

Hi dario

1. If posible, Please chcek your board host + nrf7002ek. (isolate custom board nrf7002).
 
2. And check above(nrf7002dk schmatics) showing IC session in your board.(A1 and A2).

[dejans]

Hi Lavanya_Manohar ,

Did you make any progress regarding the reported issue?

Your problem does not seem to happen due to shared antenna.
Can you please confirm that scan and station samples in NCS v2.6.1 work on your custom board as expected?

Best regards,
Dejan

[Lavanya_Manohar]

dejans said:

Can you please confirm that scan and station samples in NCS v2.6.1 work on your custom board as expected?

These all working fine.

Lavanya_Manohar said:

During debugging, we found that the pointer does not exit from the z_sys_init_run_level(INIT_LEVEL_POST_KERNEL) function, which prevents it from entering our main application. Consequently, no debug logs appear in the terminal. Please see the attached image for more details.

Please check into this. 
Why the pointer not exit from z_sys_init_run? Are we missing any configuration? 
Is Ble provisioning using external flash for storing WiFi credentials? 

Furthermore debugging, it stuck into spi_nor_wait_untill_ready function. Please see the attached image for more details.


Hence we check the zephyr/spi_flash sample (nrf5340DK configuration). Got below output
*** Booting nRF Connect SDK v3.5.99-ncs1-1 ***
mx25r6435f@0: device not ready.

While build with nrf7002dk-nrf5340dk facing issue


Are we missing SPI/Flash related configuration?Please provide your suggestion on this. 

FYI, In our board we don't have external flash.

[dejans]

Hi,

Lavanya_Manohar said:

Furthermore debugging, it stuck into spi_nor_wait_untill_ready function. Please see the attached image for more details.

Lavanya_Manohar said:

Hence we check the zephyr/spi_flash sample (nrf5340DK configuration). Got below output
*** Booting nRF Connect SDK v3.5.99-ncs1-1 ***
mx25r6435f@0: device not ready.

mx25r6435f is external flash but since you do not have external flash your device never gets ready, and you get devicetree errors.

Regarding your issue with provisioning, can you verify that you used correct COM port/ttyACM device? In addition, can you provide build command which you used? Please note that according to requirements, on the nrf7002-dk sample should be built for nrf7002_nrf5340_cpuapp (no _ns) build target.

Best regards,
Dejan

[Lavanya_Manohar]

dejans said:

mx25r6435f is external flash but since you do not have external flash your device never gets ready, and you get devicetree errors.

Ok Thank you. 

In this sample, before main application, it initialise all the kernal config in  z_sys_init_run function, It is working in DK board because all configuration satisfy but In our custom board we don't have SPI - external flash(mx25r6435f) connection, so it is stuck in configuring SPI. Hence we Disable mx25r6435f device. After that ble provisioning is working fine in our custom board.