KR20080052340A - Multi partition dependency supported embedded linux kernel and application configuration method - Google Patents

Abstract

A method for performing unified setup of multi partition dependency in an embedded system is provided to enhance development efficiency by enabling a developer to check easily stability of a system set up by the developer on various structures and environments. A method for performing unified setup of multi partition dependency comprises the following several steps. At least one partition is set up on the embedded system(S01). A position of an application program installed on the embedded system which is implemented by multi partitions is set up(S02). Dependency among application programs installed on the embedded system and stability of a system in accordance with the installation positions of the application programs is checked(S03). It is determined whether the system is in a stable setup(S04), and if not so in the step S04, an alarm message is outputted(S05). It is checked whether or not unified setup of the system is finished(S06), and if so in the step S06, an image of the embedded system is generated according to corresponding setup(S07).

Description

Multi Partition dependency supported Embedded Linux Kernel and Application Configuration method}

The present invention relates to a system integration configuration method, and more particularly, to an embedded system integration configuration method considering dependency between the disk partition structure and the dependency configuration between the application software of a computer operating system Linux on a system having a multiple disk partition structure.

An embedded system is a computer system that is specialized in a specific environment, not an environment for executing a specific application or being used for general purposes. Mobile phones, home game consoles, and digital TVs are typical embedded systems, and as the required functions of embedded system devices become more complex, they are evolving from embedded systems that have traditionally operated without operating systems to embedded systems with modern operating systems.

In addition, unlike a personal computer, an embedded system is composed of various processors, memory, and peripheral devices depending on the purpose of use.In general, the embedded system has a small storage capacity and a fast processing speed because it limits the function to a specific use. Use the device. Many attempts have been made to select Linux as an operating system (OS) used in embedded systems that can have various configurations.

Linux is a basic computer operating system that makes Unix, the operating system that used to work on large models, to run on small PCs. Linux has the advantage that the program source code is open so that programmers can add specific features as they wish, and even port them to any platform. In particular, Linux has the advantage of lowering the cost of the product because the program source code is freely available.

On the other hand, due to the limited environment of the embedded system, a development environment that can select and install only the necessary functions among application programs and kernel functions to be installed in the system is needed.

The kernel is the most important core of the computer operating system and provides several basic services to all other parts of the operating system. In general, the kernel has an interrupt handler that handles all requests that competitively require kernel services, such as terminated I / O operations, and a scheduler that determines which programs will share the kernel's processing time and in what order. It includes a supervisor that gives each process a license to the computer.

The kernel also has a memory manager that manages the operating system's address space in memory or storage and distributes it to all peripherals and other users of the kernel's services. Kernel services are requested through different parts of the operating system or through a set of program interfaces known as system calls. Because the code to maintain the kernel is used continuously, the kernel is usually loaded in a memory area that is protected from being corrupted by being overwritten by the rest of the infrequently used operating system.

There are many dependencies between the Linux kernel and application settings, which makes it difficult to configure the Linux kernel and applications. For example, option A of the Linux kernel must be selected for certain applications to work properly. Such dependencies can also exist between applications.

In order to overcome the difficulties of configuration due to such dependency, configuration menu language 2 (CML2) or embedded component description (EDC) has been developed as a computer language for enabling dependency checking during the configuration process.

That is, due to the characteristics of the embedded system, various environments may exist, and in such a diverse environment, an automated configuration program is used to efficiently and easily develop an embedded system, thereby increasing work efficiency.

However, the existing embedded system configuration tool is designed assuming a system with a single partition structure, and since only dependencies between applications are set, the basic function of the system in a partitioned environment, that is, a system with a partitioned structure, is established. There is a problem that a case can be lost.

The present invention not only sets the dependencies between the application software in the configuration of the embedded system and the configuration of the application program, but also the installation location dependency of the application program installed in each partition on the embedded system having a multi disc partition structure. The objective is to provide an integrated system integration setup method that supports multiple partition dependencies that provide automated technical requirements so that even if some partitions are separated, there is no problem with the overall system operation.

In order to achieve the above object, an embedded system integration setting method supporting multiple partition dependencies according to an embodiment of the present invention includes: setting at least one partition for an embedded system; Setting a location of an application installed in an embedded system implemented with the at least one partition structure; Checking system dependence by dependencies between applications installed in the embedded system and the installation location of the application; And after the system stability check is executed, determining whether the system is in a stable setting.

The method may further include outputting a warning message when the system is not stable after determining whether the system is stable.

And after determining whether the system is in a stable setting, checking whether the integrated setting of the system is completed; When the integration setting is completed, the method further comprises the step of generating an embedded system image with the corresponding setting.

