AUTOSAR development

Question

Is it possible to create an AUTOSAR BSW stack (for example, for CAN communications) based on the specifications presented on the website without buying any expensive supplier tool? What will be the steps that can be followed? I was asked to explore this opportunity.

Answer 1

Yes and no. Toolkit is a necessary part of the equation in AUTOSAR.

Assuming you work for a car supplier, you get a set of ECU configuration files (ECU extract?), Which is vaguely similar, but much more extensive than the various exchange formats for CAN messaging. This is usually a bunch of XML format files defined by the AUTOSAR consortium. A rather complex chain of “expensive provider tools” then converts this into something that code can generate. All specifications are open, so you can write your own tools in theory.

In addition to the tools, you will also need an OS that can be built on top of the open source OSEK system as a starting point. Then MCAL.

Can this be done ... Yes. If you work in a huge company (for example, Bosch), you may need to develop your own solution in the long run. But if you are working for a smaller supplier with a project deadline, you may have to bite the bullet and write a massive check. I hope this was taken into account when your company announced its work for a system based on AUTOSAR.

To give you an idea of ​​the scope of such an undertaking, it would be a bit like saying: "I am writing a cool game, do I need to use Windows, OSX or Linux, or can I write my own operating system too?" Well, maybe not so extreme, but much more difficult than writing your own RTOS and transport bus stacks (CAN, LIN, etc.). If you write your own RTOS + CAN stack, it sounds prohibitively complicated / complicated, don’t even think about it.

Obviously, I can’t make a decision for you, but if you accept opinions from random people on the Internet for unspecified qualifications, I would highly recommend against it as “my first auto-car”, but save it as a possible internal R&D project with possible long-term savings if you are a 50x automotive supplier that runs several auto projects every year. I doubt that you could build it less than it would be worth licensing all the time. But maybe 5-10 major road projects that he could pay.

Answer 2

You might want to take a look at COMASSO. It also provides development tools and BSW. https://www.comasso.org/

Answer 3

Take a look at the Swedish ICT MOPED project . We use it in our company projects . Relatively cheap to reproduce, since MOPED uses a raspberry Pi and easily accessible mechanical parts.

Answer 4

Full development of the BSW stack is a bit of work, after developing all the modules for stack integration that you must use for some tools and licensed compilers.

To meet QM and ASIL requirements, the stack owner must provide a list of compatible tool lists along with the entire stack. for example, for documentation of requirements, you have IBM Doors, for development, you have IBM Rhapsodhy or Enterprise architecture, configuration management tools such as IBM RTC. These are tools that meet the requirements and are listed in ISO26262. If you are only going to QM, you need to take the overhead to maintain and update all the documentation in excel or doc format, and this is normal if you cannot use these tools.

As for modules, such as OS, Comasso from Bosch is one of the options with some registration fees, you can get a basic OS level that works for your other modules. OS needs to be changed again according to the controller that you are going to use. OSEK-based Erica is another open source option that can be very useful if you are doing everything on Linux.

Later, MDT, PDF, and Vender parameter files appear, which are basic configurations. Perl is a widely used language for generating code / configuration code. In addition to all this, you should have a good knowledge of XML, since you do not need to spend configuration tools, in the background, XML should know that it changes all types of parameters. I saw some small vendors in Germany who make materials directly in XML, without using configuration TOOL.

The repository will not be an SVN issue that you can use for free.

But personally, I believe that all expensive tools are used for an individual independent system and stack maintenance. I saw small players who usually cannot spend on expensive tools, they also do a good business.

Answer 5

The clean piece of software is definitely yes! but what would you do with it if you don't have a stack with tools! This is a trick.

To be able to develop and sell the AUTOSAR BSW stack, you need to have it scalable for several configurations, this is only possible with the help of the tool part.

For your internal research and development, you can still develop software modules, their design and architecture, hard-coded configuration data in C and visualize configuration configurations using any open source xml tool. (The AUTOSAR schema is XML based)

PM me for more details