Home
last modified time | relevance | path

Searched refs:it (Results 1 – 25 of 40) sorted by relevance

12

/mcuboot-latest/boot/bootutil/src/
Dtlv.c39 bootutil_tlv_iter_begin(struct image_tlv_iter *it, const struct image_header *hdr, in bootutil_tlv_iter_begin() argument
45 if (it == NULL || hdr == NULL || fap == NULL) { in bootutil_tlv_iter_begin()
71 it->hdr = hdr; in bootutil_tlv_iter_begin()
72 it->fap = fap; in bootutil_tlv_iter_begin()
73 it->type = type; in bootutil_tlv_iter_begin()
74 it->prot = prot; in bootutil_tlv_iter_begin()
75 it->prot_end = off_ + it->hdr->ih_protect_tlv_size; in bootutil_tlv_iter_begin()
76 it->tlv_end = off_ + it->hdr->ih_protect_tlv_size + info.it_tlv_tot; in bootutil_tlv_iter_begin()
78 it->tlv_off = off_ + sizeof(info); in bootutil_tlv_iter_begin()
95 bootutil_tlv_iter_next(struct image_tlv_iter *it, uint32_t *off, uint16_t *len, in bootutil_tlv_iter_next() argument
[all …]
Dimage_validate.c310 struct image_tlv_iter it; in bootutil_get_img_security_cnt() local
327 rc = bootutil_tlv_iter_begin(&it, hdr, fap, IMAGE_TLV_SEC_CNT, true); in bootutil_get_img_security_cnt()
336 rc = bootutil_tlv_iter_next(&it, &off, &len, NULL); in bootutil_get_img_security_cnt()
408 struct image_tlv_iter it; in bootutil_img_validate() local
429 rc = bootutil_tlv_iter_begin(&it, hdr, fap, IMAGE_TLV_ANY, false); in bootutil_img_validate()
434 if (it.tlv_end > bootutil_max_image_size(fap)) { in bootutil_img_validate()
444 rc = bootutil_tlv_iter_next(&it, &off, &len, &type); in bootutil_img_validate()
457 if (!bootutil_tlv_iter_is_prot(&it, off)) { in bootutil_img_validate()
Dboot_record.c127 struct image_tlv_iter it; in boot_save_boot_status() local
143 rc = bootutil_tlv_iter_begin(&it, hdr, fap, IMAGE_TLV_ANY, false); in boot_save_boot_status()
152 rc = bootutil_tlv_iter_next(&it, &offset, &len, &type); in boot_save_boot_status()
Dencrypted.c641 struct image_tlv_iter it; in boot_enc_load() local
657 rc = bootutil_tlv_iter_begin(&it, hdr, fap, EXPECTED_ENC_TLV, false); in boot_enc_load()
662 rc = bootutil_tlv_iter_next(&it, &off, &len, NULL); in boot_enc_load()
/mcuboot-latest/ext/nrf/
DREADME.md5 …hub.com/NordicPlayground/nrfxlib) next to the MCUboot root folder. So that it's located `../nrfxli…
10 Since it defaults to tinycrypt you'll have to go into `menuconfig` and change the implementation se…
18 Build a hello world example in zephyr and sign it with imgtool.py with the `root-ec-p256.pem` and f…
/mcuboot-latest/boot/bootutil/include/bootutil/
Dimage.h212 int bootutil_tlv_iter_begin(struct image_tlv_iter *it,
216 int bootutil_tlv_iter_next(struct image_tlv_iter *it, uint32_t *off,
218 int bootutil_tlv_iter_is_prot(struct image_tlv_iter *it, uint32_t off);
/mcuboot-latest/samples/zephyr/bad-keys/
DREADME.md5 the demo keys's public keys in the bootloader should result in it not
/mcuboot-latest/docs/
Dreadme-nuttx.md25 …it to a firmware update agent, which is an important component of a secure firmware update subsyst…
27 … by downloading an application firmware image from a webserver, installing it and triggering the f…
31 …he MCUboot library. Once MCUboot validates the application firmware image, it delegates the loadin…
52 …it is safe to state that they are **not** multitasking-safe. NuttX implementation manages the MTD …
Dreadme-riot.md12 signature check it is necessary to re-compile it either with Mynewt
15 In the next version, it is planned to compile MCUboot using RIOT,
Dimgtool.md26 You can add the `-p` argument to `keygen`, which will cause it to
33 for testing. Since this private key is widely distributed, it should
45 output it as a C data structure. You can replace or insert this code
68 it from the image version.
79 --confirm When padding the image, mark it as confirmed
92 -L, --load-addr INTEGER Load address for image when it should run
104 flash device. For Zephyr, it will be configured as part of the build,
121 in the secondary slot will then cause the bootloader to upgrade to it.
DSubmittingPatches.md61 license document, but changing it is not allowed.
69 have the right to submit it under the open source license
82 it.
86 personal information I submit with it, including my sign-off) is
Dreadme-espressif.md70 eventually code revision may differ from what is currently expected, it is recommended using
111 toolchain, however it is recommended to actually create a CMake toolchain file and
112 pass it through `<CMAKE_TOOLCHAIN_FILE>` variable since it may require a distinct set of
137 so that esptool tries to automatically detect it.
174 Default slot0 size is `0x100000`, but it can change as per application flash partitions.
176 For Zephyr images, `--pad-header` is not needed as it already has the padding for MCUboot
207 Version number is added to the image when signing it with `imgtool` (`-v` parameter, e.g.
293 If signing a Zephyr image, the `--pad-header` is not needed, as it already have the padding for
413 1. On startup, since it is the first boot, the ROM bootloader will not verify the bootloader image
414 (the Secure Boot bit in the eFuse is disabled) yet, so it proceeds to execute it (our MCUboot
[all …]
Dreadme-zephyr.md28 so your SoC runs it out of reset. If there are multiple updateable images
52 be made before building it. Most of this can be done as documented in
58 it as usual:
90 a simple application with everything you need. You can try it on your
91 board and then just make a copy of it to get started on your own
96 provides additional details regarding the changes it makes to the image
103 In order to upgrade to an image (or even boot it, if
152 key. It is necessary to extract the public key and insert it into the
203 swap-using-scratch mode, the Kconfig value must be set when building it:
206 Note that it is possible for an application to get into a stuck state when
[all …]
DPORTING.md16 OS must already have it bundled. The supported libraries at the moment are
26 target OS, and it must call the following function to run the bootloader:
56 included by several files in the "library" portion of MCUboot; it
79 access contents of that object and never modifies it, instead it calls
174 …it is possible that MCUboot will open a flash area multiple times simultaneously (through nested c…
Dtestplan-zephyr.md26 After it resets, look for "main: Starting bootloader", a few debug
38 happen and sometimes it will not.
DGemfile4 # When you want to use a different version, change it below, save the
Drelease.md64 `repository.yml` in the root directory; it must be updated with the
87 easier to find, as each release has a commit associated with it, and
127 the next release version might still be different as it might be needed to do:
Decdsa.md37 accepted, but it is already the default.
44 3. An Mbed TLS implementation of EC256 can be added, but it will require
Dindex.md12 relies on hardware porting layers from the operating system it works with.
23 contributed by the community once it is good enough.
/mcuboot-latest/sim/
DREADME.rst11 The simulator is written in Rust_, and you will need to install it to
12 build it. The installation_ page describes this process. The
/mcuboot-latest/
D.travis.yml-disabled46 ## Corrupt image hash is not tested as it is in the unprotected TLV section
52 ## Max profile is not tested as it requires HW entropy source which is not
/mcuboot-latest/samples/zephyr/
DREADME.md3 In order to successfully deploy an application using MCUboot, it is
/mcuboot-latest/boot/zephyr/
DKconfig198 In case relative path is used, the build system assumes that it starts
250 It caches the result in the magic area, which makes it an unsecure
275 This is the most conservative swap mode but it can work even on
290 each sector X in the secondary slot, it is moved to index X in
302 without having to move/copy it into the primary slot. For this reason the
313 argument to the imgtool.py script which writes it to the image header.
321 default unless there is an error with it or the boot mode has been
350 bootloader considers the image faulty and erases it. After this it will
430 In case relative path is used, the build system assumes that it starts
456 memory usage; larger values allow it to support larger images.
[all …]
DKconfig.firmware_loader43 remain in bootloader firmware loader mode if it was.
/mcuboot-latest/ext/tinycrypt/documentation/
Dtinycrypt.rst95 that it is unnecessary to build and allocate object code for more primitives
158 bits). Note that if you need AES-256, it doesn't sound as though your
221 * Both non-empty payload and associated data (it encrypts and
224 * Non-empty payload and empty associated data (it encrypts and
227 * Non-empty associated data and empty payload (it degenerates to an
231 suggestions, such as: it is recommended for most applications to use a
232 mac size greater than 8. Besides, it is emphasized that the usage of the
259 primitives. With this list of primitives it becomes feasible to support a range

12