In addition, an application program installed in a predetermined partition of the embedded system is packaged for each application program, wherein each package is characterized in that the dependency between application programs and location information as basic information are described.

In addition, when the system stability is checked, if the partition in which the first application is located is Unremovable and the partition in which the second application is dependent on the first application is Removable, the system is checked as unstable. It features.

As described above, the present invention is a method for verifying system stability in a system having a multi-partition structure and a location where an application is installed, as well as calculating dependencies between simple applications provided by an existing configuration system. Through the various structures and environments, developers can easily verify the stability of the system they set up, which has the advantage of improving development efficiency.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 is a view showing a method for describing a multi-partition structure in an embedded system according to an embodiment of the present invention.

The partition information set in the embedded system is described by describing predetermined information in six fields as shown in FIG. 1.

Referring to FIG. 1, the first field is a delimiter for each partition (QPLUS_STORAGE_0; QPLUS_STORAGE_1; QPLUS_STORAGE_2), and the second field is a delimiter representing the actual device location of the partition (/ dev / mtdblock0; / dev / mtd00; / dev / xxxx), the third field is the directory where the partition is mounted on the system (/; / usr; / usr / local in FIG. 1), and the fourth field is the partition size (10000000 in FIG. 1; 35480000; 1020300). The fifth field is the file system type (jffs2; jffs2; ramdisk of FIG. 1) to be converted when the partition is finally imaged, and the sixth field is an attribute of the partition (Unremovable; Unremovable; Unremovable of FIG. 1).

At this time. In the embodiment of the present invention, the third field and the sixth field of the six fields are utilized to consider the installation location dependence of the application installed in each partition on the embedded system having the multi disc partition structure. It features.

The attributes of the partition, the sixth field, are divided into removable and unremovable.

Here, removable represents a partition that can be detached when the system is operating, and unremovable represents a partition that is not detachable while the system is operating.

In addition, the third field, which is the directory in which the partition is mounted on the system, that is, the directory applied when the partition is set in the actual device, is used. This information is important information in forming a dependency relationship between applications.

FIG. 2 is a diagram for describing a dependency between application programs and a method of describing a location where an application program is installed in an embodiment of the present invention.

In the case of an application program installed in an embedded system, each application program is packaged for each application program, and each package describes dependency and basic information between the application programs as shown in FIG. 2.

That is, the above information describes the dependencies between the application programs in the expression "A application program requires B application program to operate", and also describes the location where the application is installed.

An embodiment of the present invention provides an application program to enable the entire system to operate even if a specific partition is separated while the system is running, depending on the location where each application is installed based on the dependency information between the applications described as shown in FIG. When setting the location or partition to be installed, the user can be referred to the rules of FIG. 3 below to show the user the possibility that a problem may occur in the entire system with respect to the current configuration.

In other words, depending on the situation, the user may intentionally set the system instability and set it. Therefore, a simple warning message is output about the possibility that the whole system may have a problem with the current setting contents. By showing only the state, the integration of the actual system leaves the decision to the user who does it.

3 is a diagram illustrating the stability verification of the entire embedded system according to the installation location between the applications in the embodiment of the present invention.

Description of each state shown in FIG. 3 is as follows.

First, if application A depends on application B, that is, package A depends on package B (P _a → P _b ), if the partition where application A is located is Unremovable and the partition where application B is located is Unremovable, It is stable because dependent programs are not separated at runtime (a).

In addition, if the partition where application A is located is removable and the partition where application B is located is Unremovable, B, a program necessary to execute application A, will exist on the system for the duration of the execution time. The system is in a stable state because it is separated at run time (b).

However, if the partition in which application A is located is Unremovable and the partition in which dependent application B is located is Removable, the system is in an unstable state because application B, which is required when the application A is running, may become detached during execution. (c).

On the other hand, if the partitions where the applications A and B are located are all removable, the system can be considered as unstable, but this state can be defined as a stable state, reflecting user intention (d).

4 is a flowchart illustrating a method for integrating an embedded system supporting multiple partition dependencies according to an exemplary embodiment of the present invention.

Based on the contents described above with reference to FIGS. 1 to 3, an integrated configuration method of an embedded system supporting multiple partition dependencies operates as described below.

Referring to FIG. 4, first, at least one partition is set for an embedded system (S01).

That is, the embedded system according to the embodiment of the present invention is implemented in a multi disc partition structure, and the partition information set in the embedded system of the multi disc partition structure is 6 as shown in FIG. The predetermined information is described in each of the three fields.

Next, the location of the application installed in the embedded system implemented with the multiple partitions is set (S02).

In this case, an application program installed in a predetermined partition of the embedded system is packaged for each application program, and each package describes dependency between the application programs and location information as basic information as shown in FIG. 2.

