CN114356423B - Board-level support packet processing method and device, electronic equipment and storage medium - Google Patents

Board-level support packet processing method and device, electronic equipment and storage medium Download PDF

Info

Publication number
CN114356423B
CN114356423B CN202111546415.5A CN202111546415A CN114356423B CN 114356423 B CN114356423 B CN 114356423B CN 202111546415 A CN202111546415 A CN 202111546415A CN 114356423 B CN114356423 B CN 114356423B
Authority
CN
China
Prior art keywords
file
target
board
level
operating 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.)
Active
Application number
CN202111546415.5A
Other languages
Chinese (zh)
Other versions
CN114356423A (en
Inventor
张敏光
梁宏沛
杨艺
靳鑫
蔡思润
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Kedong Guangzhou Software Technology Co Ltd
Original Assignee
Kedong Guangzhou Software Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Kedong Guangzhou Software Technology Co Ltd filed Critical Kedong Guangzhou Software Technology Co Ltd
Priority to CN202111546415.5A priority Critical patent/CN114356423B/en
Publication of CN114356423A publication Critical patent/CN114356423A/en
Application granted granted Critical
Publication of CN114356423B publication Critical patent/CN114356423B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Abstract

The embodiment of the invention discloses a board-level support packet processing method and device, electronic equipment and a storage medium. The board-level support packet processing method specifically comprises the following steps: acquiring an initial source code file of an operating system to be processed; newly adding a newly added board level supporting package file matched with a target circuit board for running the operating system to be processed in a target root directory of the initial source code file; and generating an associated subfile of the newly added board level supporting package file according to the initial source code file. The technical scheme of the embodiment of the invention can decouple the board-level support packet of the operating system and the kernel of the operating system so as to reduce the adaptation cost of the operating system to different types of hardware, thereby improving the stability and the adaptation efficiency of the operating system.

Description

Board-level support packet processing method and device, electronic equipment and storage medium
Technical Field
The embodiment of the invention relates to the technical field of computers, in particular to a board-level support package processing method and device, electronic equipment and a storage medium.
Background
The board-level support package is a layer of important support software between the hardware board and the operating system, and faces downwards to the hardware board and upwards to the operating system. The board level support package typically contains a boot program that loads the operating system with the underlying support code, as well as drivers for all devices on the board.
In the existing operating system architecture, there is usually a strong correlation between BSP (Board Support Package), hardware file, OS (operating system kernel) file and IDE (Integrated Development Environment) tool of the operating system. If the hardware board running the operating system changes, the board-level support packet of the operating system needs to be adapted again, so that the hardware board can support the running of the operating system.
However, when the board-level support package of the operating system is re-adapted, the OS and the IDE also need to be adapted, and the modification content is large, which consumes large human resources, and increases the adaptation cost of the operating system to different types of hardware, resulting in poor stability and low adaptation efficiency of the operating system.
Disclosure of Invention
Embodiments of the present invention provide a method and an apparatus for processing a board-level support package, an electronic device, and a storage medium, which can decouple a board-level support package of an operating system from an operating system kernel to reduce the adaptation cost of the operating system to different types of hardware, thereby improving the stability and the adaptation efficiency of the operating system.
In a first aspect, an embodiment of the present invention provides a board-level support packet processing method, including:
acquiring an initial source code file of an operating system to be processed;
newly adding a newly added board-level support package file matched with a target circuit board for running the operating system to be processed in a target root directory of the initial source code file;
and generating an associated subfile of the newly added board level supporting package file according to the initial source code file.
In a second aspect, an embodiment of the present invention further provides a board-level support packet processing apparatus, including:
the initial source code file acquisition device is used for acquiring an initial source code file of the operating system to be processed;
a newly added board-level supporting package file newly adding module, configured to add, in the target root directory of the initial source code file, a newly added board-level supporting package file matched with a target circuit board for running the to-be-processed operating system;
and the association subfile determining module is used for generating the association subfile of the newly added board-level supporting package file according to the initial source code file.
In a third aspect, an embodiment of the present invention further provides an electronic device, where the electronic device includes:
one or more processors;
storage means for storing one or more programs;
when the one or more programs are executed by the one or more processors, the one or more processors are caused to implement the board-level support packet processing method provided by any embodiment of the present invention.
In a fourth aspect, an embodiment of the present invention further provides a computer storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the board-level support package processing method provided in any embodiment of the present invention.
The embodiment of the invention generates the associated subfile of the newly added board-level supporting package file according to the initial source code file by acquiring the initial source code file of the operating system to be processed and newly adding the newly added board-level supporting package file matched with a target circuit board for operating the operating system to be processed in the target root directory of the initial source code file. The method has the advantages that the newly added board-level support package file matched with the target circuit board for running the operating system to be processed is newly added in the target root directory of the initial source code file, the associated subfile of the newly added board-level support package file is generated according to the initial source code file, decoupling of the board-level support package and the kernel of the operating system is achieved, the problems of poor stability and low adaptation efficiency of the existing operating system are solved, the board-level support package and the kernel of the operating system can be decoupled, adaptation cost of the operating system to different types of hardware is reduced, and accordingly stability and adaptation efficiency of the operating system are improved.
Drawings
Fig. 1 is a flowchart of a board-level support packet processing method according to an embodiment of the present invention;
fig. 2 is a flowchart of a board-level support packet processing method according to a second embodiment of the present invention;
fig. 3 is a schematic diagram of a directory structure of an initial source code file according to a third embodiment of the present invention;
FIG. 4 is a diagram of an initial board level support package file according to a third embodiment of the present invention;
FIG. 5 is a schematic diagram of a directory structure of a target root directory according to a third embodiment of the present invention;
FIG. 6 is a table of contents structure of an initial board-level file according to a third embodiment of the present invention;
FIG. 7 is a table of contents structure of a target board-level file according to a third embodiment of the present invention;
FIG. 8 is a diagram illustrating a directory structure of a target board-level subfile according to a third embodiment of the present invention;
fig. 9 is a schematic diagram of a directory structure of a newpure controller according to a third embodiment of the present invention;
FIG. 10 is a table of contents structure of specific circuit board types according to the third embodiment of the present invention;
FIG. 11 is a diagram illustrating a directory structure of library files according to a third embodiment of the present invention;
fig. 12 is a schematic view of a directory structure of a target file to be moved according to a third embodiment of the present invention;
fig. 13 is a schematic diagram of a target structure of another target file to be moved according to a third embodiment of the present invention;
fig. 14 is a schematic diagram of a directory structure of a removed target file to be moved according to a third embodiment of the present invention;
FIG. 15 is a diagram illustrating a directory structure of a target hardware component file according to a third embodiment of the present invention;
FIG. 16 is a diagram illustrating a directory structure of supporting files of a common operating system according to a third embodiment of the present invention;
fig. 17 is a schematic diagram of a directory structure of a newly added board level support package file according to a third embodiment of the present invention;
FIG. 18 is a diagram illustrating a directory structure of an initial board level support package file according to a third embodiment of the present invention;
FIG. 19 is an interface diagram of an integrated development environment compilation tool provided by a third embodiment of the present invention;
fig. 20 is a schematic diagram of a board-level support packet processing apparatus according to a fourth embodiment of the present invention;
fig. 21 is a schematic structural diagram of an electronic device according to a fifth embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention.
It should be further noted that, for the convenience of description, only some but not all of the relevant elements of the present invention are shown in the drawings. Before discussing exemplary embodiments in more detail, it should be noted that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although a flowchart may describe the operations (or steps) as a sequential process, many of the operations can be performed in parallel, concurrently, or simultaneously. In addition, the order of the operations may be re-arranged. The process may be terminated when its operations are completed, but may have additional steps not included in the figure. The processes may correspond to methods, functions, procedures, subroutines, and the like.
Example one
Fig. 1 is a flowchart of a board-level support package processing method according to an embodiment of the present invention, where this embodiment is applicable to a case where a board-level support package of an operating system is decoupled from an operating system kernel, and the method may be executed by a board-level support package processing apparatus, where the apparatus may be implemented in a software and/or hardware manner, and may generally be directly integrated in an electronic device that executes the method, where the electronic device may be a terminal device or a server device. Specifically, as shown in fig. 1, the board-level support packet processing method may specifically include the following steps:
and S110, acquiring an initial source code file of the operating system to be processed.
The to-be-processed operating system may be an operating system that needs to be processed, for example, a Linux operating system, an Intewell operating system, or the like, which is not limited in the embodiment of the present invention. The initial source code file may be an unprocessed original code file written in any programming language. For example, the initial source code file may be an unprocessed original code file written in C language, may also be an unprocessed original code file written in C + + language, or may also be an unprocessed original code file written in java language, and the like, which is not limited in this embodiment of the present invention. It can be understood that the operating system to be processed can run on the circuit board by compiling the code file of the operating system to be processed and burning the compiled file to the circuit board.
In the embodiment of the present invention, the obtaining of the initial source code file of the to-be-processed operating system may be directly obtaining the initial source code file of the to-be-processed operating system, or may be obtaining the initial source code file of the to-be-processed operating system by using a tool. It can be understood that the obtaining of the initial source code file of the operating system to be processed by the tool may be obtaining the initial source code file of the operating system to be processed by a network tool, or obtaining the initial source code file of the operating system to be processed by a software tool, and the like.
And S120, adding a newly added board level supporting package file matched with a target circuit board for running the operating system to be processed in the target root directory of the initial source code file.
The target root directory may be a root directory in the initial source code file and may be used to store the target subdirectory, for example, an RTCore (real time kernel) root directory of the operating system, a target (device) root directory of the operating system, or the like, which is not limited in the embodiment of the present invention. The target circuit board may be a circuit board for running the to-be-processed operating system, for example, the target circuit board may be a circuit board with a different architecture, or a circuit board with a different model, and the like. For example, the target circuit board may be a circuit board of an x86 architecture, a circuit board of an ARM (Advanced RISC Machine) architecture, or a circuit board of a newboard 3200 (modular edge universal controller) model, and the like, which is not limited in this embodiment of the present invention. The newly added board-level support package file may be a newly added board-level support package file. It can be understood that by compiling the newly added board-level support package file, a compiled file matched with the target circuit board can be obtained, so that the target circuit board can run the to-be-processed operating system.
In the embodiment of the present invention, after the initial source code file of the operating system to be processed is obtained, a newly added board-level support package file matched with a target circuit board for running the operating system to be processed may be further newly added in a target root directory of the initial source code file.
In the prior art, for a target circuit board running an os to be processed, a plurality of board-level support package code files stored in a distributed manner in an initial source code file of the os to be processed are adaptively modified to compile the modified code files, so as to generate a compiled file matched with the target circuit board, and further enable the target circuit board to run the os to be processed through the generated compiled file. It can be understood that, when the code file of the board-level support package stored in a scattered manner is modified adaptively in the prior art, the kernel code file of the operating system also needs to be modified adaptively.
According to the technical scheme, the newly added board-level support package file matched with the target circuit board is newly added in the target root directory of the initial source code file, so that the board-level support package of the operating system and the kernel of the operating system can be decoupled, and the file matched with the target circuit board in the newly added board-level support package file is directly compiled to generate the compiled file matched with the target circuit board, so that the modification of the initial source code file is reduced, and the efficiency of generating the compiled file is improved.
S130, generating an associated subfile of the newly added board level supporting package file according to the initial source code file.
The associated subfile may be a subfile associated with the newly added board-level supporting package file in the newly added board-level supporting package file, for example, the associated subfile may be a subfile related to a target circuit board in the newly added board-level supporting package file, or a drive-related subfile in the newly added board-level supporting package file, which is not limited in the embodiment of the present invention.
In the embodiment of the present invention, after a new board-level support package file matched with a target circuit board for running an operating system to be processed is added in a target root directory of an initial source code file, an association subfile of the new board-level support package file may be further generated according to the initial source code file, so as to compile the association subfile of the new board-level support package file, thereby generating a compiled file matched with the target circuit board, and further enabling the target circuit board to run the operating system to be processed through the generated compiled file.
According to the technical scheme of the embodiment, an initial source code file of the operating system to be processed is obtained, and a newly added board support package file matched with a target circuit board for operating the operating system to be processed is newly added in a target root directory of the initial source code file, so that an associated subfile of the newly added board support package file is generated according to the initial source code file. The method has the advantages that the newly added board-level support package file matched with the target circuit board for running the operating system to be processed is newly added in the target root directory of the initial source code file, the associated subfile of the newly added board-level support package file is generated according to the initial source code file, decoupling of the board-level support package and the kernel of the operating system is achieved, the problems of poor stability and low adaptation efficiency of the existing operating system are solved, the board-level support package and the kernel of the operating system can be decoupled, adaptation cost of the operating system to different types of hardware is reduced, and accordingly stability and adaptation efficiency of the operating system are improved.
Example two
Fig. 2 is a flowchart of a board-level supporting package processing method according to a second embodiment of the present invention, and this embodiment further refines the above technical solutions, and provides multiple specific optional implementation manners for generating an association subfile of a newly added board-level supporting package file according to an initial source code file. The solution in this embodiment may be combined with the individual alternatives in one or more of the embodiments described above. As shown in fig. 2, the method may include the steps of:
s210, acquiring an initial source code file of the operating system to be processed.
S220, adding a newly added board level supporting package file matched with a target circuit board for running the operating system to be processed in the target root directory of the initial source code file.
And S230, determining the type of the target circuit board.
The type of the circuit board may be a specific type of the circuit board, for example, a specific model of the circuit board, or a specific architecture of the circuit board, and the like, which is not limited in this embodiment of the present invention.
In the embodiment of the present invention, after a newly added board level support package file matched with a target circuit board for running an operating system to be processed is newly added in a target root directory of an initial source code file, a circuit board type of the target circuit board may be further determined, so as to generate a target board level file according to the initial source code file and the circuit board type of the target circuit board. It can be understood that, when the operating system is run on the target circuit boards of different circuit board types, the board-level support package code file in the initial source code file of the operating system to be processed needs to be adaptively modified according to the target circuit boards of different circuit board types, and the modified code file is compiled to generate a compiled file matched with the target circuit boards of different circuit board types, so that the target circuit boards of different circuit board types can run the operating system to be processed through the compiled file.
And S240, generating a target board level file according to the initial source code file and the circuit board type of the target circuit board.
The target board-level file may be a board-level file related to a circuit board obtained by processing the board-level support package, for example, may be a board-level driver file related to the circuit board, and may also be a board-level start file related to the circuit board, and the like.
In the embodiment of the present invention, after determining the circuit board type of the target circuit board, the target board level file may be further generated according to the initial source code file and the circuit board type of the target circuit board. It will be appreciated that the target board level files for target circuit boards of different circuit board types are different.
Optionally, generating the target board-level file according to the initial source code file and the circuit board type of the target circuit board may include: acquiring an initial board level file according to the initial source code file; moving the initial board level file to a newly added board level support package file to obtain a board level file to be updated; and updating the target sub file to be updated of the board-level file to be updated according to the type of the circuit board of the target circuit board to obtain the target board-level file.
The initial board level file may be an original board level file that is not processed in the initial source code file. The board level file to be updated may be a file related to a board level that needs to be updated, for example, a board level driver file that needs to be updated, or a board level start file that needs to be updated, and the like. The target subfile to be updated may be a target subfile in a subfile to be updated in the board-level file to be updated, and may include, for example, a board-level driver subfile to be updated, a board-level initiator subfile to be updated, or a compilation control file to be updated, which is not limited in the embodiment of the present invention. It is understood that the board-level file to be updated may include a plurality of subfiles to be updated, and the target subfile to be updated may be determined according to the circuit board type of the target circuit board.
Specifically, an initial board level file is obtained according to the initial source code file, the initial board level file is moved to a newly added board level support package file to obtain a board level file to be updated, and a target sub-file to be updated of the board level file to be updated is updated according to the type of the circuit board of the target circuit board, so that the target board level file is obtained. It can be understood that the code file of the target to-be-updated subfile of the board-level file to be updated is a common code file, and if a target board-level file matching with the circuit board type of the target circuit board is desired, the target to-be-updated subfile needs to be updated according to the circuit board type of the target circuit board.
For example, taking an Intewell system as an operating system to be processed as an example, an initial board-level file Intewell _ device/target/RTCore/board may be obtained according to an initial source code file, and moved to an Intewell _ device/target/RTCore/bsp file to obtain a target to-be-updated sub-file in a board-level file Intewell _ device/target/RTCore/bsp/board, so as to obtain a target to-be-updated sub-file in the board-level file Intewell _ device/target/RTCore/bsp/board according to a board type of the target board, thereby obtaining a target board-level file Intewell _ device/target/RTCore/bsp/board.
Optionally, the target circuit board may have at least one circuit board type; correspondingly, updating the target sub-file to be updated of the board-level file to be updated according to the circuit board type of the target circuit board to obtain the target board-level file, which may include: updating the target subfiles to be updated of the board-level files to be updated according to the circuit board types of the target circuit boards to obtain target board-level subfiles matched with the circuit board types of the target circuit boards; and generating a target board level file according to each target board level subfile.
The target board-level subfile can be a target subfile in the target board-level file, can be a board-level subfile determined according to the type of the circuit board, and can be used for storing related files matched with the type of the circuit board. For example, the target board-level subfile may include a driver file of the target board-level subfile, a start file of the target board-level subfile, a library file of the target board-level subfile, or a compilation control file of the target board-level subfile, which is not limited in this embodiment of the present invention. It is understood that one circuit board type may correspond to one board level subfile. If there are multiple board types of target circuit boards, multiple target board level subfiles may be included in the target board level file.
Specifically, under the condition that there are multiple circuit board types of the target circuit board, the target to-be-updated subfile of the board-level file to be updated can be updated according to the circuit board type of each target circuit board to obtain the target board-level subfile matched with the circuit board type of each target circuit board, so that the target board-level file is generated according to each target board-level subfile. For example, taking the Intewell system as the pending operating system as an example, the target pending update subfile in the board-level file Intewell _ Developer/target/RTCore/bsp/board file may be updated according to the board type of the target circuit board, the target circuit board may be obtained as new line 3200 circuit board type matching Intewell _ devipper/target/RTCore/bsp/board/new line 3200/driver, intewell _ devipper/target/RTCore/bsp/board/new line 3200/lib, intewell _ devipper/target/RTCore/bsp/board/new line 3200/start, and Intewell _ devipper/target/RTCore/bsp/board/new line 3200/makee, to obtain target board-level sub-components Intewell _ devipper/target/RTCore/3524 zxft 3924/board/new line 3200, thereby obtaining board-level devicefile/3534.
According to the technical scheme, the problems of complicated modification process, more modified contents and the like caused by modification of a plurality of code files of the initial source code file according to different circuit board types are solved by generating the target board-level subfiles matched with the target circuit boards of different circuit board types, and the compiling file matched with the target circuit board can be generated by directly compiling according to the target board-level subfiles in the target board-level file, so that the efficiency of generating the compiling file is improved, the adaptation cost of an operating system to different types of hardware is reduced, and the adaptation efficiency of the operating system to be processed is improved.
And S250, generating a target hardware component file according to the target file to be moved in the initial source code file.
The target file to be moved may be a target file that needs to be moved, and for example, the target file may be a file related to a hardware component, such as a sysDriver file, and the like, which is not limited in this embodiment of the present invention. The target hardware component file may be a target file in a hardware component file associated with the circuit board that is processed from the board-level support package.
In the embodiment of the present invention, after the target board level file is generated according to the initial source code file and the circuit board type of the target circuit board, the target hardware component file may be further generated according to the target to-be-moved file in the initial source code file. For example, taking an Intewell system as an operating system to be processed as an example, the target hardware component file may be generated according to a target file to be moved in the initial source code file, and the target hardware component file may be generated according to the target file to be moved in the initial source code file, intewell _ device/target/RTCore/include/driver, and the target file to be moved, intewell _ device/target/RTCore/include/components/sysDriver.
S260, generating a target compiling control file according to the target board level file and the target hardware component file; and the target compiling control file is used for determining a compiling rule of the newly added board-level supporting package file.
The target compiling control file can be a target script file or a target command file for controlling compiling, and can be used for determining a compiling rule of the newly added board-level support package file. It can be understood that, when the new board-level support package file is compiled, the new board-level support package file can be compiled according to the compiling rule in the target compiling control file.
In the embodiment of the present invention, after the target hardware component file is generated according to the target to-be-moved file in the initial source code file, the target compilation control file may be further generated according to the target board-level file and the target hardware component file, so as to determine the compilation rule of the newly-added board-level support package file according to the target compilation control file, and thus compile the newly-added board-level support package file according to the compilation rule determined by the target compilation control file. For example, taking an Intewell system as an operating system to be processed as an example, the target compilation control file may be generated according to the target board-level file and the target hardware component file, and the target compilation control file may be generated according to the target board-level file Intewell _ Developer/target/RTCore/bsp/board and the target hardware component file Intewell _ Developer/target/RTCore/bsp/include.
Optionally, the method may further include: determining a public to-be-moved operating system support file according to the initial source code file; generating a public operating system supporting file according to the public operating system supporting file to be moved; correspondingly, generating the target compilation control file according to the target board level file and the target hardware component file may include: and generating a target compiling control file according to the target board level file, the target hardware component file and the common operating system support file.
The common to-be-moved operating system support file may be a support file of a common operating system that needs to be moved, for example, a common to-be-moved operating system driver file, and the like, which is not limited in the embodiment of the present invention. The common operating system support file may be a common operating system support file obtained by processing the board level support package, and may be, for example, a common operating system driver file in a newly added board level support package file, which is not limited in this embodiment of the present invention.
Specifically, the board-level support package processing method may further include determining a common to-be-moved operating system support file according to the initial source code file, and generating the common operating system support file according to the common to-be-moved operating system support file. After the common operating system support file is generated, a target compilation control file may be further generated from the target board level file, the target hardware component file, and the common operating system support file. Illustratively, taking an Intewell system as a to-be-processed operating system as an example, the common to-be-moved operating system support file Intewell _ device/product/bsp/src may be determined from the initial source code file, and the common operating system support file Intewell _ device/product/bsp/src may be generated into the common operating system support file Intewell _ device/target/RTCore/bsp/driver, and the target board level file Intewell _ device/target/RTCore/3528/board, the target hardware component file Intewell _ device/rttarget/RTCore/bsp/include and the common operating system support file Intewell _ device/target 3534/target file 3924/target file may be compiled into the target board level file Intewell _ device/target/RTCore/3528/board.
Optionally, the method may further include: determining an initial board-level supporting package file of the initial source code file; the initial board level support package file is deleted.
The initial board-level support package file may be an unprocessed board-level support package file originally in the initial source code file.
Specifically, the board-level support package processing method may further determine an initial board-level support package file of the initial source code file, so as to delete the initial board-level support package file, thereby reducing the directory hierarchy of the source code file. It will be appreciated that the functions that can be implemented in the initial board-level support package file may be implemented in the target board-level file in the newly added board-level support package file after the initial board-level support package file is deleted.
And S270, running an integrated development environment compiling tool.
S280, compiling the associated subfiles of the newly added board-level supporting package file according to the integrated development environment compiling tool to obtain a target supporting file of the to-be-processed operating system matched with the target circuit board.
Wherein, the integrated development environment compiling tool can be a tool for managing the operating system to be processed. For example, the integrated development environment compiling tool may compile the to-be-processed operating system, or may download the compiled file after the to-be-processed operating system is compiled to generate the compiled file, and the specific function of the integrated development environment compiling tool is not limited in the embodiment of the present invention. The target support file of the operating system to be processed may be a file that supports the operating system to be processed to run on the target circuit board, and may be, for example, a target driver file of the operating system to be processed, which is not limited in the embodiment of the present invention. It can be understood that, the target support file of the operating system to be processed is burned onto the target circuit board, and the operating system to be processed can run on the target circuit board according to the target support file of the operating system to be processed.
In the embodiment of the present invention, after the target compiling control file is generated according to the target board level file and the target hardware component file, the integrated development environment compiling tool may be further run to compile the associated subfiles of the newly added board level support package file according to the integrated development environment compiling tool, so as to obtain the target support file of the to-be-processed operating system matched with the target circuit board.
According to the technical scheme of the embodiment, an initial source code file of an operating system to be processed is obtained, a newly added board-level support package file matched with a target circuit board for operating the operating system to be processed is newly added in a target root directory of the initial source code file, the circuit board type of the target circuit board is determined, the target board-level file is generated according to the initial source code file and the circuit board type of the target circuit board, a target hardware component file is generated according to a target file to be moved in the initial source code file, a target compiling control file is generated according to the target board-level file and the target hardware component file, an integrated development environment compiling tool is operated, and associated subfiles of the newly added board-level support package file are compiled according to the integrated development environment compiling tool, so that the target support file of the operating system to be processed, which is matched with the target circuit board, is obtained. The method comprises the steps of adding a newly added board-level support package file matched with a target circuit board for running an operating system to be processed in a target root directory of an initial source code file, and generating a target board-level file, a target hardware component file and a target compiling control file according to the initial source code file, so that decoupling of a board-level support package and an operating system kernel of the operating system is achieved, the problems of poor stability and low adaptation efficiency of the existing operating system are solved, the board-level support package and the operating system kernel of the operating system can be decoupled, adaptation cost of the operating system to different types of hardware is reduced, and stability and adaptation efficiency of the operating system are improved.
EXAMPLE III
The embodiment of the present invention is specifically explained by taking an Intewell operating system as an example, and the board-level support packet processing method of the Intewell operating system specifically includes the following contents:
(1) An initial source code file of an Intewell operating system is obtained, fig. 3 is a directory structure schematic diagram of the initial source code file provided by the third embodiment of the present invention, and as shown in fig. 3, a directory structure in which an initial board-level supporting package file is located is Intewell _ Developer/target/RTCore/lib/gcc-3.4.4/x86/i386/little/bsp. Fig. 4 is a schematic diagram of an initial board level support package file according to a third embodiment of the present invention, and as shown in fig. 4, a compiled file libbsp _ newcre 3200.A matching the circuit board type of the target circuit board is stored in the initial board level support package file.
(2) And adding a newly added board-level support package file matched with a target circuit board for running an Intewell operating system in a target root directory of the initial source code file. Fig. 5 is a schematic diagram of a directory structure of a target root directory according to a third embodiment of the present invention, and as shown in fig. 5, a newly added board-level support package file bsp matching a target circuit board for running an Intewell operating system is newly added under the target root directory Intewell _ Developer/target/RTCore of an initial source code file.
(3) And generating a target board level file according to the initial source code file and the circuit board type of the target circuit board. Fig. 6 is a schematic diagram of a directory structure of an initial board-level file according to a third embodiment of the present invention, and as shown in fig. 6, the initial board-level file Intewell _ Developer/target/RTCore/board is obtained, and the initial board-level file is moved to a newly added board-level support package file to obtain a board-level file to be updated, so as to update a target sub-file to be updated of the board-level file to be updated according to a circuit board type of a target circuit board, thereby obtaining a target board-level file Intewell _ Developer/target/RTCore/bsp/board.
Specifically, fig. 7 is a schematic diagram of a directory structure of a target board-level file according to a third embodiment of the present invention, and as shown in fig. 7, the target board-level file may include target board-level subfiles corresponding to circuit board types of different architectures and different models. Fig. 8 is a schematic diagram of a directory structure of a target board-level subfile according to a third embodiment of the present invention, and as shown in fig. 8, the target board-level subfile may include a driver file (e.g., driver), a start file (e.g., start), and a library file (e.g., lib) for circuit board matching of different models. It is understood that the target board-level subfile may further include a compilation control file (e.g., makefile), wherein the driver file and the start file may be updated according to the board-level subfile to be updated of the board-level file to be updated moved from the initial board-level file. The compiling control file can be compiled according to the code files in the drive file and the starting file, and the compiling file generated by compiling is stored in the library file. Fig. 9 is a schematic diagram of a directory structure of a newpure controller according to a third embodiment of the present invention, and as shown in fig. 9, different circuit board types, such as 3000, 3101, and 3200, may also be included in the target board-level subfile newpure. Fig. 10 is a schematic diagram of a directory structure of a specific circuit board type according to a third embodiment of the present invention, as shown in fig. 10, under the directory of different circuit board types of the target board-level subfile newscore, a driver file (e.g., driver), a start file (e.g., start), a library file (e.g., lib), and a compiling control file (e.g., makefile) that are matched with the specific circuit board type may also be included. Fig. 11 is a schematic view of a directory structure of library files according to a third embodiment of the present invention, and as shown in fig. 11, in a directory of a 3200-type target circuit board, library files libbsp.a obtained by compiling a control file according to a driver file and a start file are stored in a lib directory in the 3200 directory.
(4) And generating a target hardware component file according to the target file to be moved in the initial source code file. Fig. 12 is a schematic view of a directory structure of a target file to be moved according to a third embodiment of the present invention, fig. 13 is a schematic view of a target structure of another target file to be moved according to a third embodiment of the present invention, fig. 14 is a schematic view of a directory structure of a removed target file to be moved according to a third embodiment of the present invention, and fig. 15 is a schematic view of a directory structure of a target hardware component file according to a third embodiment of the present invention.
Specifically, the target to-be-moved file Intewell _ device/target/RTCore/include/components/sysDriver shown in fig. 12 is moved into the target to-be-moved file Intewell _ device/target/RTCore/include/driver shown in fig. 13, the directory structure in the moved Intewell _ device/target/RTCore/include/components is shown in fig. 14, the target to-be-moved file Intewell _ device/target/RTCore/include/driver is moved into the newly added board level support package file Intewell _ device/target/RTCore/38 zft 3238, the moved Intewell _ device/target/core/include/driver is moved into the target to-be-moved file Intewell _ device/target/RTCore/3262, and the target to-be-moved into the hardware component 3262, which is only used for generating the target to-be-moved into the target to-be-moved, and the hardware component is only used for generating the target to-be-moved into the target to-be-moved file Intewell _ device/target.
(5) And determining a common to-be-moved operating system supporting file according to the initial source code file, and generating the common operating system supporting file according to the common to-be-moved operating system supporting file. Fig. 16 is a schematic diagram of a directory structure of a file supported by a common operating system according to a third embodiment of the present invention.
Specifically, the common to-be-moved operating system support file Intewell _ device/product/bsp/src is determined, and the common operating system support file Intewell _ device/target/RTCore/bsp/driver shown in fig. 16 is generated according to the common to-be-moved operating system support file Intewell _ device/product/bsp/src.
(6) And generating a target compiling control file according to the target board level file, the target hardware component file and the common operating system support file. Fig. 17 is a schematic view of a directory structure of a newly added board level support package file according to a third embodiment of the present invention. Specifically, as shown in fig. 17, the target compiling control file Intewell _ device/target/RTCore/bsp/makefile is generated according to the target board level file Intewell _ device/target/RTCore/bsp/board, the target hardware component file Intewell _ device/target/RTCore/bsp/include, and the common operating system support file Intewell _ device/target/RTCore/bsp/driver.
(7) And determining an initial board-level supporting package file of the initial source code file, and deleting the initial board-level supporting package file. Fig. 18 is a schematic diagram of a directory structure of an initial board-level supporting package file according to a third embodiment of the present invention, specifically, the initial board-level supporting package file shown in fig. 18 is determined and deleted.
(8) And operating an integrated development environment compiling tool (such as an IDE tool), and compiling the associated subfiles of the newly added board-level support package file according to the integrated development environment compiling tool to obtain the target support file of the Intewell operating system matched with the target circuit board. Fig. 19 is an interface schematic diagram of the compiling tool for an integrated development environment according to the third embodiment of the present invention, where different circuit board types shown in fig. 19 are selected, and the associated subfiles of the newly added board-level support package are compiled to obtain an Intewell operating system target support file matched with the target circuit board, so that the Intewell operating system target support file is burned onto the target circuit board, and the Intewell operating system is run on the target circuit board.
According to the technical scheme, the kernel layer, the BSP and the IDE of the Intewell operating system are isolated, the design dependence of an IDE tool is disassembled, the coupling of the BSP and the OS is reduced, the use consistency with the IDE is increased, and when a hardware board card is newly added, the compiling of the BSP file can be realized only by establishing a board-level support package in a specified directory according to an operating system template; the code architecture and the hierarchy are clear, the dependency on an Intewell operating system kernel and an IDE is greatly reduced, the independence of code maintenance is improved, the efficiency of developing the Intewell operating system and a BSP is improved, and the expansion of a hardware platform of the Intewell operating system is increased; the customized development of the board-level support package of the newly added hardware equipment is facilitated, the BSP template file of the Intebell operating system can be copied in batches, the adaptability of an embedded hardware product system using the Intebell operating system is stronger, and the scenes of flexible customization and differentiated design of the embedded product are better met; the board-level support packages of the mainstream system architecture platform (such as an x86 architecture, an ARM architecture and the like) are solidified in an Intewell operating system, directory structures of the BSP and the OS are adjusted, a uniform compiling rule file is provided for an IDE tool, the board-level support packages of various system architecture platforms are classified, and a registration interface file is provided for the IDE tool through the BSP, so that the BSP template source code is automatically generated in the IDE tool only through the registration interface file and configuration options provided by the BSP, the BSP template is burnt into a circuit board, and an operating system kernel and a file system in the circuit board can run.
Example four
Fig. 20 is a schematic diagram of a board-level support packet processing apparatus according to a fourth embodiment of the present invention, and as shown in fig. 20, the apparatus includes: an initial source code file acquiring device 2010, a newly added board level supporting package file adding module 2020 and an associated subfile determining module 2030, wherein:
an initial source code file acquiring device 2010, configured to acquire an initial source code file of an operating system to be processed;
a newly added board level support package file newly adding module 2020, configured to newly add, in the target root directory of the initial source code file, a newly added board level support package file matched with the target circuit board for running the to-be-processed operating system;
the association subfile determining module 2030 is configured to generate an association subfile of the newly added board-level supporting package file according to the initial source code file.
According to the technical scheme of the embodiment, an initial source code file of the operating system to be processed is obtained, and a newly added board support package file matched with a target circuit board for operating the operating system to be processed is newly added in a target root directory of the initial source code file, so that an associated subfile of the newly added board support package file is generated according to the initial source code file. The method has the advantages that the newly added board-level support package file matched with the target circuit board for running the operating system to be processed is newly added in the target root directory of the initial source code file, the associated subfile of the newly added board-level support package file is generated according to the initial source code file, decoupling of the board-level support package and the kernel of the operating system is achieved, the problems of poor stability and low adaptation efficiency of the existing operating system are solved, the board-level support package and the kernel of the operating system can be decoupled, adaptation cost of the operating system to different types of hardware is reduced, and accordingly stability and adaptation efficiency of the operating system are improved.
Optionally, the association subfile determining module 2030 may be specifically configured to: determining the circuit board type of a target circuit board; generating a target board level file according to the initial source code file and the circuit board type of the target circuit board; generating a target hardware component file according to a target file to be moved in the initial source code file; generating a target compiling control file according to the target board level file and the target hardware component file; and the target compiling control file is used for determining a compiling rule of the newly added board-level supporting package file.
Optionally, the association subfile determining module 2030 may be further configured to: acquiring an initial board level file according to the initial source code file; moving the initial board level file to a newly added board level support package file to obtain a board level file to be updated; and updating the target sub-file to be updated of the board-level file to be updated according to the type of the circuit board of the target circuit board to obtain the target board-level file.
Optionally, the target circuit board may have at least one circuit board type; accordingly, the association subfile determining module 2030 may be further configured to: updating the target subfiles to be updated of the board-level files to be updated according to the circuit board types of the target circuit boards to obtain target board-level subfiles matched with the circuit board types of the target circuit boards; and generating a target board level file according to each target board level subfile.
Optionally, the board-level support packet processing apparatus may further be configured to: determining a public to-be-moved operating system support file according to the initial source code file; generating a public operating system supporting file according to the public operating system supporting file to be moved; accordingly, the association subfile determining module 2030 may be further specifically configured to: and generating a target compiling control file according to the target board level file, the target hardware component file and the common operating system support file.
Optionally, the board-level support packet processing apparatus may further be configured to: determining an initial board-level supporting package file of the initial source code file; and deleting the initial board level supporting package file.
Optionally, the association subfile determining module 2030 may be further configured to: running an integrated development environment compilation tool; and compiling the associated subfiles of the newly added board-level support package file according to the integrated development environment compiling tool to obtain a target support file of the to-be-processed operating system matched with the target circuit board.
The board-level supporting packet processing device can execute the board-level supporting packet processing method provided by any embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method. For details of the technique not described in detail in this embodiment, reference may be made to the board-level support packet processing method provided in any embodiment of the present invention.
Since the board-level supporting packet processing apparatus described above is an apparatus capable of executing the board-level supporting packet processing method in the embodiment of the present invention, based on the board-level supporting packet processing method described in the embodiment of the present invention, a person skilled in the art can understand a specific implementation of the board-level supporting packet processing apparatus in the embodiment and various modifications thereof, and therefore, how the board-level supporting packet processing apparatus implements the board-level supporting packet processing method in the embodiment of the present invention is not described in detail herein. The scope of the present application is intended to be covered by the claims so long as those skilled in the art can implement the apparatus for implementing the board-level support packet processing method in the embodiments of the present invention.
EXAMPLE five
Fig. 21 is a schematic structural diagram of an electronic device according to a fifth embodiment of the present invention. FIG. 21 illustrates a block diagram of an exemplary electronic device 12 suitable for use in implementing embodiments of the present invention. The electronic device 12 shown in fig. 21 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiment of the present invention.
As shown in fig. 21, the electronic device 12 is in the form of a general purpose computing device. The components of electronic device 12 may include, but are not limited to: one or more processors 16, a memory 28, and a bus 18 that couples various system components (including the memory 28 and the processors 16).
Bus 18 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, such architectures include, but are not limited to, an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MCA) bus, an enhanced ISA bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnect (PCI) bus.
Electronic device 12 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by electronic device 12 and includes both volatile and nonvolatile media, removable and non-removable media.
Memory 28 may include computer system readable media in the form of volatile Memory, such as Random Access Memory (RAM) 30 and/or cache Memory 32. The electronic device 12 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 34 may be used to read from and write to non-removable, nonvolatile magnetic media (not shown in FIG. 21, commonly referred to as a "hard drive"). Although not shown in FIG. 21, a magnetic disk drive for reading from and writing to a removable, nonvolatile magnetic disk (e.g., a "floppy disk") and an optical disk drive for reading from or writing to a removable, nonvolatile optical disk (e.g., a Compact disk-Read Only Memory (CD-ROM), digital Video disk (DVD-ROM), or other optical media) may be provided. In these cases, each drive may be connected to bus 18 by one or more data media interfaces. Memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.
A program/utility 40 having a set (at least one) of program modules 42 may be stored, for example, in memory 28, such program modules 42 including but not limited to an operating system, one or more application programs, other program modules, and program data, each of which or some combination of which may comprise an implementation of a network environment. Program modules 42 generally carry out the functions and/or methodologies of the described embodiments of the invention.
Electronic device 12 may also communicate with one or more external devices 14 (e.g., keyboard, pointing device, display 24, etc.), with one or more devices that enable a user to interact with electronic device 12, and/or with any devices (e.g., network card, modem, etc.) that enable electronic device 12 to communicate with one or more other computing devices. Such communication may be through an Input/Output (I/O) interface 22. Also, the electronic device 12 may communicate with one or more networks (e.g., a Local Area Network (LAN), wide Area Network (WAN)) and/or a public Network (e.g., the Internet) via the Network adapter 20. As shown, the network adapter 20 communicates with the other modules of the electronic device 12 over the bus 18. It should be appreciated that although not shown in FIG. 21, other hardware and/or software modules may be used in conjunction with electronic device 12, including but not limited to: microcode, device drivers, redundant processing units, external disk drive Arrays, (Redundant Arrays of Independent Disks, RAID) systems, tape drives, and data backup storage systems, to name a few.
The processor 16 executes various functional applications and data processing by running the program stored in the memory 28, thereby implementing the board-level support packet processing method provided by the embodiment of the present invention: acquiring an initial source code file of an operating system to be processed; newly adding a newly added board level supporting package file matched with a target circuit board for running the operating system to be processed in a target root directory of the initial source code file; and generating an associated subfile of the newly added board-level supporting package file according to the initial source code file.
EXAMPLE six
An embodiment of the present invention further provides a computer storage medium storing a computer program, where the computer program is used to execute the board-level support package processing method according to any one of the above embodiments of the present invention when executed by a computer processor: acquiring an initial source code file of an operating system to be processed; newly adding a newly added board level supporting package file matched with a target circuit board for running the operating system to be processed in a target root directory of the initial source code file; and generating an associated subfile of the newly added board level supporting package file according to the initial source code file.
Computer storage media for embodiments of the present invention may take the form of any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a Read-Only Memory (ROM), an Erasable Programmable Read-Only Memory (EPROM) or flash Memory), an optical fiber, a portable compact disc Read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, radio Frequency (RF), etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
It is to be noted that the foregoing description is only exemplary of the invention and that the principles of the technology may be employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims (9)

1. A board-level support packet processing method, comprising:
acquiring an initial source code file of an operating system to be processed;
newly adding a newly added board-level support package file matched with a target circuit board for running the operating system to be processed in a target root directory of the initial source code file;
generating an associated subfile of the newly added board level supporting package file according to the initial source code file;
wherein, the generating of the associated subfile of the newly added board level support package file according to the initial source code file includes:
determining a circuit board type of the target circuit board;
generating a target board level file according to the initial source code file and the circuit board type of the target circuit board;
generating a target hardware component file according to a target file to be moved in the initial source code file;
generating a target compiling control file according to the target board level file and the target hardware component file;
the target compiling control file is used for determining a compiling rule of the newly added board-level supporting package file.
2. The method of claim 1, wherein generating a target board level file from the initial source code file and a circuit board type of the target circuit board comprises:
acquiring an initial board-level file according to the initial source code file;
moving the initial board level file to the newly added board level supporting package file to obtain a board level file to be updated;
and updating the target sub-file to be updated of the board-level file to be updated according to the circuit board type of the target circuit board to obtain the target board-level file.
3. The method of claim 2, wherein the target circuit board has at least one board type;
the updating the target to-be-updated subfile of the to-be-updated board level file according to the circuit board type of the target circuit board to obtain the target board level file includes:
updating the target to-be-updated subfiles of the to-be-updated board level files according to the circuit board types of the target circuit boards to obtain target board level subfiles matched with the circuit board types of the target circuit boards;
and generating the target board level file according to each target board level subfile.
4. The method of claim 1, further comprising:
determining a public to-be-moved operating system support file according to the initial source code file;
generating a public operating system supporting file according to the public operating system supporting file to be moved;
generating a target compilation control file according to the target board level file and the target hardware component file comprises the following steps:
and generating the target compiling control file according to the target board level file, the target hardware component file and the public operating system supporting file.
5. The method of claim 1, further comprising:
determining an initial board-level supporting package file of the initial source code file;
and deleting the initial board-level supporting package file.
6. The method of claim 1, further comprising, after the generating the associated subfile of the newly added board-level support package file from the initial source code file:
running an integrated development environment compilation tool;
and compiling the associated subfiles of the newly added board-level support package file according to the integrated development environment compiling tool to obtain a target support file of the to-be-processed operating system matched with the target circuit board.
7. A board-level support packet processing apparatus, comprising:
the initial source code file acquisition device is used for acquiring an initial source code file of the operating system to be processed;
a newly added board-level supporting package file newly adding module, configured to add, in the target root directory of the initial source code file, a newly added board-level supporting package file matched with a target circuit board for running the to-be-processed operating system;
the association subfile determining module is used for generating an association subfile of the newly added board level supporting package file according to the initial source code file;
the association subfile determining module is specifically used for determining the circuit board type of the target circuit board; generating a target board level file according to the initial source code file and the circuit board type of the target circuit board; generating a target hardware component file according to a target file to be moved in the initial source code file; generating a target compiling control file according to the target board level file and the target hardware component file; the target compiling control file is used for determining a compiling rule of the newly added board-level supporting package file.
8. An electronic device, characterized in that the electronic device comprises:
one or more processors;
storage means for storing one or more programs;
when executed by the one or more processors, cause the one or more processors to implement the board-level supported packet processing method of any of claims 1-6.
9. A computer storage medium having stored thereon a computer program, characterized in that the program, when executed by a processor, implements the board level support packet processing method according to any one of claims 1 to 6.
CN202111546415.5A 2021-12-16 2021-12-16 Board-level support packet processing method and device, electronic equipment and storage medium Active CN114356423B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111546415.5A CN114356423B (en) 2021-12-16 2021-12-16 Board-level support packet processing method and device, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111546415.5A CN114356423B (en) 2021-12-16 2021-12-16 Board-level support packet processing method and device, electronic equipment and storage medium

