runtime integrity Archives

Beyond writing code – Why system understanding is becoming a key skill

Sep 15, 2026

We graduate engineers who can explain every line of code yet struggle to explain why their systems fail in the field.
…
Embedded systems rarely fail line by line. More often, failures emerge in timing, scheduling, and runtime interactions that are difficult to observe through static development methods alone.
…
In an AI-assisted development world, the focus is no longer on teaching how to code but on developing system understanding.

New Appointment at Percepio Set to Drive Long-Term Product Development Activities

Sep 1, 2026

In order to extended the scope of its product offering and catalyse further commercial growth, specialist in observability technology for embedded and edge-based systems Percepio has confirmed Andreas Klintemyr as its new Product Lead.

Completing the Audit Trail: Why Embedded Teams Need Runtime Observability

Aug 25, 2026

Embedded engineers regularly encounter failures that are difficult to reproduce despite using the same firmware image throughout testing. A system may pass hundreds of test cycles before a watchdog reset occurs, a communication stack may hang only after many hours of operation, or a latency spike may appear intermittently and then disappear in subsequent runs. Continuous observability (CO) extends the audit trail into runtime execution. Rather than treating observability solely as a debugging technique, it becomes an ongoing capability that captures execution data throughout development, integration, testing, and validation.

Defence Capability doesn’t Sleep Anymore

Aug 6, 2026

Modern defence platforms increasingly gain capability through frequent software updates rather than major hardware upgrades. That shift brings speed, flexibility, and lower cost, but it also exposes a growing mismatch: capability is delivered continuously, while software assurance is still often treated as a one-time activity before deployment.

Traditional verification remains essential. Unit testing, static analysis, integration testing, and qualification provide the foundation for safe and reliable embedded systems. But they cannot fully reveal how software behaves under real operational conditions: timing pressure, task contention, hardware interactions, environmental factors, and complex integration scenarios. Some faults only emerge after deployment, triggered by rare combinations of runtime events that are difficult or impossible to reproduce in the laboratory.

Continued Operational Assurance in Software-Defined Medical Devices

Jul 29, 2026

In his latest video interview EPDT’s Editor-in-Chief Mike Green talks with Andreas Lifvendahl, CEO of Percepio about the emerging era of software-defined medical devices and how consistent behaviour can be maintained on an ongoing basis.

Clinical trials are an ideal opportunity not only to validate clinical outcomes but also to understand software behaviour under real operating conditions.

“Today it’s a lot of ad hoc debugging… then you remove the printf’s and alike completely, and then you’re basically flying blind from that point on. … But development never stops. We are only a small piece of a much larger puzzle—but it’s a puzzle that is rapidly growing and evolving” says Lifvendahl, CEO at Percepio.

« Older Entries

runtime integrity

Beyond writing code – Why system understanding is becoming a key skill

New Appointment at Percepio Set to Drive Long-Term Product Development Activities

Completing the Audit Trail: Why Embedded Teams Need Runtime Observability

Defence Capability doesn’t Sleep Anymore

Continued Operational Assurance in Software-Defined Medical Devices

Read About: