JP2007219893A - Firmware evaluation system and firmware evaluation method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a firmware evaluation system etc. which can further improve convenience in performing evaluation concerning hardware control function of firmware. <P>SOLUTION: This firmware evaluation system is constituted including a firmware system having an API (Application Program Interface) part 130 which stores at least one API (hardware control function) 132, an input and output part 110 which outputs evaluation result information to a PC 20 while inputting from the PC 20 character strings for evaluation to perform evaluation concerning the hardware control function, and a user interface part 120 for evaluation which uses API 132. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a firmware evaluation system and a firmware evaluation method.

  In general, in firmware development, a hardware control function (for example, API) that controls hardware and a user interface unit that realizes a user interface part are simultaneously developed.

  For this reason, the developer cannot test the hardware control function until the user interface part is completed to some extent, such as delay in finding a serious problem caused by hardware, degradation of firmware quality, extension of development period, etc. There was a bad effect.

  Another cause of such an adverse effect is that the developer performs design and implementation without fully understanding the operation of the hardware control function.

  Furthermore, as a cause of such an adverse effect, there is a case where the developer has to develop with a shortage of special equipment such as ICE (In Circuit Emulator) necessary for debugging from the viewpoint of cost reduction. .

  For example, Patent Document 1 realizes a system environment that enables execution of a general-purpose test program without using a development support device such as ICE, and improves program development efficiency and the completeness of a firmware system. An embedded firmware evaluation system for the purpose is described.

  The embedded firmware evaluation system includes a host computer, and a firmware system that is connected to the host computer so as to enable two-way communication and has a firmware application and hardware for executing the application. In the firmware evaluation system, the host computer includes a test script conversion unit that analyzes a test script previously described in a specified format for firmware evaluation and converts the test script into a test code that can be recognized by the firmware system. A test code storage means for storing the test code converted by the test script conversion means; and a test code read from the test code storage means is analyzed to obtain a firmware application. And a test code execution means for executing the spare time of the execution in accordance with the test code process.

The reason why such a configuration is adopted is that, in Patent Document 1, there is a problem of a transient test program and a test program deletion mistake in a method of mounting and deleting a test program in firmware. Also, with respect to such a problem, Patent Document 1 employs a technique of fixing a test code execution unit in a firmware system.
JP 2001-154880 A

  However, as in Patent Document 1, if the test code execution means is fixed to the firmware system, the test code execution means is also included in the product at the time of shipment, and the required storage capacity of the firmware increases. .

  An object of the present invention is to provide a firmware evaluation system and a firmware evaluation method capable of further improving convenience when performing an evaluation regarding a hardware control function of firmware.

In order to solve the above problems, a firmware evaluation system according to the present invention provides:
A function storage unit storing at least one hardware control function;
An input / output unit that inputs an evaluation character string for evaluating the hardware control function from a host computer and outputs evaluation result information to the host computer;
An evaluation user interface unit using the hardware control function;
Including a firmware system having
The evaluation user interface unit includes:
A character string interpretation unit for interpreting the evaluation character string;
A function call unit that calls a specific hardware control function stored in the function storage unit according to interpretation by the character string interpretation unit;
Based on the result of calling the specific hardware control function by the function calling unit, an evaluation result generating unit that generates the evaluation result information;
It is characterized by including.

