Home
last modified time | relevance | path

Searched +full:- +full:m (Results 1 – 25 of 1009) sorted by relevance

12345678910>>...41

/Zephyr-Core-3.4.0/samples/subsys/rtio/sensor_batch_processing/src/
Dmain.c4 * SPDX-License-Identifier: Apache-2.0
14 #define M (N/2) macro
21 #define PROCESS_TIME ((M - 1) * SAMPLE_PERIOD)
28 struct rtio_iodev *iodev = vnd_sensor->data; in main()
38 int m = 0; in main() local
39 uint8_t *userdata[M] = {0}; in main()
40 uint32_t data_len[M] = {0}; in main()
42 LOG_INF("Submitting %d read requests", M); in main()
43 rtio_submit(&ez_io, M); in main()
49 while (m < M) { in main()
[all …]
/Zephyr-Core-3.4.0/modules/trusted-firmware-m/
DKconfig.tfm.partitions1 # Configuration for the partitions in the TF-M Module
4 # SPDX-License-Identifier: Apache-2.0
15 Setting this option will cause '-DTFM_PARTITION_PROTECTED_STORAGE'
16 to be passed to the TF-M build system. Look at 'config_default.cmake'
17 in the trusted-firmware-m repository for details regarding this
19 options are handled by the build system in the trusted-firmware-m
26 Setting this option will cause '-DTFM_PARTITION_INTERNAL_TRUSTED_STORAGE'
27 to be passed to the TF-M build system. Look at 'config_default.cmake'
28 in the trusted-firmware-m repository for details regarding this
30 options are handled by the build system in the trusted-firmware-m
[all …]
DKconfig.tfm1 # Configuration for the TF-M Module
5 # SPDX-License-Identifier: Apache-2.0
29 bool "Build with TF-M as the Secure Execution Environment"
38 additionally generate a TF-M image for the Secure Execution
40 itself is to be executed in the Non-Secure Processing Environment.
42 ensures that the Zephyr image is built as a Non-Secure image. Both
43 TF-M and Zephyr images, as well as the veneer object file that links
58 default "${ZEPHYR_TRUSTED_FIRMWARE_M_MODULE_DIR}/bl2/ext/mcuboot/root-RSA-3072.pem"
65 string "Path to private key used to sign non-secure firmware images."
67 default "${ZEPHYR_TRUSTED_FIRMWARE_M_MODULE_DIR}/bl2/ext/mcuboot/root-RSA-3072_1.pem"
[all …]
/Zephyr-Core-3.4.0/samples/tfm_integration/
Dtfm_integration.rst1 .. _tfm_integration-samples:
3 TF-M Integration Samples
12 Trusted Firmware-M (TF-M)
17 These TF-M integration examples can be used with a supported Armv8-M board, and
18 demonstrate how the TF-M APIs can be used with Zephyr.
21 secure processing environment (S), with Zephyr running in the non-secure
25 built, in addition to the TF-M S and Zephyr NS binary images. The S and NS
32 What is Trusted Firmware-M (TF-M)?
35 Trusted Firmware-M (TF-M) is the reference implementation of `Platform Security
36 Architecture (PSA) <https://pages.arm.com/psa-resources.html>`_.
[all …]
/Zephyr-Core-3.4.0/doc/hardware/pinctrl/images/
Dhw-dist-control.svg1 <?xml version="1.0" encoding="UTF-8"?>
2 <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
3 …x="0 0 18000 8500" preserveAspectRatio="xMidYMid" fill-rule="evenodd" stroke-width="28.222" stroke…
13 <font id="EmbeddedFont_1" horiz-adv-x="2048">
14 …<font-face font-family="LM Roman 12 embedded" units-per-em="2048" font-weight="normal" font-style=…
15 <missing-glyph horiz-adv-x="2048" d="M 0,0 L 2047,0 2047,2047 0,2047 0,0 Z"/>
16 …-adv-x="663" d="M 668,254 L 668,371 623,371 623,258 C 623,111 563,25 483,25 344,25 344,215 344,250…
17 …<glyph unicode="r" horiz-adv-x="689" d="M 723,784 C 723,846 668,903 580,903 406,903 346,715 334,67…
18 …code="o" horiz-adv-x="901" d="M 940,438 C 940,702 739,913 502,913 256,913 61,696 61,438 61,176 266…
19 …<glyph unicode="n" horiz-adv-x="1033" d="M 1067,0 L 1067,59 C 965,59 913,59 911,121 L 911,498 C 91…
[all …]
Dhw-cent-control.svg1 <?xml version="1.0" encoding="UTF-8"?>
2 <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd">
3 …x="0 0 15000 8000" preserveAspectRatio="xMidYMid" fill-rule="evenodd" stroke-width="28.222" stroke…
13 <font id="EmbeddedFont_1" horiz-adv-x="2048">
14 …<font-face font-family="LM Roman 12 embedded" units-per-em="2048" font-weight="normal" font-style=…
15 <missing-glyph horiz-adv-x="2048" d="M 0,0 L 2047,0 2047,2047 0,2047 0,0 Z"/>
16 …-adv-x="1033" d="M 1067,0 L 1067,59 C 928,59 911,74 911,174 L 911,903 623,881 623,821 C 762,821 77…
17 …-adv-x="663" d="M 668,254 L 668,371 623,371 623,258 C 623,111 563,25 483,25 344,25 344,215 344,250…
18 …<glyph unicode="r" horiz-adv-x="689" d="M 723,784 C 723,846 668,903 580,903 406,903 346,715 334,67…
19 …code="o" horiz-adv-x="901" d="M 940,438 C 940,702 739,913 502,913 256,913 61,696 61,438 61,176 266…
[all …]
/Zephyr-Core-3.4.0/subsys/bluetooth/controller/ll_sw/
Dlll_chan.c2 * Copyright (c) 2018-2021 Nordic Semiconductor ASA
4 * SPDX-License-Identifier: Apache-2.0
137 /* Sub-expression to get natural number (N - 2d + 1) to be used in the in lll_chan_iso_subevent()
141 x = (chan_count + 1) - (d << 1); in lll_chan_iso_subevent()
165 while (byte_count--) { in chan_sel_remap()
171 while (bit_count--) { in chan_sel_remap()
176 chan_index--; in chan_sel_remap()
257 while (octet_count--) { in chan_sel_remap_index()
263 while (bit_count--) { in chan_sel_remap_index()
267 chan_index--; in chan_sel_remap_index()
[all …]
/Zephyr-Core-3.4.0/arch/arm/core/aarch32/cortex_m/
DKconfig1 # ARM Cortex-M platform configuration options
3 # Copyright (c) 2014-2015 Wind River Systems, Inc.
4 # SPDX-License-Identifier: Apache-2.0
10 # if one select a different ARM Cortex Family (Cortex-A or Cortex-R)
17 This option signifies the use of a Cortex-M0 CPU
24 This option signifies the use of a Cortex-M0+ CPU
31 This option signifies the use of a Cortex-M1 CPU
38 This option signifies the use of a Cortex-M3 CPU
46 This option signifies the use of a Cortex-M4 CPU
54 This option signifies the use of a Cortex-M23 CPU
[all …]
/Zephyr-Core-3.4.0/lib/posix/
Dpthread_mutex.c4 * SPDX-License-Identifier: Apache-2.0
39 static inline size_t posix_mutex_to_offset(struct k_mutex *m) in posix_mutex_to_offset() argument
41 return m - posix_mutex_pool; in posix_mutex_to_offset()
76 struct k_mutex *m; in to_posix_mutex() local
92 m = &posix_mutex_pool[bit]; in to_posix_mutex()
94 err = k_mutex_init(m); in to_posix_mutex()
97 return m; in to_posix_mutex()
105 struct k_mutex *m; in acquire_mutex() local
108 m = to_posix_mutex(mu); in acquire_mutex()
109 if (m == NULL) { in acquire_mutex()
[all …]
/Zephyr-Core-3.4.0/doc/services/tfm/
Dintegration.rst1 Trusted Firmware-M Integration
4 The Trusted Firmware-M (TF-M) section contains information about the
5 integration between TF-M and Zephyr RTOS. Use this information to help
6 understand how to integrate TF-M with Zephyr for Cortex-M platforms and make
7 use of its secure run-time services in Zephyr applications.
12 TF-M will be built for the secure processing environment along with Zephyr if
16 and all config flags required for TF-M should be set in a board variant with
22 `modules/trusted-firmware-m/Kconfig.tfm <https://github.com/zephyrproject-rtos/zephyr/blob/main/mod…
23 to the board name that TF-M expects for this target, so that it knows which
29 The ``mps2_an521`` target is a dual-core Arm Cortex-M33 evaluation board that,
[all …]
Dtestsuites.rst4 TF-M includes two sets of test suites:
6 * tf-m-tests - Standard TF-M specific regression tests
7 * psa-arch-tests - Test suites for specific PSA APIs (secure storage, etc.)
12 TF-M Regression Tests
20 application (TF-M).
27 being followed by the secure application, TF-M being an implementation of
37 your specific board, RTOS (Zephyr here), and PSA implementation (TF-M in this
41 changes to TF-M, such as enabling a new TF-M board target, or making changes
42 to the core TF-M module(s). They should generally be run as a coherence check
Dbuild.rst3 TF-M Build System
6 When building a valid ``_ns`` board target, TF-M will be built in the
7 background, and linked with the Zephyr non-secure application. No knowledge
8 of TF-M's build system is required in most cases, and the following will
9 build a TF-M and Zephyr image pair, and run it in qemu with no additional
12 .. code-block:: bash
14 $ west build -p auto -b mps2_an521_ns samples/tfm_integration/psa_protected_storage/ -t run
18 deal with signing the secure and non-secure images before deploying them.
20 Images Created by the TF-M Build
23 The TF-M build system creates the following executable files:
[all …]
Doverview.rst1 Trusted Firmware-M Overview
4 `Trusted Firmware-M (TF-M) <https://tf-m-user-guide.trustedfirmware.org/>`__
6 `IoT Security Framework <https://www.psacertified.org/what-is-psa-certified/>`__.
10 Zephyr RTOS has been PSA Certified since Zephyr 2.0.0 with TF-M 1.0, and
11 is currently integrated with TF-M 1.4.1.
13 What Does TF-M Offer?
16 Through a set of secure services and by design, TF-M provides:
18 * Isolation of secure and non-secure resources
19 * Embedded-appropriate crypto
22 * Protected off-chip data storage and retrieval
[all …]
/Zephyr-Core-3.4.0/subsys/bluetooth/controller/ll_sw/nordic/hal/nrf5/
Dticker.c2 * Copyright (c) 2016-2018 Nordic Semiconductor ASA
5 * SPDX-License-Identifier: Apache-2.0
61 static struct mayfly m = {0, 0, &link, NULL, in hal_ticker_instance0_sched() local
64 m.param = instance; in hal_ticker_instance0_sched()
70 &m); in hal_ticker_instance0_sched()
85 static struct mayfly m = {0, 0, &link, NULL, in hal_ticker_instance0_sched() local
88 m.param = instance; in hal_ticker_instance0_sched()
93 &m); in hal_ticker_instance0_sched()
108 static struct mayfly m = {0, 0, &link, NULL, in hal_ticker_instance0_sched() local
111 m.param = instance; in hal_ticker_instance0_sched()
[all …]
/Zephyr-Core-3.4.0/subsys/bluetooth/controller/ll_sw/openisa/hal/RV32M1/
Dticker.c2 * Copyright (c) 2016-2018 Nordic Semiconductor ASA
5 * SPDX-License-Identifier: Apache-2.0
63 static struct mayfly m = {0, 0, &link, NULL, in hal_ticker_instance0_sched() local
66 m.param = instance; in hal_ticker_instance0_sched()
72 &m); in hal_ticker_instance0_sched()
88 static struct mayfly m = {0, 0, &link, NULL, in hal_ticker_instance0_sched() local
91 m.param = instance; in hal_ticker_instance0_sched()
96 &m); in hal_ticker_instance0_sched()
111 static struct mayfly m = {0, 0, &link, NULL, in hal_ticker_instance0_sched() local
114 m.param = instance; in hal_ticker_instance0_sched()
[all …]
/Zephyr-Core-3.4.0/subsys/bluetooth/crypto/
Dbt_crypto.c2 * SPDX-License-Identifier: Apache-2.0
27 return -EIO; in bt_crypto_aes_cmac()
31 return -EIO; in bt_crypto_aes_cmac()
35 return -EIO; in bt_crypto_aes_cmac()
44 uint8_t m[65]; in bt_crypto_f4() local
52 * U, V and Z are concatenated and used as input m to the function in bt_crypto_f4()
53 * AES-CMAC and X is used as the key k. in bt_crypto_f4()
60 sys_memcpy_swap(m, u, 32); in bt_crypto_f4()
61 sys_memcpy_swap(m + 32, v, 32); in bt_crypto_f4()
62 m[64] = z; in bt_crypto_f4()
[all …]
/Zephyr-Core-3.4.0/scripts/utils/
Dmigrate_sys_init.py11 -p path/to/zephyr-based-project
14 SPDX-License-Identifier: Apache-2.0
32 m = re.match(r"^SYS_INIT\(([A-Za-z0-9_]+),.*", line)
33 if m:
34 sys_inits.append(m.group(1))
37 m = re.match(r"^SYS_INIT_NAMED\([A-Za-z0-9_]+,\s?([A-Za-z0-9_]+).*", line)
38 if m:
39 sys_inits.append(m.group(1))
50 m = re.match(
56 if m:
[all …]
/Zephyr-Core-3.4.0/samples/sensor/accel_polling/
DREADME.rst3 Generic 3-Axis accelerometer polling sample
9 This sample application demonstrates how to use 3-Axis accelerometers.
14 This sample supports up to 10 3-Axis accelerometers. Each accelerometer needs
17 .. code-block:: devicetree
27 .. zephyr-app-commands::
28 :zephyr-app: samples/sensor/accel_polling
36 .. code-block:: console
38 lis2dh@19 [m/s^2]: ( -6.013728, -3.064320, 7.277760)
39 lis2dh@19 [m/s^2]: ( -6.128640, -3.026016, 7.201152)
40 lis2dh@19 [m/s^2]: ( -6.090336, -3.064320, 7.162848)
[all …]
/Zephyr-Core-3.4.0/tests/crypto/tinycrypt/src/
Dsha256.c1 /* test_sha256.c - TinyCrypt implementation of some SHA-256 tests */
9 * - Redistributions of source code must retain the above copyright notice,
12 * - Redistributions in binary form must reproduce the above copyright
16 * - Neither the name of Intel Corporation nor the names of its contributors
37 * - NIST SHA256 test vectors
66 const char *m = "abc"; in ZTEST() local
71 tc_sha256_update(&s, (const uint8_t *)m, strlen(m)); in ZTEST()
95 const char *m = in ZTEST() local
101 tc_sha256_update(&s, (const uint8_t *)m, strlen(m)); in ZTEST()
123 const uint8_t m[1] = { 0xbd }; in ZTEST() local
[all …]
/Zephyr-Core-3.4.0/samples/kernel/metairq_dispatch/src/
Dmain.c4 * SPDX-License-Identifier: Apache-2.0
59 struct msg m; in metairq_fn() local
61 message_dev_fetch(&m); in metairq_fn()
62 m.metairq_latency = k_cycle_get_32() - m.timestamp; in metairq_fn()
64 int ret = k_msgq_put(&threads[m.target].msgq, &m, K_NO_WAIT); in metairq_fn()
68 m.target, m.seq); in metairq_fn()
103 int64_t d = (int32_t) (array[i] - *mean); in calc_stats()
111 static void record_latencies(struct msg *m, uint32_t latency) in record_latencies() argument
114 * metairq latency for the very first event of 7-8us. Maybe in record_latencies()
117 if (IS_ENABLED(CONFIG_QEMU_TARGET) && m->seq == 0) { in record_latencies()
[all …]
/Zephyr-Core-3.4.0/subsys/bluetooth/controller/util/
Dmayfly.c2 * Copyright (c) 2016-2017 Nordic Semiconductor ASA
5 * SPDX-License-Identifier: Apache-2.0
35 while (callee_id--) { in mayfly_init()
39 while (caller_id--) { in mayfly_init()
71 struct mayfly *m) in mayfly_enqueue() argument
82 ack = m->_ack; in mayfly_enqueue()
85 state = (m->_req - ack) & 0x03; in mayfly_enqueue()
90 m->_req = ack + 1; in mayfly_enqueue()
100 m->_req = ack + 2; in mayfly_enqueue()
106 m->fp(m->param); in mayfly_enqueue()
[all …]
/Zephyr-Core-3.4.0/samples/tfm_integration/psa_crypto/boards/
Dnrf9160dk_nrf9160_ns.overlay4 * SPDX-License-Identifier: Apache-2.0
8 * for the Secure (TF-M) firmware for the configuration that is
12 /* Increase the size of the Secure Firmware (TF-M).
14 * since TF-M region definitions are configured
15 * statically in the TF-M project.
21 /* Decrease the size of the Non-Secure Firmware (Zephyr),
23 * TF-M.
25 /delete-node/ &sram0_ns;
27 reserved-memory {
34 /* Disable UART1, because it is used by default in TF-M */
/Zephyr-Core-3.4.0/samples/tfm_integration/tfm_ipc/boards/
Dnrf9160dk_nrf9160_ns.overlay4 * SPDX-License-Identifier: Apache-2.0
8 * for the Secure (TF-M) firmware for the configuration that is
12 /* Increase the size of the Secure Firmware (TF-M).
14 * since TF-M region definitions are configured
15 * statically in the TF-M project.
21 /* Decrease the size of the Non-Secure Firmware (Zephyr),
23 * TF-M.
25 /delete-node/ &sram0_ns;
27 reserved-memory {
34 /* Disable UART1, because it is used by default in TF-M */
/Zephyr-Core-3.4.0/doc/hardware/peripherals/canbus/
Dtransceiver.svg1 <?xml version="1.0" encoding="UTF-8"?>
5 <symbol overflow="visible" id="glyph0-0">
8 <symbol overflow="visible" id="glyph0-1">
9 …M 4.28125 -3.375 C 4.28125 -3.453125 4.28125 -3.515625 4.203125 -3.515625 C 4.15625 -3.515625 4.14…
11 <symbol overflow="visible" id="glyph0-2">
12 …M 2.609375 -3.4375 C 2.578125 -3.53125 2.5625 -3.5625 2.4375 -3.5625 C 2.359375 -3.5625 2.3125 -3.…
14 <symbol overflow="visible" id="glyph0-3">
15 …M 1.546875 -3.34375 C 1.484375 -3.40625 1.484375 -3.40625 1.375 -3.40625 L 0.40625 -3.40625 L 0.40…
17 <symbol overflow="visible" id="glyph0-4">
18 …M 3.734375 -1.34375 L 3.53125 -1.34375 C 3.453125 -0.765625 3.328125 -0.21875 2.359375 -0.21875 L …
[all …]
/Zephyr-Core-3.4.0/tests/posix/common/src/
Dcond.c4 * SPDX-License-Identifier: Apache-2.0
19 pthread_cond_t m[CONFIG_MAX_PTHREAD_COND_COUNT + 1]; in ZTEST() local
22 zassert_ok(pthread_cond_init(&m[i], NULL), "failed to init cond %zu", i); in ZTEST()
27 zassert_not_equal(0, pthread_cond_init(&m[i], NULL), "should not have initialized cond %zu", in ZTEST()
30 for (; i > 0; --i) { in ZTEST()
31 zassert_ok(pthread_cond_destroy(&m[i - 1]), "failed to destroy cond %zu", i - 1); in ZTEST()
42 pthread_cond_t m; in ZTEST() local
45 zassert_ok(pthread_cond_init(&m, NULL), "failed to init cond %zu", i); in ZTEST()
46 zassert_ok(pthread_cond_destroy(&m), "failed to destroy cond %zu", i); in ZTEST()

12345678910>>...41