JP2007164817A - Product information management device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To collectively manage also information related to firmware in a product information management device. <P>SOLUTION: A hardware information input means 1a inputs information related to hardware. A firmware information input means 1b input information related to firmware. A storage means 1c registers the information related to hardware and the information related to firmware in association with each other. A compile means 1e compiles, when a source file corresponding to predetermined firmware is newly registered or updated, the source file to generate an object file. A retrieval means 1d retrieves hardware information and firmware information related to a predetermined product. A writing means 1f transfers and writes the object file generated by the compile means 1e into ROM 2. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a product information management apparatus, and more particularly to a product information management apparatus that manages product design information.

In recent years, many kinds of products tend to be manufactured in large quantities with shortening of the product life cycle and diversification of user needs.
In addition, with the spread of CAD (Computer Aided Design), CAE (Computer Aided Engineering), etc., data such as design drawings created by computers has been accumulated in a large amount in a company.

Therefore, a PDM (Product Data Management) system has been proposed for the purpose of efficiently managing these data and quickly searching for necessary data.
In such a PDM system, information generated from product design to production is centrally managed, thereby preventing troubles and improving design productivity by reusing information. It becomes possible.

  Incidentally, recent products (for example, electrical appliances) often include a CPU (Central Processing Unit) and a control program (firmware) for controlling each part of the apparatus.

  However, conventionally, with respect to hardware, for example, detailed information such as a circuit diagram or a component diagram is managed, but information regarding firmware is not usually managed. Therefore, there is a problem that firmware version management and the like must be performed by humans and are complicated.

  The present invention has been made in view of these points, and an object of the present invention is to provide a product information management apparatus capable of centralized management of firmware as well as hardware.

  In the present invention, in order to solve the above-described problem, in the product information management apparatus, hardware information input means for inputting information for identifying hardware constituting a product including at least a CPU name, and a source file mounted on the product are provided. Firmware information input means for input; information for identifying hardware input from the hardware information input means; and storage means for storing the source file input from the firmware information input means in association with each other; A plurality of compiling means for compiling a source file; a storage means for associating and storing the CPU name in the information for identifying the hardware input by the hardware information input means and the compiling means; and the hardware information With input of information for identifying the hardware from the input means When the source file is input from the firmware information input unit, the storage unit is referred to obtain information identifying hardware corresponding to the input source file, and the storage unit is referred to. And a compile specifying means for specifying the compile means corresponding to the CPU name included in the information for identifying the hardware.

  According to such a product information management apparatus, information for identifying the hardware constituting the product including at least the CPU name is input by the hardware information input means. The source file mounted on the product is input by the firmware information input means. The storage means stores the information identifying the hardware input from the hardware information input means and the source file input from the firmware information input means in association with each other. The source file is compiled by the compiling means. The storage means stores the CPU name in the information for identifying the hardware input by the hardware information input means and the compiling means in association with each other. Here, when the source file is input from the firmware information input means together with the information for identifying the hardware from the hardware information input means, the storage means is referred to by the compile specifying means, and the input source file Information identifying the corresponding hardware is acquired. Further, the storage unit is referred to, and the compiler corresponding to the CPU name included in the information for identifying the hardware is specified.

  In the present invention, it is possible to simultaneously manage source files together with hardware information.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.
FIG. 1 is a block diagram showing a configuration example of an embodiment of the present invention. In this figure, the product information management apparatus 1 is composed of hardware information input means 1a, firmware information input means 1b, storage means 1c, search means 1d, compile means 1e, and write means 1f. Each piece of hardware information and firmware information are managed in association with each other.

Here, the hardware information input means 1a inputs information related to hardware (for example, a circuit diagram, a component diagram, etc.) constituting the product.
The firmware information input means 1b inputs information (for example, a source file) related to firmware installed in the product.

  The storage unit 1c stores the hardware information input from the hardware information input unit 1a and the firmware information input from the firmware information input unit 1b in association with each other, and also stores a source file, an object file, and the like. Remember.

  Here, the source file is a file including code described in, for example, C language, and the object file is a file including executable code generated by compiling the source file.

  FIG. 2 is a diagram illustrating an example of information (management table) stored in the storage unit 1c. As shown in this figure, in the management table, product names, circuit board names, CPUs, ROM (Read Only Memory), versions, object names, source names, and option names are stored in association with each other. Here, from product name to ROM is information about hardware, and from version to option name is information about firmware. Although details will be described later, each time the firmware is upgraded, the version is updated, and a new source file, object file, and option name are associated and registered.

  FIG. 3 is a diagram for explaining the details of an option file having “option name” described at the end of FIG. As shown in this figure, the option file includes a compile option 10a that is a parameter when the compiling unit 1e executes compilation, a write parameter 10b that is a parameter when the writing unit 1f writes an object file to the ROM 2, and , It is configured by design related information 10c which is information related to design (for example, information such as documents).

