Grzegorz Sejnota

ZF’s SDV middleware demonstrator shows how secure, flexible, and scalable architectures can be realized today. Built on the ✅Qorix performance architecture, based on ✅Eclipse S‑CORE, and running on ✅ZF ProAI with Red Hat’s vehicle OS, it enables the safe integration of mixed workloads combining open‑source innovation with proven ZF technology.

167

1 komentarz

The Squish team is happy to announce the release of Squish GUI Tester 9.0.1, the software quality assurance tool for cross-platform GUI application test automation. Squish 9.0.1 introduces support for Qt 6.9 and Android 15 (including Android Automotive and TV), ensuring compatibility and extended testing capabilities. The release also adds 64-bit Windows binary packages for Squish for Web to better support Python users. Learn more: https://hubs.li/Q03mqJn20 #SoftwareTesting #QualityAssurance #SoftwareQuality #GUI CrossPlatform

11

Functional Safety is no longer optional, it’s becoming a core requirement across modern embedded systems. The challenge is not just understanding the standards, but applying them effectively in real-world development and testing environments. Let's hear what the experts have to say about that. This Wednesday, 18:00; Embedded Austria No. 6: Functional Safety. Secure your ticket. See you there 👋

7

1 komentarz

The Critical Role Of Safety Microcontrollers In ADAS And AD Applications. New Webinar: https://lnkd.in/d4bqBN-E Join us for an in-depth exploration of the critical role Safety Microcontrollers (MCUs) play in Advanced Driver Assistance Systems (ADAS) and Automated Driving (AD) applications. This webinar, presented by Infineon Technologies, aims to provide a comprehensive understanding of the functionalities and indispensability of Safety MCUs, particularly in contrast to the nascent Safety Islands within System on Chips (SoCs). Discover why OEMs continue to rely on external Safety MCUs, such as Infineon's AURIX™, despite the common availability of Safety Islands in modern automotive SoCs. Key takeaways: ✅ Essential Role of Safety MCUs: Safety MCUs are a cornerstone of a proper FUSA concept for ADAS/AD applications, such as domain controllers, smart cameras, LiDARs, and radars. ✅ Critical Functions of Safety MCUs: Safety MCUs supervise actuator commands, provide emergency response, monitor the health of all critical components, offer gateway functionality, and support an independent real-time software environment. ✅ Advantages of AURIX™ Safety MCUs: AURIX™ is the technically proven solution due to its best-in-class scalability, extensive AUTOSAR and safety software portfolio, and ability to handle fail-operational use cases. ✅ Limitations of Safety Islands: Safety Islands in SoCs lack the comprehensive feature set and hardware separation that dedicated Safety MCUs offer; hence, they cannot replace them.

165

2 komentarze

See who will be there at #ELIV2025 next week! ETAS' portfolio includes software development tools, software testing solutions, automotive middleware, data acquisition & processing tools, authoring & diagnostic solutions, automotive cybersecurity solutions, and end-to-end engineering and consulting services for the realization of software-defined vehicles. Its product solutions and services enable vehicle manufacturers and suppliers to develop, operate, and secure differentiating vehicle software with increased efficiency. MathWorks is the leading developer of mathematical computing software for engineers and scientists. They will bring MATLAB®Copilot which provides generative AI-powered capabilities specifically for the MATLAB desktop environment. It assists with MATLAB workflows and provides responses based on MATLAB specific information. Minerva Systems designs platform software and tools for embedded systems in autonomous and software-defined vehicles. Their solutions ensure seamless integration, high performance, and real-time AI for safe, secure applications, reducing risks and costs in complex hardware-software integration while boosting computational performance. Nexdata is a leading provider of high-quality AI training data solutions. Its services include multimodal data collection, annotation, and curation, utilizing advanced tools and adhering to ISO-certified quality standards. Headquartered in Singapore, we are committed to empowering AI innovation worldwide. Qorix accelerates the transformation to software-defined vehicles. They will bring the Qorix Performance Demonstrator, which is world-wide the first demonstrator to run on the Eclipse Foundation’s S-CORE open-source initiative. By building on S-CORE, Qorix demonstrates how open collaboration can be transformed into a production-ready distribution that original equipment manufacturers and tier-one suppliers can trust.

