| /Zephyr-latest/doc/kernel/usermode/ |
| D | overview.rst | 9 User mode threads are considered to be untrusted by Zephyr and are therefore
10 isolated from other user mode threads and from the kernel. A flawed or
11 malicious user mode thread cannot leak or modify the private data/resources
13 control another user mode thread or the kernel.
15 Example use-cases of Zephyr's user mode features:
17 - The kernel can protect against many unintentional programming errors which
20 - The kernel can sandbox complex data parsers such as interpreters, network
21 protocols, and filesystems such that malicious third-party code or data
24 - The kernel can support the notion of multiple logical "applications", each
31 For threads running in a non-privileged CPU state (hereafter referred to as
[all …]
|
| D | mpu_userspace.rst | 11 A post-build script :ref:`gen_kobject_list.py` scans the generated
16 During the process of dropping a thread to user mode, the privileged stack
21 During system calls, the user mode thread's access to the system call and the
22 passed-in parameters are all validated. The user mode thread is then elevated
25 thread is set back to user mode and the stack is restored to the user stack.
|
| /Zephyr-latest/.github/ISSUE_TEMPLATE/ |
| D | 006_nomination.md | 1 ---
3 about: Nominate a GitHub user for additional rights on the Zephyr Project
8 ---
20 Use this template to nominate a GitHub user for the Contributor role with
21 Triage permission level, which allows the user to add reviewers to a pull
26 ## GitHub User
28 Provide the following information about the GitHub user:
36 Add links to 3-5 GitHub pull requests, in the Zephyr project, authored or
37 reviewed by the GitHub user that demonstrate the user's dedication to the
42 …//docs.github.com/en/organizations/managing-access-to-your-organizations-repositories/repository-r…
|
| /Zephyr-latest/tests/subsys/logging/log_core_additional/src/ |
| D | log_test_user.c | 4 * SPDX-License-Identifier: Apache-2.0
20 LOG_MODULE_REGISTER(user);
23 * Test cases in this file run in user space to improve test coverage
31 LOG_INF("log from user"); in ZTEST_USER()
32 LOG_INF("log from user %d", d); in ZTEST_USER()
40 /* test log_hexdump_from_user() from user space */
59 /* test log_generic() from user space */
69 /* test log_filter_set from user space */
75 /* test log_panic() from user space */
80 LOG_INF("log from user\n"); in ZTEST_USER()
[all …]
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | armfvp_user_networking_setup.rst | 3 Networking with Arm FVP User Mode
11 using Arm FVP user mode networking with Zephyr.
16 User mode networking emulates a built-in IP router and DHCP server, and routes
17 TCP and UDP traffic between the guest and host. It uses the user mode socket
27 More details about Arm FVP user mode networking can be obtained from here:
28 https://developer.arm.com/documentation/100964/latest/Introduction-to-Fast-Models/User-mode-network…
30 Using Arm FVP User Mode Networking with Zephyr
33 Arm FVP user mode networking can be enabled in any applications and it doesn't
36 See :zephyr:code-sample:`dhcpv4-client` sample application.
42 * User mode networking does not support forwarding UDP ports on the host to
|
| D | qemu_user_setup.rst | 3 Networking with QEMU User
27 More details about User Networking can be obtained from here:
33 In order to use SLIRP with Zephyr, the user has to set the Kconfig option to
34 enable User Networking.
36 .. code-block:: cfg
41 In the default configuration, Zephyr only enables User Networking, and does
46 In general, QEMU User Networking can take in a lot of arguments including,
50 * Information about network to use. This may be valuable if the user does
52 * Tell QEMU to start DHCP server at user-defined IP address.
57 offloads this to the user, and expects that they will provide arguments
[all …]
|
| /Zephyr-latest/scripts/release/ |
| D | bug_bash.py | 4 # SPDX-License-Identifier: Apache-2.0
6 """Query the Top-Ten Bug Bashers
8 This script will query the top-ten Bug Bashers in a specified date window.
11 ./scripts/bug-bash.py -t ~/.ghtoken -b 2021-07-26 -e 2021-08-07
12 GITHUB_TOKEN="..." ./scripts/bug-bash.py -b 2021-07-26 -e 2021-08-07
26 parser.add_argument('-a', '--all', dest='all',
28 parser.add_argument('-t', '--token', dest='tokenfile',
30 parser.add_argument('-s', '--start', dest='start', help='start date (YYYY-mm-dd)',
32 parser.add_argument('-e', '--end', dest='end', help='end date (YYYY-mm-dd)',
60 self._repo = gh.get_repo('zephyrproject-rtos/zephyr')
[all …]
|
| /Zephyr-latest/samples/userspace/syscall_perf/ |
| D | README.rst | 1 .. zephyr:code-sample:: syscall_perf
10 user thread has to go through a system call compared to a supervisor thread that
17 This application creates a supervisor and a user thread.
19 current thread. The user thread has to go through a system call.
28 .. code-block:: console
30 User thread: 18012 cycles 748 instructions
32 User thread: 20136 cycles 748 instructions
34 User thread: 18014 cycles 748 instructions
|
| /Zephyr-latest/subsys/bluetooth/host/ |
| D | scan.h | 2 * Copyright (c) 2017-2021 Nordic Semiconductor ASA
3 * Copyright (c) 2015-2016 Intel Corporation
5 * SPDX-License-Identifier: Apache-2.0
42 * not add/remove any user.
65 * when another user that demands higher duty-cycle is being added.
66 * It is not allowed to add a user that was already added.
72 * If flag is set to @ref BT_LE_SCAN_USER_NONE, no user is being added. Instead, the
78 * @param flag user requesting the scanner
81 * @retval -EALREADY if the user is already enabled
82 * @retval -EPERM if the explicit scanner is being enabled while the initiator is running
[all …]
|
| /Zephyr-latest/soc/nxp/imxrt/imxrt118x/ |
| D | Kconfig | 2 # SPDX-License-Identifier: Apache-2.0
43 and user program images and data. The boot ROM expects container data
46 # Note- This config present the offest between container header and user
48 # value. CONTAINER_USER_IMAGE_OFFSET = ROM_START_OFFSET - IMAGE_CONTAINER_OFFSET.
50 hex "The offset between container header and user image"
53 The offset between container and user image. IF change the user image
55 value, this will make ROM could get the user image start address.
|
| /Zephyr-latest/doc/kernel/services/other/ |
| D | float.rst | 11 based on ARM Cortex-M SoCs supporting the Floating Point Extension,
46 be used by any thread (initialization in skipped on ARM Cortex-M platforms and
60 the kernel supports one or more of the following thread sub-classes:
62 * non-user: A thread that cannot use any floating point registers
64 * FPU user: A thread that can use the standard floating point registers
66 * SSE user: A thread that can use both the standard floating point registers
72 context switches to ensure the computations performed by each FPU user
73 or SSE user are not impacted by the computations performed by the other users.
75 ARM Cortex-M architecture (with the Floating Point Extension)
76 -------------------------------------------------------------
[all …]
|
| /Zephyr-latest/doc/build/dts/ |
| D | zephyr-user-node.rst | 1 .. _dt-inferred-bindings:
2 .. _dt-zephyr-user:
4 The ``/zephyr,user`` node
7 Zephyr's devicetree scripts handle the ``/zephyr,user`` node as a special case:
14 This node is meant for sample code and user applications. It should not be
20 You can store numeric or array values in ``/zephyr,user`` if you want them to
25 .. code-block:: devicetree
28 zephyr,user {
40 .. code-block:: C
54 You can store :ref:`phandles <dt-phandles>` in ``/zephyr,user`` if you want to
[all …]
|
| /Zephyr-latest/soc/raspberrypi/rpi_pico/rp2040/ |
| D | Kconfig | 5 # SPDX-License-Identifier: Apache-2.0
31 by the board definition, not the user.
37 Should be selected by the board definition, not the user.
43 by the board definition, not the user.
49 by the board definition, not the user.
55 by the board definition, not the user.
|
| /Zephyr-latest/tests/kernel/threads/dynamic_thread_stack/ |
| D | testcase.yaml | 3 - kernel
4 - security
7 - qemu_x86
8 - qemu_x86/atom/nommu
9 - qemu_x86_64
10 - qemu_cortex_a53
11 - qemu_cortex_a53/qemu_cortex_a53/smp
12 - qemu_cortex_m3
13 - qemu_riscv32
14 - qemu_riscv32e
[all …]
|
| /Zephyr-latest/boards/panasonic/pan1783/doc/ |
| D | index.rst | 6 The PAN1783, PAN1783A and PAN1783A-PA Evaluation Boards (pan1783_evb,
8 PAN1783A and PAN1783A-PA Modules which are based on the nRF5340 chipset
11 More information about the PAN1783, PAN1783A, PAN1783A-PA Modules and
25 PAN1783A-PA EVB
28 The PAN1783A-PA EVB essentially resembles a PAN1783 EVB, with the addition
35 `pan1783_evb user guide`_ / `pan1783a_evb user guide`_ / `pan1783a_pa_evb user guide`_
38 The User Guide contains (amongst other things) detailed information about
46 The schematics for the PAN1783/PAN1783A/PAN1783A-PA Evaluation Boards are
47 …in the `download section PAN1783`_ / `download section PAN1783A`_ / `download section PAN1783A-PA`_
58 .. target-notes::
[all …]
|
| /Zephyr-latest/boards/waveshare/open103z/ |
| D | waveshare_open103z.dts | 4 * SPDX-License-Identifier: Apache-2.0
7 /dts-v1/;
9 #include <st/f1/stm32f103z(c-d-e)tx-pinctrl.dtsi>
10 #include <zephyr/dt-bindings/input/input-event-codes.h>
18 zephyr,shell-uart = &usart1;
25 compatible = "gpio-leds";
28 label = "User LED1";
32 label = "User LED2";
36 label = "User LED3";
40 label = "User LED4";
[all …]
|
| /Zephyr-latest/boards/openisa/rv32m1_vega/ |
| D | rv32m1_vega_openisa_rv32m1.dtsi | 3 * SPDX-License-Identifier: Apache-2.0
6 #include "rv32m1_vega_openisa_rv32m1-pinctrl.dtsi"
7 #include <zephyr/dt-bindings/input/input-event-codes.h>
15 pwm-led0 = &blue_pwm_led;
16 pwm-led1 = &green_pwm_led;
17 pwm-led2 = &red_pwm_led;
18 blue-pwm-led = &blue_pwm_led;
19 green-pwm-led = &green_pwm_led;
20 red-pwm-led = &red_pwm_led;
30 compatible = "gpio-leds";
[all …]
|
| /Zephyr-latest/tests/subsys/zbus/integration/src/ |
| D | channels.c | 3 * SPDX-License-Identifier: Apache-2.0
13 NULL, /* User data */
23 NULL, /* User data */
32 NULL, /* User data */
41 NULL, /* User data */
50 NULL, /* User data */
59 NULL, /* User data */
|
| /Zephyr-latest/boards/nxp/twr_ke18f/ |
| D | twr_ke18f.dts | 2 * Copyright (c) 2019-2021 Vestas Wind Systems A/S
4 * SPDX-License-Identifier: Apache-2.0
7 /dts-v1/;
10 #include <zephyr/dt-bindings/clock/kinetis_scg.h>
11 #include <zephyr/dt-bindings/pwm/pwm.h>
12 #include "twr_ke18f-pinctrl.dtsi"
13 #include <zephyr/dt-bindings/input/input-event-codes.h>
27 pwm-led0 = &orange_pwm_led;
28 pwm-led1 = &yellow_pwm_led;
29 pwm-led2 = &green_pwm_led;
[all …]
|
| /Zephyr-latest/boards/nxp/twr_kv58f220m/ |
| D | twr_kv58f220m.dts | 4 * SPDX-License-Identifier: Apache-2.0
7 /dts-v1/;
10 #include "twr_kv58f220m-pinctrl.dtsi"
11 #include <zephyr/dt-bindings/input/input-event-codes.h>
28 mcuboot-button0 = &user_button_0;
34 zephyr,code-partition = &slot0_partition;
35 zephyr,uart-mcumgr = &uart0;
37 zephyr,shell-uart = &uart0;
38 zephyr,uart-pipe = &uart0;
42 compatible = "gpio-leds";
[all …]
|
| /Zephyr-latest/tests/kernel/poll/src/ |
| D | test_poll_fail.c | 4 * SPDX-License-Identifier: Apache-2.0
16 * @brief Test API k_poll with error number events in user mode
30 k_poll(&events, -1, K_NO_WAIT); in ZTEST_USER()
34 * @brief Test API k_poll with error member of events in user mode
50 * @brief Test API k_poll with NULL sem event in user mode
72 * @brief Test API k_poll with NULL signal event in user mode
94 * @brief Test API k_poll with NULL fifo event in user mode
116 * @brief Test API k_poll with NULL message queue event in user mode
139 * @brief Test API k_poll_signal_init with NULL in user mode
155 * @brief Test API k_poll_signal_check with NULL object in user mode
[all …]
|
| /Zephyr-latest/tests/benchmarks/latency_measure/src/ |
| D | thread_switch_yield.c | 2 * Copyright (c) 2012-2014 Wind River Systems, Inc.
5 * SPDX-License-Identifier: Apache-2.0
13 * When user threads are supported, there are four cases to consider. These are
14 * 1. Kernel thread -> Kernel thread
15 * 2. User thread -> User thread
16 * 3. Kernel thread -> User thread
17 * 4. User thread -> Kernel thread
108 priority - 1, start_options, K_FOREVER); in thread_switch_yield_common()
114 priority - 1, alt_options, K_FOREVER); in thread_switch_yield_common()
132 sum -= timestamp_overhead_adjustment(start_options, alt_options); in thread_switch_yield_common()
[all …]
|
| /Zephyr-latest/boards/st/nucleo_h755zi_q/ |
| D | nucleo_h755zi_q.dtsi | 4 * SPDX-License-Identifier: Apache-2.0
7 #include <st/h7/stm32h755zitx-pinctrl.dtsi>
9 #include <zephyr/dt-bindings/input/input-event-codes.h>
13 compatible = "gpio-leds";
16 label = "User LD1";
20 label = "User LD2";
24 label = "User LD3";
29 compatible = "gpio-keys";
32 label = "User SB1";
|
| /Zephyr-latest/boards/nuvoton/numaker_pfm_m487/ |
| D | numaker_pfm_m487.dts | 4 * SPDX-License-Identifier: Apache-2.0
7 /dts-v1/;
9 #include "numaker_pfm_m487-pinctrl.dtsi"
10 #include <zephyr/dt-bindings/input/input-event-codes.h>
14 compatible = "nuvoton,pfm-m487", "nuvoton,m487";
26 zephyr,shell-uart = &uart0;
32 compatible = "gpio-leds";
35 label = "User LED Red";
39 label = "User LED Yellow";
43 label = "User LED Green";
[all …]
|
| /Zephyr-latest/boards/gd/gd32f450v_start/doc/ |
| D | index.rst | 6 The GD32F450V-START board is a hardware platform that enables prototyping
7 on GD32F450VK Cortex-M4F Stretch Performance MCU.
9 The GD32F450VK features a single-core ARM Cortex-M4F MCU which can run up
16 - GD32F450VKT6 MCU
17 - 1 x User LEDs
18 - 1 x User Push buttons
19 - USB FS/HS connectors
20 - GD-Link on board programmer
21 - J-Link/SWD connector
23 For more information about the GD32F450 SoC and GD32F450V-START board:
[all …]
|
