Pedro Rodrigues

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

Engineering, to the power of AI. ⚙️ In embedded systems, a single oversight in a requirement, a design choice or a line of code can cost millions or even lives. That’s where AI makes the difference. With Expleo, engineering teams move from quality-by-testing to quality-by-design: ⏱️ Reduce Hardware-in-the-Loop testing time and costs by up to 30% 🛠️ Minimise unscheduled maintenance by up to 50% with AI-driven predictive maintenance 🛡️ Add extra safety features with ultra-light EdgeAI virtual sensors Our experts help you design smarter from the start, so you can deliver safer systems, faster testing and fewer failures. 👉 Discover how to elevate product performance, to the power of AI: https://expleo.to/3JYLQ1E #ToThePowerOfAI

53

Two cities, two goals: collaboration and innovation 🤝 🚀 ETAS is proud to support the third chapter of the Eclipse Software Defined Vehicle (SDV) Hackathon, taking place September 30 – October 2, 2025. For the first time, the hackathon will run simultaneously in two European cities: Porto and Berlin, bringing together automotive software enthusiasts to collaborate, innovate, and code in parallel across both locations. 🌍💡 🔹 About the Challenge Over 2.5 days, teams will experiment with cutting-edge SDV tools and blueprints guided by coaches from leading OEMs, Tier 1s, and tech companies including ETAS, Microsoft, Elektrobit, Eteration, and Red Hat. The hackathon features two tracks: SDV Tooling SDV Blueprints 🔹 Hack Challenges From virtual ADAS development to secure OTA update systems, teams will work hands-on with open-source tools to bring innovative SDV solutions to life. By supporting this event as part of the Eclipse Software Defined Vehicle Working Group, ETAS continues to champion innovation in open standards and modern software development for the automotive industry. 👉 Learn more & register here: https://lnkd.in/eQJvdzVm #SDV #SoftwareDefinedVehicle #SDVHackathon25

63

1 comentário

You're starting a job in the software team at Shapeways. You'd expect to be diving into the code, right? Not so fast. When new engineers join Tiago São José's team at Shapeways, they don’t start by writing code. Instead, they spend a day in production — packing boxes, shipping orders and using the tools they’ll be developing. Because developing the best software comes from understanding how its used in the real world, and knowing the people who use it. ▶️ In this clip, Tiago explains why empathy is at the heart of engineering. See the full video on our blog: https://lnkd.in/e_QZQKC8

40

3 comentários

I’ve built Cursor for Automotive Software Engineering. (Not a code generator. A humanoid software engineer.) You give it an intent: — “Develop ASIL‑B parking controller” It doesn’t just spit out snippets. It: → Plans end‑to‑end: architecture, component layout, data flows → Generates fully compliant code—header + implementation files → Embeds safety: ASIL-B logic, watchdogs, fault checks → Ensures traceability: links every line back to requirements → Writes unit & integration tests, built into CI flow → Produces docs: Doxygen‑style comments, design notes → Validates compliance: MISRA‑C, ISO 26262, ASPICE rules → Logs rationale: decision logs, spec references, design choices → Writes Make Files, Compiles clean → Organizes everything into your folder structure automatically Imagine listening to a developer watching it work: “Hold on, it just wrote 24 production‑grade files—tests, docs, safety checks—all in under 30 min.” Remember how long it takes to scaffold all that manually? Now it happens instantly. This is early. Rough edges exist. But the implications are massive. Could your team use an AI engineer that: — respects real-time safety standards, — fits into your existing architecture, — and saves weeks of work? That’s the vision. Curious who’s thinking along the same lines. Would you trust a vibe coder like this in your next sprint? ------- Early version ready for some engineering teams to test. Interested? Shoot me a DM.

193

33 comentários