The retrieval unit 1d retrieves predetermined hardware information and firmware information stored in the storage unit.
The compiling unit 1e compiles the source file.

The writing means 1 f writes the object file to the ROM 2 when a predetermined object file is designated.
The ROM 2 stores an object file generated by compiling the source file.

The display device 3 is constituted by a CRT (Cathode Ray Tube) monitor or the like, and displays and outputs information searched by the search means 1d.
The input device 4 is configured by a keyboard, a mouse, or the like, and supplies information corresponding to a user operation to the search unit 1d.

Next, the operation of the above embodiment will be described.
FIG. 4 is a flowchart for explaining an example of processing executed in the embodiment shown in FIG. This process is executed when a newly created source file is registered for the hardware information already registered in the storage unit 1c. When this flowchart is started, the following processing is executed.
[S10] The source device new registration screen 20 shown in FIG.

  In this display example, the buttons 20a to 20c are respectively operated when reducing, enlarging, and ending this screen. The name of the newly created source file (source name) is input to the text box 20d. The reference button 20e is operated when searching for a desired source file from a storage device (not shown).

  In the text box 20f, the target first product name is input. The button 20g is operated to display a pull-down menu in which a list of already registered products is displayed.

  In the text box 20h, a target second product name is input. The button 20i is operated to display a pull-down menu in which a list of already registered products is displayed.

  The add button 20j is operated when a text box for inputting a product name is newly displayed. That is, when inputting three or more product names, a new text box is displayed by operating the add button 20j, and input is possible.

The registration button 20k is operated when registering with the input content.
The cancel button 201 is operated when canceling the input content.
[S11] It is determined whether or not the registration button 20k shown in FIG. 5 has been operated. If operated, the process proceeds to step S12. Otherwise, the process returns to step S11 to repeat the same processing.

If the registration button 20k is operated after the information shown in FIG. 5 is input, the process proceeds to step S12.
Although not shown in the flowchart shown in FIG. 4, when the cancel button 20l or the button 20c is operated, the process is terminated.
[S12] The storage unit 1c is searched for product data corresponding to the product name entered in the new source file registration screen 20 shown in FIG.

Now, assuming that the management table as shown in FIG. 6 is registered in the storage unit 1c, the data related to “RJ100” stored earlier is acquired from these two data.
[S13] The CPU name is acquired from the product data acquired in step S12.

In this example, “MP680” is acquired as the CPU name corresponding to “RJ100” acquired in step S12.
[S14] A compiler corresponding to the CPU name acquired in step S13 is specified.

For example, a compiler corresponding to the CPU “MP680” is specified by referring to a table in which the CPU name and the compiler name stored in the storage unit 1c are associated with each other.
[S15] The corresponding source file is input from the firmware information input means 1b, stored in the storage means 1c, and then compiled by the compiling means 1e.
[S16] The compile options set in the compiling means 1e, the write parameters set in the writing means 1f, and design-related information that is a document showing the structure of the source file, etc. are acquired, and the options shown in FIG. A file is generated.
[S17] An option file name (option name) is generated.

For example, “OP110.01” is generated as the option file name.
[S18] A file name (object name) of an object file generated as a result of compiling by the compiling unit 1e is generated.

For example, “OB110.01” is generated as the object file name. Note that the object file generated as a result of the compile processing in step S15 is given the generated file name and stored in the storage unit 1c.
[S19] A firmware version is generated.

For example, “Ver.01” is generated as the firmware version.
[S20] The generated version, object name, source name, and option name are registered in the corresponding part of the management table of the storage means 1c.
[S21] In the new source file registration screen 20 shown in FIG. 5, it is determined whether or not another product name has been input. If it has been input, the process returns to step S12 and the same processing as described above is performed. Repeat, otherwise the process ends.

