Home
last modified time | relevance | path

Searched full:remote (Results 1 – 25 of 609) sorted by relevance

12345678910>>...25

/Zephyr-latest/boards/microchip/mec172xevb_assy6906/support/
Dmec172x_remote_flasher.py9 attached to a remote system.
12 west flash -r misc-flasher -- mec172x_remote_flasher.py <remote host>
15 1. SSH access to remote host with write access to remote /tmp.
18 2. Dediprog "dpcmd" available in path on remote host.
22 the Dediprog programmer attached to remote host.
35 - <remote host>
36 serial_pty: "nc,<remote host>,<ser2net port>"
63 This is used for remote file name to avoid file name
90 help="Remote host name or IP address")
92 # Arguments about remote machine
[all …]
/Zephyr-latest/submanifests/
Doptional.yaml10 remote: upstream
16 remote: upstream
22 remote: upstream
28 remote: upstream
34 remote: upstream
40 remote: upstream
46 remote: upstream
53 remote: upstream
59 remote: upstream
65 remote: upstream
[all …]
/Zephyr-latest/include/zephyr/bluetooth/mesh/
Drpr_cli.h19 * @defgroup bt_mesh_rpr_cli Remote Provisioning Client model
26 * Tells the Remote Provisioning Server not to put restrictions on the max
35 * @brief Remote Provisioning Client model composition data entry.
55 /** Remote Provisioning Server scanning capabilities */
63 /** Remote Provisioning Client model instance. */
67 * @param cli Remote Provisioning Client.
68 * @param srv Remote Provisioning Server.
97 /** @brief Get scanning capabilities of Remote Provisioning Server.
99 * @param cli Remote Provisioning Client.
100 * @param srv Remote Provisioning Server.
[all …]
/Zephyr-latest/samples/subsys/ipc/ipc_service/icmsg/
DREADME.rst32 serial port, one is host another is remote:
54 [00:00:00.006,256] <inf> remote: IPC-service REMOTE demo started
55 [00:00:00.006,378] <inf> remote: Ep bounded
56 [00:00:00.006,439] <inf> remote: Perform sends for 1000 [ms]
58 [00:00:01.417,572] <inf> remote: Sent 235527 [Bytes] over 1000 [ms]
59 [00:00:01.417,602] <inf> remote: IPC-service REMOTE demo ended
61 [00:00:00.006,256] <inf> remote: IPC-service REMOTE demo started
62 [00:00:00.006,347] <inf> remote: Ep bounded
63 [00:00:00.006,378] <inf> remote: Perform sends for 1000 [ms]
64 [00:00:01.006,164] <inf> remote: Sent 236797 [Bytes] over 1000 [ms]
[all …]
Dsysbuild.cmake7 "There is no remote board selected in Kconfig.sysbuild")
11 APPLICATION remote
12 SOURCE_DIR ${APP_DIR}/remote
16 native_simulator_set_child_images(${DEFAULT_IMAGE} remote)
/Zephyr-latest/samples/subsys/ipc/ipc_service/multi_endpoint/
DREADME.rst50 IPC-service REMOTE [INST 0 - ENDP A] demo started
51 IPC-service REMOTE [INST 0 - ENDP B] demo started
52 IPC-service REMOTE [INST 1] demo started
53 REMOTE [0A]: 0
54 REMOTE [0A]: 2
56 REMOTE [0A]: 98
57 IPC-service REMOTE [INST 0 - ENDP A] demo ended.
58 REMOTE [0B]: 98
59 IPC-service REMOTE [INST 0 - ENDP B] demo ended.
60 REMOTE [1]: 98
[all …]
Dsysbuild.cmake7 "There is no remote board selected in Kconfig.sysbuild")
11 APPLICATION remote
12 SOURCE_DIR ${APP_DIR}/remote
16 native_simulator_set_child_images(${DEFAULT_IMAGE} remote)
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Drpr_cli.rst3 Remote Provisioning Client
6 The Remote Provisioning Client model is a foundation model defined by the Bluetooth
10 The Remote Provisioning Client model is introduced in the Bluetooth Mesh Protocol
16 The Remote Provisioning Client model communicates with a Remote Provisioning Server model
17 using the device key of the node containing the target Remote Provisioning Server model instance.
19 If present, the Remote Provisioning Client model must be instantiated on the primary
25 The scanning procedure is used to scan for unprovisioned devices located nearby the Remote
26 Provisioning Server. The Remote Provisioning Client starts a scan procedure by using the
56 The above example shows pseudo code for starting a scan procedure on the target Remote Provisioning
63 Additionally, the Remote Provisioning Client model also supports extended scanning with the
[all …]
Drpr_srv.rst3 Remote Provisioning Server
6 The Remote Provisioning Server model is a foundation model defined by the Bluetooth
10 The Remote Provisioning Server model is introduced in the Bluetooth Mesh Protocol
14 The Remote Provisioning Server does not have an API of its own, but relies on a
15 :ref:`bluetooth_mesh_models_rpr_cli` to control it. The Remote Provisioning Server
18 If present, the Remote Provisioning Server model must be instantiated on the primary element.
27 The following limitations apply to Remote Provisioning Server model:
/Zephyr-latest/subsys/bluetooth/audio/
DKconfig.mctl15 Enables support for control of local and remote media players
35 bool "Support for remote control of local media players"
38 This option enables support for remote control of local media
42 bool "Support for control of remote media player"
47 This options enables support for control of a remote media player.
50 bool "Support for accessing objects on remote player"
57 search results, ...) on a remote media player
/Zephyr-latest/tests/bsim/bluetooth/mesh/tests_scripts/provision/
Dpb_remote_pst_ncrp.sh9 # PB-Remote client (1st device):
11 # - provision the 3rd device over PB-Remote
12 # PB-Remote server (2nd device):
14 # - run PB-Remote bearer
15 # PB-Remote server (3rd device):
19 # PB-Remote client (1st device):
25 # PB-Remote server (3rd device):
28 # PB-Remote client (1st device):
30 # PB-Remote server (3rd device):
/Zephyr-latest/subsys/net/lib/sockets/
Dsocketpair.c36 * endpoint) are said to be 'remote'.
43 * - write operations may block if the remote @a recv_q is full
47 int remote; /**< the remote endpoint file descriptor */ member
77 const struct spair *remote = zvfs_get_fd_obj(spair->remote, in sock_is_connected() local
80 if (remote == NULL) { in sock_is_connected()
102 struct spair *const remote = zvfs_get_fd_obj(spair->remote, in spair_write_avail() local
105 if (remote == NULL) { in spair_write_avail()
109 return k_pipe_write_avail(&remote->recv_q); in spair_write_avail()
147 * T1 waits on A's write signal. T2 triggers the remote
153 * If the remote endpoint is already closed, the former operation does not
[all …]
/Zephyr-latest/samples/subsys/ipc/ipc_service/static_vrings/
Dsysbuild.cmake8 "There is no remote board selected in Kconfig.sysbuild")
11 set(REMOTE_APP remote)
19 # Add dependencies so that the remote sample will be built first
21 # remote core's build, such as the output image's LMA
25 native_simulator_set_child_images(${DEFAULT_IMAGE} remote)
DREADME.rst68 serial port, one is host another is remote:
87 IPC-service REMOTE [INST 0 - ENDP A] demo started
88 IPC-service REMOTE [INST 0 - ENDP B] demo started
89 IPC-service REMOTE [INST 1] demo started
90 REMOTE [1]: 0
91 REMOTE [1]: 2
92 REMOTE [1]: 4
93 REMOTE [1]: 6
94 REMOTE [1]: 8
/Zephyr-latest/samples/sysbuild/hello_world/
Dsysbuild.cmake9 APPLICATION remote
10 SOURCE_DIR ${APP_DIR}/remote
14 add_dependencies(${DEFAULT_IMAGE} remote)
15 sysbuild_add_dependencies(FLASH ${DEFAULT_IMAGE} remote)
/Zephyr-latest/samples/drivers/ipm/ipm_esp32/
Dsysbuild.cmake5 # Prepare the full board name to be used for the remote target
10 # Make sure the remote build is using different target than host CPU
17 SOURCE_DIR ${APP_DIR}/remote
21 # Add dependencies so that the remote sample will be built first
23 # remote core's build, such as the output image's LMA
DREADME.rst43 PRO_CPU is sending a request, waiting remote response...
45 PRO_CPU is sending a request, waiting remote response...
47 PRO_CPU is sending a request, waiting remote response...
49 PRO_CPU is sending a request, waiting remote response...
51 PRO_CPU is sending a request, waiting remote response...
53 PRO_CPU is sending a request, waiting remote response...
55 PRO_CPU is sending a request, waiting remote response...
57 PRO_CPU is sending a request, waiting remote response...
/Zephyr-latest/include/zephyr/xen/
Devents.h32 * Allocate event-channel between caller and remote domain
34 * @param remote_dom - remote domain domid
41 * Allocate event-channel between remote domains. Can be used only from Dom0.
43 * @param dom - first remote domain domid (may be DOMID_SELF)
44 * @param remote_dom - second remote domain domid
51 * Allocate local event channel, binded to remote port and attach specified callback
54 * @param remote_dom - remote domain domid
55 * @param remote_port - remote domain event channel port number
/Zephyr-latest/samples/drivers/mbox_data/
Dsysbuild.cmake8 "There is no remote board selected in Kconfig.sysbuild")
11 set(REMOTE_APP remote)
23 # 'zephyr_image_info.h' generated by remote application.
25 # Let's build the remote application first
/Zephyr-latest/tests/drivers/mbox/mbox_data/
Dsysbuild.cmake8 "There is no remote board selected in Kconfig.sysbuild")
11 set(REMOTE_APP remote)
23 # 'zephyr_image_info.h' generated by remote application.
25 # Let's build the remote application first
/Zephyr-latest/samples/subsys/ipc/rpmsg_service/
DREADME.rst14 perspective and code. Note that the remote and primary image core images can be
51 serial port, one is master another is remote:
72 RPMsg Service [remote] demo started
73 Remote core received a message: 0
74 Remote core received a message: 2
75 Remote core received a message: 4
77 Remote core received a message: 98
103 remote) will appear on the corresponding serial ports:
124 RPMsg Service [remote] demo started
125 Remote core received a message: 0
[all …]
/Zephyr-latest/samples/net/syslog_net/
DREADME.rst2 :name: Remote syslog
5 Enable a remote syslog service that sends syslog messages to a remote server
10 This sample application enables a remote syslog service that will
11 send syslog messages to a remote server, as configured in ``prj.conf``.
26 For configuring the remote IPv6 syslog server, set the following
/Zephyr-latest/samples/drivers/mbox/
Dsysbuild.cmake8 "There is no remote board selected in Kconfig.sysbuild")
11 set(REMOTE_APP remote)
27 # 'zephyr_image_info.h' generated by remote application.
29 # Let's build the remote application first
/Zephyr-latest/samples/subsys/ipc/openamp/remote/
Dsample.yaml3 name: OpenAMP example integration (remote)
5 sample.ipc.openamp.remote:
12 harness: remote
/Zephyr-latest/dts/bindings/video/
Dvideo-interfaces.yaml12 If a port can be configured to work with more than one remote device on the same
37 Two 'endpoint' nodes must be linked with each other via their 'remote-endpoint'
39 references are currently not possible. A 'remote-endpoint-label' string is used
40 instead to be able to specify, at least, the label of the peer remote-endpoint.
45 remote-endpoint-label = "sink";
50 remote-endpoint-label = "source";
60 remote-endpoint-label:
64 Label of the 'remote-endpoint' subnode that interfaces with this endpoint.
65 This property is used as a 'work-around' to be able to declare the remote
66 endpoint and should be replaced by a "remote-endpoint" phandle property when

12345678910>>...25