blob: dbaa3ad9bcf4eafe4879b2246d3432939185c866 [file] [log] [blame] [view]
David Brown37f8afd2017-09-12 10:59:39 -06001# MCUboot Release Notes
2
3- Table of Contents
4{:toc}
5
Szymon Janc7fea8462019-07-04 14:45:52 +02006## Version 1.3.1
7
8The 1.3.1 release of MCUboot consists mostly of small bug fixes and updates.
9There are no breaking changes in functionality. This release should work with
10Mynewt 1.6.0 and up, and any Zephyr `master` after sha
11f51e3c296040f73bca0e8fe1051d5ee63ce18e0d.
12
13### About this release
14
15- Fixed a revert interruption bug
16- Added ed25519 signing support
17- Added RSA-3072 signing support
18- Allow ec256 to run on CC310 interface
19- Some preparation work was done to allow for multi image support, which
20 should land in 1.4.0. This includes a simulator update for testing
21 multi-images, and a new name for slot0/slot1 which are now called
22 "primary slot" and "secondary slot".
23- Other minor bugfixes and improvements
24
David Brownb1d15a72019-01-22 16:22:08 -070025## Version 1.3.0
26
27The 1.3.0 release of MCUboot brings in many fixes and updates. There
28are no breaking changes in functionality. Many of the changes are
29refactorings that will make the code easier to maintain going forward.
30In addition, support has been added for encrypted images. See [the
31docs](encrypted_images.md) for more information.
32
33### About this release
34
35- Modernize the Zephyr build scripts.
36- Add a `ptest` utility to help run the simulator in different
37 configurations.
38- Migrate the simulator to Rust 2018 edition. The sim now requires at
39 least Rust 1.32 to build.
40- Simulator cleanups. The simulator code is now built the same way
41 for every configuration, and queries the MCUboot code for how it was
42 compiled.
43- Abstract logging in MCUboot. This was needed to support the new
44 logging system used in Zephyr.
45- Add multiple flash support. Allows slot1/scratch to be stored in an
46 external flash device.
47- Add support for [encrypted images](encrypted_images.md).
48- Add support for flash devices that read as '0' when erased.
49- Add support to Zephyr for the `nrf52840_pca10059`. This board
50 supports serial recovery over USB with CDC ACM.
51- imgtool is now also available as a python package on pypi.org.
52- Add an option to erase flash pages progressively during recovery to
53 avoid possible timeouts (required especially by serial recovery
54 using USB with CDC ACM).
55- imgtool: big-endian support
56- imgtool: saves in intel-hex format when output filename has `.hex`
57 extension; otherwise saves in binary format.
58
Fabio Utzig3c939012018-06-25 13:26:32 -030059## Version 1.2.0
60
61The 1.2.0 release of MCUboot brings a lot of fixes/updates, where much of the
62changes were on the boot serial functionality and imgtool utility. There are
63no breaking changes in MCUBoot functionality, but some of the CLI parameters
64in imgtool were changed (either removed or added or updated).
65
66### About this release
67
68- imgtool accepts .hex formatted input
69- Logging system is now configurable
70- Most Zephyr configuration has been switched to Kconfig
71- Build system accepts .pem files in build system to autogenerate required
72 key arrays used internally
73- Zephyr build switched to using built-in flash_map and TinyCBOR modules
74- Serial boot has substantially decreased in space usage after refactorings
75- Serial boot build doesn't require newlib-c anymore on Zephyr
76- imgtool updates:
77 + "create" subcommand can be used as an alias for "sign"
78 + To allow imgtool to always perform the check that firmware does not
79 overflow the status area, `--slot-size` was added and `--pad` was updated
80 to act as a flag parameter.
81 + `--overwrite-only` can be passed if not using swap upgrades
82 + `--max-sectors` can be used to adjust the maximum amount of sectors that
83 a swap can handle; this value must also be configured for the bootloader
84 + `--pad-header` substitutes `--included-header` with reverted semantics,
85 so it's not required for firmware built by Zephyr build system
86
87### Known issues
88
89None
90
Fabio Utzig49045cc2018-01-09 15:56:29 -020091## Version 1.1.0
92
Carles Cufi90eda802018-01-29 18:33:20 +010093The 1.1.0 release of MCUboot brings a lot of fixes/updates to its
Fabio Utzig49045cc2018-01-09 15:56:29 -020094inner workings, specially to its testing infrastructure which now
95enables a more thorough quality assurance of many of the available
96options. As expected of the 1.x.x release cycle, no breaking changes
97were made. From the tooling perpective the main addition is
98newt/imgtool support for password protected keys.
99
100### About this release
101
102- serial recovery functionality support under Zephyr
103- simulator: lots of refactors were applied, which result in the
104 simulator now leveraging the Rust testing infrastructure; testing
105 of ecdsa (secp256r1) was added
106- imgtool: removed PKCS1.5 support, added support for password
107 protected keys
108- tinycrypt 0.2.8 and the mbed-tls ASN1 parser are now bundled with
109 mcuboot (eg secp256r1 is now free of external dependencies!)
110- Overwrite-only mode was updated to erase/copy only sectors that
111 actually store firmware
112- A lot of small code and documentation fixes and updates.
113
114### Known issues
115
116None
117
David Brown37f8afd2017-09-12 10:59:39 -0600118## Version 1.0.0
119
Carles Cufi90eda802018-01-29 18:33:20 +0100120The 1.0.0 release of MCUboot introduces a format change. It is
David Brown37f8afd2017-09-12 10:59:39 -0600121important to either use the `imgtool.py` also from this release, or
122pass the `-2` to recent versions of the `newt` tool in order to
123generate image headers with the new format. There should be no
124incompatible format changes throughout the 1.x.y release series.
125
126### About this release
127
128- Header format change. This change was made to move all of the
129 information about signatures out of the header and into the TLV
130 block appended to the image. This allows
131 - The signature to be replaced without changing the image.
132 - Multiple signatures to be applied. This can be used, for example,
133 to sign an image with two algorithms, to support different
134 bootloader configurations based on these image.
135 - The public key is referred to by its SHA1 hash (or a prefix of the
136 hash), instead of an index that has to be maintained with the
137 bootloader.
138 - Allow new types of signatures in the future.
139- Support for PKCS#1 v1.5 signatures has been dropped. All RSA
140 signatures should be made with PSS. The tools have been changed to
141 reflect this.
142- The source for Tinycrypt has been placed in the MCUboot tree. A
143 recent version of Tinycrypt introduced breaking API changes. To
144 allow MCUboot to work across various platforms, we stop using the
145 Tinycrypt bundled with the OS platform, and use our own version. A
146 future release of MCUboot will update the Tinycrypt version.
147- Support for some new targets:
148 - Nordic nRF51 and nRF52832 dev kits
149 - Hexiwear K64
150- Clearer sample applications have been added under `samples`.
Fabio Utzig4dce6aa2018-02-12 15:31:32 -0200151- Test plans for [zephyr](testplan-zephyr.md), and
152 [mynewt](testplan-mynewt.md).
David Brown37f8afd2017-09-12 10:59:39 -0600153- The simulator is now able to test RSA signatures.
154- There is an unimplemented `load_addr` header for future support for
155 RAM loading in the bootloader.
156- Numerous documentation.
157
158### Known issues
159
160None
161
162## Version 0.9.0
163
Carles Cufi90eda802018-01-29 18:33:20 +0100164This is the first release of MCUboot, a secure bootloader for 32-bit MCUs.
David Brown37f8afd2017-09-12 10:59:39 -0600165It is designed to be operating system-agnostic and works over any transport -
166wired or wireless. It is also hardware independent, and relies on hardware
167porting layers from the operating system it works with. For the first release,
168we have support for three open source operating systems: Apache Mynewt, Zephyr
169and RIOT.
170
171### About this release
172
173- This release supports building with and running Apache Mynewt and Zephyr
174 targets.
175- RIOT is supported as a running target.
176- Image integrity is provided with SHA256.
177- Image originator authenticity is provided supporting the following
178 signature algorithms:
179 - RSA 2048 and RSA PKCS#1 v1.5 or v2.1
180 - Elliptic curve DSA with secp224r1 and secp256r1
181- Two firmware upgrade algorithms are provided:
182 - An overwrite only which upgrades slot 0 with the image in slot 1.
183 - A swapping upgrade which enables image test, allowing for rollback to a
184 previous known good image.
185- Supports both mbed-TLS and tinycrypt as backend crypto libraries. One of them
186 must be defined and the chosen signing algorithm will require a particular
187 library according to this list:
188 - RSA 2048 needs mbed TLS
189 - ECDSA secp224r1 needs mbed TLS
190 - ECDSA secp256r1 needs tinycrypt as well as the ASN.1 code from mbed TLS
191 (so still needs that present).
192
193### Known issues
194
195- The image header and TLV formats are planned to change with release 1.0:
196 https://runtimeco.atlassian.net/browse/MCUB-66