| Name | pysequansutils JSON |
| Version |
2.3.3.21
JSON |
| download |
| home_page | |
| Summary | Collection of tools for cloud provisioning of Microchip IoT kits |
| upload_time | 2023-12-13 06:16:06 |
| maintainer | |
| docs_url | None |
| author | |
| requires_python | >=3.8 |
| license | MIT |
| keywords |
microchip
cellular
modem
avr-iot
sequans
|
| VCS |
 |
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
# pysequansutils
pysequansutils provides tools for the Sequans Monarch 2 platform which is used on Microchip cellular IoT development boards.
## Usage
pysequansutils can be used as a command-line interface or a library
pysequansutils comes bundled with a dup file for a full upgrade of the Sequans Monarch 2 platform. This dup file can be found in the fw folder of the package.
## Command-line interface
pysequansutils is a multi-layered command-line interface meaning that there are several commands each
with its own actions and options.
Getting help:
```bash
pysequans --help
```
Getting help for specific command (in this example the `upgrade` command):
```bash
pysequans upgrade --help
```
The amount of logging is controlled by the -v/--verbose option:
```bash
pysequans -v info
```
Possible log levels are `debug`, `info`, `warning`, `error`, `critical`. Default is `info`.
Print version info and exit:
```bash
pysequans -V
```
Print release info and exit:
```bash
pysequans -R
```
### Commands for upgrading the firmware of a Sequans Monarch2 platform
Do a full upgrade of Sequans Monarch 2 platform using the bundled firmware. This will only upgrade the firmware if the bundled firmware is newer than the current firmware of the Monarch2 platform.
```bash
pysequans upgrade full
```
Do a forced full upgrade/downgrade of Sequans Monarch 2 platform, disregarding the version check
```bash
pysequans upgrade full --force
```
Do a full upgrade with a specified firmware file.
Note that this command will not do any version checking of the provided firmware vs the current active firmware,
i.e. the provided firmware will always be programmed in the Sequans Monarch 2 platform.
```bash
pysequans upgrade full -fw myfirmware.dup
```
Read out current firmware version of Sequans Monarch 2 platform and print together with the bundled firmware version
```bash
pysequans upgrade report
```
### Commands for managing storage of certificates and private keys in Sequans Monarch2 platform
There are 20 non-volatile memory (NVM) storage slots available, numbered 0-19, each slot can hold a single private key and a certificate (bundle). Some of these slots are reserved for Sequans internal use, this utility will not allow to modify (write or erase) these, but they can be read. It is not required to erase a slot prior to writing, new content will replace previous content.
For certificates, multiple files may be written to a slot, and will be concatenated to a bundle and written to the NVM slot. This can be done either by specifying multiple `-f file` options, or `-f folder` referring to a folder containing only certificate files, or a combination of the two. For private keys, only a single file is allowed. All input files must be in PEM format.
Be advised that NVM slots 18 and 19 are used by the IoT provisioning tool (`iotprovision`) to store device and Root CA certificates for cloud provider, respectively. It is therefore recommended to avoid using these slots for other purposes (Mosquitto, HTTPS, etc) because these slots will be overwritten whenever the provisioning tool is used.
Upload a single certificate file to NVM slot 16
```bash
pysequans nvm write 16 --certificate -f mycert.pem
```
Upload all certificate files in a folder and write as a bundle to NVM slot 17
```bash
pysequans nvm write 17 --certificate -f my_certs_folder
```
Upload 3 individual certificate files and write as a bundle to NVM slot 17
```bash
pysequans nvm write 17 --certificate -f cert1.pem -f cert2.pem -f cert3.pem
```
Upload private key file to NVM slot 16
```bash
pysequans nvm write 16 --private-key -f private_key.pem
```
Erase private key in slot 17. Note that this command will fail if the private key slot is already empty.
```bash
pysequans nvm erase 17 --private-key
```
Read certificate in slot 18. Note that this command will fail if the certificate slot is empty. The readout format presented by Sequans Monarch2 platform is for informational purposes only, it is not suitable for downloading certificates or private keys from the NVM.
```bash
pysequans nvm read 18 --certificate
```
## Sequans Monarch2 platform security profiles
Security profiles define security-related attributes used by secure protocols like HTTPS or MQTT with TLS enabled. When setting up or using these protocols, security profile is referred to by a numeric security profile ID (`spId`). There are 6 security profiles numbered 1-6. Unsecured connections like plain HTTP don't need a security profile.
Security profile 1 is set up by the provisioning tool (`iotprovison`) for cloud providers, and it is not recommended using it for other purposes. In Microchip-provided cellular demo firmwares, security profile 1 is used for AWS or Azure IoT cloud connection, profile 2 is used for general secured MQTT, and security profile 3 is used for HTTPS. If you plan to use the kit for anything else than cloud provider provisioned for with `iotprovision`, you need to set up a security profile as described below.
Security profile setup is typically the next step after storing certificate(s) and private key (if any) using the pysequans NVM commands described in the previous section.
### Connect to kit using a terminal program
Pysequans has no built-in features to manage security profiles yet, so this must be done by means of using an external terminal program to connect to the kit and enter raw modem commands. Any terminal program capable of connecting to a serial port can be used.
If you don't have a favorite terminal program already installed, use `pyserial-miniterm` which is provided as a dependency when `pysequansutils` is installed. Set baud rate to 115200 for the provisioning firmware, and enable local echo (aka half duplex) to see what you are typing.
You need to have the Microchip provisioning firmware programmed into your kit, if you have used the `pysequans` command already with your kit, this will be the case.
To connect to the kit using pyserial-miniterm, use the following command:
```bash
pyserial-miniterm <port> 115200 --echo
```
The name of the serial port can be determined with our `pykitinfo` utility, or using `pyserial-ports`.
When connected, you will be talking to our provisioning firmware, you need to activate bridge mode in order to talk to the modem:
```bash
MC+BRIDGEMODE
```
which should respond with `OK`. You are now ready to type in modem commands. Modem commands are not case sensitive, but are shown in upper case here. To check that you are talking to the modem, try the `ATI` command, it shows information about modem and firmware version:
```
ATI
SEQUANS Communications
GM02S
UE8.0.5.11
OK
```
In order to get somewhat more informative error messages than just `ERROR` from the modem, in interactive sessions it is recommended to set error verbosity level to maximum before proceeding, using command `AT+CMEE`:
```
AT+CMEE=2
OK
```
### Setting up security profile using AT+SQNSPCFG modem command
THe modem command to manage security profiles is `AT+SQNSPCFG`. You can use `AT+SQNSPCFG=?` to get a usage summary:
```
AT+SQNSPCFG=?
+SQNSPCFG: (1-6),(0-3,255),("0x1301;0x1302;0x1303<...>"),(0x00-0xFF),(0-19),(0-19),(0-19),,,(0,1),(0,1),(0-UINT_MAX)
```
The parameters are described below. Parameters are separated with `","`, unused parameters can be skipped with double comma (`",,"`)
```bash
AT+SQNSPCFG=<spId> # Security profile ID (1-6)
[,<version>, # SSL/TLS protocol <version> to use (0-3 => TLS v.1.0 - 1.3), 255 to reset (clear) the security profile
[<cipherSpecs>, # List of cipher suites (<cipherSpecs>) to be used for SSL/TLS connection security settings negotiation
[<certValidLevel>, # Server certificate validation level <certValidLevel>: 0=None, bit 0=1: Check against root CA certificates, bit 2=1: verify server URL against certificate common name
[<caCertificateID>, # NVM slot containing Root CA certificate(s) for server validation
[<clientCertificateID>, # NVM slot containing certificate to be used for client authentication
[<clientPrivateKeyID>, # NVM slot containing client private key
[<psk>, # Pre-shared key <psk> used for connection
[<pskIdentity>, # Pre-shared key identity <pskIdentity> used for connection
[<storageId>, # <storageId> used to identify whether the private key is stored in NVM or HCE (Hardware Crypto Engine)
[<resume>, # Attempt to resume the previous security session if possible.
[<lifetime>]]]]]]]]] # TLS session maximum lifetime
```
The parameters most commonly used are: `spId`, `version` (=2 or 3), `certValidLevel` (=1), `caCertificateID`, `clientCertificateID`, `storageId`. If NVM private key is used (`storageId` == 0), `clientPrivateKeyID` also needs to be set.
Content of security profiles may be viewed by using `AT+SQNSPCFG` command without parameters:
```
AT+SQNSPCFG
+SQNSPCFG: 1,2,"0xC02B",1,19,18,0,"","",1,0,0
+SQNSPCFG: 2,2,"",0,,,,"","",0,0,0
+SQNSPCFG: 3,2,"",1,5,,,"","",0,0,0
```
### Examples
Set up security profile 2 to use TLS 1.2, root CA certificates in slot 17, device certificate in slot 16, certificate generated from ECC public key (typical setup for Mosquitto test):
```
AT+SQNSPCFG=2,2,"",1,17,16,,"","",1
+SQNSPCFG: 2,2,"",1,17,16,,"","",1,0,0
OK
```
Set up security profile 3 to use TLS 1.2, root CA certificates in slot 15 (typical setup for HTTPS):
```
AT+SQNSPCFG=3,2,"",1,15,,,"",""
+SQNSPCFG: 3,2,"",1,15,,,"","",0,0,0
OK
```
## Library
pysequansutils is a collection of utilities and it can be used as a library by accessing the individual modules.
### Logging
This package uses the Python logging module for publishing log messages to library users.
A basic configuration can be used (see example below), but for best results a more thorough configuration is
recommended in order to control the verbosity of output from dependencies in the stack which also use logging.
See logging.yaml which is included in the package (although only used for CLI).
```python
# pysequansutils uses the Python logging module
import logging
logging.basicConfig(format="%(levelname)s: %(message)s", level=logging.WARNING)
```
### Do a full upgrade with bundled firmware
The `upgrade` module contains functions to do full firmware upgrades. For example:
```python
from pysequansutils.upgrade import full_upgrade
upgraded, active_version = full_upgrade()
if upgraded:
print(f"Successfully upgraded firmware to version '{active_version}'")
else:
print(f"Upgrade skipped. Current version is '{active_version}'")
```
### Write certificate data to a NVM slot
The `nvmstorage` module contains functions to access NVM storage slots. Note that most argument validation is done in the CLI, in particular protection of the reserved slots, so unless the Sequans Monarch2 platform enforces this protection, which it does not at the time of writing, the user of this API must do so using the list AVAILABLE_NVM_SLOTS defined in the module.
```python
import pysequansutils.nvmstorage as nvm
from pysequansutils.pysequans_errors import PysequansError
...
if slot in nvm.AVAILABLE_NVM_SLOTS:
try:
nvm.write_slot(atdriver, slot, nvm.NVM_CERTIFICATE, data)
except PysequansError as e:
...
else:
raise ValueError(f'Illegal NVM slot: {slot}')
```
## Notes for Linux® systems
This package uses pyedbglib and other libraries for USB transport and some udev rules are required.
For details see the pyedbglib package: https://pypi.org/project/pyedbglib
# Changelog
## [2.3] - December 2023
### Added
- DSG-5807 Added new Sequans firmware
### Changed
- DSG-5680 Removed unused --report argument in pysequans upgrade CLI
### Fixed
- DSG-5944 Unable to recover kit that previously failed full upgrade
- DSG-6135 PEP-0440 compliance for pysequansutils
## [2.1.4] - October 2022
### Added
- DSG-5246 CLI `nvm` subcommand for managing certificate and private key storage
- DSG-5369 Added documentation of security profile usage
### Changed
- DSG-5246 CLI `-v`/`--verbose` option now has global scope only, and must be placed before subcommand
- DSG-5541 Updated bundled Sequans FW from version LR8.0.5.10 to LR8.0.5.11
- DSG-5398 CLI short form options now always use single-dash prefix (eg: -sprov instead of --sprov)
- DSG-5447 Added metadata tag for Python 3.10
- DSG-5545 Removed metadata tag for Python 3.6
- DSG-5111 Removed github links
- DSG-5613 Updated pykitcommander dependency requirement (to use updated provisioning firmware)
- DSG-5627 Changed behaviour of -P switch to override an automatically detected port
- DSG-5624 Updated pyedbglib dependency requirement for improved serial port detection
## [1.0.3] - June 2022 - initial release
### Added
- DSG-4706 upgrade (backend API)
- DSG-4712 full upgrade support
- DSG-4705 CLI for full upgrade
- DSG-4707 CLI option to skip programming bridge firmware
- DSG-4708 CLI option to provide modem firmware
- DSG-4709 CLI command for version reporting (on-kit, bundled)
Raw data
{
"_id": null,
"home_page": "",
"name": "pysequansutils",
"maintainer": "",
"docs_url": null,
"requires_python": ">=3.8",
"maintainer_email": "",
"keywords": "Microchip,Cellular,Modem,AVR-IoT,Sequans",
"author": "",
"author_email": "Microchip Technology <support@microchip.com>",
"download_url": "",
"platform": null,
"description": "# pysequansutils\npysequansutils provides tools for the Sequans Monarch 2 platform which is used on Microchip cellular IoT development boards.\n\n\n\n\n\n## Usage\npysequansutils can be used as a command-line interface or a library\n\npysequansutils comes bundled with a dup file for a full upgrade of the Sequans Monarch 2 platform. This dup file can be found in the fw folder of the package.\n\n## Command-line interface\npysequansutils is a multi-layered command-line interface meaning that there are several commands each\nwith its own actions and options.\n\nGetting help:\n```bash\npysequans --help\n```\nGetting help for specific command (in this example the `upgrade` command):\n```bash\npysequans upgrade --help\n```\nThe amount of logging is controlled by the -v/--verbose option:\n```bash\npysequans -v info\n```\nPossible log levels are `debug`, `info`, `warning`, `error`, `critical`. Default is `info`.\n\nPrint version info and exit:\n```bash\npysequans -V\n```\nPrint release info and exit:\n```bash\npysequans -R\n```\n### Commands for upgrading the firmware of a Sequans Monarch2 platform\nDo a full upgrade of Sequans Monarch 2 platform using the bundled firmware. This will only upgrade the firmware if the bundled firmware is newer than the current firmware of the Monarch2 platform.\n```bash\npysequans upgrade full\n```\nDo a forced full upgrade/downgrade of Sequans Monarch 2 platform, disregarding the version check\n```bash\npysequans upgrade full --force\n```\nDo a full upgrade with a specified firmware file.\nNote that this command will not do any version checking of the provided firmware vs the current active firmware,\ni.e. the provided firmware will always be programmed in the Sequans Monarch 2 platform.\n```bash\npysequans upgrade full -fw myfirmware.dup\n```\nRead out current firmware version of Sequans Monarch 2 platform and print together with the bundled firmware version\n```bash\npysequans upgrade report\n```\n### Commands for managing storage of certificates and private keys in Sequans Monarch2 platform\nThere are 20 non-volatile memory (NVM) storage slots available, numbered 0-19, each slot can hold a single private key and a certificate (bundle). Some of these slots are reserved for Sequans internal use, this utility will not allow to modify (write or erase) these, but they can be read. It is not required to erase a slot prior to writing, new content will replace previous content.\n\nFor certificates, multiple files may be written to a slot, and will be concatenated to a bundle and written to the NVM slot. This can be done either by specifying multiple `-f file` options, or `-f folder` referring to a folder containing only certificate files, or a combination of the two. For private keys, only a single file is allowed. All input files must be in PEM format.\n\nBe advised that NVM slots 18 and 19 are used by the IoT provisioning tool (`iotprovision`) to store device and Root CA certificates for cloud provider, respectively. It is therefore recommended to avoid using these slots for other purposes (Mosquitto, HTTPS, etc) because these slots will be overwritten whenever the provisioning tool is used.\n\nUpload a single certificate file to NVM slot 16\n```bash\npysequans nvm write 16 --certificate -f mycert.pem\n```\nUpload all certificate files in a folder and write as a bundle to NVM slot 17\n```bash\npysequans nvm write 17 --certificate -f my_certs_folder\n```\nUpload 3 individual certificate files and write as a bundle to NVM slot 17\n```bash\npysequans nvm write 17 --certificate -f cert1.pem -f cert2.pem -f cert3.pem\n```\nUpload private key file to NVM slot 16\n```bash\npysequans nvm write 16 --private-key -f private_key.pem\n```\nErase private key in slot 17. Note that this command will fail if the private key slot is already empty.\n```bash\npysequans nvm erase 17 --private-key\n```\nRead certificate in slot 18. Note that this command will fail if the certificate slot is empty. The readout format presented by Sequans Monarch2 platform is for informational purposes only, it is not suitable for downloading certificates or private keys from the NVM.\n```bash\npysequans nvm read 18 --certificate\n\n```\n## Sequans Monarch2 platform security profiles\nSecurity profiles define security-related attributes used by secure protocols like HTTPS or MQTT with TLS enabled. When setting up or using these protocols, security profile is referred to by a numeric security profile ID (`spId`). There are 6 security profiles numbered 1-6. Unsecured connections like plain HTTP don't need a security profile.\n\nSecurity profile 1 is set up by the provisioning tool (`iotprovison`) for cloud providers, and it is not recommended using it for other purposes. In Microchip-provided cellular demo firmwares, security profile 1 is used for AWS or Azure IoT cloud connection, profile 2 is used for general secured MQTT, and security profile 3 is used for HTTPS. If you plan to use the kit for anything else than cloud provider provisioned for with `iotprovision`, you need to set up a security profile as described below.\n\nSecurity profile setup is typically the next step after storing certificate(s) and private key (if any) using the pysequans NVM commands described in the previous section.\n\n### Connect to kit using a terminal program\nPysequans has no built-in features to manage security profiles yet, so this must be done by means of using an external terminal program to connect to the kit and enter raw modem commands. Any terminal program capable of connecting to a serial port can be used.\n\nIf you don't have a favorite terminal program already installed, use `pyserial-miniterm` which is provided as a dependency when `pysequansutils` is installed. Set baud rate to 115200 for the provisioning firmware, and enable local echo (aka half duplex) to see what you are typing.\n\nYou need to have the Microchip provisioning firmware programmed into your kit, if you have used the `pysequans` command already with your kit, this will be the case.\n\nTo connect to the kit using pyserial-miniterm, use the following command:\n```bash\npyserial-miniterm <port> 115200 --echo\n```\nThe name of the serial port can be determined with our `pykitinfo` utility, or using `pyserial-ports`.\nWhen connected, you will be talking to our provisioning firmware, you need to activate bridge mode in order to talk to the modem:\n```bash\nMC+BRIDGEMODE\n```\nwhich should respond with `OK`. You are now ready to type in modem commands. Modem commands are not case sensitive, but are shown in upper case here. To check that you are talking to the modem, try the `ATI` command, it shows information about modem and firmware version:\n```\nATI\n\nSEQUANS Communications\nGM02S\nUE8.0.5.11\n\nOK\n```\nIn order to get somewhat more informative error messages than just `ERROR` from the modem, in interactive sessions it is recommended to set error verbosity level to maximum before proceeding, using command `AT+CMEE`:\n```\nAT+CMEE=2\n\nOK\n\n```\n### Setting up security profile using AT+SQNSPCFG modem command\n\nTHe modem command to manage security profiles is `AT+SQNSPCFG`. You can use `AT+SQNSPCFG=?` to get a usage summary:\n```\nAT+SQNSPCFG=?\n\n+SQNSPCFG: (1-6),(0-3,255),(\"0x1301;0x1302;0x1303<...>\"),(0x00-0xFF),(0-19),(0-19),(0-19),,,(0,1),(0,1),(0-UINT_MAX)\n\n```\nThe parameters are described below. Parameters are separated with `\",\"`, unused parameters can be skipped with double comma (`\",,\"`)\n```bash\nAT+SQNSPCFG=<spId> # Security profile ID (1-6)\n[,<version>, # SSL/TLS protocol <version> to use (0-3 => TLS v.1.0 - 1.3), 255 to reset (clear) the security profile\n[<cipherSpecs>, # List of cipher suites (<cipherSpecs>) to be used for SSL/TLS connection security settings negotiation\n[<certValidLevel>, # Server certificate validation level <certValidLevel>: 0=None, bit 0=1: Check against root CA certificates, bit 2=1: verify server URL against certificate common name\n[<caCertificateID>, # NVM slot containing Root CA certificate(s) for server validation\n[<clientCertificateID>, # NVM slot containing certificate to be used for client authentication\n[<clientPrivateKeyID>, # NVM slot containing client private key\n[<psk>, # Pre-shared key <psk> used for connection\n[<pskIdentity>, # Pre-shared key identity <pskIdentity> used for connection\n[<storageId>, # <storageId> used to identify whether the private key is stored in NVM or HCE (Hardware Crypto Engine)\n[<resume>, # Attempt to resume the previous security session if possible.\n[<lifetime>]]]]]]]]] # TLS session maximum lifetime\n```\nThe parameters most commonly used are: `spId`, `version` (=2 or 3), `certValidLevel` (=1), `caCertificateID`, `clientCertificateID`, `storageId`. If NVM private key is used (`storageId` == 0), `clientPrivateKeyID` also needs to be set.\n\nContent of security profiles may be viewed by using `AT+SQNSPCFG` command without parameters:\n```\nAT+SQNSPCFG\n\n+SQNSPCFG: 1,2,\"0xC02B\",1,19,18,0,\"\",\"\",1,0,0\n+SQNSPCFG: 2,2,\"\",0,,,,\"\",\"\",0,0,0\n+SQNSPCFG: 3,2,\"\",1,5,,,\"\",\"\",0,0,0\n```\n\n### Examples\nSet up security profile 2 to use TLS 1.2, root CA certificates in slot 17, device certificate in slot 16, certificate generated from ECC public key (typical setup for Mosquitto test):\n```\nAT+SQNSPCFG=2,2,\"\",1,17,16,,\"\",\"\",1\n\n+SQNSPCFG: 2,2,\"\",1,17,16,,\"\",\"\",1,0,0\n\nOK\n```\nSet up security profile 3 to use TLS 1.2, root CA certificates in slot 15 (typical setup for HTTPS):\n```\nAT+SQNSPCFG=3,2,\"\",1,15,,,\"\",\"\"\n\n+SQNSPCFG: 3,2,\"\",1,15,,,\"\",\"\",0,0,0\n\nOK\n```\n\n## Library\npysequansutils is a collection of utilities and it can be used as a library by accessing the individual modules.\n\n### Logging\nThis package uses the Python logging module for publishing log messages to library users.\nA basic configuration can be used (see example below), but for best results a more thorough configuration is\nrecommended in order to control the verbosity of output from dependencies in the stack which also use logging.\nSee logging.yaml which is included in the package (although only used for CLI).\n```python\n# pysequansutils uses the Python logging module\nimport logging\nlogging.basicConfig(format=\"%(levelname)s: %(message)s\", level=logging.WARNING)\n```\n\n### Do a full upgrade with bundled firmware\nThe `upgrade` module contains functions to do full firmware upgrades. For example:\n```python\nfrom pysequansutils.upgrade import full_upgrade\nupgraded, active_version = full_upgrade()\nif upgraded:\n print(f\"Successfully upgraded firmware to version '{active_version}'\")\nelse:\n print(f\"Upgrade skipped. Current version is '{active_version}'\")\n```\n### Write certificate data to a NVM slot\nThe `nvmstorage` module contains functions to access NVM storage slots. Note that most argument validation is done in the CLI, in particular protection of the reserved slots, so unless the Sequans Monarch2 platform enforces this protection, which it does not at the time of writing, the user of this API must do so using the list AVAILABLE_NVM_SLOTS defined in the module.\n```python\nimport pysequansutils.nvmstorage as nvm\nfrom pysequansutils.pysequans_errors import PysequansError\n...\nif slot in nvm.AVAILABLE_NVM_SLOTS:\n try:\n nvm.write_slot(atdriver, slot, nvm.NVM_CERTIFICATE, data)\n except PysequansError as e:\n ...\nelse:\n raise ValueError(f'Illegal NVM slot: {slot}')\n```\n\n\n## Notes for Linux\u00ae systems\nThis package uses pyedbglib and other libraries for USB transport and some udev rules are required.\nFor details see the pyedbglib package: https://pypi.org/project/pyedbglib\n# Changelog\n\n## [2.3] - December 2023\n\n### Added\n- DSG-5807 Added new Sequans firmware\n\n### Changed\n- DSG-5680 Removed unused --report argument in pysequans upgrade CLI\n\n### Fixed\n- DSG-5944 Unable to recover kit that previously failed full upgrade\n- DSG-6135 PEP-0440 compliance for pysequansutils\n\n## [2.1.4] - October 2022\n\n### Added\n- DSG-5246 CLI `nvm` subcommand for managing certificate and private key storage\n- DSG-5369 Added documentation of security profile usage\n\n### Changed\n- DSG-5246 CLI `-v`/`--verbose` option now has global scope only, and must be placed before subcommand\n- DSG-5541 Updated bundled Sequans FW from version LR8.0.5.10 to LR8.0.5.11\n- DSG-5398 CLI short form options now always use single-dash prefix (eg: -sprov instead of --sprov)\n- DSG-5447 Added metadata tag for Python 3.10\n- DSG-5545 Removed metadata tag for Python 3.6\n- DSG-5111 Removed github links\n- DSG-5613 Updated pykitcommander dependency requirement (to use updated provisioning firmware)\n- DSG-5627 Changed behaviour of -P switch to override an automatically detected port\n- DSG-5624 Updated pyedbglib dependency requirement for improved serial port detection\n\n## [1.0.3] - June 2022 - initial release\n\n### Added\n- DSG-4706 upgrade (backend API)\n- DSG-4712 full upgrade support\n- DSG-4705 CLI for full upgrade\n- DSG-4707 CLI option to skip programming bridge firmware\n- DSG-4708 CLI option to provide modem firmware\n- DSG-4709 CLI command for version reporting (on-kit, bundled)\n",
"bugtrack_url": null,
"license": "MIT",
"summary": "Collection of tools for cloud provisioning of Microchip IoT kits",
"version": "2.3.3.21",
"project_urls": {
"Homepage": "https://github.com/microchip-pic-avr-tools/pysequansutils"
},
"split_keywords": [
"microchip",
"cellular",
"modem",
"avr-iot",
"sequans"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "b7167b82fd4fc42689ee2f2e2c68d4d96a120279366d1ba098150dcc1bbb3b3f",
"md5": "3eb16ba7ba0a118e51f14b1712082f47",
"sha256": "13b5601b60475ca575b9b75ec2a3124d41b164048e5dbf3bdcab849b86b57645"
},
"downloads": -1,
"filename": "pysequansutils-2.3.3.21-py3-none-any.whl",
"has_sig": false,
"md5_digest": "3eb16ba7ba0a118e51f14b1712082f47",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.8",
"size": 3643681,
"upload_time": "2023-12-13T06:16:06",
"upload_time_iso_8601": "2023-12-13T06:16:06.991946Z",
"url": "https://files.pythonhosted.org/packages/b7/16/7b82fd4fc42689ee2f2e2c68d4d96a120279366d1ba098150dcc1bbb3b3f/pysequansutils-2.3.3.21-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2023-12-13 06:16:06",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "microchip-pic-avr-tools",
"github_project": "pysequansutils",
"github_not_found": true,
"lcname": "pysequansutils"
}
