CN112445502A - Cloud management general module assembling and testing method - Google Patents
Cloud management general module assembling and testing method Download PDFInfo
- Publication number
- CN112445502A CN112445502A CN202011402178.0A CN202011402178A CN112445502A CN 112445502 A CN112445502 A CN 112445502A CN 202011402178 A CN202011402178 A CN 202011402178A CN 112445502 A CN112445502 A CN 112445502A
- Authority
- CN
- China
- Prior art keywords
- information
- firmware
- production
- module
- test
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000012360 testing method Methods 0.000 title claims abstract description 100
- 238000004519 manufacturing process Methods 0.000 claims abstract description 95
- 238000000034 method Methods 0.000 claims abstract description 43
- 238000012795 verification Methods 0.000 claims description 3
- 230000005540 biological transmission Effects 0.000 claims description 2
- 238000001514 detection method Methods 0.000 claims description 2
- 238000009434 installation Methods 0.000 abstract description 4
- 238000010998 test method Methods 0.000 abstract description 2
- 238000013461 design Methods 0.000 description 13
- 239000000047 product Substances 0.000 description 13
- 238000007726 management method Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 4
- 230000002950 deficient Effects 0.000 description 3
- 238000003860 storage Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000002360 preparation method Methods 0.000 description 2
- 239000013589 supplement Substances 0.000 description 2
- 238000005259 measurement Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000003908 quality control method Methods 0.000 description 1
- 230000033764 rhythmic process Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
- G06F8/63—Image based installation; Cloning; Build to order
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2205—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing using arrangements specific to the hardware being tested
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2273—Test methods
Abstract
The invention relates to the technical field of module installation and test, and discloses a cloud management general module installation and test method, which comprises the following steps of splitting a traditional module burning mode into two parts: the utility model discloses a production process, including basic firmware information, entrusting party's production plan list, production side, and the customization of basic firmware information burns and additionally records the customization of firmware information, on the other hand is through burning basic firmware information into, by the entrusting party at the backstage to the high in the clouds release customization production plan list, makes the producer receive can be based on the list and carry out the customization dress survey task that contains firmware additional recording process and write code test process when the production plan list, thereby can make the entrusting party can be directed against same batch of general module, according to different firmware content of different product demand customization, satisfies its diversified shipment demand, so that can the paster stock in batches, shorten the lead time, reduce cost, and can be controlled whole article by the entrusting party, make things convenient for the entrusting party to control the production quality of general module better.
Description
Technical Field
The invention belongs to the technical field of module assembling and testing, and particularly relates to a cloud management general module assembling and testing method.
Background
In the conventional production process of a Circuit module, after a Circuit module is obtained by SMT (Surface mount Technology) (short for serial process flow of processing on the basis of PCB, namely, abbreviation of Printed Circuit Board (PCB), meaning Printed Circuit Board (PCB), and abbreviation of Surface Mount Technology (SMT), meaning Surface assembly Technology, which is the most popular Technology and process in the electronic assembly industry), the Circuit module is subjected to the following process testing stage: patch- > complete firmware burning- > code writing- > test, wherein a client needs to send down a serial number range, and then a producer finishes the test through a local code writing test tool, so that the producer can control the test process and details in full authority. However, this presents two problems: (1) aiming at the same batch of universal circuit modules (the full text is called as the universal modules for short), the entrusting party can customize different firmware contents, so that diversified delivery requirements are difficult to meet, the entrusting party is not matched with the productivity of a production party, the entrusting party only can increase order quantity for stock or prolong order delivery time, and the capital occupation cost is increased; (2) the firmware subdivision versions of the universal module are generally many, and due to human factors of a production party, defective products such as repeated burning of serial numbers, missed burning, disordered firmware and the like may occur, while a consignor cannot control the whole quality control process.
Disclosure of Invention
The invention aims to solve the problems that an entrusting party cannot customize different firmware contents and cannot control the whole product control process in the universal module assembly and test process, and provides a cloud management universal module assembly and test method.
The invention provides a method for installing and testing a cloud management general module, which comprises the following steps:
after the universal module is obtained by mounting, burning basic firmware information into the universal module by using a burning tool;
uploading a production plan sheet customized by a consignor for the universal module to a cloud database, wherein the production plan sheet comprises additional firmware information and code writing test information of the universal module, and the additional firmware information comprises firmware version information and serial number range information;
downloading the additional firmware information of the universal module from the cloud database by a production party by using a cloud burning tool, and burning the additional 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 test tool by a production party, and writing the code writing test information into the universal module to obtain a code writing test result.
Based on the above invention, on one hand, the conventional module burning mode is divided into two parts: the universal burning of the basic firmware information and the customized burning of the additional firmware information, on the other hand, after the basic firmware information is burnt, the consignor issues the customized production schedule to the cloud end in the background, so that the producer can execute the customized testing task comprising the firmware additional recording process and the code writing testing process according to the schedule when receiving the production schedule, thereby enabling the consignor to aim at the same batch of universal modules, different firmware contents are customized according to different product requirements, diversified shipment requirements are met, so that patch preparation can be carried out in batches, delivery time is shortened, cost is reduced, and because the consignor customizes the production plan list, the producer only plays an executing role in the whole module assembling and testing process and cannot modify the information locked by the background, therefore, the whole product can be controlled by the consignor, and the consignor can better control the production quality of the universal module.
In one possible design, uploading a production schedule customized by a client for the generic module to a cloud database includes:
and customizing the production schedule by using terminal equipment by the entrusting party, and uploading the production schedule to the cloud database, wherein the terminal equipment comprises a smart phone, a tablet personal computer, a notebook computer and/or a desktop computer.
In one possible design, burning the additional firmware information into the generic module includes:
recording firmware supplementary recording information generated in the firmware supplementary recording process by using the cloud burning tool, and uploading the firmware supplementary recording information to the cloud database;
and binding and storing the firmware supplementary recording information and the production plan list customized by the universal module by the cloud database so that a consignor can synchronously display or access and inquire the firmware supplementary recording information by using terminal equipment, wherein the terminal equipment comprises a smart phone, a tablet computer, a notebook computer and/or a desktop computer.
Based on the design, the consignor can be ensured to use the terminal equipment to carry out real-time or non-real-time monitoring on the whole firmware additional recording process at any time and any place through recording, uploading, binding and storing the firmware additional recording information, and the consignor is further convenient to control the production quality of the universal module.
In one possible design, the firmware entry supplement information includes the number of the universal modules that have completed firmware entry, and the firmware entry supplement time and/or the universal module serial number that correspond to the universal modules that have completed firmware entry.
In one possible design, writing the test-for-write 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 list customized by the universal module by the cloud database so that a client 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 computer, a notebook computer and/or a desktop computer.
Based on the design, the production test information can be recorded, uploaded and bound for storage, so that a consignor can use the terminal equipment to monitor the whole code writing test process in real time or non-real time at any time and any place, and the consignor can further conveniently control the production quality of the universal module.
In one possible design, the production test information includes the number of the universal modules that have completed the code writing test, and the code writing test time, the serial number of the universal module, 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 basic firmware information includes driving firmware information, control firmware information, decoding firmware information, transmission firmware information, and detection firmware information.
In one possible design, the additional 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 production testing tool are integrated tools, wherein the integrated tools are integrated with a module assembly testing operation line from firmware re-recording to code writing testing.
Based on the design, the firmware additional recording and code writing test can be sequentially carried out on the general module through a production line, so that errors in the installation and test are further avoided, and defective products such as repeated burning of serial numbers, burning missing, disordered firmware and the like are avoided.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic flow chart of a method for installing and testing a cloud management general module according to the present invention.
FIG. 2 is an exemplary diagram of a production schedule provided by the present invention.
Detailed Description
The invention is further described with reference to the following figures and specific embodiments. It should be noted that the description of the embodiments is provided to help understanding of the present invention, but the present invention is not limited thereto. Specific structural and functional details disclosed herein are merely illustrative 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. 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" as may appear herein, it is merely an associative relationship that describes an associated object, meaning that three relationships may exist, e.g., a and/or B may mean: a exists alone, B exists alone, and A and B exist at the same time; for the term "/and" as may appear herein, which describes another associative object relationship, it means that two relationships may exist, e.g., a/and B, may mean: a exists independently, and A and B exist independently; in addition, for the character "/" that may appear herein, it generally means that the former and latter associated objects are in 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. Conversely, if a unit is referred to herein as being "directly connected" or "directly coupled" to another unit, it is intended that no intervening units are present. In addition, other words used to describe the relationship between elements should be interpreted in a similar manner (e.g., "between … …" versus "directly between … …", "adjacent" versus "directly adjacent", etc.).
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" and/or "including," when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, numbers, steps, operations, elements, components, and/or groups thereof.
It should also be noted that, in some alternative designs, the functions/acts noted may occur out of the order noted in the figures. 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 facilitate a thorough understanding of 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, systems may be shown in block diagrams in order not to obscure the examples in unnecessary detail. In other instances, well-known processes, structures and techniques may be shown without unnecessary detail in order to avoid obscuring example embodiments.
As shown in fig. 1 to 2, the method for installing and testing the cloud management general module provided in this embodiment may include, but is not limited to, the following steps S101 to S104.
S101, after the universal module is obtained through surface mounting, basic firmware information is burnt into the universal module through a burning tool.
In step S101, the universal module is obtained by SMT mounting, and the basic firmware information is burned in using a conventional burning tool (i.e., an IC burner, which is a necessary process more important than IC testing and generally performed by a final electronic product manufacturer) to write the latest version of control program and data into a blank data area of each IC chip purchased by a manufacturer from a semiconductor manufacturer. The basic firmware information refers to a program written in a storage medium such as an EPROM (Erasable Programmable Read-Only Memory) or an EEPROM (Electrically Erasable Programmable Read-Only Memory), and the specific content of the basic firmware information can be determined according to the following principle: the universal module can be normally powered on to conduct work, but cannot be normally assembled on a related product to operate due to incomplete information. Therefore, the basic firmware information may include, but is not limited to, drive firmware information for enabling the general-purpose module to have a drive function after burn-in, control firmware information for enabling the general-purpose module to have a control function after burn-in, decode firmware information for enabling the general-purpose module to have a decode function after burn-in, transmit firmware information for enabling the general-purpose module to have a transmit function after burn-in, detect firmware information for enabling the general-purpose module to have a self-check function after burn-in, and the like, and specific contents of these firmware information may be conventionally obtained based on the prior art.
And S102, uploading a production plan sheet customized by the entrusting party for the universal module to a cloud database, wherein the production plan sheet comprises additional firmware information and code writing test information of the universal module, and the additional firmware information comprises firmware version information and serial number range information.
In step S102, specifically, the production schedule customized by the client for the generic module is uploaded to a cloud database (i.e. a cloud server), which includes but is not limited to: the client side customizes the production plan list by using the terminal device, and uploads the production plan list to the cloud database, wherein the terminal device comprises but is not limited to electronic devices such as a smart phone, a tablet computer, a notebook computer and/or a desktop computer, and therefore the client side can conveniently customize and issue the production plan list anytime and anywhere, for example, the production plan list is customized and uploaded by using the smart phone with a specific application program APP. The production plan list is a customized assembly test plan executed by a production party by a consignor, wherein the additional firmware information is used for being delivered to the production party for additional firmware recording, so that the universal module has more complete information, and code writing test can be completed or the universal module can be normally assembled on a related product to run; the firmware version information is used to make the universal module have a customized firmware version after burning in, so that different firmware versions can be distinguished to meet different client requirements, including but not limited to "firmware version: v01.0.2 "; the serial number range information is used to make the universal module have unique identity information after burning serial numbers one by one, which is shown in fig. 2, for example, "serial number segment: 12345679A-12346679B ". The additional firmware information may also include, but is not limited to, firmware name information (used to distinguish different module firmware after burning in), and/or firmware verification information (used to verify whether the firmware content is correct and complete after burning in, where the specific content may be conventionally obtained based on the prior art), and the like. The code writing test information is used for completing module test in a conventional mode after being written into the general module, and the specific content of the code writing test information can be obtained conventionally based on the prior art. In addition, as shown in FIG. 2, the production schedule may also include, 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 additional firmware information of the universal module from the cloud database by the production party according to the production plan list by using a cloud burning tool, and burning the additional 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 normally download and burn in the additional firmware information. S301, recording firmware additional information generated in the firmware additional recording process by using the cloud burning tool, and uploading the firmware additional information to the cloud database; s302, the firmware supplementary recording information and the production plan list customized by the universal module are bound and stored by the cloud database, so that a client can synchronously display or access and inquire the firmware supplementary recording information by using terminal equipment, 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. The firmware additional recording information is used for recording the detailed information of the firmware additional recording process, and can include but is not limited to the number of universal modules completing the firmware additional recording, the firmware additional recording time and/or the serial number of the universal modules corresponding to the universal modules completing the firmware additional recording one by one, and the like.
S104, downloading the code writing test information of the universal module from the cloud database by the production side according to the production plan list by using a cloud production test tool, and writing the code writing test information into the universal module to obtain a code writing test result.
In step S104, the cloud product test tool is a code writing test tool that can access the cloud database, and can normally download and write the code writing test information, so as to obtain a code writing test result. Preferably, the writing of the coding test information to the general-purpose module includes, but is 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 production test tool, and uploading the production test information to the cloud database; s402, the production test information and the production plan list customized by the universal module are bound and stored by the cloud database, so that a client can synchronously display or access and query 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 computer, a notebook computer and/or a desktop computer. The production test information is used for recording the detailed information of the code writing test process, and can include but not be limited to the number of universal modules which have completed the code writing test, the code writing test time which is in one-to-one correspondence with the universal modules which have completed the code writing test, the serial number of the universal modules, and/or the code writing test result, 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 assembly and test operation assembly line from firmware additional recording to code writing test, so that the universal module can be sequentially subjected to firmware additional recording and code writing test through the assembly line, errors in assembly and test are further avoided, and defective products such as repeated burning of serial numbers, missing burning, disordered firmware and the like are avoided.
Therefore, 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: the universal burning of the basic firmware information and the customized burning of the additional firmware information, on the other hand, after the basic firmware information is burnt, the consignor issues the customized production schedule to the cloud end in the background, so that the producer can execute the customized testing task comprising the firmware additional recording process and the code writing testing process according to the schedule when receiving the production schedule, thereby enabling the consignor to aim at the same batch of universal modules, different firmware contents are customized according to different product requirements, diversified shipment requirements are met, so that patch preparation can be carried out in batches, delivery time is shortened, cost is reduced, and because the consignor customizes the production plan list, the producer only plays an executing role in the whole module assembling and testing process and cannot modify the information locked by the background, therefore, the whole product can be controlled by the consignor, and the consignor can better control the production quality of the universal module. In addition, the firmware additional recording information and/or the production test information can be recorded, uploaded and bound for storage, so that a consignor can use the terminal equipment to monitor the whole firmware additional recording process and/or the code writing test process in real time or non-real time at any time and any place, the production quantity, the production batch and the delivery rhythm of all production schedule lists can be monitored by the background of the consignor, and the consignor can further conveniently control the production quality of the universal module.
The above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present 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: modifications may be made to the embodiments described above, or equivalents may be substituted for some of the features described. And such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Finally, it should be noted that the present invention is not limited to the above alternative embodiments, and that various other forms of products can be obtained by anyone in light of the present invention. The above detailed description should not be taken as limiting the scope of the invention, which is defined in the claims, and which the description is intended to be interpreted accordingly.
Claims (10)
1. A method for installing and testing a cloud management general module is characterized by comprising the following steps:
after the universal module is obtained by mounting, burning basic firmware information into the universal module by using a burning tool;
uploading a production plan sheet customized by a consignor for the universal module to a cloud database, wherein the production plan sheet comprises additional firmware information and code writing test information of the universal module, and the additional firmware information comprises firmware version information and serial number range information;
downloading the additional firmware information of the universal module from the cloud database by a production party by using a cloud burning tool, and burning the additional 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 test tool by a production party, and writing the code writing test information into the universal module to obtain a code writing test result.
2. The method of claim 1, wherein uploading a production schedule customized by a client for the generic module to a cloud database comprises:
and customizing the production schedule by using terminal equipment by the entrusting party, and uploading the production schedule to the cloud database, wherein the terminal equipment comprises a smart phone, a tablet personal computer, a notebook computer and/or a desktop computer.
3. The method of claim 1, wherein burning the patch firmware information into the generic module comprises:
recording firmware supplementary recording information generated in the firmware supplementary recording process by using the cloud burning tool, and uploading the firmware supplementary recording information to the cloud database;
and binding and storing the firmware supplementary recording information and the production plan list customized by the universal module by the cloud database so that a consignor can synchronously display or access and inquire the firmware supplementary recording information by using terminal equipment, wherein the terminal equipment comprises a smart phone, a tablet computer, a notebook computer and/or a desktop computer.
4. The method as claimed in claim 3, wherein the firmware entry information includes a number of universal modules that have completed firmware entry and a firmware entry time and/or a universal module serial number that correspond to the universal modules that have completed firmware entry.
5. The method of claim 1, wherein writing the coded test information to the generic module comprises:
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 list customized by the universal module by the cloud database so that a client 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 computer, a notebook computer and/or a desktop computer.
6. The method of claim 5, wherein the production test information comprises the number of the generic modules that have completed the code writing test and the code writing test time, the serial number of the generic module, and/or the code writing test result corresponding to the generic modules that have completed the code writing test.
7. The method of claim 1, wherein the base firmware information comprises driver firmware information, control firmware information, decoding firmware information, transmission firmware information, and detection firmware information.
8. The method of claim 1, wherein the additional firmware information further comprises firmware name information and/or firmware verification information.
9. The method of claim 1, wherein the production schedule further comprises upload date information, production quantity information, and/or production lot information.
10. The method of claim 1, wherein the cloud burning tool and the cloud production testing tool are integrated tools, and wherein the integrated tools are integrated with a module assembly testing line from firmware logging to code writing testing.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011402178.0A CN112445502A (en) | 2020-12-02 | 2020-12-02 | Cloud management general module assembling and testing method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011402178.0A CN112445502A (en) | 2020-12-02 | 2020-12-02 | Cloud management general module assembling and testing method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112445502A true CN112445502A (en) | 2021-03-05 |
Family
ID=74739269
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011402178.0A Pending CN112445502A (en) | 2020-12-02 | 2020-12-02 | Cloud management general module assembling and testing method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112445502A (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140379677A1 (en) * | 2013-06-24 | 2014-12-25 | Sap Ag | Test sandbox in production systems during productive use |
| CN108681459A (en) * | 2018-03-26 | 2018-10-19 | 深圳前海有电物联科技有限公司 | A kind of firmware update of intelligent hardware devices, apparatus and system |
| CN109905256A (en) * | 2017-12-07 | 2019-06-18 | 阿里巴巴集团控股有限公司 | A kind of firmware update and device |
| CN110413295A (en) * | 2019-06-26 | 2019-11-05 | 上海电器科学研究所（集团）有限公司 | A kind of embedded device remote firmware updating method |
| CN111404733A (en) * | 2020-03-06 | 2020-07-10 | 上海钧正网络科技有限公司 | Firmware control method and system and storage medium |
| CN111651180A (en) * | 2020-06-11 | 2020-09-11 | 上海庆科信息技术有限公司 | Firmware updating method and device, processor and intelligent gateway equipment |
-
2020
- 2020-12-02 CN CN202011402178.0A patent/CN112445502A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140379677A1 (en) * | 2013-06-24 | 2014-12-25 | Sap Ag | Test sandbox in production systems during productive use |
| CN109905256A (en) * | 2017-12-07 | 2019-06-18 | 阿里巴巴集团控股有限公司 | A kind of firmware update and device |
| CN108681459A (en) * | 2018-03-26 | 2018-10-19 | 深圳前海有电物联科技有限公司 | A kind of firmware update of intelligent hardware devices, apparatus and system |
| CN110413295A (en) * | 2019-06-26 | 2019-11-05 | 上海电器科学研究所（集团）有限公司 | A kind of embedded device remote firmware updating method |
| CN111404733A (en) * | 2020-03-06 | 2020-07-10 | 上海钧正网络科技有限公司 | Firmware control method and system and storage medium |
| CN111651180A (en) * | 2020-06-11 | 2020-09-11 | 上海庆科信息技术有限公司 | Firmware updating method and device, processor and intelligent gateway equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108170447A (en) | The on-line automatic method for burn-recording of chip and system | |
| CN103049770A (en) | SMT (Surface Mount Technology) anti-false material detection system and method | |
| US5241657A (en) | Information display system | |
| CN111404733A (en) | Firmware control method and system and storage medium | |
| CN103592898A (en) | An electronic product production automatic control system and a method | |
| CN107346244B (en) | A kind of automobile EPS director demon automation download system and method | |
| CN111831495A (en) | Production automation test method and system | |
| CN110519982A (en) | Pasting method, device, electronic equipment and storage medium | |
| CN110826671B (en) | Power cable information reading and writing system and reading and writing method thereof | |
| CN101739322B (en) | Test device and method of embedded system | |
| CN112445502A (en) | Cloud management general module assembling and testing method | |
| CN114414908A (en) | Digital test system and test method for power protection control equipment | |
| CN116205210B (en) | Method and system for judging matching performance of electric parts of whole vehicle | |
| CN101436157A (en) | Method for processing program BUG in program test process flow | |
| CN114968883A (en) | Automated testing apparatus, method, device, and computer-readable storage medium | |
| CN114740807A (en) | Production monitoring method for satellite positioner equipment | |
| CN113721562A (en) | Automatic configuration method for production line test resources | |
| CN102496388A (en) | Method for examining memory code of printed circuit board | |
| CN112783708A (en) | DTU hardware testing method, terminal and computer readable storage medium | |
| CN101196943A (en) | Test point error-checking method | |
| KR20100056234A (en) | Product control system using 2d barcode and methode the same | |
| CN111143262A (en) | Switching device, instrument control system and instrument control method | |
| CN118034719A (en) | System for burning program of streaming media product | |
| CN107967434A (en) | It is a kind of that the method and system for throwing plate are realized using laser engraving machine | |
| US20230003834A1 (en) | Method and system for importing parameter calibration and terminal device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |