# firmware-update Published articles for firmware-update. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## ESPHome 2025.9.0: MIPI RGB displays and a camera JPEG encoder DevFeed: [ESPHome 2025.9.0: MIPI RGB displays and a camera JPEG encoder]() Original publisher: [Read original article]() Author: Jesse Hills Published: 2025-09-17T00:00:00Z Content type: release Language: en Sources: [ESPHome - Smart Home Made Simple - Blog]() Topics: [esphome](), [Compression](), [dev-tools](), [Streaming]() Tags: [2025](), [camera](), [compatibility](), [compression](), [developer-tools](), [dfu](), [display](), [firmware-update](), [improvements](), [jpeg](), [memory](), [mipi](), [releases](), [rgb]() ### AI overview ESPHome 2025.9.0 adds MIPI RGB display support, a camera JPEG encoder, nRF52 DFU support, ESPHome Builder improvements, memory optimizations, and enhanced sensor and component support. ### Source excerpt ESPHome 2025.9.0 adds MIPI RGB display support, a camera JPEG encoder, DFU support for nRF52, and ESPHome Builder improvements, along with extensive memory optimizations. ## How to migrate from IDF Bootloader to MCUboot using ESP Self-Reflasher DevFeed: [How to migrate from IDF Bootloader to MCUboot using ESP Self-Reflasher]() Original publisher: [Read original article]() Author: John Lee Published: 2025-01-16T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [migration](), [Embedded Software Dev](), [ESP-IDF](), [NuttX](), [Zephyr RTOS](), [Espressif]() Tags: [blog](), [bootloader](), [component](), [embedded-systems](), [esp-idf](), [esp-self-reflasher](), [firmware](), [firmware-update](), [flashing](), [mcuboot](), [migration](), [nuttx]() ### AI overview This tutorial discusses migrating embedded firmware from the ESP-IDF bootloader to MCUboot using ESP Self-Reflasher. It explains why bootloader compatibility matters during RTOS or platform migration and notes that direct serial flashing may be impractical for inaccessible devices. ### Source excerpt Migration is a word that carries a weighty importance in many contexts. It means relocation, resettling or, in case of the tech area, it could mean upgrade or replacement. A variety of reasons may motivate the big decision of migrating an entire piece of hardware or software from a production running system. ## OTA Firmware Updates with ESP Privilege Separation DevFeed: [OTA Firmware Updates with ESP Privilege Separation]() Original publisher: [Read original article]() Author: John Lee Published: 2023-01-29T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [ESP-IDF](), [Embedded Software Dev]() Tags: [blog](), [business-logic](), [esp](), [esp-idf](), [esp-privilege-separation](), [esp32](), [firmware](), [firmware-update](), [iot](), [ota](), [partition](), [security](), [updates]() ### AI overview This article explains independent over-the-air firmware updates for protected_app and user_app in ESP Privilege Separation. It describes the ESP-IDF partition layout, the user-app update workflow, background downloading, reboot handling, and optional signature verification. ### Source excerpt Over-The-Air (OTA) firmware update is one of the most important feature of any connected device. It enables the developers to ship out new features and bug fixes by remotely updating the application. In ESP Privilege Separation, there are two applications -- protected_app and user_app for which the framework provides the ability to independently update both the application binaries. In this post we will describe the independent OTA update feature under ESP Privilege Separation. ## December Update: Thank You For 2019! DevFeed: [December Update: Thank You For 2019!]() Original publisher: [Read original article]() Published: 2019-12-05T00:00:00Z Content type: news Language: en Sources: [Community blog on PINE64]() Topics: [foss](), [Hardware](), [Pinephone](), [.NET Conf]() Tags: [communities](), [community](), [community-update](), [contributors](), [developers](), [firmware-update](), [fosdem](), [foss](), [hardware](), [pine64](), [pinebook-pro](), [pinephone](), [pinephone-keyboard](), [pinetab](), [pinetime](), [users]() ### AI overview PINE64's December 2019 community update thanks contributors and users, reviews progress across PineTime, PineTab, PinePhone, keyboards, firmware, and other hardware, and previews January updates and FOSDEM 2020 announcements. ### Source excerpt Welcome to the last community update of the year. I think that 2019 will be remembered as the year PINE64 transitioned from being a relatively niche FOSS hardware project to a mainstream one. This transition is an exciting prospect for all of us involved with PINE64, and we cannot wait to see how the project develops over the next 12 months. Let me take this opportunity to thank those of you whom have been with us thus far: the partner-project developers, community contributors, mods and admins, shipping and assembly teams, and - above all else - the end-users who make this project possible. Thank you for actively shaping PINE64 and making it one of the most vibrant and welcoming communities in the FOSS space. The amount of progress we've made in just one year is incredible and the success is truly collectively ours. Thank you! Here's the TL;DR: Next Community Update January 12th ; Give us some feedback The PineTime is now in the PINE Store ; Great development PineTab early adopter pre-orders likely in January ; New keyboard ; LTE/ SSD adapter Brave Heart PinePhones worked on ; shipping early January ; PinePhone cases ; First phone call ; PinePhone keyboard Continual good reception ; Keyboard / TP firmware update available ; A lot of OSs coming ; regional keyboards ; OG Pinebook upgrade kit likely in January 2020. New announcements at FOSDEM 2020 ; teaser of what's to come next year Happy New Year! Housekeeping I'll try to keep this section short. It's unlikely that I'll be able to publish the next Community Update on 05/01/2020 seeing as I'll be traveling during the Holiday and New Year's period. In other words, I won't have an opportunity to sit down and write the blog until I am back home on January 7th. I feel like the earliest date I can commit to for an update blog entry is 12/01/2020. In the meantime, if some noteworthy or urgent information surface then I'll post ad-hoc updates in the forum news section. Make sure to check it once in a while during the holid ## ESP32 OTA Updates -- Amazon FreeRTOS DevFeed: [ESP32 OTA Updates -- Amazon FreeRTOS]() Original publisher: [Read original article]() Author: John Lee Published: 2018-09-30T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [ESP32](), [Embedded Software Dev](), [Security](), [Amazon S3](), [Amazon Web Services](), [Internet of things]() Tags: [amazon](), [aws](), [blog](), [certificates](), [ecdsa](), [esp32](), [firmware-update](), [framework](), [freertos](), [iot](), [public-key](), [s3](), [secure-boot](), [security](), [sha256](), [signing]() ### AI overview This tutorial explains how to perform secure Over-the-Air firmware updates on ESP32 using Amazon FreeRTOS and AWS services. It covers storing firmware in Amazon S3, signing and transmitting updates through an AWS OTA Job, verifying firmware on the device, and using ESP32 hardware security features such as secure boot. ### Source excerpt ESP32 now supports secure Over-the-Air firmware updates with Amazon FreeRTOS. This enables users of ESP32 with Amazon FreeRTOS to: - Deploy new firmware on ESP32 in secure manner (single or group of devices, along with dynamic addition of new/re-provisioned device) - Verify authenticity and integrity of new firmware after its deployed - Extend OTA update security scheme to take leverage of hardware security features in ESP32 Working# At a high level, - The firmware image (or any other... ## Flash your Lenovo Ideapad laptop BIOS from Linux using UEFI capsule updates DevFeed: [Flash your Lenovo Ideapad laptop BIOS from Linux using UEFI capsule updates]() Original publisher: [Read original article]() Author: Christophe Beyls Published: 2018-07-14T23:20:42Z Content type: tutorial Language: en Sources: [Stories by Christophe Beyls on Medium]() Topics: [UEFI](), [Linux](), [Embedded Software Dev](), [Vulnerabilities]() Tags: [bootloader](), [firmware](), [firmware-update](), [laptop](), [lenovo](), [linux](), [uefi](), [vulnerabilities]() ### AI overview This tutorial explains how to update the BIOS of a Lenovo Ideapad laptop from an existing Linux installation using UEFI Capsule Updates. It describes how some Lenovo Windows executables may contain a capsule update and outlines the requirements for the standard UEFI update mechanism, including booting Linux in UEFI mode with an EFI system partition. ### Source excerpt I'm the happy owner of a Lenovo Ideapad laptop (model 710S-13IKB). It's comparable to the Dell XPS 13 and runs beautifully under Linux, but one detail has always been bugging me: Lenovo only provides BIOS updates for its Ideapad laptops in the form of Windows 10 executable files. System firmware updates are important, especially to mitigate newly found vulnerabilities like Meltdown and Spectre. Since I wiped Windows off my machine a long time ago, I was wondering if there was an alternative (and secure) way to flash firmware updates on it. And it turns out there is! After months of investigation, I found an elegant and stable update procedure which doesn't require Windows at all. It doesn't even need the creation of a bootable USB key: everything is done from the existing Linux installation. How is that possible? Let me introduce you to an interesting new feature of the UEFI specification. Different machines, different firmware updates Many latop brands like Dell or Asus provide firmware files that you can put on a USB key and flash from an update application located in the BIOS menu itself. Lenovo does not. Instead, they give you two options: For the higher-end ThinkPad series inherited from IBM, they provide bootable CD images that can be turned into bootable USB keys. That's another good OS-agnostic solution. For the Ideapad and Yoga series, you're stuck with a Windows executable file. The contents of this file and the actual flashing procedure varies depending on the BIOS/Firmware brand. If you have a modern machine with a Phoenix firmware, chances are that the Windows executable contains the update in the form of an UEFI Capsule Update. Capsule what? When a firmware is distributed in that form, the update program won't flash it directly under Windows. Instead, it will delegate the task to the standard UEFI update mechanism called Capsule Update. In practice, it will ask the operating system to copy an update file to the system partition then program the UEFI to