Talking about cars, today we discuss automotive development technology!

I have previously written some articles mainly analyzing cars or the automotive industry, or sharing some automotive knowledge, but another area I really want to delve into, which also aligns with the positioning of this public account, is knowledge related to “automotive technology”. After all, we are talking about cars, discussing information, knowledge, and technology, but I have not been able to create the technology section. So I plan to start a collection of learning materials, sharing as I learn.RTOS and functional safety topics are all part of my plan, along with several other fields, to update them together.

Speaking of FreeRTOS, we must discuss why we should learn FreeRTOS. Isn’t the automotive industry using Autosar OS? Learning FreeRTOS seems to be going in the opposite direction, right?

Actually, that’s not the case. I initially thought the same way, but as I delved deeper, I realized the significance for us beginners: understanding FreeRTOS first makes it easier to grasp AUTOSAR OS later. I was initially conflicted about whether to learn AUTOSAR OS directly, but then I realized that FreeRTOS is the “foundation of real-time operating systems”. First, we need to understand concepts like “task scheduling” and “priority” in FreeRTOS, and then look at the functionalities of AUTOSAR OS. It should be like learning to drive a manual car before switching to an automatic one. Moreover, we will document our learning process on this public account, starting with FreeRTOS, and some modules in cars also use FreeRTOS, allowing beginners to follow along. When we later tackle more complex automotive technologies, we can discuss AUTOSAR OS then. Additionally, there is a wealth of publicly available information about FreeRTOS online, making it relatively easier to find solutions to any problems.

Of course, for the advancement of this collection, my ideal plan is to start with the code, analyzing the principles of the code based on the FreeRTOS manual, interspersing some understanding related to automotive industry development, with a focus on code interpretation, while also improving my personal code reading skills. Furthermore, I have noticed that there is relatively little interpretation of code available online, and I hope to keep updating this.

By following this collection, you will gain:

1. Improved C language code reading skills.
2. A “green pass” for in-depth learning of Autosar OS principles.
3. Analysis from the perspective of the automotive industry.
4. Acquaintance with an interesting blogger to learn together.
5. Continuous updates on the learning process of “functional safety”.

[Bosses, please give some attention ⬆]