That is, the information includes the location information of the partition where the application is installed.

Next, the system stability by the dependence between the applications installed in the embedded system and the installation location of the application is checked (S03).

As described above with reference to FIG. 2, the dependency between the application programs may be confirmed through information of each packaged application program.

That is, in each of the packages, dependency and basic information between application programs are described as shown in FIG. The above information describes the dependencies between the applications in the expression "A application program requires B application program to operate."

In addition, according to the embodiment of the present invention, the entire system may be stably operated even when a specific partition is separated while the system is running, based on the location of each application installed based on the dependency information between the applications described as shown in FIG. Check the system for stability.

This is implemented through the diagram shown in FIG. 3 based on dependency information between the application programs and attributes of the partition divided into removable and unremovable as the sixth field described in FIG.

That is, for example, assuming that applications A and B are located in different partitions, first, when application A depends on application B, that is, when package A depends on package B (P _a → P _b ), If the partition where application A is located is Unremovable and the partition where application B is located is Unremovable, then the dependent programs are not separated at run time and thus become stable.

In addition, if the partition where application A is located is removable and the partition where application B is located is Unremovable, B, a program necessary to execute application A, will exist on the system for the duration of the execution time. The system is stable because it is separated at run time.

However, if the partition in which application A is located is Unremovable and the partition in which dependent application B is located is also Removable, the system is in an unstable state because application B, which is required when the application A is running, may become detached during execution. do.

On the other hand, if the partitions where the applications A and B are located are all removable, the system can be considered as unstable, but this state can be defined as a stable state that reflects the user's intention.

After determining whether the system is stable after executing the system stability check according to the installation location of the application program as described above (S04), if the system is not stable setting, a warning message is output (S05).

In other words, depending on the situation, the user may intentionally set the system instability and set it. Therefore, the current state of the current setting is displayed by outputting a simple warning message about the possibility that the whole system may have a problem with respect to the current setting. By showing only the integration of the actual system, it is up to the user to do this.

Next, after confirming that the integration setting of the system is completed (S06), if the integration setting is completed, generate an embedded system image with the corresponding setting (S07), otherwise, that is, if the integration setting is not completed, the first embedded The system feeds back to the partition setting step S01 of the system.

That is, since the determination of the integration of the actual system is determined by the user's judgment, when the user does not complete the setting, the feedback is fed back to the first step.

The integrated system integrated configuration method for supporting multiple partition dependencies according to the embodiments of the present invention described above may be embodied as computer readable codes on a computer readable recording medium.

Computer-readable recording media include any type of recording device that stores data that can be read by a computer system. Examples of computer-readable recording media include ROM, RAM, CD-ROM, magnetic tape, floppy disks, optical data storage devices, and the like, and may also be implemented in the form of a carrier wave (for example, transmission over the Internet). It includes being. The computer readable recording medium can also be distributed over network coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.

So far I looked at the center of the preferred embodiment for the present invention. Those skilled in the art will appreciate that the present invention can be implemented in a modified form without departing from the essential features of the present invention. The scope of the present invention is shown in the claims rather than the foregoing description, and all differences within the scope will be construed as being included in the present invention.

1 is a diagram illustrating a method for describing a multi-partition structure in an embedded system according to an embodiment of the present invention.

2 is a diagram illustrating a method for describing dependencies between applications and a location where the corresponding applications will be installed in an embodiment of the present invention.

Figure 3 is a diagram showing the stability verification of the entire embedded system according to the installation location between applications in the embodiment of the present invention.

4 is a flowchart illustrating a method for integrating an embedded system supporting multiple partition dependencies according to an exemplary embodiment of the present invention.

Claims (5)

Establishing at least one partition for the embedded system; Setting a location of an application installed in an embedded system implemented with the at least one partition structure; Checking system dependence by dependencies between applications installed in the embedded system and the installation location of the application; And determining whether the system is in a stable setting after the system stability check is executed. The method of claim 1, And determining whether the system is in a stable setting, and outputting a warning message if the system is not in a stable setting. The method of claim 1, After determining whether the system is in a stable setting, checking whether the integrated setting of the system is completed; When the integration setting is completed, the embedded system integrated configuration method for supporting multiple partition dependencies, characterized in that further comprising the step of generating an embedded system image with the corresponding setting. The method of claim 1, An application program installed in a predetermined partition of the embedded system is packaged for each application program, and each package includes an integrated system integrated configuration supporting multiple partition dependencies, wherein dependency information between applications and location information as basic information are described. Way. The method of claim 1, In the checking of the system stability, if the partition in which the first application is located is Unremovable, and the partition in which the second application is dependent on the first application is Removable, the system is checked in an unstable state. How to set up an embedded system integration that supports multiple partition dependencies.

Images