Searched refs:will (Results 551 – 575 of 1633) sorted by relevance
1...<<21222324252627282930>>...66
| /Zephyr-latest/share/zephyr-package/cmake/ |
| D | ZephyrConfig.cmake | 11 # It will be empty if not set in environment.
17 # honor that argument, the package_message() macro will not print messages when
135 # CMake finds packages will look all packages registered in the user package registry.
138 # and if so, we will return here, and let CMake call into the other registered package for real
|
| /Zephyr-latest/boards/ti/sk_am62/doc/ |
| D | index.rst | 75 onto an SD-card. This will boot Linux on the A53 application cores of the EVM.
76 These cores will then load the zephyr binary on the M4 core using remoteproc.
108 The SD card can now be used for booting. The binary will now be loaded onto the M4F core on boot.
113 The binary will run and print Hello world to the MCU_UART0 port.
|
| /Zephyr-latest/boards/phytec/phyboard_electra/doc/ |
| D | index.rst | 93 an etching software onto an SD-card. This will boot Linux on the A53 application
94 cores of the SoM. These cores will then load the zephyr binary on the M4 core
127 The SD card can now be used for booting. The binary will now be loaded onto the M4F core on boot.
131 The board should boot into Linux and the binary will run and print Hello world to the MCU_UART0
|
| /Zephyr-latest/boards/atmel/sam/sam4e_xpro/doc/ |
| D | index.rst | 93 By default a factory new SAM4E chip will boot SAM-BA boot loader located in
95 (General-Purpose NVM bit 1). The flash procedure will ensure that GPNVM1 is
98 If your chip has a security bit GPNVM0 set you will be unable to program flash
100 is to perform a chip erase procedure that will erase all GPNVM bits and the full
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | net_mgmt.rst | 42 may change in a future release, it will not affect the users of this
52 your callback is invoked. The callback will have to be unique for a
53 pair of layer and code, whereas on the command part it will be a mask of
75 events it will handle, **regardless** of how many events were in the
178 will be found in the :zephyr_file:`include/zephyr/net/net_event.h` header file. But in case
|
| /Zephyr-latest/arch/ |
| D | Kconfig | 262 Secure firmware image will execute in Secure state. It may
277 Execution. A Non-Secure firmware image will execute
310 If a user thread overflows its stack, this will be caught and the
311 kernel itself will be shielded from harm. Enabling this option
322 This option sets the privileged stack region size that will be used
324 this region will be inaccessible from user mode. During system calls,
325 this region will be utilized by the system call. This value must be
369 changes will be necessary for this.
380 Selected if the architecture will generate a fault if unused stack
390 Every kernel object will have an associated bitfield to store
[all …]
|
| /Zephyr-latest/subsys/net/l2/openthread/ |
| D | Kconfig | 9 as the OPENTHREAD_MBEDTLS setting will be controlled through other
50 If enabled, OpenThread stack will have to be configured and
52 Otherwise, OpenThread will configure the network parameters and try to
165 Security settings will be controlled directly by the user.
166 Enabling this setting will give access to full control of mbed TLS
304 When enabled the OpenThread logs will be prepended with the appropriate
|
| /Zephyr-latest/arch/arc/ |
| D | Kconfig | 144 Interrupt priorities available will be 0 to NUM_IRQ_PRIO_LEVELS-1.
153 Interrupts available will be 0 to NUM_IRQS-1.
169 register bank, in the set, will be used by FIRQ interrupts.
174 to use second register bank - otherwise all interrupts will use
186 with highest priority, status32 and pc will be saved in aux regs,
187 other regs will be saved according to the number of register bank;
189 will be same with other interrupts.
200 irq, this will get the minimal interrupt latency.
|
| /Zephyr-latest/subsys/logging/ |
| D | Kconfig | 10 Global switch for the logger, when turned off log calls will not be
|
| /Zephyr-latest/subsys/logging/backends/ |
| D | Kconfig.spinel | 9 When enabled, backend will use OpenThread dedicated SPINEL protocol for logging.
|
| /Zephyr-latest/drivers/usb_c/tcpc/ |
| D | Kconfig.tcpc_tcpci | 20 Number of I2C transaction tries that will be performed for each request.
|
| /Zephyr-latest/soc/espressif/esp32c2/ |
| D | Kconfig | 22 If enabled, the MAC and baseband of Wi-Fi and Bluetooth will be powered
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | coredump.rst | 13 array with a size of 0 and a desired size. The driver will statically allocate memory
|
| /Zephyr-latest/samples/sensor/adc_cmp_npcx/ |
| D | README.rst | 22 will be printed.
|
| /Zephyr-latest/samples/bluetooth/bthome_sensor_template/ |
| D | README.rst | 26 Assistant. There you will be asked to configure the BTHome sensor if everything
|
| /Zephyr-latest/subsys/net/l2/dummy/any/ |
| D | Kconfig | 12 The option will create an "any" network interface which acts
|
| /Zephyr-latest/samples/bluetooth/peripheral_ht/ |
| D | README.rst | 14 die temperature values. On other boards, it will generate dummy temperature
|
| /Zephyr-latest/boards/nxp/rd_rw612_bga/ |
| D | Kconfig.defconfig | 14 # Increase descriptor count. LVGL will allocate a 30KB buffer,
|
| /Zephyr-latest/tests/bsim/bluetooth/ |
| D | tests.nrf5340bsim_nrf5340_cpunet.txt | 1 # Search paths(s) for tests which will be run in the nrf5340 net core (both app, host and controller
|
| /Zephyr-latest/tests/arch/arm/arm_custom_interrupt/ |
| D | README.txt | 8 option. It will locate a unused interrupt to trigger via software and test
|
| /Zephyr-latest/doc/releases/ |
| D | migration-guide-3.5.rst | 22 The new signature will not immediately trigger a compiler error or warning,
24 statement, that you can enable with :kconfig:option:`CONFIG_ASSERT`, will
46 memory reserved for the stack, so stack usage for every thread will
52 will always fail. When using Picolibc, the default is 16kB with
61 toolchain. When building as part of the OS, the build will increase by
70 compiler will now warn about declarations of `main` which don't conform to
86 :kconfig:option:`CONFIG_CBPRINTF_FP_SUPPORT`, you will see increased
188 ``manage_callback``, ``get_pending_int``. The public API will return
195 will see last 3 bytes of their MAC address modified by this change.
214 set in the board DTS as a way to configure the amount of structures the driver will allocate.
[all …]
|
| /Zephyr-latest/doc/services/zbus/ |
| D | index.rst | 27 thread publishes a message on a channel, the bus will make the message available to all the
83 or observations individually. The event dispatcher will ignore disabled observers and observations.
94 shows the observer is disabled, so the event dispatcher will ignore it. (c) shows the observer
95 enabled. However, there is one static observation disabled. The event dispatcher will only stop
96 sending notifications from channel ``C3``. In (d), the event dispatcher will stop sending
307 in the calculation. The VDED will elevate the publisher's priority based on the HOP to ensure small
328 subscriber is attached to a thread, it assumes its priority, and the priority boost algorithm will
355 On the above code, the :c:func:`zbus_obs_attach_to_thread` will set the ``s1`` observer with
358 will be considered on the channel HOP calculation. Masking a specific observation of a channel will
364 * No bounded priority inversion will happen among the publisher and the observers;
[all …]
|
| /Zephyr-latest/doc/project/ |
| D | documentation.rst | 52 scheme and following a well-defined structure we will be able to group this
108 To generate the matrix, you will first need to build the documentation,
109 specifically you will need to build the doxygen XML output::
|
| /Zephyr-latest/boards/qemu/nios2/doc/ |
| D | index.rst | 6 This board configuration will use QEMU to emulate the Altera MAX 10 platform.
52 If SLIP networking is enabled (see below), an additional serial port will be
82 This will build an image with the synchronization sample app, boot it using
|
| /Zephyr-latest/doc/connectivity/bluetooth/ |
| D | bluetooth-tools.rst | 44 Controller. In order to benefit from these tools you will need to make sure
90 the host OS (Linux) to the emulator. For this purpose you will need some tools
112 If you are using QEMU, in order to make the Controller available you will need
209 When running both Host and Controller in actual Integrated Circuits, you will
228 To decode the binary protocol that will now be sent to the console UART you need
236 :kconfig:option:`CONFIG_BT_DEBUG_MONITOR_RTT` instead, which will use Segger
293 This command will create a TCP server bridge on the local host IP address ``127.0.0.1``
300 After following these steps the Zephyr application will be available to the Android Emulator
313 Host, you will need a few tools described in the :ref:`bluetooth_bluez` section.
|
1...<<21222324252627282930>>...66
