Chip module upward integration method, electronic device and medium

Abstract

The present invention relates to the field of chip technology, and in particular to a chip component module upward integration method, electronic equipment and medium, the method comprising S1, in which a chip component module A is formed; i Build B in the code warehouse j i The original subdirectory C ij ; S2, store the code file to be integrated into C ij S3, determine the code file to be integrated in A i Is all the code in the code warehouse adapted? If so, directly change B j i Integrated into A i Otherwise, execute S4; S4, in the chip composition module A i Generate A directly in the code warehouse i Update code files and build B j i Replace subdirectory D ij , in A i Debugging incompatible BF in the code warehouse m ij Generate the corresponding replacement code file DF m ij And store it in D ij Medium; S5, based on C ij and D ij B j i Integrated into A i The present invention reduces the time required for upward integration of chip component modules and speeds up the development of the entire chip.

Description

Technical Field

[0001] The present invention relates to the field of chip technology, and in particular to a chip component module upward integration method, electronic equipment and medium. Background Art

[0002] A chip is composed of interconnected, hierarchical chip modules. A chip module is generated by combining its own code with the code it relies on. For a chip module with submodules, the code it relies on includes the code of its submodules. During the chip module design process, the code of the submodules of the chip module needs to be integrated into the chip module. The code of the submodules of the chip module is constantly updated. During the integration process, code from one version of the submodule of the chip module is required, but this may not necessarily be compatible with the chip module. If there is a mismatch, the submodule of the chip module needs to be updated within the submodule. After the update is complete, the submodule code of the chip module has typically been updated multiple times. The latest version of the submodule code of the chip module needs to be reintegrated into the chip module. If there is still a mismatch, the submodule code of the chip module needs to be updated within the submodule. This results in a lengthy upward integration process for the chip module, impacting the overall chip development progress. Therefore, reducing the time required for upward integration of the chip module and accelerating overall chip development progress has become a pressing technical challenge. Summary of the Invention

[0003] The present invention aims to provide a chip component module upward integration method, electronic equipment and medium, which reduces the process time of chip component module upward integration and speeds up the development progress of the entire chip.

[0004] According to a first aspect of the present invention, a method for upward integration of chip components and modules is provided, comprising:

[0005] Step S1: Chip composition module A i Build B in the code warehouse j i The original subdirectory C ij , B j i A i The jth submodule of A, the value of j ranges from 1 to f(i), f(i) is i The number of sub-modules, i ranges from 1 to 1, and 1 is the number of chip components containing sub-modules in the chip;

[0006] Step S2: B j i The code file to be integrated {BF1ij ,BF2 ij ,...,BF m ij ,...,BF M ij}Store to C ij In, BF m ij For B j i The corresponding mth code file to be integrated, the value range of m is 1 to M, M is B j i The corresponding number of code files to be integrated;

[0007] Step S3, determine {BF1 ij ,BF2 ij ,...,BF m ij ,...,BF M ij}In A i Is all the code in the code warehouse adapted? If so, directly based on {BF1 ij ,BF2 ij ,...,BF m ij ,...,BF M ij}B j i Integrated into A i Otherwise, execute step S4;

[0008] Step S4: Chip composition module A i Generate A directly in the code warehouse i Update code files and build B j i Replace subdirectory D ij , in A i Debugging incompatible BF in the code warehouse m ij Generate the corresponding replacement code file DF m ij And store it in D ij middle;

[0009] Step S5: Based on C ij and D ij B j i Integrated into A i middle.

[0010] According to a second aspect of the present invention, an electronic device is provided, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executed by the at least one processor, the instructions being configured to execute the method described in the first aspect of the present invention.

[0011] According to a third aspect of the present invention, a computer-readable storage medium is provided, storing computer-executable instructions, wherein the computer instructions are used to execute the method according to the first aspect of the present invention.

[0012] The present invention has significant advantages and beneficial effects compared to the prior art. By utilizing the above-mentioned technical solution, the present invention provides a chip component module-up integration method, electronic device, and medium that achieves considerable technological advancement and practicality, and has wide industrial application value, with at least the following beneficial effects:

