Newsletter in May 2026

                      - Collaboration between RAZORCAT and SEGGER
                        - Trace-based Insights into the CI/CT Workflow
                                      - From Uncertainty to Clarity:
             How PERCEPIO Detect 2025.2 is revolutionizing Debugging
                         - Why invisible Bugs plague Embedded Systems
                 - The TaskMonitor Revolution: Making the Invisible visible
                    - The strategic Shift: From Firefighting to Prevention

---

Our long-standing partners, RAZORCAT Development GmbH and SEGGER Microcontroller GmbH, are further expanding their collaboration in the field of embedded software testing. The goal of the partnership is to continue developing test solutions for embedded systems and to further optimize the integration of SEGGER development tools into the TESSY test automation tool.

Collaboration between RAZORCAT and SEGGER TESSY from RAZORCAT is a well-established tool for module and integration testing of embedded software, particularly in safety-critical projects. It automates the creation and execution of tests, assists with the organization and management of test cases, and is compatible with a wide range of microcontrollers, compilers, and debuggers. SEGGER’s development tools are already fully integrated into TESSY. SEGGER Embedded Studio is a powerful IDE for project management and the development of embedded software. It includes the SEGGER toolchain for generating highly optimized firmware, as well as seamless integration with J-Link debug probes for debugging and testing on the target system. In addition, a core simulator is available, enabling fast and efficient testing without physical hardware. TESSY supports Embedded Studio projects by allowing tests to be generated directly based on existing development environments. Test execution takes place within TESSY using J-Run or emSim for result capture. If tests fail, TESSY can automatically start a debug session in Embedded Studio so that the causes can be analyzed immediately. Read more about this topic here.

Trace-based Insights into CI/CT Workflow -  An important Feedback Loop! One of the most interesting discussions we frequently have with customers revolves around how trace-based insights can be integrated more seamlessly into automated development workflows, such as CI tests. That’s why PERCEPIO is now offering an early access opportunity for Tracealyzer CLI. Tracealyzer CLI (Command Line Interface) is a new command-line interface for Tracealyzer designed for teams that want to use trace analysis more systematically as part of their CI/CD workflows, test automation, and regression feedback loops. As part of this early access program, the interface can continue to evolve based on real-world customer feedback prior to its official release. We believe the timing is right and want to work closely with our customers to ensure optimal alignment with your workflows: It facilitates the integration of trace-based diagnostics into automated pipelines It helps teams transition from one-off debugging to more repeatable analysis It supports the early detection of timing anomalies, latency deviations, and unwanted behavior changes It opens up new possibilities for using trace data as part of continuous quality assurance For many embedded teams, this could become a practical bridge between runtime observability and structured engineering workflows: not just opening a trace when a problem occurs, but continuously using trace insights to detect regressions and deviations earlier. If you’d like to test Tracealyzer-CLI in your production environment and provide us with feedback, we welcome you as an early adopter. In return, you’ll receive early access to a feature we believe can be of great value to teams working with automation, CI, and continuous testing. Are you interested in early access or beta status?  Please reply to this email or contact us directly via this form, and we’d be happy to continue our conversation. On this topic, we also recommend the article by Editor-in-Chief Chris Edwards in New Electronics: “Keeping a Close Watch”, in which PERCEPIO founder Johan Kraft contributes to the dialogue on embedded observability.

From Uncertainty to Clarity: How PERCEPIO Detect 2025.2 is revolutionizing Debugging   The embedded world 202 conference in March clearly demonstrated that embedded software teams are facing increasing pressure from multiple fronts simultaneously: faster release cycles, more complex software, higher expectations for quality and reliability, and a growing need for more robust evidence in verification and validation. What was particularly striking in Nuremberg was that observability is no longer a niche topic. More and more teams are realizing that better insight into runtime is not only useful when something has already gone wrong, but also as a continuous feedback loop throughout the entire development and testing phase. This is exactly what PERCEPIO means by Continuous Observability.

Why invisible Bugs plague Embedded Systems   Embedded software teams are facing an increasingly frustrating paradox. Paradoxically, the more complex and interconnected systems become, the less able they are to observe what is actually happening at runtime. The most costly bugs today are not the ones that predictably cause crashes—they are the phantom bugs: mysterious freezes, resource exhaustion, and timing anomalies that vanish before leaving any diagnostic clues. Let’s consider a typical scenario: A device reboots on its own, leaving developers completely in the dark about the “why.” What triggered the reboot? Was it a deadlock? Did the CPU starve? Memory bottlenecks? No idea. Conventional debugging tools offer virtually no help. Engineers resort to extensive logging, which causes massive overhead that fundamentally alters system behavior and obscures the very problems they’re actually looking for. This reactive approach wastes countless development hours and delays critical releases.

The TaskMonitor Revolution: Making the Invisible visible PERCEPIO Detect 2025.2 ushers in a paradigm shift with its TaskMonitor feature. Instead of waiting for catastrophic failures to become apparent, this technology proactively monitors CPU activity at the thread level and continuously watches for the warning signs that precede a system failure.  More importantly, TaskMonitor automatically detects firmware freezes and overload conditions even when no explicit error occurs—thereby eliminating the very blind spots that plague conventional approaches. The elegance of this solution lies in its architecture. TaskMonitor maintains a continuous, resource-efficient monitoring window across your entire system. When anomalies occur—whether it’s a thread consuming an excessive number of CPU cycles, a scheduler neglecting critical tasks, or timing violations creeping into your execution patterns—the system detects them immediately. Unlike reactive debugging, PERCEPIO Detect doesn’t wait for a catastrophe. It nips problems in the bud when they’re still small enough to understand and fix. Furthermore, this capability transforms how teams approach embedded development. By preserving the critical execution context of the original incident, Detect enables engineers to precisely reconstruct what happened, drastically accelerating root cause analysis. The proven reduction in debugging time by up to 90 percent on resource-constrained systems represents a massive, measurable improvement for teams that constantly struggle with time and resource constraints.

The strategic Shift: From Firefighting to Prevention Perhaps most significantly, PERCEPIO Detect 2025.2 is driving a fundamental shift in embedded software quality assurance. Teams can finally transition from reactive debugging - constantly putting out fires after system failures - to preventive quality assurance strategies. This shift transforms the entire workflow of embedded software development. As a result, companies that adopt this approach benefit from earlier risk detection and identify potential defects during development rather than after deployment - possibly at the customer’s site. Engineers gain confidence in the reliability of their system because they have actually observed and validated its behavior under stress conditions. This proactive approach not only saves time but also fundamentally improves product reliability and customer satisfaction. Ultimately, PERCEPIO Detect 2025.2 makes embedded software development more predictable and resilient. By uncovering previously invisible defects, the platform enables teams to develop systems that not only function but also operate reliably under real-world conditions.

The era of blind debugging of embedded software is coming to an end. Sincerely Yours, Marian A. Wosnitza „Freedom is worthless unless it includes the freedom to make mistakes." (Mahatma Gandhi, Indian lawyer, pacifist)