Searched refs:created (Results 51 – 75 of 278) sorted by relevance
12345678910>>...12
27 In order to use this, a retention area must be created and set as
31 ``zephyr.efi`` is a Zephyr EFI binary created above.
57 created in the build directory after the application is built.
29 metadata, and a pointer to the raw data. Entries can be created using the
126 * will be created in this area.
70 -doc="Entities created with Z_LINK_ITERABLE in linker.ld"
19 object created by functions :c:func:`bt_conn_le_create` and
36 Note that the later can also disconnect channel instances created by servers.
27 Set the AWS Thing name created on IoT Console
16 of sockets. This saves memory as only one thread needs to be created in the
56 MAC Address which would be assigned to network device, created in
11 A project must have already been created with Zephyr and west.44 #. Right-click on the newly created project in the workspace, and select
93 the BIG and output the current counter (since the BIG was created)::107 [00:00:08.813,171] <inf> iso_broadcast_broadcaster: BIG created
22 # Also newlib or picolibc may be created as add-ons. Thus always stating that LLVM does not have
35 Stack size of thread created for each instance.
53 created in the build directory after the application is built.
50 created in the build directory after the application is built.
67 created in the build directory after the application is built.
59 created in the RPMsg Service backend module to prevent notifying
27 The following is an example of a request structure created correctly:
49 created in the build directory after the application is built.
50 Replace :code:`<tty_device>` with the correct device path automatically created on
25 when a memory domain is created.
12 connected UNIX-domain sockets. The pairs of sockets are created with
53 Replace :code:`<tty_device>` with the correct device path automatically created on
