A module configuration method and terminal supporting module data of multiple manufacturers

Abstract

The present invention discloses a module configuration method and terminal supporting module data from multiple manufacturers. The method pre-divides a delta partition into multiple sub-partitions. During the development phase of a product to be developed, the following steps are performed: obtaining the module manufacturer corresponding to the hardware device of the product to be developed; based on the obtained module manufacturer, copying the module data of the corresponding module data partition to the partition to be burned; transporting the module data of the partition to be burned to the DDR of a modem; assembling the modem's NV data based on the module data in the modem's DDR to obtain NV splicing data; comparing the obtained NV splicing data with the versions of the existing stored NV splicing data; if the obtained NV splicing data is newer, updating the NV configuration based on the obtained NV splicing data. By detecting the hardware manufacturer, the module data corresponding to the manufacturer is copied to the partition to be burned. During transport, only the data of the partition to be burned is transported, thereby meeting the configuration requirements of multiple modules from multiple module manufacturers.

Description

Technical Field

[0001] The present invention relates to the technical field of module configuration, and in particular to a module configuration method and a terminal supporting module data of multiple manufacturers. Background Art

[0002] Many existing mobile phones, POS terminals, and cash registers are developed based on domestic chip manufacturers. During the device development phase, different modules are often purchased from different manufacturers for patch integration. For example, manufacturers A, B, and C each have different hardware configurations, primarily manifesting in differences in hardware radio frequency and standards. Even when making the same module, each manufacturer may adjust parameters differently.

[0003] To this end, in the existing technology, the Spreadtrum platform has a mature single-software and multiple-hardware mechanism. This solution mainly obtains different ADC (Analog-to-digital converter) values ​​or different GPIO (General Purpose Input Output) combination values ​​corresponding to different hardware, and transparently transmits the rf_board (radio frequency board) id to the modem (modem) side. The modem side defaults to moving the first 128KB of the deltaNv partition to DDR (Double Data Rate, random access memory). After obtaining the data, it is assembled and obtained into hw_verxx.nv. By comparing with the value of nv_ver_flag, it decides whether to merge the hw_verxx.nv parameters. That is, it can be understood that a hw_verxx.nv configuration is a module configuration.

[0004] The deltanv partition is 1MB in size. The Unisoc platform supports up to 64 non-volatile (nv) configurations by default, which is generally sufficient. However, the Unisoc platform can only carry a maximum of 128KB of data. If the deltanvbin exceeds 128KB, data will be truncated when transferred to DDR. The deltanv is generated by the nvtool tool, which cannot check whether it exceeds 128KB. This tool often requires customers to check the size of the generated deltanv.bin file, which can easily lead to errors.

[0005] In actual project processes, the configuration of a single manufacturer's module reaches 128KB after being compressed into a delta-nv image. Therefore, the existing development platform cannot meet the configuration requirements of multiple modules from multiple module manufacturers. Summary of the Invention

[0006] The technical problem to be solved by the present invention is to provide a module configuration method and terminal that supports module data of multiple manufacturers, and can meet the configuration requirements of multiple modules of multiple module manufacturers.

[0007] In order to solve the above technical problems, the technical solution adopted by the present invention is:

[0008] A module configuration method supporting module data from multiple manufacturers, pre-dividing a delta partition into multiple sub-partitions, wherein the sub-partitions include a partition to be burned and multiple module data partitions corresponding to module manufacturers, wherein the module data partition stores the module data of the corresponding manufacturer, and the partition to be burned is a blank partition by default;

[0009] During the development phase of the product to be developed, the following steps are performed:

[0010] S1. Obtain the module manufacturer corresponding to the hardware device of the product to be developed;

[0011] S2. According to the module manufacturer information obtained, copy the module data of the corresponding module data partition to the partition to be burned;

[0012] S3, transfer the module data of the partition to be burned to the DDR of the modem;

[0013] S4, assembling the modem nv data according to the module data of the DDR of the modem to obtain nv splicing data;

[0014] S5. Compare the versions of the nv splicing data obtained in step S4 with the currently stored nv splicing data. If the nv splicing data obtained in step S4 is newer, update the nv configuration according to the nv splicing data obtained in step S4.

[0015] In order to solve the above technical problems, another technical solution adopted by the present invention is:

[0016] A module configuration terminal supporting module data of multiple manufacturers includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the following method is implemented:

[0017] The deltanv partition is pre-divided into multiple sub-partitions, wherein the sub-partitions include a partition to be burned and multiple module data partitions corresponding to a module manufacturer respectively, the module data partition stores the module data of the corresponding manufacturer, and the partition to be burned is a blank partition by default;

