wolfSSL announces wolfBoot support for the NXP LPC55S69, available now in PR #713. With Secure Boot, TrustZone-M, and an industry-standard cryptographic API, your non-secure application can be rapidly developed for a secure world. About the NXP LPC55S69 The LPC55S69 is a general purpose edge computing device, with dual ARM Cortex-M33 cores running up to 150 […]
Read MoreMore TagCategory: wolfBoot
wolfBoot Port for NXP T2080 QorIQ for Avionics
wolfSSL is pleased to announce wolfBoot support for the NXP QorIQ T2080, a quad-core Power Architecture e6500 processor used in aerospace, defense, and industrial control. wolfBoot is a compact, portable secure bootloader that replaces U-Boot with cryptographic firmware verification and optional Post-Quantum Cryptography (PQC) – pure PQC or hybrid classical/PQC. It compiles to under 32 […]
Read MoreMore TagStopping Ransomware at the Device Level
Ransomware now targets medical devices, not just IT systems. Once malicious code runs on a device, it can disrupt patient care. The best defense is preventing execution. wolfSSL blocks ransomware before it runs: wolfBoot – Prevents unauthorized firmware from executing at startup wolfCrypt – Encrypts storage and secures firmware updates to prevent tampering wolfSentry – […]
Read MoreMore TagWhy Secure Boot Is Now an FDA Expectation
The FDA now expects medical devices to use a secure boot. Without it, devices can run unauthorized firmware, including malware or compromised code from supply chain attacks. wolfBoot is a secure bootloader for embedded medical devices. It uses wolfCrypt to verify firmware signatures before allowing code to run. Only authenticated firmware executes. For additional security: […]
Read MoreMore TagA Second Helping of Security for the Raspberry Pi Pico
Last year, we wrote about the support we added for the Raspberry Pi Pico in wolfSSL. Since then, we haven’t been sitting idle. The wolf pack has been busy adding even more security goodness to the Pico ecosystem. If you thought TLS on a $1 microcontroller was impressive, wait until you see what we’ve been […]
Read MoreMore TagwolfBoot Secure Boot on the STM32N6
wolfSSL is announcing wolfBoot support for the STM32N6 series added in PR #720, starting with the NUCLEO-N657X0-Q development board (STM32N657X0H). The STM32N6 is ST’s first Cortex-M55 microcontroller, designed for high-performance edge AI workloads with a dedicated Neural Processing Unit (NPU). wolfBoot provides cryptographic signature verification and secure firmware updates on this new platform. Getting started […]
Read MoreMore TagwolfBoot Adds SD Card Secure Boot for Xilinx Zynq UltraScale+ MPSoC
wolfBoot now supports SD card boot on the AMD/Xilinx Zynq UltraScale+ MPSoC (PR #699). This brings authenticated, signature-verified boot of Linux directly from SD card partitions on the ZCU102 evaluation kit, complementing the existing QSPI flash boot path that has been the sole production boot option until now. The ZCU102 (quad-core Cortex-A53, dual Cortex-R5, FPGA […]
Read MoreMore TagwolfBoot 2.8.0 released
We are pleased to announce the release of wolfBoot 2.8.0, a major update that expands platform support, strengthens PSA and TrustZone integration, and delivers another round of meaningful hardening across the secure boot and firmware update flow. This release stands out for the breadth of hardware now supported. wolfBoot 2.8.0 adds or extends support for […]
Read MoreMore TagwolfBoot vs Intel Slim Bootloader
Since version 2.0.0, wolfBoot runs as a bare-metal bootloader on x86-64 (amd64 / Intel 64), using Intel FSP for silicon initialization — the same approach taken by Intel’s Slim Bootloader. So what sets them apart? Quite a lot. Getting started with wolfSSL? Download the latest libraries here and start exploring. Advanced Cryptography & Quantum Readiness […]
Read MoreMore TagwolfBoot adds DICE and Measured boot via PSA Initial Attestation
Secure boot establishes authenticity (“this image is signed by a trusted key”). But many modern deployments also need attestation: a portable, verifiable way to prove what actually booted to a relying party: during onboarding, after updates, and throughout a device’s lifetime. That’s where DICE (Device Identifier Composition Engine) comes in. DICE composes a device identity […]
Read MoreMore Tag