Technical blog articles written by our embedded software experts on embedded Linux, automated testing, cybersecurity, IoT and more.
At Avnet Silica and The Embedded Kit, we collaborate with hundreds of customers across industries and see firsthand how component obsolescence can derail even the most well-planned embedded projects. From sudden supply chain disruptions to overlooked scalability constraints, the risks are real…and costly.
The best way to manage obsolescence? Don’t wait for it. Anticipate it, starting at the design phase.
With the upcoming European regulation known as the Cyber Resilience Act, or CRA, manufacturers of connected devices must prepare for a series of technical and organizational requirements.
The harmonized standards meant to guide compliance won’t be published until mid-2026, with a final version expected by October 2026. Yet, compliance will be required as early as the end of 2027...
One approach already allows manufacturers to anticipate these requirements effectively: software composition analysis security.
This article is based on a real-world use case: one of our clients in the railway sector needed to strengthen the security of their Zephyr RTOS platforms. Integrating this requirement into our CVE scanning tool revealed several challenges, some of which you may have encountered yourself. In this article, we share the key obstacles we faced and the solutions we developed to overcome them.
In a world where connected devices are proliferating, managing embedded connectivity is becoming more complex. This highlights the role of what we call embedded agents, i.e. modules that ensure robustness, security, and scalability in modern architecture, especially in industrial and IoT systems.
We all see it day after day: devices are becoming more intelligent. Now, designing embedded systems means equipping them with the ability to interact with their environment, communicate remotely, and even adapt in real time to unexpected constraints.
This article explores the core principles of connected system architecture and the role of an IoT platform, using the concrete example of connected lawn mowers.
In the embedded world, every second counts. Whether it's to improve user experience, reduce energy consumption, or meet industrial constraints, the boot time of an embedded Linux system is often an underestimated challenge.
We conducted an in-depth study on this topic with a clear goal: launch a graphic application (DOOM) in under 2 seconds on an i.MX93 board using our Welma distribution.
Spoiler: mission accomplished.
Building a solid vulnerability management strategy requires more than just tools. It’s about aligning your process, your team, and your technology. Here’s how to structure your plan effectively.
As part of our software industrialization strategy, we’ve built an automated test infrastructure tailored to embedded systems based on Yocto. This initiative, led by our development team, was designed to improve delivery reliability, accelerate embedded software development cycles, and ensure the quality of the system images we deliver.
Whether you're working on the OS or the application layer of your embedded system, security is non-negotiable. One of the most effective ways to prevent attacks is to find and patch vulnerabilities (also called CVE) regularly. This is the essence of the vulnerability management lifecycle. Let’s break it down.