56

2 komentarze

Empower your embedded systems with ZF Engineering Solutions’ end-to-end Cybersecurity Solutions. From concept to long-term support, we offer a comprehensive suite of services tailored to the unique challenges of embedded systems. We cover various markets, including IoT, Railway & OT, Automotive, Motorbike, Agriculture, and Construction Machinery. 🛡️ Regulations & Compliance: We’re here to support you in embedding Cybersecurity into your workflows - ensuring compliance, boosting efficiency, and raising your standards. 🛠️ Cybersecurity Engineering (SYS & SW): We offer systematic analysis of stakeholder requirements, threat and risks analysis (TARA), the development of a secure architecture based on current best practices, the integration of security measures into the manufacturing process, tailored software implementation across various hardware platforms and operating systems and define a secure configuration for your underlying hardware. 🧪 Validation & Verification: We validate your product’s security - from basic functional testing to penetration and fuzz testing. 🛰️ Product SOC: We ensure real-time protection for your products and components through our monitoring, incident response and long-term support services including Hardware and Software preservation for up to 25 years. 🧰 Tooling & Automation: Effectiveness relies on automation and fast access to details. Stay tuned for our SBoM generator tailored into your environment, CSMS, and EPIC Framework for CAN/Flexray/LIN/Ethernet Fuzzing with advanced monitors and scanning. For more details stay tuned! If you have any questions or need assistance, our ZES Cybersecurity team is happy to help. Feel free to reach out to Christian Becker and team.

79

At AUTOSAR Open Conference (AOC) 2025, Fabian Klebert, Technical Coordinator at NDS Association, will join leading voices from across the automotive sector to spotlight the role of open-source software in the development and implementation of industry standards, focusing specifically on the open-source tool zserio and its integration within NDS. zserio is a framework for serializing structured data with a compact and efficient way with low overhead. You can find out more in our new blog post: https://lnkd.in/dXpsGpu5

16

In case you missed it, the AUTOSAR Newsletter for Q4 2025 is now publicly available and presents key developments and updates from across the organization In this issue: - CAPI: The Collaborative Foundation for Software-Defined Vehicles - 17th AOC: Sponsorship Opportunities - Release Event 2025: Recap of Achievements - All WG 2026: Registration Continues - Concept Roadmap - Concept Descriptions: Improvements to MACsec support - Removal of CP TR Franca Integration - Regional updates: China Hub News by Echo Wang​​​, Japan Hub News by Tsuyoshi Sakurai, and North America Hub News by Steve Crumb​ The newsletter is available in English, Japanese, and Chinese. Please visit our website to access the full issue: https://lnkd.in/d_Ew-ug5 #AUTOSAR #SoftwareDevelopment #Automotive #AUTOSARCommunity #AutomotiveInnovation #AUTOSAREnthusiasts​

15

Software is pervasive in automotive platforms and components, but its development is not without challenges. For its “2025 State of Automotive Software Development Report,” Perforce Software surveyed more than 650 automotive development professionals around the world on current practices and emerging trends within the #automotive #software industry. Anne-Françoise Pelé spoke with Jill Britton, director of compliance at Perforce Software, for perspective on the facts and figures in this year’s survey. https://lnkd.in/eSSGbnKz #automotiveelectronics #automotiveengineers #automotivesafety #automotivesecurity #autonomousvehicles #autonomousdriving #ADAS #Rust #C++ #programminglanguage #MISRA #ISO26262 #ASIL #opensourcesoftware Motor Industry Software Reliability Association

2

