Home
last modified time | relevance | path

Searched refs:has (Results 151 – 175 of 1361) sorted by relevance

12345678910>>...55

/Zephyr-4.1.0/samples/bluetooth/peripheral/
DREADME.rst10 Application demonstrating the Bluetooth LE Peripheral role. It has several well-known and
/Zephyr-4.1.0/samples/net/ipv4_autoconf/
DREADME.rst53 Once IPv4 LL has completed probing and announcement, details are shown like this:
66 To verify the Zephyr application is running and has configured an IP address
/Zephyr-4.1.0/boards/bbc/microbit_v2/doc/
Dindex.rst10 The board is 4 cm × 5 cm and has an ARM Cortex-M4F processor, accelerometer and
21 The micro:bit-v2 has the following physical features:
/Zephyr-4.1.0/dts/arm/nxp/
Dnxp_rt1010.dtsi55 /* Each channel has separate interrupt entry */
187 /* RT1010 has only one flexSPI controller */
190 /* Fixup FlexPWM1 it has different base addr and interrupt numbers on RT1010 */
245 /* Fixup USB it has different base addr and interrupt numbers on RT1010 */
275 /* Fix SAI1, 3, it has different base addr on RT1010 */
350 /* RT1015 only has two LPSPI blocks */
/Zephyr-4.1.0/boards/nordic/thingy52/doc/
Dindex.rst15 for the Thingy:52 board. The board has the nRF52832 MCU with ARM Cortex-M4F
51 Thingy:52 has the following features:
125 Thingy:52 has a pushbutton, connected to the P0.11 SOC GPIO pin.
130 By default the system UART has the following pin configuration:
257 Thing:52 has multiple power rails. The necessary rails for the currently
275 to power the CCS811 gas sensor, VDD has to be turned on first and VDD_CCS after
/Zephyr-4.1.0/doc/services/storage/nvs/
Dnvs.rst23 only calculated over the metadata and only ensures that a write has been
46 sufficient free space. NVS has a protection mechanism to avoid getting in a
65 - ``NVS_SECTOR_SIZE`` is the sector size, it has to be a multiple of
75 When writing data to flash a study of the flash wear is important. Flash has a
78 hardware. As an example a nRF51822 device has a pagesize of 1024 bytes and each
85 needs to be restored after reboot. NVS has been defined with a sector_size
/Zephyr-4.1.0/tests/drivers/flash/common/boards/
Dnrf52840dk_mx25r_high_perf.overlay24 has-dpd;
/Zephyr-4.1.0/drivers/gpio/
DKconfig.mmio329 is useful when an SoC or board has registers that aren't part of a
/Zephyr-4.1.0/drivers/dai/intel/alh/
DKconfig.alh19 bool "Intel ALH driver has ownership only on ACE 1.5"
/Zephyr-4.1.0/dts/arm/st/wb0/
Dstm32wb09.dtsi20 * STM32WB09 TRNG has an interrupt line.
/Zephyr-4.1.0/samples/boards/nordic/mesh/onoff-app/
DREADME.rst11 Each element has a mesh onoff client and server
41 This sample has been tested on the Nordic nRF52840-PDK board, but would
85 root element's unicast address as it is the only one that has a
94 that has that LED's model and issuing the onoff command.
/Zephyr-4.1.0/doc/kernel/services/data_passing/
Dstacks.rst20 A stack has the following key properties:
38 and prevent attempts to add a data value to a stack that has already reached
46 that has waited longest.
79 The following code has the same effect as the code segment above. Observe
/Zephyr-4.1.0/soc/intel/intel_adsp/cavs/
DKconfig.defconfig.cavs_v2510 # Hardware has four cores, limited to two pending test fixes
/Zephyr-4.1.0/boards/phytec/phyboard_lyra/
Dphyboard_lyra_am6234_a53.dts37 /* Note: This board actually has 2GB DRAM available */
/Zephyr-4.1.0/drivers/interrupt_controller/
DKconfig.esp32c319 interrupt allocator. This has no impact on the interrupt allocator usage
/Zephyr-4.1.0/cmake/compiler/xcc/
Dcompiler_flags.cmake5 # XCC is based on GCC 4.2 which has a somewhat pedantic take on the
/Zephyr-4.1.0/drivers/led_strip/
DKconfig.lpd880x14 Each LPD880x LED driver chip has some output channels
/Zephyr-4.1.0/doc/kernel/services/other/
Dfatal.rst82 It makes use of the ``__ASSERT()`` macro, but has some extra flexibility. It
129 This has the same semantics as C's ``_Static_assert`` or C++'s
183 If the CPU receives a hardware interrupt on an interrupt line that has not had
215 buffer has been corrupted. It does not require hardware support, but provides
223 canary has not been overwritten at function exit. If the check fails, the
226 that the entire stack buffer has overflowed, but instead that the current
227 function stack frame has been corrupted. See the compiler documentation for
241 function has a default implementation with weak linkage that calls
/Zephyr-4.1.0/doc/services/task_wdt/
Dindex.rst11 malfunctions. Once initialized, the watchdog timer has to be restarted ("fed")
22 watchdog itself or the scheduler has a malfunction.
/Zephyr-4.1.0/boards/renesas/da14695_dk_usb/doc/
Dindex.rst23 DA14695 Development Kit USB has two external oscillators. The frequency of
66 The DA14695 Development Kit USB has one LED and one push button which can be used
89 written to flash has to have proper header prepended. The process is simplified
/Zephyr-4.1.0/doc/build/dts/
Dintro-syntax-structure.rst37 syntax, which has replaced a now-obsolete "version 0".
42 Like any tree data structure, a devicetree has a hierarchy of *nodes*.
43 The above tree has three nodes:
52 the labeled node. Above, ``a-sub-node`` has the node label
70 Node ``a-sub-node`` has a property named ``foo``, whose value is a cell with
116 represents. For example, an I2C peripheral's node has a property whose value is
180 in the previous section has I2C address 0x39.
212 The node named ``partition@0`` has offset 0 from the start of its flash
249 Within Zephyr's bindings syntax, this property has type ``string-array``.
296 of one or more *interrupt specifiers*. Each interrupt specifier has some
[all …]
/Zephyr-4.1.0/soc/nordic/
DKconfig.defconfig10 # If the kernel has timer support, enable clock control, except for SoCs
/Zephyr-4.1.0/soc/snps/hsdk4xd/
DKconfig.defconfig19 # Actually cpu has 4 banks but zephys currently supports up to 2
/Zephyr-4.1.0/boards/snps/em_starterkit/support/
Dopenocd.cfg2 # EM Starter Kit has built-in FT2232 chip, which is similar to Digilent HS-1.
/Zephyr-4.1.0/cmake/toolchain/iar/
DKconfig.defconfig23 # IAR has slightly different types

12345678910>>...55