Experience with Autosar development tools and techniques

Question

Does anyone know where to find a description of how to develop Autosar software for an embedded controller to explain all the steps and tools? Are some of these development tools available for free use (for example, for students)? What Autosar development software providers exist and how is experience working with each development software?

Answer 1

This answer is based on my recent experience developing two automotive controllers using AUTOSAR OS. The best description of how to get ahead with AUTOSAR development probably comes from various tool providers, as the tools are quite complex. I do not know the final guide. But, in general, the main steps are:

1) An architect / project application that will work on the controller using AUTOSAR constructs. In AUTOSAR, for example, the basic RTOS constructs are available, but with slightly different terminology than many other RTOS. In the most basic AUTOSAR application, a Task object will be defined to execute the body of each formal state machine from your project. Alarm objects are equivalent to timers, and Resource objects are equivalent to Mutexes / Binary Semaphores. In general, you will want to minimize the use of Resource objects to reduce the likelihood of priority inversion. Rate Monotonic Schedulability Analysis is a good way to set the right priorities for your tasks (although the execution time for tasks can be difficult to estimate at the beginning of the design cycle).

2) Use the AUTOSAR tools from the selected provider to create the application according to your design. In AUTOSAR, the configuration of your application is stored in XML format, which is theoretically ported through AUTOSAR tools from different vendors.

3) Create an application structure using tools. The result of this step is the actual AURTOSAR runtime (in the form of source or object code, depending on how much you paid for your license) and the skeleton of your actual application (for example, empty objects of the Task and ISR functions). A good AUTOSAR toolkit will generate highly optimized code for the real AUTOSAR environment, excluding code for functions that your application does not use.

4) Keep the body of your application in C using the skeleton code you created in the previous step.

5) Build, debug, test and deploy your application using the appropriate tool chain for your controller hardware. The main tool chain for your microcontroller is independent of AUTOSAR tools. Debugging a complex application will be easier if you have a full source license for the AIUTOSAR environment.

I don’t know any free AUTOSAR tools, but I suspect that you could discuss lower prices for academic use. The sellers I'm familiar with are Vector, Electrobit, and ETAS. All of their tools are quite expensive, of the order of $ 10K to $ 50K for just AUTOSAR OS, not including CAN communication protocol protocols, which cost even more.

Answer 2

I suggest taking a look at http://arccore.com/ . Their autosar firmware is open source. To configure the autosar application, you need to purchase the configuration tools, but if you want to evaluate them, you can request a trial license. Hope this helps you.

Answer 3

There is a free openOS platform for AUTOSAR, which is artop .

But be honest, the tool is not able to use (at least for me). If you are not familiar with the AUTOSAR standard and EMF, a model-based development concept, you cannot do anything with this tool.

The most significant tool manufacturer is all of Germany, maybe one or two from Sweden or Sweden.

For the main software configuration tool. There is a company like Vector, which is always a market leader, and EB, whose headquarters are in Finland. Product - Davinci Configurator. and Tresos.

For SW architecture architecture, there is Davinci Configurator from vector and SystemDesk from Dspace.

If you do not know about the AUTOSAR architecture, I recommend that you read this document .

Answer 4

Another version of the open source AUTOSAR platform is available, as if it were not completely free, check this out

https://www.comasso.org/

Let me know if you have any questions.

Answer 5

As already mentioned, using Autosar projects is much more complicated. One of the most important assumptions was to reuse as much code as possible, as well as reduce the number of developers. In fact, auto projects sometimes even consume two or more people than without.

But the reason for its popularity is because Automakers just want it because they trust Autosar's assumptions.

When you need Autosar for a student project, I think you can try contacting AUTOSAR sellers and ask them if they can provide something accurate. (there are evaluation or non-production prototypes)

I saw the Autosar Tool Master Thesis, which covered the Autosar tool. Thus, it is possible that suppliers can provide some kind of answer for student projects.

AUTOSAR Webpage: https://www.autosar.org/

Vector also has a lot of AUTOSAR stuff. https://vector.com/vi_microsar_en.html