From single-core to multicore — but you don’t have to start from scratch. 🚗⚙️ In automotive embedded systems, the shift to multicore is inevitable. But with safety-critical legacy code and real-time constraints, migrating from single-core isn’t just plug-and-play. That’s where our AUTOSAR expertise comes in. We contributed to the introduction of multicore into AUTOSAR with release 4.0.1 in 2009 and simultaneously developed the ETAS RTA-CAR BSW stack: a robust, field-proven solution that fully supports any customer use case. Built by engineers, for engineers —RTA-CAR at a glance: 🔧 Compact & efficient - Optimized for resource-constrained, low-latency real-time environments. 🛡️ Safety & security - Complies with industry standards like ISO26262 and ISO/SAE21434, along with MISRA-C & CERT-C guidelines. 🛠️ Versatile compatibility - Suitable for all ECU types, from smart sensors to vehicle computers, and adaptable for single and multi-OEM projects. ⚡Wide device support - Compatible with various target devices and integrates seamlessly with third-party MCALs and security solutions. 🚀 Proven success - Deployed on over 4 billion ECUs globally. We’ve summed up more exclusive insights and real-world cases to help you navigate the transition in a white paper. Download it now: https://brnw.ch/21wSQG3 #YourAmbitionIsOurMission #AUTOSARClassic

53

In regulated automotive software, “extra capacity” is not the problem. Ownership is. At Thinking in Code, we do not position ourselves as staff augmentation. We take responsibility for defined workstreams in safety-critical and security-critical embedded systems. Our core focus is AUTOSAR Classic integration, ISO 26262 Part 6 software safety, and ISO/SAE 21434 cybersecurity execution. What this looks like in practice: A typical pattern is a program stuck in late integration. BSW partially configured. OS and MPU not fully aligned. Timing unstable. Safety work products drafted but not coherently closed. Multiple suppliers, unclear interfaces. We step in with a defined scope: – Full BSW and MCAL integration ownership – OS, memory layout, linker, and timing closure – SWRS, SWAD, SWDD and safety analysis alignment – Cyber stack and HSM integration where required – Clear Definition of Done and evidence package The insight is simple. In ASIL programs, integration friction is not solved by adding engineers. It is solved by assigning accountability. The takeaway: if a workstream has no single owner for deliverables and audit evidence, it will drift. We exist to prevent that drift.

8

🏁 The 2026 State of Automotive Software Development Report is now LIVE! 🚘 Get full access to the report for in-depth analysis on: ⚙️ The biggest challenges in automotive development 🧠 How AI is transforming SDVs — and why safety concerns are on the rise 🔑 Key coding standards shaping the industry 🧰 Essential tools & best practices for dev teams Scroll to find out how automotive organizations are being impacted this year and how they plan to overcome challenges. Unlock your FREE copy of the report today! https://ter.li/mmtw0x #AutomotiveDevelopment #AutomotiveSoftware #DevOps #DevSecOps #MISRA #ADAS #Infotainment #FunctionalSafety #SoftwareCompliance

27

Discover how following ISO 26262 requirements enhances automotive system safety and reduces failure risks through structured development and testing practices. ⬇️ In this article, we explore: 🔸Who needs to comply and why 🔸What essential information about ISO 26262 automotive companies should know 🔸What functional safety trends to watch out for https://cutt.ly/urcgyydk #embeddedsoftware #embeddedsoftwaretesting #SecurityTesting #automotive #automotivesecurity #automotivesolution #aprioritblog

11

