Searched refs:file (Results 1 – 9 of 9) sorted by relevance
| /nrf_hw_models-latest/ |
| D | CMakeLists.txt | 4 # CMake file to compile this BabbleSim component as a west module in Zephyr
35 file(STRINGS make_inc/52833_hw_files HW_MODEL_SRCS)
36 file(STRINGS make_inc/52833_hal_files HAL_SRCS)
42 file(STRINGS make_inc/5340_hw_files HW_MODEL_SRCS)
45 file(STRINGS make_inc/5340_net_hal_files HAL_SRCS)
51 file(STRINGS make_inc/5340_app_hal_files HAL_SRCS)
58 file(STRINGS make_inc/54L15_hw_files HW_MODEL_SRCS)
59 file(STRINGS make_inc/54L15_app_hal_files HAL_SRCS)
|
| /nrf_hw_models-latest/docs/ |
| D | GPIO.md | 21 * From an input stimuli file (`-gpio_in_file=<path>`). Which follows the stimuli format
24 * By shortcuiting the input and output, either set from a configuration file
30 It is possible to have the GPIOs output activity dumped into a file.
32 Any toggle in any pin configured as an output will be dumped to that file, following the
33 stimuli file format described below.
62 ### Stimuli file format
64 This is a comma separated file (.csv), with 4 columns: time,port,pin,level. Where:
86 ### Configuration file format
88 The configuration file can define output->input short-circuits.
94 The configuration file is made of lines, each with the following format, either:
|
| D | UART.md | 19 Each UART can be configured to log to a file the Tx and/or Rx bytes.
20 Enabling this and selecting the file is done with command line options.
21 When enabled, the model will dump one line in this file per byte, with two columns:
30 [the UART header file](../src/HW_models/NHW_UART.h) for more info.
81 To do this, just configure the same FIFO file name for both the Rx and Tx, for example like:
|
| D | LICENSE | 5 BSD-3-Clause licensed. Please see each respective file for license information.
113 (d) If the Work includes a "NOTICE" text file as part of its
116 within such NOTICE file, excluding those notices that do not
118 of the following places: within a NOTICE text file distributed
123 of the NOTICE file are for informational purposes only and
148 origin of the Work and reproducing the content of the NOTICE file.
191 comment syntax for the file format. We also recommend that a
192 file or class name and description of purpose be included on the
199 you may not use this file except in compliance with the License.
|
| D | README_HW_models.md | 7 This file is a particularized version of the first sections of
11 section after reading this file, for further information.
128 The actual HW models of the SOC peripherals are normally split in one file per peripheral.
|
| /nrf_hw_models-latest/src/HW_models/ |
| D | NHW_NVM_backend.h | 30 char *file; member
51 .dest = (void*)&nvmc_args. arg .file, \
59 .dest = (void*)&nvmc_args. arg . file, \
|
| D | NHW_NVM_backend.c | 76 st->file_path = args->file; in nhw_nvm_init_storage()
|
| /nrf_hw_models-latest/src/nrfx_config/ |
| D | nrfx_config.h | 15 #error This file should not be included in builds with Zephyr. Use the one provided by the nordic_h…
|
| D | nrfx_glue.h | 19 #error This file should not be included in builds with Zephyr. Use the one provided by the nordic_h…
|
