Searched refs:configuration (Results 1 – 25 of 2609) sorted by relevance
12345678910>>...105
| /Zephyr-latest/doc/connectivity/bluetooth/shell/audio/ |
| D | gmap.rst | 23 ac_1 : Unicast audio configuration 1
24 ac_2 : Unicast audio configuration 2
25 ac_3 : Unicast audio configuration 3
26 ac_4 : Unicast audio configuration 4
27 ac_5 : Unicast audio configuration 5
28 ac_6_i : Unicast audio configuration 6(i)
29 ac_6_ii : Unicast audio configuration 6(ii)
30 ac_7_ii : Unicast audio configuration 7(ii)
31 ac_8_i : Unicast audio configuration 8(i)
32 ac_8_ii : Unicast audio configuration 8(ii)
[all …]
|
| /Zephyr-latest/boards/nxp/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-latest/boards/nxp/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-latest/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-latest/boards/nxp/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-latest/boards/arm/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-latest/boards/nxp/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-latest/boards/nxp/mimxrt1060_evk/ |
| D | CMakeLists.txt | 22 # 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-latest/tests/drivers/gnss/gnss_api/ |
| D | Kconfig | 7 int "Enabled systems configuration 0"
12 int "Enabled systems configuration 1"
17 int "Enabled systems configuration 2"
22 int "Enabled systems configuration 3"
|
| /Zephyr-latest/boards/nxp/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-latest/boards/nxp/mimxrt1040_evk/ |
| D | CMakeLists.txt | 18 "update your flash configuration or device configuration data blocks")
23 # Include flash configuration block for RT1040 EVK from NXP's HAL.
24 # This configuration block may need modification if another flash chip is
32 # Include device configuration data block for RT1040 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-latest/boards/nxp/mimxrt1170_evk/ |
| D | CMakeLists.txt | 13 "update your flash configuration or device configuration data blocks")
23 # Include flash configuration block for RT1170 EVK from NXP's HAL.
24 # This configuration block may need modification if another flash chip is
32 # Include external memory configuration data block for RT1170 EVK from NXP's HAL.
33 # This configuration block may need modification if another SDRAM chip
40 "configuration data (XMCD) is included. This configuration may not boot")
|
| /Zephyr-latest/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-latest/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
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-latest/boards/xen/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 for this board can be found in these files:
45 This board configuration uses a system clock frequency of 8.32 MHz. This is the
59 following board configuration variants:
67 Default core in this configuration is Cortex A72. Depending on yours actual
69 Controller configuration.
75 environment. On other hand, Zephyr uses static configuration that should be know
77 configuration would not boot on your hardware. In this case you need to update
78 configuration by altering device tree and Kconfig options. This will be covered
[all …]
|
| /Zephyr-latest/boards/nxp/mimxrt1180_evk/ |
| D | CMakeLists.txt | 15 "update your flash configuration or device configuration data blocks")
20 # Include flash configuration block for RT1180 EVK from NXP's HAL.
21 # This configuration block may need modification if another flash chip is
|
| /Zephyr-latest/soc/nxp/mcx/mcxc/ |
| D | Kconfig | 25 bool "MCXC flash configuration field"
28 Include the 16-byte flash configuration field that stores default
44 and clock configuration of the watchdog at boot is SOC dependent.
47 the SOC requires watchdog configuration before initial expiration
49 # Enable watchdog configuration function if watchdog is left enabled at boot
|
| /Zephyr-latest/boards/nxp/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-latest/boards/qemu/kvm_arm64/doc/ |
| D | index.rst | 6 This board configuration will use QEMU to run a KVM guest on an AArch64
9 This configuration provides support for an AArch64 Cortex-A CPU and these
40 This board configuration uses the host system clock frequency.
45 This board configuration uses a single serial communication channel with the
|
| /Zephyr-latest/tests/drivers/can/host/ |
| D | README.rst | 29 The host end of the CAN fixture can be configured through python-can. Available configuration
31 flexibility for configuration as decribed in the `python-can configuration`_ page, all centered
32 around the concept of a configuration "context. The configuration context for this test suite can be
35 * By default, the python-can configuration context is not specified, causing python-can to use the
36 default configuration context.
37 * A specific configuration context can be provided along with the ``can`` fixture separated by a
38 ``:`` (i.e. specify fixture ``can:zcan0`` to use the ``zcan0`` python-can configuration context).
39 * The configuration context can be overridden using the ``--can-context`` test suite argument
41 python-can configuration context).
61 dedicated ``zcan0`` context in the ``~/.canrc`` configuration file as shown here:
[all …]
|
| /Zephyr-latest/boards/seeed/xiao_esp32s3/support/ |
| D | openocd.cfg | 4 # Source the JTAG interface configuration file
6 # Source the ESP32-S3 configuration file
|
| /Zephyr-latest/boards/heltec/heltec_wireless_stick_lite_v3/support/ |
| D | openocd.cfg | 4 # Source the JTAG interface configuration file
6 # Source the ESP32-S3 configuration file
|
| /Zephyr-latest/boards/luatos/esp32s3_luatos_core/support/ |
| D | openocd.cfg | 4 # Source the JTAG interface configuration file
6 # Source the ESP32-S3 configuration file
|
| /Zephyr-latest/boards/adafruit/qt_py_esp32s3/support/ |
| D | openocd.cfg | 4 # Source the JTAG interface configuration file
6 # Source the ESP32-S3 configuration file
|
12345678910>>...105