In this example, since “SX250” is input as the other product name, the process returns to step S12 and the same processing is repeated.
With the above processing, for example, the management table shown in FIG. 7 is created.

Next, with reference to FIG. 8, a process for updating the source file registered as described above will be described. When this flowchart is started, the following processing is executed.
[S30] The display device 3 displays the source file update registration screen 40 shown in FIG.

  In this display example, the buttons 40a to 40c are respectively operated when reducing, enlarging, and ending this screen. In the text box 40d, the old source file name before update is input. The button 40e is operated to display a pull-down menu in which a list of source file names already registered in the storage unit 1c is displayed.

  In the text box 40f, the updated new source file name is input. The reference button 40g is operated when searching for a desired source file stored in a storage device (not shown).

  In the text box 40h, the product name corresponding to the source file input in the text boxes 40d and 40f is displayed. In this example, products “RJ100” and “SX250” having the same source file “SO110.01” are displayed as corresponding product names (see FIG. 7). The buttons 40i and 40j are operated when scrolling the display content of the text box 40h in the vertical direction.

The registration button 40k is operated when registering with the input content.
The cancel button 40l is operated when canceling the input content.
[S31] In FIG. 9, it is determined whether or not the registration button 40k has been operated. If it is operated, the process proceeds to step S32. Otherwise, the process returns to step S31 and the same process is repeated.

If the registration button 40k is operated after the information shown in FIG. 9 is input, the process proceeds to step S32.
Although not shown in the flowchart shown in FIG. 8, when the cancel button 40l or the button 40c is operated, the process ends.
[S32] The storage unit 1c is searched for product data corresponding to the input content.

In the present example, information described in the management table shown in FIG. 7 is acquired.
[S33] The CPU name is acquired from the data acquired in step S32.
In the present example, for example, “MP680” corresponding to “RJ100” is acquired.
[S34] The compiler corresponding to the CPU name acquired in step S33 is specified.

In the present example, a compiler corresponding to “MP680” is specified.
[S35] The compiling unit 1e inputs a new source file (a file corresponding to the source file name input in the text box 40f of FIG. 9) from the firmware information input unit 1b, and registers it in the storage unit 1c. Compile processing is executed by the compiler specified in step S34.

In the present example, the new source file “SO110.02” is compiled by the compiler corresponding to the CPU “MP680”.
[S36] A file name of the object file generated by the process of step S35 is generated.

In this example, for example, “OB110.02” is generated by incrementing the extension value of the old object file name as the object file name.
[S37] A version for new firmware is generated.

In this example, “Ver.02” is generated.
[S38] The generated version, object name, source name, and option name are registered in the corresponding part of the management table of the storage means 1c.
[S39] It is determined whether or not there is another product using the target source file. If it exists, the process returns to step S32 and the same processing is repeated. Ends the process.

In this example, since the product “SX250” exists, the process returns to step S32 and the same processing is repeated.
With the above processing, for example, the management table shown in FIG. 10 is created. That is, in the present example, the source file “SO110.01” is updated (for example, updated by debugging or the like), and the source file “SO110.02” is generated, so the product names “RJ100” and “SX250” It is registered as the second (Ver.02) firmware.

  Since the option file has not been changed, Ver. The same option file name as 01 is registered. As object file names, “OB110.02” and “OB210.02” with the extension value incremented are additionally registered.

Next, processing for updating an option file will be described with reference to FIG. When this flowchart is started, the following processing is executed.
[S50] The option file update registration screen 60 shown in FIG.

  In this display example, the buttons 60a to 60c are respectively operated when reducing, enlarging, and ending this screen. In the text box 60d, the name of the product for which the option file is to be updated is input. The button 60e is operated when displaying a pull-down menu in which a list of product names already registered in the storage unit 1c is displayed.

  In the text box 60f, an updated new option file name is input. The reference button 60g is operated when searching for a desired option file from files stored in a storage device (not shown).

The registration button 60h is operated when registering with the input content.
The cancel button 60i is operated when canceling the input content.
[S51] If the registration button 60h shown in FIG. 12 is operated, the process proceeds to step S52. Otherwise, the process returns to step S51 and the same process is repeated.

If the registration button 60h is operated after the information shown in FIG. 12 is input, the process proceeds to step S52.
Although not shown in the flowchart shown in FIG. 11, when the cancel button 60i or the button 60c is operated, the process is terminated.
[S52] The product data corresponding to the product name input in the text box 60d shown in FIG. 12 is searched from the management table of the storage means 1c.
[S53] The CPU name is acquired from the product data acquired in step S52.

