Troubleshooting Tips#

Use this section to diagnose and resolve common issues encountered while using Simplicity Commander Command Line Interface (CLI) with SiWG917 devices. This table includes general connection and flashing issues, along with specific command error codes and their resolutions.

Common Issues and Resolutions#


Error / Symptom	Likely Cause	Recommended Action
Device not detected	Missing drivers, incorrect cabling, or no power	Install or update SEGGER J-Link drivers, check all cable connections, power cycle the board, and specify the device with `-d <OPN>`.
Flash write failures	Incorrect flash type, wrong pin configuration, or misuse of `--skipload`	Verify flash type and configuration. Use `--pinset n` to define the correct pin group for external flash (see Pinset Mapping Table below). Avoid using `--skipload` immediately after power-on.
Flash erase or read fails	Device not powered or debugger disconnected	Check power, reconnect the J-Link debugger, and confirm target voltage.
Security mismatch	Firmware image security does not match MBR/eFuse	Ensure MBR/eFuse security fields match firmware signing or encryption settings.
Commander not recognized	Commander binary not in system `PATH`	Add the Commander installation directory to the system `PATH` or use the full file path.
Operation timeout	Unstable USB connection or JTAG inaccessible	Reconnect the device, use a direct USB port, or retry in ISP mode.
Incorrect or corrupted RPS image	Invalid or incomplete RPS file	Regenerate the RPS file and ensure compatibility with the device and Commander version.
Device reset has no effect	Command sent to inactive or wrong target	Specify the correct device using `-d <OPN>` and verify connectivity before running the reset command.
Permission denied (Linux/macOS)	User lacks access to USB/JTAG	Run the command with `sudo` or configure udev rules for user-level access.

Pinset Mapping Table#

Use the --pinset n option when working with external flash or when no in-package flash is available.
The pinset parameter specifies the General Purpose Input/Output (GPIO) range connected to the external flash.


Pinset No. (n)	GPIO Range	Description
`0`	GPIO 0–5	Default configuration for in-package flash or standard development boards
`2`	GPIO 46–51	Used when external flash is connected to alternate GPIO pins
`3`	GPIO 52–57	Used when external flash is connected to alternate GPIO pins

Note: Incorrect pinset configuration can cause flash detection or write failures. Always ensure the correct pin mapping based on your hardware design.

Commander CLI Error Codes and Resolutions#


Command / Function	Error Code	Description	Resolution
MBR	`0xA0AC`	Verification failed from flash	Occurs when incorrect inputs are used for `--pinset` or the MBR file is corrupted. Verify the MBR file and pin configuration.
Activation Code	`0xA0B0`	Activation code generation failed	If the device is locked for PUF (Physically Unclonable Function) usage, this error may appear. Re-enroll or unlock the PUF before retrying.
Intrinsic Keys	`0xA0B1`	Intrinsic key generation failed	Triggering this command before generating an activation code can cause failure. Run activation first, then retry intrinsic key generation.
Static Keys	`0xA0B2`	Static key storage failed	Occurs when intrinsic keys are missing. Generate intrinsic keys before attempting static key storage.
Update Firmware	`108`	Failed to load firmware	The RPS file header may be incorrect or corrupted. Recreate the RPS file and reload firmware.
Bootloader Timeout	`102`	Failed to load firmware	Device may be in Sleep mode or JTAG is not accessible. Keep the device in ISP mode and retry.
Start Radio	Cannot execute the radio command	Cannot execute the radio command	This error appears if the first command after power-on uses `--skipload`. Avoid using `--skipload` as the first command each time the device is powered on.

Reference:
For additional troubleshooting and commands reference, see Simplicity Commander General Information.