# Bootloader Published articles for Bootloader. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Libreboot 20231101 released! DevFeed: [Libreboot 20231101 released!]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T04:32:50.666044Z Content type: release Language: en Sources: [News about Libreboot releases and development]() Topics: [libreboot](), [boot](), [coreboot](), [x86](), [Arm](), [UEFI](), [Linux]() Tags: [bios](), [boot](), [bootloader](), [canoeboot](), [coreboot](), [firmware](), [free-software](), [hardware](), [libre](), [libreboot](), [linux](), [opensource](), [release](), [security](), [uefi]() ### AI overview Libreboot 20231101 is a new testing release published on 1 November 2023. The article describes its boot firmware support, added ThinkPad X201 support, the re-added Intel D945GCLF, and updated Coreboot, GRUB, U-Boot, and SeaBIOS revisions with additional patches. ### Source excerpt Article: Libreboot 20231101 released! Web link: https://libreboot.org/news/libreboot20231101.html ## Run Zephyr on ESP32 with QEMU: no board required DevFeed: [Run Zephyr on ESP32 with QEMU: no board required]() Original publisher: [Read original article]() Author: John Lee Published: 2026-09-15T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [Zephyr RTOS](), [ESP32](), [qemu](), [Espressif](), [Emulator](), [Embedded Software Dev](), [SDK]() Tags: [blog](), [boot](), [bootloader](), [build](), [debugger](), [emulator](), [esp32](), [esp32-c3](), [esp32-c6](), [esp32-s3](), [espressif](), [firmware](), [flash](), [gdb](), [install](), [qemu](), [sdk](), [toolchain](), [tutorial](), [zephyr]() ### AI overview This tutorial explains how to install and use the Espressif QEMU fork to build and run Zephyr firmware for emulated ESP32, ESP32-S3, ESP32-C3, and ESP32-C6 targets without physical boards. It covers Simple Boot and MCUboot/sysbuild workflows, debugger attachment through GDB, and the relevant Zephyr SDK toolchain setup. ### Source excerpt Install the Espressif QEMU fork and run Zephyr on emulated ESP32, ESP32-S3, ESP32-C3, and ESP32-C6 targets without a physical board. ## BFS File-System Being Removed For Linux 7.4 DevFeed: [BFS File-System Being Removed For Linux 7.4]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-13T11:03:26Z Content type: news Language: en Sources: [Phoronix]() Topics: [Filesystems](), [Linux](), [kernels](), [Unix](), [boot]() Tags: [boot](), [bootloader](), [desktop-linux](), [filesystem](), [filesystems](), [kernels](), [linux](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [open-source-graphics](), [os](), [phoronix](), [phoronix-test-suite](), [systems](), [technical](), [ubuntu-benchmarks](), [ubuntu-hardware]() ### AI overview BFS, the obsolete UnixWare boot-partition filesystem, is slated for removal from the Linux kernel in version 7.4. The article cites its extremely limited functionality, lack of likely users, and broader efforts to reduce maintenance burdens from rarely used filesystems. ### Source excerpt The latest upstream file-system to be removed from the mainline Linux kernel is... BFS... ## I moved my laptop to a rolling-release distro and the snapshots did the heavy lifting DevFeed: [I moved my laptop to a rolling-release distro and the snapshots did the heavy lifting]() Original publisher: [Read original article]() Author: Shed Stack Published: 2026-09-06T18:00:00Z Content type: opinion Language: en Sources: [Shed Stack]() Topics: [btrfs](), [Kernel](), [Hardware]() Tags: [boot](), [bootloader](), [btrfs](), [driver](), [laptop](), [packages](), [rollback](), [snapshots](), [update]() ### AI overview The author describes moving a laptop to CachyOS, a rolling-release distribution, to obtain newer kernels and packages. Automatic Btrfs snapshots managed with snapper provide rollback protection when updates affect boot components, drivers, or the desktop. ### Source excerpt CachyOS, snapper, and the DPTF fix. What a rolling release is actually like when you keep a parachute. ## Artery AT32F406 and AT32F408 Cortex-M4F MCUs feature optional high-speed USB OTG PHY DevFeed: [Artery AT32F406 and AT32F408 Cortex-M4F MCUs feature optional high-speed USB OTG PHY]() Original publisher: [Read original article]() Author: Debashis Das Published: 2026-09-03T09:40:39Z Content type: news Language: en Sources: [CNX Software - Embedded Systems News]() Topics: [Microcontroller](), [Embedded Systems](), [Arm](), [USB](), [Internet of things](), [cpu](), [Hardware]() Tags: [arm](), [boot](), [bootloader](), [c-c-plus-plus](), [cortex-m4](), [cpu](), [development-board](), [embedded](), [embedded-systems](), [hardware](), [industrial](), [iot](), [mcu](), [microcontrollers](), [processors](), [specifications](), [usb]() ### AI overview The article describes Artery Technology's AT32F406 and AT32F408 Arm Cortex-M4F microcontrollers, which run at up to 216 MHz. The AT32F408 adds USB 2.0 OTG High-Speed support with an integrated PHY, while both devices provide DSP and floating-point capabilities, configurable memory options, QSPI, and a range of digital and analog peripherals. ### Source excerpt Artery Technology AT32F406 and AT32F408 are two new Arm Cortex-M4F MCUs running at up to 216 MHz, with the F408 adding USB OTG High-Speed and an integrated PHY for industrial automation, IoT, USB accessories, and gaming peripherals. The AT32F406/F408 series both offer DSP instructions and a floating-point unit (FPU), integrate up to 512 KB Flash and 192 KB SRAM, and a 4 KB OTP memory for critical data and parameters. The microcontrollers also offer a QSPI interface for external Flash or RAM expansion, and a range of digital and analog peripheral interfaces. Artery AT32F406/AT32F408 specifications: MCU - 32-bit Arm Cortex-M4F CPU up to 216 MHz; also features Memory Protection Unit (MPU) and DSP instructions Memory/Storage 128 KB to 192 KB SRAM 256 KB to 512 KB Flash memory 26 KB boot memory (configurable as a bootloader or general instruction/data memory) 4 KB OTP (one-time programmable) memory QSPI interface for external SPI [...] The post Artery AT32F406 and AT32F408 Cortex-M4F MCUs feature optional high-speed USB OTG PHY appeared first on CNX Software - Embedded Systems News. ## Recovery Bootloader DevFeed: [Recovery Bootloader]() Original publisher: [Read original article]() Author: John Lee Published: 2026-07-27T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [ESP-IDF](), [ESP32-C5](), [Boot Process](), [Security]() Tags: [blog](), [bootloader](), [embedded-systems](), [esp-idf](), [esp32-c5](), [flash](), [ota](), [updates](), [vulnerability]() ### AI overview This article explains how to safely perform bootloader OTA updates with the recovery bootloader feature. It describes keeping a known-good bootloader image in a separate flash location so the device can recover if the primary bootloader becomes invalid. Examples use ESP-IDF v6.1 and ESP32-C5. ### Source excerpt In this article, we will explore how to safely perform OTA updates for the bootloader using the recovery bootloader feature. ## postmarketOS in 2026-01: monthly blog post reboot DevFeed: [postmarketOS in 2026-01: monthly blog post reboot]() Original publisher: [Read original article]() Published: 2026-01-25T00:00:00Z Content type: article Language: en Sources: [postmarketOS Blog]() Topics: [foss](), [Linux](), [Mobile](), [Kernel](), [e-ink](), [Testing]() Tags: [2026](), [blog-post](), [bootloader](), [e-ink](), [fosdem](), [foss](), [kernel](), [linux](), [mobile](), [pinenote](), [postmarketos](), [team](), [update]() ### AI overview A postmarketOS update explains the project's new blog format, highlights organizational changes and contributor work, and previews FOSDEM 2026 talks about Linux Mobile, Fairphone kernel support, and reliability. It also covers PineNote and other device, package, kernel, and bootloader contributions. ### Source excerpt A new year is a good opportunity to reflect on what has worked and what did not, and improve the things that didn't. We did that with the "monthly" blog posts, of which we had published the last one for October 2025. The reason that it took us so long to write these is, that we were trying to link every merge request that got merged since the previous post and write short summaries for most of them. While this results in a very detailed account of what has happened, it became less feasible over time as we had more contributions in postmarketOS. After a good conversation we decided to change the format to talk about the highlights and going into detail sometimes, instead of achieving a complete report of everything that has happened. One major goal of the previous approach was thanking all the amazing people who contributed to the project, but we solved that by just adding the contributor names in the blog post in a separate section. The title image of this blog post was taken at the very inspiring 39C3. If you would like to have some postmarketOS stickers as well, the next chance to get them is FOSDEM 2026 where we will have our own stand again where you can stop by and talk to us about all things postmarketOS! We are also excited to have two talks from postmarketOS team members: Mainline kernel for Fairphones - 2026 update postmarketOS: Reliability in 2026 ...as well as many more postmarketOS and Linux Mobile related talks in the FOSS on Mobile devroom! Organizational Alexey M. stepped down as Trusted Contributor. He has been improving postmarketOS across the whole stack since 2019. Among lots of other things he created libapk-qt and used it to add an apk backend to KDE's Plasma Discover, which eventually found its way upstream. He also improved pmbootstrap, maintained multiple devices and kernels and did a lot of kernel and bootloader work. Thank you very much and all the best for your new endeavours! The PineNote using Sway with hrdl's opinionated configuration. No ## MCUboot - Getting Started Guide for ESP32 DevFeed: [MCUboot - Getting Started Guide for ESP32]() Original publisher: [Read original article]() Author: John Lee Published: 2026-01-09T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [ESP32](), [Embedded Software Dev](), [Espressif](), [NuttX](), [Zephyr RTOS](), [configuration]() Tags: [blog](), [bootloader](), [building](), [configuration](), [ecdsa](), [ed25519](), [embedded](), [esp32](), [espressif](), [firmware](), [flashing](), [getting-started](), [mcuboot](), [nuttx](), [rsa](), [secure-boot](), [security](), [zephyr]() ### AI overview A practical guide to using MCUboot on ESP32-based projects. It explains MCUboot's secure bootloader role, environment and application configuration, bootloader building, and flashing, with examples for NuttX and Zephyr RTOS applications. ### Source excerpt This guide provides a practical getting-started walkthrough for using MCUboot on ESP32. It covers step-by-step environment setup, bootloader building, application configuration, and flashing. It also gives an overview of MCUboot's execution flow. ## A Simplified ESP32 Boot Process Using Single-Image Binaries DevFeed: [A Simplified ESP32 Boot Process Using Single-Image Binaries]() Original publisher: [Read original article]() Author: John Lee Published: 2025-06-30T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [Boot Process](), [ESP32](), [Embedded Systems](), [Development](), [Code]() Tags: [article](), [blog](), [boot-process](), [bootloader](), [development](), [embedded-systems](), [esp-idf](), [esp32](), [flash](), [nuttx](), [simpleboot](), [speed](), [zephyr]() ### AI overview This article explains how to create a simplified ESP32 bootable image by integrating essential bootloader functionality into the application image. The single-image approach can reduce build and flashing time for development workflows, but it sacrifices features such as OTA updates. ### Source excerpt In this article, we explore a simplified ESP32 boot process using single-image binaries to speed up build and flash times -- ideal for development workflows. This approach sacrifices features like OTA updates but enables faster iteration. ## 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. ## Please refrain from installing WASP-OS on new PineTimes for the moment DevFeed: [Please refrain from installing WASP-OS on new PineTimes for the moment]() Original publisher: [Read original article]() Published: 2024-12-29T00:00:00Z Content type: article Language: en Sources: [Community blog on PINE64]() Topics: [Software](), [Hardware](), [GitHub](), [Documentation]() Tags: [bootloader](), [documentation](), [end-of-life](), [eol](), [github](), [hardware](), [infinitime](), [pinetime](), [version]() ### AI overview The article warns users not to install WASP-OS on PineTime devices with factory bootloader v1.0.1 because the reloader tool does not yet support a replacement flash chip, which can soft-brick the device when reverting to InfiniTime. ### Source excerpt In July 2024, PineStore notified the community that a small hardware change was needed on the PineTime: the current flash chip was end of life (EoL) and needed to be replaced by a new one. From the software point of view, the new chip behaves exactly like the old on so very few code changes were required to support it. The new chip exposes different identifiers (manufacturer ID, for example) than the previous one. Which means that if the software checks those IDs, it would need to be updated to take the new ones into account. No change was needed in InfiniTime, but we however added a new field in the SystemInfo app to display the IDs of the chip. We figure this could be useful in the future. The bootloader does check against those IDs so we released a new version of the bootloader (v1.0.1) as well. We provided the new software to PineStore so they could test them and use them to flash the new batch of PineTimes at the factory. Everything went well and PineTimes equipped with the new memory chip and software are being delivered to happy users. Everything? Well, not really: a few users reported soft-bricked PineTimes after switching to WASP-OS and then reverting to InfiniTime again. This is a bummer: the "reloader" tool that reinstalls the InfiniTime bootloader also needed to be upgraded to support the new memory chip! An issue has already been opened on the WASP-OS GitHub repo and a new reloader tool will hopefully be released soon to tackle this issue. We also added a big red warning on the documentation page that explains how to switch to and from InfiniTime and WASP-OS to ensure that users won't try to switch OS until the issue is fixed and the documentation updated. Warning In the meantime, do not try to install WASP-OS on your PineTime if it's running bootloader v1.0.1 from the factory (unless you know exactly what you are doing), this WILL brick your PineTime! Be sure that the community will try to fix this as soon as possible, but please remember that develope ## ESP32 bootstrapping in Zephyr DevFeed: [ESP32 bootstrapping in Zephyr]() Original publisher: [Read original article]() Author: John Lee Published: 2024-10-30T00:00:00Z Content type: article Language: en Sources: [Blog on Developer Portal]() Topics: [ESP32](), [Espressif](), [boot](), [Zephyr RTOS](), [SOC](), [Hardware](), [Tooling]() Tags: [blog](), [boot](), [bootloader](), [debugging](), [embedded](), [esp-idf](), [esp32](), [esp32-c3](), [esp32-c6](), [esp32-s2](), [esp32-s3](), [espressif](), [esptool](), [format](), [zephyr]() ### AI overview This article explains how Espressif SoCs, including ESP32 devices up to ESP32-C6, boot in Zephyr RTOS. It covers the ROM loader, second-stage loader, image formats, build and memory considerations, and related tooling. ### Source excerpt This article explains the booting process of Espressif devices up to ESP32-C6 (and probably newer devices). ## How to switch between multiple ESP32 firmware binaries stored in the flash memory DevFeed: [How to switch between multiple ESP32 firmware binaries stored in the flash memory]() Original publisher: [Read original article]() Author: John Lee Published: 2024-07-24T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [ESP32](), [Microcontroller](), [Embedded Software Dev](), [Internet of things](), [ESP32-S3](), [m5stack](), [Wokwi]() Tags: [binaries](), [blog](), [boot](), [bootloader](), [bsp](), [build](), [code](), [embedded](), [embedded-systems](), [esp32](), [esp32-p4](), [esp32-s3](), [espressif](), [firmware](), [flash](), [gui](), [how-to](), [iot](), [m5stack](), [memory](), [ota](), [partition](), [quick-start](), [releases](), [simulation](), [wokwi]() ### AI overview A tutorial on using the ESP32 Graphical Bootloader to store multiple firmware images in flash memory and switch between them. It explains the bootloader flow, partition-table configuration, and steps for building, merging, flashing, and simulating the application. ### Source excerpt Introduction# The ESP32 microcontroller is a versatile and powerful device, widely used in IoT and embedded applications. One of its advanced features is the ability to store multiple firmware images in its flash memory and switch between them. This capability can be leveraged for various purposes, such as testing different firmware versions, running multiple applications, or maintaining a backup firmware. ## 1st-stage GUI setup, Part 3 - December 2023: First tests DevFeed: [1st-stage GUI setup, Part 3 - December 2023: First tests]() Original publisher: [Read original article]() Published: 2024-02-01T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [GUI](), [Testing](), [Code]() Tags: [bootloader](), [code](), [free](), [gui](), [iso](), [open-source](), [os](), [partition](), [react](), [reactos](), [tests](), [win32](), [winapi]() ### AI overview This third post in the ReactOS "1st-stage GUI setup" series describes December 2023 work testing the complete graphical installer with a partially Wine-synced setupapi DLL. It covers partition-management UI behavior, the all-in-one CD ISO test scenario, installation dialogs, hardware presets, and current limitations to initialized MBR disks, with GPT and uninitialized-disk support planned. ### Source excerpt Greetings! Welcome to the third blog of the series "1st-stage GUI setup": September 2023: Partly Wine-syncing setupapi October-November 2023: Making partitioning UI work December 2023: First tests In this third blog post, I will cover my work done during the month of December 2023: testing the whole 1st-stage GUI setup, together with the partially wine-synced setupapi dll. Finishing and testing the partitioning page UI The first week was devoted to finally putting together the code for manipulating partitions from the user interface, using the new workflow, and testing it. ## 1st-stage GUI setup, Part 2 - October-November 2023: Making partitioning UI work DevFeed: [1st-stage GUI setup, Part 2 - October-November 2023: Making partitioning UI work]() Original publisher: [Read original article]() Published: 2024-01-31T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [GUI](), [ui](), [Code]() Tags: [bootloader](), [free](), [gui](), [open-source](), [os](), [partitioning](), [react](), [reactos](), [ui](), [win32](), [winapi]() ### AI overview This second ReactOS development blog post describes work from October and November 2023 on the new first-stage GUI setup, focusing on disk partitioning and its workflow compared with the existing text-mode installer. It also notes related setupapi synchronization work and identifies file copying and registry settings as features discussed in future posts. ### Source excerpt Greetings! Welcome to the second blog of the series "1st-stage GUI setup": September 2023: Partly Wine-syncing setupapi October-November 2023: Making partitioning UI work December 2023: First tests As you may have noticed, I have been quite silent about my work and not regularly writing blog posts about what I have done so far. Well, I am more concerned about getting actual code written and working before discussing about it, instead of doing that about half-done not-yet-tested code; much like what the GUI setup was during these previous months. ## Call For Tegra U-Boot Testers DevFeed: [Call For Tegra U-Boot Testers]() Original publisher: [Read original article]() Published: 2024-01-13T00:00:00Z Content type: article Language: en Sources: [postmarketOS Blog]() Topics: [tegra](), [Nvidia](), [boot]() Tags: [bootloader](), [devices](), [nvidia](), [postmarketos](), [tegra](), [testing]() ### AI overview postmarketOS is seeking testers for its generic U-Boot port on Nvidia Tegra 2, 3, and 4 devices. The port supports nine devices, and user testing can help replace proprietary vendor bootloaders with U-Boot. ### Source excerpt We currently have a generic port for Nvidia Tegra 2/3/4 devices using U-Boot as bootloader, supporting 9 different devices at the time of writing. This wouldn't have been possible without the work of Svyatoslav Ryhel (also known as Clamor), who has been working on Tegra devices for the last few years and is also a maintainer of Nvidia Tegra SoCs in U-Boot. The wiki page has a list of supported devices. Svyatoslav ported most of these devices without owning one, just relying on testing from people. This means anyone having such a device can reach him and eventually will be able to replace the old proprietary vendor bootloader with U-Boot. If you're interested, you can reach out Svyatoslav in #postmarketOS-on-tegra:matrix.org matrix room or e-mail him to get personal contacts at clamor95@gmail.com. ## Running the operating system that you're currently using in a virtual machine (with Secure Boot and TPM emulation) DevFeed: [Running the operating system that you're currently using in a virtual machine (with Secure Boot and TPM emulation)]() Original publisher: [Read original article]() Author: andreacorbellini Published: 2023-11-19T16:33:00Z Content type: tutorial Language: en Sources: [Andrea Corbellini]() Topics: [Ubuntu](), [Secure Boot](), [qemu](), [Operating system](), [boot](), [Kernel]() Tags: [bootloader](), [information-technology](), [operating-systems](), [qemu](), [secure-boot](), [systems](), [ubuntu](), [virtual]() ### AI overview A tutorial explains how to run the operating system currently in use inside a virtual machine, preserving its settings and files. The procedure targets Ubuntu and uses a copy of the drive, TPM emulation with swtpm, and QEMU; it is intended for testing Secure Boot and predicting TPM state without rebooting. ### Source excerpt In this article I will show you how to start your current operating system inside a virtual machine. That is: launching the operating system (with all your settings, files, and everything), inside a virtual machine, while you're using it. This article was written for Ubuntu, but it can be easily adapted to other distributions, and with appropriate care it can be adapted to ... ## Hermès Bélusca-Maïto hired full-time to work on the ReactOS GUI Setup DevFeed: [Hermès Bélusca-Maïto hired full-time to work on the ReactOS GUI Setup]() Original publisher: [Read original article]() Published: 2023-10-01T00:00:00Z Content type: news Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [GUI]() Tags: [bare-metal](), [bootloader](), [community](), [free](), [gui](), [open-source](), [os](), [partition](), [react](), [reactos](), [registry](), [team](), [virtual-machines](), [win32](), [winapi]() ### AI overview ReactOS Deutschland e.V. hired Hermès Bélusca-Maïto to work full-time for five months on the ReactOS GUI Setup. The planned work includes completing setup functionality, adding GPT support, integrating registry callbacks, and making other refinements. ### Source excerpt Our team proudly announces that ReactOS Deutschland e.V. has hired Hermès Bélusca-Maïto to work full-time on the ReactOS GUI Setup for the next 5 months, starting September 2, 2023. Hermès is a long-time contributor and developer who worked on the project since 2012. He has several skills and expertise into various components of ReactOS, notably being the Client/Server Runtime Subsystem (CSRSS), Console Server Subsystem (CONSRV), NTVDM, and others. His upcoming goal is to finish the first-stage ReactOS GUI setup, which offers an alternative to the classic first-stage text-mode setup (also called USETUP). ## Moving to Tow-Boot: Towards Device-Independant Images DevFeed: [Moving to Tow-Boot: Towards Device-Independant Images]() Original publisher: [Read original article]() Author: Mobian team Published: 2022-03-30T00:00:00Z Content type: release Language: en Sources: [Mobian's Blog]() Topics: [Mobile](), [Linux](), [Arm](), [boot]() Tags: [arm](), [boot](), [bootloader](), [deprecated](), [devices](), [firmware](), [install](), [linux](), [mobile](), [partitions](), [storage](), [update]() ### AI overview Mobian explains its move toward device-independent images by requiring PinePhone and PinePhone Pro users to install Tow-Boot before flashing Mobian images. The change stops Mobian from embedding device-specific bootloader copies; existing installations should continue booting, while distribution-installed u-boot is deprecated. ### Source excerpt Mobian (and most of the Arm Linux ecosystem) have been dealing with device-specific boot sequences since our inception. However, recent changes have made it possible to standardise these. This blog post will discuss how these changes affect Mobian and the long term goal of creating a universal image for Mobian devices. Every problem has a solution Each ARM-based SoC implements its own boot sequence, looking for a bootloader at different locations on different storage devices. For example, the OG PinePhone's Allwinner A64 looks for it at an 8KiB offset, first on the SD card, then on the eMMC. The PinePhone Pro's RK3399 expects it to be either on a SPI flash device, or at offset 32KiB on the eMMC or the SD card. Until now, we dealt with those differences by generating per-device images, each one embedding a copy of the bootloader (u-boot in our case) at the exact offset expected by the SoC. However, this isn't very practical, as it prevents us from generating device-independent images, and it can have annoying side effects: in some cases, the bootloader can remain untouched on an SD card even after reformatting. Fortunately, there is way to work around this problem: by letting users install the bootloader themselves, either on the SPI flash (for devices including one) or the eMMC's boot partitions (which are left untouched when flashing new images to the device), we can stop embedding our own copy of the bootloader. Following the trend across the Mobile Linux community, we therefore settled for Tow-Boot as the recommended bootloader and will now require PinePhone (OG and Pro versions) users to install it before flashing a Mobian image to their devices. Existing Installs The most important part of this change is that it will not break existing installs. Distribution-installed u-boot is however deprecated and will not receive updates. If you do nothing but update, you will see the u-boot-sunxi (PinePhone) or u-boot-rockchip (PinePhone Pro) package removed. Removing it w ## How to use custom partition tables on ESP32 DevFeed: [How to use custom partition tables on ESP32]() Original publisher: [Read original article]() Author: John Lee Published: 2021-02-12T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [ESP32](), [Embedded Software Dev](), [configuration]() Tags: [blog](), [bluetooth](), [bootloader](), [esp-idf](), [esp32](), [espressif](), [firmware](), [flash](), [how-to](), [iot](), [ota](), [partition](), [storage](), [wifi]() ### AI overview This tutorial explains how ESP32 flash memory is organized and how custom partition tables can separate application firmware from persistent data. It references ESP-IDF v4.2 and discusses partitions used for configuration, calibration, WiFi and Bluetooth data, and OTA updates. ### Source excerpt Introduction# When we create a new project using ESP32 , sometimes we need to store data in the flash to persist even after a restart or power down. In the past, the most common way to do that was by using EEPROM, with just a few bytes of storage ability which limited it for larger amount of data. On the other hand, the ESP32 uses a flash memory to store the firmware, including the bootloader and other relevant data. ## Newsletter 100 - January 2021 news DevFeed: [Newsletter 100 - January 2021 news]() Original publisher: [Read original article]() Published: 2021-02-06T00:00:00Z Content type: news Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Kernel](), [pull-requests](), [Cache](), [Windows](), [gcc](), [MSVC](), [USB]() Tags: [boot](), [bootloader](), [cache](), [filesystem](), [free](), [gcc](), [kernel](), [msvc](), [news](), [open-source](), [os](), [pull-requests](), [react](), [reactos](), [win32](), [winapi](), [windows]() ### AI overview ReactOS's January 2021 newsletter reports kernel development, including memory-manager and cache changes, improved Windows driver compatibility, GCC build progress, NTFS boot work, and USB boot improvements. ### Source excerpt Hello ReactOS followers! This is an attempt to re-instate the Newsletter, which informed you about recent developments. The previous Newsletter 99 was in 2013! This month we were mostly focused on the kernel work, merging pull requests and fixing regressions. Memory manager and Common cache work Being in development for almost six month, this work by Jérôme Gardou finally landed in the master branch. This change refactors many aspects of the Section Objects feature in NT-compatible kernel, making it more compatible with Windows. ## OTA Updates Framework DevFeed: [OTA Updates Framework]() Original publisher: [Read original article]() Author: John Lee Published: 2020-12-22T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [ESP-IDF](), [ESP32](), [Internet of things](), [Security]() Tags: [blog](), [bootloader](), [configuration](), [embedded-systems](), [esp-idf](), [esp32](), [firmware](), [git](), [iot](), [ota](), [partition](), [rollback](), [security](), [updates](), [vulnerabilities]() ### AI overview This tutorial explains the design and internal workings of the Over-The-Air Updates framework in ESP-IDF. It covers ESP32 partition tables and flash layout, application image descriptors, firmware and security versions, reliability, security, and anti-rollback considerations. ### Source excerpt In this post we will discuss the design and internal workings of Over-The-Air (OTA) Updates framework in ESP-IDF. We shall also cover some of the features from OTA updates, focused around reliability and security that can help to build better IoT products with ESP32. Background Information# Lets cover some basic information essential for understanding the overall OTA update procedure. Partition Table & Flash Layout# The Partition table defines the flash layout on ESP32. ## Blink LED on ESP32 with RTOS NuttX DevFeed: [Blink LED on ESP32 with RTOS NuttX]() Original publisher: [Read original article]() Author: John Lee Published: 2020-12-01T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [ESP32](), [Tutorial](), [Embedded Software Dev](), [Operating system](), [configuration]() Tags: [blog](), [bootloader](), [devkit](), [esp32](), [esptool](), [firmware](), [flash](), [getting-started](), [how-to](), [led](), [nuttx](), [partition](), [port](), [tutorial](), [usb]() ### AI overview This tutorial explains how to configure NuttX on an ESP32 DevKit, add LED support and the LED Driver Example, build and flash the firmware, and run an application that blinks an LED. ### Source excerpt This is a tutorial on how to blink an LED with NuttX after getting started. ## ESP32-S2 -- Security Features DevFeed: [ESP32-S2 -- Security Features]() Original publisher: [Read original article]() Author: John Lee Published: 2019-12-09T00:00:00Z Content type: article Language: en Sources: [Blog on Developer Portal]() Topics: [Esp32 S2](), [Security](), [ESP32](), [boot](), [Encryption](), [Cryptography](), [SOC](), [Espressif](), [Wi-Fi](), [Hardware]() Tags: [algorithm](), [article](), [blog](), [boot](), [bootloader](), [bootrom](), [code](), [cryptographic](), [cryptography](), [devices](), [encryption](), [esp32](), [esp32-s2](), [espressif](), [firmware](), [flash](), [flash-encryption](), [hardware](), [secure-boot](), [security](), [soc]() ### AI overview This article examines the security features of Espressif's ESP32-S2 Wi-Fi SoC. It describes improvements to Secure Boot and Flash Encryption, including RSA-PSS signature verification in BootROM and faster secure-boot verification enabled by an improved hardware RSA accelerator. ### Source excerpt Espressif recently announced ESP32-S2 -- a new Wi-Fi SoC with additional security features and improvements over some of the ESP32 security features. Given the current state of the security of the connected devices, these are quite meaningful features. This article discusses these changes and what do they mean from security perspective. My colleague wrote about ESP32 security features here. We continue to carry forward Secure Boot and Flash Encryption features. [Next page]()