[0013] In the process of upward integration of the sub-modules of the chip component module, the present invention first determines whether they are compatible with the chip component module. If there is an incompatibility, there is no need to return to the sub-module of the chip component module to update the code of the sub-module of the chip component module. Instead, a replacement sub-directory of the sub-module of the chip component module is constructed in the code warehouse of the chip component module, and the incompatible code files to be integrated are directly debugged in the code warehouse of the chip component module to generate corresponding replacement code files. Then, the sub-modules of the chip component module are integrated into the chip component module according to the code files to be integrated in the original sub-directory and the replacement code files in the replacement sub-directory, thereby reducing the process time of upward integration of the chip component module and accelerating the development progress of the entire chip. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0015] Figure 1 This is a flow chart of the chip component module upward integration method provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0016] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without making any creative efforts shall fall within the scope of protection of the present invention.

[0017] The embodiment of the present invention provides a chip component module upward integration method, such as Figure 1 Shown, including:

[0018] Step S1: Chip composition module A i Build B in the code warehouse j i The original subdirectory C ij , B j i A i The jth submodule of A, the value of j ranges from 1 to f(i), f(i) is i The value range of i is 1 to I, and I is the number of chip components containing sub-modules in the chip.

[0019] The code bin of the chip component module includes the environment code, design code, verification code, and preset process code of the corresponding version of the chip component module. The chip component module will generate multiple versions of code files during the development process, and each version corresponds to a code bin. i The code warehouse is the current A i The code repository corresponding to the version to be processed, B j i The original subdirectory refers to B j i The original subdirectory corresponding to the pending version. The environment code is mainly used to configure and manage the environment required for operation. The design code is the chip design code corresponding to the chip component module. The verification code is the chip verification code corresponding to the chip component module. The preset process code is the code required to execute the preset operation process corresponding to the chip component module.

[0020] As an embodiment, a chip component module includes a system on chip (SOC) component module, an IP (Intellectual Property) component module, a sub-system component module, and a block component module. A block component module is a chip component module that does not include sub-modules. The sub-modules of the SOC component module include one or more of the IP component module, the sub-system component module, and the block component module. The sub-modules of the IP component module include one or both of the sub-system component module and the block component module. The sub-modules of the sub-system component module include the block component module.

[0021] Taking the SOC component module including multiple IP component modules, the IP component module including multiple sub-system component modules, and the sub-system component module including multiple block component modules as an example, the chip module upward integration described in the embodiment of the present invention can specifically be the integration of the IP component module into the SOC component module, that is, A i For SOC component modules, B j i The chip module of the embodiment of the present invention may be integrated upwards into a sub-system module into an IP module. i IP component module, B j i The chip module of the embodiment of the present invention can be integrated upwards into a block module into a sub-system module. i For sub-system components, B j i Chip module upward integration specifically refers to the process of integrating the submodule code files of a chip component module into the code repository of the corresponding chip component module to generate the chip component module. The chip component module includes the code files of the chip component module itself and the code files of the submodules of the integrated chip component module.

[0022] Step S2: B j i The code file to be integrated {BF1 ij ,BF2 ij ,...,BF m ij ,...,BF M ij}Store to C ij In, BF m ij For B j i The corresponding mth code file to be integrated, the value range of m is 1 to M, M is B j i The corresponding number of code files to be integrated.

[0023] Step S3, determine {BF1 ij ,BF2 ij ,...,BF m ij ,...,BF M ij}In A i Is all the code in the code warehouse adapted? If so, directly based on {BF1ij ,BF2 ij ,...,BF m ij ,...,BF M ij}B j i Integrated into A i Otherwise, execute step S4.

[0024] It should be noted that if {BF1 ij ,BF2 ij ,...,BF m ij ,...,BF M ij}In A i If all the target code warehouses are adapted, you can directly base on {BF1 ij ,BF2 ij ,...,BF m ij ,...,BF M ij}B j i Integrated into A i In the case of {BF1 ij ,BF2 ij ,...,BF m ij ,...,BF M ij}In A i If the target code repository cannot be fully adapted, it cannot be directly integrated upward. It needs to be debugged and fully adapted before it can be integrated upward.