𝗔𝗜 𝗶𝗻 𝗤𝘁 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗺𝗲𝗻𝘁: 𝗪𝗵𝗲𝗿𝗲 𝗜𝘁 𝗜𝘀 𝗔𝗹𝗿𝗲𝗮𝗱𝘆 𝗖𝗵𝗮𝗻𝗴𝗶𝗻𝗴 𝗥𝗲𝗮𝗹 𝗪𝗼𝗿𝗸𝗳𝗹𝗼𝘄𝘀 In our work with Qt teams across automotive, industrial automation, robotics and medical, we are seeing AI influence development workflows earlier than many expected. The most immediate impact is often not in the final product, but in how Qt and QML-based software is implemented, refined, and validated. A clear shift is already becoming visible: AI-assisted coding can support QML component generation, layouts, state handling, and other repetitive implementation tasks. Code can be created faster, but that does not automatically make development workflows faster overall. In Qt projects, even small UI changes still need to be verified in a real application context. Layout behaviour, property bindings, navigation logic, and interaction flows must still be checked quickly and repeatedly to ensure that the result behaves as expected. This is where a new bottleneck starts to appear. If every generated change still requires a full rebuild and restart cycle, much of the expected productivity gain disappears again. Faster code generation only creates value if the surrounding workflow can keep up. As AI becomes part of Qt development, iteration speed is becoming more strategic. Fast feedback loops are no longer just a developer convenience. They are increasingly a workflow capability, especially in larger projects where validation needs to happen consistently across teams and systems. AI in Qt development is therefore not only about generating code faster. It is about reducing friction across the full implementation and validation workflow. This is where solutions such as 𝗙𝗲𝗹𝗴𝗼 𝗤𝗠𝗟 𝗛𝗼𝘁 𝗥𝗲𝗹𝗼𝗮𝗱 become increasingly relevant. By enabling real-time UI validation and shorter feedback loops, they help larger Qt projects turn AI-assisted coding into a practical workflow improvement rather than adding another layer of complexity. If AI-assisted development is becoming part of your Qt workflow, try Felgo QML Hot Reload to reduce validation friction and shorten feedback loops. 👉 https://lnkd.in/eXY2ja73 #Qt #QtDevelopment #AI #EmbeddedSystems #HMI #SoftwareArchitecture #SoftwareEngineering #AutomotiveSoftware #IndustrialSoftware #Felgo

7

Everyone knows what CPU load is, how it is defined and how to deal with it, right? Well, many projects actually get it wrong and even a relatively good approach might report less then 100% load although the system already suffers from a local hotspot, an overload. With his talk, Peter will help to avoid pitfalls. He even comes up with a new suggestion how to get a more reliable load indicator in the future.

44

🧩 Requirements Engineering – how to define requirements properly in an ECU project? Well-defined requirements are the backbone of any embedded project. In ECUs – they’re key for ASPICE, ISO 26262 compliance and ensuring the system behaves as expected. But how do we ensure that requirements actually work – not just look good in DOORS? 🚘 What does “well-defined requirements” actually mean? ✅ Unambiguous – everyone understands them the same way ✅ Testable – easy to verify ✅ Right level of detail – not too broad or low-level ✅ Traceable – linked to architecture, code, and tests ✅ Reviewed & versioned – living artifacts, not PDFs 🚧 Most common challenges in requirements gathering: 🔻 Vague expectations – “fast, safe, reliable” ≠ requirement 🔻 Changing scope – requirements evolve throughout the project 🔻 Inconsistent detail level – some are specific, others abstract 🔻 Too much room for interpretation ✏️ “The system should react quickly to voltage errors.” ➡️ What does “quickly” mean? 1 ms? 100 ms? After how many errors? Without clarification, everyone is free to interpret it differently – and there’s nothing to verify in the tests. 🔻 Converting system to software requirements – often leads to functional gaps 🧾 System requirement: “The system shall detect a temperature sensor fault and enter safe mode.” “Detect sensor fault and enter safe mode.” 🛠 If not clarified → problems on the software side: – How do we detect the sensor failure? – What exactly is “safe mode”? – Should a DTC be sent? How fast? Should there be a CAN message? ➡️ If this isn’t broken down into specific software requirements, a developer may implement a simplified logic… which won’t meet the customer's expectations – or the safety goals. 🔻 Missing context – especially in Tier1–Tier2 setups, specs are incomplete 🔧 What helps get requirements under control? 🔹 Templates (EARS) – write clear, structured specs 🔹 Modeling (SysML, architecture) – reveal missing pieces 🔹 Tools – DOORS, Polarion, Jama 🔹 Early collaboration – system/software/test alignment 🔹 Traceability – links to tests = confidence 🔹 Regular reviews – prevent last-minute surprises 🧠 Good requirements aren’t just audit artifacts. They’re an engineering tool that: ✅ speeds up development ✅ reduces bugs & confusion ✅ improves collaboration ✅ lowers change costs 💬 How do you handle requirements in your team? ➡️ Who owns the specs – system engineer or architect? ➡️ What helps most – tools, workshops, templates? Let’s share tips 👇 #RequirementsEngineering #SystemsEngineering #EmbeddedSystems #SoftwareRequirements #Traceability #ModelBasedDesign #DOORS #ASPICE #SoftwareQuality

5