Required: * Python 3.12.10
Installation:
python -m pip uninstall -y flash_images_builder_core
python -m build --wheel --no-isolation
python -m pip install flash_images_builder_core --find-links dist\
Changelog: ## Version 1.0.72 updates: * Add warning after programming if rollback protection fuses not match to the programed image major version.
## Version 1.0.71 updates:
* Implemented ILTOOLS-962 - Implement support for BL3
* Support WSoC as part of the vendor outfile
## Version 1.0.70 updates:
* Mark MX25U12843G as experimental flash
## Version 1.0.69 updates:
* Implemented ILTOOLS-1029 - Added new Flash device Macronix MX25U12843GM2I00
* Implemented ILTOOLS-1044 - Added new Flash devices W25Q33PW / W25Q64PW
## Version 1.0.68 updates:
* Implements ILTOOLS-1056 - Revert UseHardware enum to previous order and add explicit flash detection error handling
## Version 1.0.67 updates:
* No-OTA Memory Map Enhancement: When OTA is disabled, secondary image physical addresses are now set to 0xFFFFFFFF (invalid address) instead of calculated values. Affected addresses:
- boot_region_sec_ti_bl_start_phy_address
- nvs_region_sec_wsoc_start_phy_address
- alt_code_region_vendor_image_start_phy_address
- alt_code_region_sbl_start_phy_address
- nvs_region_sec_wsoc_bl2_start_phy_address
* Region 2 Boundaries: When OTA is disabled, region 2 boundaries are set to 0 (disabled region):
- mem_region_2_start_phy_address
- mem_region_2_end_phy_address
* Alternate Image Flags: When OTA is disabled, alternate image flags are now set to false:
- vendor_alternate_image
- vendor_sbl_alternate_image
- ti_bl_alternate_image
- ti_wsoc_alternate_image
- ti_wsoc_bl2_alternate_image
* Logical Address Calculation Fix: When physical address is 0xFFFFFFFF (invalid/no OTA), the calculate_logical_addr function in tlv.py now returns 0xFFFFFFFF instead of calculating an incorrect logical address.
## Version 1.0.66 updates:
* Add 2MB Stacked PSRAM option for MX3
## Version 1.0.65 updates:
* Add CC37XXR device support
* Make device parameter mandatory in TBLImageBuilder, WSOCImageBuilder, and PSImageBuilder constructors
* Move device parameter to first position in builder constructors for consistency
* Support new device family constants (CC370XR, CC360XR, CC33XX)
* Update device type handling throughout image builders
## Version 1.0.64 updates:
* Remove flash type W25Q12PW from experimental flash types
## Version 1.0.63 updates:
* Implements ILTOOLS-983 - add FLASH_AUTO_DETECT constant
## Version 1.0.62 updates:
* Implements ILTOOLS-989 - [TB][FIB] OTA enable should configure OTFDE region 'enable'
## Version 1.0.61 updates:
* Implements ILTOOLS-991 - [TB][Programmer] Set "flash_reset_type" to be zero for all flash devices
## Version 1.0.60 updates:
* Implements ILTOOLS-964 - [TB][FIB] Add FLASH_SIZE_MB_MAP for auto flash detection feature
## Version 1.0.59 updates:
* Implements ILTOOLS-937 - [TB][Communicator] Update CC35X1E update useHardware enum to be aligned with External Flash detection
## Version 1.0.58 updates:
* BugFix ILTOOLS-973 - [TB][Programmer] 'FIBUtility' object has no attribute 'fib_utility' when trying run memory validation test
## Version 1.0.57 updates:
* Add get_flash_jedec_reset() function to read flash_jedec_reset from flash configuration
## Version 1.0.56 updates:
* BugFix ILTOOLS-892 - [TB][Programmer] External PSRAM options should be visible for external release of Toolbox
## Version 1.0.55 updates:
* Add support for rollback protection fuse programming
## Version 1.0.54 updates:
* Rename CC33XXR, CC35XXR into CC36XXR, CC37XXR
## Version 1.0.53 updates:
* Add new device CC35XXR - ILTOOLS-941 - [TB][FIB] Align FIB with CC35XXR
## Version 1.0.52 updates:
* Bugfix ILTOOLS-924 - [TB][FIB] Protected Storage image generating with user specific data and w/o different
## Version 1.0.51 updates:
* Update default version from 0.0.0.1 into 0.0.1.0
## Version 1.0.50 updates:
* Bugfix #ILTOOLS-916 - Fix mismatch between UI and CLI memory map outputs
## Version 1.0.49 updates:
* Fix ps_img.py logging issue
## Version 1.0.48 updates:
* Add new Flash device Winbond W25Q12PW
## Version 1.0.47 updates:
* Bugfix #ILTOOLS-896 - Apply support of "no OTA" option to Flash larger than 4M
## Version 1.0.46 updates:
* Change syntax to support python 3.9
## Version 1.0.45 updates:
* Bugfix #ILTOOLS-770 - Building of vendor image fails for Zephyr project
## Version 1.0.44 updates:
* Change utility to class
## Version 1.0.43 updates:
* Added ability to mark Flash as experimental not thought the folder name
## Version 1.0.42 updates:
* Bugfix ILTOOLS-848: [TB][Programmer] Vendor image version return -1,-1,-1,-1 when selecting pre builder vendor image
## Version 1.0.41 updates:
* Add new Flash support IS25WJ128F_EXPERIMENTAL
## Version 1.0.40 updates:
* Add new Flash support MX25U3235F_EXPERIMENTAL and MX25U6435F_EXPERIMENTAL
## Version 1.0.39 updates:
* Implemented dynamic memory calculation functionality
## Version 1.0.38 updates:
* Added signing module functions
* Add new static method into GPEBuilder and ActionReq to pull data for signing
* Create new utility module
## Version 1.0.37 updates:
* Update fuse struct
## Version 1.0.36 updates:
* Update logic addr for vendor image on slot 0 to run from 0x14000000
## Version 1.0.35 updates:
* Update vendor image build with conf.bin file
## Version 1.0.34 updates:
* Add new Flash support PY25Q128LA and PY25Q256LC
## Version 1.0.33 updates:
* Update flash-ready builder due to TI programmer issue
## Version 1.0.32 updates:
* Add psram type to TLV
## Version 1.0.31 updates:
* Add more debug messages
## Version 1.0.30 updates:
* Add build of wSoC image
* Update vendor image struct to fit reset vector run from 0x10000200000
## Version 1.0.29 updates:
* Fix bug on build bootsector from jsons
* Get container version using fib
* Create basic class for ti images
## Version 1.0.28 updates:
* Add option to select image output name
## Version 1.0.27 updates:
* Add new Flash support PY25Q64LB
## Version 1.0.26 updates:
* Add option to set tbl image version
## Version 1.0.25 updates:
* Add clean image builder
## Version 1.0.24 updates:
* Add Puya 4M device into UseHardware enum
## Version 1.0.23 updates:
* Add GIGA device into UseHardware enum
## Version 1.0.22 updates:
* [[TB][FIB] Extend flash configuration JSON with new field](https://jira.itg.ti.com/browse/ILTOOLS-615)
## Version 1.0.21 updates:
* Fix logging message
## Version 1.0.20 updates:
* Ghost
## Version 1.0.19 updates:
* Ghost
## Version 1.0.18 updates:
* Add support for multiple flash types
## Version 1.0.17 updates:
* Add WSOC-BL2 container in multiple places (boot sector as pointer, TLV, DSSM prog/query/…, etc.)
## Version 1.0.16 updates:
* Add new manifest record struct for cc35xxe in tbl_img.py
## Version 1.0.15 updates:
* Add manifest integrity for cc35xxe
Metadata
Release files for flash-images-builder-core 1.0.72
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| flash_images_builder_core-1.0.72-py3-none-any.whl | Python 3 | none | any | Details |
Release files / flash_images_builder_core-1.0.72-py3-none-any.whl
| Download URL | flash_images_builder_core-1.0.72-py3-none-any.whl |
|---|---|
| Size | 93.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6bf23e1cc0d175591ce1dffffded309326ec73b62495f4beded8d73e6b6c3515
|
|
BLAKE2b-256 checksum How to use checksums |
123d1d5ff3815ebf98cc0d5fc610c72ef5be56b236de6c4229136035cc85a3b4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.10
|
Security for flash-images-builder-core 1.0.72
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.