| /samples/net/syslog_net/src/ |
| A D | main.c | 37 const struct log_backend *backend = log_backend_net_get(); in main() local
39 if (!log_backend_is_active(backend)) { in main()
50 log_backend_init(backend); in main()
51 log_backend_enable(backend, backend->cb->ctx, CONFIG_LOG_MAX_LEVEL); in main()
|
| /samples/subsys/fs/littlefs/ |
| A D | Kconfig | 12 prompt "Storage backend type used by the application"
15 Specify the type of storage backend.
18 bool "Use flash memory backend"
21 bool "Use block device (e.g. SD MMC) backend"
|
| /samples/subsys/logging/ble_backend/ |
| A D | sample.yaml | 2 description: A simple application that demonstrates the use of the logging Bluetooth backend.
3 name: logger backend Bluetooth
|
| A D | README.rst | 1 .. zephyr:code-sample:: logging-ble-backend
2 :name: Bluetooth logging backend
5 Send log messages over Bluetooth using the Bluetooth logging backend.
10 Sample that demonstrates how to setup and use the Bluetooth Logging backend. The
14 The notification size of the Bluetooth backend buffer is dependent on the
|
| /samples/subsys/modbus/tcp_gateway/src/ |
| A D | main.c | 19 static int backend; variable
36 backend = modbus_iface_get_by_name(bend_name); in init_backend_iface()
37 if (backend < 0) { in init_backend_iface()
43 return modbus_init_client(backend, backend_param); in init_backend_iface()
83 rc = modbus_raw_backend_txn(backend, &tmp_adu); in modbus_tcp_connection()
|
| /samples/subsys/modbus/tcp_gateway/ |
| A D | CMakeLists.txt | 6 project(modbus-serial-backend)
|
| /samples/subsys/ipc/rpmsg_service/ |
| A D | sample.yaml | 2 name: IPC Service example integration (rpmsg backend)
|
| /samples/boards/nxp/adsp/number_crunching/ |
| A D | CMakeLists.txt | 21 # this is an example for NatureDSP backend
35 # this is an example for CMSIS-DSP backend
|
| A D | README.rst | 37 If one wants to include a new backend it needs to create a new wrapper for that library or backend.
|
| /samples/subsys/ipc/ipc_service/multi_endpoint/ |
| A D | README.rst | 8 By default, it uses the ``icmsg_me`` backend.
9 You can also configure it to use the ``icbmsg`` backend.
64 Changing the backend
67 To change the backend to ``icbmsg``, switch the devicetree
|
| A D | sample.yaml | 2 name: IPC Service example integration (icmsg multi endpoint backend)
|
| /samples/subsys/ipc/ipc_service/icmsg/ |
| A D | README.rst | 2 :name: IPC service: icmsg backend
5 Send messages between two cores using the IPC service and icmsg backend.
10 This application demonstrates how to use IPC Service and the icmsg backend with
|
| A D | sample.yaml | 2 name: IPC Service example integration (icmsg backend)
|
| /samples/subsys/ipc/ipc_service/static_vrings/ |
| A D | README.rst | 2 :name: IPC service: static vrings backend
5 Send messages between two cores using the IPC service and static vrings backend.
11 backend with Zephyr. It is designed to demonstrate how to integrate it with
|
| A D | sample.yaml | 2 name: IPC Service example integration (OpenAMP static_vrings backend)
|
| /samples/net/syslog_net/ |
| A D | sample.yaml | 8 description: syslog network backend
|
| A D | Kconfig | 21 app before the backend is initialized. This can be
|
| /samples/subsys/usb/dfu/ |
| A D | README.rst | 52 Building with flash backend enabled
55 The USB DFU device support has a built-in flash backend. This backend uses
60 To use flash backend set the :kconfig:option:`CONFIG_APP_USB_DFU_USE_FLASH_BACKEND`.
66 flash backend and MCUboot support enabled using the :ref:`sysbuild`:
|
| /samples/boards/nxp/s32/netc/ |
| A D | README.rst | 20 and backend is also enabled.
49 [00:00:00.058,000] <inf> shell_telnet: Telnet shell backend initialized
74 [00:00:00.058,000] <inf> shell_telnet: Telnet shell backend initialized
|
| /samples/subsys/usb/console/ |
| A D | README.rst | 11 experimental USB device stack as a serial backend for the console.
|
| /samples/subsys/dap/ |
| A D | README.rst | 10 controller through DAP USB backend.
|
| /samples/net/mqtt_publisher/ |
| A D | README.rst | 224 MQTT logging backend
227 The sample can be configured to use an MQTT logging backend, which allows log
231 The MQTT logging backend uses the :c:func:`log_backend_mqtt_client_set` API to
232 register an MQTT client for publishing log messages. The backend only uses the
236 To enable the MQTT logging backend in the sample, build it with
237 ``-DEXTRA_CONF_FILE=overlay-log-backend-mqtt.conf`` parameter.
|
| /samples/subsys/logging/dictionary/ |
| A D | README.rst | 11 the UART backend. This is configured to output binary log data
|
| /samples/subsys/tracing/ |
| A D | README.rst | 8 backend under tracing generic infrastructure.
|
| /samples/subsys/mgmt/mcumgr/smp_svr/ |
| A D | README.rst | 96 To build the serial sample with USB CDC_ACM backend:
286 :ref:`file_system_api`, this is useful with e.g. FS log backend, when files are stored in
|