Home
last modified time | relevance | path

Searched refs:objects (Results 1 – 25 of 116) sorted by relevance

12345

/Zephyr-4.2.1/samples/bluetooth/peripheral_ots/src/
Dmain.c38 } objects[OBJ_POOL_SIZE]; variable
47 #define OTS_OBJ_ID_TO_OBJ_IDX(id) (((id) - BT_OTS_OBJ_ID_MIN) % ARRAY_SIZE(objects))
80 if (obj_cnt >= ARRAY_SIZE(objects)) { in ots_obj_created()
98 objects[index].name[0] = '\0'; in ots_obj_created()
100 created_desc->name = objects[index].name; in ots_obj_created()
154 *data = &objects[obj_index].data[offset]; in ots_obj_read()
183 (void)memcpy(&objects[obj_index].data[offset], data, len); in ots_obj_write()
208 *data = &objects[obj_index].data[offset]; in ots_obj_cal_checksum()
258 cur_size = sizeof(objects[0].data) / 2; in ots_init()
259 alloc_size = sizeof(objects[0].data); in ots_init()
[all …]
/Zephyr-4.2.1/subsys/mgmt/updatehub/
Dupdatehub_priv.h97 struct resp_probe_objects objects; member
101 struct resp_probe_objects_array objects[4]; member
106 struct resp_probe_objects_array_array objects[2]; member
113 struct resp_probe_objects_array_array objects[2]; member
153 objects, recv_probe_objects_descr),
158 objects, 4, objects_len,
170 objects, 2, objects_len,
183 objects, 2, objects_len,
Dupdatehub.c859 i, metadata_any_boards.objects[i].objects_len); in z_impl_updatehub_probe()
860 for (size_t j = 0; j < metadata_any_boards.objects[i].objects_len; ++j) { in z_impl_updatehub_probe()
862 &metadata_any_boards.objects[i].objects[j].objects; in z_impl_updatehub_probe()
875 metadata_any_boards.objects[1].objects[0].objects.sha256sum) + 1; in z_impl_updatehub_probe()
884 metadata_any_boards.objects[1].objects[0].objects.sha256sum, in z_impl_updatehub_probe()
886 update_info.image_size = metadata_any_boards.objects[1].objects[0].objects.size; in z_impl_updatehub_probe()
893 i, metadata_some_boards.objects[i].objects_len); in z_impl_updatehub_probe()
894 for (size_t j = 0; j < metadata_some_boards.objects[i].objects_len; ++j) { in z_impl_updatehub_probe()
896 &metadata_some_boards.objects[i].objects[j].objects; in z_impl_updatehub_probe()
916 metadata_some_boards.objects[1].objects[0].objects.sha256sum) + 1; in z_impl_updatehub_probe()
[all …]
/Zephyr-4.2.1/tests/bluetooth/tester/src/
Dbtp_ots.c35 } objects[OBJ_POOL_SIZE]; variable
43 #define OTS_OBJ_ID_TO_OBJ_IDX(id) (((id) - BT_OTS_OBJ_ID_MIN) % ARRAY_SIZE(objects))
62 for (size_t i = 0; i < ARRAY_SIZE(objects); i++) { in get_object()
63 if (!objects[i].in_use) { in get_object()
64 objects[i].in_use = true; in get_object()
65 return &objects[i]; in get_object()
178 obj = &objects[obj_index]; in ots_obj_created()
212 obj = &objects[obj_index]; in ots_obj_deleted()
240 *data = &objects[obj_index].data[offset]; in ots_obj_read()
257 (void)memcpy(&objects[obj_index].data[offset], data, len); in ots_obj_write()
[all …]
/Zephyr-4.2.1/doc/kernel/usermode/
Dkernelobjects.rst14 The set of known kernel objects and driver subsystems is defined in
17 Kernel objects are completely opaque to user threads. User threads work
18 with addresses to kernel objects when making API calls, but may never
20 All kernel objects must be placed in memory that is not accessible by
23 Since user threads may not directly manipulate kernel objects, all use of
31 or objects which themselves have been allocated from a runtime memory pool.
44 Kernel objects that are only used by supervisor threads have no restrictions
53 appears in the ELF symbol table. It is permitted to declare kernel objects
55 generated ELF file to find kernel objects and places their memory addresses
56 in a special table of kernel object metadata. Kernel objects may be members
[all …]
Doverview.rst65 - We prevent use of device drivers or kernel objects not specifically granted,
80 - Use of kernel objects that are not in a proper initialization state.
105 logic for creating the tables of valid kernel objects, defining system calls,
111 for kernel objects should always be configured as supervisor-only.
114 assign them permissions to kernel objects. In general, all C and header
142 domains, or via kernel objects such as semaphores and pipes.
144 - User threads cannot directly access memory belonging to kernel objects.
145 Although pointers to kernel objects are used to reference them, actual
146 manipulation of kernel objects is done through system call interfaces. Device
147 drivers and threads stacks are also considered kernel objects. This ensures
[all …]
Dmpu_userspace.rst12 ELF file and finds all of the thread stack objects. A set of privileged
/Zephyr-4.2.1/doc/kernel/object_cores/
Dindex.rst7 perform operations on registered objects.
22 tools to traverse all the objects in the system.
24 Object cores have been integrated into following kernel objects:
39 Developers are free to integrate them if desired into other objects within
44 A variety of kernel objects allow for the gathering and reporting of statistics.
54 The following table indicates both what objects have been integrated into the
75 :c:struct:`k_obj_type`. It must be initialized before any objects of that type
120 Kernel objects that have already been integrated into the object core framework
122 initialized. However, developers that wish to add their own objects into the
143 above and prints the addresses of all the objects of that new object type.
[all …]
/Zephyr-4.2.1/subsys/bluetooth/services/ots/
DKconfig21 from all other objects, for easy exposure to a client. Enabling this will use one of the
22 objects given by BT_OTS_MAX_OBJ_CNT.
59 bool "Support patching of objects"
85 hex "Maximum number of objects that each service instance can store"
88 # object using the net_buf implementation is 2^16-1, the maximum number of objects is given
/Zephyr-4.2.1/include/zephyr/linker/common-rom/
Dcommon-rom-kernel-devices.ld8 * link in initialization objects for all objects that are
9 * automatically initialized by the kernel; the objects are
75 /* Build-time assignment of permissions to kernel objects to
/Zephyr-4.2.1/soc/ti/simplelink/
DKconfig18 Turn on dynamic memory allocation for DPL objects. Reserves
/Zephyr-4.2.1/subsys/bluetooth/audio/
DKconfig.mpl73 bool "Support for media player objects"
79 Enables support for objects in the media player
86 int "Total memory size to use for storing the content of objects"
90 Sets the total memory size (in octets) to use for storing the content of objects.
DKconfig.mctl50 bool "Support for accessing objects on remote player"
56 This options enables support for accessing objects (tracks, groups,
/Zephyr-4.2.1/kernel/
DKconfig.obj_core9 participating kernel objects and their respective types together
118 system objects into the object core framework. As these are internal
135 into kernel objects.
146 bool "Object core statistics for system level objects"
DKconfig.device50 int "Kernel objects initialization priority"
53 Kernel objects use this priority for initialization. This
/Zephyr-4.2.1/include/zephyr/sys/internal/
Dkobject_internal.h71 void * const *objects; member
/Zephyr-4.2.1/samples/bluetooth/central_otc/
DREADME.rst13 to read data, and to calculate checksum of selected objects.
/Zephyr-4.2.1/include/zephyr/linker/
Dcommon-noinit.ld11 * This section is used for non-initialized objects that
Dcommon-ram.ld45 /* Device states used by the device objects. */
69 /* All kernel objects within are assumed to be either completely
/Zephyr-4.2.1/dts/arm/infineon/cat3/xmc/
Dxmc4500_F100x1024.dtsi101 message-objects = <64>;
Dxmc4700_F144x2048.dtsi104 message-objects = <256>;
/Zephyr-4.2.1/doc/kernel/services/
Dpolling.rst18 kernel objects rather than on file descriptors.
48 Apart from the kernel objects, there is also a **poll signal** pseudo-object
326 Because objects are only signaled if no other thread is waiting for them to
328 is best used when objects are not subject of contention between multiple
330 "dispatcher" for multiple objects and is the only one trying to acquire
331 these objects.
/Zephyr-4.2.1/tests/kernel/pending/
DREADME.txt6 kernel objects: FIFOs, LIFOs, semaphores and timers.
/Zephyr-4.2.1/tests/kernel/sleep/
DREADME.txt37 Kernel objects initialized
/Zephyr-4.2.1/doc/connectivity/bluetooth/api/mesh/
Dblob.rst7 Transfer Model specification version 1.0 and provide functionality for sending large binary objects
12 The BLOB Transfer models support transfers of continuous binary objects of up to 4 GB (2 \ :sup:`32`
46 BLOBs are binary objects up to 4 GB in size, that can contain any data the application would like to
47 transfer through the mesh network. The BLOBs are continuous data objects, divided into blocks and
60 The binary objects are divided into blocks, typically from a few hundred to several thousand bytes

12345