Skip to content
0:00 / 0:00

#autosar#ecu#mcal

Introduction to AUTOSAR

Xsman

1.8K subscribers • 1 video on Hallway

YouTube
  • Recommended by 2 people: 2 in engineering communities.

Intermediate. Assumes working knowledge.

142K views10 years ago2 recommendations

Systems programmingSoftware designEmbedded systemsSoftware architecture

An in-depth lecture explaining the AUTOSAR standard, its architecture, and automotive software development.

The uploader added no description.

Why it's here

2 people recommend this

What people say. Recommended as a solid introductory resource for understanding the overall structure and elements of AUTOSAR.

u/KefasXin r/embedded • Recommends

On “What are the essential or fundamental things an Autosar Embedded developer must be knowing in order to be able to have systems level understanding?”

…he main four elements are communication/diagnostic/memory stacks and RTE. Here are some materials that might help: https://automotivetechis.files.wordpress.com/2012/05/lesson19\_autosar.pdf https://hpi.de/fileadmin/user\_upload/fachgebiete/giese/Ausarbeitungen\_AUTOSAR0809/CommunicationStack\_gosda.pdf Also this video is good for beginning: [video Then if you get familiar with overall structure I think it is good idea to dive into specific modules, documentation is freely available: https://www.autosar.org/standards/classic-platform/ But you can just type <module name> sws autosar and usually first link is the one you need. Eq. communication (depends what communication you use -…

u/DeCyborgin r/embedded • Recommends

On “Salary Automotive vs General Embedded systems”

…the ADC channels, pinmux etc... and perhaps some middle layer code for ECU abstractions \- Driver development per the autosar standards, this is likely the "best" since you get to write more code within autosar specs, however this is mostly carried out by the semiconductor vendors or whoever provides the MCAL This video should give you an idea: [video But in summary autosar was created by the OEMs to allow them to outsource most of their work and farm it out to several Tier1s, they do some high level block diagrams of their system and then in theory that would allow them to switch vendors as they please. **On "general embedded"** This varies a lot, would you be using an MCU? or an MPU…