In the present example, the name “MP680” of the CPU mounted on the product “RJ100” is acquired.
[S54] A compiler corresponding to the CPU name acquired in step S53 is specified.

In the present example, the compiler corresponding to the CPU “MP680” is specified.
[S55] An option file corresponding to the new option file name input in the text box 60f shown in FIG. 12 is input and registered in the storage means 1c, and compiler options stored in the option file are read out and the contents thereof are read. Accordingly, the compiling means 1e is set.
[S56] The compiling unit 1e compiles the latest source file of the corresponding product according to the set compile option.

In this example, the latest source file “SO110.02” of the product “RJ100” is compiled.
Note that a specified source file may be compiled instead of the latest source file.
[S57] A file name of the object file generated by the compiling process of step S56 is generated.

In the present example, “OB110.03” is generated by incrementing the extension of the latest registered object file “OB110.02”.
[S58] A version is generated.

In this example, the version “Ver.03” is generated.
[S59] The generated version, object name, source name, and option name are registered in the corresponding part of the management table of the storage means 1c.

  Through the above processing, a new option file “OP110.03” is registered in the storage unit 1c, and the management table registered in the storage unit 1c is updated as shown in FIG. In this example, the firmware information of “Ver.03” related to the product “RJ100” is newly registered in the management table. In this example, since the option file has been changed, a new option file “OP110.02” has been registered, and the object file “OB110.03” generated by performing the compile process with the new compile option has been registered. "Is registered. Since the source file has not been changed, “SO110.02” is registered as it is.

  In the above example, when the option file is updated, the compile process is executed unconditionally. For example, the compile process is executed only when the compile option of the option file is changed. It may be. With such a configuration, unnecessary compilation processing and generation of unnecessary object files can be prevented.

Next, a process for transferring an object file generated by compilation to the ROM 2 and burning it will be described with reference to FIG. When this flowchart is started, the following processing is executed.
[S70] The ROM printing screen 80 shown in FIG.

  In this display example, the buttons 80a to 80c are respectively operated when the screen is reduced, enlarged, or terminated. In the text box 80d, the product name of the target product is input. The button 80e is operated to display a pull-down menu in which a list of product names already registered in the storage unit 1c is displayed.

  In the text box 80f, the version of the firmware to be burned in the ROM 2 is input. The button 80g is operated when displaying a pull-down menu in which a list of firmware versions already registered in the storage unit 1c is displayed.

The execution button 80h is operated when printing on the ROM 2 with the input content.
The cancel button 80i is operated when canceling the input content.
[S71] If the execution button 80h shown in FIG. 15 is operated, the process proceeds to step S72. Otherwise, the process returns to step S71 and the same process is repeated.

If the execution button 80h is operated after the information shown in FIG. 15 is input, the process proceeds to step S72.
Although not shown in the flowchart shown in FIG. 14, if the cancel button 80i or the button 80c is operated, the process is terminated.
[S72] Object data corresponding to the information input on the ROM burning screen 80 shown in FIG. 15 is acquired from the storage means 1c.

In this example, “OB110.03” that is an object file of “Ver.03” of the product “RJ100” illustrated in FIG. 13 is acquired.
[S73] The corresponding option file is acquired.

In the present example, the option file “OP110.02” shown in FIG. 13 is acquired.
[S74] The write parameters included in the option file acquired in step S73 are extracted, and the write parameters of the writing means 1f are set.

In this example, the write parameter is extracted from the option file “OP110.02”, and the write parameter of the writing unit 1f is set.
[S75] The writing unit 1f executes a process of writing the object file acquired in step S72 into the ROM 2.

  According to the above processing, the writing unit 1f is set by the option file, and the object file specified by the product name and version is acquired from the storage unit 1c and written to the ROM 2. Accordingly, firmware can be collectively managed by version, and the burden on the user can be reduced.

  According to the above embodiment, the hardware information and the firmware information are associated with each other, the version is assigned to the firmware, and the firmware is managed together with the source file, the object file, and the option file. Even in the case of an error, it is possible to perform an operation check on the firmware before and after the change. Therefore, for example, when an operation failure is found in a product having an older version of firmware, the operation check of the product can be performed in an environment equivalent to that product.

  In addition, when a source file is shared by multiple products, if this source file is changed, an object file must be generated and registered by the compiler corresponding to the CPU of all applicable products. Therefore, a change in a certain source file can be reflected in all related object files.

  Even when the source file is modified with specific hardware, the hardware information and firmware information are managed in association with each other, so that an object file can be generated and registered by a compiler corresponding to the corresponding CPU.

  In addition, since the compile option, the write parameter, and the design related information are registered at the same time, it is possible to set the compile and write conditions to be the same as those of the product, generate the ROM 2, and perform the operation check. Further, useful information can be obtained from the design related information during debugging.