[0018] During the development phase of the product to be developed, the following steps are performed:

[0019] S1. Obtain the module manufacturer corresponding to the hardware device of the product to be developed;

[0020] S2. According to the module manufacturer information obtained, copy the module data of the corresponding module data partition to the partition to be burned;

[0021] S3, transfer the module data of the partition to be burned to the DDR of the modem;

[0022] S4, assembling the modem nv data according to the module data of the DDR of the modem to obtain nv splicing data;

[0023] S5. Compare the versions of the nv splicing data obtained in step S4 with the currently stored nv splicing data. If the nv splicing data obtained in step S4 is newer, update the nv configuration according to the nv splicing data obtained in step S4.

[0024] The beneficial effects of the present invention are: a module configuration method and terminal that supports module data from multiple manufacturers, which identifies and detects the manufacturer of hardware, selects the module data corresponding to the hardware manufacturer and copies it to the partition to be burned. During the transfer, only the data of the partition to be burned is transferred, thereby meeting the configuration requirements of multiple modules from multiple module manufacturers. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Figure 1 A flowchart of a module configuration method supporting module data from multiple manufacturers according to an embodiment of the present invention;

[0026] Figure 2 This is a structural diagram of a module configuration terminal supporting module data of multiple manufacturers according to an embodiment of the present invention.

[0027] Description of labels:

[0028] 1. A module configuration terminal that supports module data from multiple manufacturers; 2. A processor; 3. A memory. DETAILED DESCRIPTION

[0029] To illustrate the technical content, achieved objectives and effects of the present invention in detail, the following description is given in conjunction with the embodiments and accompanying drawings.

[0030] Please refer to Figure 1 A module configuration method supporting module data from multiple manufacturers, pre-dividing a deltanv partition into multiple sub-partitions, wherein the sub-partitions include a partition to be programmed and multiple module data partitions corresponding to module manufacturers, wherein the module data partitions store module data of the corresponding manufacturers, and the partition to be programmed is a blank partition by default;

[0031] During the development phase of the product to be developed, the following steps are performed:

[0032] S1. Obtain the module manufacturer corresponding to the hardware device of the product to be developed;

[0033] S2. According to the module manufacturer information obtained, copy the module data of the corresponding module data partition to the partition to be burned;

[0034] S3, transfer the module data of the partition to be burned to the DDR of the modem;

[0035] S4, assembling the modem nv data according to the module data of the DDR of the modem to obtain nv splicing data;

[0036] S5. Compare the versions of the nv splicing data obtained in step S4 with the currently stored nv splicing data. If the nv splicing data obtained in step S4 is newer, update the nv configuration according to the nv splicing data obtained in step S4.

[0037] From the above description, it can be seen that the beneficial effects of the present invention are: a module configuration method and terminal that supports module data from multiple manufacturers, which detects the manufacturer of the hardware and copies the module data corresponding to the manufacturer to the partition to be burned. During the transfer, only the data of the partition to be burned is transferred, thereby meeting the configuration requirements of multiple modules from multiple module manufacturers.

[0038] Furthermore, the partition to be burned is the first partition of the deltanv partition, and its size is consistent with the maximum data size carried by the development platform used in the development stage.

[0039] From the above description, it can be seen that the delta partition is fully utilized while ensuring development needs.

[0040] Furthermore, the size of the partition to be burned is specifically 128 KB.

[0041] As can be seen from the above description, it is suitable for development platforms that are widely used in existing technologies.

[0042] Furthermore, the deltanv partition also includes an extended partition located at the end of the deltanv partition.

[0043] From the above description, it can be seen that full utilization of the delta partition is achieved.

[0044] Furthermore, the step S1 specifically obtains the module manufacturer corresponding to the hardware device of the product to be developed by reading the product configuration table or the coreID value of the product to be developed.

[0045] From the above description, it can be seen that the module manufacturer corresponding to the hardware device is obtained.

[0046] A module configuration terminal supporting module data of multiple manufacturers includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the following method is implemented:

[0047] The deltanv partition is pre-divided into multiple sub-partitions, wherein the sub-partitions include a partition to be burned and multiple module data partitions corresponding to a module manufacturer respectively, the module data partition stores the module data of the corresponding manufacturer, and the partition to be burned is a blank partition by default;

[0048] During the development phase of the product to be developed, the following steps are performed:

[0049] S1. Obtain the module manufacturer corresponding to the hardware device of the product to be developed;

[0050] S2. According to the module manufacturer information obtained, copy the module data of the corresponding module data partition to the partition to be burned;

