Initial commit

Initial commit.

bootloader/mcuboot/docs/release-notes.d/00readme.md

@@ -0,0 +1,29 @@
+# Pending release notes directory
+
+This directory contains release note entries that have not been merged
+into the main release-notes.md document.
+
+Generally a release note entry should be created for changes that:
+
+- Fix bugs in the code.
+- Implement new features.
+- Change existing behavior.
+
+Release notes are generally not needed for:
+
+- Some documentation improvements.
+- Strictly internal changes to the code that won't be visible to users
+  of the code.
+
+## Release note format
+
+Release notes are included in files under this `docs/release-notes.d`
+directory and have a name of `*.md`.  They will be included in the
+`release-notes.md` file, and should be formatted as a Markdown list
+entry.  (A script will be developed to collect these, ordered by when
+the commits were added to the tree.)
+
+Choose a filename that is related to what this change does.  The names
+are not used for anything in particular, but to keep the files
+distinct so that there isn't a concern with merge conflicts as
+different pull requests merge in different orders.

bootloader/mcuboot/docs/release-notes.d/bootutil-enc-hw-keys.md

@@ -0,0 +1,2 @@
+- Added support for retrieving hw embed private keys for image encryption
+  (The private key can be retrieved from trusted sources like OTP, TPM.).

bootloader/mcuboot/docs/release-notes.d/bootutil-image-verification.md

@@ -0,0 +1,4 @@
+- Changed bootutil's order of events to verify the image header
+  before checking the image.
+- Added the bootloader state object to the bootutil
+  boot_is_header_valid() function

bootloader/mcuboot/docs/release-notes.d/encrypted-scratch-partition.md

@@ -0,0 +1,3 @@
+- When using swap with scratch, the image is now decrypted when copying from
+  the scratch partition to the primary slot. Therefore, the sratch partition
+  doesn't contain plaintext firmware data anymore.

bootloader/mcuboot/docs/release-notes.d/fix-nordic.md

@@ -0,0 +1,2 @@
+- Fixed errors when building for ``thingy52``, ``thingy53`` and
+  ``nrf9160dk`` boards.

bootloader/mcuboot/docs/release-notes.d/fix-ram-load-zephyr-address.md

@@ -0,0 +1,2 @@
+- Fixed chain load address output log message for RAM load
+  mode in Zephyr

bootloader/mcuboot/docs/release-notes.d/fix-zephyr-sysbuild-name.md

@@ -0,0 +1,2 @@
+- Fixed clash when using sysbuild with other
+  applications (i.e. tests) using the name sysbuild

bootloader/mcuboot/docs/release-notes.d/imgtool_sanity_test.md

@@ -0,0 +1,2 @@
+- imgtool: added initial sanity tests for imgtool commands,
+- imgtool: added and enabled unittests in GitGub workflow,

bootloader/mcuboot/docs/release-notes.d/max-app-size-changes.md

@@ -0,0 +1,4 @@
+- Fixed wrong maximum application size calculation when
+  operating in swap using move mode
+- Added additional images max size support to shared data
+  function

bootloader/mcuboot/docs/release-notes.d/serial-recovery-slot-info.md

@@ -0,0 +1 @@
+- Added slot info command support to serial recovery mode

bootloader/mcuboot/docs/release-notes.d/zephyr-auto-max-sectors.md

@@ -0,0 +1,5 @@
+- Added support for automatically calculating the maximum number
+  of sectors that are needed for a build by checking the erase
+  sizes of the partitions using CMake for Zephyr. This behaviour
+  can be reverted to the old manual behaviour by disabling
+  ``CONFIG_BOOT_MAX_IMG_SECTORS_AUTO``

bootloader/mcuboot/docs/release-notes.d/zephyr-compression.md

@@ -0,0 +1,7 @@
+- Added protected TLV size to image size check in bootutil
+- Added Kconfig for decompression support in Zephyr
+- Added compressed image flags and TLV to bootutil
+- Added support for removing images with conflicting flags in
+  bootutil
+- Added support for removing encrypted/compressed images when
+  MCUboot is compiled without support for them