Searched +full:- +full:- +full:upgrade (Results 1 – 25 of 113) sorted by relevance
12345
/Zephyr-latest/samples/subsys/lorawan/fuota/ |
D | README.rst | 1 .. zephyr:code-sample:: lorawan-fuota 3 :relevant-api: lorawan_api 5 Perform a LoRaWAN firmware-upgrade over the air (FUOTA) operation. 10 An application to demonstrate firmware-upgrade over the air (FUOTA) over LoRaWAN. 14 - Application Layer Clock Synchronization (`TS003-2.0.0`_) 15 - Remote Multicast Setup (`TS005-1.0.0`_) 16 - Fragmented Data Block Transport (`TS004-1.0.0`_) 19 work queue thread. After a firmware upgrade is successfully received, the application is notified 20 via a callback and can reboot the device into MCUboot to apply the upgrade. 24 .. _`TS003-2.0.0`: https://resources.lora-alliance.org/technical-specifications/ts003-2-0-0-applica… [all …]
|
D | sample.yaml | 2 description: Demonstration of LoRaWAN Firmware Upgrade Over The Air 7 filter: dt_label_with_parent_compat_enabled("slot0_partition", "fixed-partitions") 8 and dt_label_with_parent_compat_enabled("slot1_partition", "fixed-partitions") 9 and dt_chosen_enabled("zephyr,flash-controller") and CONFIG_FLASH_HAS_DRIVER_ENABLED 14 - "<inf> lorawan_fuota: Joining network over OTAA" 18 - nucleo_wl55jc 21 - nucleo_wl55jc
|
/Zephyr-latest/doc/services/device_mgmt/ |
D | dfu.rst | 3 Device Firmware Upgrade 9 The Device Firmware Upgrade subsystem provides the necessary frameworks to 10 upgrade the image of a Zephyr-based application at run time. It currently 26 The flash image API as part of the Device Firmware Upgrade (DFU) subsystem 31 ------------- 45 ------------- 57 Zephyr is directly compatible with the open source, cross-RTOS 59 format required by it, so that Device Firmware Upgrade is available when MCUboot 69 .. code-block:: devicetree 73 zephyr,code-partition = &slot0_partition; [all …]
|
D | ota.rst | 3 Over-the-Air Update 9 Over-the-Air (OTA) Update is a method for delivering firmware updates to remote 33 upgrade occurs. 47 There is a :zephyr:code-sample:`hawkbit-api` sample included in the 48 Zephyr :zephyr:code-sample-category:`mgmt` section. 58 There is an :zephyr:code-sample:`updatehub-fota` sample included in the Zephyr 59 :zephyr:code-sample-category:`mgmt` section. 67 upgrade occurs. 69 There is an :zephyr:code-sample:`smp-svr` sample included in the Zephyr 70 :zephyr:code-sample-category:`mgmt` section. [all …]
|
/Zephyr-latest/samples/net/sockets/http_server/src/ |
D | ws.h | 4 * SPDX-License-Identifier: Apache-2.0 13 * @param request_ctx Request context associated with websocket HTTP upgrade request 24 * @param request_ctx Request context associated with websocket HTTP upgrade request
|
/Zephyr-latest/boards/nxp/lpcxpresso55s36/ |
D | Kconfig.defconfig | 4 # SPDX-License-Identifier: Apache-2.0 10 # Board only supports MCUBoot via "upgrade only" method:
|
/Zephyr-latest/boards/nxp/frdm_mcxa156/ |
D | Kconfig.defconfig | 1 # FRDM-MCXA156 board 4 # SPDX-License-Identifier: Apache-2.0 10 # Board only supports MCUBoot via "upgrade only" method:
|
/Zephyr-latest/boards/nxp/lpcxpresso55s06/ |
D | Kconfig.defconfig | 5 # SPDX-License-Identifier: Apache-2.0 11 # Board only supports MCUBoot via "upgrade only" method:
|
/Zephyr-latest/boards/nxp/frdm_mcxn947/ |
D | Kconfig.defconfig | 2 # SPDX-License-Identifier: Apache-2.0 19 # Board only supports MCUBoot via "upgrade only" method:
|
/Zephyr-latest/boards/nxp/lpcxpresso55s16/ |
D | Kconfig.defconfig | 4 # SPDX-License-Identifier: Apache-2.0 14 # Board only supports MCUBoot via "upgrade only" method:
|
/Zephyr-latest/subsys/net/lib/http/ |
D | http_server_ws.c | 4 * SPDX-License-Identifier: Apache-2.0 30 #define WS_MAGIC "258EAFA5-E914-47DA-95CA-C5AB0DC85B11" 32 /* Handle upgrade from HTTP/1.1 to Websocket, see RFC 6455 38 "Connection: Upgrade\r\n" in handle_http1_to_websocket_upgrade() 39 "Upgrade: websocket\r\n" in handle_http1_to_websocket_upgrade() 40 "Sec-WebSocket-Accept: "; in handle_http1_to_websocket_upgrade() 48 key_len = MIN(sizeof(key_accept) - 1, sizeof(client->ws_sec_key)); in handle_http1_to_websocket_upgrade() 49 strncpy(key_accept, client->ws_sec_key, key_len); in handle_http1_to_websocket_upgrade() 52 olen = MIN(sizeof(key_accept) - 1 - key_len, sizeof(WS_MAGIC) - 1); in handle_http1_to_websocket_upgrade() 57 ret = base64_encode(tmp, sizeof(tmp) - 1, &olen, accept, sizeof(accept)); in handle_http1_to_websocket_upgrade() [all …]
|
/Zephyr-latest/include/zephyr/net/http/ |
D | parser.h | 1 /* SPDX-License-Identifier: MIT */ 60 * environment (e.g. -DHTTP_MAX_HEADER_SIZE=<value>). To remove 62 * to a very large number (e.g. -DHTTP_MAX_HEADER_SIZE=0x7fffffff) 72 /* Callbacks should return non-zero to indicate an error. The parser will 78 * HEAD request which may contain 'Content-Length' or 'Transfer-Encoding: 84 * `Upgrade` or `Connection: upgrade` headers. 147 #define HTTP_PARSER_ERRNO(p) ((enum http_errno) (p)->http_errno) 159 * semi-public 168 uint64_t content_length; /* # bytes in body (0 if no Content-Length 173 /** READ-ONLY **/ [all …]
|
/Zephyr-latest/subsys/dfu/ |
D | Kconfig | 4 # SPDX-License-Identifier: Apache-2.0 43 upgrade. 51 (https://github.com/JuulLabs-OSS/mcuboot/pull/485) 86 Another use is to ensure that firmware upgrade routines from internet 92 module-str = image manager 102 application is combined with MCUboot multi-image boot.
|
/Zephyr-latest/tests/boot/test_mcuboot/src/ |
D | main.c | 2 * Copyright 2022-2024 NXP 4 * SPDX-License-Identifier: Apache-2.0 20 printk("Failed to request upgrade: %d", err); in main()
|
/Zephyr-latest/boards/bbc/microbit/ |
D | board.cmake | 1 # SPDX-License-Identifier: Apache-2.0 3 board_runner_args(pyocd "--target=nrf51822") 4 board_runner_args(jlink "--device=nRF51822_xxAA" "--speed=4000") 6 # Note: micro:bit DAPLink may be upgraded to J-Link OB by following the instructions at 7 # https://www.segger.com/products/debug-probes/j-link/models/other-j-links/bbc-microbit-j-link-upgr… 9 set(OPENOCD_NRF5_INTERFACE "cmsis-dap") 15 include(${ZEPHYR_BASE}/boards/common/openocd-nrf5.board.cmake)
|
/Zephyr-latest/cmake/modules/ |
D | west.cmake | 1 # SPDX-License-Identifier: Apache-2.0 16 # Cut out any symbolic links, e.g. python3.x -> python 37 -c 54 ${PYTHON_EXECUTABLE} -m pip install west\ 59 set(WEST WEST-NOTFOUND CACHE INTERNAL "West") 65 # Keep this version identical to the one in scripts/requirements-base.txt 70 Please upgrade with:\n\ 71 ${PYTHON_EXECUTABLE} -m pip install --upgrade west\ 77 set(WEST ${PYTHON_EXECUTABLE} -m west CACHE INTERNAL "West") 95 set(WEST WEST-NOTFOUND CACHE INTERNAL "West")
|
/Zephyr-latest/boards/bbc/microbit_v2/ |
D | board.cmake | 1 # SPDX-License-Identifier: Apache-2.0 3 board_runner_args(pyocd "--target=nrf52833") 4 board_runner_args(nrfjprog "--nrf-family=NRF52") 5 board_runner_args(jlink "--device=nRF52833_xxAA" "--speed=4000") 7 # Note: micro:bit v2 DAPLink may be upgraded to J-Link OB by following the instructions at 8 # https://www.segger.com/products/debug-probes/j-link/models/other-j-links/bbc-microbit-j-link-upgr… 10 set(OPENOCD_NRF5_INTERFACE "cmsis-dap") 15 include(${ZEPHYR_BASE}/boards/common/openocd-nrf5.board.cmake)
|
/Zephyr-latest/tests/boot/test_mcuboot/ |
D | testcase.yaml | 8 - "I: Starting bootloader" 9 - "Launching primary slot application on (.*)" 10 - "Secondary application ready for swap, rebooting" 11 - "I: Starting swap using (.*)|I: Image 0 upgrade secondary slot -> primary slot" 12 - "Swapped application booted on (.*)" 16 - frdm_k22f 17 - frdm_k64f 18 - frdm_k82f 19 - frdm_ke17z 20 - frdm_ke17z512 [all …]
|
/Zephyr-latest/boards/nxp/lpcxpresso55s28/ |
D | Kconfig.defconfig | 4 # SPDX-License-Identifier: Apache-2.0 21 # of the flash, or into the code-partition defined in DT if it is intended to 22 # be loaded by MCUboot. If the secure firmware is to be combined with a non- 25 # For the non-secure version of the board, the firmware 26 # must be linked into the code-partition (non-secure) defined in DT, regardless. 31 DT_CHOSEN_Z_CODE_PARTITION := zephyr,code-partition 39 # Board only supports MCUBoot via "upgrade only" method:
|
/Zephyr-latest/subsys/net/lib/lwm2m/ |
D | README_lwm2m | 2 ---------------------- 13 The CDDL description is based on the RFC 8428 - Sensor Measurement Lists (SenML). For further 14 details please see the chapter 11 - CDDL. 19 pip install --upgrade zcbor 24 …you can attempt to use the 3-way merge capabilities by committing the un-patched changes (i.e. up … 27 git am -3 < lwm2m_senml_cbor.patch 33 git format-patch --stdout HEAD~1.. > lwm2m_senml_cbor.patch
|
/Zephyr-latest/tests/boot/with_mcumgr/ |
D | README.rst | 1 Upgrade testing with MCUmgr 16 .. code-block:: console 18 ./zephyr/scripts/twister -vv --west-flash --enable-slow -T zephyr/tests/boot/with_mcumgr \ 19 -p nrf52840dk/nrf52840 --device-testing --device-serial /dev/ttyACM0 22 Twister requires ``--west-flash`` flag enabled (without additional parameters 28 .. code-block:: console 30 pytest zephyr/tests/boot/with_mcumgr/pytest --collect-only -v
|
/Zephyr-latest/include/zephyr/usb/class/ |
D | usb_dfu.h | 1 /* SPDX-License-Identifier: BSD-3-Clause */ 38 * @brief USB Device Firmware Upgrade (DFU) public header 41 * Device Firmware Upgrade Version 1.1 81 /** Run-Time Functional Descriptor */
|
/Zephyr-latest/boards/nxp/lpcxpresso55s69/ |
D | Kconfig.defconfig | 2 # SPDX-License-Identifier: Apache-2.0 19 # of the flash, or into the code-partition defined in DT if it is intended to 20 # be loaded by MCUboot. If the secure firmware is to be combined with a non- 23 # For the non-secure version of the board, the firmware 24 # must be linked into the code-partition (non-secure) defined in DT, regardless. 29 DT_CHOSEN_Z_CODE_PARTITION := zephyr,code-partition 57 # Board only supports MCUBoot via "upgrade only" method:
|
/Zephyr-latest/samples/sysbuild/with_mcuboot/ |
D | README.rst | 1 .. zephyr:code-sample:: with_mcuboot 29 configures MCUboot to prevent downgrades and operate in upgrade-only mode. 33 .. zephyr-app-commands:: 35 :zephyr-app: samples/sysbuild/with_mcuboot 38 :west-args: --sysbuild 43 .. code-block:: console 45 *** Booting Zephyr OS build v3.2.0-rc3-209-gdcf4201d3573 *** 46 *** Booting Zephyr OS build v3.2.0-rc3-209-gdcf4201d3573 ***
|
/Zephyr-latest/boards/st/stm32373c_eval/doc/ |
D | index.rst | 5 …e STM32373C-EVAL evaluation board is designed as a complete demonstration and development platform… 7 …user evaluate all peripherals (USB FS, USART, audio DAC, microphone ADC, dot-matrix LCD, IrDA, LDR… 11 More information about the board can be found at the `STM32373C-EVAL website`_. 16 STM32373C-EVAL provides the following hardware components: 18 - STM32F373VCT6 microcontroller 19 - Four 5 V power supply options: 20 - Power jack 21 - ST-LINK/V2 USB connector 22 - User USB connector 23 - Daughter board [all …]
|
12345