Based on official arc-stable-9c57d86f66be, AUTOSAR version 3.1.5
fundamental issue
The code organization in Arctic Core has a lot to be improved. Here are a few points:
1. The header file reference is confusing, all header files are referenced from the search path (-I) , there is a problem of name pollution, and path information needs to be added;
2. Whether the code files in the compilation system are compiled and the target files are centrally defined in boards/board_common.mk instead of belonging to their respective modules;
3. All code files in the compilation system are searched through the search path ( VPATH ), there is a problem of name pollution, and path information needs to be added;
4. The module switch macros CFG_% and USE_% are mixed in the compilation system ;
5. The module switch macros in the compilation system are scattered in multiple Makefiles , and should be configured in a top-level Makefile , such as .config ;
6. Relative paths are often used for path references in the compilation system, coupled with make -C transformation, it is easy to get confused;
7. The MAKE_LEVEL variable is used in the compilation system to distinguish the reference level, which is too complicated and can be simplified;
In addition, there is a problem of unclear division of AUTOSAR .
8. Although MCAL in AUTOSAR contains various drviers , after all, it is AL , the abstraction layer, and should not contain architecture and device -specific information. Should only contain model definitions, no implementation details.