CN116737117A - Model development method based on Autosar architecture - Google Patents
Model development method based on Autosar architecture Download PDFInfo
- Publication number
- CN116737117A CN116737117A CN202310632988.2A CN202310632988A CN116737117A CN 116737117 A CN116737117 A CN 116737117A CN 202310632988 A CN202310632988 A CN 202310632988A CN 116737117 A CN116737117 A CN 116737117A
- Authority
- CN
- China
- Prior art keywords
- autosar
- model
- configuration
- development method
- processor
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 39
- 238000011161 development Methods 0.000 title claims abstract description 33
- 238000013461 design Methods 0.000 claims abstract description 10
- 230000006870 function Effects 0.000 claims description 8
- 238000013507 mapping Methods 0.000 claims description 6
- 238000007639 printing Methods 0.000 claims description 3
- 238000012545 processing Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000005265 energy consumption Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002688 persistence Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/36—Software reuse
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The application relates to a model development method based on an Autosar architecture, which comprises the following steps: establishing a model by using a modeling tool; performing Autosar configuration on the model; generating an Arxml file and an Autosar code; and importing the Arxml file into an Autosar architecture management tool for runtime environment RTE design.
Description
Technical Field
The application relates to the field of vehicles, and more particularly to a model development method based on an Autosar architecture.
Background
An automotive open system architecture (Autosar) is an open standard software architecture that uses Run-Time Environment (RTE) and virtual bus technology to make the software complexity of an electronic control unit (electronic controlunit, ECU) controllable. Developers currently use Model-based design (MBD) methods to develop software, so that MBD design meets the Autosar specification and needs to meet the requirements of the Autosar Model (such as Interface and software running entity Runnable), and thus an Autosar architecture management tool is often used to manage a Model framework in combination with Arxml (xml file meeting the Autosar), which is divided into two different workflows: top-down and bottom-up. However, in both workflows, the developer is forced to manually configure a large amount of configurability work of the Autosar framework to enable the model to generate Autosar code and Arxml.
Disclosure of Invention
The application provides a model development method based on an Autosar architecture, a computer readable storage medium and a computing device.
According to a first aspect of the present application, there is provided a model development method based on an Autosar architecture. The model development method comprises the following steps: establishing a model by using a modeling tool; performing Autosar configuration on the model; generating an Arxml file and an Autosar code; and importing the Arxml file into an Autosar architecture management tool for runtime environment RTE design.
In some embodiments of the application, optionally, the Autosar configuring of the model further comprises: loading a first table, the first table comprising one or more of: software development function information, port interface information, configuration information, path information, software running entity information, and data type information.
In some embodiments of the application, optionally, the Autosar configuring of the model further comprises: the configuration API interface is invoked to set the configuration scheme of the model to an Autosar scheme.
In some embodiments of the application, optionally, the Autosar configuring of the model further comprises: the Autosar framework of the calling model configures the toolbox API interface to perform Autosar configuration according to the Autosar scheme required by the project.
In some embodiments of the application, optionally, the Autosar configuring of the model further comprises: and mapping the port of the model and the interface configured by Autosar.
In some embodiments of the application, optionally, the Autosar configuring of the model further comprises: configuration information of the model is automatically modified to enable the model to generate Autosar code.
In some embodiments of the application, optionally, the method further comprises: the steps of the Autosar configuration are synchronously printed to the command window.
In some embodiments of the application, the modeling tool optionally includes MATLAB/Simulink.
According to another aspect of the present application, a computer-readable storage medium having instructions stored therein is provided. The instructions, when executed by the processor, cause the processor to perform any of the model development methods as described above.
According to yet another aspect of the present application, a computing device is provided that includes a memory storing instructions and a processor. The instructions, when executed by the processor, cause the processor to perform any of the model development methods described above.
The application carries out automatic configuration aiming at the process of carrying out Autosar conversion on the model, improves the development and multiplexing efficiency of the model, saves a great deal of manual configuration work and reduces potential errors in the development process.
Drawings
The foregoing and/or other aspects and advantages of the present application will become more apparent and more readily appreciated from the following description of the various aspects taken in conjunction with the accompanying drawings in which like or similar elements are designated with the same reference numerals. In the drawings:
FIG. 1 illustrates a flow diagram of a method of model development based on an Autosar architecture in accordance with one or more embodiments of the application.
Detailed Description
Exemplary embodiments of the present application are described in detail below, examples of which are illustrated in the accompanying drawings. It should be noted that the following description is for the purposes of explanation and illustration and is not to be construed as limiting the application. Those skilled in the art may make electrical, mechanical, logical and structural changes in these embodiments as may be made in the practice without departing from the principles of the application without departing from the scope thereof. Furthermore, one skilled in the art will appreciate that one or more features of the different embodiments described below may be combined for any particular application scenario or actual need.
Terms such as "comprising" and "including" mean that in addition to having elements and steps that are directly and explicitly recited in the description, the inventive aspects also do not exclude the presence of other elements and steps not directly or explicitly recited.
In the following description, numerous specific details are set forth, such as examples of specific procedures, in order to provide a thorough understanding of the present application. Furthermore, in the following description and for purposes of explanation, specific nomenclature is set forth to provide a thorough understanding of the various aspects of the present application. However, it will be apparent to one skilled in the art that the example implementations may be practiced without these specific details.
The model development method 100 based on the Autosar architecture will be described below in conjunction with fig. 1. FIG. 1 illustrates a flow diagram of a model development method 100 based on an Autosar architecture in accordance with one or more embodiments of the application.
As shown in fig. 1, the model development method 100 based on the Autosar architecture includes steps S110 to S140. The automobile open system architecture Autosar may be divided into an application layer (AppL), a runtime environment RTE layer, a base software layer BSL, and a microcontroller layer. In the Autosar architecture, the software of the application layer is composed of a series of mutually interacted software components SWC, and in the design flow of automobile application software based on Autosar, the development of the software components is key, and the software components encapsulate the functional modules of an automobile electronic functional unit ECU, so that functions and corresponding function descriptions can be realized specifically. When developing application layer software, a developer uses a model-based design MBD method, and uses a modeling tool to develop the software in a mode of generating codes by using a model so as to test more environments in a early development stage of the software.
In step S110, a model is built using a modeling tool. For example, an algorithmic model of the developed software may be built in the Simulink and/or Stateflow of the MATLAB modeling tool. In a bottom-up development mode, for example, the building of the top layer of the model (model framework) is made to conform to the Autosar modeling specification, i.e. a function call (functionall) and a plurality of input-output interfaces.
In step S120, autosar configuration is performed on the model. For example, the Autosar framework configuration toolbox provided in the modeling tool of step S110 is used to perform related Autosar configurations on the built model, such as Interface (Interface) configuration, port (Port) configuration, software running entity (Runneable) function configuration, path (Path) configuration, and the like.
In some embodiments, the method 100 of the present application may enable automation of the above-described model framework configuration process. For example, the required Autosar configuration related information and files may be stored in a table (e.g., the sheet of EXCEL) after application layer model creation, which may be called and loaded, and typically includes information such as software development functions (such as information, names, and cycles of the software development functions), port interface information (e.g., inputs and outputs of the interface), configuration information, path information, software running entity information, and data type information. In this way, the developer can be facilitated to implement automation of some basic Autosar configurations. It will be appreciated that in other embodiments, information such as Runables, interface, dataType, port, path of all models may also be filled into Excel tables, processed using third party scripting language and generated into Arxml, which may be imported into both the modeling tool and the Autosar architecture management tool to similarly implement automated framework building.
In some embodiments, to, for example, cause the model development system to automatically generate Autosar code instead of ordinary embedded code, autosar configuring the model further includes invoking a configuration API (ApplicationProgrammingInterface) interface to set the configuration scheme of the model to an Autosar scheme. Further, in some examples, the Autosar framework configuration toolbox API interface of the model may be invoked to conduct Autosar configuration according to the Autosar scheme of the project requirements. Autosar schemas required by these projects, such as data element (DataElement) correlation rules, port naming correlation rules, and the like. Autosar configuration such as interface ports, software running entities, paths, enumeration types (CompuMethod) and the like as described above is performed.
In some embodiments, the Autosar configuring the model may further include mapping ports of the model with the Autosar configured interfaces described above. This may be, for example, the application of a Simulink-Autosar map editor, performing a Simulink-to-Autosar mapping in a SimulinkMappingview. For example, the model Port and Port, interface, data element (DataElement) in the Autosar configuration are mapped. According to the development flow of Autosar, a modeling tool such as MATLAB has the task of building a functional model and generating application software codes and model descriptive files in the application software development process, and MATLAB can generate codes compatible with the Autosar standard, also because a certain mapping relationship exists between MATLAB model elements and Autosar elements, such as a virtual subsystem of MATLAB can correspond to an atomic software component of Autosar, an atomic subsystem of MATLAB can correspond to a software running entity of Autosar (a triggered atomic subsystem of MATLAB can correspond to a software running entity activated by RTE time of Autosar), a Simulink port of MATLAB can correspond to an interface of a software component of Autosar, and the like. In this way, it can be ensured that the interface objects are set correctly, to further ensure that the code can be integrated correctly.
In this process, the configuration information of the model may also be automatically modified, so that the model can generate the Autosar code, i.e. the automatically loaded configuration information is modified for the case that the model configuration information is not adapted to the Autosar code generation.
In step S130, an Arxml file and Autosar code are generated. In this way, code and an Arxml file conforming to the Autosar architecture can be generated.
In some embodiments, the method may further include synchronously printing the steps of the Autosar configuration to a command window, for example, synchronously printing creation and mapping of interfaces and ports to the command window, so as to achieve synchronous persistence and display of the configuration process of the Autosar frame configuration.
In step S140, the Arxml file is imported into an Autosar architecture management tool for runtime environment RTE design. After generating the Autosar code and Arxml file that meet the Autosar specification, the Arxml file may be imported into an Autosar architecture management tool for further run-time environment RTE design for further algorithm model design and Autosar framework adaptation.
The method can automatically call the configuration information for carrying out Autosar configuration on the algorithm model, can convert the traditional model into the Autosar model by one key, can automatically configure Autosar information such as Runnable, interface, port, path, dataType of the model of which the framework accords with the Autosar standard in a modeling tool, improves the development efficiency of the model based on the Autosar, does not need to manually build the model framework, reduces the time and energy consumption of a large number of models for the automatic sar configuration under the conditions of more models and more interfaces, and improves the accuracy.
According to another aspect of the present application, there is provided a computer-readable storage medium having stored therein instructions, which when executed by a processor, cause the processor to perform any of the Autosar architecture-based model development methods 100 described above. Computer-readable media, as referred to herein, include any type of computer storage media which can be accessed by a general purpose or special purpose computer. By way of example, a computer-readable medium may comprise a RAM, ROM, EPROM, E PROM, register, hard disk, removable disk, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage device, or any other temporary or non-temporary medium that can be used to carry or store desired program code elements in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Disk, as used herein, typically replicates data magnetically, while disk replicates data optically with a laser. Combinations of the above should also be included within the scope of computer-readable media. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.
According to yet another aspect of the present application, an electronic device is provided. The electronic device includes a processor and a memory storing instructions that, when executed by the processor, perform the Autosar architecture-based model development method 100 described in any of the embodiments above. The memory and the processor may be connected by wire or wirelessly to enable transmission or interaction of data. For example, the components may be electrically connected to each other via one or more communication buses. The memory may be, for example, the computer readable storage medium described above. The processor may have a processing module with signal processing capability, such as a general-purpose processor, including a central processing unit CPU, a network processor NP, and the like; but may also be a digital signal processor DSP, an application specific integrated circuit ASIC, a field programmable gate array FPGA or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component.
The above is merely an embodiment of the present application, but the scope of the present application is not limited thereto. Other possible variations or substitutions will occur to those skilled in the art from the teachings disclosed herein and are intended to be within the scope of the present application. The embodiments of the present application and features in the embodiments may also be combined with each other without conflict. The protection scope of the present application is subject to the claims.
The embodiments and examples set forth herein are presented to best explain the embodiments consistent with the application and its particular application and to thereby enable those skilled in the art to make and use the application. However, those skilled in the art will recognize that the foregoing description and examples have been presented for the purpose of illustration and example only. The description as set forth is not intended to cover various aspects of the application or to limit the application to the precise form disclosed.
Claims (10)
1. The model development method based on the Autosar architecture is characterized by comprising the following steps of:
establishing a model by using a modeling tool;
performing Autosar configuration on the model;
generating an Arxml file and an Autosar code; and
and importing the Arxml file into an Autosar architecture management tool to perform run-time environment RTE design.
2. The model development method according to claim 1, wherein the Autosar configuring the model further comprises:
loading a first table, the first table comprising one or more of: software development function information, port interface information, configuration information, path information, software running entity information, and data type information.
3. The model development method according to claim 2, wherein the Autosar configuring the model further comprises:
the configuration API interface is invoked to set the configuration scheme of the model to an Autosar scheme.
4. The model development method according to claim 2, wherein the Autosar configuring the model further comprises:
and calling an Autosar framework configuration tool box API interface of the model to perform Autosar configuration according to an Autosar scheme required by the project.
5. The model development method according to claim 2, wherein the Autosar configuring the model further comprises:
and mapping the port of the model and the interface configured by the Autosar.
6. The model development method according to claim 1, wherein the Autosar configuring the model further comprises:
configuration information of a model is automatically modified to enable the model to generate the Autosar code.
7. The model development method according to claim 1, characterized in that the method further comprises:
and synchronously printing the steps of the Autosar configuration to a command window.
8. The model development method according to claim 1, wherein the modeling tool comprises MATLAB/Simulink.
9. A computer readable storage medium having instructions stored therein, which when executed by a processor, cause the processor to perform the model development method of any one of claims 1-8.
10. A computing device comprising a memory and a processor, the memory storing instructions that, when executed by the processor, cause the processor to perform the model development method of any one of claims 1-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310632988.2A CN116737117A (en) | 2023-05-31 | 2023-05-31 | Model development method based on Autosar architecture |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310632988.2A CN116737117A (en) | 2023-05-31 | 2023-05-31 | Model development method based on Autosar architecture |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116737117A true CN116737117A (en) | 2023-09-12 |
Family
ID=87912533
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310632988.2A Pending CN116737117A (en) | 2023-05-31 | 2023-05-31 | Model development method based on Autosar architecture |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116737117A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117331565A (en) * | 2023-10-09 | 2024-01-02 | 镁佳(北京)科技有限公司 | Software generation method, device, computer equipment and storage medium |
| CN117555553A (en) * | 2023-12-18 | 2024-02-13 | 上海烜翊科技有限公司 | Universal software protocol interface generation method and system based on autosar modeling |
-
2023
- 2023-05-31 CN CN202310632988.2A patent/CN116737117A/en active Pending
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN117331565A (en) * | 2023-10-09 | 2024-01-02 | 镁佳(北京)科技有限公司 | Software generation method, device, computer equipment and storage medium |
| CN117331565B (en) * | 2023-10-09 | 2024-05-28 | 镁佳(北京)科技有限公司 | Software generation method, device, computer equipment and storage medium |
| CN117555553A (en) * | 2023-12-18 | 2024-02-13 | 上海烜翊科技有限公司 | Universal software protocol interface generation method and system based on autosar modeling |
| CN117555553B (en) * | 2023-12-18 | 2024-05-28 | 上海烜翊科技有限公司 | Method and system for generating universal software protocol interface based on autosar modeling |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN116737117A (en) | Model development method based on Autosar architecture | |
| US10354031B2 (en) | Information processing by interpenetrating signal transmission channel in design for testability of chip | |
| US10817284B2 (en) | Melding of mediation flow service component architecture (SCA) components | |
| CN107885500B (en) | Runtime environment generation method oriented to AUTOSAR software architecture | |
| CN105912334A (en) | Internal behavior object code generation method of AUTOSAR software assembly | |
| CN113407362A (en) | SOMEIP communication intermediate layer implementation method and system based on SOA architecture of vehicle-mounted Android system | |
| CN116069648A (en) | Software testing method, system, equipment and storage medium | |
| KR20130138468A (en) | Apparatus and method for connecting application software and autosar service | |
| Di Natale et al. | An MDA approach for the generation of communication adapters integrating SW and FW components from Simulink | |
| CN111399816A (en) | Automobile ECU program file generation method and system, storage medium and terminal | |
| CN117131834A (en) | Chip design reorganization method, electronic equipment and medium | |
| CN116107669B (en) | Operator registration method, device and equipment of deep learning framework and storage medium | |
| Di Natale et al. | A Model-based approach for the synthesis of software to firmware adapters for use with automatically generated components | |
| CN116305877A (en) | Vehicle body control system development method and system based on simulation in foggy scene | |
| CN113971019A (en) | Data type creating method, device, server and medium | |
| US8135943B1 (en) | Method, apparatus, and computer-readable medium for generating a dispatching function | |
| Delic et al. | Validation of a SIL3 middleware for safety-related system-on-chips | |
| CN117331565B (en) | Software generation method, device, computer equipment and storage medium | |
| CN110414097A (en) | IMA system resource configuration verification method and system, computer readable storage medium | |
| CN116931916A (en) | Application layer software development method and device, computer equipment and storage medium | |
| JP2009110504A (en) | Method for integrating integrated circuit into standardized software architecture for embedded system | |
| Foss et al. | From uml to simulink: a graph grammar specification | |
| CN113342426A (en) | Application layer software component integration method and system | |
| Syed et al. | Automated Migration of Legacy Functions and Algorithms to Model Based Design | |
| CN110955423A (en) | Model design method, system, storage medium and terminal |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |