Executable software object code translation and upload authorization method
By generating and automatically verifying binary file names and information, the problem of low efficiency and low accuracy of manual verification in online uploading of software target code is solved, realizing an efficient and accurate automated verification and uploading process.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- 贵州航天控制技术有限公司
- Filing Date
- 2026-01-30
- Publication Date
- 2026-06-09
AI Technical Summary
In the current online upload process of software target code, manual verification is inefficient and cannot guarantee accuracy, which can easily lead to version errors and status errors.
By generating binary filenames containing key information and using compilation tools to generate target files, converting them into binary files, and automatically verifying filenames and information, we ensure that all information is completely correct before uploading.
It achieves high efficiency in verifying software target code information and ensures the correctness of uploaded data, improving the accuracy and efficiency of automated approval and avoiding the inefficiency and errors of manual approval.
Smart Images
Figure CN122173091A_ABST
Abstract
Description
Technical Field
[0001] This invention belongs to the technical field of online software uploading, specifically relating to a method for converting and uploading executable software target code for approval. Background Technology
[0002] Online software upload technology has been around for a long time. Its main purpose is to replace emulator-based software uploading when software needs to be rewritten or updated, thus avoiding the need to open or disassemble sealed or finished products and damage their hardware. However, any software uploading or update requires verification of the correctness of the software target code, which necessitates checking the correctness of the software target code.
[0003] Traditionally, verifying information about software target code relies primarily on manual methods, checking the name, date, and size of the target code. However, most software versions, and even different software versions, use the compiler's default names for their target code, meaning the names are identical. Therefore, the main focus is on verifying the modification date and size. In recent years, some regions have implemented MD5 hash verification, but this requires specialized MD5 generation and comparison tools. Nevertheless, all of these verification processes still require manual work, which is inefficient and prone to errors due to oversight, leading to problems such as version and status errors in the uploaded software. Summary of the Invention
[0004] The purpose of this invention is to provide a method for converting and uploading executable software object code for approval, so as to solve the technical problems of low efficiency and inability to guarantee accuracy in existing manual approval processes.
[0005] To achieve the above objectives, the present invention adopts the following technical solution: A method for converting and uploading executable software target code for approval includes: generating a binary filename for the software target code, wherein the filename includes key information of the software target code; using a compiler to generate a target file for the software target code and converting the target file into a binary file; and automatically verifying the filename and information of the binary file during software upload.
[0006] A computer-readable storage medium storing a computer program, wherein the computer program is configured to execute the above-described executable software object code conversion and upload approval method at runtime.
[0007] An electronic device includes a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the executable software object code conversion and upload approval method via the computer program.
[0008] In this invention, an online upload verification process is implemented using interface software programming. The executable software file is converted into a binary file according to a specified data protocol. This binary file is named according to a specified format and serves as the final online upload target code. Before uploading, users input verification information into the interface. Each piece of information is automatically compared one by one with the information in the binary file during the online upload verification process. Only after all information is completely correct can the online upload process begin. This solves the technical problems of low efficiency and unreliable accuracy associated with existing manual verification methods, achieving both high efficiency in software target code information verification and guaranteed upload accuracy. Attached Figure Description
[0009] Figure 1 This is a flowchart illustrating a method for converting and uploading executable software target code for approval, as described in an embodiment of the present invention. Figure 2 This is a schematic diagram of the process for generating binary file names of executable software target code in an embodiment of the present invention, which describes a method for converting and uploading executable software target code for approval. Figure 3 This is a schematic diagram of the automatic approval process for binary target code information in an embodiment of the present invention, which describes a method for converting and uploading executable software target code for approval. Figure 4 This is a schematic diagram of the structure of an executable software target code conversion and upload approval system according to an embodiment of the present invention. Detailed Implementation
[0010] The present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments. The advantages and features of the present invention will become clearer from the following description and claims. It should be noted that the drawings are all in a very simplified form and are not to a precise scale, and are only used to facilitate and clarify the illustration of the embodiments of the present invention.
[0011] It should be noted that, in order to clearly illustrate the content of this invention, several embodiments are provided to further explain different implementations of the invention. These embodiments are enumerated rather than exhaustive. Furthermore, for the sake of brevity, content mentioned in the preceding embodiments is often omitted in the following embodiments. Therefore, content not mentioned in the later embodiments can be referred to in the preceding embodiments.
[0012] Example 1 A method for converting and uploading executable software object code for approval, such as Figure 1 As shown, the method includes: S102, Generate the binary filename of the software target code, wherein the filename includes key information of the software target code; S104 uses compiler tools to generate object files for the software's target code and converts the object files into binary files; S106 automatically verifies the filename and information of the binary file during software upload.
[0013] As an optional implementation, key information includes: the project code name to which the software belongs, the date the binary file was generated, and the software version number.
[0014] As an optional implementation, generating the binary filename of the software target code includes: obtaining the input project code and software version number of the software; automatically capturing the current actual system time as the binary file generation date; and generating the binary filename based on the project code, software version number, and binary file generation date.
[0015] As an optional implementation, converting the target file into a binary file includes: extracting the data information of the target file and converting it into a binary file containing the target code address, length, and code data.
[0016] As an optional implementation, after converting the target file into a binary file, the method also includes recording the file name, file size, modification time, and MD5 hash of the binary file.
[0017] As an optional implementation, after converting the target file into a binary file, the method further includes storing the binary file and the target file in a database.
[0018] As an alternative implementation, binary files are extracted from the database during software upload.
[0019] As an optional implementation, the filename and information of the binary file are automatically checked, including: automatically calculating the MD5 code of the binary file and comparing it with the input MD5 code.
[0020] As an optional implementation, the filename and various information of the binary file are automatically verified, including: obtaining the project code, software version number, file size, and modification time of the input software, and comparing and verifying them with the binary file.
[0021] As an optional implementation, after automatically verifying the filename and information of the binary file, the method further includes: if all information of the binary file is verified to be correct, reading the binary file frame by frame and uploading it.
[0022] Specifically, the above-mentioned method for converting and uploading executable software target code for approval is not limited to the following steps: The first step is to generate the name of the software target code binary file.
[0023] The software uploads and approves the generated binary target code file name, which contains key information. The information included in the binary target code file name is not limited to: the software's project codename, the date the binary target code file was generated, and the software version number. Among this information, the project codename and version number are not limited to manual input, and the file generation date is not limited to automatically capturing the current system time (year, month, day, hour, minute, second) through the software's online upload and approval module. The steps for generating the software target code binary file name are not limited to... Figure 2 As shown, enter the project code, enter the software version number, and automatically obtain the system time to create a binary file containing the above information.
[0024] The second step is to convert the software target code into a binary file.
[0025] Select the target file generated by the compiler tool, such as a .out target file generated using CCS or IAR. Upload the file online using approved software to automatically extract the target file information generated by the compiler tool, and then convert it into a binary file containing information such as target code addresses, length, and code data.
[0026] After the binary file is generated, its filename, size, modification time, and MD5 hash are recorded and stored in the database along with the target file generated by the compilation tool. Subsequent online software uploads will directly retrieve this binary file from the database and automatically verify its filename, size, modification time, MD5 hash, and other information using the online upload verification module. Once all information is confirmed to be correct, the file will be uploaded online.
[0027] The third step is to automatically verify the binary target code information during software upload.
[0028] During online software upload, the online upload verification module automatically checks various information of the binary file, including filename, file size, modification time, and MD5 hash. The filename includes information such as the project code, target code modification time, and software version number. This information is manually entered by the online upload verification module for verification. During automatic verification, the module automatically calculates the MD5 hash of the binary file and compares it with the input MD5 hash. Once all target code information is verified correctly, the online upload process automatically begins, reading and uploading the binary file frame by frame; otherwise, the online upload is not executed. The automatic verification process for binary target code information during software upload is not limited to the following... Figure 3As shown, input the project code, software version number, binary file modification time, file size, and binary file MD5 hash, and the system will automatically compare the information. If all information is correct, the online software upload process will start automatically. If any information is incomplete or incorrect, the online software upload process will terminate.
[0029] Optionally, during the processes of generating the binary file name for the software target code, converting the software target code into a binary file, and automatically verifying the binary target code information during software upload, the input of the project code and version number during binary file name generation, and the input of the project code, software version number, file size, modification time, and MD5 code during the automatic verification of binary target code information, can be manually entered or copied from electronic inventory slips, etc. The remaining steps are all automatically completed by the software online uploading and verification, which improves efficiency compared to the traditional manual verification method.
[0030] Optionally, during the online upload of the software target code, the project code, version number, file size, modification time, and MD5 code are all automatically checked one by one by the online software upload verification. Only after all the information has been completely verified to be correct will the online upload process begin, thus fully ensuring the correctness of the uploaded software target code.
[0031] In this embodiment, an online upload approval process is implemented using interface software programming. The executable software file is converted into a binary file according to a specified data protocol. This binary file is named according to a specified format and serves as the final online upload target code. Before uploading, users input information such as the project code, target code modification time, version number, and MD5 hash of the software to be uploaded into the interface. This information is automatically and systematically compared with the binary file information through the online upload approval process. Only after all information is completely correct can the online upload process begin, ensuring the correctness of the online software upload. The online upload approval process using programming software guarantees the efficiency of software target code information verification and the correctness of the upload.
[0032] Example 2 An executable software object code conversion and upload approval system, such as Figure 4 As shown, the system includes: The generation unit 402 is used to generate binary filenames for the software target code, wherein the filenames include key information of the software target code; The conversion unit 404 is used to generate object files of software object code using compilation tools, and convert the object files into binary files; The approval unit 406 is used to automatically verify the filename and information of the binary file when the software is uploaded.
[0033] Optionally, the above key information includes: the project code name to which the software belongs, the date the binary file was generated, and the software version number.
[0034] Optionally, the above-mentioned generation unit 402 generates the binary file name of the software target code, including: obtaining the input project code and software version number of the software; automatically capturing the current actual system time as the binary file generation date; and generating the binary file name based on the project code, software version number, and binary file generation date.
[0035] Optionally, the conversion unit 404 converts the target file into a binary file, including: extracting the data information of the target file and converting it into a binary file containing the target code address, length, and code data.
[0036] Optionally, the executable software target code conversion and upload approval system mentioned above also includes a recording unit, which records the file name, file size, modification time and MD5 code of the binary file after the target file is converted into a binary file.
[0037] Optionally, the executable software target code conversion and upload approval system mentioned above also includes a storage unit for converting the target file into a binary file and then storing the binary file and the target file in a database.
[0038] Optionally, the executable software object code conversion and upload approval system described above extracts binary files from the database during software upload.
[0039] Optionally, the approval unit 406 automatically verifies the filename and information of the binary file, including automatically calculating the MD5 code of the binary file and comparing it with the input MD5 code.
[0040] Optionally, the aforementioned approval unit 406 automatically verifies the filename and various information of the binary file, including: obtaining the input project code, software version number, file size, and modification time of the software, and comparing and verifying them with the binary file.
[0041] Optionally, the aforementioned executable software target code conversion and upload approval system automatically verifies the filename and information of the binary file, and then, if all information in the binary file is verified to be correct, reads and uploads the binary file frame by frame.
[0042] In this embodiment, an online upload verification process is implemented using interface software programming. The executable software file is converted into a binary file according to a specified data protocol. This binary file is named according to a specified format and serves as the final online uploaded software target code. Before uploading, users input verification information into the interface. Each piece of information is automatically compared one by one with the information in the binary file during the online upload verification process. Only after all information is completely correct can the online upload process begin. This solves the technical problems of low efficiency and unreliable accuracy associated with existing manual verification methods, achieving both high efficiency in software target code information verification and guaranteed upload accuracy.
[0043] Example 3 In another aspect, the present invention provides an electronic device for implementing the above-described executable software object code conversion and upload approval method. This electronic device is not limited to a terminal device or server within a system. The electronic device includes, but is not limited to, a memory and a processor. The memory stores a computer program, and the processor is configured to execute the steps of any of the above method embodiments via the computer program.
[0044] Example 4 In another aspect, the present invention provides a computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the methods provided in various optional embodiments of the executable software object code conversion and upload approval method described above. The computer program is configured to execute the steps in any of the above method embodiments at runtime.
Claims
1. A method for converting and uploading executable software object code for approval, characterized in that, include: Generate a binary filename for the software target code, wherein the filename includes key information about the software target code; The compiler generates object files for the software's target code and then converts these object files into binary files. When uploading the software, the filename and other information of the binary file are automatically verified.
2. The executable software object code conversion and upload approval method as described in claim 1, characterized in that, The key information includes: the project code name to which the software belongs, the date the binary file was generated, and the software version number.
3. The executable software object code conversion and upload approval method as described in claim 2, characterized in that, The binary filename for the generated software object code includes: Obtain the project code and software version number of the input software; Automatically capture the current system time as the binary file generation date; Generate binary filenames based on the project code name, software version number, and binary file generation date.
4. The executable software object code conversion and upload approval method as described in claim 1, characterized in that, Converting the target file into a binary file includes: extracting the data information from the target file and converting it into a binary file containing the target code address, length, and code data.
5. The executable software object code conversion and upload approval method as described in claim 1, characterized in that, After converting the target file into a binary file, the process also includes recording the binary file's filename, file size, modification time, and MD5 hash.
6. The executable software object code conversion and upload approval method as described in claim 1, characterized in that, After converting the target file into a binary file, the process also includes storing the binary file and the target file in a database.
7. The executable software object code conversion and upload approval method as described in claim 6, characterized in that, When uploading the software, the binary file is extracted from the database.
8. The executable software object code conversion and upload approval method as described in claim 1 or 5, characterized in that, Automatically verify the filename and information of binary files, including automatically calculating the MD5 hash of the binary file and comparing it with the input MD5 hash.
9. The executable software object code conversion and upload approval method as described in claim 1, characterized in that, Automatically verify the filename and information of the binary file, including: obtaining the project code of the software, the software version number, the file size, and the modification time, and comparing and verifying them with the binary file.
10. The executable software object code conversion and upload approval method as described in claim 1, characterized in that, After automatically verifying the filename and information of the binary file, the process also includes: reading and uploading the binary file frame by frame, provided that all information in the binary file has been verified to be correct.