[0025] Step S4: Chip composition module A i Generate A directly in the code warehouse i Update code files and build B j i Replace subdirectory D ij , in A i Debugging incompatible BF in the code warehouse m ij Generate the corresponding replacement code file DF m ij And store it in D ij middle.

[0026] It should be noted that when {BF1 ij ,BF2 ij ,...,BF m ij ,...,BF Mij}In A i When all code bins cannot be adapted, it may be that the chip component module A i The code in the code warehouse needs to be debugged, or it may be {BF1 ij ,BF2 ij ,...,BF m ij ,...,BF M ij} need to be debugged, or both may need to be debugged. i When the code in the code warehouse needs to be debugged, it can be directly stored in A after debugging. i in the code repository.

[0027] Step S5: Based on C ij and D ij B j i Integrated into A i middle.

[0028] As an embodiment, step S4 includes:

[0029] Step S41, according to {BF1 ij ,BF2 ij ,...,BF m ij ,...,BF M ij}In A i Debugging the incompatible results in the code warehouse A i The code generates A i The updated code files are stored in A i in the code repository.

[0030] Step S42: Build B j i Replace subdirectory D ij , in A i Debugging incompatible BF in the code warehouse m ij Generate the corresponding replacement code file DF m ij And store it in D ij middle.

[0031] It should be noted that the unsuitable BF m ij There may be one or more BFs. Each BF that is not compatible is debugged in step S41. m ij Generate the corresponding replacement code file DF m ij.

[0032] As an embodiment, step S5 includes:

[0033] Step S51: i Set B in the code warehouse j i The corresponding replacement configuration table {E1 ij ,E2 ij ,...,E n ij ,...,E N ij}, E n ij For B j i The nth replacement configuration information in the corresponding replacement configuration table, where n ranges from 1 to N, and N is B j i The total number of corresponding replacement configuration information, E n ij Including E1 n and E2 n , E1 n For the file to be replaced in A i The original code file path in the code warehouse, E2 n For the file to be replaced in A i The replacement code file path in the code repository.

[0034] Step S52: Analyze B j i Corresponding replacement configuration table, get each E n ij Corresponding E1 n and E2 n .

[0035] Step S53: Based on E2 n From D ij Get E2 n The corresponding replacement code file, C ij Middle E1 n The corresponding code file to be integrated is replaced with E2 n Corresponding replacement code file, if E2 n The corresponding replacement code file is E1 n If the read and write properties of the corresponding code files to be integrated are inconsistent, E1 n The corresponding read and write attributes of the replaced code file are changed to E1 n The read and write properties of the corresponding code file to be integrated.

[0036] It should be noted that in the process of generating the replacement code file, the read-write attributes of the file may change. For example, the original code file is read-only, but the generated replacement code file is read-write. In order to maintain consistency, the read-write attributes of the file will be changed to the read-write attributes of the original code file after the replacement is completed.

[0037] Step S54: B j i All E in the corresponding replacement configuration table n ij After the corresponding replacement operation is completed, the code file to be integrated is integrated into A i middle.

[0038] It should be noted that B j i All E in the corresponding replacement configuration table n ij After the corresponding replacement operation is completed, the code file to be integrated can adapt to A i The code warehouse, so B can be j i All E in the corresponding replacement configuration table n ij After the corresponding replacement operation is completed, the code file to be integrated is integrated into A i So it does not affect A i development progress.

[0039] As an example, E n ij It also includes user identification, replacement time and replacement reason information. By storing the above information, subsequent tracking and debugging can be further facilitated.

[0040] B j i All E in the corresponding replacement configuration table n ij After the corresponding replacement operation is completed, the code file to be integrated is integrated into A i After that, the corresponding update information needs to be synchronized to B j i As an example, E n ij Also includes the files to be replaced in B j i Corresponding file path, said step S54 further includes:

[0041] Step S6: According to E n ij The file to be replaced is in B j i Corresponding file path and E2 nThe corresponding replacement code file is updated B j i Code warehouse.

[0042] Step S7: A i In the code warehouse B j i Corresponding D ij and B j i The corresponding replacement configuration table is deleted.

