The following are the troubleshooting steps to follow for different scenarios mentioned below.

Troubleshoot Demo Run#

  • Error code: 0x10003 is displayed in logs indicating Wi-Fi initialization failure.

    • This is observed when SiWx917 SoC MBR upgrade is done but SiWx917 connectivity firmware is not updated. Update SiWx917 connectivity firmware to the latest. See the Update the SiWx917 connectivity firmware section.

  • SiWx917 SoC wakes up from sleep after few seconds of putting it in low-power mode.

  • Improper UART Prints

  • Error code: 0x10016 is displayed in logs indicating Wi-Fi connection failure.

  • Liquid crystal display (LCD) output appears distorted while powering on the SiWx917 SoC radio board

    • Reset the radio board a few times. This is a known issue

Troubleshoot a Board Detection Failure#

If Simplicity Studio does not detect your radio board, try the following:

  • In the Debug Adapters pane, Click the Refresh button (having an icon of two looping arrows).

  • Press the RESET button on the WPK board.

  • Power-cycle your device by disconnecting and reconnecting the USB cable.

Troubleshoot a Firmware Update Failure#

If the firmware update fails, try the following:

  • Toggle the power switch towards AEM (Advanced Energy Monitoring) on the WPK board

  • Try the following steps:

    • Press and hold the ISP button on the radio board.

    • Press and release the RESET button on the WPK board.

    • Release the ISP button on the radio board.

    • In the Flash section in step 5 above, click Erase chip.

    • The flash will be erased.

    • Press the RESET button on the WPK again.

    • Retry the firmware update.

  • In case studio failed to detect your board, see the Troubleshoot a Board Detection Failure section.

  • If the firmware update fails and Device is shown as Cortex M4 in step 5 in step 5 of the Update SiWx91x Connectivity Firmware section:

    • Select Help > About Simplicity Commander from the Simplicity Commander menu.

    • Verify that the version is 1v16p6b1592 or later. Note that the first digit represents the major version number, v is preceded by the minor version number, p by the patch number, and b by the build number. So for example, 1v16p6v1592 is the same as 1.16.6.1592.

    • If the version is earlier than that mentioned above, download and install the latest Simplicity Commander version.

    About Simplicity Commander

Troubleshoot an Application Build#

  • For Toolchain errors

    • Try upgrading GNU ARM toolchain version to v12.2.1 for GSDK versions v4.4.0 onnwards. See the GNU ARM v12.2.1 Toolchain section.

Troubleshoot an Application Flash Failure#

The application may fail to flash for one of the following reasons:

  • Error code 102 is displayed in the logs, indicating that ISP mode is enabled. Try the following steps:

    • Press and hold the ISP button on the radio board.

    • Press and release the RESET button on the WPK board.

    • Release the ISP button on the radio board.

    • Retry flashing the application.

  • "Could not connect debugger. Could not connect to target device" is displayed in the logs, indicating that the application processor is in a low power state with no flash access. Try the same steps as those described above for error 102.

  • Error code: 0x10016 is displayed in logs indicating Wi-Fi connection failure.

  • Unknown reason - try re-launching Simplicity Studio.

  • For additional tips, see the Troubleshoot Firmware Update Failure section. Follow the suggested steps and then, instead of retrying the connectivity firmware update, retry flashing the application.

Troubleshoot an Application Run Failure#

  • Liquid crystal display (LCD) output appears distorted while powering on the SiWx917 SoC radio board

    • Reset the radio board a few times. This is a known issue

Troubleshoot an Application Debug Failure#

The application may fail to enter the debug mode due to one of the following reasons:

  • Studio failed to halt execution at the main() function. Perform the following steps before trying again:

    • Click the Suspend button (having a pause button icon).

    • Click the Reset button (having an icon of a play button with an arrow underneath).

      Reset Debug

    • Retry debugging the application.

  • For additional tips, see the Troubleshoot an Application Flash Failure section. Follow the suggested steps and then, instead of retrying the flashing of the application, retry debugging the application.