Publications (2)

Publication Number Publication Date
CN114356423A CN114356423A (en) 2022-04-15
CN114356423B true CN114356423B (en) 2022-11-11

Family

ID=81098472

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111546415.5A Active CN114356423B (en) 2021-12-16 2021-12-16 Board-level support packet processing method and device, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN114356423B (en)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113127077A (en) * 2021-03-29 2021-07-16 中科信安(深圳)信息技术有限公司 Server-based microkernel operating system deployment method and operating system

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101488093A (en) * 2009-03-11 2009-07-22 华为技术有限公司 Embedded computer system and its hardware configuration method
CN109558142B (en) * 2019-01-14 2021-10-29 郑州云海信息技术有限公司 Method and device for transplanting open network installation environment
CN113656049B (en) * 2021-08-30 2023-12-29 浪潮商用机器有限公司 Operating system deployment method and device, electronic equipment and storage medium

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113127077A (en) * 2021-03-29 2021-07-16 中科信安(深圳)信息技术有限公司 Server-based microkernel operating system deployment method and operating system

Also Published As

Publication number Publication date
CN114356423A (en) 2022-04-15

Similar Documents

Publication Publication Date Title
US10447814B2 (en) Joint servicing of software packages
JP6294886B2 (en) Generate native code from intermediate language code for applications
JP2008234673A (en) System and method for managing application installation for mobile device
KR20070049095A (en) Servicing a component-base software product
US8341599B1 (en) Environments sharing remote mounted middleware
CN111740948B (en) Data packet issuing method, dynamic updating method, device, equipment and medium
US20230266958A1 (en) Method for creating private image in public cloud and related device
CN110221840B (en) Function implementation method and device of application program, equipment and storage medium
CN115291946A (en) Hongmong system transplanting method, device, electronic equipment and readable medium
CN111459506B (en) Deep learning platform cluster deployment method and device, medium and electronic equipment
CN114356423B (en) Board-level support packet processing method and device, electronic equipment and storage medium
CN113760306A (en) Method and device for installing software, electronic equipment and storage medium
CN112379867B (en) Embedded operating system, method and storage medium based on modular development
US11372627B2 (en) System and method for providing integrated development environment (IDE) for programmable software system
CN111984300B (en) Code copying method and device, electronic equipment and computer readable storage medium
CN110795102B (en) Module compiling method, device, electronic equipment and computer readable medium
CN113672465A (en) Method, system, medium, terminal and unmanned aerial vehicle for generating process log system by process name
CN113901025A (en) Database management method, device, equipment and storage medium
CN113590179A (en) Plug-in detection method and device, electronic equipment and storage medium
CN112559006A (en) Enterprise client automatic upgrading method, system, equipment and storage medium
CN114253615B (en) Method and device for setting bootstrap program, electronic equipment and storage medium
CN111290746A (en) Object access method, device, equipment and storage medium
CN112083939A (en) Batch upgrading method, device, system and medium
KR100670797B1 (en) Apparatus for real-time patching without auxiliary storage device and method therefor
CN114443582B (en) File system mounting method, device, equipment and medium on operating system

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