Searched refs:like (Results 326 – 350 of 517) sorted by relevance
1...<<1112131415161718192021
| /Zephyr-latest/doc/build/dts/ |
| D | bindings-intro.rst | 96 hardware on a bus, like I2C or SPI, then the bus type is also taken into
|
| /Zephyr-latest/doc/services/pm/ |
| D | system.rst | 12 The kernel requests an amount of time it would like to suspend, then the PM subsystem decides
|
| /Zephyr-latest/boards/shields/amg88xx/doc/ |
| D | index.rst | 151 When using the PAN1780 evaluation board the build invocation looks like this:
|
| /Zephyr-latest/boards/native/nrf_bsim/doc/ |
| D | nrf5340bsim.rst | 24 Just like for the nrf5340dk targets,
|
| /Zephyr-latest/boards/ezurio/pinnacle_100_dvk/doc/ |
| D | index.rst | 20 Bluetooth 5 sensor data to cloud services like AWS IoT over a
|
| /Zephyr-latest/drivers/clock_control/ |
| D | Kconfig.nrf | 117 Enables retrieving debug information like number of performed or
|
| /Zephyr-latest/tests/subsys/logging/log_blocking/ |
| D | REAME.md | 52 comforting to know, even if it is something astronomical like 1G `[msg/s]`.
|
| /Zephyr-latest/samples/philosophers/ |
| D | README.rst | 72 tools like OpenOCD and J-link to inspect thread data using ``info threads``.
|
| /Zephyr-latest/samples/modules/thrift/hello/ |
| D | README.rst | 121 Build the Zephyr version of the ``hello/server`` sample application like this:
|
| /Zephyr-latest/boards/amd/kv260_r5/doc/ |
| D | index.rst | 109 the Zephyr application ``.elf`` file using utility like the ``scp`` or ``rsync``,
|
| /Zephyr-latest/boards/nxp/imx95_evk/doc/ |
| D | index.rst | 247 multiple elements required, like ELE+V2X firmware, System Manager, TCM OEI, Cortex-M7
277 board. For the ``imx95_evk/mimx9596/m7`` board you should see something like:
|
| /Zephyr-latest/doc/kernel/memory_management/ |
| D | heap.rst | 147 a :c:func:`malloc`-like manner.
227 :c:func:`malloc`-like manner.
|
| /Zephyr-latest/doc/develop/test/ |
| D | pytest.rst | 50 file can look like the following:
67 configuration file may look like this:
|
| /Zephyr-latest/samples/subsys/logging/syst/ |
| D | README.rst | 61 The :file:`/tmp/syst` should contain something like this:
232 The :file:`/tmp/syst` should contain something like this:
|
| /Zephyr-latest/boards/intel/adsp/doc/ |
| D | chromebooks_adsp.rst | 8 arbitrary user-developed firmware like Zephyr applications (of which
191 doesn't own the system!) so Ubuntu services like openssh-server don't
308 You can verify this image if you like with "vbutil_kernel --verify".
|
| /Zephyr-latest/arch/xtensa/core/ |
| D | README_MMU.txt | 131 like a design flaw).
212 The ASID mechanism in Xtensa works like other architectures, and is
242 like any other CPU memory access, and in particular it is governed by
|
| /Zephyr-latest/doc/kernel/drivers/ |
| D | index.rst | 133 A subsystem API definition typically looks like this:
196 A device-specific API definition typically looks like this:
593 Some drivers or driver-like code may not user Zephyr's device model,
|
| /Zephyr-latest/soc/nordic/ |
| D | Kconfig | 94 pins as GPIOS like this:
|
| /Zephyr-latest/soc/nxp/imxrt/ |
| D | Kconfig | 104 useful if your application expects components like SDRAM to be
|
| /Zephyr-latest/scripts/ci/ |
| D | pylintrc | 61 # message "types" (~= severities) like F(atal), E(error),... are listed
|
| /Zephyr-latest/include/zephyr/arch/nios2/ |
| D | linker.ld | 183 * This is code not data, but we need this copied just like XIP data
|
| /Zephyr-latest/boards/pjrc/teensy4/doc/ |
| D | index.rst | 320 #. After application startup a serial device named like
|
| /Zephyr-latest/boards/renesas/ek_ra8d1/doc/ |
| D | index.rst | 136 like so:
|
| /Zephyr-latest/boards/renesas/ek_ra8m1/doc/ |
| D | index.rst | 119 like so:
|
| /Zephyr-latest/subsys/net/l2/ethernet/ |
| D | Kconfig | 74 get IPv4 working (like Ethernet devices).
|
1...<<1112131415161718192021
