JP2005284963A - Method and system for loading program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a method and a system for loading programs, which may reduce a period of an executing cycle for a program loader as well as a time period for transferring a file to a targeted system. <P>SOLUTION: The system includes a relocatable file storage 2, a data output unit 18 for transferring a relocatable object file to a targeted system 47; a section data storage unit 3 for storing a section table data which is transferred from the targeted system 47; a linker 5 which is coupled to the relocatable file storage 2 and the section data storage 3 for generating an absolute object file; an absolute object storage unit 4 for storing the absolute object files; a relocatable file storage unit 2; a section data storage unit 3; and a central processing unit 33 which controls the absolute file storage 4 and the linker 5. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a program loading apparatus and a program loading method for loading a relocatable object file format program.

A conventional program loading apparatus creates a relocatable object file by adding program load address information and hook (setting) information to a symbol table in a host system, and transfers the relocatable object file to the target system. The symbol allocation address is determined according to the load address information, and the symbol hook processing is executed according to the hook information, and the symbol is allocated to the address on the target system designated by the user for each symbol of the program (Patent Document) 1).
JP 2002-132521 A (see paragraph 0061, FIG. 1)

  However, since the relocatable object file is expressed by a calculation formula each time an address unresolved section or unresolved symbol is referenced in the object, the capacity of the object file becomes larger than the absolute object file, and There has been a problem that the transfer time or the execution cycle period of the program loader increases.

  Accordingly, an object of the present invention is to provide a program loading apparatus and a program loading method for shortening the file transfer time to the target system or the execution cycle period of the program loader.

  In order to achieve the above object, the first feature of the present invention is, for example, a relocatable file storage device that stores a relocatable object file of a program, and data that transfers a relocatable object file read from the relocatable file storage device to a target system. Connected to the output unit, the section data storage device for storing the section table data transferred from the target system through the data input unit, the relocatable file storage device and the section data storage device, and read the relocatable object file and the section table data, A linker that generates an absolute object file of the program and an absolute file that stores the absolute object file generated by the linker And yl storage device, relocatable file storage device, section data storage device, and summarized in that a program loading device comprising a central processing unit for controlling the absolute file storage and linker, a.

  In order to achieve the above object, the second feature of the present invention is, for example, a relocatable file storage device that stores a relocatable object file of a program, and data that transmits a relocatable object file read from the relocatable file storage device to a target system. Absolute file storage device that stores the absolute object file of the program transferred from the output unit and the target system through the data input unit, and the absolute object file read from the absolute file storage device is transferred to the target system via the data output unit And a central processing unit for controlling a relocatable file storage device and an absolute file storage device. And summarized in that a Ingu device.

  In order to achieve the above object, the third feature of the present invention is that, for example, a central processing unit stores a source file of a program in a source file storage device, and a central processing unit from the source file storage device. Relocatable file storage process that stores the relocatable object file of the program compiled by reading the source file in the relocatable file storage device, and the central processing unit transfers the relocatable object file from the relocatable file storage device to the target system, and tests the relocatable object file Generated on the target system side when the central processing unit completes the test of the relocatable object file in the debugging process. An absolute file storage process for storing the absolute object file of the program to be stored in the absolute file storage device, a test process for the central processing unit to read the absolute object file from the absolute file storage device, transfer it to the target system, and test the program; A program loading method comprising:

  The program loading apparatus and the program loading method of the present invention have a special effect of shortening the file transfer time to the target system or the execution period of the program loader.

(First embodiment)
FIG. 1 is a block diagram of a program loading apparatus according to the first embodiment of the present invention.

  The program loading apparatus includes a host system 1 and a target system 47, transfers a relocatable object file created by the host system 1 to a random access memory 10 (hereinafter abbreviated as “RAM”) provided in the target system 47, The program loader 12 is operated to determine an unresolved address.

  The target system 47 is configured to transfer the section / symbol table 16 created by the program loader 12 to the host system 1 in accordance with a command from the host system 1.

  The host system 1 includes a relocatable file storage device 2, a section data storage device 3, an absolute file storage device 4, a linker 5, and a central processing unit 33 (hereinafter abbreviated as “CPU”). Connect to the output unit 7 to input / output command (command) input, debug processing, and program test status.

  The host system 1 is connected to the target system 47 through the data communication unit 9, the data output unit 18, and the data input unit 19, and executes transmission / reception of files, data, and commands.

  Here, a keyboard, a mouse pointer, a numeric keypad, and a touch panel can be adopted as the form of the input unit 8, and a display device or a printing device can be adopted as the form of the output unit 7.

    The target system 47 includes a RAM 10 and a CPU 34, and includes a relocatable object section data load unit 11, a program loader 12, a section / symbol table 16, and a section data storage device 15 after loading a program.

  The program loader 12 includes an unresolved address determination unit 13 and a section data load unit 14, and is configured to analyze the relocatable object section data load unit 11 and generate section data after loading.

  Here, the relocatable object format program stored in the relocatable file storage device 2 is not the final executable format of the program, but the section allocation address and symbol value are unresolved and the relocatable object format program is stored in the RAM 10 of the target system 47. This is a highly flexible program that arranges symbols at addresses corresponding to free states.

  In response to the command from the input unit 8, the CPU 33 transfers the relocatable object file (program) from the relocatable file storage device 2 to the RAM 10 on the target system 47 side through the data output unit 18.

  After the relocatable object file is transferred from the CPU 33 on the host system 1 side, a program loader start command is transmitted to the CPU 34 through the data communication unit 9, the program loader 12 is activated, and the load processing of the relocatable object section data load unit 11 is executed. To do.

  The CPU 34 on the target system 47 side operates the program loader 12 to store the section table data in the section / symbol table 16 and then transfers the section table data to the data input unit 19.

  The CPU 33 stores the transferred section table data in the section data storage device 3, gives the section table data to the linker 5, and stores the absolute object file linked to the relocatable object file stored in the relocatable file storage device 2 in the absolute file. Store in device 4.

  FIG. 2 is a flowchart of the program loading process used in the first embodiment of the present invention. The operation of the program loading apparatus will be described with reference to the block diagram of FIG. 1 and the flowchart of FIG.

  The CPU 34 operates the unresolved address determination unit 13 in the section address analysis step 20 (hereinafter, “step” is abbreviated as “ST”), and analyzes the section definition unit of the relocatable object section data load unit 11.

  If the CPU 34 determines in step ST21 that the section address is unresolved (YES), the CPU 34 branches to ST22, reserves the capacity defined by the “size” from the free area of the RAM 10 as a section data area, and this data area Is determined as a “section address”.

  On the other hand, if it is determined that the section address resolution is determined (NO) in determination ST21, the CPU 34 branches to ST23, and the capacity defined by “size” from the free area of the RAM 10 specified by “address” is set as section data. Secure as an area.

  Next, the CPU 34 shifts the process to ST24, registers the analysis result of the section definition section in the section / symbol table 16 in the RAM 10, advances to ST25, and determines whether or not the section definition section analysis ends. If the determination result is non (NO), the process returns to determination ST21, and if the determination result is good (YES), the process proceeds to the thimble definition analysis process ST26.

  The CPU 34 executes ST27 in the analysis process ST26, analyzes the symbol definition section, and calculates an address value using the address in the section table when the symbol value is given by an expression. Next, the process proceeds to ST28, and a symbol name and a symbol value are registered (stored) in the section symbol table 16 in the RAM 10.

  The CPU 34 advances the process to ST48 and determines whether or not the symbol definition unit analysis is finished. If the determination result is non (NO), the process returns to ST27, and if the determination result is good (YES), the process proceeds to the data part analysis process ST29.

  The CPU 34 executes ST30 in the analysis process ST29, analyzes the data definition unit (see FIG. 1), and loads data into the section area. When the load data is given by an expression, the CPU 34 calculates the data value using the symbol value, and stores the loaded section data in the RAM 10.

  The CPU 34 loads the value specified by the load data at the position specified by the offset from the head of each section at the stage of the load process. When the load data is a calculation formula that refers to an unresolved section address or an unresolved symbol, the load data is calculated using values in the section table 110 of FIG. 3 or the section / symbol table 114 of FIG.

  The CPU 34 advances the process to ST31 and determines whether or not the data part analysis is finished. If the determination result is non (NO), the process returns to ST30, and if the determination result is good (YES), the process proceeds to the data transfer process ST32.

  After loading all the section data, the CPU 34 executes a data transfer process ST32, transfers all the data in the section / symbol table 16 to the data input unit 19 on the host system 1, and ends the program loading process.

  The section / symbol table 16 includes a section table data storage area and a table size.

  FIG. 3 is a configuration diagram of the section table 110. The matrix table is provided with a section name column 35, a section size column 36, and a section address column 37, and all unresolved section addresses calculated in the process of ST23 (see FIG. 2) are stored.

  FIG. 4 is a configuration diagram of the section symbol table 114. The matrix table is provided with a symbol name field 38 and a symbol value field 39, and symbol values (for example, symbol value M1, symbol M3, unresolved symbol names in the relocatable object (for example, symbol M1, symbol M2, symbol M3)). All symbol values M2 and M3) are stored.

  The CPU 34 calculates, for example, the “symbol value” in the symbol value column 39 using the “address” in the section address column 37 shown in FIG. 3 (ST27 in FIG. 2), and stores it in the section / symbol table 16 in the RAM 10 ( The registration process ST24 in FIG. 2 is performed.

  FIG. 5 is a flowchart of a program development process for the target system 47 used in the first embodiment. The program development flow will be described with reference to the block diagram of FIG. 1 and the flowchart of FIG.

  The CPU 33 reads the program source file created in editing ST40 from the program storage device 17, compiles it in ST41, creates a relocatable object file, and stores it in the relocatable file storage device 2.

  The CPU 33 transfers the relocatable object file in the relocatable file storage device 2 to the target system 47, operates the program loader 12, and executes test and debug of the program (ST42).

  In the program modification / change determination ST43, the user can send a command to the CPU 33 using the input unit 8 and the output unit 7, and execute a program modification determination (NO) so as to repeat ST40 to ST42. .

  In the program modification / change determination ST43, the user transmits a determination (YES) result indicating that the program configuration is fixed to the CPU 33 using the input unit 8, and gives a program loading instruction.

  The CPU 33 gives the information of the section table data obtained from the target system 47 to the linker 5, relinks the relocatable object, and stores the absolute object file in the absolute file storage device 4 (ST44).

  The user loads the absolute object file stored in the absolute file storage device 4 to the target system 47 using a storage medium 98 such as a magnetic storage device or a flash memory, and executes a test or debug of the program in the absolute object format. (ST45).

  Of course, the load to the target system 47 may be transferred via the data output unit 18.

  The CPU 34 on the target system 47 side detects the loading of the program in the absolute object format, starts the program, and moves to the end of program development when the program test / debug completion determination (YES) is detected in the determination ST46. If it is determined that correction / change is necessary (NO), the process returns to ST40 to prompt the user to correct or change the program.

  FIG. 6 is a diagram showing a format of a relocatable object used in the first embodiment. The relocatable object 50 includes a section definition unit 57, a symbol definition unit 58, and a data unit 64, and is stored in the relocatable file storage device 2 (see FIG. 1).

  However, the present invention is not limited to this configuration, and there may be other parts in addition to the three types of parts.

  In the section definition section 57, a section name 51, a section size 52, and a section address 53 of each section in the program are defined. In the “section S2” of the second stage 55 in which the address is resolved, an absolute value address is designated as the section address 53. Such a section is defined as an absolute section.

  On the other hand, a section whose address has not been resolved (for example, a relocatable section) corresponds to “section S1” in the first stage 54 and “section S3” in the third stage 56. “None” and “None” are both described. A relocatable section may be defined in the relocatable object.

  The symbol definition unit 58 defines a symbol name 59 and a symbol value 60 of each symbol in the program. In the symbol value definition part of the “symbol M1” of the first stage 61 and the “symbol M3” of the third stage 63 in the relocatable section, a calculation formula representing the address of the section where the corresponding symbol is arranged Is defined.

  For example, using the variable R, the section index I, and the offset value V from the beginning of the section, the section symbol S is arranged at an address obtained by adding the offset value V to the variable R (I).

The calculation formulas M1 and M3 are
S = R (I) + V (1)
(1). Further, the symbol value of the symbol M2 in the absolute section of the second stage 62 is defined as an absolute value.

  In the data part 64, a definition part for each section data in the program is provided for each section. For example, a definition unit 65 of section S1, a definition unit 69 of section S2, and a definition unit 70 of section S3 are provided.

  The definition section 65 of the section S1 includes an offset 66 from the head address of each section and load data 67. In the definition of the load data 67, when referring to a relocatable section or an unresolved symbol, a calculation formula 68 using a variable representing a section address or a symbol value is described.

  The relocatable object can operate a program according to the availability of the RAM 10 of the target system 47. In addition, since it is not necessary for the program creator to perform address resolution at the time of compiling the program, it is effective when the code and data size of the program are dynamically changed in the early stage of program development.

(Second Embodiment)
FIG. 7 is a block diagram of a program loading apparatus according to the second embodiment of the present invention. The program loading apparatus includes the host system 1 and the target system 47 as in the first embodiment, and the description of the overlapping components is omitted.

  A relocatable file storage device 2 for storing a relocatable object format program file is provided inside the host system 1, and the relocatable object file is transferred to the RAM 10 of the target system 47 through the data output unit 18.

  In the RAM 10 of the target system 47, a relocatable object section data load unit 11 is provided. After transferring a relocatable object format program, a command is transmitted to the CPU 34 through the data communication unit 9, and the program loader 12a of the target system 47 is loaded. Start and load a relocatable object format program.

  The program loader 12a includes an unresolved address determination unit 13, a section data load unit 14, and a newly added absolute object creation unit 72 therein.

  The CPU 34 operates the absolute object creation unit 72 to generate an absolute object file 73 using the section data after loading stored in the section data storage device 15 and the information in the section symbol table 16.

  The CPU 34 stores the absolute object file 73 in the absolute file storage device 4 via the data input unit 19 on the host system 1 side.

  The CPU 34 can also simultaneously store the absolute object file 73 in the absolute file storage device 4 in order from the top data of the absolute object file 73 while generating the absolute object file 73. In this case, there is an advantage that the capacity of the RAM 10 of the target system 47 can be reduced.

  The host system 1 operates the CPU 33 to transfer the entire program in the absolute object format stored in the absolute file storage device 4 to the RAM 10 of the target system 47 via the load path 71 and the data output unit 18.

  The CPU 34 on the target system 47 side detects the loading of the program in the absolute object format, starts the program and terminates the program development when the program completion judgment is detected, and in the case of the program malfunction judgment, restarts the program development. Prompt.

  FIG. 8 is a flowchart showing an operation flow of the program loader 12a used in the second embodiment. The operation of the program loader 12a will be described with reference to the block diagram of FIG. 7 and the flowchart of FIG. First, in ST75, the unresolved address determination unit 13 in the program loader 12a analyzes the section definition unit (see FIG. 6) in the relocatable object format program in ST75.

  When the section address is unresolved (for example, “section S1”, “section S3”), the CPU 34 secures the size defined by the size from the free area of the RAM 10 as the section data area, and starts the head of the area. The address is determined as a section address.

  On the other hand, if the section address has been resolved (for example, “section S2”), the CPU 34 uses, as the section data area, an area for the size specified by the size from the address specified by the address from the free area of the RAM 10. Secure.

  In step ST76, the CPU 34 registers (or records) the analysis result of the section definition section in the section table 110 (see FIG. 3) on the RAM. Also in the second embodiment, the section table 110 illustrated in FIG. 3 and the section symbol table 114 illustrated in FIG. 4 can be used, so redundant description will be omitted.

  After analyzing the section definition portion and the symbol definition portion, the CPU 34 analyzes the data portion in the relocatable object and loads the data into the data area of each section by the section data load portion 14 in the program loader 12a ( ST77).

  In ST77, the CPU 34 loads the value specified by the load data to the position specified by the offset from the head of each section, as in the first embodiment.

  If the load data is a calculation formula referring to an unresolved section address or an unresolved symbol in ST78, the CPU 34 calculates the load data by using a value in the section table or symbol table, and creates a section definition section.

  In step ST79, the CPU 34 completes loading of all section data based on the information in the section definition section, completes the data definition section, and then proceeds to ST80.

  In ST80, the CPU 34 calculates the capacity of the storage area of the absolute object file 73. For example, it can be calculated from the number of sections registered in the section table data and the total section size.

  In ST80, the absolute object creation unit 72 in the program loader 12a secures a storage area for the absolute object file 73 in the RAM 10 and stores the generated absolute object file 73 in ST80.

  In ST80, the CPU 34 converts the data information in the section / symbol table 16 into a format corresponding to the section definition section in the absolute object file 73, transfers it to the storage area of the absolute object file 73, and completes the section definition section.

  After completion of the section definition section, the CPU 34 converts the section data after loading each section into a format corresponding to the data section in the absolute object file 73 and transfers it to the storage area of the absolute object file 73 to define the data. Complete the department.

  The CPU 34 operates the program loader 12a after completing the data definition section in ST80. The absolute object file can be transferred and stored in the absolute file storage device 4 through the data input unit 19 on the host system 1 side.

  Further, the data information of the section definition part and the data part constituting the absolute object file 73 may be transferred to the host system 1 side while being divided. In this case, there is an advantage that the capacity of the RAM 10 of the target system 47 can be afforded.

  When all the absolute object files 73 have been transferred, the program loading process can be terminated.

  FIG. 9 is a block diagram of the format conversion process of the absolute object file 73.

  The object data 85 is data obtained by the CPU 34 converting the data in the section table of the section / symbol table 16 into the format of the section definition unit 86 in the absolute object file 73. The section definition unit 86 includes a section name 87, a size 88, An address 89 is used.

  The loaded section data 15 a is data obtained by the CPU 34 converting the section data into the format of the data definition unit 90 inside the absolute object file 73.

  The section data 15a is converted from the head address 15b of the section S1 to data of absolute values S11, S12, and S13. The head address 15c of the section S2 is also converted to absolute value data, and the head address 15d of the section S3 is also the same. Has been converted to absolute value data.

  The data definition unit 90 of the absolute object file 73 writes the offset 91a and the load data 91b to the storage area corresponding to the section data 15a via the CPU 34.

  For example, the load data “absolute value S11” of “offset S11” corresponding to the head address 15b of the section S1 is written to the offset 91a via the CPU 34, and the load data “absolute value S12” of “offset S12” is stored in the CPU 34. The load data “absolute value S13” of “offset S13” is written via the CPU 34.

  Similarly, the “start address S2” 15c of the “section S2” 91c and the “start address S3” 15d of the “section S3” 91d are configured to be written by the CPU 34 with the offset and the absolute value associated with each other. Yes.

  FIG. 10 is a flowchart of program development used in the second embodiment. ST92, ST93, ST94, ST95, and ST97 are all the same as the source file editing ST40, compilation ST41, test / debug ST42, determination ST43, and determination ST46 of the first embodiment, and redundant description is omitted.

  In the second embodiment, the absolute object format program is loaded from the absolute file storage device 4 (see FIG. 7) to the target system 47 via the data output unit 18 (see FIG. 7), and then the test / debug ST96 is performed. Then, the CPU 34 on the target system 47 side activates the loaded program.

  The host system 1 according to the second embodiment executes the test and debug of the activated target system 47 side program via the data communication unit 9 using the input unit 8 and output unit 7 on the host system 1 side. Since this is different from the first embodiment, it is advantageous over the first embodiment in that the linker 5 (see FIG. 1) and the section data storage device 3 (see FIG. 1) are not required.

  According to the program loader 12 or 12a as described above, the target system 47 receives a relocatable object file and determines an unresolved address, thereby performing simple debugging without using a special device such as ICE. be able to.

  Further, the program loaders 12 and 12a can determine the arrangement address of each symbol from the load address information of each symbol of the relocatable object file, and can perform section data processing after loading.

  Furthermore, by creating a symbol table, the program loaders 12 and 12a can easily perform simple debugging without using a detailed symbol arrangement on the target system 47 for each symbol or using a special device such as ICE. The debugging efficiency of the target system 47 can be improved.

  In addition, since the absolute object format program from which excess data is deleted from the host system 1 is transferred to the target system 47, the transfer speed is improved and the RAM capacity of the target system 47 can be reduced.

  Note that the actions and effects described in the embodiments of the present invention only list the most preferable actions and effects resulting from the present invention, and the actions and effects according to the present invention are described in the embodiments of the present invention. It is not limited to what was done.

1 is a block diagram of a program loading apparatus according to a first embodiment of the present invention. The flowchart of the program loading process used for 1st Embodiment. The block diagram of the section table used for each embodiment. The block diagram of the section table used for each embodiment. The flowchart of the program development process used for 1st Embodiment. The format of the relocatable object used in the first embodiment. The block diagram of the program loading apparatus which concerns on the 2nd Embodiment of this invention. The flowchart of the program loading process used for 2nd Embodiment. The block diagram of the format conversion process used for 2nd Embodiment. The flowchart of the program development used for 2nd Embodiment.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 ... Host system 2 ... Relocatable file storage device 3 ... Section data storage device 4, 4a ... Absolute file storage device 5 ... Linker 7 ... Output part 8 ... Input part 9 ... Data communication part 10 ... Random access memory 11 ... Relocatable object section Data load unit 12, 12a ... Program loader 13 ... Unresolved address determination unit 14 ... Section data load unit 16 ... Section symbol table 17 ... Program storage device 18 ... Data output unit 19 ... Data input unit 33, 34 ... Central processing unit 47 ... Target system 71 ... Load path 72 ... Absolute object creation part 86 ... Section definition part 90 ... Data definition part 110 ... Section table 114 ... Section symbol table

Claims (5)

A relocatable file storage device for storing a relocatable object file of the program;
A data output unit for transferring a relocatable object file read from the relocatable file storage device to a target system;
A section data storage device for storing section table data transferred from the target system through a data input unit;
A linker that connects to the relocatable file storage device and the section data storage device, reads the relocatable object file and the section table data, and generates an absolute object file of the program;
An absolute file storage device for storing an absolute object file generated by the linker;
A central processing unit for controlling the relocatable file storage device, section data storage device, absolute file storage device and the linker;
A program loading apparatus comprising:   The central processing unit transfers a program loader start command input from an input unit to the target system through a data communication unit, starts a program loader in the memory of the target system, and outputs the data from the relocatable file storage device 2. The program loading apparatus according to claim 1, wherein a test result of the relocatable object file transferred through a central processing unit is output to an output unit connected to the central processing unit. A relocatable file storage device for storing a relocatable object file of the program;
A data output unit for transmitting a relocatable object file read from the relocatable file storage device to a target system;
An absolute file storage device for storing an absolute object file of a program transferred from the target system through a data input unit;
A load path for transferring the absolute object file read from the absolute file storage device to the target system via the data output unit;
A central processing unit for controlling the relocatable file storage device and the absolute file storage device;
A program loading apparatus comprising:   The central processing unit transfers a program loader start command input from an input unit to the target system through a data communication unit, starts a program loader in the memory of the target system, and outputs the data from the relocatable file storage device 4. The program loading device according to claim 3, wherein the test result of the relocatable object file transferred through a unit is output to an output unit connected to the central processing unit. A source file storage step in which a central processing unit stores a source file of a program in a source file storage device;
A relocatable file storage step of storing in the relocatable file storage device a relocatable object file of a program compiled by the central processing unit reading the source file from the source file storage device;
A debugging step in which the central processing unit transfers a relocatable object file from the relocatable file storage device to a target system, and tests and debugs the relocatable object file;
An absolute file storage step of storing an absolute object file of a program generated on the target system side in an absolute file storage device when the central processing unit completes the test of the relocatable object file in the debugging step;
A test step in which the central processing unit reads an absolute object file from the absolute file storage device, transfers it to the target system, and tests a program;
A program loading method comprising:

Images