Home
last modified time | relevance | path

Searched refs:update (Results 151 – 175 of 420) sorted by relevance

12345678910>>...17

/Zephyr-latest/boards/m5stack/m5stack_atoms3_lite/doc/
Dindex.rst42 It is recommended running the command above after :file:`west update`.
/Zephyr-latest/boards/m5stack/m5stack_atom_lite/doc/
Dindex.rst42 It is recommended running the command above after :file:`west update`.
/Zephyr-latest/boards/rakwireless/rak3172/doc/
Dindex.rst52 $ pyocd pack --update
/Zephyr-latest/doc/develop/west/
Dinstall.rst40 like ``west init``, ``west update``, along with any extensions discovered
/Zephyr-latest/subsys/bluetooth/mesh/
Dmain.c425 if (mod->pub && mod->pub->update) { in model_suspend()
494 if (mod->pub && mod->pub->update) { in model_resume()
/Zephyr-latest/include/zephyr/bluetooth/mesh/
Daccess.h757 int (*update)(const struct bt_mesh_model *mod); member
774 .update = _update, \
/Zephyr-latest/doc/releases/
Drelease-notes-1.13.rst249 * ext: stm32cube: update stm32l4xx cube version
250 * ext: stm32cube: update stm32f7xx cube version
251 * ext: stm32cube: update stm32f4xx cube version
252 * ext: stm32cube: update stm32f3xx cube version
253 * ext: stm32cube: update stm32f1xx cube version
293 * :github:`9788` - update to mbedTLS 2.12.0
319 * :github:`9649` - readme of LPCxpresso54114_mo core needs update for R1.13
451 * :github:`8871` - drivers: can: Compiling error due to stm23Cube update
492 * :github:`8636` - MCUboot firmware update issue
536 * :github:`8366` - mcumgr: unable to perform 2nd update
[all …]
/Zephyr-latest/boards/nxp/frdm_k22f/doc/
Dindex.rst181 and require an update. Please see the `DAPLink Bootloader Update`_ page for
182 instructions to update from the CMSIS-DAP bootloader to the DAPLink bootloader.
305 https://os.mbed.com/blog/entry/DAPLink-bootloader-update/
/Zephyr-latest/boards/shields/nrf7002eb/doc/
Dindex.rst38 west update
/Zephyr-latest/boards/shields/nrf7002ek/doc/
Dindex.rst38 west update
/Zephyr-latest/doc/connectivity/networking/api/
Dnet_timeout.rst45 explicitly update the timeout, which should be done by canceling any
/Zephyr-latest/samples/modules/tflite-micro/magic_wand/
DREADME.rst33 west update
/Zephyr-latest/samples/bluetooth/encrypted_advertising/
DREADME.rst16 - and the update of the Randomizer field whenever the RPA is changed.
/Zephyr-latest/doc/services/device_mgmt/smp_groups/
Dsmp_group_1.rst37 is supposed to run from the "primary slot" and update is supposed to be
257 The image upload command allows to update application image.
333 The MCUmgr library uses "sha" field to tag ongoing update session, to be able
337 state and if it matches it will respond to update client application with
396 | "off" | offset of last successfully written byte of update. |
/Zephyr-latest/scripts/
Dget_maintainer.py244 res.update(self.path2areas(path))
265 res.update(areas)
Dlist_boards.py252 board.update({'dir': board_yml.parent})
346 boards.update(b)
/Zephyr-latest/subsys/net/l2/ethernet/gptp/
DKconfig170 bool "Use a default clock update function"
173 Use a default internal function to update port local clock.
/Zephyr-latest/doc/project/
Dcode_flow.rst59 - Keep the branch in sync with upstream and update on a regular basis.
/Zephyr-latest/share/sysbuild/images/bootloader/
DKconfig43 slots. In this mode application is not able to DFU its own update to secondary slot and
127 application used to update the slot0_partition application.
/Zephyr-latest/tests/bsim/bluetooth/mesh/src/
Dmesh_test.c124 .update = test_model_pub_update,
155 .update = test_vnd_model_pub_update,
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Daccess.rst98 populate the :c:member:`bt_mesh_model_pub.update` callback. The
99 :c:member:`bt_mesh_model_pub.update` callback will be called right before the
104 configure the :c:member:`bt_mesh_model_pub.update` callback to be triggered
213 change after a firmware update. See :ref:`bluetooth_mesh_dfu_srv_comp_data_and_models_metadata`
Ddfu.rst124 incoming firmware update, and what the effect of the update would be. The metadata format is
292 passed to the Distributor along with an update policy. The update policy decides whether the
308 response to the Firmware Update Client, indicating if the firmware update will have any effect on
323 attempts to update the lost Target nodes after the current attempt is finished.
/Zephyr-latest/boards/silabs/dev_kits/xg24_ek2703a/doc/
Dindex.rst75 Before using the kit the first time, you should update the J-Link firmware
/Zephyr-latest/boards/silabs/dev_kits/sltb009a/doc/
Dindex.rst80 Before using the kit the first time, you should update the J-Link firmware
/Zephyr-latest/boards/waveshare/esp32s3_touch_lcd_1_28/doc/
Dindex.rst74 It is recommended running the command above after :file:`west update`.

12345678910>>...17