TWI529623B - The Method of Dynamic Customization of Embedded System Function - Google Patents

Description

Method for dynamically customizing embedded system functions

The present invention relates to a customized embedded system, and more particularly to a method of dynamically customizing the functionality of an embedded system.

1 shows a block diagram of a conventional embedded system, which shows a conventional embedded system 100 including a power supply unit 11, a processor unit 12, and a system memory 13 (for example, random access memory RAM, Random Access Memory) A programmable memory 14 (for example, a flash memory can be used), a communication interface 15, and an input/output unit 16. The communication interface 15 includes, for example, a communication interface such as Ethernet or WiFi.

2 shows a schematic diagram of memory planning in a conventional embedded system, which shows that a boot loader block 21 (boot loader), a work system block 22 (kernel), and a plan are programmed in the programmable memory 14. A file system block 23 (root file system) and a system setting data block 24.

In the conventional method, if the embedded system 100 is to be customized, the method needs to recompile all the changed code on a development host, and the executable image file will be regenerated. The image file of the stylized memory block is overwritten by a specific burning tool. After the system is rebooted, the updated system functions can be run.

Accordingly, in order to solve the above problems, the present invention provides a method for dynamically customizing the functionality of an embedded system to avoid cumbersome conventional customization procedures.

In order to achieve the above object, the technical means adopted by the present invention is embedded in an A custom data file system block is planned in the programmable memory in the entry system, and a customized data file system is stored. During the startup process of the embedded system, the system startup engine checks whether there is a customized data file system in the customized data file system block. If so, copy the customized data file system to a memory location in the system memory that is being read and written by at least one application that is performing the search, and finally complete the boot process of the embedded system. The customized data file system may include at least one directory or at least one file, and may also include at least one directory and at least one file.

Compared with the traditional customization method, the method is characterized in that it does not require special burning tools and can be completed without a professional background, so it is convenient and time-sensitive in use, and also increases. The flexibility of product customization requirements.

Compared with the traditional technology, if the traditional method is used, it is necessary to maintain individual software versions for each customer, so if the number of customers is large, this will increase the burden of software maintenance and production costs. By using the invention, the original factory can develop and maintain only one system software, and then customize the method according to the customer's product requirements by using the method of the invention, for example, replacing the customer-specific system page (web page), original factory Set the default value or system application function. This will not only solve the maintenance problems of the system software and reduce the cost, but also increase the energy of developing new customers.

Another feature of the present invention is that even if the user performs a firmware upgrade procedure, the customized system data is retained, and the user's customized data is not lost because the firmware is updated. The transfer process of customized data needs to be re-executed.

The specific embodiments of the present invention will be further described by the following examples and the accompanying drawings.

100,200‧‧‧ embedded system

11‧‧‧Power supply unit

12‧‧‧ Processor unit

13‧‧‧System Memory

14‧‧‧Programmable memory

15‧‧‧Communication interface

16‧‧‧Output unit

17‧‧‧System Startup Engine

18‧‧‧Communication equipment

19‧‧‧Remote host

21‧‧‧ boot loader block

22‧‧‧Operating system block

23‧‧‧ Root File System Block

24‧‧‧System setting data block

25‧‧‧Customized Data File System Block

Figure 1 shows a block diagram of a conventional embedded system; 2 is a schematic diagram of memory planning in a conventional embedded system; FIG. 3 is a block diagram showing the host of the embedded system of the present invention; FIG. 4 is a schematic diagram showing memory planning in the embedded system of the present invention; FIG. 6A and FIG. 6B are flowcharts showing the system startup of the first embodiment of the present invention; and FIGS. 7A and 7B are flowcharts showing the system startup of the second embodiment of the present invention.

The so-called dynamic customization according to the present invention means that when the embedded system is in the state of being powered on, all the customized data files can be transmitted to the embedded system by using the network transmission tool at the remote end. Customized dedicated memory block. In the future, the embedded system will replace the customized file in the original memory or add it to the appropriate directory location in time. After booting, That is to perform customized system functions.