Porto, leadership in QA does not always come with a title. As Quality Engineering evolves, so do the careers of the people within it. Many professionals find themselves leading initiatives, influencing decisions, and guiding teams long before leadership is formally recognized. This often leads to important questions about growth, direction, and long-term career choices. At the 22nd Test Tribe Porto Meetup, we create space not only for technical learning but also for honest reflection on leadership journeys in modern organizations. Session 2 focuses on a question many professionals quietly ask: To Lead or Not to Lead? A Discussion on Career, Functional and Technical Leadership In this session, Tiago Paixão explores how leadership takes many forms. From technical and functional leadership to informal influence, this talk examines when leadership begins, how it develops, and what challenges leaders face along the way. With decades of experience across industries, Tiago brings a thoughtful and grounded perspective that encourages attendees to reflect on their own paths. This session is especially relevant for anyone considering leadership or already influencing teams without a formal role. Meetup Details 📅 14th January 2026 🕡 18:30 (Portugal Time) 📍 Uphold, Porto If you are thinking about your next career step or want clarity on leadership paths, this session will resonate. 👉 RSVP here: https://lnkd.in/ghmEaaGz Thank you to our Tribe Champions Allan Ferreira and Paulo Oliveira for making community-driven learning possible in Porto. #thetesttribe #portoevents #qacareer #techleadership #testingcommunity

15

1 comentário

Automotive SPICE: A Map of the Past? Everyone’s fighting about ASPICE… Maybe it’s not ASPICE we should be fighting about… Maybe it's the world that changed – and the map didn't. Today, the entire debate about ASPICE feels stuck between two camps: → Those who defend it at all costs, saying: “If everyone would just follow it properly, everything would work.” → Those who reject it outright, saying: “It’s outdated overhead that blocks real engineering.” But maybe… both sides are missing the bigger truth. The world has changed. ➡️ Platform architectures evolve continuously ➡️ Agile thinking & real-world feedback loops dominate product development ➡️ Milestone-based models clash with lifecycle-driven innovation ASPICE wasn’t created for this kind of world. It was designed for a time when engineering was project-centered, not product-centered. That doesn’t make ASPICE wrong. It makes it incomplete for what’s coming. And that’s why so many engineers feel torn: → Some try to force the new world onto the old map. → Some want to throw the map away entirely. What we really need is something else… A conversation. A conscious evolution. A new map. Not to erase what was good – but to blend the strengths of the past with the realities of software-defined vehicles and adaptive platforms. Maybe we don’t need “Automotive SPICE” anymore. Maybe we need an SDV-SPICE – a Software-Defined-Vehicle SPICE. → One that respects structure – but honors change. The real question isn’t whether we still need ASPICE. The real question is: Who’s willing to stop pretending the map still fits – and start drawing the next one? #MrBrokenTesting #TruthInTesting #AutomotiveSPICE #ASPICE #SDV #MapAndTerritory

68

28 comentários

Why ISO 26262 Is Crucial in Automotive Development As vehicles become smarter, more connected, and increasingly autonomous, ensuring functional safety is not just important — it’s essential. That’s where ISO 26262 comes in. ISO 26262 is an international standard specifically designed for the functional safety of electrical and electronic systems in production automobiles. It provides a structured framework to identify and mitigate risks related to system failures, ensuring that vehicles operate safely even in the face of unexpected faults. Why is it needed? Complexity is growing: Modern vehicles have hundreds of ECUs and millions of lines of code. ISO 26262 helps manage this complexity with systematic risk assessment and development processes. Safety is non-negotiable: From ADAS to electric powertrains, safety must be built in — not added on. Global trust: Compliance with ISO 26262 builds credibility with OEMs, regulators, and end users alike. Whether you're a developer, engineer, or product leader, integrating ISO 26262 early in your V-model or agile development cycle is a proactive step toward safer mobility. Safety isn’t just a feature — it’s a responsibility. #Automotive #ISO26262 #FunctionalSafety #AutonomousVehicles #AutomotiveDevelopment #ASIL #SafetyFirst

38

2 comentários

