Home
last modified time | relevance | path

Searched refs:system (Results 1 – 25 of 1075) sorted by relevance

12345678910>>...43

/Zephyr-Core-3.7.0/subsys/fs/
DKconfig8 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 int "File system initialization priority"
55 bool "File system shell"
60 file system.
[all …]
/Zephyr-Core-3.7.0/tests/drivers/gnss/gnss_nmea0183/src/
Dmain.c375 .system = GNSS_SYSTEM_GPS,
383 .system = GNSS_SYSTEM_GPS, .is_tracked = true},
385 .system = GNSS_SYSTEM_GPS, .is_tracked = true},
387 .system = GNSS_SYSTEM_GPS, .is_tracked = true},
389 .system = GNSS_SYSTEM_GPS, .is_tracked = true},
418 .system = GNSS_SYSTEM_GPS,
426 .system = GNSS_SYSTEM_GPS, .is_tracked = true},
428 .system = GNSS_SYSTEM_GPS, .is_tracked = true},
430 .system = GNSS_SYSTEM_GPS, .is_tracked = true},
432 .system = GNSS_SYSTEM_GPS, .is_tracked = true},
[all …]
/Zephyr-Core-3.7.0/doc/services/file_system/
Dindex.rst9 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.7.0/modules/trusted-firmware-m/
DKconfig.tfm.partitions16 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.7.0/samples/subsys/fs/littlefs/
DREADME.rst5 Use file system API over LittleFS.
10 This sample app demonstrates use of Zephyr's :ref:`file system API
11 <file_system_api>` over `littlefs`_, using file system with files that:
12 * count the number of times the system has booted
15 Other information about the file system is also displayed.
26 The partition labeled "storage" will be used for the file system; see
28 compatible littlefs file system its contents will be replaced by an
29 empty file system. You will see diagnostics like this::
35 The error and warning are normal for a new file system.
37 After the file system is mounted you'll also see::
[all …]
/Zephyr-Core-3.7.0/samples/boards/nrf/system_off/
DREADME.rst1 .. _nrf-system-off-sample:
17 system off was entered, and total uptime since initial power-on are retained
19 the containing RAM section powered while in system-off mode.
36 nrf52dk system off demo
37 Entering system off; press sw0 to restart
/Zephyr-Core-3.7.0/boards/intel/niosv_g/doc/
Dindex.rst9 …Intel FPGA Design Store Nios® V/g Hello World Example Design system and this complete system is co…
17 Nios® V/g hello world example design system
20 Prebuilt Nios® V/g hello world example design system is available in Intel FPGA Design store.
23 For example, Arria10 Nios® V/g 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/g processor example design system in FPGA
31 Please use Intel Quartus Programmer tool to program Nios® V/g 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/g processor system.
/Zephyr-Core-3.7.0/boards/intel/niosv_m/doc/
Dindex.rst9 …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.7.0/subsys/logging/backends/
DKconfig.fs5 bool "File system backend"
10 When enabled, backend is using the configured file system to output logs.
11 As the file system must be mounted for the logging to work, it must be
13 Log messages are discarded as long as the file system is not mounted.
25 When enabled automatically start the file system backend on
39 User defined name of log files saved in the file system.
60 size of file system partition.
/Zephyr-Core-3.7.0/subsys/fs/ext2/
DKconfig4 # Ext2 file system
7 bool "Ext2 file system support"
10 Enable Ext2 file system support.
18 menu "Ext2 file system Settings"
45 of the file system must be specified by this option.
/Zephyr-Core-3.7.0/samples/subsys/usb/mass/
DKconfig9 Use this to force an existing file system to be created.
12 prompt "Storage and file system type used by the application"
15 Specify the type of storage and file system.
21 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.7.0/drivers/timer/
DKconfig.rv32m1_lptmr7 bool "RV32M1 LPTMR system timer driver"
13 peripheral as the system clock. It provides the standard "system clock
DKconfig.nrf_xrtc15 When this option is picked, system clock may not be ready when code relying
25 it is ready. When this option is picked, system clock is available after
26 system clock driver initialization but it may be less accurate. Option is
34 option is picked, system clock is available and stable after system clock
DKconfig.riscv_machine20 timer driver. It provides the standard "system clock driver" interfaces.
28 Specifies the division ratio of the system clock supplied to the Machine Timer.
30 A clock obtained by dividing the system clock by a value of [2^N] is
33 Default case is N=0, this means use system clock as machine timer clock.
/Zephyr-Core-3.7.0/doc/kernel/services/threads/
Dsystem_threads.rst10 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.7.0/cmake/toolchain/oneApi/
Dgeneric.cmake10 string(TOLOWER ${CMAKE_HOST_SYSTEM_NAME} system)
12 set(TOOLCHAIN_HOME ${ONEAPI_TOOLCHAIN_PATH}/compiler/latest/${system}/bin/)
13 set(ONEAPI_LLVM_BIN_PATH ${ONEAPI_TOOLCHAIN_PATH}/compiler/latest/${system}/bin-llvm)
27 if(system STREQUAL "linux")
39 elseif(system STREQUAL "windows")
/Zephyr-Core-3.7.0/samples/modules/chre/
DREADME.rst20 #. *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.7.0/soc/nxp/kinetis/k8x/
DKconfig38 from the system clock.
45 system clock.
52 system clock.
59 system clock.
/Zephyr-Core-3.7.0/drivers/clock_control/
DKconfig.numaker7 bool "NuMaker system clock controller driver"
11 Enable support for NuMaker system clock controller driver
/Zephyr-Core-3.7.0/doc/services/pm/
Dindex.rst6 Zephyr RTOS power management subsystem provides several means for a system
14 system
/Zephyr-Core-3.7.0/drivers/pinctrl/
DKconfig.xlnx5 bool "Xilinx Zynq 7000 processor system MIO pin controller driver"
10 Enable the Xilinx Zynq 7000 processor system MIO pin controller driver.
/Zephyr-Core-3.7.0/scripts/tests/twister/
Dtest_log_helper.py28 def test_log_command(caplog, system, expected_log): argument
35 with mock.patch('platform.system', return_value=system):
/Zephyr-Core-3.7.0/doc/
Dglossary.rst16 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.
42 A target system with a defined set of devices and capabilities,
44 hardware system or a simulated system running under QEMU. A board can
51 The Zephyr build system defines one or more board configurations
53 specified by the build system can be over-ridden by the application,
58 identifies a particular system, but does not include additional
71 hardware system. This is useful to avoid duplication of board files
72 whenever small changes are introduced to a hardware system.
[all …]
/Zephyr-Core-3.7.0/tests/kernel/mem_protect/protection/
DREADME.rst46 Caught system error -- reason 0
55 Caught system error -- reason 0
64 Caught system error -- reason 0
73 Caught system error -- reason 0
82 Caught system error -- reason 0
/Zephyr-Core-3.7.0/doc/kernel/usermode/
Dmpu_userspace.rst8 defined in the system. The privileged stacks are created as a part of the
17 information is filled in and later used by the swap and system call
21 During system calls, the user mode thread's access to the system call and the

12345678910>>...43