[0043] It should be noted that, in step S6, E2 n The corresponding replacement code file is updated to B j i The code warehouse does not need to be in B j i After the update, A is promptly updated in step S7. i In the code warehouse B j i Corresponding D ij and B j i The corresponding replacement configuration table is deleted to avoid A i impact on subsequent development.

[0044] As an embodiment, step S6 includes:

[0045] Step S61: E2 n The corresponding replacement code file and the file to be replaced are in B j i The corresponding file path is sent to B j i Code warehouse.

[0046] Step S62: E2 n The corresponding replacement code file is updated to B j i The file to be replaced in the code warehouse is in B j i The corresponding file path.

[0047] As an embodiment, step S62 includes:

[0048] Step S621: Determine the updated E2 n The corresponding replacement code file and the current B j i Whether there is a conflict in the code files in the code warehouse, if so, determine the conflict and then execute step S622, otherwise, directly execute step S622.

[0049] Step S622: Update E2n The corresponding replacement code file and the current version of B j i The code files are integrated and j i The latest version of the code file is generated in the code warehouse.

[0050] It should be noted that the fusion process will exist in E2 n The corresponding replacement code file but does not exist in the current version of B j i The code files in the code file are retained and will exist in the current version of B j i code file and does not exist in E2 n The corresponding replacement code file is retained, and E2 n The corresponding replacement code file and the current version of B j i The common parts of the code files are kept, and if there is a conflict, the parameters after the conflict selection are kept.

[0051] It should be noted that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although the flowcharts describe the steps as sequential processes, many of the steps can be performed in parallel, concurrently, or simultaneously. In addition, the order of the steps can be rearranged. A process can be terminated when its operation is completed, but can also have additional steps not included in the accompanying drawings. A process can correspond to a method, function, procedure, subroutine, subprogram, etc.

[0052] An embodiment of the present invention also provides an electronic device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executed by the at least one processor, and the instructions are configured to execute the method described in the embodiment of the present invention.

[0053] An embodiment of the present invention further provides a computer-readable storage medium storing computer-executable instructions, wherein the computer instructions are used to execute the method described in the embodiment of the present invention.

[0054] In the process of upward integration of the sub-modules of the chip component module, the embodiment of the present invention first determines whether it is compatible with the chip component module. If there is an incompatibility, there is no need to return to the sub-module of the chip component module to update the code of the sub-module of the chip component module. Instead, a replacement sub-directory of the sub-module of the chip component module is constructed in the code warehouse of the chip component module, and the incompatible code files to be integrated are directly debugged in the code warehouse of the chip component module to generate corresponding replacement code files. Then, the sub-modules of the chip component module are integrated into the chip component module according to the code files to be integrated in the original sub-directory and the replacement code files in the replacement sub-directory, thereby reducing the process time of upward integration of the chip component module and accelerating the development progress of the entire chip.

[0055] The above description is merely a preferred embodiment of the present invention and does not constitute any form of limitation to the present invention. Although the present invention has been disclosed as a preferred embodiment, it is not intended to limit the present invention. Any technician familiar with the present profession can make slight changes or modifications to equivalent embodiments using the technical contents disclosed above without departing from the scope of the technical solution of the present invention. However, any simple modifications, equivalent changes and modifications made to the above embodiments based on the technical essence of the present invention without departing from the content of the technical solution of the present invention are still within the scope of the technical solution of the present invention.

Claims

