1. Running “shell” routine on our board，it works well. This indicates that the WiFi part is working properly.
2. When running the “mqtt_over_wifi_nrf7002dk_master “routine on our board, the following error message is output [00:00:00.396,820] wifi_nrf: qspi_init: QSPI freq = 24 MHz [00:00:00.396,850] wifi_nrf: qspi_init: QSPI latency = 1 [00:00:00.404,022] wifi_nrf: zep_shim_pr_info: wifi_nrf_fmac_fw_load: LMAC patches loaded [00:00:00.414,886] wifi_nrf: zep_shim_pr_info: wifi_nrf_fmac_fw_load: LMAC boot check passed [00:00:00.417,449] wifi_nrf: zep_shim_pr_info: wifi_nrf_fmac_fw_load: UMAC patches loaded [00:00:00.428,222] wifi_nrf: zep_shim_pr_info: wifi_nrf_fmac_fw_load: UMAC boot check passed [00:00:00.449,920] wifi_nrf: zep_shim_pr_info: RPU LPM type: HW [00:00:00.568,328] fs_nvs: nvs_mount: 2 Sectors of 4096 bytes [00:00:00.568,328] fs_nvs: nvs_mount: alloc wra: 0, fe8 [00:00:00.568,359] fs_nvs: nvs_mount: data wra: 0, 0 *** Booting Zephyr OS build v3.2.99-ncs2 *** [00:00:00.568,420] net_config: net_config_init_by_iface: Initializing network [00:00:00.568,450] net_config: check_interface: Waiting interface 1 (0x200014b0) to be up... [00:00:00.569,244] net_config: setup_ipv4: IPv4 address: 192.165.100.150 [00:00:00.569,274] net_config: setup_dhcpv4: Running dhcpv4 client... [00:00:00.570,587] wpa_supp: wpa_printf_impl: z_wpas_start: 385 Starting wpa_supplicant thread with debug level: 3 [00:00:00.570,800] wpa_supp: wpa_printf_impl: Successfully initialized wpa _supplicant [00:00:01.582,824] bt_hci_core: hci_vs_init: HW Platform: Nordic Semiconductor (0x0002) [00:00:01.582,855] bt_hci_core: hci_vs_init: HW Variant: nRF53x (0x0003) [00:00:01.582,885] bt_hci_core: hci_vs_init: Firmware: Standard Bluetooth controller (0x00) Version 216.11532 Build 3803067951 [00:00:01.584,808] bt_hci_core: bt_dev_show_info: Identity: E7:52:91:92:A6 :E5 (random) [00:00:01.584,838] bt_hci_core: bt_dev_show_info: HCI: version 5.3 (0x0c) revision 0x224b, manufacturer 0x0059 [00:00:01.584,869] bt_hci_core: bt_dev_show_info: LMP: version 5.3 (0x0c) subver 0x224b [00:00:01.584,869] MQTT_OVER_WIFI: main: Bluetooth initialized. [00:00:01.584,899] MQTT_OVER_WIFI: main: Wi-Fi provisioning service starts successfully. [00:00:01.586,883] MQTT_OVER_WIFI: main: BT Advertising successfully started. [00:00:44.001,251] MQTT_OVER_WIFI: connected: BT Connected: 55:F6:0C:31:F9:0C (random) [00:00:45.130,584] MQTT_OVER_WIFI: disconnected: BT Disconnected: 55:F6:0C:31:F9:0C (random) (reason 0x13). [00:00:45.130,767] MQTT_OVER_WIFI: update_adv_data_task: Cannot update advertisement data, err = -11 [00:00:55.056,488] MQTT_OVER_WIFI: connected: BT Connected: 55:F6:0C:31:F9:0C (random) [00:00:59.322,998] MQTT_OVER_WIFI: security_changed: BT Security changed: 55:F6:0C:31:F9:0C (random) level 2. [00:00:59.423,004] MQTT_OVER_WIFI: pairing_complete: BT pairing completed: 55:F6:0C:31:F9:0C (random), bonded: 0 [00:00:59.973,083] wifi_prov: control_point_ccc_cfg_changed: Wi-Fi Provisioning service - control point: indications enabled [00:01:00.222,869] wifi_prov: data_out_ccc_cfg_changed: Wi-Fi Provisioning service - data out: notifications enabled [00:01:00.623,046] wifi_prov: prov_request_handler: Start parsing... [00:01:00.623,107] wifi_prov: prov_get_status_handler: GET_STATUS received... [00:01:02.472,930] wifi_prov: prov_request_handler: Start parsing... [00:01:02.472,961] wifi_prov: prov_start_scan_handler: Start_Scan received... [00:01:02.490,905] wpa_supp: wpa_printf_impl: wlan0: CTRL-EVENT-DSCP-POLICY clear_all [00:01:12.372,985] wifi_prov: prov_request_handler: Start parsing... [00:01:12.373,016] wifi_prov: prov_stop_scan_handler: Stop_Scan received... [00:01:34.273,651] wifi_prov: prov_request_handler: Start parsing... [00:01:34.273,681] wifi_prov: prov_set_config_handler: Set_config received... [00:01:34.291,900] wpa_supp: wpa_printf_impl: wlan0: CTRL-EVENT-DSCP-POLICY clear_all [00:01:38.016,906] wpa_supp: wpa_printf_impl: wlan0: SME: Trying to authenticate with 70:af:6a:81:c5:4d (SSID='link_earth' freq=2412 MHz) [00:01:38.020,111] wifi_nrf: wifi_nrf_wpa_supp_authenticate: wifi_nrf_wpa_supp_authenticate:Authentication request sent successfully [00:01:38.277,038] wpa_supp: wpa_printf_impl: wlan0: Trying to associate with 70:af:6a:81:c5:4d (SSID='link_earth' freq=2412 MHz) [00:01:38.285,491] wifi_nrf: wifi_nrf_wpa_supp_associate: wifi_nrf_wpa_supp_associate: Association request sent successfully [00:01:38.298,583] wpa_supp: wpa_printf_impl: wlan0: Associated with 70:af:6a:81:c5:4d [00:01:38.298,736] wpa_supp: wpa_printf_impl: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 [00:01:38.421,478] wpa_supp: wpa_printf_impl: wlan0: WPA: Key negotiation completed with 70:af:6a:81:c5:4d [PTK=CCMP GTK=CCMP] [00:01:38.421,722] wpa_supp: wpa_printf_impl: wlan0: CTRL-EVENT-CONNECTED - Connection to 70:af:6a:81:c5:4d completed [id=0 id_str=] [00:01:38.426,727] MQTT_OVER_WIFI: wifi_connect_handler: Connected to a Wi-Fi Network [00:01:43.520,690] net_dhcpv4: dhcpv4_handle_msg_ack: Received: 192.168.0.3 [00:01:43.520,812] net_config: ipv4_addr_add_handler: IPv4 address: 192.168.0.3 [00:01:43.520,843] net_config: ipv4_addr_add_handler: Lease time: 172800 seconds [00:01:43.520,874] net_config: ipv4_addr_add_handler: Subnet: 255.255.255.0 [00:01:43.520,904] net_config: ipv4_addr_add_handler: Router: 192.168.0.1 [00:01:44.427,520] MQTT_OVER_WIFI: main: Connecting to MQTT Broker... [00:01:46.427,795] MQTT_OVER_WIFI: broker_init: getaddrinfo failed: -101 [00:01:46.427,825] MQTT_OVER_WIFI: client_init: Failed to initialize broker connection [00:01:46.427,825] MQTT_OVER_WIFI: connect_mqtt: Failed to initialize MQTT client: -10
3. When running the “mqtt_over_wifi_nrf7002dk_master “routine on DK board, Occasionally, the following error message output may occur
It seems that the operation is unstable. How to solve this problem? I guess the problem is that the coupling between the code and hardware is too tight. If so, can we improve the tolerance of the code by modifying it?
Thank you all for answering the questions
