Searched refs:will (Results 1226 – 1250 of 1633) sorted by relevance
1...<<41424344454647484950>>...66
| /Zephyr-latest/boards/dptechnics/walter/doc/ |
| D | index.rst | 187 With ``--sysbuild`` option the bootloader will be re-build and re-flash
213 The usual ``flash`` target will work with the ``walter`` board
|
| /Zephyr-latest/boards/espressif/esp32c3_devkitc/doc/ |
| D | index.rst | 168 With ``--sysbuild`` option the bootloader will be re-build and re-flash
194 The usual ``flash`` target will work with the ``esp32c3_devkitc`` board
|
| /Zephyr-latest/boards/espressif/esp32c3_devkitm/doc/ |
| D | index.rst | 168 With ``--sysbuild`` option the bootloader will be re-build and re-flash
194 The usual ``flash`` target will work with the ``esp32c3_devkitm`` board
|
| /Zephyr-latest/doc/develop/west/ |
| D | west-apis.rst | 81 True if reading the manifest property will succeed instead of erroring
95 True if reading the config property will succeed instead of erroring
182 ``west.log`` module to a per-command interface that will allow for a global
|
| /Zephyr-latest/boards/raspberrypi/rpi_pico/doc/ |
| D | index.rst | 257 a UF2 file. By default, building an app for this board will generate a
259 button pressed, it will appear on the host as a mass storage device. The
260 UF2 file should be drag-and-dropped to the device, which will flash the Pico.
|
| /Zephyr-latest/boards/nordic/nrf7002dk/doc/ |
| D | index.rst | 207 The Zephyr build system will perform the following steps automatically:
240 the Secure application will have to set the IDAU (SPU) configuration to allow
266 protection is active, you will need to recover the chip before reflashing.
|
| /Zephyr-latest/doc/develop/ |
| D | beyond-GSG.rst | 85 * If the variables are not set, the latest compatible version of Zephyr SDK will be selected
88 * If :envvar:`ZEPHYR_TOOLCHAIN_VARIANT` is set, the corresponding toolchain will be selected
93 * If the :envvar:`ZEPHYR_SDK_INSTALL_DIR` environment variable is set, it will override
210 The main build products will be in :file:`build/zephyr`;
|
| /Zephyr-latest/boards/toradex/colibri_imx7d/doc/ |
| D | index.rst | 8 Zephyr was ported to run on the M4 core. In a later release, it will also
161 At compilation time you have to choose which RAM will be used. This configuration is
185 Below you will find the instructions to load and run Zephyr on M4 from A7 using u-boot.
387 #dmesg will detail the boot process:
|
| /Zephyr-latest/doc/build/dts/ |
| D | api-usage.rst | 104 /* These will give you compiler errors: */
182 as shown above. It will expand to either 0 or 1 depending on if the property
249 /* This will cause a compiler error. */
390 useful to understand them since they will frequently be seen in compiler error
|
| /Zephyr-latest/boards/nxp/hexiwear/doc/ |
| D | index.rst | 144 To enable battery sensing, you will need to enable the ``en_bat_sens``
146 or 3V3 power rails (sensors), you will need to enable the ``en_ldo``
214 Regardless of your choice in debug probe, we will use the OpenSDA
302 will then see a plot of the heart rate data that updates once per second.
|
| /Zephyr-latest/doc/security/ |
| D | security-overview.rst | 69 recommendations or requirements as most implementors will not have had
77 changes are identified, they will be added to this document through the
80 1. Changes will be submitted from the interested party(ies) via pull
83 2. The Zephyr Security Subcommittee will review these changes and provide feedback
86 3. Once accepted, these changes will become part of the document.
202 - **Memory separation:** Memory will be partitioned into regions and
204 Threads will only have access to regions they control.
212 resources owned by that thread will be accessible. Topics such as
|
| /Zephyr-latest/subsys/logging/frontends/ |
| D | Kconfig | 95 When enabled, accessing STMESP registers will stall if write cannot be
|
| /Zephyr-latest/drivers/serial/ |
| D | Kconfig.ns16550 | 68 16550 (DesignWare UART) only allows word access, byte access will raise
|
| /Zephyr-latest/samples/subsys/usb/webusb/ |
| D | README.rst | 90 The demo app will receive the same text from the device and display it in
|
| /Zephyr-latest/cmake/modules/ |
| D | FindHostTools.cmake | 8 # This module will lookup the following tools for Zephyr development:
|
| /Zephyr-latest/cmake/sca/eclair/ |
| D | sca.cmake | 116 # configure the camke script which will be used to replace the compiler call with the eclair_env
|
| /Zephyr-latest/boards/innblue/innblue21/doc/ |
| D | index.rst | 93 When building a Secure/Non-Secure application, the Secure application will
|
| /Zephyr-latest/boards/innblue/innblue22/doc/ |
| D | index.rst | 93 When building a Secure/Non-Secure application, the Secure application will
|
| /Zephyr-latest/samples/subsys/tracing/ |
| D | README.rst | 7 formatted packet will be sent to the host with the currently supported tracing
|
| /Zephyr-latest/drivers/ethernet/ |
| D | Kconfig | 20 i.e. without a MAC stack (the net L2 layer for ethernet will not
|
| /Zephyr-latest/doc/hardware/peripherals/edac/ |
| D | ibecc.rst | 71 Exceptional care needs to be taken with Non Maskable Interrupt (NMI). NMI will
|
| /Zephyr-latest/samples/drivers/fpga/fpga_controller/ |
| D | README.rst | 103 It will print the sum of the read bytes and return to the shell:
|
| /Zephyr-latest/include/zephyr/arch/mips/ |
| D | linker.ld | 178 * will not be cleared during the boot process.
|
| /Zephyr-latest/modules/ |
| D | Kconfig | 7 Exclude firmware blobs from the build. This will produce a
|
| /Zephyr-latest/samples/net/sockets/http_get/ |
| D | README.rst | 82 Linux. (Note: if you look at the source, you will see that the code is
|
1...<<41424344454647484950>>...66
