Let’s consider the general case where the development team and the manufacturer are two separate entities, possibly different companies in different countries. We will focus on products based on Arm processors.

Enabling secure boot on Raspberry Pi 4 is often identified as a key development step to protect devices against cyber-attacks. In this third article of our secure boot series, Simon, a software engineer at The Embedded Kit, walks us through the process to configure secure boot on Raspberry Pi 4 boards: hardware setup, software dependencies, and verification steps.

Secure boot is a fundamental security mechanism designed to protect devices from executing unauthorized or malicious code at startup. The problem it solves is simple but crucial: without validation, a device could load altered firmware or malware at startup, potentially compromising the entire system.

In this first article of our secure boot series, Zakaria, an engineer at The Embedded Kit, discusses the concepts and mechanisms associated with the secure boot process.

AAEON announced its collaboration with The Embedded Kit to offer a complete solution for the challenges facing industrial companies such as integration, maintenance, and cybersecurity. The partnership will provide a seamless and efficient design process by simplifying the complexities of software and hardware integration.  

The Embedded Kit recently conducted a survey to understand the biggest challenges facing an embedded developer. You would think those challenges are obvious, and some of them are, but the survey uncovered some fairly interesting areas that are not so obvious.