[0051] S3, transfer the module data of the partition to be burned to the DDR of the modem;

[0052] S4, assembling the modem nv data according to the module data of the DDR of the modem to obtain nv splicing data;

[0053] S5. Compare the versions of the nv splicing data obtained in step S4 with the currently stored nv splicing data. If the nv splicing data obtained in step S4 is newer, update the nv configuration according to the nv splicing data obtained in step S4.

[0054] From the above description, it can be seen that the beneficial effects of the present invention are: a module configuration method and terminal that supports module data from multiple manufacturers, which detects the manufacturer of the hardware and copies the module data corresponding to the manufacturer to the partition to be burned. During the transfer, only the data of the partition to be burned is transferred, thereby meeting the configuration requirements of multiple modules from multiple module manufacturers.

[0055] Furthermore, the partition to be burned is the first partition of the deltanv partition, and its size is consistent with the maximum data size carried by the development platform used in the development stage.

[0056] From the above description, it can be seen that the delta partition is fully utilized while ensuring development needs.

[0057] Furthermore, the size of the partition to be burned is specifically 128 KB.

[0058] As can be seen from the above description, it is suitable for development platforms that are widely used in existing technologies.

[0059] Furthermore, the deltanv partition also includes an extended partition located at the end of the deltanv partition.

[0060] From the above description, it can be seen that full utilization of the delta partition is achieved.

[0061] Furthermore, the step S1 specifically obtains the module manufacturer corresponding to the hardware device of the product to be developed by reading the product configuration table or the coreID value of the product to be developed.

[0062] From the above description, it can be seen that the module manufacturer corresponding to the hardware device is obtained.

[0063] The present invention is used for Android devices. For the whole terminal manufacturer, different modules from different module manufacturers will be attached. For example, manufacturer A has modules such as AM, WU, JP, and CN. These modules can represent the modules corresponding to the Americas region, the global region, the Japanese region, and the Chinese region respectively, and adapt to the configuration schemes of different modules from multiple different module manufacturers to support more different module configurations.

[0064] Please refer to Figure 1 , embodiment 1 of the present invention is:

[0065] In order to enable the whole machine to adapt to different modules from different module manufacturers, it is still based on the existing single-software and multiple-hardware solution of the Spreadtrum platform and is extended (the platform is limited to transferring 128KB), because the platform defaults to transferring the first 128KB of the partition to DDR.

[0066] Therefore, a module configuration method that supports module data from multiple manufacturers is provided, in which the deltanv partition is pre-divided into multiple sub-partitions, wherein the sub-partitions include a partition to be burned and multiple module data partitions corresponding to a module manufacturer respectively, wherein the partition to be burned is the first partition of the deltanv partition, and its size is consistent with the maximum data size handled by the development platform. It is a blank partition, and the module data partition stores the module data of the corresponding manufacturer.

[0067] Specifically, in this embodiment, the 1st to 128KB of the deltanv partition is the partition to be burned, xxxx_manufacturer_default_deltanv.bin; the 129th to 256KB is the first module data partition, xxxx_manufacturer_A_deltanv.bin, storing the module data of manufacturer A; the 257th to 384KB is the second module data partition, xxxx_manufacturer_B_deltanv.bin, storing the module data of manufacturer B; the 385th to 512KB is the third module data partition, xxxx_manufacturer_C_deltanv.bin, storing the module data of manufacturer C; and the 513th to 640KB is the fourth module data partition, xxxx_manufacturer_D_deltanv.bin, storing the module data of manufacturer D. As shown in Table 1 below:

[0068] Table 1

[0069]

[0070]

[0071] In this embodiment, an extended partition with a segment of 641KB-1MB is also included, which is used for future expansion.

[0072] During the development phase of the product to be developed, the following steps are performed:

[0073] S1. Obtain the module manufacturer corresponding to the hardware device of the product to be developed.

[0074] Specifically, in the U-boot (Universal Boot Loader) stage, the product configuration table or core (processor) ID value of the product to be developed is read to distinguish which module manufacturer and the value of rf_boardid.

[0075] S2. According to the module manufacturer information obtained, copy the module data of the corresponding module data partition to the partition to be burned.

[0076] S3. Move the module data of the partition to be burned to the DDR of the modem.

[0077] S4. Assembling the modem's nv data according to the DDR module data of the modem to obtain nv splicing data.

[0078] Specifically, the modem's nv data is assembled according to the module data of the DDR transferred to the modem, and according to the module value preset in the product matching table, the module value is obtained on the modem side and spliced ​​with hw_ver into nv splicing data hw_verxx.nv. Among them, the module value preset in the product matching table, in this embodiment, the AM module value corresponds to 1, and the WU module value corresponds to 2.

