Searched full:system (Results 1 – 25 of 1374) sorted by relevance
12345678910>>...55
| /Zephyr-Core-2.7.6/subsys/fs/ |
| D | Kconfig | 8 bool "File system support"
10 Enables support for file system.
27 int "Maximum number of distinct file system types allowed"
30 Zephyr provides several file system types including FatFS and
39 system types. Zero or a negative value selects the maximum
42 file system. Selecting a value less than the actual length
43 supported by a file system may result in memory access
47 bool "Enable file system shell"
52 file system.
55 bool "Enable FUSE based access to file system partitions"
[all …]
|
| D | Kconfig.fatfs | 6 bool "ELM FAT file system support"
10 Use the ELM FAT File system implementation.
14 menu "ELM FAT file system settings"
20 The option excludes write code from ELM FAT file system driver;
25 This option translates to _FS_READONLY within ELM FAT file system
32 This option translates to _USE_MKFS within ELM FAT file system
42 a volume if no file system is found.
|
| /Zephyr-Core-2.7.6/doc/reference/file_system/ |
| D | index.rst | 9 to instantiate, mount, and operate on a file system. The File system Switch
10 decouples the applications from directly accessing an individual file system's
11 specific API or internal functions by introducing file system registration
14 In Zephyr, any file system implementation or library can be plugged into or
15 pulled out through a file system registration API. Each file system
25 Zephyr RTOS supports multiple instances of a file system by making use of
26 the mount point as the disk volume name, which is used by the file system library
29 A file system is declared as:
41 - ``FS_FATFS`` is the file system type like FATFS or LittleFS.
42 - ``FATFS_MNTP`` is the mount point where the file system will be mounted.
[all …]
|
| /Zephyr-Core-2.7.6/include/ |
| D | syscall.h | 24 * System Call Declaration macros
26 * These macros are used in public header files to declare system calls.
37 * All system calls require a verifier function and an implementation
38 * function. These must follow a naming convention. For a system call
46 * z_impl_k_foo(). This is the actual implementation of the system
52 * @brief System call handler function type
54 * These are kernel-side skeleton functions for system calls. They are
55 * necessary to sanitize the arguments passed into the system call:
63 * - If the system call has more than 6 arguments, then arg6 will be a pointer
69 * Even if the system call implementation has no return value, these always
[all …]
|
| /Zephyr-Core-2.7.6/drivers/timer/ |
| D | Kconfig | 16 Use the x86 local APIC in one-shot mode as the system time
89 system timer.
98 and provides the standard "system clock driver" interfaces.
133 SYSTICK timer and provides the standard "system clock driver" interfaces.
143 standard "system clock driver" interfaces.
161 Counter NRF_RTC1 and provides the standard "system clock driver"
179 System clock source is initiated but does not wait for clock readiness.
180 When this option is picked, system clock may not be ready when code relying
187 System clock source initialization waits until clock is available. In some
190 it is ready. When this option is picked, system clock is available after
[all …]
|
| /Zephyr-Core-2.7.6/dts/bindings/fs/ |
| D | zephyr,fstab-common.yaml | 13 The absolute path used as the file system mount point.
19 A reference to the file system's partition.
24 Mount file system on boot if present.
26 During initialization the file system driver will attempt to mount
32 Mount file system read-only if present.
35 mount descriptor generated for the file system.
40 Do not format file system if mount fails.
43 mount descriptor generated for the file system.
|
| /Zephyr-Core-2.7.6/samples/subsys/fs/littlefs/ |
| D | README.rst | 3 littlefs File System Sample Application
9 This sample app demonstrates use of Zephyr's :ref:`file system API
10 <file_system_api>` over `littlefs`_, using a file system with a file that
11 counts the number of times the system has booted. Other information
12 about the file system is also displayed.
20 The partition labeled "storage" will be used for the file system; see
22 compatible littlefs file system its contents will be replaced by an
23 empty file system. You will see diagnostics like this::
29 The error and warning are normal for a new file system.
31 After the file system is mounted you'll also see::
[all …]
|
| /Zephyr-Core-2.7.6/modules/trusted-firmware-m/ |
| D | Kconfig.tfm.partitions | 13 to be passed to the TF-M build system. Look at 'config_default.cmake'
16 options are handled by the build system in the trusted-firmware-m
24 to be passed to the TF-M build system. Look at 'config_default.cmake'
27 options are handled by the build system in the trusted-firmware-m
35 to be passed to the TF-M build system. Look at 'config_default.cmake'
38 options are handled by the build system in the trusted-firmware-m
46 to be passed to the TF-M build system. Look at 'config_default.cmake'
49 options are handled by the build system in the trusted-firmware-m
57 to be passed to the TF-M build system. Look at 'config_default.cmake'
60 options are handled by the build system in the trusted-firmware-m
[all …]
|
| /Zephyr-Core-2.7.6/include/fs/ |
| D | nvs.h | 34 * @brief Non-volatile Storage File system structure
36 * @param offset File system offset in flash
40 * @param sector_size File system is split into sectors, each sector must be multiple of pagesize
73 * Initializes a NVS file system in flash.
75 * @param fs Pointer to file system
85 * Clears the NVS file system from flash.
86 * @param fs Pointer to file system
95 * Write an entry to the file system.
97 * @param fs Pointer to file system
111 * Delete an entry from the file system
[all …]
|
| D | fs.h | 21 * @brief File System APIs
22 * @defgroup file_system_api File System APIs
34 /** @brief Enumeration to uniquely identify file system types.
37 * requires a unique identifier used to register the file system
38 * implementation and to associate a mount point with the file system
45 * identifiers are unique if multiple file system implementations are
49 /** Identifier for in-tree FatFS file system. */
52 /** Identifier for in-tree LittleFS file system. */
59 /** Flag prevents formatting device if requested file system not found */
61 /** Flag makes mounted file system read-only */
[all …]
|
| /Zephyr-Core-2.7.6/doc/reference/kernel/threads/ |
| D | system_threads.rst | 3 System Threads
10 A :dfn:`system thread` is a thread that the kernel spawns automatically
11 during system initialization.
13 The kernel spawns the following system threads:
26 this means a fatal system error is raised if the thread aborts. If
31 This thread executes when there is no other work for the system to do.
34 loop. The idle thread remains in existence as long as the system is running
42 The idle thread is an essential thread, which means a fatal system error
45 Additional system threads may also be spawned, depending on the kernel
47 enabling the system workqueue spawns a system thread
|
| /Zephyr-Core-2.7.6/subsys/pm/ |
| D | Kconfig | 8 bool "System Power management"
14 bool "System Power Management"
25 bool "System Power Management debug hooks"
27 Enable System Power Management debugging hooks.
32 module-str = System Power Management
42 targets where system power management is not supported, for example
51 that get called by the power manager application when the system
70 usage even while the CPU or system is running.
|
| /Zephyr-Core-2.7.6/scripts/west_commands/tests/ |
| D | test_stm32cubeprogrammer.py | 19 """Home path (used for Linux system CLI path)."""
22 """Program files x86 path (used for Windows system CLI path)."""
27 """Environment (used for Windows system CLI path)."""
72 "system": "",
94 "system": "",
116 "system": "",
138 "system": "",
160 "system": "",
182 "system": "",
204 "system": "",
[all …]
|
| /Zephyr-Core-2.7.6/doc/ |
| D | glossary.rst | 16 The set of user-supplied files that the Zephyr build system uses
20 The application's kernel configuration settings direct the build system
34 of the system, initializes it, and runs as the system's sole application.
39 A target system with a defined set of devices and capabilities,
41 hardware system or a simulated system running under QEMU.
47 The Zephyr build system defines one or more board configurations
49 specified by the build system can be over-ridden by the application,
69 `System on a chip`_
89 A directory on your system with a :file:`.west` subdirectory and
91 code onto your system by creating a west workspace using the
|
| /Zephyr-Core-2.7.6/drivers/syscon/ |
| D | Kconfig | 10 bool "SYSCON (System Controller) drivers"
12 SYSCON (System Controller) drivers. System controller node represents
28 bool "Generic SYSCON (System Controller) driver"
31 Enable generic SYSCON (System Controller) driver
34 int "SYSCON (System Controller) driver init priority"
|
| /Zephyr-Core-2.7.6/samples/subsys/usb/mass/ |
| D | Kconfig | 10 Use this to force an existing file system to be created.
13 prompt "Storage and file system type used by the application"
16 Specify the type of storage and file system.
23 bool "Use RAM disk and FAT file system"
29 bool "Use FLASH disk and FAT file system"
41 bool "Use SDHC and FAT file system"
|
| /Zephyr-Core-2.7.6/include/drivers/timer/ |
| D | system_timer.h | 12 * Declare API implemented by system timer driver and used by kernel components.
33 * @brief Initialize system clock driver
35 * The system clock is a Zephyr device created globally. This is its
42 * @brief Initialize system clock driver
44 * The system clock is a Zephyr device created globally. This is its
53 * @brief Set system clock timeout
55 * Informs the system clock driver that the next needed call to
69 * and that the system is permitted to enter an indefinite sleep even
71 * system uptime counter is allowed to be wrong
86 * exactly once across the system. The kernel does not (cannot,
[all …]
|
| /Zephyr-Core-2.7.6/doc/reference/usermode/ |
| D | syscalls.rst | 3 System Calls
7 limited part of the memory map. System calls (may) allow user threads to
10 When defining system calls, it is very important to ensure that access to the
11 API's private data is done exclusively through system call interfaces.
18 supervisor mode should never be exposed as system calls. Reserve these
21 This section describes how to declare new system calls and discusses a few
27 All system calls have the following components:
39 system call. The implementation function may assume that all parameters
61 :ref:`parse_syscalls.py` script, it indicates that this API is a system call.
76 The preprocessor is intentionally not used when determining the set of system
[all …]
|
| /Zephyr-Core-2.7.6/doc/guides/networking/ |
| D | networking_with_host.rst | 3 Networking with the host system
19 exchange data with the host system like a Linux desktop computer.
25 * Here IP packets are exchanged between Zephyr and the host system via serial
31 * Here IP packets are exchanged between Zephyr and the host system via QEMU's
48 system. This is the most convenient way to debug the Zephyr system as one
51 with the host system. An Ethernet driver exists in Zephyr for this purpose.
57 the host system is done via USB.
|
| /Zephyr-Core-2.7.6/include/sys/ |
| D | arch_interface.h | 198 * @brief Start a numbered CPU on a MP-capable system
389 * This will invoke z_sched_ipi() on other CPUs in the system.
405 * Invoke a system call with 0 arguments.
415 * should be enabled when invoking the system call marshallers from the
416 * dispatch table. Thread preemption may occur when handling system calls.
419 * index the system call dispatch table, containing function pointers to the
420 * specific system call code.
422 * @param call_id System call ID
423 * @return Return value of the system call. Void system calls return 0 here.
428 * Invoke a system call with 1 argument.
[all …]
|
| /Zephyr-Core-2.7.6/doc/security/ |
| D | security-overview.rst | 26 1. **Secure Development:** Defines the system architecture and
31 to enforce them. A security architecture of the system and
123 cryptographic algorithms, and on its monolithic system design.
141 binary. System calls are implemented as function calls without requiring
148 features to split the system into privileged and unprivileged execution
150 partition system resources (memory, peripheral address space, etc) and
162 Code reviews are documented and enforced using a voting system before
178 conventions. Functional correctness is ensured by the build system and
220 System Level Security (Ecosystem, ...)
223 System level security encompasses a wide variety of categories. Some
[all …]
|
| /Zephyr-Core-2.7.6/samples/boards/nrf/system_off/ |
| D | README.rst | 1 .. _nrf-system-off-sample:
3 nRF5x System Off demo
16 * Turn the system off after enabling wakeup through a button press
30 system off was entered, and total uptime since initial power-on are retained
32 the containing RAM section powered while in system-off mode.
67 nrf52dk_nrf52832 system off demo
72 Entering system off; press BUTTON1 to restart
|
| /Zephyr-Core-2.7.6/dts/arm/st/h7/ |
| D | stm32h750.dtsi | 16 /* System data RAM accessible over AXI bus: AXI SRAM in D1 domain */
22 /* System data RAM accessible over AHB bus: SRAM1 in D2 domain */
28 /* System data RAM accessible over AHB bus: SRAM2 in D2 domain */
34 /* System data RAM accessible over AHB bus: SRAM3 in D2 domain */
40 /* System data RAM accessible over AHB bus: SRAM4 in D3 domain */
|
| /Zephyr-Core-2.7.6/samples/subsys/shell/fs/ |
| D | README.rst | 3 File system shell example
9 This example provides shell access to a LittleFS file system partition in flash.
14 A board with LittleFS file system support and UART console
63 All file system related commands are available as sub-commands of fs.
65 Begin by mounting the LittleFS file system.
71 Files System Shell Commands
77 Mount a file system partition to a given mount point
160 Linux system.
|
| /Zephyr-Core-2.7.6/drivers/clock_control/ |
| D | clock_control_lpc11u6x.h | 52 volatile uint32_t sys_mem_remap; /* System memory remap */
54 volatile uint32_t sys_pll_ctrl; /* System PLL control */
55 volatile const uint32_t sys_pll_stat; /* System PLL status */
60 volatile uint32_t sys_osc_ctrl; /* System oscillator control */
66 volatile uint32_t sys_rst_stat; /* System reset status */
68 volatile uint32_t sys_pll_clk_sel; /* System PLL clock source */
69 volatile uint32_t sys_pll_clk_uen; /* System PLL source update */
77 volatile uint32_t sys_ahb_clk_div; /* System clock divider */
79 volatile uint32_t sys_ahb_clk_ctrl; /* System clock control */
110 volatile uint32_t sys_tck_cal; /* System tick calibration */
|
12345678910>>...55
