Lines Matching +full:user +full:- +full:files

10 specific management area, which is addressed with a 16-bit identification value,
13 group a command belongs to, there is also an 8-bit command ID which identifies the function of
14 that group to execute - see :ref:`mcumgr_smp_protocol_specification` for details on the SMP
24 .. code-block:: none
35 Note that the header files in upstream Zephyr MCUmgr handlers reside in the
36 ``zephyr/include/zephyr/mgmt/mcumgr/grp/<grp_name>_mgmt`` directory to allow the files to be
52 responses that return a :c:enum:`mcumgr_err_t` - there should always be an OK error code with the
55 :c:enumerator:`MGMT_GROUP_ID_PERUSER`, which is the start group ID for user-defined groups, note
73 :c:enumerator:`MGMT_EVT_GRP_USER_CUSTOM_START`, which is the start event ID for user-defined groups,
97 base Zephyr callback include file and the custom handler callback file, only in-tree Zephyr
112 The CMakeLists.txt file is used by the build system to setup files to compile, include
114 source files if the Kconfig options are enabled. An example file would look similar to:
118    .. group-tab:: Zephyr module
123    .. group-tab:: Application
127          :start-after: Include handler files
132 Application-specific MCUmgr handlers can be added by creating/editing application build files.
141 .. code-block:: cmake
152 .. code-block:: kconfig
163 without needing to duplicate the code in each application's source tree, see :ref:`module-yml` for
164 details on how to set up the module files. Example files are shown below.
169 This is an example file which can be used to load the Kconfig and CMake files from the root of the
172 .. code-block:: yaml
184 .. code-block:: cmake
194 .. code-block:: kconfig
202 module-MCUmgr handlers which can be used as a basis for created your own in