In addition, the firmware evaluation method according to the present invention includes:
A firmware evaluation method using a host computer and a firmware system,
The firmware system is:
A function storage unit storing at least one hardware control function;
An input / output unit;
An evaluation user interface unit using the hardware control function;
Including
The input / output unit inputs an evaluation character string for evaluating the hardware control function from the host computer,
The character string interpretation unit interprets the evaluation character string,
The evaluation user interface unit calls a specific hardware control function stored in the function storage unit according to the interpretation by the character string interpretation unit,
The evaluation user interface unit generates the evaluation result information based on a result of calling the specific hardware control function,
The input / output unit outputs evaluation result information to the host computer.

  According to the present invention, the user can perform an evaluation on the hardware control function using the evaluation character string. Thereby, since the user does not need to use a special device such as ICE, convenience in the case of evaluating the hardware control function of the firmware can be further improved.

  Further, according to the present invention, a firmware evaluation system or the like can be evaluated using a hardware control function using an evaluation user interface unit in the firmware system. As a result, the user can perform the evaluation using the hardware control function without using the product version user interface unit, so that the evaluation can be performed without waiting for the product version user interface unit to be completed. Development efficiency is improved.

  In addition, the host computer may include the product version user interface unit that uses the hardware control function instead of the evaluation user interface unit after the evaluation related to the hardware control function is completed. An update unit for updating may be included.

  According to this, the firmware evaluation system or the like can remove the evaluation user interface unit used for the evaluation after the evaluation is completed, and can suppress an increase in the capacity of the firmware due to the evaluation. Since the evaluation user interface part is not included, it is possible to eliminate the malfunction of the product caused by the evaluation user interface part.

  Hereinafter, a case where the present invention is applied to a firmware evaluation system will be described as an example with reference to the drawings. In addition, the Example shown below does not limit the content of the invention described in the claim at all. In addition, all of the configurations shown in the following embodiments are not necessarily essential as means for solving the problems described in the claims.

  FIG. 1 is a functional block diagram of the firmware evaluation system in the present embodiment.

  The firmware evaluation system includes a PC 20 that is a host computer, and a firmware system 10 that is connected to the PC 20 via a serial cable.

  The PC 20 also includes an evaluation character string input unit 210 that inputs an evaluation character string that is a command for performing firmware evaluation, an evaluation result display unit 220, an update unit 230 that updates the firmware system 10, and a PC side. An input / output unit 240 is included.

  The firmware system 10 includes an input / output unit 110 that inputs / outputs various information to / from the PC 20, an evaluation user interface unit 120, and an API (Application Program Interface) unit 130. The API unit 130 stores multiple types of APIs 132. The API in this embodiment is a hardware control function, and the API unit 130 functions as a function storage unit.

  The evaluation user interface unit 120 also interprets a character string interpretation unit 122 that interprets the evaluation character string, and a specific hardware control function (API 130) stored in the API unit according to the interpretation by the character string interpretation unit 122. A function calling unit 124 to be called and an evaluation result generating unit 126 that generates evaluation result information based on a result of calling a specific hardware control function by the function calling unit 124 are configured.

  The firmware system 10 is mounted on an electronic device such as a projector, for example, and has a function of controlling the operation of hardware of the electronic device.

  Note that the following can be employed as hardware for mounting these components. For example, the evaluation character string input unit 210 is a keyboard, a ROM, a CPU, etc. storing an evaluation program, the evaluation result display unit 220 is a ROM, CPU, liquid crystal display, etc., storing an evaluation program, and the updating unit 230 is CPU, PC-side input / output unit 240, input / output unit 110 is a serial port, etc., and evaluation user interface unit 120 is a CPU, RAM, HDD, etc. that operate based on a program that executes API calling processing, etc. As 130, RAM, HDD, etc. can be adopted.

  Next, a flow of firmware evaluation processing using each of these units will be described.

  FIG. 2 is a flowchart showing the flow of firmware evaluation processing in the present embodiment.

  The evaluation character string input unit 210 inputs an evaluation character string based on an operation by a developer as a user (step S1). The evaluation character string is an ASCII character string that can be input in a language that is easy for the user to use, such as a so-called interpreter language. More specifically, the evaluation character string includes, for example, an API name (API_1) to be called, an argument (10) of the API 132, and a line feed code (CR), such as “API_1 (10) CR”.

  The evaluation character string input method may be an interactive input method using a keyboard or the like, or a method of reading a file in which an evaluation character string is stored in advance.

  The PC-side input / output unit 240 outputs the evaluation character string input by the evaluation character string input unit 210 to the firmware system 10. The input / output unit 110 of the firmware system 10 inputs the evaluation character string.

  Then, the evaluation user interface unit 120 executes an evaluation process (step S2).

  FIG. 3 is a flowchart showing the flow of evaluation processing in the present embodiment.

  The character string interpretation unit 122 inputs the character string for evaluation character by character from the beginning (step S11).

  Then, the character string interpretation unit 122 determines whether the character is a line feed code (step S12).

  If it is not a line feed code, the character string interpretation unit 122 adds the character to the character buffer in the character string interpretation unit 122 (step S14).

  On the other hand, if it is a line feed code, the character string interpretation unit 122 analyzes the character string added to the character buffer (step S13) and determines whether it is a function call command (step S15).

  If it is not a function call command, the character string interpretation unit 122 generates error information indicating that it is not an appropriate evaluation character string, and the input / output unit 110 outputs the error information to the PC 20 (step S17).

  On the other hand, if it is a function call command, the function call unit 124 executes API call processing (step S16).

  FIG. 4 is a flowchart showing the flow of API call processing in this embodiment.

  The function calling unit 124 searches for API management information in the function calling unit 124 based on the evaluation character string (step S21). The API management information is, for example, information indicating “name”, “address”, “argument number” for each API 132, “argument data type” for each argument, and the like.

  Then, the function calling unit 124 determines whether the API 132 to be evaluated exists by comparing the name of the API 132 included in the evaluation character string with the name of the API 132 included in the API management information (step S22). ).

  When there is an API to be evaluated, the function calling unit 124 compares the number and data types of the arguments included in the evaluation character string with the number and data types of the API 132 arguments included in the API management information. It is determined whether or not the argument is appropriate (step S23).

  When the API does not exist or the argument is not appropriate, the function call unit 124 generates error information indicating that the API does not exist or the argument is not appropriate, and the input / output unit 110 outputs the error information to the PC 20. (Step S26).

  On the other hand, when the argument is appropriate, the function calling unit 124 calls the API 132 by specifying the argument based on the evaluation character string (step S24). More specifically, the function call unit 124 executes a call statement such as “call API_1 (10)” and returns a value when the argument “10” is input to the API “API_1” to the API unit 130. Request information that requests to return is output.

  The evaluation result generation unit 126 converts the return value (for example, “0101”, etc.) included in the response information from the API unit 130 to the request information into a character string (for example, “5”, etc.) and converts the evaluation result information into Then, the input / output unit 110 outputs the evaluation result information to the PC 20 (step S25).

  After completion of the API call process (step S16) shown in FIG. 4, the character string interpretation unit 122 clears the character buffer as shown in FIG. 3 (step S18).

  After the evaluation process (step S2) shown in FIG. 3 is completed, as shown in FIG. 2, the evaluation result display unit 220 determines whether the output from the firmware system 10 is normal (step S3).

  If not normal, that is, if error information is output, the evaluation result display unit 220 displays an error message based on the error information (step S5).

  On the other hand, when normal, that is, when the evaluation result information is output, the evaluation result display unit 220 displays the evaluation result (for example, “5”, etc.) based on the evaluation result information (step S4).

  The firmware system 10 and the PC 20 execute the above processing until the evaluation is completed (step S6).

  When the evaluation is completed and the product is ready to be shipped, the updating unit 230 updates the firmware system 10 so that the product version user interface unit is included instead of the evaluation user interface unit 120 (step S7). More specifically, for example, the updating unit 230 deletes the module of the evaluation user interface unit 120 from the firmware, and adds the module of the product version user interface unit to the firmware.

  As described above, according to this embodiment, the user can perform an evaluation on the hardware control function using the evaluation character string. Thus, the user can directly use the hardware control API 132 as if using an interpreted language. In addition, since it is not necessary to use a special device such as ICE, it is possible to further improve the convenience in the case of evaluating the hardware control function of the firmware.

  Further, according to the present embodiment, the firmware evaluation system can perform evaluation using the hardware control function using the evaluation user interface unit 120 in the firmware system 10. As a result, the user can perform the evaluation using the hardware control function without using the product version user interface unit, so that the evaluation can be performed without waiting for the product version user interface unit to be completed. Development efficiency is improved.

  Furthermore, according to the present embodiment, the firmware evaluation system can improve convenience and development efficiency in firmware evaluation, so that the quality of firmware can also be improved.

  In addition, according to the present embodiment, the firmware evaluation system can remove the evaluation user interface unit 120 used for the evaluation after the evaluation is completed, and can suppress an increase in firmware capacity due to the evaluation. Since the product does not include the evaluation user interface unit 120, it is possible to eliminate the malfunction of the product caused by the evaluation user interface unit 120.

  In addition, application of this invention is not limited to the Example mentioned above, A various deformation | transformation is possible.

  For example, in the above-described embodiment, the firmware evaluation system performs the evaluation regarding the API 132, but may perform the evaluation regarding the firmware other than the API 132. That is, the firmware evaluation system may perform an evaluation for confirming the existence of constants, variables, and the like included in the firmware.

  Further, the contents of the evaluation character string, the API calling method, and the like are not limited to the above-described embodiments, and any commonly used method can be employed. For example, the argument for calling the API may be a variable. When the argument is a variable, the function calling unit 124 can determine whether the argument is appropriate based on the variable management information in which the variable name, the variable type, and the variable value are associated.

  The use of the firmware evaluation system is not limited to the purpose of testing the API 132, and may be for the purpose of educating the developer by confirming the behavior of the API 132.

  In the above-described embodiment, the firmware evaluation system includes the PC 20, but may not include the PC 20.

