Dear All, I'm using the nRF Connect SDK and try to do a FOTA upgrade to my nRF52832, with MCUboot installed. After I downloaded the binary via nRF Connect Android App to the device, i get "<wrn> mcubo

#nrf52832 #mcuboot #fota

Hi there I am having issues getting started with MCUboot. I flashed MCUboot version 1.8-dev onto my "nrf52840dk_nrf52840" and "nrf5340dk_nrf5340_cpuapp". I then flashed the hello_world sample to my bo

#mcuboot

Hi Brenton, The only images you should flash are MCUboot and an image that goes to Slot#0. Any further operations should be conducted with the mcumgr tool. At least I used to do that. This tool gives

#mcuboot

Hi, may be you forgot to sign the image? west sign -t imgtool -- --key path_to_mcuboot\root-rsa-2048.pem (or other key that mcuboot is using) west flash --skip-rebuild -- --hex-file build/zephyr/zephy

#mcuboot

Hi Adam Thank you for your reply. Sorry for the late response, as I have been getting sporadic results, i.e. sometimes the image upgrade works and most of the time it doesn't. I have been using the fo

#mcuboot

Hi, why do you want to compile it with offset of slot1? Normaly you compile image for slot0, upload it to slot1 and MCUboot will swap them after reboot. Martin Dne 25.10.2021 v 13:40 Brenton Chetty na

#mcuboot

1. Hi, how do I go about signing an image for slot1 usage. I used the following command for flashing into slot0 successfully: west sign -t imgtool -- --key ~/zephyrproject/bootloader/mcuboot/root-rsa-

#mcuboot

Hi Brenton, please try similar command: imgtool.py sign --key root-rsa-2048.pem --header-size 0x200 --align 8 --version <YOUR_VERSION> --slot-size <YOUR_SLOT_SIZE_IN_HEX> ZEPHYR_BIN_FILE NAME_OF_THE_S

#mcuboot

Hi, I am trying to learn how to perform an OTA update for my nrf5340dk. I was initially planning to use the "big_http_download" sample to download the update file, and then flash that image into slot1

#networking #mcuboot #mcumgr

I believe I have found a bug in the current HCI-USB code for the nRF52 series when it is started from the MCUboot bootloader. This is on the current Zephyr 2.6 branch. In usb_dc_nrfx.c, usb_dc_attach(

#hci #mcuboot #nrf52

Hi, For DFU using mcumgr over UDP we have a working configuration based on a version of the manifest-rev branch of mcuboot modified to support 32 byte alignment. Environment is Zephyr 3.0.0 running on

#mcuboot #stm32

Hi again, I am still struggling with DFU/MCUboot... Is there anyone out there that has successfully used MCUboot together with the STM32H7 line of MCU's? I have updated my build environment to Zephyr

#mcuboot #stm32

Hi Mate, I have very small issue that is when i am trying to link config_bootloader_mcuboot=y in zephyr application the program is not flashed. I need to run zephyr application in mcuboot for the reas

#zephyr #mcuboot

Hi Zephyr developers/users I'm working on an OTA firmware upgrade application. I just wanted to find out, if there is any way to change slots during the zephyr application's runtime? An example would

#mcumgr #mcuboot #fota

Hi, so you have FW update solved, using boot_request_upgrade(BOOT_UPGRADE_TEST), mcuboot swaps the data between slots and starts your new FW? And then you want to rollback? Then I think you should che

#mcumgr #mcuboot #fota