Searched refs:configuration (Results 1 – 25 of 2311) sorted by relevance
12345678910>>...93
| /Zephyr-Core-3.5.0/boards/arm/mimxrt1020_evk/ |
| D | CMakeLists.txt | 13 "update your flash configuration or device configuration data blocks")
18 # Include flash configuration block for RT1020 EVK from NXP's HAL.
19 # This configuration block may need modification if another flash chip is
27 # Include device configuration data block for RT1020 EVK from NXP's HAL.
28 # This configuration block may need modification if another SDRAM chip
35 "configuration data (DCD) is included. This configuration may not boot")
|
| /Zephyr-Core-3.5.0/boards/arm/mimxrt1024_evk/ |
| D | CMakeLists.txt | 13 "update your flash configuration or device configuration data blocks")
18 # Include flash configuration block for RT1024 EVK from NXP's HAL.
19 # This configuration block may need modification if another flash chip is
27 # Include device configuration data block for RT1024 EVK from NXP's HAL.
28 # This configuration block may need modification if another SDRAM chip
35 "configuration data (DCD) is included. This configuration may not boot")
|
| /Zephyr-Core-3.5.0/boards/arm/mimxrt1040_evk/ |
| D | CMakeLists.txt | 13 "update your flash configuration or device configuration data blocks")
18 # Include flash configuration block for RT1040 EVK from NXP's HAL.
19 # This configuration block may need modification if another flash chip is
27 # Include device configuration data block for RT1040 EVK from NXP's HAL.
28 # This configuration block may need modification if another SDRAM chip
35 "configuration data (DCD) is included. This configuration may not boot")
|
| /Zephyr-Core-3.5.0/scripts/net/ |
| D | run-sample-tests.sh | 10 configuration=""
234 if [ "$docker_pid" -ne 0 -a "$configuration" != "keep" ]; then
302 additional configuration/overlay files for the Zephyr build process
343 if [ -n "$configuration" ]; then
347 configuration=start_only
350 if [ -n "$configuration" ]; then
354 configuration=stop_only
357 configuration=keep
392 if [ -z "$configuration" -o "$configuration" = "start_only" -o \
393 "$configuration" = "keep" ]; then
[all …]
|
| /Zephyr-Core-3.5.0/boards/arm/mimxrt1050_evk/ |
| D | CMakeLists.txt | 22 "update your flash configuration or device configuration data blocks")
23 # Default EVK configuration uses hyperflash, so use that file
29 # Include flash configuration block for RT1050 EVK from NXP's HAL.
30 # This configuration block may need modification if another flash chip is
38 # Include device configuration data block for RT1050 EVK from NXP's HAL.
39 # This configuration block may need modification if another SDRAM chip
46 "configuration data (DCD) is included. This configuration may not boot")
|
| /Zephyr-Core-3.5.0/boards/arm64/fvp_baser_aemv8r/doc/ |
| D | debug-with-arm-ds.rst | 37 Create a new configuration database
40 Create a new configuration database by selecting ``File -> New -> Other... -> Configuration Databas…
42 .. image:: images/create-new-configuration-database.jpg
44 :alt: Arm DS create new configuration database
48 .. image:: images/create-new-configuration-database_database-name.jpg
50 :alt: Arm DS create new configuration database: choose database name
52 Click ``Finish`` and the new configuration database can be seen in ``Project Explorer``:
54 .. image:: images/create-new-configuration-database_shown-in-project-explorer.jpg
56 :alt: Arm DS create new configuration database: shown in project explorer
58 Create a new model configuration
[all …]
|
| /Zephyr-Core-3.5.0/boards/arm/mimxrt1160_evk/ |
| D | CMakeLists.txt | 13 "update your flash configuration or device configuration data blocks")
18 # Include flash configuration block for RT1160 EVK from NXP's HAL.
19 # This configuration block may need modification if another flash chip is
27 # Include device configuration data block for RT1160 EVK from NXP's HAL.
28 # This configuration block may need modification if another SDRAM chip
35 "configuration data (DCD) is included. This configuration may not boot")
|
| /Zephyr-Core-3.5.0/boards/arm/mimxrt1060_evk/ |
| D | CMakeLists.txt | 19 # No flash configuration block exists for the RT1060 with HyperFlash in
30 "update your flash configuration or device configuration data blocks")
31 # Default EVK configuration uses qspi, so use that file
38 # Include flash configuration block for RT1060 EVK from NXP's HAL.
39 # This configuration block may need modification if another flash chip is
47 # Include device configuration data block for RT1060 EVK from NXP's HAL.
48 # This configuration block may need modification if another SDRAM chip
55 "configuration data (DCD) is included. This configuration may not boot")
|
| /Zephyr-Core-3.5.0/boards/arm/mimxrt1064_evk/ |
| D | CMakeLists.txt | 18 "update your flash configuration or device configuration data blocks")
23 # Include flash configuration block for RT1064 EVK from NXP's HAL.
24 # This configuration block may need modification if another flash chip is
32 # Include device configuration data block for RT1064 EVK from NXP's HAL.
33 # This configuration block may need modification if another SDRAM chip
40 "configuration data (DCD) is included. This configuration may not boot")
|
| /Zephyr-Core-3.5.0/boards/arm/mimxrt1170_evk/ |
| D | CMakeLists.txt | 15 "update your flash configuration or device configuration data blocks")
27 # Include flash configuration block for RT1170 EVK from NXP's HAL.
28 # This configuration block may need modification if another flash chip is
36 # Include device configuration data block for RT1170 EVK from NXP's HAL.
37 # This configuration block may need modification if another SDRAM chip
44 "configuration data (DCD) is included. This configuration may not boot")
|
| /Zephyr-Core-3.5.0/doc/build/kconfig/ |
| D | setting.rst | 3 Setting Kconfig configuration values
26 up in the interactive configuration interfaces (hence *visible*), and can be
27 set in configuration files.
44 not shown in the interactive configuration interfaces, and users have no
61 Setting symbols in configuration files
64 Visible symbols can be configured by setting them in configuration files. The
65 initial configuration is produced by merging a :file:`*_defconfig` file for the
69 Assignments in configuration files use this syntax:
94 This is the format you will see in the merged configuration in
97 This style is accepted for historical reasons: Kconfig configuration files
[all …]
|
| D | index.rst | 8 Kconfig, which is the same configuration system used by the Linux kernel. The
9 goal is to support configuration without having to change any source code.
14 keep the interactive configuration interfaces organized.
20 The following sections explain how to set Kconfig configuration options, go
33 Users interested in optimizing their configuration for security should refer
|
| /Zephyr-Core-3.5.0/doc/connectivity/bluetooth/api/mesh/ |
| D | cfg.rst | 6 The runtime configuration API allows applications to change their runtime
7 configuration directly, without going through the Configuration models.
12 Configuration Client can communicate with to change the node configuration. In some
15 scenarios, this API can be used to change the configuration locally.
18 Runtime configuration changes before the node is provisioned will not be stored
|
| /Zephyr-Core-3.5.0/boards/arm64/xenvm/doc/ |
| D | index.rst | 10 ARM Virtualization Extensions. This is example configuration, as almost any VM
11 configuration is unique in many aspects.
35 The default configuration using GICv2 can be found in the defconfig file:
38 The default configuration using GICv3 can be found in the defconfig file:
46 This board configuration uses a system clock frequency of 8.32 MHz. This is the
68 Default core in this configuration is Cortex A72. Depending on yours actual
70 Controller configuration.
76 environment. On other hand, Zephyr uses static configuration that should be know
78 configuration would not boot on your hardware. In this case you need to update
79 configuration by altering device tree and Kconfig options. This will be covered
[all …]
|
| /Zephyr-Core-3.5.0/boards/arm/mimxrt1062_fmurt6/ |
| D | CMakeLists.txt | 10 # No flash configuration block exists for the RT1060 with HyperFlash in
19 # Include flash configuration block for RT1050 EVK from NXP's HAL.
20 # This configuration block may need modification if another flash chip is
28 # Include device configuration data block for RT1050 EVK from NXP's HAL.
29 # This configuration block may need modification if another SDRAM chip
|
| /Zephyr-Core-3.5.0/boards/arm64/qemu_kvm_arm64/doc/ |
| D | index.rst | 9 This board configuration will use QEMU to run a KVM guest on an AArch64
12 This configuration provides support for an AArch64 Cortex-A CPU and these
43 This board configuration uses the host system clock frequency.
48 This board configuration uses a single serial communication channel with the
|
| /Zephyr-Core-3.5.0/subsys/lorawan/nvm/ |
| D | Kconfig | 1 # LoRaWAN Non Volatile Memory configuration options
14 If this configuration is used, it is the responsibility of the
17 join configuration directly.
|
| /Zephyr-Core-3.5.0/boards/xtensa/esp32s3_devkitm/support/ |
| D | openocd.cfg | 4 # Source the JTAG interface configuration file
6 # Source the ESP32-S3 configuration file
|
| /Zephyr-Core-3.5.0/boards/xtensa/xiao_esp32s3/support/ |
| D | openocd.cfg | 4 # Source the JTAG interface configuration file
6 # Source the ESP32-S3 configuration file
|
| /Zephyr-Core-3.5.0/boards/xtensa/esp32s3_luatos_core/support/ |
| D | openocd.cfg | 4 # Source the JTAG interface configuration file
6 # Source the ESP32-S3 configuration file
|
| /Zephyr-Core-3.5.0/boards/arm/ubx_bmd345eval_nrf52840/ |
| D | Kconfig | 1 # BMD-345-EVAL board configuration
7 # No special configuration is required.
|
| /Zephyr-Core-3.5.0/modules/ |
| D | Kconfig.simplelink | 1 # CC3220/CC32XX SDK HAL configuration
22 # MSP432 SDK HAL configuration
28 # CC13X2 / CC26X2 SDK HAL configuration
|
| /Zephyr-Core-3.5.0/boards/xtensa/esp32_net/ |
| D | Kconfig.board | 1 # ESP32 board configuration
7 bool "ESP32 Board configuration for APP_CPU"
|
| /Zephyr-Core-3.5.0/boards/arm/rpi_pico/ |
| D | board.cmake | 3 # This configuration allows selecting what debug adapter debugging rpi_pico
7 # And any other SWD debug adapter might also be usable with this configuration.
12 # the debugger's configuration file.
14 # in the openocd interface configuration file.
24 # The adapter speed is expected to be set by interface configuration.
|
| /Zephyr-Core-3.5.0/boards/arm/nucleo_wl55jc/support/ |
| D | openocd.cfg | 7 # Debug compatible reset configuration (default)
10 # Sleep mode compatible reset configuration (stock firmware compatible)
|
12345678910>>...93
