Searched refs:have (Results 1 – 25 of 909) sorted by relevance
12345678910>>...37
| /Zephyr-Core-3.7.0/soc/intel/intel_adsp/ace/ |
| D | Kconfig.defconfig.ace30_ptl | 17 # Need to have enough to accommodate samples and tests.
18 # Also need to have some room for future expansions or
|
| /Zephyr-Core-3.7.0/tests/bsim/bluetooth/host/privacy/device/ |
| D | README.rst | 12 type. That, even if they have previously exchanged IRK; (Core Specification version 5.4, vol. 1
14 * After devices have exchanged IRK, they must correctly resolve RPA when receiving packets from the
|
| /Zephyr-Core-3.7.0/lib/smf/ |
| D | Kconfig | 12 bool "States to have 1 or more ancestors"
20 If y, then each state can have an initial transition to a sub-state
|
| /Zephyr-Core-3.7.0/doc/develop/toolchains/ |
| D | designware_arc_mwdt.rst | 6 #. You need to have `ARC MWDT <https://www.synopsys.com/dw/ipdir.php?ds=sw_metaware>`_ installed on
9 #. You need to have :ref:`Zephyr SDK <toolchain_zephyr_sdk>` installed on your host.
28 If you have only one ARC MWDT toolchain version installed on your machine you may skip setting
31 #. To check that you have set these variables correctly in your current
|
| D | other_x_compilers.rst | 13 :ref:`toolchains`, the Zephyr build system may not have been
36 toolchain's binaries have, e.g. the path to the directory containing the
39 #. To check that you have set these variables correctly in your current
54 directory and have a common file name prefix. The ``CROSS_COMPILE`` variable
|
| /Zephyr-Core-3.7.0/boards/snps/em_starterkit/ |
| D | Kconfig.em_starterkit | 14 Both version 2.2 and 2.3 firmware have EM7D, EM9D and EM11D configurations.
16 EM7D and EM11D have access to 128MB DRAM and use i-cache and d-cache.
|
| /Zephyr-Core-3.7.0/scripts/coccinelle/ |
| D | boolean.cocci | 49 msg = "WARNING: Violation to rule 14.4 (Controlling expression shall have essentially Boolean type)"
78 msg = "WARNING: Violation to rule 14.4 (Controlling expression shall have essentially Boolean type)"
99 msg = "WARNING: Violation to rule 14.4 (Controlling expression shall have essentially Boolean type)"
|
| /Zephyr-Core-3.7.0/soc/native/inf_clock/ |
| D | Kconfig | 26 How many AMP MCUs does this target have in total.
34 This MCU will for example have its tests command line parameters presented
42 This option can be used to provide the native simulator with other MCUs/Cores images which have
45 have it produce the final link with the native simulator runner and the other MCU images.
|
| /Zephyr-Core-3.7.0/doc/hardware/peripherals/sensor/ |
| D | channels.rst | 9 Sensors may have multiple channels, either to represent different axes of
12 humidity). Sensors may have multiple channels of the same measurement type to
|
| /Zephyr-Core-3.7.0/boards/nxp/frdm_mcxn947/ |
| D | frdm_mcxn947_mcxn947_cpu0.dts | 38 * application can have an application specific device tree to
42 * for cpu1. This would require the value of sram0 to have a DT_SIZE_K
43 * of 384. You would have to make updates to cpu1 sram settings as well.
|
| /Zephyr-Core-3.7.0/samples/sensor/ds18b20/ |
| D | README.rst | 22 The devicetree must have an enabled node with ``compatible = "maxim,ds18b20";``.
35 Your board may have a DS18B20 node configured in its devicetree by default,
47 Make sure that you have an external circuit to provide an open-drain interface
49 Once you have wired the sensor and the serial peripheral on the Arduino header
|
| /Zephyr-Core-3.7.0/boards/nxp/lpcxpresso55s69/ |
| D | lpcxpresso55s69_lpc55s69_cpu1.dts | 30 * application can have an application specific device tree to
35 * to be changed to sram4 and the value of sram0 to have a DT_SIZE_K
|
| /Zephyr-Core-3.7.0/tests/drivers/counter/counter_basic_api/boards/ |
| D | nrf54h20dk_nrf54h20_cpuppr.overlay | 5 /* PPR does not have interrupts for fast peripherals. */
|
| /Zephyr-Core-3.7.0/doc/kernel/services/synchronization/ |
| D | events.rst | 19 whose wait conditions have been satisfied become ready simultaneously.
23 * A 32-bit value that tracks which events have been delivered to it.
31 posting. Both posting and setting events have the potential to fulfill match
33 match conditions have been met are made active at the same time.
37 have the option of resetting the current set of events tracked by the event
158 Use events to indicate that a set of conditions have occurred.
|
| /Zephyr-Core-3.7.0/tests/boot/test_mcuboot/swapped_app/ |
| D | Kconfig | 4 # Workaround for not being able to have commas in macro arguments
|
| /Zephyr-Core-3.7.0/arch/ |
| D | CMakeLists.txt | 3 # FIXME: SHADOW_VARS: Remove this once we have enabled -Wshadow globally.
|
| /Zephyr-Core-3.7.0/.github/ISSUE_TEMPLATE/ |
| D | 001_bug_report.md | 28 - What have you tried to diagnose or workaround this issue?
29 - Is this a regression? If yes, have you been able to "git bisect" it to a
50 What impact does this issue have on your progress (e.g., annoyance, showstopper)
|
| /Zephyr-Core-3.7.0/tests/boards/espressif_esp32/rtc_clk/ |
| D | README.rst | 10 Espressif SOCs have 3 main clock subsystems: CPU, RTC_FAST and RTC_SLOW. Each of these subsystems h…
24 Make sure you have the target connected over USB port.
|
| /Zephyr-Core-3.7.0/doc/connectivity/bluetooth/api/audio/shell/ |
| D | bap_scan_delegator.rst | 5 in the examples below, some lines of debug have been
11 The Scan Delegator server typically resides on devices that have inputs or
14 It is necessary to have
|
| /Zephyr-Core-3.7.0/doc/hardware/peripherals/eeprom/ |
| D | index.rst | 9 EEPROMs have an erase block size of 1 byte, a long lifetime, and allow
|
| /Zephyr-Core-3.7.0/tests/kernel/mp/ |
| D | Kconfig | 5 # Must have this on where available, otherwise the linker will place
|
| /Zephyr-Core-3.7.0/boards/shields/esp_8266/doc/ |
| D | index.rst | 53 all connections. Make sure that the board you are using have all
57 available at Espressif Systems web site. The ESP-01 module have up to 1MB of
62 The ESP-8266 Modules that have 2MB or more is highly recommended upgrade to
80 you module have 26MHz crystal to detect boot fails.
83 Boards that already have a network interface: Check network
|
| /Zephyr-Core-3.7.0/doc/security/ |
| D | reporting.rst | 14 view the issues that they have reported.
52 - New: This state represents new reports that have been entered
117 numbers that have been assigned to the issue. The developer instead
136 have been fixed. After the embargo period, the vulnerabilities page
145 vetted by the project director to determine that they have a
157 When issues have been triaged, this list will be informed of:
200 important to share details and fixes only with those parties that have
204 - Maintainers will have access to all information within their domain
210 - The Project Security Incident Response (PSIRT) team will have full
|
| D | secure-coding.rst | 6 Traditionally, microcontroller-based systems have not placed much
8 They have usually been thought of as isolated, disconnected
12 the internet, or at least to other devices (that may themselves have
37 need to have. This section gives references to other security
41 should have. This knowledge will be necessary for the review process
87 program, and thread, shall have the smallest possible subset
137 The Zephyr project must have at least one primary developer who knows
193 initiated the project (and have not left the project more than three
194 years ago), have the option of receiving information on a private
246 shall have the ability to block the change from being merged into the
[all …]
|
| /Zephyr-Core-3.7.0/tests/boards/espressif_esp32/cache_coex/ |
| D | README.rst | 12 value. By the end of the thread iterations, both PSRAM and SPI Flash have its contents compared aga…
24 Make sure you have the target connected over USB port.
|
12345678910>>...37