In the above embodiment, for simplification of description, one piece of hardware corresponds to one product name, but a plurality of pieces of hardware may correspond.
In the above embodiment, only one source file is generated for generating an object file. However, an object file may be generated from a plurality of source files.

  Finally, the above processing functions can be realized by a computer. In this case, the processing contents of the functions that the product information management apparatus should have are described in a program recorded on a computer-readable recording medium. By executing this program on the computer, the above processing is performed by the computer. Realized. Examples of the computer-readable recording medium include a magnetic recording device and a semiconductor memory. In the case of distribution to the market, a program is stored and distributed on a portable recording medium such as a CD-ROM (Compact Disk Read Only Memory) or a floppy disk (registered trademark), or a computer connected via a network. It can also be stored in a storage device and transferred to another computer via a network. When executed by a computer, the program is stored in a hard disk device or the like in the computer, loaded into the main memory and executed.

It is a block diagram which shows the structural example of embodiment of this invention. It is a figure which shows an example of the management table memorize | stored in the memory | storage means shown in FIG. It is a figure which shows an example of the data structure of an option file. 2 is a flowchart for explaining an example of processing executed when a new source file is registered in the embodiment shown in FIG. It is a figure which shows an example of the screen displayed on a display apparatus as a result of performing the flowchart shown in FIG. It is a figure which shows an example of the management table memorize | stored in the memory | storage means shown in FIG. FIG. 7 is an example of a management table generated by adding new data to the management table shown in FIG. 6 as a result of executing the flowchart shown in FIG. 4. 2 is a flowchart illustrating an example of processing executed when a source file is updated in the embodiment illustrated in FIG. 1. It is a figure which shows an example of the screen displayed on a display apparatus as a result of performing the flowchart shown in FIG. FIG. 9 is an example of a management table generated by adding new data to the management table shown in FIG. 7 as a result of executing the flowchart shown in FIG. 8; 2 is a flowchart illustrating an example of processing executed when an option file is updated in the embodiment illustrated in FIG. 1. It is a figure which shows an example of the screen displayed on a display apparatus as a result of performing the flowchart shown in FIG. 11 is an example of a management table generated by adding new data to the management table shown in FIG. 10 as a result of executing the flowchart shown in FIG. 2 is a flowchart for explaining an example of processing executed when an object file is burned into a ROM in the embodiment shown in FIG. It is a figure which shows an example of the screen displayed on a display apparatus as a result of performing the flowchart shown in FIG.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Product information management apparatus 1a Hardware information input means 1b Firmware information input means 1c Storage means 1d Search means 1e Compile means 1f Writing means 2 ROM
3 Display device 4 Input device

Claims (3)

In product information management equipment,
Hardware information input means for inputting information for identifying hardware constituting a product including at least a CPU name;
Firmware information input means for inputting the source file installed in the product,
Storage means for associating and storing information identifying hardware input from the hardware information input means and a source file input from the firmware information input means;
A plurality of compiling means for compiling the source file;
Storage means for associating and storing the CPU name in the information for identifying the hardware input by the hardware information input means and the compiling means;
When the source file is input from the firmware information input means together with the input of information for identifying the hardware from the hardware information input means, the storage file is referred to and the input source file is supported. Compile specifying means for acquiring information identifying hardware to be used, referring to the storage means, and identifying the compile means corresponding to the CPU name included in the information identifying the hardware;
A product information management apparatus comprising:   2. The product information management apparatus according to claim 1, wherein the compiling means specified by the compiling means generates an object file by performing a compiling process on the input source file.   2. The product information management apparatus according to claim 1, further comprising a writing unit for writing the object file generated by the compiling unit to the semiconductor device.

Images