-
Notifications
You must be signed in to change notification settings - Fork 0
Reference Security
commander.security — SecurityCommand. Secure Engine commands. All methods return a dict. See Command-Reference for shared conventions.
Many of these operations change device lifecycle/security state, some permanently (OTP writes, disabling device erase). Several accept
prompt— setprompt=Falseto emit--nopromptand skip the interactive confirmation, and most acceptdryrun=True(--dryrun) to preview without applying. Most acceptreset=True(reset=False→--noreset).For task-oriented wrappers, prefer Target-Class (
getSecurityStatus,lockDebugAccess,unlockDebugAccess,write*Key, region config, SE firmware, …).
Run Secure Engine attestation.
Close a code region by index. Series 3 only. codeversion sets the code version.
Disable the device-erase capability.
disabletamper(reset=True, store=True, cert=None, cert_privkey=None, command_key=None, cert_signature=None, command_signature=None, authorization=None, cert_pubkey=None, disable_param=None, **kwargs)
Disable tamper detection, supplying the relevant certificate/signature/authorization material. store=False → --nostore.
Erase the device via the Secure Engine.
Upgrade the Secure Engine firmware from filename, optionally at address.
Check whether an SE firmware upgrade is available.
Generate authorization data (to outfile and/or stored on device).
gencert(outfile=None, store=True, deviceserialno=None, reset=True, cert_pubkey=None, authorization=None, command_key=None, extsign=False, **kwargs)
Generate a Secure Engine certificate. extsign=True outputs an unsigned form for external signing.
gencommand(outfile=None, store=True, reset=True, action=None, disable_param=None, unlock_param=None, **kwargs)
Generate a Secure Engine command (e.g. disable/unlock actions).
Generate a Secure Engine configuration.
Generate a Secure Engine key. type selects the algorithm; outfile/privkey/pubkey choose outputs.
Get the Secure Engine / certificate path.
Lock the Secure Engine / device. trustzone supplies a TrustZone configuration.
Lock the Secure Engine configuration. secure_debug_unlock enables/disables secure debug unlock.
Read the OTP rollback count.
Provision the Secure Engine. sefw is the SE firmware file.
Read a Secure Engine certificate of cert_type (optionally to outfile).
Read the Secure Engine configuration.
Read a Secure Engine key. Choose sign and/or command.
Read the code-region configuration. Series 3 only.
Roll the challenge value (store=False → --nostore).
Read the Secure Engine status. trustzone=True includes TrustZone info; verbose=True adds detail.
Transition the device to development (unlock for debug).
unlock(reset=True, store=True, cert=None, cert_privkey=None, command_key=None, cert_signature=None, command_signature=None, authorization=None, cert_pubkey=None, unlock_param=None, **kwargs)
Unlock the Secure Engine, supplying certificate/signature/authorization material.
Write a Secure Engine configuration to the device.
writekey(sign_keyfile=None, command_keyfile=None, decrypt_keyfile=None, reset=True, store=True, prompt=True, dryrun=False, **kwargs)
Write Secure Engine key(s) to the device — sign (--sign), command (--command), and/or decrypt (--decrypt).
Write a code-region configuration from file. Series 3 only.
PyCommander · GitHub · Simplicity Commander docs · Licensed under the Silicon Labs MSLA
Getting started
Using PyCommander
Topics
Command reference
- Overview
- adapter · aem · vcom · ctune
- device · flash · verify · readmem · extflash
- security
- tokens · nvm3 · littlefs
- convert · ebl · gbl3 · gbl4 · ota · rps · postbuild
- util · serial · mfg917
Contributing