| /Zephyr-latest/samples/subsys/modbus/rtu_server/ |
| D | README.rst | 24 The user can of course try out other client implementations with this sample.
74 On the client side, PC or laptop, the following command connects PyModbus
88 > client.write_coil address=0 value=1 slave=1
103 > client.write_coils address=0 values=0,1,1 slave=1
109 > client.read_coils address=0 count=3 slave=1
131 > client.write_register address=0 value=42 slave=1
137 > client.write_registers address=0 values=42,42,42 slave=1
143 > client.read_holding_registers address=0 count=3 slave=1
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | dhcpv4.rst | 21 Note that Zephyr supports both DHCPv4 client and server functionality.
26 See :zephyr:code-sample:`dhcpv4-client` sample application for details.
|
| D | http_client.rst | 13 The HTTP client library allows you to send HTTP requests and
25 The API of the HTTP client library has a single function.
72 See :zephyr:code-sample:`HTTP client sample application <sockets-http-client>` for
|
| D | websocket.rst | 13 The Websocket client library allows Zephyr to connect to a Websocket server.
14 The Websocket client API can be used directly by application to establish
29 protocols like MQTT. The Zephyr MQTT client library can be configured to use
49 Websocket client API will encapsulate the sent or received data to/from
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | qemu_802154_setup.rst | 20 * Terminal #2 is terminal window with ``echo-client`` Zephyr sample application.
62 Step 2 - Compile and start echo-client
71 :build-dir: client
73 :goals: client
|
| /Zephyr-latest/tests/bsim/bluetooth/host/gatt/settings_clear/src/ |
| D | server.c | 91 bt_addr_le_t client = {}; in connect_and_set_security() local
93 err = bt_testlib_scan_find_name(&client, ADVERTISER_NAME); in connect_and_set_security()
96 err = bt_testlib_connect(&client, conn); in connect_and_set_security()
|
| /Zephyr-latest/subsys/net/lib/lwm2m/ |
| D | Kconfig.ipso | 25 Sensor instances available to the LWM2M client.
54 Sensor instances available to the LWM2M client.
94 Sensor instances available to the LWM2M client.
125 Sensor instances available to the LWM2M client.
158 instances available to the LWM2M client.
171 instances available to the LWM2M client.
200 instances available to the LWM2M client.
228 instances available to the LWM2M client.
241 instances available to the LWM2M client.
271 instances available to the LWM2M client.
[all …]
|
| /Zephyr-latest/doc/connectivity/bluetooth/shell/audio/ |
| D | mcp.rst | 5 using the shell, both as a client and as a server.
10 the player. The media control client consists of one part, the GATT
11 based client (mcc).
14 and the media control client may include an object transfer client
18 The media control server and client both implement the Generic Media
73 The media control client is used to control, and to get information
79 Using the media control client
82 Before use, the media control client must be initialized by the
89 When the media control client is connected to a media control server,
90 the client can discover the server's Generic Media Control Service, by
[all …]
|
| D | ccp.rst | 5 a client and as a (telephone bearer service (TBS)) server. Note that in the
12 The telephone bearer service client will typically exist on a resource
14 laptops. The call control client will also thus typically be the advertiser.
15 The client can control the states of calls on a server using the call control
19 enabled for using the client interactively.
21 Using the telephone bearer service client
25 and a device has been connected, the telephone bearer service client can
36 the client may subscribe and use either when sending requests if
170 or the TBS server may initiate a call to remote device, without a TBS_CLIENT client.
221 Answering a call for a peer device originated by a client:
[all …]
|
| /Zephyr-latest/soc/nordic/nrf54h/gpd/ |
| D | gpd.c | 217 struct onoff_client client; in nrf_gpd_request() local
231 sys_notify_init_spinwait(&client.notify); in nrf_gpd_request()
233 ret = onoff_request(&gpd_mgr->mgr, &client); in nrf_gpd_request()
238 while (sys_notify_fetch_result(&client.notify, &ret) == -EAGAIN) { in nrf_gpd_request()
241 sys_notify_init_callback(&client.notify, request_cb); in nrf_gpd_request()
244 ret = onoff_request(&gpd_mgr->mgr, &client); in nrf_gpd_request()
|
| /Zephyr-latest/subsys/net/lib/sntp/ |
| D | Kconfig | 8 Enable SNTP client library
25 module-help = Enable debug message of SNTP client library.
|
| /Zephyr-latest/tests/net/socket/tls_ext/ |
| D | CMakeLists.txt | 28 # we reuse the same certificate / private key for client
33 ${gen_dir}/client.inc
|
| /Zephyr-latest/soc/intel/intel_adsp/tools/ |
| D | cavstool_client.py | 116 client = cavstool_client(HOST, PORT, args)
117 client.send_cmd(CMD_LOG_START)
123 client = cavstool_client(HOST, PORT, args)
124 client.send_cmd(CMD_DOWNLOAD)
|
| /Zephyr-latest/samples/net/sockets/echo_client/ |
| D | README.rst | 1 .. zephyr:code-sample:: sockets-echo-client
2 :name: Echo client (advanced)
5 Implement a client that sends IP packets, waits for data to be sent back, and verifies it.
10 The echo-client sample application for Zephyr implements a UDP/TCP client
26 usage scenario is to run echo-client application inside QEMU. This is
30 echo-client directory:
51 Build echo-client sample application like this:
151 Here echo-client is run in QEMU and echo-server is run in Linux host.
161 Run echo-client application in QEMU:
172 before you start the echo-client application in QEMU.
[all …]
|
| /Zephyr-latest/drivers/clock_control/ |
| D | nrf_clock_calibration.c | 47 static struct onoff_client client; variable
90 clk_request(&mgrs[CLOCK_CONTROL_NRF_TYPE_HFCLK], &client, cal_hf_callback); in hf_request()
95 clk_request(&mgrs[CLOCK_CONTROL_NRF_TYPE_LFCLK], &client, cal_lf_callback); in lf_request()
|
| /Zephyr-latest/samples/drivers/video/tcpserversink/ |
| D | README.rst | 5 Capture video frames and send them over the network to a TCP client.
11 them over the network to the connected TCP client.
48 TCP: Waiting for client...
|
| /Zephyr-latest/subsys/sip_svc/ |
| D | Kconfig | 55 Maximum number of transaction_id per client.
65 bool "Allow a single client to open a connection at a time"
67 Allow only one client to open a session per controller
|
| /Zephyr-latest/drivers/usb/bc12/ |
| D | bc12_pi3usb9201.c | 143 static int pi3usb9201_get_status(const struct device *dev, uint8_t *const client, in pi3usb9201_get_status() argument
155 if (client != NULL) { in pi3usb9201_get_status()
156 *client = status; in pi3usb9201_get_status()
493 uint8_t client; in pi3usb9201_isr_work() local
497 rv = pi3usb9201_get_status(dev, &client, &host); in pi3usb9201_isr_work()
503 if (client != 0) { in pi3usb9201_isr_work()
508 pi3usb9201_client_detect_finish(dev, client); in pi3usb9201_isr_work()
|
| /Zephyr-latest/samples/subsys/modbus/rtu_client/ |
| D | CMakeLists.txt | 6 project(modbus-rtu-client)
|
| /Zephyr-latest/subsys/mgmt/mcumgr/smp_client/ |
| D | CMakeLists.txt | 9 zephyr_library_sources(src/client.c)
|
| /Zephyr-latest/samples/net/ipv4_autoconf/ |
| D | README.rst | 2 :name: IPv4 autoconf client
30 Running Avahi client in Linux Host
61 [ipv4ll] [INF] main: Run ipv4 autoconf client
|
| /Zephyr-latest/subsys/net/lib/coap/ |
| D | Kconfig | 105 bool "CoAP client support [EXPERIMENTAL]"
108 This option enables the API for CoAP-client for sending CoAP requests
113 int "Coap client thread priority"
116 Priority of receive thread of the CoAP client.
123 CoAP block size used by CoAP client when performing block-wise
130 CoAP client message payload size. Can't be smaller than COAP_CLIENT_BLOCK_SIZE.
140 int "Stack size of the CoAP client thread"
150 int "Maximum number of simultaneous requests per client"
153 Maximum number of CoAP requests a single client can handle at a time
|
| /Zephyr-latest/tests/modules/thrift/ThriftTest/src/ |
| D | context.hpp | 28 std::unique_ptr<ThriftTestClient> client; member
|
| /Zephyr-latest/samples/net/prometheus/ |
| D | README.rst | 11 This library provides prometheus client library(pull method) implementation.
39 See `Prometheus client library documentation
54 streams that can be established per client.
57 for each client. This limits the maximum length of an individual HTTP header
|
| /Zephyr-latest/subsys/net/lib/http/ |
| D | Kconfig | 26 bool "HTTP client API"
30 HTTP client API
68 This setting determines the maximum number of HTTP/2 streams for each client.
75 This setting determines the buffer size for each client.
133 This setting determines the size of the (per-client) buffer used to store
150 This timeout specifies maximum time the client may remain inactive
207 module-str = Log level for HTTP client library
208 module-help = Enables HTTP client code to output debug messages.
|
