Home
last modified time | relevance | path

Searched full:file (Results 1 – 25 of 3186) sorted by relevance

12345678910>>...128

/Zephyr-latest/scripts/utils/
Dgen_util_macros.py23 def write_hidden_start(file): argument
24 file.write("/**\n")
25 file.write(" * @cond INTERNAL_HIDDEN\n")
26 file.write(" */\n")
29 def write_hidden_stop(file): argument
30 file.write("/**\n")
31 file.write(" * INTERNAL_HIDDEN @endcond\n")
32 file.write(" */\n")
36 with open("util_listify.h", "w") as file:
37 write_hidden_start(file)
[all …]
/Zephyr-latest/subsys/fs/
DKconfig5 menu "File Systems"
8 bool "Link file system libraries into build"
10 Link in the underlying file system libraries. This can be
12 to work directly with the underlying file system libraries.
18 bool "File system support"
21 Enables support for file system.
38 int "Maximum number of distinct file system types allowed"
41 Zephyr provides several file system types including FatFS and
46 int "Optional override for maximum file name length"
49 Specify the maximum file name allowed across all enabled file
[all …]
/Zephyr-latest/include/zephyr/fs/
Dfs.h21 * @brief File System APIs
22 * @defgroup file_system_api File System APIs
34 /** Identifier for file entry */
40 /** @brief Enumeration to uniquely identify file system types.
42 * Zephyr supports in-tree file systems and external ones. Each
43 * requires a unique identifier used to register the file system
44 * implementation and to associate a mount point with the file system
46 * in-tree file systems.
48 * External file systems should be registered using unique identifiers
50 * applications that use external file systems to ensure that these
[all …]
Dfs_sys.h20 * @brief File System interface structure
24 * @name File operations
28 * Opens or creates a file, depending on flags given.
30 * @param filp File to open/create.
31 * @param fs_path Path to the file.
32 * @param flags Flags for opening/creating the file.
40 * @param filp File to read from.
49 * @param filp File to write to.
57 * Moves the file position to a new location in the file.
59 * @param filp File to move.
[all …]
/Zephyr-latest/tests/subsys/fs/ext2/src/
Dtestfs_dirops.c18 struct fs_file_t file; in ZTEST() local
21 fs_file_t_init(&file); in ZTEST()
28 zassert_equal(fs_open(&file, "/sml/file1", FS_O_CREATE), 0, "Create file1 failed"); in ZTEST()
29 zassert_equal(fs_close(&file), 0, "Close file error"); in ZTEST()
30 zassert_equal(fs_open(&file, "/sml/dir1/file2", FS_O_CREATE), 0, "Create file2 failed"); in ZTEST()
31 zassert_equal(fs_close(&file), 0, "Close file error"); in ZTEST()
32 zassert_equal(fs_open(&file, "/sml/dir2/file3", FS_O_CREATE), 0, "Create file3 failed"); in ZTEST()
33 zassert_equal(fs_close(&file), 0, "Close file error"); in ZTEST()
36 zassert_equal(fs_open(&file, "/sml/dir1", 0), -EINVAL, "Should return error"); in ZTEST()
37 zassert_equal(fs_open(&file, "/sml/dir2", 0), -EINVAL, "Should return error"); in ZTEST()
[all …]
/Zephyr-latest/subsys/mgmt/mcumgr/grp/fs_mgmt/
DKconfig5 # The Kconfig file is dedicated to File System management group of
9 # Options defined in this file should be prefixed:
16 bool "MCUmgr handlers for file management"
20 Enables MCUmgr handlers for file management
23 file system, including application-stored secrets like
27 callbacks when file access is attempted, which they can then filter,
33 prompt "Maximum file size that could be uploaded/downloaded"
36 Maximum file size that will be allowed to be downloaded from
39 CBOR frame for storage of offset/size of file downloaded.
45 size/offset within CBOR frame with file chunk.
[all …]
/Zephyr-latest/tests/posix/fs/src/
Dtest_fs_file.c13 int file = -1; variable
21 TC_ERROR("Failed opening file: %d, errno=%d\n", res, errno); in test_file_open()
26 file = res; in test_file_open()
36 res = lseek(file, 0, SEEK_SET); in test_file_write()
39 close(file); in test_file_write()
40 file = -1; in test_file_write()
44 brw = write(file, (char *)test_str, strlen(test_str)); in test_file_write()
46 TC_PRINT("Failed writing to file [%d]\n", (int)brw); in test_file_write()
47 close(file); in test_file_write()
48 file = -1; in test_file_write()
[all …]
/Zephyr-latest/tests/subsys/fs/common/
Dtest_fs_basic.c18 * File system should be mounted before tests are started.
25 struct fs_file_t file; in create_write_hello() local
27 fs_file_t_init(&file); in create_write_hello()
28 TC_PRINT("creating and writing file\n"); in create_write_hello()
30 zassert_equal(fs_open(&file, in create_write_hello()
45 "stat new hello not file"); in create_write_hello()
50 zassert_equal(testfs_write_incrementing(&file, 0, TESTFS_BUFFER_SIZE), in create_write_hello()
59 "stat written hello not file"); in create_write_hello()
64 /* VARIATION POINT: littlefs does not update the file size of in create_write_hello()
65 * an open file. See upstream issue #250. in create_write_hello()
[all …]
/Zephyr-latest/tests/bluetooth/controller/common/include/
Dhelper_pdu.h67 void helper_pdu_verify_ping_req(const char *file, uint32_t line, struct pdu_data *pdu, void *param);
68 void helper_pdu_verify_ping_rsp(const char *file, uint32_t line, struct pdu_data *pdu, void *param);
70 void helper_pdu_verify_feature_req(const char *file, uint32_t line, struct pdu_data *pdu,
72 void helper_pdu_verify_peripheral_feature_req(const char *file, uint32_t line, struct pdu_data *pdu,
74 void helper_pdu_verify_feature_rsp(const char *file, uint32_t line, struct pdu_data *pdu,
77 void helper_pdu_verify_min_used_chans_ind(const char *file, uint32_t line, struct pdu_data *pdu,
80 void helper_pdu_verify_version_ind(const char *file, uint32_t line, struct pdu_data *pdu,
83 void helper_pdu_verify_enc_req(const char *file, uint32_t line, struct pdu_data *pdu, void *param);
85 void helper_pdu_ntf_verify_enc_req(const char *file, uint32_t line, struct pdu_data *pdu,
88 void helper_pdu_verify_enc_rsp(const char *file, uint32_t line, struct pdu_data *pdu, void *param);
[all …]
/Zephyr-latest/tests/subsys/fs/fat_fs_api/src/
Dtest_fat_file_reentrant.c43 /* File open should wait here, as the fs is locked. Therefore, automatic switch back to in test_reentrant_access()
46 TC_PRINT("Open file\n"); in test_reentrant_access()
48 zassert_ok(res, "Err: File could not be opened [%d]\n", res); in test_reentrant_access()
49 TC_PRINT("File opened\n"); in test_reentrant_access()
53 "File open with locked mutex"); in test_reentrant_access()
57 zassert_ok(res, "Error closing file [%d]\n", res); in test_reentrant_access()
59 zassert_ok(res, "Error deleting file [%d]\n", res); in test_reentrant_access()
70 TC_PRINT("\nParallel reentrant-safe file access test:\n"); in test_reentrant_parallel_file_access()
72 TC_PRINT("Open file 1\n"); in test_reentrant_parallel_file_access()
74 zassert_ok(res, "Err: File 1 could not be opened [%d]\n", res); in test_reentrant_parallel_file_access()
[all …]
/Zephyr-latest/doc/hardware/porting/
Dsoc_porting.rst76 #. :file:`soc.yml`: a YAML file describing the high-level meta data of the
84 #. :file:`soc.h`: a header file which can be used to describe or provide
85 configuration macros for the SoC. The :file:`soc.h` will often be included in
88 #. :file:`Kconfig.soc`: the base SoC configuration which defines a Kconfig SoC
92 be defined in this file. Kconfig settings outside of the SoC tree must not be
93 selected. To select general Zephyr Kconfig settings the :file:`Kconfig` file
96 #. :file:`CMakeLists.txt`: CMake file loaded by the Zephyr build system. This
97 CMake file can define additional include paths and/or source files to be used
103 - :file:`Kconfig`, :file:`Kconfig.defconfig` software configuration in
110 The SoC YAML file describes the SoC family, SoC series, and SoC at a high level.
[all …]
/Zephyr-latest/subsys/logging/backends/
DKconfig.fs5 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
35 bool "Append to the newest log file"
38 When enabled and when there is space left in the newest log file,
40 When disabled backend creates a new log file on every startup.
43 string "Log file name prefix"
46 User defined name of log files saved in the file system.
[all …]
/Zephyr-latest/include/zephyr/mgmt/mcumgr/grp/fs_mgmt/
Dfs_mgmt.h17 * Command IDs for file system management group.
26 * Command result codes for file system management group.
35 /** The specified file name is not valid. */
38 /** The specified file does not exist. */
41 /** The specified file is a directory, not a file. */
44 /** Error occurred whilst attempting to open a file. */
47 /** Error occurred whilst attempting to seek to an offset in a file. */
50 /** Error occurred whilst attempting to read data from a file. */
53 /** Error occurred whilst trying to truncate file. */
56 /** Error occurred whilst trying to delete file. */
[all …]
/Zephyr-latest/doc/develop/west/
Dbasics.rst22 :file:`zephyrproject` as well as all its subfolders, looks like this:
28 │ └── config # per-workspace local configuration file
32 │ ├── west.yml # manifest file
52 Above, :file:`zephyrproject` is the name of the workspace's top level
53 directory, or *topdir*. (The name :file:`zephyrproject` is just an example
60 The topdir contains the :file:`.west` directory. When west needs to find
61 the topdir, it searches for :file:`.west`, and uses its parent directory.
66 configuration file
67 The file :file:`.west/config` is the workspace's :ref:`local configuration
68 file <west-config>`.
[all …]
/Zephyr-latest/doc/services/file_system/
Dindex.rst3 File Systems
7 file systems at different mount points (e.g., ``/fatfs`` and ``/lfs``). The
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:
[all …]
/Zephyr-latest/scripts/
Dwest-commands.yml3 - file: scripts/west_commands/completion.py
8 - file: scripts/west_commands/boards.py
13 - file: scripts/west_commands/shields.py
18 - file: scripts/west_commands/build.py
23 - file: scripts/west_commands/twister_cmd.py
28 - file: scripts/west_commands/sign.py
33 - file: scripts/west_commands/flash.py
38 - file: scripts/west_commands/debug.py
52 - file: scripts/west_commands/export.py
57 - file: scripts/west_commands/spdx.py
[all …]
/Zephyr-latest/doc/build/snippets/
Dwriting.rst10 Snippets are defined using YAML files named :file:`snippet.yml`.
12 A :file:`snippet.yml` file contains the name of the snippet, along with
20 Build system settings go in other keys in the file as described later on in
24 you can combine a snippet-specific devicetree overlay and a ``.conf`` file like
71 application source directory (so :file:`<app>/snippets` is also).
79 :file:`snippet.yml` files underneath a subdirectory named :file:`snippets/`,
83 system will look for :file:`snippet.yml` files underneath the following
86 - :file:`/foo/snippets/`
87 - :file:`/bar/snippets/`
89 The :file:`snippet.yml` files can be nested anywhere underneath these
[all …]
/Zephyr-latest/cmake/
Dcfb.cmake3 # These functions can be used to generate a CFB font include file from
4 # a TrueType/OpenType font file or an image file.
6 input_file # The TrueType/OpenType font file or the image file
7 output_file # The generated header file
29 target # The cmake target that depends on the generated file
30 input_file # The TrueType/OpenType font file or the image file
31 output_file # The generated header file
34 gen_target # The generated file target we depend on
47 target # The cmake target that depends on the generated file
48 input_file # The TrueType/OpenType font file or image file
[all …]
/Zephyr-latest/doc/build/dts/
Dintro-input-output.rst26 The devicetree files inside the :file:`zephyr` directory look like this:
35 Generally speaking, every supported board has a :file:`BOARD.dts` file
39 :file:`BOARD.dts` includes one or more ``.dtsi`` files. These ``.dtsi`` files
42 multiple boards. In addition to these includes, :file:`BOARD.dts` also describes
45 The :file:`dts/common` directory contains :file:`skeleton.dtsi`, a minimal
46 include file for defining a complete devicetree. Architecture-specific
47 subdirectories (:file:`dts/<ARCH>`) contain ``.dtsi`` files for CPUs or SoCs
48 which extend :file:`skeleton.dtsi`.
54 :file:`BOARD.dts` can be extended or modified using *overlays*. Overlays are
55 also DTS files; the :file:`.overlay` extension is just a convention which makes
[all …]
/Zephyr-latest/tests/bluetooth/controller/common/src/
Dhelper_pdu.c47 zassert_mem_equal(_s._f, _p->_f, sizeof(_p->_f), _t "\nCalled at %s:%d\n", file, line);
534 void helper_pdu_verify_version_ind(const char *file, uint32_t line, struct pdu_data *pdu, in helper_pdu_verify_version_ind() argument
539 zassert_equal(pdu->ll_id, PDU_DATA_LLID_CTRL, "Not a Control PDU.\nCalled at %s:%d\n", file, in helper_pdu_verify_version_ind()
542 "Not a LL_VERSION_IND.\nCalled at %s:%d\n", file, line); in helper_pdu_verify_version_ind()
544 "Wrong version number.\nCalled at %s:%d\n", file, line); in helper_pdu_verify_version_ind()
546 "Wrong company id.\nCalled at %s:%d\n", file, line); in helper_pdu_verify_version_ind()
548 "Wrong sub version number.\nCalled at %s:%d\n", file, line); in helper_pdu_verify_version_ind()
551 void helper_pdu_verify_ping_req(const char *file, uint32_t line, struct pdu_data *pdu, void *param) in helper_pdu_verify_ping_req() argument
553 zassert_equal(pdu->ll_id, PDU_DATA_LLID_CTRL, "Not a Control PDU.\nCalled at %s:%d\n", file, in helper_pdu_verify_ping_req()
556 "Not a LL_PING_REQ. Called at %s:%d\n", file, line); in helper_pdu_verify_ping_req()
[all …]
/Zephyr-latest/modules/cmsis-nn/
DCMakeLists.txt18 file(GLOB SRC "${CMSIS_NN_DIR}/Source/ActivationFunctions/*_s8*.c")
19 file(GLOB SRC_S16 "${CMSIS_NN_DIR}/Source/ActivationFunctions/*_s16*.c")
26 file(GLOB SRC "${CMSIS_NN_DIR}/Source/BasicMathFunctions/*_*.c")
31 file(GLOB SRC "${CMSIS_NN_DIR}/Source/ConcatenationFunctions/*_*.c")
36 file(GLOB SRC_S4 "${CMSIS_NN_DIR}/Source/ConvolutionFunctions/*_s4*.c")
37 file(GLOB SRC_S8 "${CMSIS_NN_DIR}/Source/ConvolutionFunctions/*_s8*.c")
38 file(GLOB SRC_S16 "${CMSIS_NN_DIR}/Source/ConvolutionFunctions/*_s16*.c")
43 file(GLOB SRC_S4 "${CMSIS_NN_DIR}/Source/FullyConnectedFunctions/*_s4.c")
44 file(GLOB SRC_S8 "${CMSIS_NN_DIR}/Source/FullyConnectedFunctions/*_s8.c")
45 file(GLOB SRC_S16 "${CMSIS_NN_DIR}/Source/FullyConnectedFunctions/*_s16*.c")
[all …]
/Zephyr-latest/scripts/pylib/pytest-twister-harness/tests/resources/
Dfifo_mock.py20 self.file = None
24 self.logger.info(f'Creating fifo file: {self.filename}')
29 self.logger.error(f'Did not able create fifo file: {self.filename}')
31 self.file = open(self.filename, self.mode, buffering=0)
32 self.logger.info(f'File created: {self.filename}')
39 if self.file:
40 self.file.write(data)
43 if self.file:
44 return self.file.readline()
47 if self.file:
[all …]
/Zephyr-latest/doc/develop/toolchains/
Dcustom_cmake.rst6 To use a custom toolchain defined in an external CMake file, :ref:`set these
14 :file:`TOOLCHAIN_ROOT` directory:
16 - :file:`cmake/toolchain/<toolchain name>/generic.cmake`: configures the
19 :ref:`devicetree` file.
20 - :file:`cmake/toolchain/<toolchain name>/target.cmake`: configures the
28 :file:`generic.cmake` and :file:`target.cmake` files should contain.
43 settings in a file named :file:`my-toolchain.cmake`, you can then invoke cmake
46 Zephyr includes :file:`include/toolchain.h` which again includes a toolchain
50 based, for example ``llvm`` which then gets the :file:`toolchain/llvm.h` included.
51 This included file may though not be right for the custom toolchain. In order
[all …]
/Zephyr-latest/doc/build/kconfig/
Dsetting.rst65 initial configuration is produced by merging a :file:`*_defconfig` file for the
66 board with application settings, usually from :file:`prj.conf`. See
95 saved to :file:`zephyr/.config` in the build directory.
130 1. A ``BOARD``-specific configuration file stored in
131 :file:`boards/<VENDOR>/<BOARD>/<BOARD>_defconfig`
137 The application configuration can come from the sources below (each file is
139 configuration used for a particular build). By default, :file:`prj.conf` is
142 #. If ``CONF_FILE`` is set, the configuration file(s) specified in it are
146 1. In :file:`CMakeLists.txt`, before calling ``find_package(Zephyr)``
148 2. By passing ``-DCONF_FILE=<conf file(s)>``, either directly or via ``west``
[all …]
/Zephyr-latest/dts/bindings/fs/
Dzephyr,fstab-common.yaml13 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.

12345678910>>...128