We are seeing different behavior/performance on our system depending on whether we reset the system using JTAG (JLinkRTT Viewer) or we power cycle the system.
Our project is based on the AWS IoT Sample.
When the system is brought up through a Power On Reset, it works as expected.
However, when the system goes through a reset via the Reset pin on the 5340 (JTAG Reset), we get the following errors in the J-Link RTT viewer:
00> [00:00:00.801,300] <err> wifi_nrf: RDSR failed: -16
00> [00:00:00.801,330] <err> wifi_nrf: zep_shim_bus_qspi_dev_add: QSPI device init failed
00>
00> [00:00:00.801,391] <err> wifi_nrf: nrf_wifi_bus_qspi_dev_add: nrf_wifi_osal_bus_qspi_dev_add failed
00>
00> [00:00:00.801,452] <err> wifi_nrf: nrf_wifi_bal_dev_add: Bus dev_add failed
00>
00> [00:00:00.801,544] <err> wifi_nrf: nrf_wifi_hal_dev_add: nrf_wifi_bal_dev_add failed
00>
00> [00:00:00.801,666] <err> wifi_nrf: nrf_wifi_fmac_dev_add: nrf_wifi_hal_dev_add failed
00>
00> [00:00:00.801,696] <err> wifi_nrf: nrf_wifi_fmac_dev_add_zep: nrf_wifi_fmac_dev_add failed
00>
00> [00:00:00.801,696] <err> wifi_nrf: nrf_wifi_if_init_zep: nrf_wifi_fmac_dev_add_zep failed
00>
Our system utilizes a Fanstel WT02V40V module (nRF5340/nRF7002 combination).
To avoid interference with the QSPI interface, the design does not have anything connected to the 5340 pins utilized by the 7002.
