NWP Debugging Wi-Fi#

This section provides information about the prerequisites for debugging NWP issues.

  • NWP issues can be analyzed/debugged using the following methods:

    1. Checking NWP responsiveness through debug logs.

    2. Collecting and sharing RAM dumps with Silabs for detailed analysis.

    3. Collecting and sharing sniffer logs with silabs for detailed analysis.

Checking NWP Responsiveness Through Debug Logs#

  • Trigger any query command from the application. For example:

    • Firmware Version: Use the sl_si91x_get_firmware_version command to get the firmware version.

    • Network Parameters: If the device is connected to a network, use the network_params command.

    Firmware version details and wireless infoFirmware version details and wireless info

  • Trigger a Ping test between the device and AP.

    Ping resultsPing results

Collecting and Sharing RAM Dumps with Silabs for Detailed Analysis#

  • RAM dumps are used to debug NWP-related issues. We can collect a RAM dump as explained in the link below:

https://docs.silabs.com/wiseconnect/3.4.1/wiseconnect-developers-guide-troubleshoot-application-debugging/#procedure-for-capturing-nwp-ram-dump

Collecting and Sharing Sniffer Logs with Silabs for Detailed Analysis#

In the following scenarios, debugging may require wireless sniffer logs (e.g., Wireshark):

  1. If the NWP is in a responsive state and the issue is protocol-related (DHCP, DNS, MQTT, HTTP, etc.).

  2. Wi-Fi connection failure.

  3. TLS handshake failure.

  4. Certificate-based authentication issues (e.g., EAP TLS, TTLS, PEAP, etc.,).

    • Collect certificates used for authentication.

    • If possible, obtain radius server logs.

  5. Network application connection failure.

  6. Data stall.

  7. Interoperability issues (e.g., the SiWx91x module fails to connect to a specific Access Point (AP) while successfully
    connecting to other APs).

  8. For TWT and power save related issues.

Example

EAPOL 4-Way Handshake Sniffer Capture Wireless sniffer for EAPOLWireless sniffer for EAPOL

EAP Authentication Sniffer Capture Wireless sniffer for EAPWireless sniffer for EAP

Note

  • For network application protocol issues, it is essential to capture all EAPOL (Extensible Authentication Protocol over LAN) Wi-Fi frames exchanged during the Wi-Fi authentication process in the sniffer log. Additionally, any decryption keys must be provided to facilitate the analysis.

  • For any EAP-related issues, capturing EAP packets is mandatory in the sniffer log.