I had the opportunity to test GLIWA T1 4.0 recently. Thanks to Cristian Garzón and Germano Brunacci for the oportunity. GLIWA T1 4.0 is not “new.” It’s just less friction. And that matters. And honestly: it’s hard to improve an already great tool without just adding noise. This feels like the opposite, same fundamentals, fewer steps, faster loops. What stood out in my quick test: - Overall it feels faster (less waiting, quicker iterations) - A new page that puts the key information in one place, no more tab switching between cont / scope / … just to keep context - A very practical one: T1.flex across all functions at once, no more manual work selecting each function, starting measurements, repeating the same setup cycle Why this matters in real projects: timing/resource closure isn’t blocked by “lack of data”, it’s blocked by workflow friction. Reducing manual steps increases cadence and makes it easier to keep integration disciplined. What’s your biggest time sink today in timing analysis: setup/selection, running measurements, or turning results into decisions?

24

1 comentário

Traditional development approaches that prioritize hardware and mechanical systems are no longer sufficient in the era of software-defined vehicles. As the industry shifts its focus and the competition adapts, automakers must consider new strategies that emphasize agility and innovation. Read the “Don’t Get Outpaced” eBook to identify outdated approaches and learn new strategies to navigate the future of mobility: https://lnkd.in/eNf8hitn

41

Kinematic Equations in ADAS Advanced Driver Assistance Systems (ADAS) rely on kinematic equations to predict motion, avoid collisions, and keep drivers safe. These equations help calculate: ✔ How fast a car is moving (velocity) ✔ How quickly it can stop (deceleration) ✔ How far it travels before reacting (stopping distance) v=v₀+at: Final velocity. d=v₀t+½at²: Displacement. v²=v₀²+2ad: Velocity-displacement relationship. d=1/2(v₀+v)t: Displacement with average velocity. Where: v = final velocity v₀ = initial velocity a = acceleration t = time d = displacement Automatic Emergency Braking (AEB): Scenario: Your car is traveling at 20 m/s (v₀). A pedestrian suddenly appears 25 meters ahead (d). The AEB system needs to determine the deceleration (a) required to stop in time. Calculation: We know the final velocity (v) must be 0 m/s to stop. Using v²=v₀²+2ad, we can rearrange to solve for a: a=(v2−​vo^2)/(2d) a=(0^2−20^2)/(2∗25) −400/50 =-8m/s² This means the AEB system needs to apply a deceleration of 8 m/s² to avoid a collision. Adaptive Cruise Control (ACC): Scenario: Your car is traveling at 30 m/s (v₀). The car ahead slows down, causing your radar to detect a relative acceleration of -2 m/s² (a). The system wants to calculate the distance (d) your car will travel in the next 3 seconds (t). Calculation: Using the equation d=Vo​t+1/2​at^2 d=(30∗3)+(0.5∗−2∗3^2) d=90+(−9) d=81 meters. The system calculates your car will travel 81 meters in that time frame. This information is used to adjust your car's speed to maintain a safe following distance. Time-to-Collision (TTC): Scenario: Your car is traveling at 15 m/s, and a car ahead is traveling at 10 m/s. The distance between them is 25 meters. Assuming the car ahead maintains its velocity. How much time until a collision? Calculation: Relative velocity = 15-10 = 5 m/s. TTC = distance / relative velocity. TTC = 25 / 5 = 5 seconds. Therefore, the time to collision is 5 seconds. If the car ahead were decelerating, then the "a" variable would be used to calculate a more accurate TTC. Key ADAS Points Sensors (radar, lidar, cameras) provide the initial data (position, velocity). ADAS algorithms use kinematic equations to: Predict future object positions. Calculate safe following distances. Determine necessary braking or steering actions. The accuracy of these calculations is critical for the reliable operation of ADAS. Disclaimer: This post is intended for educational purposes from a software development perspective. It does not cover complex non-linear vehicle dynamics.

561

12 comentários

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 comentários