Even though AUTOSAR is open source to learn with Specs, it needs some puch and overview of basics. And these videos bridge that gap. Thank you for the team for all your effort and making it look so simple and intersting 😄
There is no receiver port, but there are three types of ports in Autosar: require port, provide port, or provide-require port. In Client-Server interface client is always having RPort and server will have PPort. In Sender-Receiver interface, sender will always have PPort and receiver will have RPort.
Difference betweeen synchronous and asynchronous server call points, is that when async, client will return back to execute code and will be notified with the result of requested operation via the callback, and when synchronous client will be blocked until receive result of the requested operation.
2:30 Motive of the WEBINAR
2:48 Agend
3:15 Why AUTOSAR?
4:41 AUTOSAR Layered Architecture
6:20 Application Layer and RTE
6:46 AUTOSAR Methodology
8:15 Application Software Component Development
11:12 Design and Communication of Software Components
13:56 SeatHeatingControl (Example)
17:03 SeatHeatingControl- Simplified (VFB Level)
21:16 AUTOSAR ASWC DEVELOPMENT STEPS/ Summary
22:57 Introduction of Artop
25:45 Creating SWC with Artop
Creating Application Software Component, Ports and Interfaces
40:34 Configuring Ports with Artop
41:52 Creating another SWC with Artop
44:41 RTE Configuration
Internal Behavior and Runnable Entity
1:01:54 SWC Implementation
1:06:54 Questions and Answers
Even though AUTOSAR is open source to learn with Specs, it needs some puch and overview of basics. And these videos bridge that gap. Thank you for the team for all your effort and making it look so simple and intersting 😄
There is no receiver port, but there are three types of ports in Autosar: require port, provide port, or provide-require port. In Client-Server interface client is always having RPort and server will have PPort. In Sender-Receiver interface, sender will always have PPort and receiver will have RPort.
Difference betweeen synchronous and asynchronous server call points, is that when async, client will return back to execute code and will be notified with the result of requested operation via the callback, and when synchronous client will be blocked until receive result of the requested operation.
marvelous session and genius explanation Sir. You have done a great job and brilliant way of teaching
What a wonderful session. I really appreciate Sir, the way you made the explaination so easy with examples and real experience
Thanks for the session, could you have another session on NVM SWC configuration?
Great Initiation Karthik ...
And Concepts well explained
That's really great
Could you please do session on DCM and DEM Configurations.
Well explained. Congrats!
When are data send by argument and data receive by argument used?
Thank you so much for the great presentation
Do you skip modeling via ARText by intention?
Great work sir !..thnk you ❤️
Can you suggest any course to be autosar developer?
where do I find the next webinar mentioned at the end of the video?
Good job!
What is software sharing adapter
how to extract .c file
How does data flow from ASWC to MCAL layer
If i am not wrong, com stack handles it with the help of RTE
artop?