/Zephyr-Core-3.5.0/boards/arm/mec172xevb_assy6906/support/ |
D | mec172x_remote_flasher.py | 9 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-Core-3.5.0/submanifests/ |
D | optional.yaml | 9 remote: upstream 15 remote: upstream 21 remote: upstream 27 remote: upstream 33 remote: upstream 39 remote: upstream 46 remote: upstream 52 remote: upstream 58 remote: upstream
|
/Zephyr-Core-3.5.0/include/zephyr/bluetooth/mesh/ |
D | rpr_cli.h | 19 * @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-Core-3.5.0/samples/subsys/ipc/ipc_service/icmsg/ |
D | README.rst | 31 serial port, one is host another is remote: 53 [00:00:00.006,256] <inf> remote: IPC-service REMOTE demo started 54 [00:00:00.006,378] <inf> remote: Ep bounded 55 [00:00:00.006,439] <inf> remote: Perform sends for 1000 [ms] 57 [00:00:01.417,572] <inf> remote: Sent 235527 [Bytes] over 1000 [ms] 58 [00:00:01.417,602] <inf> remote: IPC-service REMOTE demo ended 60 [00:00:00.006,256] <inf> remote: IPC-service REMOTE demo started 61 [00:00:00.006,347] <inf> remote: Ep bounded 62 [00:00:00.006,378] <inf> remote: Perform sends for 1000 [ms] 63 [00:00:01.006,164] <inf> remote: Sent 236797 [Bytes] over 1000 [ms] [all …]
|
/Zephyr-Core-3.5.0/doc/connectivity/bluetooth/api/mesh/ |
D | rpr_cli.rst | 3 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 …]
|
D | rpr_srv.rst | 3 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.
|
/Zephyr-Core-3.5.0/samples/subsys/ipc/ipc_service/static_vrings/ |
D | README.rst | 31 serial port, one is host another is remote: 50 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 [1]: 0 54 REMOTE [1]: 2 55 REMOTE [1]: 4 56 REMOTE [1]: 6 57 REMOTE [1]: 8
|
/Zephyr-Core-3.5.0/subsys/bluetooth/audio/ |
D | Kconfig.mctl | 16 Enables support for control of local and remote media players 36 bool "Support for remote control of local media players" 39 This option enables support for remote control of local media 43 bool "Support for control of remote media player" 48 This options enables support for control of a remote media player. 51 bool "Support for accessing objects on remote player" 58 search results, ...) on a remote media player
|
/Zephyr-Core-3.5.0/subsys/net/lib/sockets/ |
D | socketpair.c | 36 * 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 = z_get_fd_obj(spair->remote, in sock_is_connected() local 80 if (remote == NULL) { in sock_is_connected() 102 struct spair *const remote = z_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-Core-3.5.0/tests/bsim/bluetooth/mesh/tests_scripts/provision/ |
D | pb_remote_pst_ncrp.sh | 9 # 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-Core-3.5.0/samples/subsys/ipc/rpmsg_service/ |
D | README.rst | 49 serial port, one is master another is remote: 70 RPMsg Service [remote] demo started 71 Remote core received a message: 0 72 Remote core received a message: 2 73 Remote core received a message: 4 75 Remote core received a message: 98 101 remote) will appear on the corresponding serial ports: 122 RPMsg Service [remote] demo started 123 Remote core received a message: 0 124 Remote core received a message: 2 [all …]
|
/Zephyr-Core-3.5.0/include/zephyr/xen/ |
D | events.h | 32 * 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-Core-3.5.0/samples/net/syslog_net/ |
D | README.rst | 2 :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-Core-3.5.0/samples/drivers/ipm/ipm_esp32/ |
D | README.rst | 42 PRO_CPU is sending a fake request, waiting remote response... 44 PRO_CPU is sending a fake request, waiting remote response... 46 PRO_CPU is sending a fake request, waiting remote response... 48 PRO_CPU is sending a fake request, waiting remote response... 50 PRO_CPU is sending a fake request, waiting remote response... 52 PRO_CPU is sending a fake request, waiting remote response... 54 PRO_CPU is sending a fake request, waiting remote response...
|
/Zephyr-Core-3.5.0/samples/subsys/ipc/openamp/remote/ |
D | sample.yaml | 3 name: OpenAMP example integration (remote) 5 sample.ipc.openamp.remote: 12 harness: remote
|
/Zephyr-Core-3.5.0/samples/subsys/ipc/rpmsg_service/remote/ |
D | sample.yaml | 4 name: RPMsg Service example integration (remote) 6 harness: remote 8 sample.ipc.rpmsg_service.remote:
|
/Zephyr-Core-3.5.0/samples/subsys/ipc/openamp/ |
D | sysbuild.cmake | 8 SOURCE_DIR ${APP_DIR}/remote 12 # Add dependencies so that the remote sample will be built first 14 # remote core's build, such as the output image's LMA
|
D | README.rst | 12 and code. Note that the remote and primary core images can be flashed 69 serial port, one is master another is remote: 90 OpenAMP[remote] demo started 91 Remote core received a message: 0 92 Remote core received a message: 2 93 Remote core received a message: 4 95 Remote core received a message: 98
|
/Zephyr-Core-3.5.0/samples/drivers/ipm/ipm_mcux/ |
D | sysbuild.cmake | 8 SOURCE_DIR ${APP_DIR}/remote 12 # Add dependencies so that the remote sample will be built first 14 # remote core's build, such as the output image's LMA
|
/Zephyr-Core-3.5.0/scripts/ |
D | series-push-hook.sh | 8 remote=$1 25 # At each (forced) push, examine all commits since $remote/main 26 base_commit=`git rev-parse $remote/main`
|
/Zephyr-Core-3.5.0/ |
D | west.yml | 19 remote: upstream 42 remote: babblesim 49 remote: babblesim 56 remote: babblesim 63 remote: babblesim 70 remote: babblesim 77 remote: babblesim 84 remote: babblesim 91 remote: babblesim 98 remote: babblesim [all …]
|
/Zephyr-Core-3.5.0/boards/xtensa/intel_adsp_cavs25/doc/ |
D | intel_adsp_generic.rst | 168 Remote Flashing to cAVS-based ADSP 174 this point onward, we will refer to the board as the "remote host" and your 178 :zephyr_file:`soc/xtensa/intel_adsp/tools/remote-fw-service.py` will receive 182 :file:`remote-fw-service.py`. 187 scp -r $ZEPHYR_BASE/soc/xtensa/intel_adsp/tools/remote-fw-service.py username@remotehostname 189 sudo ./remote-fw-service.py 191 :file:`remote-fw-service.py` uses ports 9999 and 10000 on the remote host to 203 west flash --remote-host remotehostname --pty remotehostname 209 …ntel_adsp/tools/cavstool_client.py,-s,remotehostname,-l" --west-flash="--remote-host=remotehostnam… 212 :file:`cavstool_client.py` to :file:`remote-fw-service.py` is forwarded through [all …]
|
/Zephyr-Core-3.5.0/samples/subsys/debug/gdbstub/ |
D | README.rst | 4 Use GDB Remote Serial Protocol to debug a Zephyr application running on QEMU. 10 Remote Serial Protocol (RSP) capabilities. 29 (gdb) target remote :5678
|
/Zephyr-Core-3.5.0/include/zephyr/logging/ |
D | log_multidomain_helper.h | 148 /** @brief Union for holding data returned by associated remote backend. */ 167 /** @brief Remote link API. */ 170 /** @brief Remote link structure. */ 189 /** @brief Remote backend API. */ 192 /** @brief Remote backend structure. */ 202 /** @brief Function to be called when data is received from remote. 218 /** @brief Function called when connection with remote is established. 225 /** @brief Function to be called when data is received from remote. 241 /** @brief Function called when connection with remote is established.
|
/Zephyr-Core-3.5.0/samples/drivers/mbox/remote/ |
D | sample.yaml | 2 name: MBOX IPC sample (remote) 9 harness: remote
|