I want to know, what is it? An attempt to create a uniform software architecture/interface/tool landscape across different suppliers. Why it was made? So that company A can manufacture a piece of software that can either run on the ECU of company B or C without having to make big changes. To be able to buy a product from company E or F without having vendor lock-in. To be able to pawn off liability to other suppliers. Why it is still used? Because car manufacturers demand it to be used. If your product isn't using Autosar, they won't buy your product. Is it a library, framework or architecture? It's everything. There are specifications for common software components, their behavior and their interfaces. Specifications for the XML files that glue everything together. Specifications for toolchains. Specifications for compilers/linkers/linker files. Specifications for processes. And more. But with Autosar alone, you won't be able to fulfill everything, it's still a subset of what you need to do to build a product that car manufacturers can/will buy. It does help, though, because it guarantees a minimum standard. Is there anything similar in other industries? Not that I know of. More on reddit.com

Obligatory: https://www.reddit.com/r/embedded/s/UQnJIo2Why More on reddit.com

In 25 years, sadly, we've always done it manually. It's absurd. The Vivado IPI does help automate many of the issues (but has its own bullshit issues, like not working well in version control). And of course, its a AMD only solution. In Versal devices, we have the NOC (network on chip) where a lot of the interconnect is magically handled by the NOC so that's a little better. At various companies, I've seen instances of AUTO_INST type editor mode aids that automate connections which are widely used in system interconnect scenarios. That helps with the large number of AXI signals but is not a holistic solutioon/ Curious to see if there are any good tools (internal I would guess) from the ASIC people? More on reddit.com

Even traditional german automakers are kinda shifting away from Autosar. "Vehicle-OS" and "Sw defined vehicle" are the new buzzwords and Autosar group just fails to keep the pace, forcing the automakers go each on their own way. Autosar is still the tool that's used in small to medium ECUs but the functions that were once distributed all over the car in small/medium ECUs are getting more and more clustered in a set of central, powerful ECUs which currently run some sort of classic Autosar/Linux hybrid system. I never worked with Adaptive so no idea what it can do. Currently it looks like Autosar is losing ground even in traditional car-makers. This being said I think that Tesla started to externalize some ECUs to traditional Tier2 companies so they might push some Autosar ECUs in their cars :) The Chinese OEMs externalize lots of their ECUs so for sure they have some sort of Autosar in them. More on reddit.com