3 is a block diagram showing an embedded system of the present invention, which shows an embedded system 200 of the present invention including a power supply unit 11, a processor unit 12, and a system memory 13 (for example, a random access memory RAM can be used. Random Access Memory, a programmable memory 14 (for example, flash memory), a communication interface 15, an input/output unit 16, and a system start engine 17. The communication interface 15 includes, for example, Ethernet, WiFi, and the like. A remote host 19 can perform bidirectional data exchange work with the embedded system 200 via the communication device 18 and the communication interface 15.

The embedded system 200 has an operating system running thereon, such as a Linux operating system. The embedded system 200 is configured by the Linux operating system for system resources and work distribution. The processor unit 12 is responsible for performing arithmetic processing of the data, and performing data access operations through the system memory 13 and the programmable memory 14 to complete the complete processing of the data.

The programmable memory 14 used in the present invention is a device that supports the MTD (Memory Technology Device) subsystem. Through the operation of the MTD subsystem of the Linux operating system, the cutting plan of the memory device can be performed.

4 is a schematic diagram showing memory planning in the embedded system of the present invention, which shows that a boot loader block 21 (boot loader), a work system block 22 (kernel), and a plan are programmed in the programmable memory 14. A file system block 23 (root file system) and a system setting data block 24, wherein the boot loader block 21, the operating system block 22, and the root file system block 23 respectively store a boot loader, Core operating system, a file system.

In the programmable memory 14, the present invention further plans to add a readable and writable customized data file system block 25 for complying with the system startup procedure of the present invention. In the embodiment of the present invention, the memory block partitioning method of the programmable memory can be used to plan a customized customized file system block 25 for software customization and to provide a readable and writable file system for The customized data file system of the present invention is stored.

If the user needs to use the technology of the present invention, it can be customized according to the process described in FIG. The embedded system is first started (step 101), and then the user needs to prepare a customized data file system to be updated (step 102). The customized data file system includes at least one directory or at least one file, and may include at least one directory and at least one file, and the customized data file system is in a format predetermined by the system.

Then, the user can log in to the embedded system host through a remote host on a remote host (step 103), and then transfer the customized data file system to the embedded system's planned customized data file through the file transfer program. System block 25 (step 104), and finally the user can execute the customized embedded system (step 106) by simply restarting the embedded system (step 105) (e.g., powering down and then powering up).

6A and 6B are flowcharts showing the system startup of the first embodiment of the present invention. As shown in FIG. 6A, the embedded system host must first be started (step 201), and then started. The boot loader (step 202) and the Linux kernel operating system are started (step 203), and the root file system is loaded into the core operating system via the file system management tool provided by the Linux operating system (step 204). The system startup engine is then initiated (step 205) and the customized data archive system block required for the invention is mounted to the core operating system (step 206).

As shown in FIG. 6B, after the system startup engine is started, the system startup engine first checks whether the customized data file system block has a customized data file system (step 207). If yes, it is determined whether the search operation of all applications is completed (step 208), and if not, according to the design of the application, the corresponding data file in the customized data file system searched by the system startup engine or The directory is copied to a memory location in the system memory readable and writable by the application (step 209), and then returns to step 208 to determine whether the search operation of all applications has been completed until all applications are executed. Search for work.

If the customized data file system is not checked in the customized data file system block in step 207, all applications are directly launched (step 210) to complete the boot process of the entire embedded system (step 211). .

7A and 7B are flow charts showing the system startup of the second embodiment of the present invention. In this embodiment, most of the process steps are the same as those of the first embodiment, except that after entering the boot loader (step 202), if the memory block plan has not been performed, the program must be executed first. Planning the memory block (step 202a) (as shown in the memory plan diagram shown in FIG. 4), and then starting the Linux core operating system (step 203), loading the root file system to the core operating system (step 204) The system startup engine is started (step 205), and the customized data file system block is mounted to the core operating system (step 206).

After the various flow steps shown in FIG. 7A are completed, the flow steps shown in FIG. 7B are performed, and the flow shown in FIG. 7B is the same as FIG. 6B.

In step 202a, when programming the programmable memory block, In addition to planning a boot loader block 21, a work system block 22, a file system block 23, and a system setting data block 24, the stylized memory 14 is further planned to add readable and writable. The customized data file system block 25 is used to store the customized data file system of the present invention.

In terms of system response description, the dynamic customizable design of the present invention cannot in principle destroy the original factory data of the system, so if the customized system is to be restored to the initial setting of the original factory, only the customized data block will exist. The file is deleted directly, and then the boot process is restarted, and the system can reply.

In terms of applications, the present invention is mainly applied to an embedded system that executes a Linux operating system. In terms of business model application, the present invention can be mainly applied to the business model of B2B, for example, the original factory for manufacturing embedded systems, which is generally marketed by ODM or modular products, and therefore needs to face the product requirements of different customers.

The above embodiments are merely illustrative of the structural design of the present invention and are not intended to limit the present invention. Any modifications and variations of the above-described embodiments can be made by those skilled in the art, and such changes are still within the spirit of the invention and the scope of the invention as defined below. Therefore, the scope of protection of the present invention should be as set forth in the appended claims.

Claims (12)

A method for dynamically customizing an embedded system function includes a processor unit, a system memory, a system startup engine, a programmable memory, and an input/output unit in an embedded system, wherein the In the stylized memory, there is a boot loader block, a work system block, a file system block, and a system setting data block, respectively storing a boot loader, a core operating system, and a file. The system further includes a customized data file system block in the programmable memory, the method comprising the steps of: (a) initiating the embedded system; (b) starting the boot loader and the core Operating system; (c) loading the root file system to the core operating system; (d) executing the system boot engine and mounting the customized data file system block to the core operating system; (e) checking the Whether there is a customized data file system in the customized data file system block; (f) according to the design of the application, the phase in the customized data file system searched by the system startup engine Data should be copied to a directory file or a memory location of the application in the system can read and write the memory; (G) of the embedded system to complete the boot process. The method for dynamically customizing an embedded system function as described in claim 1, wherein the customized data file system is configured by a user to remotely log in to the embedded system through a remote host. Then, it is transmitted to the customized data file system block in the embedded system through a file transfer program. The method for dynamically customizing an embedded system function as described in claim 1, wherein after the step (e), the step of determining whether to complete the search operation of all the applications is further included. The method of dynamically customizing an embedded system function as described in claim 1, wherein the customized data file system includes at least one directory. The method of dynamically customizing an embedded system function as described in claim 1, wherein the customized data file system includes at least one file. The method of dynamically customizing an embedded system function as described in claim 1, wherein the customized data file system includes at least one directory and at least one file. A method for dynamically customizing an embedded system function includes a processor unit, a system memory, a system startup engine, a programmable memory, and an input/output unit in an embedded system, wherein the In the stylized memory, there is a boot loader block, a work system block, a file system block, and a system setting data block, respectively storing a boot loader, a core operating system, and a file. System, the method comprising the steps of: (a) initiating the embedded system; (b) initiating the boot loader; (c) performing block programming of the programmable memory, in the programmable memory Planning a custom data file system block; (d) launching the core operating system; (e) loading the root file system into the core operating system; (f) executing the system boot engine and mounting the guest Systematize the data file system block to the core operating system; (g) check whether there is a customized data file system in the customized data file system block; (h) start the engine according to the application design Relative to the copy data file or directory should find the system customized data file in the application can write the system memory in a memory location; (i) Complete the boot process of the embedded system. The method for dynamically customizing an embedded system function according to claim 7, wherein the customized data file system is configured by a user to remotely log in to the embedded system through a remote host. Then, it is transmitted to the customized data file system block in the embedded system through a file transfer program. The method for dynamically customizing the embedded system function as described in claim 7, wherein after the step (g), the step of determining whether to complete the search operation of all the applications is further included. The method of dynamically customizing an embedded system function as described in claim 7, wherein the customized data file system includes at least one directory. A method for dynamically customizing an embedded system function as described in claim 7 wherein the customized data file system includes at least one file. The method for dynamically customizing an embedded system function according to claim 7, wherein the customized data file system includes at least one directory and at least one file.