Searched full:monitoring (Results 1 – 25 of 124) sorted by relevance
12345
/Zephyr-latest/doc/connectivity/networking/ |
D | network_monitoring.rst | 35 interface so that we can transfer monitoring data from Zephyr to host. 136 ``net-shell`` to setup and enable the monitoring. 138 The network packet monitoring needs to be setup first. The ``net-shell`` has 176 The current monitoring configuration can be checked like this: 187 monitoring, the ``Capture iface`` is not set. 189 Then we need to enable the network packet monitoring like this: 198 monitoring in this example. The monitoring system avoids to capture already 217 After enabling the monitoring, the system will send captured (either received 220 The monitoring can be disabled like this: 226 which will turn currently running monitoring off. The monitoring setup can [all …]
|
/Zephyr-latest/dts/bindings/watchdog/ |
D | nxp,fs26-wdog.yaml | 9 functionalities for system control and monitoring, including a configurable 54 The Challenger watchdog monitoring feature is enabled for ASIL D devices. 57 The Simple watchdog monitoring feature is enabled for ASIL B devices. This
|
/Zephyr-latest/samples/sensor/tmp108/ |
D | Kconfig | 28 it requires continuous monitoring mode to be enabled 39 it requires continuous monitoring mode to be enabled
|
/Zephyr-latest/dts/bindings/charger/ |
D | nxp,pf1550-charger.yaml | 33 pf1550,thermistor-monitoring-mode: 42 Thermistor monitoring mode.
|
D | maxim,max20335-charger.yaml | 68 thermistor-monitoring-mode: 77 Thermistor monitoring mode.
|
/Zephyr-latest/subsys/net/conn_mgr/ |
D | Kconfig | 29 Sets the stack size which will be used by the connection manager for connectivity monitoring. 32 int "Monitoring thread starting priority"
|
/Zephyr-latest/include/zephyr/debug/ |
D | cpu_load.h | 18 * @brief Module for monitoring CPU Load 20 * This module allow monitoring of the CPU load.
|
/Zephyr-latest/doc/connectivity/networking/conn_mgr/ |
D | main.rst | 19 * :ref:`Connectivity monitoring <conn_mgr_monitoring>` (header file :file:`include/zephyr/net/conn_… 35 Connectivity monitoring 38 Connectivity monitoring tracks all available ifaces (whether or not they support :ref:`Connectivity… 92 Connectivity monitoring is enabled if the :kconfig:option:`CONFIG_NET_CONNECTION_MANAGER` Kconfig o… 114 /* Call this before Connection Manager monitoring initializes */ 136 …vity events, you should register your listener(s) before Connection Manager monitoring initializes. 144 Connectivity monitoring may trigger events immediately upon initialization. 146 If your application registers its event listeners after connectivity monitoring initializes, it is … 148 …gister its event listeners <conn_mgr_monitoring_usage>` before connectivity monitoring initializes. 150 Connectivity monitoring initializes using the :c:macro:`SYS_INIT` ``APPLICATION`` initialization pr… [all …]
|
/Zephyr-latest/include/zephyr/drivers/i3c/ |
D | error_types.h | 28 /** Monitoring Error */ 79 /** Monitoring Error */
|
/Zephyr-latest/subsys/net/lib/lwm2m/ |
D | lwm2m_obj_connmon.c | 33 /* Connectivity Monitoring resource IDs */ 110 /* only 1 instance of Connection Monitoring object exists */ 194 LOG_DBG("Create LWM2M connectivity monitoring instance: %d", in connmon_create() 204 /* initialize the Connection Monitoring field data */ in lwm2m_connmon_init()
|
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
D | statistic.rst | 6 The frame statistic API allows monitoring the number of received frames over
|
D | heartbeat.rst | 6 The Heartbeat feature provides functionality for monitoring Bluetooth Mesh nodes
|
/Zephyr-latest/tests/bsim/bluetooth/mesh/tests_scripts/beacon/ |
D | beacon_cache.sh | 10 # 0. RX device starts monitoring all accepted SNB messages.
|
/Zephyr-latest/tests/bsim/bluetooth/mesh/tests_scripts/priv_beacon/ |
D | priv_beacon_cache.sh | 10 # 0. RX device starts monitoring all accepted private beacon messages.
|
/Zephyr-latest/dts/bindings/power-domain/ |
D | power-domain-gpio-monitor.yaml | 10 child nodes. Additionally, due to the asynchronous nature of monitoring, a
|
/Zephyr-latest/subsys/stats/ |
D | Kconfig | 9 and usage monitoring. Statistics can be retrieved with the mcumgr
|
/Zephyr-latest/drivers/adc/ |
D | Kconfig.tla202x | 13 TLA202x Cost-Optimized, Ultra-Small, 12-Bit, System-Monitoring ADCs
|
/Zephyr-latest/subsys/net/lib/shell/ |
D | events.c | 576 PR_INFO("Network event monitoring %s.\n", "disabled"); in event_mon_handler() 586 PR_INFO("Network event monitoring is already %s.\n", in cmd_net_events_on() 603 PR_INFO("Network event monitoring %s.\n", "enabled"); in cmd_net_events_on() 624 PR_INFO("Network event monitoring is already %s.\n", in cmd_net_events_off() 647 PR("Network event monitoring is %s.\n", in cmd_net_events() 651 PR_INFO("Give 'on' to enable event monitoring and " in cmd_net_events() 673 SHELL_CMD(on, NULL, "Turn on network event monitoring.", 675 SHELL_CMD(off, NULL, "Turn off network event monitoring.",
|
/Zephyr-latest/subsys/net/ip/ |
D | Kconfig.mgmt | 103 "net events [on|off]" command. The monitoring is disabled by 119 Allow user to start monitoring network events automatically
|
/Zephyr-latest/subsys/mgmt/osdp/ |
D | Kconfig.pd | 94 menu "Contact Status Monitoring" 108 - 03: Like 02, plus: PD supports supervised monitoring. The operating mode 119 endmenu # "Contact Status Monitoring"
|
/Zephyr-latest/dts/bindings/power/ |
D | atmel,sam-supc.yaml | 8 monitoring of the device. It have a special feature that it can wake-up the
|
/Zephyr-latest/samples/sensor/ina219/ |
D | README.rst | 35 When monitoring a 3.3 V bus with a 0.1 Ohm shunt resistor
|
/Zephyr-latest/tests/drivers/build_all/charger/ |
D | i2c.dtsi | 33 thermistor-monitoring-mode = "JEITA-2";
|
/Zephyr-latest/boards/particle/boron/ |
D | particle_boron.dts | 47 &i2c1 { /* power monitoring */
|
/Zephyr-latest/doc/connectivity/networking/api/ |
D | net_shell.rst | 27 "net events", "Enable network event monitoring. Only available if
|
12345