1. A chip component module upward integration method, characterized in that: include: Step S1: Chip composition module A i Build B in the code warehouse j i The original subdirectory C ij , B j i A i The jth submodule of A, the value of j ranges from 1 to f(i), f(i) is i The number of sub-modules, i ranges from 1 to 1, and 1 is the number of chip components containing sub-modules in the chip; The chip component module generates multiple versions of code files during the development process, each version corresponds to a code warehouse. i The code warehouse is the current A i The code repository corresponding to the version to be processed, B j i The original subdirectory refers to B j i The original subdirectory corresponding to the version to be processed; Step S2: B j i The code file to be integrated {BF1 ij ,BF2 ij ,...,BF m ij ,...,BF M ij }Store to C ij In, BF m ij For B j i The corresponding mth code file to be integrated, the value range of m is 1 to M, M is B j i The corresponding number of code files to be integrated; Step S3, determine {BF1 ij ,BF2 ij ,...,BF m ij ,...,BF M ij }In A i Is all the code in the code warehouse adapted? If so, directly based on {BF1 ij ,BF2 ij ,...,BF m ij ,...,BF M ij }B j i Integrated into A i Otherwise, execute step S4; Step S4: Chip composition module A i Generate A directly in the code warehouse i Update code files and build B j i Replace subdirectory D ij , in A i Debugging incompatible BF in the code warehouse m ij Generate the corresponding replacement code file DF m ij And store it in D ij middle; Step S4 include: Step S41, according to {BF1 ij ,BF2 ij ,...,BF m ij ,...,BF M ij }In A i Debugging the incompatible results in the code warehouse A i The code generates A i The updated code files are stored in A i In the code warehouse; Step S42: Build B j i Replace subdirectory D ij , in A i Debugging incompatible BF in the code warehouse m ij Generate the corresponding replacement code file DF m ij And store it in D ij middle; Step S5: Based on C ij and D ij B j i Integrated into A i middle.

2. The method according to claim 1, characterized in that The code repository of the chip component module includes the environment code, design code, verification code, and preset process code corresponding to the chip component module.

3. The method according to claim 1, characterized in that The step S5 comprises: Step S51: i Set B in the code warehouse j i The corresponding replacement configuration table {E1 ij ,E2 ij ,...,E n ij ,...,E N ij }, E n ij For B j i The nth replacement configuration information in the corresponding replacement configuration table, where n ranges from 1 to N, and N is B j i The total number of corresponding replacement configuration information, E n ij Including E1 n and E2 n , E1 n For the file to be replaced in A i The original code file path in the code warehouse, E2 n For the file to be replaced in A i The replacement code file path in the code warehouse; Step S52: Analyze B j i Corresponding replacement configuration table, get each E n ij Corresponding E1 n and E2 n ; Step S53: Based on E2 n From D ij Get E2 n The corresponding replacement code file, C ij Middle E1 n The corresponding code file to be integrated is replaced with E2 n Corresponding replacement code file, if E2 n The corresponding replacement code file is E1 n If the read and write properties of the corresponding code files to be integrated are inconsistent, E1 n The corresponding read and write attributes of the replaced code file are changed to E1 n The read and write properties of the corresponding code file to be integrated; Step S54: B j i All E in the corresponding replacement configuration table n ij After the corresponding replacement operation is completed, the code file to be integrated is integrated into A i middle.

4. The method according to claim 3, characterized in that E n ij It also includes user identification, replacement time and replacement reason information.

5. The method according to claim 4, characterized in that E n ij Also includes the files to be replaced in B j i Corresponding file path, said step S54 further includes: Step S6: According to E n ij The file to be replaced is in B j i Corresponding file path and E2 n The corresponding replacement code file is updated B j i Code warehouse; Step S7: A i In the code warehouse B j i Corresponding D ij and B j i The corresponding replacement configuration table is deleted.

6. The method according to claim 5, characterized in that The step S6 comprises: Step S61: E2 n The corresponding replacement code file and the file to be replaced are in B j i The corresponding file path is sent to B j i Code warehouse; Step S62: E2 n The corresponding replacement code file is updated to B j i The file to be replaced in the code warehouse is in B j i The corresponding file path.

7. The method according to claim 1, characterized in that The chip component modules include SOC component modules, IP component modules, sub-system component modules, and block component modules. The sub-modules of the SOC component modules include one or more of the IP component modules, sub-system component modules, and block component modules. The sub-modules of the IP component modules include one or two of the sub-system component modules and block component modules. The sub-modules of the sub-system component modules include block component modules.

8. An electronic device, characterized in that: include: at least one processor; and, a memory communicatively coupled to the at least one processor; The memory stores instructions to be executed by the at least one processor, wherein the instructions are configured to execute the method according to any one of claims 1 to 7.

9. A computer-readable storage medium, characterized in that The computer-executable instructions are stored, and the computer-executable instructions are used to execute the method according to any one of the preceding claims 1 to 7.

Images