Searched full:system (Results 1 – 25 of 1853) sorted by relevance
12345678910>>...75
| /Zephyr-Core-3.4.0/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 "File system shell"
52 file system.
57 bool "File system shell read/write/erase test commands"
[all …]
|
| /Zephyr-Core-3.4.0/doc/services/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-3.4.0/include/zephyr/ |
| 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-3.4.0/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.
51 the mount descriptor generated for the file system.
|
| /Zephyr-Core-3.4.0/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,
54 save energy independently of the the system power state. Devices will keep
60 A system thread that runs when there are no other threads ready to run.
88 `System on a chip`_
[all …]
|
| /Zephyr-Core-3.4.0/boards/arm/arduino_nano_33_ble/support/ |
| D | startup.cmm | 32 ; process system-wide settings
34 IF OS.FILE("~~/system-settings.cmm")
35 DO "~~/system-settings.cmm"
40 SYStem.Down
41 IF PRACTICE.CoMmanD.AVAILable(SYStem.CPU.NANO33BLE)
42 SYStem.CPU NANO33BLE
44 SYStem.CPU NRF52840QI
77 IF !SYStem.Up()
79 SYStem.PORT &gdbRemote
81 SYStem.Option MMUSPACES ON
[all …]
|
| /Zephyr-Core-3.4.0/modules/trusted-firmware-m/ |
| D | Kconfig.tfm.partitions | 16 to be passed to the TF-M build system. Look at 'config_default.cmake'
19 options are handled by the build system in the trusted-firmware-m
27 to be passed to the TF-M build system. Look at 'config_default.cmake'
30 options are handled by the build system in the trusted-firmware-m
38 to be passed to the TF-M build system. Look at 'config_default.cmake'
41 options are handled by the build system in the trusted-firmware-m
50 to be passed to the TF-M build system. Look at 'config_default.cmake'
53 options are handled by the build system in the trusted-firmware-m
61 to be passed to the TF-M build system. Look at 'config_default.cmake'
64 options are handled by the build system in the trusted-firmware-m
[all …]
|
| /Zephyr-Core-3.4.0/include/zephyr/fs/ |
| D | fs.h | 21 * @brief File System APIs
22 * @defgroup file_system_api File System APIs
35 /** @brief Enumeration to uniquely identify file system types.
38 * requires a unique identifier used to register the file system
39 * implementation and to associate a mount point with the file system
46 * identifiers are unique if multiple file system implementations are
50 /** Identifier for in-tree FatFS file system. */
53 /** Identifier for in-tree LittleFS file system. */
60 /** Flag prevents formatting device if requested file system not found */
62 /** Flag makes mounted file system read-only */
[all …]
|
| D | nvs.h | 35 * @brief Non-volatile Storage File system structure
37 * @param offset File system offset in flash
41 * @param sector_size File system is split into sectors, each sector must be multiple of pagesize
77 * Mount a NVS file system onto the flash device specified in @p fs.
79 * @param fs Pointer to file system
88 * Clears the NVS file system from flash.
89 * @param fs Pointer to file system
98 * Write an entry to the file system.
100 * @param fs Pointer to file system
114 * Delete an entry from the file system
[all …]
|
| /Zephyr-Core-3.4.0/include/zephyr/arch/common/ |
| D | pm_s2ram.h | 26 * @brief System off function
29 * to power the system off after the CPU context has been saved.
31 * This function never returns if the system is powered off. If the operation
33 * of restoring the system in a fully operational state before returning.
35 * @retval none The system is powered off.
36 * @retval -EBUSY The system is busy and cannot be powered off at this time.
45 * (retained) RAM before powering the system off using the provided function.
52 * @param system_off Function to power off the system.
55 * @retval -EBUSY The system is busy and cannot be suspended at this time.
|
| /Zephyr-Core-3.4.0/drivers/timer/ |
| D | Kconfig.nrf_rtc | 15 Counter NRF_RTC1 and provides the standard "system clock driver"
51 System clock source is initiated but does not wait for clock readiness.
52 When this option is picked, system clock may not be ready when code relying
59 System clock source initialization waits until clock is available. In some
62 it is ready. When this option is picked, system clock is available after
63 system clock driver initialization but it may be less accurate. Option is
70 System clock source initialization waits until clock is stable. When this
71 option is picked, system clock is available and stable after system clock
|
| /Zephyr-Core-3.4.0/subsys/logging/backends/ |
| D | Kconfig.fs | 5 bool "File system backend"
9 When enabled, backend is using the configured file system to output logs.
10 As the file system must be mounted for the logging to work, it must be
12 Log messages are discarded as long as the file system is not mounted.
24 When enabled automatically start the file system backend on
38 User defined name of log files saved in the file system.
59 size of file system partition.
|
| /Zephyr-Core-3.4.0/samples/subsys/usb/mass/ |
| D | Kconfig | 7 Use this to force an existing file system to be created.
10 prompt "Storage and file system type used by the application"
13 Specify the type of storage and file system.
20 bool "Use RAM disk and FAT file system"
26 bool "Use FLASH disk and FAT file system"
38 bool "Use SDHC and FAT file system"
|
| /Zephyr-Core-3.4.0/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 file system with files that:
11 * count the number of times the system has booted
14 Other information about the file system is also displayed.
25 The partition labeled "storage" will be used for the file system; see
27 compatible littlefs file system its contents will be replaced by an
28 empty file system. You will see diagnostics like this::
34 The error and warning are normal for a new file system.
36 After the file system is mounted you'll also see::
[all …]
|
| /Zephyr-Core-3.4.0/doc/kernel/services/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-3.4.0/drivers/syscon/ |
| D | Kconfig | 10 bool "System Controller (SYSCON) drivers"
12 SYSCON (System Controller) drivers. System controller node represents
26 bool "Generic SYSCON (System Controller) driver"
30 Enable generic SYSCON (System Controller) driver
33 int "SYSCON (System Controller) driver init priority"
|
| /Zephyr-Core-3.4.0/doc/services/pm/ |
| D | system.rst | 1 .. _pm-system:
3 System Power Management
8 Subsystem can put an idle system in one of the supported power states, based
18 The following diagram describes system power management:
20 .. image:: images/system-pm.svg
22 :alt: System power management
53 power state the system should transition to based on states defined by the
62 The power management system enters the power state which offers the highest
64 :dtcompatible:`zephyr,power-state`) less than or equal to the scheduled system
82 to decide which power state the system should transition to based on the
[all …]
|
| /Zephyr-Core-3.4.0/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-3.4.0/subsys/pm/ |
| D | Kconfig | 8 bool "System Power Management"
19 module-str = System Power Management
23 bool "System Power Management Stats"
26 Enable System Power Management Stats.
61 targets where system power management is not supported, for example
70 that get called by the power manager application when the system
111 usage even while the CPU or system is running.
115 bool "Use only on Runtime Power Management on system suspend / resume"
118 On system suspend / resume do not trigger the Device PM hooks but
|
| /Zephyr-Core-3.4.0/dts/bindings/timer/ |
| D | nuclei,systimer.yaml | 5 Nuclei System Timer
7 The Nuclei system timer provides RISC-V privileged mtime and mtimecmp
25 clock used by the system timer.
26 This property supports the case that the system timer and CPU use
30 For example, the CPU clock frequency is 108MHz, and the system timer
44 Setting clk-divider to 2 specifies the system timer uses the clock
|
| /Zephyr-Core-3.4.0/samples/modules/chre/ |
| D | README.rst | 20 #. *System* - a framework allowing nanoapps to make common system requests such as logging, clock,
21 and some basic memory allocation/deallocation. See `pal/system.h`_ for API details.
46 #. Print a message notifying that it's not possible to remove a system level nanoapp
52 #. Add an implementation of the `pal/sensor.h`_ and `pal/system.h`_ to Zephyr. These will be
63 .. _`chre_api/chre/nanoapp.h`: https://cs.android.com/android/platform/superproject/+/master:system…
64 .. _`pal/audio.h`: https://cs.android.com/android/platform/superproject/+/master:system/chre/pal/in…
65 .. _`pal/gnss.h`: https://cs.android.com/android/platform/superproject/+/master:system/chre/pal/inc…
66 .. _`pal/sensor.h`: https://cs.android.com/android/platform/superproject/+/master:system/chre/pal/i…
67 .. _`pal/system.h`: https://cs.android.com/android/platform/superproject/+/master:system/chre/pal/i…
68 .. _`pal/wifi.h`: https://cs.android.com/android/platform/superproject/+/master:system/chre/pal/inc…
[all …]
|
| /Zephyr-Core-3.4.0/boards/riscv/niosv_m/doc/ |
| D | index.rst | 9 …Intel FPGA Design Store Nios® V/m Hello World Example Design system and this complete system is co…
17 Nios® V/m hello world example design system
20 Prebuilt Nios® V/m hello world example design system is available in Intel FPGA Design store.
23 For example, Arria10 Nios® V/m processor example design system prebuilt files can be downloaded fro…
26 ready_to_test/top.sof file is the prebuilt SRAM Object File for hello world example design system a…
28 Create Nios® V/m processor example design system in FPGA
31 Please use Intel Quartus Programmer tool to program Nios® V/m processor based system into the FPGA …
44 top.sof is referring to Nios® V/m processor based system SRAM Object File.
55 Use the JTAG UART terminal to print the stdout and stderr of the Nios® V/m processor system.
|
| /Zephyr-Core-3.4.0/soc/arm/nxp_imx/mimx8ml8_m7/ |
| D | soc.c | 59 /* SYSTEM PLL1 configuration */
64 .postDiv = 2U, /*!< SYSTEM PLL1 frequency = 800MHZ */
67 /* SYSTEM PLL2 configuration */
72 .postDiv = 1U, /*!< SYSTEM PLL2 frequency = 1000MHZ */
75 /* SYSTEM PLL3 configuration */
80 .postDiv = 2U, /*!< SYSTEM PLL3 frequency = 600MHZ */
87 * driver on M7 core side . Please note that the ROM has already configured the SYSTEM PLL1 in SOC_ClockInit()
88 * to 800Mhz when power up the SOC, meanwhile A core would enable SYSTEM PLL1, SYSTEM PLL2 in SOC_ClockInit()
89 * and SYSTEM PLL3 by U-Boot. Therefore, there is no need to configure the system PLL again in SOC_ClockInit()
93 /* switch AHB NOC root to 24M first in order to configure the SYSTEM PLL1. */ in SOC_ClockInit()
[all …]
|
| /Zephyr-Core-3.4.0/doc/kernel/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-3.4.0/doc/connectivity/networking/ |
| D | networking_with_host.rst | 3 Networking with the host system
20 exchange data with the host system like a Linux desktop computer.
26 * Here IP packets are exchanged between Zephyr and the host system via serial
32 * Here IP packets are exchanged between Zephyr and the host system via QEMU's
59 system. This is the most convenient way to debug the Zephyr system as one
62 with the host system. An Ethernet driver exists in Zephyr for this purpose.
68 the host system is done via USB.
|
12345678910>>...75
