Disclosure of Invention
In order to solve the problems that a consignor cannot customize different firmware contents and cannot control the whole quality control process in the universal module assembling and testing process, the invention aims to provide a cloud management universal module assembling and testing method.
The invention provides a cloud management universal module installing and testing method, which comprises the following steps:
After the patch obtains the universal module, using a burning tool to burn basic firmware information into the universal module;
Uploading a production plan customized by a consignor for the universal module to a cloud database, wherein the production plan comprises the complement firmware information and the code writing test information of the universal module, and the complement firmware information comprises firmware version information and serial number range information;
downloading the complement firmware information of the universal module from the cloud database by using a cloud burning tool by a producer, and burning the complement firmware information into the universal module;
And downloading the code writing test information of the universal module from the cloud database by using a cloud production testing tool by a producer, and writing the code writing test information into the universal module to obtain a code writing test result.
Based on the above summary, on one hand, the conventional module burning mode is split into two parts: on the other hand, after the basic firmware information is burned, the consignor issues a customized production plan to the cloud end, so that when receiving the production plan, a producer can execute customized test tasks comprising a firmware complement process and a code writing test process according to the bill, and therefore, the consignor can customize different firmware contents according to different product requirements for the same batch of universal modules, and meet diversified shipment requirements, so that the consignor can prepare goods in batches, the delivery period is shortened, the cost is reduced, and the consignor can customize the production plan only to bear an execution role in the whole module assembly and test process and cannot modify information locked by the background, and therefore, the consignor can control the whole product, and the consignor can better control the production quality of the universal modules.
In one possible design, uploading a production schedule customized by a consignor for the generic module to a cloud database includes:
And customizing the production plan by using terminal equipment by a consignor, and uploading the production plan to the cloud database, wherein the terminal equipment comprises a smart phone, a tablet computer, a notebook computer and/or a desktop computer.
In one possible design, burning the complementary firmware information into the generic module includes:
recording firmware complement information generated in a firmware complement process by using the cloud burning tool, and uploading the firmware complement information to the cloud database;
and binding and storing the firmware complement information and the production plan customized by the universal module by the cloud database so that a consignor can synchronously display or access and inquire the firmware complement information by using terminal equipment, wherein the terminal equipment comprises a smart phone, a tablet personal computer, a notebook computer and/or a desktop computer.
Based on the design, the record, uploading and binding storage of the firmware complement information can ensure that the consignor uses the terminal equipment to monitor the whole firmware complement process in real time or not in real time anytime anywhere, thereby further facilitating the consignor to control the production quality of the universal module.
In one possible design, the firmware repair information includes the number of general modules for which the firmware repair is completed and the firmware repair time and/or the general module serial number corresponding to the general modules for which the firmware repair is completed.
In one possible design, writing the test information to the generic module includes:
Recording production test information generated in the code writing test process by using the cloud production test tool, and uploading the production test information to the cloud database;
And binding and storing the production test information and the production plan customized by the universal module by the cloud database so that a consignor can synchronously display or access and inquire the production test information by using terminal equipment, wherein the terminal equipment comprises a smart phone, a tablet personal computer, a notebook computer and/or a desktop computer.
Based on the design, the record, uploading and binding storage of the production test information can ensure that the consignor uses the terminal equipment to monitor the whole code writing test process in real time or not in real time anytime anywhere, so that the consignor can control the production quality of the universal module conveniently.
In one possible design, the production test information includes the number of universal modules that have completed the code writing test, and a code writing test time, a universal module serial number, and/or the code writing test result that are in one-to-one correspondence with the universal modules that have completed the code writing test.
In one possible design, the base firmware information includes drive firmware information, control firmware information, decode firmware information, transmit firmware information, and detect firmware information.
In one possible design, the repair firmware information further includes firmware name information and/or firmware verification information.
In one possible design, the production schedule further includes upload date information, production quantity information, and/or production lot information.
In one possible design, the cloud burning tool and the cloud testing tool are integrated tools, wherein the integrated tools are integrated with a module testing operation pipeline from firmware complement to code writing test.
Based on the design, the general module can be subjected to firmware complement and code writing test in sequence through a pipeline, so that the error detection during assembly is further avoided, and defective products such as repeated burning, missing burning and firmware disorder caused by serial numbers are avoided.
Detailed Description
The invention will be further elucidated with reference to the drawings and to specific embodiments. The present invention is not limited to these examples, although they are described in order to assist understanding of the present invention. Specific structural and functional details disclosed herein are merely representative of example embodiments of the invention. This invention may, however, be embodied in many alternate forms and should not be construed as limited to the embodiments set forth herein.
It will be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element, without departing from the scope of example embodiments of the present invention.
It should be understood that for the term "and/or" that may appear herein, it is merely one association relationship that describes an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a alone, B alone, and both a and B; for the term "/and" that may appear herein, which is descriptive of another associative object relationship, it means that there may be two relationships, e.g., a/and B, it may be expressed that: a alone, a alone and B alone; in addition, for the character "/" that may appear herein, it is generally indicated that the context associated object is an "or" relationship.
It will be understood that when an element is referred to herein as being "connected," "connected," or "coupled" to another element, it can be directly connected or coupled to the other element or intervening elements may be present. In contrast, when an element is referred to herein as being "directly connected" or "directly coupled" to another element, it means that there are no intervening elements present. In addition, other words used to describe relationships between elements (e.g., "between … …" pair "directly between … …", "adjacent" pair "directly adjacent", etc.) should be interpreted in a similar manner.
It is to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments of the invention. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises," "comprising," "includes," "including" and/or "including," when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, and do not preclude the presence or addition of one or more other features, quantities, steps, operations, elements, components, and/or groups thereof.
It should be appreciated that in some alternative designs, the functions/acts noted may occur out of the order in which the figures appear. For example, two figures shown in succession may in fact be executed substantially concurrently or the figures may sometimes be executed in the reverse order, depending upon the functionality/acts involved.
It should be understood that specific details are provided in the following description to provide a thorough understanding of the example embodiments. However, it will be understood by those of ordinary skill in the art that the example embodiments may be practiced without these specific details. For example, a system may be shown in block diagrams in order to avoid obscuring the examples with unnecessary detail. In other instances, well-known processes, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the example embodiments.
As shown in fig. 1 to 2, the method for installing and testing the cloud management general module provided in the embodiment may include, but is not limited to, the following steps S101 to S104.
S101, after a general module is obtained through the surface mounting, basic firmware information is burned into the general module by using a burning tool.
In the step S101, the universal module is specifically obtained through SMT bonding, and the basic firmware information is burned by using a conventional burning tool (i.e. an IC burner, which means that the manufacturer buys various recordable IC chips from the semiconductor manufacturer, and the latest version of control program and data are written by using the IC burner before assembly, which is an important and necessary process than the IC test, and is generally performed by the final electronic product manufacturer). The basic firmware information refers to a program written into a storage medium such as EPROM (Erasable Programmable Read-Only Memory) or EEPROM (ELECTRICALLY ERASABLE PROGRAMMABLE READ-Only Memory), and the specific content thereof can be determined according to the following principle: the universal module can be normally electrified to conduct work, but cannot be normally assembled to related products to operate due to incomplete information. Therefore, the basic firmware information may include, but is not limited to, driving firmware information, control firmware information, decoding firmware information, transmitting firmware information, detecting firmware information, and the like, where the driving firmware information is used to enable the universal module to have a driving function after burning, the control firmware information is used to enable the universal module to have a control function after burning, the decoding firmware information is used to enable the universal module to have a decoding function after burning, the transmitting firmware information is used to enable the universal module to have a transmitting function after burning, the detecting firmware information is used to enable the universal module to have a self-checking function after burning, and the specific content of these firmware information can be obtained conventionally based on the prior art.
S102, uploading a production plan customized by a consignor for the universal module to a cloud database, wherein the production plan comprises the complement firmware information and the code writing test information of the universal module, and the complement firmware information comprises firmware version information and serial number range information.
In the step S102, specifically, the production schedule customized by the consigner for the universal module is uploaded to a cloud database (i.e. cloud server), including but not limited to: the production plan is customized by the consignor through terminal equipment and uploaded to the cloud database, wherein the terminal equipment comprises, but is not limited to, electronic equipment such as a smart phone, a tablet computer, a notebook computer and/or a desktop computer, and therefore the consignor can conveniently customize and issue the production plan anytime and anywhere, for example, the production plan is customized and uploaded through the smart phone with a specific application program APP. The production plan is a customized test plan executed by the commissioner according to the production party, wherein the repair firmware information is used for being delivered to the production party for repair firmware, so that the universal module has more complete information, and further, the code writing test or normal assembly to related products can be completed for operation; the firmware version information is used to enable the universal module to have customized firmware versions after burn-in, so that different firmware versions can be distinguished to meet different client requirements, including but not limited to "firmware versions" as shown in fig. 2: v01.0.2"; the sequence number range information is used to make the universal module have unique identity information after the sequence numbers are burned one by one, and as shown in fig. 2, for example, the sequence number section is: 12345679A-12346679B). The repair firmware information may also include, but is not limited to, firmware name information (for distinguishing different module firmware after burning in) and/or firmware verification information (for verifying whether the firmware content is correct and complete after burning in, and specific content may be conventionally obtained based on the prior art). The code writing test information is used for completing the module test in a conventional mode after being written into the universal module, and the specific content of the code writing test information can be obtained conventionally based on the prior art. Further, as shown in FIG. 2, the production schedule also includes, but is not limited to, upload date information (i.e., "release date: 2020.11.3" shown in FIG. 2), production quantity information (i.e., "production quantity: 3000" shown in FIG. 2), and/or production lot information, etc.
S103, downloading the complement firmware information of the universal module from the cloud database by using a cloud burning tool according to the production plan by a producer, and burning the complement firmware information into the universal module.
In step S103, the cloud burning tool is an IC burner that can access the cloud database, and can download and burn the repair firmware information normally. S301, recording firmware complement information generated in a firmware complement process by using the cloud burning tool, and uploading the firmware complement information to the cloud database; s302, binding and storing the firmware complement information and a production plan customized by the universal module by the cloud database so that a consignor can synchronously display or access and inquire the firmware complement information by using terminal equipment, wherein the terminal equipment comprises but is not limited to electronic equipment such as a smart phone, a tablet personal computer, a notebook computer and/or a desktop computer. The firmware complement information is used for recording detail information of the firmware complement process, and can include, but is not limited to, the number of the general modules which complete the firmware complement, firmware complement time and/or general module serial number which are in one-to-one correspondence with the general modules which complete the firmware complement, and the like, so that the client can be ensured to monitor the whole firmware complement process in real time or non-real time by using the terminal equipment at any time and any place through recording, uploading and binding storage of the firmware complement information.
S104, downloading the code writing test information of the universal module from the cloud database by using a cloud production testing tool according to the production plan by a producer, and writing the code writing test information into the universal module to obtain a code writing test result.
In step S104, the cloud end generating tool is a code writing test tool capable of accessing the cloud end database, and the code writing test information can be normally downloaded and written in, so as to finally obtain a code writing test result. Preferably, the writing test information is written into the universal module, including but not limited to the following steps S401 to S402: s401, recording production test information generated in a code writing test process by using the cloud end production test tool, and uploading the production test information to the cloud end database; s402, binding and storing the production test information and a production plan customized by the universal module by the cloud database, so that a consignor can synchronously display or access and inquire the production test information by using terminal equipment, wherein the terminal equipment comprises but is not limited to electronic equipment such as a smart phone, a tablet personal computer, a notebook computer and/or a desktop computer. The production test information is used for recording detailed information of the code writing test process, and can include, but is not limited to, the number of the universal modules which have completed the code writing test, code writing test time, universal module serial numbers and/or code writing test results which are in one-to-one correspondence with the universal modules which have completed the code writing test, and the like. In addition, the cloud burning tool and the cloud production testing tool are preferably integrated tools, wherein the integrated tools are integrated with a module mounting and testing operation pipeline from firmware complement to code writing test, so that the firmware complement and the code writing test can be sequentially carried out on the universal module through the pipeline, mounting and testing errors are further avoided, and defective products such as repeated burning, missing burning, firmware disorder and the like caused by serial numbers are avoided.
Based on the cloud management general module installation and measurement scheme described in the foregoing steps S101 to S104, on one hand, the conventional module burning mode is split into two parts: on the other hand, after the basic firmware information is burned, the consignor issues a customized production plan to the cloud end, so that when receiving the production plan, a producer can execute customized test tasks comprising a firmware complement process and a code writing test process according to the bill, and therefore, the consignor can customize different firmware contents according to different product requirements for the same batch of universal modules, and meet diversified shipment requirements, so that the consignor can prepare goods in batches, the delivery period is shortened, the cost is reduced, and the consignor can customize the production plan only to bear an execution role in the whole module assembly and test process and cannot modify information locked by the background, and therefore, the consignor can control the whole product, and the consignor can better control the production quality of the universal modules. In addition, the firmware complement information and/or the production test information can be recorded, uploaded and bound and stored, so that the commissioner can monitor the whole firmware complement process and/or the code writing test process in real time or not in real time at any time and any place by using the terminal device, and the production quantity, production batch and delivery rhythm of all production planning sheets can be monitored in the background of the commissioner, and the commissioner can further conveniently control the production quality of the universal module.
The above embodiments are only for illustrating the technical solution of the present invention, and are not limiting; although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some of the technical features thereof can be replaced by equivalents. Such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention.
Finally, it should be noted that the invention is not limited to the alternative embodiments described above, but can be used by anyone in various other forms of products in the light of the present invention. The above detailed description should not be construed as limiting the scope of the invention, which is defined in the claims and the description may be used to interpret the claims.