Searched refs:will (Results 301 – 325 of 1633) sorted by relevance
1...<<11121314151617181920>>...66
| /Zephyr-latest/lib/posix/options/ |
| D | Kconfig.file_system_r | 10 Select 'y' here and Zephyr will provide an implementation of the POSIX_FILE_SYSTEM_R
|
| D | Kconfig.fs | 18 When selected via Kconfig, Zephyr will provide an alias for fstat() as _fstat().
|
| /Zephyr-latest/doc/develop/debug/ |
| D | index.rst | 26 You will need an :abbr:`ELF (Executable and Linkable Format)` binary image for
34 We will use the standard 1234 TCP port to open a :abbr:`GDB (GNU Debugger)`
50 will setup Qemu to listen on port 1234 and wait for a GDB connection to it.
69 QEMU will write the console output to the path specified in
83 QEMU will write the console output to the terminal from which you invoked
93 If the option is unset, then the QEMU invocation will lack a ``-s`` or a
157 As configured above, when you connect the GDB client, the application will be
163 :command:`gdb` will not print the system console output as the application runs,
165 :command:`continue` after connecting the client, the application will run,
166 but nothing will appear to happen. Check the console output as described
[all …]
|
| /Zephyr-latest/subsys/mgmt/mcumgr/smp/ |
| D | Kconfig | 73 This is a maximum number of levels of maps/lists that will
80 it will need 2 levels.
129 This is a maximum number of levels of maps/lists that will
139 This will enable SMP command status notification hooks for when an SMP message is
146 This option will enable supporting the original SMP protocol whereby
|
| /Zephyr-latest/subsys/net/ip/ |
| D | Kconfig.mgmt | 30 If NET_MGMT_EVENT_INFO is enabled the data will be copied to
38 If NET_MGMT_EVENT_INFO is enabled the data will be copied to
78 3rd event comes in, the first will be removed without generating any
94 Event notifier will be able to provide information to an event,
95 and listeners will then be able to get it. Such information depends
|
| /Zephyr-latest/soc/nxp/imxrt/ |
| D | Kconfig | 106 an MPU region will be defined to disable cached access to the
114 or an MPU region will be defined to disable cached access to the
120 Indicates the second core will be enabled, and the part will run
123 The M4 image will be loaded from flash into RAM based off a
|
| /Zephyr-latest/samples/modules/chre/ |
| D | README.rst | 57 #. Add an implementation of the `pal/sensor.h`_ and `pal/system.h`_ to Zephyr. These will be
59 will also provide an implementation of ``chrePalSensorGetApi()`` and ``struct chrePalSystemApi``.
60 #. Add a directory ``chre/nanoapps`` which will host various nanoapps to be used by the Zephyr
62 dependencies. The first nanoapp will be a lid angle calculator which will use 2 accelerometers.
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | blob_srv.rst | 19 The BLOB Transfer Server keeps track of the received blocks and chunks, and will process each block
80 will attempt to recover the transfer. When the Bluetooth Mesh subsystem is started (for instance by
81 calling :c:func:`bt_mesh_init`), the BLOB Transfer Server will check for aborted transfers, and call
88 will stay suspended until the BLOB Transfer Client resumes the transfer, or the user cancels it.
93 will stay suspended until the application calls :c:func:`bt_mesh_blob_srv_cancel`.
|
| /Zephyr-latest/samples/bluetooth/iso_connected_benchmark/ |
| D | README.rst | 58 The peripheral will output overall data (since boot),
86 The central will ask if any changes to the current settings are wanted.
87 If y/Y is chosen, then it will create a prompt to changes the settings,
88 otherwise continue with the current settings. The central will then start
90 role. Once connected, the central will output overall data (since boot),
|
| /Zephyr-latest/boards/shields/rk055hdmipi4m/boards/ |
| D | mimxrt595_evk_mimxrt595s_cm33.overlay | 9 * This will improve performance when using external pSRAM.
|
| /Zephyr-latest/boards/shields/rk055hdmipi4ma0/boards/ |
| D | mimxrt595_evk_mimxrt595s_cm33.overlay | 9 * This will improve performance when using external pSRAM.
|
| /Zephyr-latest/soc/nxp/kinetis/ |
| D | CMakeLists.txt | 16 # CMSIS SystemInit will disable watchdog unless instructed not to.
|
| /Zephyr-latest/cmake/modules/ |
| D | boards.cmake | 7 # This CMake module will validate the BOARD argument as well as splitting the
9 # is enabled (default) this module will also take care of finding board
12 # If a board implementation is not found for the specified board an error will
13 # be raised and list of valid boards will be printed.
15 # If user provided board is a board alias, the board will be adjusted to real
18 # If board name is deprecated, then board will be adjusted to new board name and
19 # a deprecation warning will be printed to the user.
22 # The following variables will be defined when this CMake module completes:
37 # The following targets will be defined when this CMake module completes:
38 # - board: when invoked, a list of valid boards will be printed
[all …]
|
| /Zephyr-latest/doc/develop/application/ |
| D | index.rst | 91 Once an application has been defined, you will use CMake to generate a **build
265 This will create a new workspace with the :ref:`T2 topology <west-t2>`, with
270 repository will match the example-application's contents when you clone it. You
282 and your workspace will be ready for use.
320 :file:`C:\\Users\\YourName\\app` will work, but
321 :file:`C:\\Users\\Your Name\\app` will not.
354 invoked by the Zephyr package on the next line. CMake will error out if
360 target is how you include them in the build. The Zephyr package will
406 ``find_package(Zephyr)`` will automatically set this as a cached CMake
411 will use for the default configuration. See :ref:`boards` for
[all …]
|
| /Zephyr-latest/samples/subsys/usb/mass/ |
| D | README.rst | 48 In this example we will build the sample with a RAM-based disk:
58 In this example we will build the sample with a FLASH-based disk and FAT
71 The board will be detected as shown by the Linux journalctl command:
94 The output to the console will look something like this
95 (file system contents will be different):
108 On most operating systems the drive will be automatically mounted.
173 console will look something like this (file system contents will be
236 which produces output like this (disk contents will vary):
275 specification the file system will not mount correctly.
|
| /Zephyr-latest/doc/connectivity/bluetooth/autopts/ |
| D | autopts-linux.rst | 40 After you extract archive, you will see 2 .deb files, e.g.:
72 configured, and will not get blocked by the Windows Firewall.
77 Open virtual machine network settings. On adapter 1 you will have created by default NAT.
85 For example setting up the following will allow you to use
125 VirtualBox on Linux, macOS and Solaris Oracle VM VirtualBox will only allow IP addresses in
139 Open virtual machine network settings. On adapter 1 you will have created by default NAT.
182 consoles. We will use Git Bash as Windows terminal.
306 Server and client by default will run on localhost address. Run server:
395 - Delete temporary workspace. You will find it in auto-pts-code/workspaces/zephyr/zephyr-master/ as…
404 then the title of the window will show the Bluetooth address of the dongle.
|
| /Zephyr-latest/samples/net/cloud/tagoio_http_post/ |
| D | README.rst | 10 This sample application implements an HTTP client that will do an HTTP post
33 is it! Now reveal your device token. The token will be used to identify your
90 * Add a line plot graph. You will see your device, temperature variable will
|
| /Zephyr-latest/samples/application_development/ |
| D | application_development.rst | 8 `example-application`_. Among others, you will find on it out of tree driver
|
| /Zephyr-latest/doc/hardware/arch/ |
| D | arm_cortex_m.rst | 135 Typically a thread context-switch will perform the following operations
233 ISRs will be handled by the corresponding fault handler and will not escalate to
237 (an exception to this rule will be described below).
243 result of this, kernel runtime errors during interrupt handling will escalate to
276 will set the PRIMASK register to 1, eventually, masking all IRQs with configurable
278 is that kernel runtime errors (triggering SVCs) will escalate to HardFault.
321 the highest configurable interrupt priority level for its own use (SVC). SVCs will
323 an interrupt at the highest interrupt priority which will not be blocked by interrupt
326 Zero latency IRQs have minimal interrupt latency, as they will always preempt regular HW
329 Note, however, that since ZLI ISRs will run at a priority level higher than the kernel
[all …]
|
| /Zephyr-latest/doc/hardware/cache/ |
| D | guide.rst | 21 in general ensures that memory will be seen in a coherent state from multiple
22 cores. Most applications will only need to use the cache APIs for interaction
30 of this, data moved into and out of memory by DMA engines will be stale in the
75 Assuming the MPU driver is enabled, it will configure the specified regions
99 attribute will be placed in a special ``nocache`` linker region in memory. This
100 region will be configured as uncached by the MPU driver during initialization.
152 cache lines in the specified region as stale, ensuring that the cache line will
159 and then invalidate it, ensuring that the cache will be refreshed the next time
|
| /Zephyr-latest/samples/net/secure_mqtt_sensor_actuator/ |
| D | README.rst | 79 Using the default config, the application will use DHCP to acquire an IP address and attempt
82 - The MQTT broker to which the board will connect is specified by
91 - The application will then attempt to connect to the public Mosquitto broker
94 This will require provisioning of certificates.
162 LED will turn on and the board will begin publishing sensor readings in JSON format
171 - The application will subscribe to a topic determined by ``CONFIG_NET_SAMPLE_MQTT_SUB_TOPIC_CMD``.
172 If a supported command string is received by the board on this topic, the board will execute
|
| /Zephyr-latest/kernel/ |
| D | Kconfig.vm | 23 address from DTS, in which case RAM will be identity-mapped. Some
76 mappings. The kernel itself will be mapped in here as well at boot.
79 will want to use a 64-bit build of Zephyr, there are no plans to
91 there isn't overlap with the existed mappings, it will reserve the
93 it will fail. And any attempt across the boundary of the virtual
94 memory space will fail.
141 will cause a kernel panic. Such code must work with exclusively pinned
155 This sets the number of page frames that will be reserved for
|
| /Zephyr-latest/drivers/timer/ |
| D | Kconfig.rcar_cmt | 13 If unchecked, no timer will be used.
|
| /Zephyr-latest/samples/bluetooth/direction_finding_central/boards/ |
| D | nrf5340dk_nrf5340_cpuapp.overlay | 7 /* Enable pin forwarding to network core. The selected pins will be used by
|
| /Zephyr-latest/samples/bluetooth/direction_finding_connectionless_rx/boards/ |
| D | nrf5340dk_nrf5340_cpuapp.overlay | 7 /* Enable pin forwarding to network core. The selected pins will be used by
|
1...<<11121314151617181920>>...66
