Home
last modified time | relevance | path

Searched refs:should (Results 251 – 275 of 1262) sorted by relevance

1...<<11121314151617181920>>...51

/Zephyr-latest/doc/connectivity/networking/api/
Dmqtt.rst97 When notified, the application should call the ``mqtt_input`` function to process
99 therefore the application should use socket ``poll`` to wait for the response.
120 In the above code snippet, the MQTT callback function should set the ``connected``
155 credentials that the MQTT library should use for authentication. We do not specify
Dnet_if.rst20 For Ethernet network, a macro called ``ETH_NET_DEVICE_INIT()`` should be used
70 Network drivers or L2 implementations should not change administrative state on
93 driver should set the dormant state to ON during initialization, and once it
94 detects that it connected to a Wi-Fi network, the dormant state should be set
/Zephyr-latest/boards/xen/xenvm/doc/
Dindex.rst46 default value, which should be corrected for user's actual hardware.
75 environment. On other hand, Zephyr uses static configuration that should be know
164 static, build time configuration. While provided configuration should work on
168 Also, frequency of system timer is board specific and should be updated when running
/Zephyr-latest/doc/develop/test/twister/
Dtwister_blackbox.rst7 to understand existing files and create their own. All developers should fix any tests
20 Blackbox tests should not be aware of the internal twister code. Instead, they should
99 Twister call. How should we approach that?
/Zephyr-latest/drivers/sensor/st/vl53l1x/
DKconfig30 Enable to use the xshut pin on the VL53L1X. If not, the pin should be
/Zephyr-latest/subsys/mgmt/mcumgr/transport/
DKconfig.dummy9 # Options defined in this file should be prefixed:
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Dcfg.rst9 Bluetooth Mesh nodes should generally be configured by a central network
Dcfg_cli.rst17 and ``addr`` as their first parameters. These should be set to the network
/Zephyr-latest/doc/hardware/peripherals/sensor/
Dchannels.rst18 At times only :c:enum:`sensor_channel` is used but this should be considered
/Zephyr-latest/include/zephyr/linker/
Dthread-local-storage.ld22 /* The "master copy" of tdata should be only in flash on XIP systems */
/Zephyr-latest/subsys/rtio/
DKconfig.workq34 to issue, the bigger this pool should be.
/Zephyr-latest/doc/releases/
Dmigration-guide-3.5.rst133 Vbat or temperature) using the ADC driver. The dedicated sensor driver should
216 in the SOC devicetree definition. Downstream boards should not override this property and
248 * NXP i.MX RT based boards should now enable
281 ``16``). Bootloaders that use a part of the SRAM should set this value to an
344 :c:func:`smp_add_cmd_err` should be used instead, ``MGMT_CB_ERROR_RET`` is
345 now deprecated and :c:enumerator:`MGMT_CB_ERROR_ERR` should be used instead.
374 The GIC version should now be specified by adding the appropriate compatible, for
378 to configure NFCT pins as GPIOs, should instead set the new UICR
389 to configure reset GPIO as nRESET, should instead set the new UICR
400 Instead the new :kconfig:option:`CONFIG_MODEM_CELLULAR` driver should be used.
[all …]
Dmigration-guide-4.0.rst25 signing should be set in :kconfig:option:`CONFIG_MCUBOOT_EXTRA_IMGTOOL_ARGS` instead.
30 * Removed the deprecated :kconfig:option:`CONFIG_MP_NUM_CPUS`, application should be updated to use
59 … you want to enforce the selection of another runner like OpenOCD or pyOCD for flashing, you should
127 ``microchip,mcp230xx`` and ``microchip,mcp23sxx`` should change their devicetree ``compatible``
131 their driver API, users of these devices should ensure they pass appropriate values to
222 Existing devicetree compatibles should be updated to :dtcompatible:`u-blox,m8`, and Kconfig
258 devicetree property ``detect-cd`` should be added to the USDHC node in use.
276 property names should be updated to the new property names.
376 scan delegator registration and initialization dynamically. It should also be mentioned that
401 * ``BT_AUDIO_BROADCAST_CODE_SIZE`` has been removed and ``BT_ISO_BROADCAST_CODE_SIZE`` should be
[all …]
/Zephyr-latest/boards/silabs/starter_kits/efm32wg_stk3800/doc/
Dindex.rst79 Before using the kit the first time, you should update the J-Link firmware
105 should see a USB connection which exposes a Mass Storage (STK3800) and a
115 Reset the board and you should be able to see on the corresponding Serial Port
/Zephyr-latest/boards/atmel/sam/sam4l_ek/doc/
Dindex.rst90 terminal should be :code:`/dev/ttyACM0`. For example:
97 Connection should be configured as follows:
112 You should see "Hello World! sam4l_ek" in your terminal.
/Zephyr-latest/boards/atmel/sam0/same54_xpro/doc/
Dindex.rst133 terminal should be :code:`/dev/ttyACM0`. For example:
140 string. Connection should be configured as follows:
155 You should see "Hello World! same54_xpro" in your terminal.
/Zephyr-latest/subsys/logging/
DKconfig.misc57 removing strings from final binary and should be used for dictionary
73 Logging strings cannot use %p with character pointers. They should be
110 read-only string arguments in the package. This should be selected by
/Zephyr-latest/boards/adafruit/feather_m0_lora/doc/
Dindex.rst101 terminal should be :code:`/dev/ttyACM0`. For example:
108 string. Connection should be configured as follows:
125 You should see "Hello World! adafruit_feather_m0_lora" in your terminal.
/Zephyr-latest/boards/adafruit/grand_central_m4_express/doc/
Dindex.rst89 terminal should be :code:`/dev/ttyUSB0`. For example:
96 string. Connection should be configured as follows:
113 You should see "Hello World! adafruit_grand_central_m4_express" in your terminal.
/Zephyr-latest/doc/develop/tools/
Dvscode.rst12 The instructions have been tested on Linux, but the steps should be the same for macOS and
67 Linting errors in the code should now be resolved, and you should be able to navigate through the
/Zephyr-latest/samples/net/telnet/
DREADME.rst42 Once started, you should see you IP address details for example:
98 Reset the board, you should see first on the console:
118 At this point you should be able to connect via telnet over the network.
/Zephyr-latest/boards/arduino/mkrzero/doc/
Dindex.rst102 terminal should be :code:`/dev/ttyACM0`. For example:
109 string. Connection should be configured as follows:
126 You should see "Hello World! arduino_mkrzero" in your terminal.
/Zephyr-latest/drivers/retained_mem/
DKconfig29 memory access. This option should only be enabled when retained
/Zephyr-latest/subsys/mgmt/mcumgr/grp/os_mgmt_client/
DKconfig8 # Options defined in this file should be prefixed:
/Zephyr-latest/doc/templates/
Dboard.tmpl6 The picture should be named after the board (e.g., "board_name.webp")

1...<<11121314151617181920>>...51