Searched refs:to (Results 1 – 25 of 79) sorted by relevance
1234
3 This sample demonstrates how to use a non flash storage to retrieve the image4 being booted. It was tested on a FRDM K64F. Both slots are used to store two5 different images. The image to be booted is selected based on a button press.13 source <path-to-zephyr>/zephyr-env.sh21 Then, build the sample application to be loaded. We need to build it twice, one30 Then change the overlay file to use the second slot. For instance, open38 to:53 Open a serial terminal to see the output and reset the board. It shall boot the
8 - Boot serial: Add response to echo command if support is not20 - bootutil: Added debug logging to show write location of swap status23 - Update ptest to support test selection. Ptest can now be invoked with `list`24 to show the available tests and `run` to run them. The `-t` argument will25 select specific tests to run.26 - Allow sim tests to skip slow tests. By setting `MCUBOOT_SKIP_SLOW_TESTS` in28 instance this reduces the test time from 2 hours to about 5 minutes. These32 to chain-loading an application, this will be automatically34 can be disabled by setting `CONFIG_BOOT_DISABLE_CACHES` to `n`.38 - Zephyr: Add estimated image footer size to cache in sysbuild.[all …]
4 acquired the ability to be used as a bootloader for RIOT as well.5 Currently the support is limited to the nrf52dk platform.10 compile time. This binary was compiled to do an integrity check, but11 not a signature check. In order to configure the bootloader for12 signature check it is necessary to re-compile it either with Mynewt15 In the next version, it is planned to compile MCUboot using RIOT,16 which should be able to boot any of the supported OS images.22 The only variable which needs to be set is `IMAGE_VERSION` loaded25 exported in the Makefile or manually, prior to the compilation process.27 The goal is to produce an ELF file which is linked to be flashed at a[all …]
3 When the ECDSA SECP256R1 (EC256) signature support was added to MCUboot, a4 shortcut was taken, and these signatures were padded to make them9 There are two ways to fix this:12 at least one pad byte to always be added (to set the length). This20 that the length does not need to be known until the signature is28 This document proposes a multi-stage approach to give a transition31 1. Add a `--no-pad-sig` argument to the sign command in39 2. MCUboot will be modified to allow unpadded signatures right away.42 to accept padded and unpadded signatures.45 the `--no-pad-sig` signature to be able to boot all generated[all …]
3 Due to small differences between Mynewt's bundled bootloader and MCUboot,5 which at the same time requires to use `newtmgr` to manage images, MCUboot8 First you need to add the repo to your `project.yml`:35 different TLV structure, so images created by `newt` have to be generated43 like listing images and uploading a new image to `slot0`. The serial bootloader44 requires that `mtu` is set to a value that is less than or equal to `256`.
24 to describe the release. This should be a high-level description of31 should be removed to ready the directory for the next release cycle.38 is to freeze the code and allow testing.41 that should be merged into the main branch are those to fix bugs found47 It requires its version to be updated by editing63 the RC step is finished, the release needs to be exported by modifying65 new release version, including updates to the pseudo keys70 There is a version file used by Zephyr builds to indicate the version71 of MCUboot being used which needs to be updated at73 versions should set `PATCHLEVEL` to `99` and `EXTRAVERSION` to `dev`,[all …]
3 The Python program `scripts/imgtool.py` can be used to perform the4 operations that are necessary to manage keys and sign images. Using5 this script should be preferred to the manual steps described in21 should match what MCUboot is configured to verify.23 This key file is what is used to sign images, this file should be26 You can add the `-p` argument to `keygen`, which will cause it to27 prompt for a password. You will need to enter this password in every39 mynewt, follow the instructions in `doc/signed_images.md` to generate62 --vector-to-sign [payload|digest]63 send to OUTFILE the payload or payloads[all …]
8 Each commit has to have, in the commit message, a "Signed-off-by" line11 line. You can also add a line linking the commit to a specific GitHub12 issue, as this section supports multiple lines, similarly to RFC-2822.16 - A line that indicates that the signer agrees to the "Developer23 - A line that links this commit to specific GitHub issues, if present:29 For more details about linking a GitHub pull request to a GitHub issue,31 …(https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-iss…38 (generally, if there are multiple commits to the pull request, the60 Everyone is permitted to copy and distribute verbatim copies of this66 By making a contribution to this project, I certify that:[all …]
1 # Porting how-to3 This document describes the requirements and necessary steps required to port4 `MCUboot` to a new target `OS`.12 * `MCUboot` requires that the target provides a `flash` API with ability to18 used to provide functionality not existing in `tinycrypt`).20 # Steps to port26 target OS, and it must call the following function to run the bootloader:37 /** A pointer to the header of the image to be executed. */41 * The flash offset of the image to execute. Indicates the position of50 an initialized `boot_rsp` which has pointers to the location of the image[all …]
13 To use MCUboot, you need to create an Mbed OS project with the following configurations:23 You need to provide an instance of `mbed::BlockDevice` as the secondary slot. It can be any types o…25 …write operations are aligned to. If the read size is larger than _one byte_, you need to set `"mcu…27 In order for MCUboot to access your secondary slot, the interface to implement is39 …to `false` so MCUboot is built as a _library only_ without a bootloader application. This is usefu…41 …he beginning of the whole flash), you need to set the start address (`"target.mbed_app_start"`) to…
4 acquired the ability to be used as a bootloader for Zephyr as well.19 It is not recommended to use the swap-using-scratch algorithm of MCUboot, but22 and how to use the swap-using-scratch algorithm):44 cd ~/mcuboot # or to your directory where MCUboot is cloned51 Zephyr's point of view. There is a bit of configuration that needs to54 guidance. It is important to select a signature algorithm, and decide65 In addition to the partitions defined in DTS, some additional66 information about the flash layout is currently required to build75 to flash these binaries from the build directory. Depending77 memory (mass erase) or only the sectors where the bootloader resides prior to[all …]
19 …message(FATAL_ERROR "The mcuboot imgtool python package needs to be installed (from mcuboot/script…24 set(MCUBOOT_SIGNING_KEY "" CACHE STRING "Path to key file (.pem) used to sign firmware updates for …26 # Make sure the signing key path is absolute for EXISTS, relative to the top level build dir31 …message(FATAL_ERROR "Must specify path to valid image signing key via MCUBOOT_SIGNING_KEY CMake op…36 …set(MCUBOOT_ENCRYPTION_KEY "" CACHE STRING "Path to key file (.pem) used to encrypt firmware updat…38 # Make sure the signing key path is absolute for EXISTS, relative to the top level build dir43 …abled, you must specify the path to a valid image encryption key via the MCUBOOT_ENCRYPTION_KEY CM…54 …message(FATAL_ERROR "Hex file output must be enabled to use mcuboot. Set MBED_OUTPUT_EXT to empty…58 …message(FATAL_ERROR "You must set the project version to sign images by passing a version number i…95 …--key ${MCUBOOT_SIGNING_KEY_ABSPATH} # this specifies the file containing the keys used to sign/ve…[all …]
40 unsigned int _copy(uint8_t *to, unsigned int to_len, in _copy() argument44 (void)memcpy(to, from, from_len); in _copy()51 void _set(void *to, uint8_t val, unsigned int len) in _set() argument53 (void)memset(to, val, len); in _set()
19 MCUboot itself to load update images into flash over a UART.33 The serial device to use will be fist selected via chosen36 the "zephyr,uart-mcumgr" points to the same device as45 precedence and redirects serial recovery to uart pointed by51 bool "Allow to select image number for DFU"57 The mapping of image number to partition is as follows:74 memory access when data is written to a device with memory alignment75 requirements. Set to 0 to disable.82 fragments of 128-bytes, this should not need to be changed unless a97 be equal to the maximum line length, BOOT_MAX_LINE_INPUT_LEN times[all …]
12 # Hidden option to mark a project as MCUboot104 When possible to map storage device, at least for read operations,105 to address space or RAM area, enabling this option allows hash106 calculation functions to directly access the storage through that address111 SHA requires image to be decrypted first, which is done in RAM.225 Image to be verified needs to be accessible through memory address269 This option instructs MCUboot to perform a clean-up of a set of270 architecture core HW registers before jumping to the application271 firmware. The clean-up sets these registers to their warm-reset274 This option is enabled by default to prevent possible problems when[all …]
5 Implements simple Blinky LED CM4 application to demonstrate MCUboot Application operation in terms …12 * Prints debug info and version of itself to terminal at 115200 baud.23 Since this application is created to demonstrate MCUboot library features and not as reference exam…25 …to configure serial port for debug prints. These pins are the most commonly used for serial port c…26 …to define user connection LED. This pin is the most commonly used for USER_LED connection among av…36 * `BlinkyApp.mk` to `-DUSER_APP_START=0x10018000`45 …uild regular HEX file of a BlinkyApp for BOOT slot. Substitute `PLATFORM=` to a paltform name you …66 `BlinkyApp` can be built to use in multi-image bootloader configuration.68 To get appropriate artifacts to use with multi image MCUBootApp, makefile flag `HEADER_OFFSET=` can…84 **How to build upgrade image for external memory:**[all …]
1 ### Port of MCUboot library to be used with Cypress targets31 …ry, secondary slot and bootloader app sizes are appropriate and correspond to flash area size defi…38 …celeration of cryptography shortens boot time more then 4 times, comparing to software implementat…40 To enable hardware acceleration in `MCUBootApp` pass flag `USE_CRYPTO_HW=1` to `make` while build.44 ### How to modify memory map48 Navigate to `sysflash.h` and modify the flash area(s) / slots sizes to meet your needs.52 Navigate to `sysflash.h`, uncomment `CY_FLASH_MAP_EXT_DESC` definition.55 …e sure you have updated `MCUBOOT_MAX_IMG_SECTORS` appropriatery with sector size assumed to be 512.57 **How to override the flash map values during build process:**59 Navigate to MCUBootApp.mk, find section `DEFINES_APP +=`[all …]
10 Using external memory for secondary slot allows to nearly double the size of Boot Image.21 This corresponds to PSoC6's SMIF (Serial Memory InterFace) IP block mapping.22 * The slot size for upgrade slot is even (or smaller) to erase size (0x40000) of given memory modul…53 …ry, secondary slot and bootloader app sizes are appropriate and correspond to flash area size defi…55 **Note 2**: make sure secondary slot start address is aligned (or smaller) to erase size (0x40000 -…57 MCUBootApp's `main.c` contains the call to Init-SFDP API which performs required GPIO configuration…59 After that MCUBootApp is ready to accept upgrade image from external memory module.63 **How to enable external memory support:**65 1. Pass `USE_EXTERNAL_FLASH=1` flag to `make` command when building MCUBootApp.66 2. Navigate to `cy_flash_map.c` and check if secondary slot start address and size meet the applica…[all …]
3 In order to successfully deploy an application using MCUboot, it is4 necessary to build at least one other binary: the application itself.5 It is beyond the scope of this documentation to describe what an6 application is able to do, however a working example is certainly10 details on how to build and test this application.
6 Permission is hereby granted, free of charge, to any person obtaining a copy7 of this software and associated documentation files (the "Software"), to deal9 to use, copy, modify, merge, publish, distribute, sublicense, and/or sell10 copies of the Software, and to permit persons to whom the Software is11 furnished to do so, subject to the following conditions:
15 - Strictly internal changes to the code that won't be visible to users23 entry. (A script will be developed to collect these, ordered by when24 the commits were added to the tree.)26 Choose a filename that is related to what this change does. The names27 are not used for anything in particular, but to keep the files
1 - Added optional write block size checking to ensure expected3 - Added optional erase size checking to ensure expected sizes5 - Added debug logs for zephyr to output discrepencies in erase
2 correctly initialised to default values which could cause3 some commands to do unexpected operations
18 "control" means (i) the power, direct or indirect, to cause the27 including but not limited to software source code, documentation32 not limited to compiled object code, generated documentation,33 and conversions to other media types.37 copyright notice that is included in or attached to the work45 separable from, or merely link (or bind by name) to the interfaces of,50 to that Work or Derivative Works thereof, that is intentionally51 submitted to Licensor for inclusion in the Work by the copyright owner52 or by an individual or Legal Entity authorized to submit on behalf of55 to the Licensor or its representatives, including but not limited to[all …]
5 Clone [nrfxlib](https://github.com/NordicPlayground/nrfxlib) next to the MCUboot root folder. So th…10 Since it defaults to tinycrypt you'll have to go into `menuconfig` and change the implementation se…
