CN111061460A - Universal software development platform based on embedded system - Google Patents
Universal software development platform based on embedded system Download PDFInfo
- Publication number
- CN111061460A CN111061460A CN201911282845.3A CN201911282845A CN111061460A CN 111061460 A CN111061460 A CN 111061460A CN 201911282845 A CN201911282845 A CN 201911282845A CN 111061460 A CN111061460 A CN 111061460A
- Authority
- CN
- China
- Prior art keywords
- unit
- module
- software development
- development platform
- embedded system
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Abstract
The invention discloses a structure block diagram of a general software development platform based on an embedded system, which relates to the technical field of embedded software and is used for solving the problem that the existing platform lacks a standard embedded software platform; the driving unit, the object unit, the data mapping unit, the driving management unit, the storage management unit and the application unit all comprise standard API interfaces, and the standard API interfaces are used for connecting all the units. The units of the invention can work independently, realize the mutual call among the units through API interface, can be used as the standardized platform of embedded software, reduce the development cost.
Description
Technical Field
The invention relates to the technical field of embedded software, in particular to a general software development platform based on an embedded system.
Background
With the development of energy internet, the concept of interconnection of everything appears, namely people, processes, data and things are combined together to enable network connection to become more relevant and valuable; the realization of the interconnection of everything requires various hardware devices to provide basic data, and the hardware usually realizes the functions through an embedded system. The embedded software field and the computer software are already independent, and the computer software has a large number of open-source and widely-applied standard architectures; the current embedded software lacks a standardized development platform, and due to various hardware and various functional requirements, hardware is often needed to be crossed, a system is often crossed or a new technical module is added, so that the embedded software often needs to be repeatedly developed, and the problems of high development cost, low efficiency and incapability of effectively guaranteeing reliability are caused.
With the development of equipment intellectualization, more and more complex hardware acquisition equipment is required for data acquisition, analysis and processing, and a standardized embedded system development platform is urgently needed.
Disclosure of Invention
In order to overcome the defects of the prior art, the invention provides a general software development platform based on an embedded system, which divides different units according to functions, and each unit provides an API (application programming interface) to the outside, so that each unit can work independently.
The invention is realized by adopting the following technical scheme:
a general software development platform based on an embedded system comprises a driving unit, an object unit, a data mapping unit, a driving management unit, a storage management unit and an application unit; the driving unit, the object unit, the data mapping unit, the driving management unit, the storage management unit and the application unit all comprise standard API interfaces, and the standard API interfaces are used for connecting all the units;
the driving unit is used for providing a standard hardware interface;
the object unit is connected with the driving unit, is a protocol and data collection unit and is used for data acquisition and logical operation;
the data mapping unit is connected with the application unit and is used for data mapping of the application unit;
the drive management unit is respectively connected with the drive unit, the object unit and the application unit and is used for managing the drive unit and the object unit;
the storage management unit is used for storing data and also storing system configuration and system logs;
the application unit is used for executing the embedded application software program.
Furthermore, the system also comprises a pre-compiling system, wherein the pre-compiling system comprises a set of standard compiling switches, and the pre-compiling system is used for realizing the functions of capacity expansion and clipping of the platform. The setting of the pre-compiling system can lead the platform to be infinitely expanded and randomly cut, and realize the uniform API interface of the platform.
Further, the drive management unit manages a drive node by creating a linked list, the drive node is hung with an object of the object unit, and the drive node and the object are determined by the storage configuration of the storage unit.
Further, the drive management unit provides a data storage address interface and a drive node parameter setting interface for other unit calls. The data storage address interface and the driving node parameter setting interface can facilitate the calling of the upper layer unit.
Further, the application unit comprises a UI module, a UPCOM module and an APP module; the UI module is used for realizing a human-computer interaction interface, the UPCOM module is used for loading configuration files of different products and completing communication with a background, and the APP module is used for realizing a logic function of the products. The three modules of the application unit can realize the butt joint of various application programs, and the operation of other units or modules can not be influenced.
Further, the storage management unit comprises a configuration module, a log module and a bottom storage module; the configuration module is used for configuration management, the log module is used for realizing the unified management of a log alarm system, and the bottom storage module is used for reading, writing and storing embedded product data.
Further, still include the frock unit, the frock unit is used for the frock of product production to detect.
Furthermore, the system also comprises a CBB module unit which is an integrated unit of the general software function and provides a standard library for the platform.
Furthermore, the system also comprises a general background unit which is used for running the background program.
And further, the system also comprises a program task scheduling unit which is used for scheduling the tasks of all units and completing the detection of the watchdog and the abnormal detection of the thread task. The program task scheduling unit can ensure the safe and stable operation of the system.
Compared with the prior art, the invention has the beneficial effects that:
according to the embedded software development platform, each layer of the embedded software development platform is subdivided, each unit can work independently, the operation of other units is not influenced, a new technical module can be accommodated without being limited by an operating system, the provided standard API can be used for butting various hardware and completing the connection and calling among the units, so that the platform supports cross-hardware, the development cost is reduced, and the development efficiency is improved; in addition, when a developer develops on the basis of the platform, only configuration of bottom hardware and compiling of application logic are needed, understanding of a system scheduling principle and a storage principle is not needed, and difficulty in embedded software development is reduced.
Drawings
FIG. 1 is a block diagram of a general software development platform based on an embedded system according to a first embodiment;
FIG. 2 is a diagram of the operation mechanism of the drive management unit according to the first embodiment;
fig. 3 is a block diagram of a general software development platform based on an embedded system according to the second embodiment.
Detailed Description
The present invention will now be described in more detail with reference to the accompanying drawings, in which the description of the invention is given by way of illustration and not of limitation. The various embodiments may be combined with each other to form other embodiments not shown in the following description.
Example one
The first embodiment provides a general software development platform based on an embedded system, which is used for solving the problem that embedded software needs to be re-developed according to different hardware or different functions due to the fact that a standard platform is lacked in the prior art.
The existing embedded software development platform is generally layered according to business logic, such as a driver layer, an application layer, a hardware layer and the like, each layer has a plurality of functions, and once one function needs to be changed, the whole embedded software needs to be recompiled.
In the embodiment, each unit of the general software development platform based on the embedded system is independent in function and has no strict dependency relationship, and different units are called by providing a standard API interface.
Referring to the structural block diagram shown in fig. 1, a general software development platform based on an embedded system includes a driving unit 110, an object unit 120, a data mapping unit 130, a driving management unit 140, a storage management unit 150, and an application unit 160; the driving unit 110, the object unit 120, the data mapping unit 130, the driving management unit 140, the storage management unit 150, and the application unit 160 all include standard API interfaces for connecting the units;
in order to reduce the compiling workload, the platform also comprises a pre-compiling system, and the system realizes the capacity expansion and the cutting of the platform by adding a set of standard compiling switches. The selection and matching of a chip, a hardware platform, a software platform and a programming language can be met through the compiling switch, so that the expansion can be unlimited, and different scenes can be targeted.
The pre-compiling refers to the preprocessing of codes, namely, the code texts are compiled in advance, and then the compiling work can be completed by carrying out corresponding code text replacement according to specific programs, hardware and the like, so that repeated compiling is not needed, the workload is reduced, and a uniform compiling format is provided. The embodiment does not limit the specific precompilation system, and the specific format of the precompilation system needs to be performed according to a specific programming language.
The driving unit 110 is used for providing a standard hardware interface;
the object unit 120 is connected to the driving unit 110, and the object unit 120 is a protocol and data collection unit for data acquisition and logical operation;
the data mapping unit 130 is connected to the application unit 160, and is used for data mapping of the application unit 160;
the driving management unit 140 is respectively connected to the driving unit 110, the object unit 120 and the application unit 160, and is configured to manage the driving unit 110 and the object unit 120;
the driver management unit 140 manages a driver node by creating a linked list, the driver node is mounted with an object of the object unit 120, and the driver node and the object are determined by the storage configuration of the storage unit 150.
The drive management unit 140 also provides a data storage address interface and a drive node parameter setting interface for other unit calls.
The storage management unit 150 is configured to store data, and the storage management unit 150 further stores system configuration and system logs;
the storage management unit 150 comprises a configuration module 1501, a log module 1502 and a bottom storage module 1503; the configuration module 1501 is used for configuration management, the log module 1502 is used for implementing unified management of a log alarm system, and the bottom storage module 1503 is used for reading, writing and storing embedded product data.
The application unit 160 is used to execute embedded application software programs.
The application unit 160 includes a UI module 1601, a UPCOM module 1602, and an APP module 1603; the UI module 1601 is used for implementing a human-computer interaction interface, the UPCOM module 1602 is used for loading configuration files of different products and completing communication with a background, and the APP module 1603 is used for implementing a logic function of the product.
The driving unit 110 is mainly a set of standard hardware interfaces, and is a set of standard API interfaces for upper layer applications, and different hardware can be completely integrated into the platform only by programming according to the specified API interfaces. The upper layer applications need not be concerned with which hardware and operating system is specifically used.
The object unit 120 integrates various operation hardware interface units, such as a battery voltage sampling unit, a weather information acquisition unit, a temperature and humidity acquisition control unit, and the like. The units are directly integrated through communication external equipment or the units are all units of data required to be collected, after the units are designed, hardware and protocols are determined, and a set of standard interfaces, namely the operation hardware interface, can be formed according to the hardware and the protocols. The platform integrates these operation hardware interface units into the object unit 120 for data collection and logical operation analysis. All the operating hardware interface units in the object unit 120 can be configured or tailored at any time.
The data mapping unit 130 mainly performs mapping between the application unit 160 and the underlying data. The data mapping unit 130 performs underlying data access through the data access interface provided by the storage management unit 150; meanwhile, the data mapping unit 130 may create a data mapping configuration table, and determine the physical data source of the application unit 160 through background configuration, so that the data of the application program becomes flexible and the data source can be configured arbitrarily; and the data logic operation of the application unit 160 becomes simple and independent without depending on the bottom layer. The underlying hardware, systems, and objects units 120 described above.
The drive management unit 140 is configured to manage the entire drive unit 110 and the object unit 120, and is used for scheduling and storing data of the two units, without performing logical operation and data analysis. The logical operation and data analysis are performed by the object unit 120. Fig. 2 shows an operation mechanism of the drive management unit 140, and the drive management unit 140 manages objects mounted on each drive node (the objects are objects of the object unit 120) by creating a linked list, which is a "tree diagram" in fig. 2, that is, a linked list, determined according to the system configuration stored in the storage management unit 150. When power-on initialization is performed, the driving management unit 140 obtains a corresponding node according to the configuration information, and simultaneously applies a corresponding space to the system for data storage. The drive management unit 140 provides an address interface for data storage and a device node parameter setting interface at the same time, so as to be used by other units for scheduling.
It should be noted that both the object unit 120 and the driver unit 110 must register with the driver management unit 140 according to a specified format, and finally, the driver management unit 140 performs scheduling management.
The following is an example of the specified format in the present embodiment, and the specified format is as follows:
drive (drive unit 110) registration interface: DMU _ DEV _ INIT (d _ xx, d _ xx _ Op), where DMU refers to the driver management unit 140, d _ xx is the name of a driver node, and d _ xx _ Op is an operation function pointer provided by the driver node for scheduling by the driver management unit 140; i.e. the operation function that the drive unit 110 has to implement.
Object (object unit 120) registration interface: DMU _ OBJ _ INIT (j _ xx, j _ xx _ Func, j _ Format, size), where j _ xx is the name of an object node, and j _ xx _ Func is an object node execution function, and the execution function is scheduled by the drive management unit 140, that is, the function prototype to be implemented by the object unit 120 includes functions of protocol packet unpacking, data operation, and the like. The J _ Format is a structural body with parameter configuration, and mainly comprises parameters such as cycle time required by the operation of the object, communication timeout time, communication baud rate, serial or parallel driving management scheduling mode and the like. The size is the size of the data structure required for the object, and after registration is completed, the drive management unit 140 completes the application of the memory space.
The configuration module 1501 in the storage management unit 150 manages the configuration of the entire system, and uses a general standard protocol to interface with a background to complete the distribution and storage of the configuration, where the background refers to the processing background of the application unit 160, and the configuration module 1501 provides a set of standard read-write configuration interfaces for other units, such as the drive management unit 140, to use in the read-write system configuration. The log module 1502 is used to implement unified management of a log alarm system, is compatible with different log storage modes, and provides an API interface for connecting other units or other hardware, so as to facilitate log acquisition and log storage. The bottom-layer storage module 1503 is used to store related data in the embedded software, and the storage algorithm in the bottom-layer storage module 1503 is not specifically limited in this embodiment as long as the read-write requirements of the flash (flash memory) of the embedded product can be met.
In order to further improve the application unit 160, the application unit 160 is subdivided, wherein the UI module 1601 is used for realizing a human-computer interaction interface, the functions of the module are completely independent, and the realization principle of randomly docking various UIs, such as QT/serial port screen display/configuration software, can be realized. The UPCOM module 1602 is a set of background protocols established by the platform, and the platform realizes the function of docking different product backgrounds by loading different configuration files. The APP module is a main logic function area of the whole embedded software and mainly completes specific service indexes.
The present embodiment further explains a usage flow of the present platform:
according to the hardware requirement of the real product, the driver of the hardware is added in the drive unit 110 according to the specified API format.
The storage management unit 150 adds the storage model and the interface supported by the product hardware according to a specified format.
The logical management of the product is added at the application unit 160.
The configuration table is written in the background according to the platform configuration requirements and stored in the storage management unit 150 (the configuration table is the configuration tree used by the drive management unit 140 to facilitate scheduling by the drive management unit 140).
According to the actual demand of the product, new modules can be added to the object unit 120, the object unit 120 can be selected and matched according to the demand as an independent part of the platform, and the follow-up general object function does not need to be developed again.
Example two
The second embodiment is performed on the basis of the first embodiment, and a functional unit is added on the basis of the first embodiment, so that the embedded system-based general software development platform can realize more functions.
Referring to fig. 3, the embodiment further includes a tool unit 210, a CBB module unit 220, a general background unit 230, and a program task scheduling unit 240, wherein the tool unit 210 is connected to the driving unit 110, the general background unit 230 is connected to the application unit 160, and the CBB module unit 220 and the program task scheduling unit 240 are directly connected to the platform.
In the embedded field, when the products are required to be produced in batches, strict detection is required to ensure the usability of the products, and the tool unit 210 meets the tool test of the hardware products through a stored standard hardware interface detection algorithm; the tool unit 210 uses a standardized background protocol, and then only a hardware configuration table needs to be completed for tools of different hardware, and the development of the protocol is not needed.
The CBB module unit 220 mainly refers to a general software-only function integration unit, such as a general battery management unit BMS, a core insulation detection algorithm, an MQTT network protocol, an SNMP network protocol, and the like; these mainstream core algorithms are incorporated into the CBB module 220 of the platform to add a standard library function to the platform.
The general background unit 230 is used as a background of the platform, and is mainly used for running a background program, and completes communication with the application unit 160 through the UPCOM module 1602.
The task scheduling unit 240 is a program task scheduling unit designed by the platform for different hardware and operating systems, and completes task scheduling of a program, including running of the driving unit 110, running of the storage management unit 150, running of the application unit 160, running of the data mapping unit 130, and the like, and also completes special functions such as watchdog detection and thread task exception detection, so as to ensure safe and stable running of the system.
Various other modifications and changes may be made by those skilled in the art based on the above-described technical solutions and concepts, and all such modifications and changes should fall within the scope of the claims of the present invention.
Claims (10)
1. A general software development platform based on an embedded system is characterized by comprising a driving unit, an object unit, a data mapping unit, a driving management unit, a storage management unit and an application unit; the driving unit, the object unit, the data mapping unit, the driving management unit, the storage management unit and the application unit all comprise standard API interfaces, and the standard API interfaces are used for connecting all the units;
the driving unit is used for providing a standard hardware interface;
the object unit is connected with the driving unit, is a protocol and data collection unit and is used for data acquisition and logical operation;
the data mapping unit is connected with the application unit and is used for data mapping of the application unit;
the drive management unit is respectively connected with the drive unit, the object unit and the application unit and is used for managing the drive unit and the object unit;
the storage management unit is used for storing data and also storing system configuration and system logs;
the application unit is used for executing the embedded application software program.
2. The embedded system-based general software development platform of claim 1, further comprising a pre-compilation system, wherein the pre-compilation system comprises a set of standard compilation switches, and the pre-compilation system is configured to implement capacity expansion and tailoring functions of the platform.
3. The embedded system-based generic software development platform of claim 1, wherein the driver management unit manages driver nodes by creating a linked list, the driver nodes are loaded with objects of the object unit, and the driver nodes and the objects are determined by the storage configuration of the storage unit.
4. The embedded system-based generic software development platform of claim 3, wherein the driver management unit provides a data storage address interface and a driver node parameter setting interface for other unit calls.
5. The embedded system-based generic software development platform of claim 1, wherein the application unit comprises a UI module, a UPCOM module and an APP module; the UI module is used for realizing a human-computer interaction interface, the UPCOM module is used for loading configuration files of different products and completing communication with a background, and the APP module is used for realizing a logic function of the products.
6. The embedded system-based general software development platform of claim 1, wherein the storage management unit comprises a configuration module, a log module and an underlying storage module; the configuration module is used for configuration management, the log module is used for realizing the unified management of a log alarm system, and the bottom storage module is used for reading, writing and storing embedded product data.
7. The embedded system-based general software development platform of claim 1, further comprising a tooling unit for tooling detection for product production.
8. The embedded system-based generic software development platform of claim 1, further comprising a CBB-based module unit, wherein the CBB-based module unit is an integrated unit of generic software functions and provides a standard library for the platform.
9. The embedded system-based general software development platform as claimed in claim 1 or 5, further comprising a general background unit for running a background program.
10. The embedded system-based generic software development platform of claim 1, further comprising a program task scheduling unit for task scheduling of each unit and completing watchdog detection and thread task exception detection.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911282845.3A CN111061460B (en) | 2019-12-13 | 2019-12-13 | Universal software development platform based on embedded system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911282845.3A CN111061460B (en) | 2019-12-13 | 2019-12-13 | Universal software development platform based on embedded system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111061460A true CN111061460A (en) | 2020-04-24 |
| CN111061460B CN111061460B (en) | 2023-09-29 |
Family
ID=70301417
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911282845.3A Active CN111061460B (en) | 2019-12-13 | 2019-12-13 | Universal software development platform based on embedded system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111061460B (en) |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101089814A (en) * | 2007-07-12 | 2007-12-19 | 浙江大学 | Software applied frame for data analysing instrument equipment and device and method for developing embedded system using the frame |
| US20120144376A1 (en) * | 2009-06-02 | 2012-06-07 | Vector Fabrics B.V. | Embedded system development |
| CN102968311A (en) * | 2012-12-13 | 2013-03-13 | 中国航空无线电电子研究所 | Onboard embedded software development platform |
| CN103077039A (en) * | 2013-02-28 | 2013-05-01 | 福州昌晖自动化系统有限公司 | Software development platform for embedded industrial control instrument |
| CN104699489A (en) * | 2015-04-02 | 2015-06-10 | 成都彬鸿科技有限公司 | Multiple operating systems based embedded software platform |
| KR20160112755A (en) * | 2015-03-20 | 2016-09-28 | 한국전자통신연구원 | Method of self-adaptive design of embedded software |
| CN106528153A (en) * | 2016-11-10 | 2017-03-22 | 成都中嵌自动化工程有限公司 | Embedded software modular construction method and device |
| US20170102924A1 (en) * | 2015-10-11 | 2017-04-13 | Renesas Electronics America Inc. | Software architecture for embedded systems |
| CN107133034A (en) * | 2017-04-17 | 2017-09-05 | 王成 | The platform software implementation method and system of cross operating system |
| WO2017148287A1 (en) * | 2016-03-02 | 2017-09-08 | 中兴通讯股份有限公司 | Embedded software development method, apparatus and platform, and storage medium |
| CN109508202A (en) * | 2018-09-27 | 2019-03-22 | 华东计算技术研究所（中国电子科技集团公司第三十二研究所） | Drive development system, method and medium for embedded operating system |
-
2019
- 2019-12-13 CN CN201911282845.3A patent/CN111061460B/en active Active
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101089814A (en) * | 2007-07-12 | 2007-12-19 | 浙江大学 | Software applied frame for data analysing instrument equipment and device and method for developing embedded system using the frame |
| US20120144376A1 (en) * | 2009-06-02 | 2012-06-07 | Vector Fabrics B.V. | Embedded system development |
| CN102968311A (en) * | 2012-12-13 | 2013-03-13 | 中国航空无线电电子研究所 | Onboard embedded software development platform |
| CN103077039A (en) * | 2013-02-28 | 2013-05-01 | 福州昌晖自动化系统有限公司 | Software development platform for embedded industrial control instrument |
| KR20160112755A (en) * | 2015-03-20 | 2016-09-28 | 한국전자통신연구원 | Method of self-adaptive design of embedded software |
| CN104699489A (en) * | 2015-04-02 | 2015-06-10 | 成都彬鸿科技有限公司 | Multiple operating systems based embedded software platform |
| US20170102924A1 (en) * | 2015-10-11 | 2017-04-13 | Renesas Electronics America Inc. | Software architecture for embedded systems |
| WO2017148287A1 (en) * | 2016-03-02 | 2017-09-08 | 中兴通讯股份有限公司 | Embedded software development method, apparatus and platform, and storage medium |
| CN106528153A (en) * | 2016-11-10 | 2017-03-22 | 成都中嵌自动化工程有限公司 | Embedded software modular construction method and device |
| CN107133034A (en) * | 2017-04-17 | 2017-09-05 | 王成 | The platform software implementation method and system of cross operating system |
| CN109508202A (en) * | 2018-09-27 | 2019-03-22 | 华东计算技术研究所（中国电子科技集团公司第三十二研究所） | Drive development system, method and medium for embedded operating system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111061460B (en) | 2023-09-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9405653B1 (en) | Filtering data frames using program instrumentation | |
| Österlind | A sensor network simulator for the Contiki OS | |
| EP3030969B1 (en) | Automated application test system | |
| Levis | Experiences from a Decade of {TinyOS} Development | |
| CN105144118A (en) | Application testing and analysis | |
| GB2425622A (en) | Programming real-time systems using data flow diagrams | |
| US11250193B1 (en) | Productivity platform using system-on-chip with programmable circuitry | |
| CN109507991B (en) | Double-shaft servo control platform debugging system and method | |
| CN113434131A (en) | Programming method and device, computer equipment and storage medium | |
| CN114691188A (en) | Compatibility evaluation method, device, equipment and storage medium | |
| US11789775B2 (en) | Progress visualization of computational job | |
| CN102331961B (en) | Method, system and dispatcher for simulating multiple processors in parallel | |
| CN107436839B (en) | Process load acquisition method, electronic terminal and computer readable storage medium | |
| CN115438768A (en) | Model reasoning method, device, computer equipment and storage medium | |
| CN109388505B (en) | A kind of asynchronous multitask sequence loading method based on Android | |
| CN111061460A (en) | Universal software development platform based on embedded system | |
| Panfilov et al. | Dataflow computing and its impact on automation applications | |
| CN110908644A (en) | Configuration method and device of state node, computer equipment and storage medium | |
| US10474610B1 (en) | Hardware trace and introspection for productivity platform using a system-on-chip | |
| CN112764729B (en) | Application software development method, device, computer equipment and readable storage medium | |
| CN115543534A (en) | Training task management method and device, electronic equipment and storage medium | |
| CN108334313A (en) | Continuous integrating method, apparatus and code management system for large-scale SOC research and development | |
| US20190050231A1 (en) | Slave processor within a system-on-chip | |
| CN108984238A (en) | Gesture processing method, device and the electronic equipment of application program | |
| CN114201382A (en) | Test case generation method and device, storage medium and electronic equipment |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |