Searched refs:like (Results 151 – 175 of 517) sorted by relevance
12345678910>>...21
| /Zephyr-latest/doc/build/sysbuild/ |
| D | images.rst | 92 This image can be enabled when building with west like so:
178 This secondary image can be enabled when building with west like so:
189 This can then be extended by :ref:`modules` like so:
220 This alternative secondary image can be enabled when building with west like so:
285 which allows sysbuild to be the central location for things like the signing key which are then
|
| /Zephyr-latest/doc/develop/west/ |
| D | built-in.rst | 132 Some branch names might look like short SHAs, like ``deadbeef``. West treats
133 these like SHAs. You can disambiguate by prefixing the ``revision`` value with
151 If you would like ``west update`` to keep local branches checked out as
171 does not even try to rebase and leaves your branches behind just like a
|
| D | without-west.rst | 81 Running build system targets like ``ninja flash``, ``ninja debug``,
123 line like ``west build -t flash``. In that case, west is run twice:
|
| /Zephyr-latest/samples/subsys/usb/shell/ |
| D | README.rst | 18 built like:
|
| /Zephyr-latest/subsys/fs/zms/ |
| D | Kconfig | 14 It supports classical on-chip NOR flash as well as new technologies like RRAM and MRAM.
|
| /Zephyr-latest/subsys/mgmt/mcumgr/mgmt/ |
| D | Kconfig | 7 # directory, like management group registration or overall hooks support.
|
| /Zephyr-latest/doc/services/modem/ |
| D | index.rst | 20 a variety of mechanisms, like UART and CMUX DLCI channels, in a
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | net_shell.rst | 7 enabling/disabling features, and issuing commands like ping or DNS resolving.
|
| /Zephyr-latest/dts/arm/st/f1/ |
| D | stm32f103Xg.dtsi | 6 * where 'x' is replaced for specific SoCs like {R,V,Z}
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | i2c.rst | 31 the most common mode, used to interact with I2C devices like sensors and
|
| D | rtc.rst | 45 features missing, like input clock calibration and the update
135 The emulated RTC device fully implements the RTC API, and will behave like a real
|
| /Zephyr-latest/samples/net/vlan/ |
| D | README.rst | 26 file when running :file:`net-setup.sh` script in Linux like this:
|
| /Zephyr-latest/samples/drivers/adc/adc_dt/ |
| D | README.rst | 30 Configuration of channels (settings like gain, reference, or acquisition time)
|
| /Zephyr-latest/samples/drivers/adc/adc_sequence/ |
| D | README.rst | 24 child node, with your desired settings like gain, reference, or acquisition time and
|
| /Zephyr-latest/samples/subsys/modbus/rtu_client/ |
| D | README.rst | 24 An Arduino header compatible shield like `joy-it RS-485 shield for Arduino`_
|
| /Zephyr-latest/samples/boards/intel/adsp/code_relocation/ |
| D | linker_xtensa_intel_adsp_cavs.ld | 15 * usage), they are laid out like this:
|
| /Zephyr-latest/lib/posix/options/getopt/ |
| D | README | 12 [Shell users would like to parse options passed to the command handler.]
|
| /Zephyr-latest/doc/hardware/porting/ |
| D | board_porting.rst | 171 like the :ref:`thingy52_nrf52832` contains a single SoC with no CPU clusters and
255 Your board directory should look like this:
375 In general, :file:`plank.dts` should look like this:
417 &some_peripheral_you_want_to_enable { /* like a GPIO or SPI controller */
530 A :file:`Kconfig.plank` may look like this:
549 a prompt, like this:
566 lines, like this:
596 something like this:
643 - If your board uses a well-known connector standard (like Arduino, Mikrobus,
654 For boards like :ref:`nRF52840 Dongle <nrf52840dongle_nrf52840>`, that do not
[all …]
|
| /Zephyr-latest/subsys/lorawan/services/ |
| D | Kconfig | 114 For some MCUs like the STM32WL the fragment size has to be a multiple
135 For some MCUs like the STM32WL the fragment size has to be a multiple
|
| /Zephyr-latest/doc/releases/ |
| D | migration-guide-4.2.rst | 124 but there is no size increase for other network technologies like Ethernet.
126 which has checks like ``if (lladdr->addr == NULL)``, will no longer work as expected
|
| /Zephyr-latest/arch/x86/zefi/ |
| D | README.txt | 8 device's EFI boot partition via whatever means you like and run it
22 binary into memory and copy it vs. a bootloader like grub that will
|
| /Zephyr-latest/cmake/sca/eclair/ECL/ |
| D | zephyr_common_config.ecl | 37 -doc_begin="The following function-like macros are not writable as inline functions."
45 -doc_begin="For the following function-like macros it should be decided whether substitution with e…
|
| /Zephyr-latest/doc/build/signing/ |
| D | index.rst | 50 should see something like this on your device's serial console when you run
67 would like it to, please send a patch or file an issue for adding support.
|
| /Zephyr-latest/samples/net/mqtt_sn_publisher/ |
| D | README.rst | 17 on any datagram-based transport like UDP, ZigBee or even a plain UART
34 - MQTT-SN gateway, like Eclipse Paho
|
| /Zephyr-latest/boards/native/doc/ |
| D | bsim_boards_design.rst | 53 least, run with the Zephyr RTOS just like for any other
111 that platform. Just like the bsim boards, this Zephyr target board can
146 When you target a multi MCU SOC like the :ref:`nrf5340bsim<nrf5340bsim_multi_mcu_build>`, you can
177 functionality like bs_tests hooks, trace control, etc, and
323 This can be used to support the test logic, like run checks or perform actions
335 Note also that, for AMP targets like the :ref:`nrf5340bsim <nrf5340bsim>`, each embedded MCU has
345 - Basic arguments: to enable selecting things like trace verbosity, random seed,
|
12345678910>>...21
