Home
last modified time | relevance | path

Searched refs:update (Results 351 – 375 of 420) sorted by relevance

1...<<11121314151617

/Zephyr-latest/samples/net/lwm2m_client/
DREADME.rst174 instance. In that case, the user should make sure to update the port number in
/Zephyr-latest/subsys/usb/device_next/class/
Dusbd_midi2.c353 .update = usbd_midi_class_update,
Dusbd_uac2.c914 .update = uac2_update,
/Zephyr-latest/boards/st/nucleo_u5a5zj_q/doc/
Dindex.rst265 $ pyocd pack --update
/Zephyr-latest/doc/releases/
Drelease-notes-3.4.rst398 update procedures.
399 * Implemented the CAP unicast audio start, stop and metadata update procedures.
1113 * Added possibility to register a callback function for FW update cancel action.
1120 * Fixed a possible out-of-bounds memory access when creating FW update object.
1432 Among other things, this update brings:
Drelease-notes-2.0.rst350 over-the-air update of devices.
740 * :github:`17990` - BLE Mesh When IV update test procedure
748 * :github:`17951` - RFC: update FS API for readdir consistency
915 * :github:`17114` - drivers: usb_dc_stm32 broken after west update
1042 * :github:`16416` - sram size for RT1015 and RT1020 needs to be update.
1069 * :github:`16278` - [Zepyhr v1.14.0] Unable to update FW with mcumgr over UART
1340 * :github:`14604` - BLE disconnection caused by channel map request or connection parameter update
Drelease-notes-1.14.rst42 * :github:`23069` - Bluetooth: controller: Assert in data length update procedure
133 * :github:`16416` - sram size for RT1015 and RT1020 needs to be update.
332 * :github:`16416` - sram size for RT1015 and RT1020 needs to be update.
867 * ARP cache update fix.
1128 * :github:`15300` - Bluetooth: Mesh: bt_mesh_fault_update() doesn't update publication message
1163 * :github:`15157` - mps2_an385 and GNU Arm Embedded gcc-arm-none-eabi-7-2018-q2-update failed tests
1283 …4635` - bluetooth: controller: Control procedure collision with Encryption and PHY update procedure
1310 * :github:`14492` - doc: update robots.txt to exclude more old docs
2167 * :github:`9510` - zephyr/doc/security/security-overview.rst needs update
2190 * :github:`8796` - Bluetooth: controller: assert on conn update in slave role under max. throughput…
[all …]
Dmigration-guide-4.1.rst570 If a provisioned device is going to update its image that was built with
574 it should be unprovisioned first and reprovisioned after update again.
Drelease-notes-1.5.rst260 * ``ZEP-703`` - USB sample apps are broken after QMSI update
Drelease-notes-3.6.rst16 * Integrated Trusted Firmware-M (TF-M) 2.0, including an update to Mbed TLS 3.5.2.
1029 * Added support for image slot size checking to ensure an update can be utilised by MCUboot.
1246 is used to update the primary image.
1266 It is used by non-swap update modes.
Drelease-notes-2.6.rst714 * Changed to trigger registration update only when registered.
1001 update to mbedtls.
1028 To update, replace uses like this:
1194 * :github:`35191` - GIT Checkout of Master Branch is 2.6.0rc1 versus west update as 2.5.99
1317 * :github:`34757` - west update: Default behavior should fetch only --depth 1
1416 * :github:`34201` - Fatal error when perform "bt phy-update" if there is not any connections at ./t…
1661 * :github:`33269` - ILI9341 (ILI9XXX) set orientation function fails to update the display area cor…
1969 * :github:`32234` - Documentation: How to update Zephyr itself (with west)
2086 * :github:`28096` - fatfs update to latest upstream version
Drelease-notes-1.11.rst320 * :github:`5101` - LwM2M: device hang after requesting a firmware update to a loopback device IP
323 * :github:`5136` - "Distinguishing Features" section in docs is outdated and needs an update
/Zephyr-latest/boards/arm/mps3/doc/
Dindex.rst316 The update requires 3 steps:
/Zephyr-latest/doc/_extensions/zephyr/kconfig/static/
Dkconfig.mjs371 /* update navigation */
/Zephyr-latest/boards/arm/v2m_musca_b1/doc/
Dindex.rst260 Musca-B1 test chip also support to boot from 8MB QSPI. You can update the
/Zephyr-latest/boards/nxp/lpcxpresso55s69/doc/
Dindex.rst296 …2. To update the debug firmware, please follow the instructions on `LPCXPRESSO55S69 Debug Firmware…
/Zephyr-latest/subsys/bluetooth/mesh/
DKconfig770 will update the replay protection cache for messages those cannot be handled
817 pages after a performed device firmware update.
1562 hex "Sequence number limit to start iv update"
1566 This option specifies the sequence number value to start iv update.
1859 infrequently a value as low as 0 (update storage for every
/Zephyr-latest/samples/net/mqtt_publisher/
DREADME.rst142 While it is possible to set up a local secure MQTT server and update the
/Zephyr-latest/subsys/bluetooth/host/
Dhci_core.c2463 struct bt_hci_cmd_state_set *update = cmd(buf)->state; in hci_cmd_done() local
2465 atomic_set_bit_to(update->target, update->bit, update->val); in hci_cmd_done()
/Zephyr-latest/scripts/
Dspelling.txt1614 udpate||update
1671 upate||update
/Zephyr-latest/doc/contribute/
Dguidelines.rst422 * ``doc: update wiki references to new site``
654 information as you can about your change, update appropriate documentation,
781 By force pushing your update, your original pull request will be updated
/Zephyr-latest/boards/arm/v2m_musca_s1/doc/
Dindex.rst254 32MB off-chip QSPI flash. You can update the DAPLink firmware and set the boot
/Zephyr-latest/doc/connectivity/bluetooth/
Dbluetooth-tools.rst51 Linux distribution. If you need to build BlueZ from scratch to update to a
/Zephyr-latest/doc/develop/api/
Dapi_lifecycle.rst269 migration and update the roadmap with the aim to remove the API in the next
/Zephyr-latest/doc/develop/debug/
Dindex.rst269 :file:`C:\\gcc-arm-none-eabi-6_2017-q2-update\\bin\\arm-none-eabi-gdb.exe`

1...<<11121314151617