It is a functional block diagram of the firmware evaluation system in a present Example. It is a flowchart which shows the flow of the firmware evaluation process in a present Example. It is a flowchart which shows the flow of the evaluation process in a present Example. It is a flowchart which shows the flow of the API call process in a present Example.

Explanation of symbols

  10 Firmware System (Firmware Evaluation System), 20 PC (Host Computer, Firmware Evaluation System), 110 Input / Output Unit, 120 Evaluation User Interface Unit, 122 Character String Interpretation Unit, 124 Function Calling Unit, 126 Evaluation Result Generation Unit, 130 API section (function storage section), 132 API (hardware control function), 230 update section

Claims (3)

A function storage unit storing at least one hardware control function;
An input / output unit that inputs an evaluation character string for evaluating the hardware control function from a host computer and outputs evaluation result information to the host computer;
An evaluation user interface unit using the hardware control function;
Including a firmware system having
The evaluation user interface unit includes:
A character string interpretation unit for interpreting the evaluation character string;
A function call unit that calls a specific hardware control function stored in the function storage unit according to interpretation by the character string interpretation unit;
Based on the result of calling the specific hardware control function by the function calling unit, an evaluation result generating unit that generates the evaluation result information;
A firmware evaluation system comprising: The firmware evaluation system according to claim 1,
After the evaluation on the hardware control function is completed, the host computer updates the firmware system so that a product version user interface unit that uses the hardware control function is included instead of the evaluation user interface unit. A firmware evaluation system comprising an update unit. A firmware evaluation method using a host computer and a firmware system,
The firmware system is:
A function storage unit storing at least one hardware control function;
An input / output unit;
An evaluation user interface unit using the hardware control function;
Including
The input / output unit inputs an evaluation character string for evaluating the hardware control function from the host computer,
The character string interpretation unit interprets the evaluation character string,
The evaluation user interface unit calls a specific hardware control function stored in the function storage unit according to the interpretation by the character string interpretation unit,
The evaluation user interface unit generates the evaluation result information based on a result of calling the specific hardware control function,
A firmware evaluation method, wherein the input / output unit outputs evaluation result information to the host computer.

Images