Home
last modified time | relevance | path

Searched refs:a (Results 1 – 25 of 82) sorted by relevance

1234

/mcuboot-latest/ext/tinycrypt/lib/source/
Dsha256.c157 static inline unsigned int ROTR(unsigned int a, unsigned int n) in ROTR() argument
159 return (((a) >> n) | ((a) << (32 - n))); in ROTR()
162 #define Sigma0(a)(ROTR((a), 2) ^ ROTR((a), 13) ^ ROTR((a), 22)) argument
163 #define Sigma1(a)(ROTR((a), 6) ^ ROTR((a), 11) ^ ROTR((a), 25)) argument
164 #define sigma0(a)(ROTR((a), 7) ^ ROTR((a), 18) ^ ((a) >> 3)) argument
165 #define sigma1(a)(ROTR((a), 17) ^ ROTR((a), 19) ^ ((a) >> 10)) argument
167 #define Ch(a, b, c)(((a) & (b)) ^ ((~(a)) & (c))) argument
168 #define Maj(a, b, c)(((a) & (b)) ^ ((a) & (c)) ^ ((b) & (c))) argument
183 unsigned int a, b, c, d, e, f, g, h; in compress() local
190 a = iv[0]; b = iv[1]; c = iv[2]; d = iv[3]; in compress()
[all …]
Daes_decrypt.c67 #define mult8(a)(_double_byte(_double_byte(_double_byte(a)))) argument
68 #define mult9(a)(mult8(a)^(a)) argument
69 #define multb(a)(mult8(a)^_double_byte(a)^(a)) argument
70 #define multd(a)(mult8(a)^_double_byte(_double_byte(a))^(a)) argument
71 #define multe(a)(mult8(a)^_double_byte(_double_byte(a))^_double_byte(a)) argument
Dutils.c59 uint8_t _double_byte(uint8_t a) in _double_byte() argument
61 return ((a<<1) ^ ((a>>7) * MASK_TWENTY_SEVEN)); in _double_byte()
64 int _compare(const uint8_t *a, const uint8_t *b, size_t size) in _compare() argument
66 const uint8_t *tempa = a; in _compare()
Daes_encrypt.c62 static inline unsigned int rotword(unsigned int a) in rotword() argument
64 return (((a) >> 24)|((a) << 8)); in rotword()
67 #define subbyte(a, o)(sbox[((a) >> (o))&0xff] << (o)) argument
68 #define subword(a)(subbyte(a, 24)|subbyte(a, 16)|subbyte(a, 8)|subbyte(a, 0)) argument
122 #define triple(a)(_double_byte(a)^(a)) argument
/mcuboot-latest/ext/tinycrypt-sha512/lib/source/
Dsha512.c170 static inline uint64_t ROTR(uint64_t a, uint64_t n) in ROTR() argument
172 return (((a) >> n) | ((a) << (64 - n))); in ROTR()
175 #define Sigma0(a)(ROTR((a), 28) ^ ROTR((a), 34) ^ ROTR((a), 39)) argument
176 #define Sigma1(a)(ROTR((a), 14) ^ ROTR((a), 18) ^ ROTR((a), 41)) argument
177 #define sigma0(a)(ROTR((a), 1) ^ ROTR((a), 8) ^ ((a) >> 7)) argument
178 #define sigma1(a)(ROTR((a), 19) ^ ROTR((a), 61) ^ ((a) >> 6)) argument
180 #define Ch(a, b, c)(((a) & (b)) ^ ((~(a)) & (c))) argument
181 #define Maj(a, b, c)(((a) & (b)) ^ ((a) & (c)) ^ ((b) & (c))) argument
200 uint64_t a, b, c, d, e, f, g, h; in compress() local
207 a = iv[0]; b = iv[1]; c = iv[2]; d = iv[3]; in compress()
[all …]
/mcuboot-latest/docs/
Drelease.md8 follow a `MAJOR.MINOR.PATCH` format with the following guidelines on
12 2. MINOR version when new functionalities were added in a
23 Before making a release, update the `docs/release-notes.md` file
24 to describe the release. This should be a high-level description of
25 the changes, not a list of the git commits.
36 release candidate (a.b.c-rc1, followed by a.b.c-rc2 and the subsequent
37 release candidates, followed by the official a.b.c release). The intent
62 On Mynewt, `newt` always fetches a versioned MCUboot release, so after
70 There is a version file used by Zephyr builds to indicate the version
79 To make a release, make sure your local repo is on the tip version by
[all …]
DSubmittingPatches.md8 Each commit has to have, in the commit message, a "Signed-off-by" line
10 must add this line at the end of the commit text, separated by a blank
11 line. You can also add a line linking the commit to a specific GitHub
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…
36 changes must include a release note snippet in the pull request.
37 This can be either a separate commit, or as part of a single commit
39 release note snippet should be a separate commit, and a pull request
40 that is a single commit can include the release note snippet in that
66 By making a contribution to this project, I certify that:
[all …]
Dreadme-nuttx.md5 The NuttX port of MCUboot secure boot library expects that the platform provides a Flash storage wi…
25 …a firmware update agent, which is an important component of a secure firmware update subsystem. Th…
27 …a webserver, installing it and triggering the firmware update process for the next boot after a sy…
29 ## Using MCUboot on NuttX as a secure boot solution
31 …a secure bootloader application requiring minimal platform-specific implementation. The logical im…
39 The implementation of `<flash_map_backend/flash_map_backend.h>` expects that the MTD driver for a g…
45 … MTD. So The NuttX implementation of `flash_area_align()` is able to return a fixed value of 1 byt…
Dreadme-mbed.md7 Note: The following is a general overview. It does not cover MCUboot or Mbed OS basics.
9 See https://github.com/AGlass0fMilk/mbed-mcuboot-demo as a detailed example.
21 ### Providing a secondary slot
35 …ild a bootloader based on MCUboot, make sure `"mcuboot.bootloader-build"` is `true` (already the d…
37 ### Building a user application
39 …a user application, set `"mcuboot.bootloader-build"` to `false` so MCUboot is built as a _library …
Dreadme-zephyr.md4 acquired the ability to be used as a bootloader for Zephyr as well.
21 needed (see end of this help file for details on creating a scratch partition
33 The flash partitions are typically defined in the Zephyr boards folder, in a
51 Zephyr's point of view. There is a bit of configuration that needs to
54 guidance. It is important to select a signature algorithm, and decide
57 To build MCUboot, create a build directory in boot/zephyr, and build
70 MCUboot on a per-SoC family basis.
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
92 application; see samples/zephyr/README.md for a tutorial.
[all …]
DPORTING.md4 `MCUboot` to a new target `OS`.
8 * `MCUboot` requires a configuration file, which can be included as
12 * `MCUboot` requires that the target provides a `flash` API with ability to
15 * `MCUboot` doesn't bundle a cryptographic library, which means the target
24 From the perspective of the target OS, the bootloader can be seen as a library,
25 so an entry point must be provided. This is likely a typical `app` for the
32 This function is located at `boot/bootutil/loader.c` and receives a `struct
55 You must provide a file, mcuboot_config/mcuboot_config.h. This is
60 See the file samples/mcuboot_config/mcuboot_config.template.h for a
61 starting point and more information. This is a good place to convert
[all …]
Dtestplan-zephyr.md21 Begin by doing a full erase, and programming the bootloader itself:
26 After it resets, look for "main: Starting bootloader", a few debug
42 This should print a message: `boot_swap_type: Swap type: test`, and
49 And you should see a revert and "hello1" running.
53 Repeat this, to make sure we can mark the image as OK, and that a
61 $ pyocd flash -a 0x7ffe8 image_ok.bin
Dreadme-riot.md4 acquired the ability to be used as a bootloader for RIOT as well.
9 In this first version, a prebuilt Mynewt binary is downloaded at
11 not a signature check. In order to configure the bootloader for
23 with a valid formatted value. The format is `major.minor.patch+other`
27 The goal is to produce an ELF file which is linked to be flashed at a
37 If no key is provided, a new key will be automatically generated. The
Decdsa.md3 When the ECDSA SECP256R1 (EC256) signature support was added to MCUboot, a
5 always a fixed length. Unfortunately, this padding was done in a way
11 - Use a reversible padding scheme. This solution requires
28 This document proposes a multi-stage approach to give a transition
31 1. Add a `--no-pad-sig` argument to the sign command in
57 behavior, but will not specify a specific version of imgtool.
80 signature will vary by a couple of bytes, depending on whether one or
86 signature ended in a zero, MCUboot would remove too many bytes and render the
Drelease-notes.md22 a given board.
40 allows for a single application slot and firmware loader image in
45 - Zephyr: Add USB CDC serial recovery check that now causes a build
48 - Zephyr: Add USB CDC serial recovery check that now causes a build
53 improves support a bit for some configurations of external flash.
54 - fix a memory leak in the HKDF implementation.
55 - Zephyr: Added a MCUboot banner which displays the version of
62 Note that this release, 2.0.0 is a new major number, and contains a small API
94 - imgtool's getpub can print the output to a file
98 output was sent, this would lead to a divergence of commands
[all …]
/mcuboot-latest/ext/tinycrypt/tests/
Dtest_cbc_mode.c106 struct tc_aes_key_sched_struct a; in test_1_and_2() local
114 (void)tc_aes128_set_encrypt_key(&a, key); in test_1_and_2()
120 plaintext, sizeof(plaintext), iv_buffer, &a) == 0) { in test_1_and_2()
132 (void)tc_aes128_set_decrypt_key(&a, key); in test_1_and_2()
138 encrypted, &a) == 0) { in test_1_and_2()
/mcuboot-latest/samples/zephyr/hello-world/
DREADME.rst1 This is a "Hello world" skeleton application which can be used as a
5 loadable by mcuboot in addition to a basic Zephyr hello world
DCMakeLists.txt8 # This provides a basic application structure suitable for loading by
9 # mcuboot, which is easy to customize on a per-board basis. It can be
10 # used as a starting point for new applications.
/mcuboot-latest/ext/tinycrypt/lib/
DMakefile29 all: libtinycrypt.a
31 libtinycrypt.a: $(OBJS)
37 -$(RM) *.exe $(OBJS) $(DEPS) *~ libtinycrypt.a
/mcuboot-latest/docs/release-notes.d/
Dswap-using-offset.md1 - Added a new swap using offset algorithm which is set with
5 the update slot, which offers a faster update process and
6 requires a smaller swap status area
D00readme.md6 Generally a release note entry should be created for changes that:
21 directory and have a name of `*.md`. They will be included in the
22 `release-notes.md` file, and should be formatted as a Markdown list
26 Choose a filename that is related to what this change does. The names
28 distinct so that there isn't a concern with merge conflicts as
Dfix-stuck-revert.md1 - Fixed issue for swap using move whereby a device could get
2 stuck in a revert loop despite there being no image in the
/mcuboot-latest/ext/tinycrypt/lib/include/tinycrypt/
Dutils.h79 uint8_t _double_byte(uint8_t a);
89 int _compare(const uint8_t *a, const uint8_t *b, size_t size);
/mcuboot-latest/ext/fiat/
DREADME.md9 To generate the field arithmetic procedures in `curve25519.c` from a fiat-crypto
16 unsigned integers with a single carry chain and two wraparound carries" where
26 To generate the field arithmetic procedures in `p256.c` from a fiat-crypto
33 untrusted. There is currently a known issue where `fesub.c` for p256 does not
34 manage to complete the build (specialization) within a week on Coq 8.7.0.
43 contains an overview of the implementation templates followed by a tour of the
/mcuboot-latest/samples/runtime-source/zephyr/
DREADME.md3 This sample demonstrates how to use a non flash storage to retrieve the image
4 being booted. It was tested on a FRDM K64F. Both slots are used to store two
5 different images. The image to be booted is selected based on a button press.
53 Open a serial terminal to see the output and reset the board. It shall boot the

1234