[0079] S5. Compare the versions of the nv splicing data obtained in step S4 with the currently stored nv splicing data. If the nv splicing data obtained in step S4 is newer, update the nv configuration according to the nv splicing data obtained in step S4.

[0080] Compare the size of nv_ver_flag with the terminal's nv_ver_flag. If it is larger than the terminal's, perform the merge item NV operation.

[0081] Please refer to Figure 2 , the second embodiment of the present invention is:

[0082] A module configuration terminal 1 supporting module data of multiple manufacturers includes a memory 3, a processor 2, and a computer program stored in the memory 3 and executable on the processor 2. When the processor 2 executes the computer program, the steps of the above-mentioned embodiment 1 are implemented.

[0083] In summary, the present invention provides a module configuration method and terminal that supports module data from multiple manufacturers. By detecting the manufacturer of the hardware, the module data corresponding to the manufacturer is copied to the partition to be burned. During the transfer, only the data of the partition to be burned is transferred, thereby meeting the configuration requirements of multiple modules from multiple module manufacturers.

[0084] The above descriptions are merely embodiments of the present invention and are not intended to limit the patent scope of the present invention. Any equivalent transformations made using the contents of the present invention's description and drawings, or directly or indirectly applied in related technical fields, are also included in the patent protection scope of the present invention.

Claims

1. A module configuration method supporting module data of multiple manufacturers, characterized in that: The deltanv partition is pre-divided into multiple sub-partitions, wherein the sub-partitions include a partition to be burned and multiple module data partitions corresponding to a module manufacturer respectively, the module data partition stores the module data of the corresponding manufacturer, and the partition to be burned is a blank partition by default; The partition to be burned is the first partition of the deltanv partition, and its size is consistent with the maximum data size transported by the development platform; During the development phase of the product to be developed, the following steps are performed: S1. Obtain the module manufacturer corresponding to the hardware device of the product to be developed; S2. According to the module manufacturer information obtained, copy the module data of the corresponding module data partition to the partition to be burned; S3, transfer the module data of the partition to be burned to the DDR of the modem; S4, assembling the modem nv data according to the module data of the DDR of the modem to obtain nv splicing data; S5. Compare the versions of the nv splicing data obtained in step S4 with the currently stored nv splicing data. If the nv splicing data obtained in step S4 is newer, update the nv configuration according to the nv splicing data obtained in step S4.

2. A module configuration method supporting module data of multiple manufacturers according to claim 1, characterized in that: The size of the partition to be burned is specifically 128KB.

3. The module configuration method supporting module data of multiple manufacturers according to claim 1, characterized in that: The deltanv partition also includes an extended partition located at the end of the deltanv partition.

4. The module configuration method supporting module data of multiple manufacturers according to claim 1, characterized in that: The step S1 specifically obtains the module manufacturer corresponding to the hardware device of the product to be developed by reading the product configuration table or the coreID value of the product to be developed.

5. A module configuration terminal supporting module data of multiple manufacturers, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the following method is implemented: The deltanv partition is pre-divided into multiple sub-partitions, wherein the sub-partitions include a partition to be burned and multiple module data partitions corresponding to a module manufacturer respectively, the module data partition stores the module data of the corresponding manufacturer, and the partition to be burned is a blank partition by default; The partition to be burned is the first partition of the deltanv partition, and its size is consistent with the maximum data size transported by the development platform; During the development phase of the product to be developed, the following steps are performed: S1. Obtain the module manufacturer corresponding to the hardware device of the product to be developed; S2. According to the module manufacturer information obtained, copy the module data of the corresponding module data partition to the partition to be burned; S3, transfer the module data of the partition to be burned to the DDR of the modem; S4, assembling the modem nv data according to the module data of the DDR of the modem to obtain nv splicing data; S5. Compare the versions of the nv splicing data obtained in step S4 with the currently stored nv splicing data. If the nv splicing data obtained in step S4 is newer, update the nv configuration according to the nv splicing data obtained in step S4.

6. The module configuration terminal supporting module data of multiple manufacturers according to claim 5, characterized in that: The size of the partition to be burned is specifically 128KB.

7. The module configuration terminal supporting module data of multiple manufacturers according to claim 5, characterized in that: The deltanv partition also includes an extended partition located at the end of the deltanv partition.

8. The module configuration terminal supporting module data of multiple manufacturers according to claim 5, characterized in that: The step S1 specifically obtains the module manufacturer corresponding to the hardware device of the product to be developed by reading the product configuration table or the coreID value of the product to be developed.

Images