CN112631594A - Hardware system development method, equipment and computer readable storage medium - Google Patents
Hardware system development method, equipment and computer readable storage medium Download PDFInfo
- Publication number
- CN112631594A CN112631594A CN201910905539.4A CN201910905539A CN112631594A CN 112631594 A CN112631594 A CN 112631594A CN 201910905539 A CN201910905539 A CN 201910905539A CN 112631594 A CN112631594 A CN 112631594A
- Authority
- CN
- China
- Prior art keywords
- bottom layer
- file
- code
- hardware
- matlab
- 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 70
- 230000033772 system development Effects 0.000 title claims abstract description 47
- 238000012360 testing method Methods 0.000 claims abstract description 81
- 238000004088 simulation Methods 0.000 claims abstract description 50
- 238000011161 development Methods 0.000 claims abstract description 46
- 230000018109 developmental process Effects 0.000 claims abstract description 46
- 238000004806 packaging method and process Methods 0.000 claims description 31
- 238000004590 computer program Methods 0.000 claims description 11
- 238000005538 encapsulation Methods 0.000 claims description 3
- 238000010276 construction Methods 0.000 claims 1
- 230000000007 visual effect Effects 0.000 abstract description 5
- 239000010410 layer Substances 0.000 description 159
- 230000010354 integration Effects 0.000 description 7
- 238000010586 diagram Methods 0.000 description 6
- 239000002346 layers by function Substances 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000006870 function Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000013101 initial test Methods 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000013024 troubleshooting Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
- G06F8/44—Encoding
- G06F8/447—Target code generation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2205—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing using arrangements specific to the hardware being tested
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2273—Test methods
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Prevention of errors by analysis, debugging or testing of software
- G06F11/3668—Testing of software
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
- G06F8/63—Image based installation; Cloning; Build to order
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Software Systems (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides a hardware system development method, equipment and a computer readable storage medium, wherein the method comprises the following steps: adding the packaged bottom layer code to an application layer in a Matlab system to obtain a system file; testing the system file in a Matlab system; after the test is qualified, downloading the system file to a hardware development board to obtain a hardware system; and debugging the hardware system. Therefore, the main process of hardware system development is completed in the Matlab system, bottom layer testing and application layer combination can be directly performed in the Matlab system, joint simulation is performed, then codes are generated by one key, and the codes are burned into a hardware development board, so that visual debugging can be performed in the Maltab environment by using debugging equipment, and joint debugging of the Matlab system and the whole project is realized.
Description
Technical Field
The present invention relates to the field of hardware bottom layer development, and in particular, to a hardware system development method, device, and computer-readable storage medium.
Background
In the existing hardware system development scheme, an application layer is developed in a Matlab system, modeling, simulation and function realization are performed on the application layer, codes corresponding to the application layer are generated and integrated into a C system project containing bottom codes, then the system codes are compiled uniformly, then the system codes are programmed into a hardware development board, and finally, debugging equipment is used for debugging the system of the hardware development board.
However, in the existing hardware system development scheme, the problem of the application layer can be found only in the debugging process after the system file is written into the hardware development board, and the debugging and modifying process is complicated.
Disclosure of Invention
The embodiment of the invention provides a hardware system development method, hardware system development equipment and a computer readable storage medium, and aims to solve the technical problem that the existing model development scheme is complicated in debugging and modifying processes.
In order to achieve the purpose, the invention provides the following specific scheme:
in a first aspect, an embodiment of the present invention provides a hardware system development method, where the method includes:
adding the packaged bottom layer code to an application layer in a Matlab system to obtain a system file;
testing the system file in a Matlab system;
after the test is qualified, downloading the system file to a hardware development board to obtain a hardware system;
and debugging the hardware system.
Optionally, before the step of adding the encapsulated underlying code to the application layer, the method further includes:
acquiring the pre-developed bottom layer code;
testing the bottom layer code;
and packaging the bottom layer code after the test is qualified.
Optionally, the step of encapsulating the underlying code includes at least one of:
packaging the bottom layer code into a target language editor format;
packaging the bottom layer code into an executable file format;
and after the bottom layer codes are packaged into the target language editor format, packaging the code file of the target language editor format into the executable file format.
Optionally, the step of adding the encapsulated bottom layer code to the application layer to obtain the system file includes:
adding the packaged bottom layer code into a library file of the Matlab system;
and adding the bottom layer code in the library file to the application layer to obtain the system file.
Optionally, before the step of adding the underlying code in the library file to an application layer, the method further includes:
constructing an application layer model in the Matlab system;
the step of adding the bottom layer code in the library file to an application layer to obtain a system file comprises the following steps:
and loading the bottom layer code to the application layer model to obtain the system file.
Optionally, the step of testing the system file in the Matlab system includes:
performing combined simulation of the application layer and the bottom layer in a Matlab system by using the system file to obtain a simulation model of the system file;
carrying out simulation test on the simulation model;
and if the simulation test is passed, judging that the test is qualified.
Optionally, after the step of debugging the system corresponding to the system file on the hardware development board, the method further includes:
and outputting debugging data of the system aiming at the hardware development board in the Matlab system.
In a second aspect, an embodiment of the present invention further provides a hardware system development device, including:
the adding module is used for adding the packaged bottom layer code to an application layer in the Matlab system to obtain a system file;
the first testing module is used for testing the system file in the Matlab system;
the downloading module is used for downloading the system file to a hardware development board to obtain a hardware system after the test is qualified;
and the debugging module is used for debugging the hardware system.
Optionally, the apparatus further comprises:
the acquisition module is used for acquiring a pre-developed bottom code;
the second testing module is used for testing the bottom layer code;
and the packaging module is used for packaging the bottom layer code after the test is qualified.
Optionally, the encapsulation module is configured to implement at least one of the following steps:
packaging the bottom layer code into a target language editor format;
packaging the bottom layer code into an executable file format;
and after the bottom layer codes are packaged into a target language editor format, packaging the code files of the target language editor format into an executable file format.
Optionally, the adding module is configured to:
adding the packaged bottom layer code into a library file of the hardware development system;
and adding the bottom layer code in the library file to the application layer to obtain the system file.
Optionally, the apparatus further comprises:
the building module is used for building an application layer model in the hardware development system;
the adding module is used for:
and loading the bottom layer code to the application layer model to obtain the system file.
Optionally, the apparatus further comprises:
the simulation module is used for carrying out combined simulation on an application layer and a bottom layer by utilizing the system file to obtain a simulation model of the system;
the first test module is configured to:
carrying out simulation test on the simulation model;
and if the simulation test is passed, judging that the test is qualified.
Optionally, the apparatus further comprises:
and the output module is used for outputting debugging data aiming at the system of the hardware development board in the hardware development system.
In a third aspect, an embodiment of the present invention further provides a hardware system development device, which includes a transceiver, a bus interface, a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor implements the hardware system development method according to any one of the first aspect when executing the computer program.
In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the steps of the hardware system development method according to the first aspect.
In the embodiment of the invention, the system file can be obtained and tested by adding the packaged bottom layer code to the application layer in the Matlab system, and the hardware system can be debugged by downloading the system file which is qualified in the test to the hardware development board to obtain the hardware system. Therefore, the main process of hardware system development is completed in the Matlab system, bottom layer testing and application layer combination can be directly performed in the Matlab system, joint simulation is performed, then codes are generated by one key, and the codes are burned into a hardware development board, so that visual debugging can be performed in the Maltab environment by using debugging equipment, and joint debugging of the Matlab system and the whole project is realized.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments of the present invention will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without inventive exercise.
Fig. 1 is a schematic flowchart of a hardware system development method according to an embodiment of the present invention;
FIG. 2 is a partial flow chart of another hardware system development method according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram of a hardware system development device according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of another hardware system development device according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of another hardware system development device according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of another hardware system development device according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Referring to fig. 1, fig. 1 is a schematic flowchart of a hardware system development method according to an embodiment of the present invention. As shown in fig. 1, the hardware system development method mainly includes the following steps:
the hardware system development method provided by the embodiment of the invention is applied to hardware system development equipment (hereinafter referred to as equipment) with a hardware system development function, and the hardware system development equipment is provided with a Matlab system. The device can be an electronic device such as a server and a terminal. The steps of the hardware system development method provided by this embodiment are all performed in the Matlab system.
When the method is implemented specifically, firstly, the packaged bottom layer code is obtained, and the packaged bottom layer code is added to the application layer, so that the system file corresponding to the hardware system can be obtained, wherein the system file at least comprises the bottom layer code and the application layer code corresponding to the hardware system.
102, testing the system file in a Matlab system;
the device obtains the system file corresponding to the hardware system according to the steps, namely, the system file can be tested in the Matlab system, namely, the bottom layer and the application layer are simultaneously tested, and whether the operation of each functional layer and the cooperation between the functional layers are normal is tested.
If the bottom layer or the application layer has problems in the test process, the test device can directly return to the bottom layer or the application layer with problems for modification, and real-time test and feedback are realized.
103, downloading the system file to a hardware development board after the test is qualified to obtain a hardware system;
if the test is qualified, the process of writing into the board card can be executed. And downloading the system file to a hardware development board to obtain a hardware system, and operating a system corresponding to the system file on the hardware development board through operations such as compiling and the like.
And 104, debugging the hardware system.
And downloading the system file on the hardware development board according to the steps, and compiling to debug the obtained hardware system.
Optionally, after the step of debugging the hardware system, the method further includes:
and outputting debugging data of a hardware system aiming at the hardware development board in the Matlab system.
When a system on a hardware development board is debugged, the Matlab system can directly output debugging data according to real-time communication, and a user can directly observe values and running paths aiming at the inside of each module in the Matlab system, so that specific conditions and problem nodes in the debugging process can be more visually checked, and the problem troubleshooting time is shortened.
In the hardware system development method provided by the embodiment of the present invention, the system file can be obtained and tested by adding the encapsulated bottom layer code to the application layer in the Matlab system, and the system file that is qualified after the test is downloaded to the hardware development board, so that the system implemented on the hardware development board can be debugged. Therefore, the main process of hardware system development is completed in the Matlab system, bottom layer testing and application layer combination can be directly performed in the Matlab system, joint simulation is performed, then codes are generated by one key, and the codes are burned into a hardware development board, so that visual debugging can be performed in the Maltab environment by using debugging equipment, and joint debugging of the Matlab and the whole project is realized.
On the basis of the foregoing embodiment, as shown in fig. 2, before the step of adding the encapsulated underlying code to the application layer in step 101, the method may further include:
the underlying code refers to the most primitive, basic code used to support the system, and the implementation code of the system framework is written using an underlying development language, such as C or assembly language. When a system is built, a user needs to develop a bottom layer code for realizing a system framework in a C language environment or an assembly language environment in advance.
after the bottom layer code is compiled according to the steps, the compiled bottom layer code needs to be tested to verify whether a system framework can be realized, so that an error program or an unreasonable operation flow and the like can be found in time, rework adjustment is carried out in time, the number of errors in the subsequent integration and paper burning program process is reduced, the development efficiency is improved, and the rework rate is reduced.
And 203, packaging the bottom layer code after the test is qualified.
And obtaining the bottom code qualified in the test according to the steps, and packaging the bottom code. The code encapsulation is to hide the implementation details of classes and only reserve interfaces, so that the underlying code is classified, visible and transparent. And the coupling degree can be reduced by encapsulating the bottom layer code, and the inquiry, the call and the update are facilitated.
Optionally, in step 203, the step of encapsulating the underlying code includes at least one of:
packaging the bottom layer code into a Target Language logic (TLC for short) format;
packaging the bottom layer code into an Executable File (EXE) format;
and after the bottom layer code is packaged into the target language logic, packaging the code file of the target language logic into an executable file.
The device uses Matlab language, and can directly package the bottom layer code containing the bottom layer driver and other bottom layer modules into TLC format to be added on the application layer. Certainly, the underlying code can also be encapsulated into an EXE format, and the file in the EXE format can avoid other users from directly acquiring the source code in the file, so as to reduce the risk of copying the underlying source code. In the embodiment, the bottom layer code is preferably packaged into a TLC format capable of directly adding integration, and then the code file in the TLC format is directly packaged into an EXE format, so that the risk of reverse copying is reduced, and the security and confidentiality are improved.
Specifically, in step 101, adding the encapsulated bottom layer code to the application layer to obtain a system file, which may include:
adding the packaged bottom layer code into a library file of the Matlab system;
and adding the bottom layer code in the library file to the application layer to obtain the system file.
And installing the packaged bottom layer code into a Matlab system, wherein the Matlab system can rotate to add the packaged Library file containing the bottom layer code file into the Library file of the Library. Subsequently, when the bottom layer code file is integrated into the application layer, the library file containing the bottom layer code file can be directly called in Matlab, the complicated operation of performing code integration on the C code generated by the application layer is not needed, the code integration process is simplified, and the debugging visibility and the positioning accuracy are improved.
In addition, as described in step 101, before adding the underlying code in the library file to the application layer, the method may further include:
constructing an application layer model in the Matlab system;
correspondingly, in step 101, the step of adding the bottom layer code in the library file to the application layer to obtain the system file may include:
and loading the bottom layer code to the application layer model to obtain the system file.
The device models an application layer developed in the Matlab system according to a strategy and an algorithm in the Matlab system, constructs an application layer model, finds a bottom layer code in a Library file of Library and loads the bottom layer code to the application layer model. The joint debugging of the application layer and the bottom layer is directly carried out in the Matlab development environment, the operation is simple and convenient, the integrated debugging visibility is higher, the positioning problem efficiency is higher, the system development efficiency is improved, the development period is shortened, and the performance of a development system is improved.
In another embodiment, the step 102 of testing the system file may include:
performing combined simulation of the application layer and the bottom layer in a Matlab system by using the system file to obtain a simulation model of the system file;
carrying out simulation test on the simulation model;
and if the simulation test is passed, judging that the test is qualified.
In this embodiment, the device performs joint simulation on the bottom layer and the application layer to obtain a simulation model of the corresponding system, and performs simulation test on the simulation model, so as to directly detect whether the bottom layer and the application layer still have problems. If the problem of the bottom layer or the application layer is found, the corresponding functional layer can be directly returned to for adjustment.
It should be noted that, if the adjustment needs to be performed on the bottom layer or the application layer after the simulation test, the adjusted bottom layer code needs to be repackaged, and/or the repackaged bottom layer code needs to be added to the adjusted application layer. The process only needs to update the partial data, the workload is low, and the problems possibly occurring in the later hardware system debugging process can be effectively reduced.
In addition, if a problem occurs during debugging of the system on the hardware development board, the system also needs to go back to the bottom layer or the application layer for code modification, so that the subsequent packaging and integration processes also need to be executed again. The code is only updated in the process, and the workload is relatively small. Moreover, because more problems are solved in the early initial test and simulation test processes, the workload in the later debugging process is correspondingly reduced.
In the hardware system development method provided by the embodiment of the invention, the drive module related to the bottom layer is added in the Matlab, so that joint debugging of the application layer and the bottom layer can be conveniently performed in the development environment of the Matlab, the software integration work is simplified, the integration debugging becomes higher in visibility, and the positioning problem efficiency is higher.
Referring to fig. 3, fig. 3 is a schematic structural diagram of a hardware system development device according to an embodiment of the present invention. As shown in fig. 3, the apparatus 300 mainly includes:
an adding module 301, configured to add the encapsulated bottom layer code to an application layer in a Matlab system to obtain a system file;
a first testing module 302, configured to test the system file in a Matlab system;
the downloading module 303 is configured to download the system file to a hardware development board after the test is qualified, so as to obtain a hardware system;
and the debugging module 304 is used for debugging the hardware system.
Optionally, as shown in fig. 4, the apparatus 300 further includes:
an obtaining module 305, configured to obtain a pre-developed underlying code;
a second testing module 306, configured to test the underlying code;
and the encapsulating module 307 is configured to encapsulate the bottom layer code after the test is qualified.
Optionally, the encapsulating module 307 is configured to implement at least one of the following steps:
packaging the bottom layer code into a target language editor format;
packaging the bottom layer code into an executable file format;
and after the bottom layer codes are packaged into a target language editor format, packaging the code files of the target language editor format into an executable file format.
Optionally, the adding module 301 is configured to:
adding the packaged bottom layer code into a library file of the Matlab system;
and adding the bottom layer code in the library file to the application layer to obtain the system file.
Optionally, as shown in fig. 4, the apparatus 300 may further include:
a building module 308, configured to build an application layer model in the Matlab system;
the adding module 301 is configured to:
and loading the bottom layer code to the application layer model to obtain the system file.
Optionally, as shown in fig. 5, the apparatus 300 may further include:
the simulation module 309 is configured to perform joint simulation on the application layer and the bottom layer by using the system file to obtain a simulation model of the system;
the first test module 302 is used for
Carrying out simulation test on the simulation model;
and if the simulation test is passed, judging that the test is qualified.
Optionally, as shown in fig. 5, the apparatus 300 may further include:
an output module 310, configured to output, in the Matlab system, debugging data of the system for the hardware development board.
In the hardware system development device provided by the embodiment of the present invention, the system file can be obtained and tested by adding the encapsulated bottom layer code to the application layer in the Matlab system, and the hardware system can be debugged by downloading the system file after the test is qualified to the hardware development board to obtain the hardware system. Therefore, the main process of hardware system development is completed in the Matlab system, bottom layer testing and application layer combination can be directly performed in the Matlab system, joint simulation is performed, then codes are generated by one key, and the codes are burned into a hardware development board, so that visual debugging can be performed in the Maltab environment by using debugging equipment, and joint debugging of the Matlab and the whole project is realized. The specific implementation process of the hardware system development device provided by the embodiment of the present invention may refer to the specific implementation process of the hardware system development method shown in fig. 1 and fig. 2, and is not described in detail herein.
Referring to fig. 6, fig. 6 is a structural diagram of a hardware system development device according to an embodiment of the present invention, and as shown in fig. 6, the hardware system development device 600 includes: transceiver 601, bus interface and processor 602, wherein:
the processor 602 is configured to add the encapsulated bottom layer code to an application layer in a Matlab system to obtain a system file, and test the system file;
the transceiver 601 is configured to download the system file to a hardware development board after the test is qualified, so as to obtain a hardware system;
the processor 602 is further configured to: and debugging the hardware system.
Optionally, the transceiver 601 is further configured to:
acquiring a bottom layer code developed in advance;
the processor 602 is further configured to:
testing the bottom layer code;
and packaging the bottom layer code after the test is qualified.
Optionally, the processor 602 is further configured to perform at least one of the following:
packaging the bottom layer code into a target language editing format;
packaging the bottom layer code into an executable file format;
and after the bottom layer codes are packaged into the target language editing format, packaging the code file in the target language editor format into the executable file format.
Optionally, the processor 602 is further configured to:
adding the packaged bottom layer code into a library file of the Matlab system;
and adding the bottom layer code in the library file to the application layer to obtain the system file.
Optionally, the processor 602 is further configured to:
constructing an application layer model in the Matlab system;
and loading the bottom layer code to the application layer model to obtain the system file.
Optionally, the processor 602 is further configured to:
performing combined simulation of the application layer and the bottom layer in a Matlab system by using the system file to obtain a simulation model of the system file;
carrying out simulation test on the simulation model;
and if the simulation test is passed, judging that the test is qualified.
Optionally, the processor 602 is further configured to:
and outputting debugging data of the system aiming at the hardware development board in the Matlab system.
In this embodiment of the present invention, the server 600 further includes: a memory 603. In FIG. 6, the bus architecture may include any number of interconnected buses and bridges, with one or more processors represented by processor 602 and various circuits of memory represented by memory 603 linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 601 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium. The processor 602 is responsible for managing the bus architecture and general processing, and the memory 603 may store data used by the processor 602 in performing operations.
The hardware system development device 600 provided by the embodiment of the present invention can obtain and test a system file by adding the encapsulated bottom layer code to the application layer in the Matlab system, and debug a system implemented on the hardware development board by downloading the system file that is qualified after the test onto the hardware development board. Therefore, the main process of hardware system development is completed in the Matlab system, bottom layer testing and application layer combination can be directly performed in the Matlab system, joint simulation is performed, then codes are generated by one key, and the codes are burned into a hardware development board, so that visual debugging can be performed in the Maltab environment by using debugging equipment, and joint debugging of the Matlab and the whole project is realized. The embodiment of the present invention may execute the steps that the server in the above method embodiments may execute, and details are not described again.
The embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements each process of the embodiment of the hardware system development method, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.
While the present invention has been described with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, which are illustrative and not restrictive, and it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the invention as defined in the appended claims.
Claims (16)
1. A method for hardware system development, the method comprising:
adding the packaged bottom layer code to an application layer in a Matlab system to obtain a system file;
testing the system file in a Matlab system;
after the test is qualified, downloading the system file to a hardware development board to obtain a hardware system;
and debugging the hardware system.
2. The method of claim 1, wherein prior to the step of adding the encapsulated underlying code to the application layer, the method further comprises:
acquiring the pre-developed bottom layer code;
testing the bottom layer code;
and packaging the bottom layer code after the test is qualified.
3. The method of claim 2, wherein the step of encapsulating the underlying code comprises at least one of:
packaging the bottom layer code into a target language editing format;
packaging the bottom layer code into an executable file format;
and after the bottom layer codes are packaged into the target language editing format, packaging the code file in the target language editor format into the executable file format.
4. The method of claim 1, wherein the step of adding the encapsulated underlying code to the application layer to obtain the system file comprises:
adding the packaged bottom layer code into a library file of the Matlab system;
and adding the bottom layer code in the library file to the application layer to obtain the system file.
5. The method of claim 4, wherein prior to the step of adding the underlying code in the library file to an application layer, the method further comprises:
constructing an application layer model in the Matlab system;
the step of adding the bottom layer code in the library file to an application layer to obtain a system file comprises the following steps:
and loading the bottom layer code to the application layer model to obtain the system file.
6. The method of claim 5, wherein the step of testing the system file in the Matlab system comprises:
performing combined simulation of the application layer and the bottom layer in a Matlab system by using the system file to obtain a simulation model of the system file;
carrying out simulation test on the simulation model;
and if the simulation test is passed, judging that the test is qualified.
7. The method of claim 6, wherein after the step of debugging the hardware system, the method further comprises:
and outputting debugging data of the system aiming at the hardware development board in the Matlab system.
8. A hardware system development device, comprising:
the adding module is used for adding the packaged bottom layer code to an application layer in the Matlab system to obtain a system file;
the first testing module is used for testing the system file in the Matlab system;
the downloading module is used for downloading the system file to a hardware development board to obtain a hardware system after the test is qualified;
and the debugging module is used for debugging the hardware system.
9. The apparatus of claim 8, further comprising:
the acquisition module is used for acquiring the pre-developed bottom layer code;
the second testing module is used for testing the bottom layer code;
and the packaging module is used for packaging the bottom layer code after the test is qualified.
10. The apparatus of claim 9, wherein the encapsulation module is configured to implement at least one of:
packaging the bottom layer code into a target language editor format;
packaging the bottom layer code into an executable file format;
and after the bottom layer codes are packaged into a target language editor format, packaging the code files of the target language editor format into an executable file format.
11. The apparatus of claim 8, wherein the adding module is configured to:
adding the packaged bottom layer code into a library file of the Matlab system;
and adding the bottom layer code in the library file to the application layer to obtain the system file.
12. The apparatus of claim 11, further comprising:
the construction module is used for constructing an application layer model in the Matlab system;
the adding module is used for:
and loading the bottom layer code to the application layer model to obtain the system file.
13. The apparatus of claim 11, further comprising:
the simulation module is used for performing combined simulation on the application layer and the bottom layer by using the system file to obtain a simulation model of the system;
the first test module is configured to:
carrying out simulation test on the simulation model;
and if the simulation test is passed, judging that the test is qualified.
14. The apparatus of claim 13, further comprising:
and the output module is used for outputting debugging data of the system aiming at the hardware development board in the Matlab system.
15. A hardware system development device comprising a transceiver, a bus interface, a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the hardware system development method of any one of claims 1 to 7 when executing the computer program.
16. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, carries out the steps of the hardware system development method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910905539.4A CN112631594A (en) | 2019-09-24 | 2019-09-24 | Hardware system development method, equipment and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910905539.4A CN112631594A (en) | 2019-09-24 | 2019-09-24 | Hardware system development method, equipment and computer readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112631594A true CN112631594A (en) | 2021-04-09 |
Family
ID=75282652
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910905539.4A Pending CN112631594A (en) | 2019-09-24 | 2019-09-24 | Hardware system development method, equipment and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112631594A (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070192076A1 (en) * | 2004-03-10 | 2007-08-16 | Renault S.A.S | Validation method for embedded systems |
| CN102200913A (en) * | 2011-06-20 | 2011-09-28 | 奇瑞汽车股份有限公司 | Layered design method of model-based automatic transmission software development platform |
| CN106055351A (en) * | 2016-05-20 | 2016-10-26 | 北京经纬恒润科技有限公司 | Development method and apparatus of control system |
| CN108415699A (en) * | 2018-02-12 | 2018-08-17 | 北京智行鸿远汽车有限公司 | The method that the bottom layer driving of microcontroller carries out code building is customized using Simulink |
-
2019
- 2019-09-24 CN CN201910905539.4A patent/CN112631594A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070192076A1 (en) * | 2004-03-10 | 2007-08-16 | Renault S.A.S | Validation method for embedded systems |
| CN102200913A (en) * | 2011-06-20 | 2011-09-28 | 奇瑞汽车股份有限公司 | Layered design method of model-based automatic transmission software development platform |
| CN106055351A (en) * | 2016-05-20 | 2016-10-26 | 北京经纬恒润科技有限公司 | Development method and apparatus of control system |
| CN108415699A (en) * | 2018-02-12 | 2018-08-17 | 北京智行鸿远汽车有限公司 | The method that the bottom layer driving of microcontroller carries out code building is customized using Simulink |
Non-Patent Citations (2)
| Title |
|---|
| 潘志前: "基于AUTOSAR架构的电动汽车VCU软件功能设计", 国防制造技术, no. 1, 30 March 2019 (2019-03-30), pages 36 - 39 * |
| 蔡潇扬 等: "基于Simulink的电动客车整车控制器软件层设计", 重庆理工大学学报(自然科学), vol. 32, no. 06, 15 June 2018 (2018-06-15), pages 14 - 20 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110008113B (en) | Test method and device and electronic equipment | |
| US7487080B1 (en) | Partitioning a model in modeling environments | |
| Apvrille et al. | A UML-based environment for system design space exploration | |
| CN101667134B (en) | Method for constructing compiling system and compiling system constructing device | |
| US7194726B2 (en) | Method for automatically decomposing dynamic system models into submodels | |
| US10909285B2 (en) | Method for creating a model compatible with a simulation device | |
| CN100492387C (en) | Method and system for software protected development based on Keil C51 | |
| CN112148278A (en) | Visual block chain intelligent contract framework and intelligent contract development and deployment method | |
| CN104573193A (en) | Rapid designing method for GNC (Guidance, Navigation and Control) system of spacecraft | |
| CN116643732B (en) | Method for generating joint codes of different modeling systems based on software radio communication | |
| CN116069648A (en) | Software testing method, system, equipment and storage medium | |
| CN111752841A (en) | Single test simulation method, device, equipment and computer readable storage medium | |
| CN111367579A (en) | V-REP plug-in and processor in-loop simulation method based on V-REP plug-in | |
| CN116860324B (en) | Development data processing method, development data processing apparatus, and readable storage medium | |
| Jamro et al. | Agile and hierarchical round-trip engineering of IEC 61131-3 control software | |
| CN112631594A (en) | Hardware system development method, equipment and computer readable storage medium | |
| Hawa | A Graphical User Interface for the ns-3 Simulator | |
| CN117435483A (en) | Form tool-based simulation verification excitation generation method, device, medium and terminal | |
| CN115542878A (en) | Simulation virtualization test method, system, equipment and medium based on controller | |
| CN115034165A (en) | Chip simulation verification method, system, equipment and storage medium | |
| CN114297088A (en) | Method, device, equipment and medium for testing front end vue frame assembly | |
| CN113177292A (en) | Universal BIM secondary development implementation method and device | |
| Farkas et al. | Integration of UML with Simulink into embedded software engineering | |
| US7580962B1 (en) | Automatic code generation for co-simulation interfaces | |
| CN117331565B (en) | Software generation method, device, computer equipment and storage medium |
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 |