CN117492777A - Method, system and equipment for realizing safe burning of MCU software production data - Google Patents

Method, system and equipment for realizing safe burning of MCU software production data Download PDF

Info

Publication number
CN117492777A
CN117492777A CN202311478482.7A CN202311478482A CN117492777A CN 117492777 A CN117492777 A CN 117492777A CN 202311478482 A CN202311478482 A CN 202311478482A CN 117492777 A CN117492777 A CN 117492777A
Authority
CN
China
Prior art keywords
mcu
burned
production data
firmware
software production
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
Application number
CN202311478482.7A
Other languages
Chinese (zh)
Inventor
王巨
姜波
赵晨曦
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shenzhen Snowball Technology Co ltd
Original Assignee
Shenzhen Snowball Technology Co ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Shenzhen Snowball Technology Co ltd filed Critical Shenzhen Snowball Technology Co ltd
Priority to CN202311478482.7A priority Critical patent/CN117492777A/en
Publication of CN117492777A publication Critical patent/CN117492777A/en
Pending legal-status Critical Current

Links

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
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
    • G06F21/12—Protecting executable software
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
    • G06F21/57—Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
    • G06F21/575—Secure boot

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Multimedia (AREA)
  • Technology Law (AREA)
  • Storage Device Security (AREA)

Abstract

The invention provides a method, a system and equipment for realizing safe burning of MCU software production data, relating to the technical field of MCU burning, comprising the following steps: acquiring temporary firmware corresponding to an MCU to be burned, and burning the temporary firmware into the MCU to be burned; acquiring the MCU software production data to be burned, and transmitting the MCU software production data to be burned to the temporary firmware through a secure channel; the temporary firmware writes the production data of the MCU software to be burned into the Flash of the MCU to be burned, so that the technical problem of firmware leakage in the process of generating the MCU-containing equipment in the prior art is solved, and the technical effect of preventing information of firmware in the MCU from being leaked in the process of delivery is achieved.

Description

Method, system and equipment for realizing safe burning of MCU software production data
Technical Field
The invention relates to the technical field of MCU burning, in particular to a safe burning method, system and equipment for realizing MCU software production data.
Background
The internet of things equipment or other products developed based on the MCU are required to be used for recording software such as firmware, factory data and the like in the MCU, the MCU can work according to established processing logic, the internal firmware of the MCU is required to be kept secret, if the internal firmware of the MCU is leaked, the internal firmware of the MCU can be used for manufacturing imitation, however, in the prior art, the information is recorded in the MCU through a recorder, and encryption is not performed when the MCU is used for recording software production data such as the firmware, the factory data and the like, so that the firmware can be leaked, and loss is caused.
Disclosure of Invention
The invention aims to provide a method, a system and equipment for realizing safe burning of MCU software production data, so as to solve the technical problem of firmware leakage in the process of generating equipment containing MCU in the prior art.
The invention provides a safe burning method for realizing MCU software production data, which comprises the following steps:
acquiring temporary firmware corresponding to an MCU to be burned, and burning the temporary firmware into the MCU to be burned;
acquiring the MCU software production data to be burned, and transmitting the MCU software production data to be burned to the temporary firmware through a secure channel;
and the temporary firmware writes the production data of the MCU software to be burned into the Flash of the MCU to be burned.
In a possible implementation manner, before the obtaining the temporary firmware corresponding to the MCU to be burned, the method further includes:
and creating temporary firmware corresponding to the MCU to be burned according to the model of the MCU to be burned.
In a possible embodiment, the safety channel comprises:
based on the link application, determining safety communication between the PC end production tool and the cloud end;
and determining the safety communication between the PC end production tool and the MCU according to the communication parameters.
In a possible implementation manner, before obtaining the software production data of the MCU to be burned, the method further includes:
creating a product to be burned, wherein the product to be burned uses the MCU to be burned;
creating a version of the product to be burned based on the product to be burned, wherein the version of the product to be burned comprises a plurality of software production data;
and creating a batch of the product to be burned based on the version of the product to be burned.
In a possible embodiment, the software production material includes firmware, factory data, keys, certificates, and configuration information.
In a possible implementation manner, the obtaining the production data of the MCU software to be burned includes:
acquiring authentication information of the MCU to be burned;
and obtaining the MCU software production data to be burned based on the authentication information of the MCU to be burned.
In a possible implementation manner, the temporary firmware writes the production data of the MCU software to be burned into the Flash of the MCU to be burned, including:
the MCU software production data to be burned is data for enabling the safety characteristic, and the data for enabling the safety characteristic comprises any one of starting Flash encryption, enabling safe starting and closing a debugging interface.
The invention also provides a safe burning system for realizing MCU software production data, comprising: cloud, PC end production instrument, write ware, MCU, interim firmware, wherein the cloud with PC end production instrument is connected, PC end production instrument with MCU connects, PC end production instrument with write ware connects, write ware with MCU interface connection, interim firmware is located MCU.
In a possible implementation manner, the cloud end is connected with the PC end production tool through a network;
the PC end production tool is connected with the MCU through a serial port or a bidirectional communication interface;
the PC end production tool is connected with the burner through a USB;
the burner is connected with the MCU through a burning interface.
The invention also provides an electronic device, which comprises a memory, a processor and a computer program stored in the memory and capable of running on the processor, wherein the processor realizes the steps of the method for realizing the safe burning of MCU software production data according to any one of the above when executing the program.
According to the method, the system and the equipment for realizing the safe burning of the MCU software production data, the temporary firmware is arranged in the MCU, the MCU software production data is sent to the temporary firmware through the safe channel, and the temporary firmware writes the MCU software production data into the Flash of the MCU so as to facilitate the subsequent use and prevent the data from being stolen or illegally accessed in the transmission process.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings that are needed in the description of the embodiments or the prior art will be briefly described, and it is obvious that the drawings in the description below are some embodiments of the present invention, and other drawings can be obtained according to the drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic diagram of a security burning system for implementing MCU software production data according to an embodiment of the present invention;
FIG. 2 is a flowchart of a method for implementing secure burning of MCU software production data according to an embodiment of the present invention;
FIG. 3 is a second flowchart of a method for implementing secure burning of MCU software production data according to an embodiment of the present invention;
fig. 4 is an electronic device provided by the present invention.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are some embodiments of the present invention, but not all embodiments of the present invention. The components of the embodiments of the present invention generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations.
Thus, the following detailed description of the embodiments of the invention, as presented in the figures, is not intended to limit the scope of the invention, as claimed, but is merely representative of selected embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
It should be noted that: like reference numerals and letters denote like items in the following figures, and thus once an item is defined in one figure, no further definition or explanation thereof is necessary in the following figures.
In the description of the present invention, it should be noted that, directions or positional relationships indicated by terms such as "center", "upper", "lower", "left", "right", "vertical", "horizontal", "inner", "outer", etc., are directions or positional relationships based on those shown in the drawings, or are directions or positional relationships conventionally put in use of the inventive product, are merely for convenience of describing the present invention and simplifying the description, and are not indicative or implying that the apparatus or element to be referred to must have a specific direction, be constructed and operated in a specific direction, and thus should not be construed as limiting the present invention. Furthermore, the terms "first," "second," "third," and the like are used merely to distinguish between descriptions and should not be construed as indicating or implying relative importance.
Furthermore, the terms "horizontal," "vertical," "overhang," and the like do not denote a requirement that the component be absolutely horizontal or overhang, but rather may be slightly inclined. As "horizontal" merely means that its direction is more horizontal than "vertical", and does not mean that the structure must be perfectly horizontal, but may be slightly inclined.
In the description of the present invention, it should also be noted that, unless explicitly specified and limited otherwise, the terms "disposed," "mounted," "connected," and "connected" are to be construed broadly, and may be, for example, fixedly connected, detachably connected, or integrally connected; can be mechanically or electrically connected; can be directly connected or indirectly connected through an intermediate medium, and can be communication between two elements. The specific meaning of the above terms in the present invention will be understood in specific cases by those of ordinary skill in the art.
Some embodiments of the present invention are described in detail below with reference to the accompanying drawings. The following embodiments and features of the embodiments may be combined with each other without conflict.
MCU (Microcontroller Unit) the micro control unit is a chip with a microprocessor as a core, integrating a memory, a timer, an I/O port, various interface circuits and specific functional circuits, and is generally used for controlling and driving various mechanical or electronic devices.
The MCU UID refers to a unique identification code of the micro-control unit, typically programmed into the chip by the chip manufacturer during production, for uniquely identifying each chip. The UID may also be used as a serial number of the device to identify and distinguish the device in the communication protocol, and may also be used as a security key, used in conjunction with software encryption algorithms, to reduce the risk of the firmware being maliciously copied.
Flash (Flash Memory) memory is a non-volatile memory for storing program code and data, the data within which can be modified by a particular program.
RAM (Random Access Memory) random access memory is an electronic device for storing data, and RAM is operable to write or read information from any one of the specified addresses at any time.
Software production data refers to various tools, techniques, resources, talents, etc. used in the software production process. In this application, the software production material specifically includes data such as firmware, factory data, keys, certificates, and configuration information.
The burner is a machine for copying data files to chips, is usually connected with a computer, is used in combination with programming software, and is mainly used for programming chips such as a singlechip/a memory.
According to the invention, in the production process of the equipment, the writer is not used for writing the plaintext directly into the Flash of the MCU, but is used for writing a temporary proxy firmware, namely the temporary firmware, into the RAM to operate in the MCU, a safety channel is established between the MCU and the cloud, the cloud sends software production data to the MCU based on the safety channel, the software production data is written into the Flash of the MCU after being received in the temporary firmware safety channel, and the firmware in the MCU can be effectively prevented from being leaked in the delivery process through the safety protection of the cloud and the MCU side in the whole writing process.
Fig. 1 is a system architecture diagram for implementing secure burning of MCU software production data, as shown in fig. 1, the system includes: cloud end, PC end production instrument, write ware, MCU, interim firmware, wherein the cloud end passes through the network connection with PC end production instrument, and PC end production instrument passes through serial ports or other two-way communication interface connection with MCU, and PC end production instrument passes through USB connection with write ware, and write ware passes through write interface connection with MCU, and interim firmware is located in the MCU.
In the application, the cloud end stores and manages software production data and equipment MCU, and has at least the following functions: safety management software production data, verification of validity of a request device, establishment of a safety channel with the device, capability of issuing the software production data based on the safety channel and the like;
the PC-side production tool is the main interactive portal for factory worker operation, and has at least the following functions: the recorder is used for writing the RAM of the temporary firmware in the MCU, running the temporary firmware in the RAM, communicating with the temporary firmware through a serial port, communicating with a far end, and mutually and thoroughly transmitting communication data of the MCU and a cloud end;
the temporary firmware is developed for a MCU of a specific model, can be applicable to different products designed based on the MCU, and has at least the following functions: calling a device certificate and a corresponding private key thereof preset in a safe environment of the MCU, reading the MCU UID, communicating with a PC-end production tool through a serial port, proving legal devices to a cloud end based on the device certificate and the MCU UID, verifying the validity of a cloud end server through presetting a follow-up certificate of the cloud end, establishing a safe channel with the cloud end, writing software production data into a corresponding Flash space and the like.
Fig. 2 and fig. 3 are diagrams showing a method for implementing secure burning of MCU software production data, wherein the method is implemented by burning a PC-side production tool to an MCU, obtaining the software production data from a cloud and enabling MCU security features, as shown in fig. 2 and fig. 3, and comprises the following specific processes:
s110, acquiring temporary firmware corresponding to the MCU to be burned, and burning the temporary firmware into the MCU to be burned.
In the application, the PC side tool acquires temporary firmware corresponding to the MCU to be burned according to the type of the MCU to be burned, burns the temporary firmware into the MCU by using the burner, and starts the temporary firmware.
Further, the temporary firmware typically contains code for communicating with the PC-side production tool for subsequent communication and data transmission.
In a possible implementation manner, before acquiring the temporary firmware, the method further includes:
and creating temporary firmware corresponding to the MCU to be burned according to the model of the MCU to be burned.
Specifically, a tool with firmware development may be used to create a temporary firmware corresponding to the MCU to be burned based on the characteristics of the MCU to be burned, and the development process may include the following steps: firstly, carrying out demand analysis on an MCU to be burned, defining the design requirement and the function requirement of the MCU to be burned, secondly, carrying out hardware design of the MCU to be burned according to the result of the demand analysis, then carrying out software design and coding according to the result of the hardware design and the demand analysis, and finally compiling a source code into an executable binary file by using a development tool, and carrying out debugging and testing.
In the application, temporary firmware suitable for MCUs of different models is stored in the cloud, and the temporary firmware can be suitable for different products designed based on the MCU.
Further, the temporary firmware may be burned somewhere in the Flash of the MCU, as long as it is not covered by the main firmware.
S120, acquiring software production data of the MCU to be burned, and sending the software production data of the MCU to be burned to the temporary firmware through a secure channel.
In a possible implementation manner, before obtaining the software production data of the MCU to be burned, the method further includes:
creating a product to be burned, wherein the product to be burned uses the MCU to be burned;
creating a version of the product to be burned based on the product to be burned, wherein the version of the product to be burned comprises a plurality of software production data;
and creating a batch of the product to be burned based on the version of the product to be burned.
Specifically, software production data of the related product to be burned is configured at the cloud, wherein the software production data comprises data such as firmware, factory data, secret keys, certificates, configuration information and the like.
Creating a product in a cloud disk, selecting MCU signals used in the product, automatically matching temporary firmware according to the MCU model, creating a version in the product, selecting software production data such as firmware to be programmed, factory data and the like, creating a batch on the version, selecting the number of creation by a user, automatically generating corresponding number of production data according to the number of users, and encrypting and storing the production data.
Furthermore, MCU software production data can be recorded for a plurality of MCU products to be recorded with the same model at the same time.
In a possible implementation manner, the obtaining the production data of the MCU software to be burned includes:
acquiring authentication information of the MCU to be burned;
and obtaining the MCU software production data to be burned based on the authentication information of the MCU to be burned.
Specifically, the PC end production tool obtains authentication information of the MCU to be burned, the authentication information is information such as a device certificate and a UID of the MCU to be burned, the authentication information is sent to the cloud end through the serial port, the cloud end obtains software production data of the MCU to be burned according to the authentication information of the MCU to be burned, the software production data of the MCU to be burned is sent to the PC end production tool through the safety channel, and the PC end production tool sends the software production data of the MCU to be burned to temporary firmware in the MCU to be burned through the safety channel.
In a possible embodiment, the safety channel comprises:
based on the link application, determining communication between the PC side production tool and the cloud side;
and determining communication between the PC end production tool and the MCU according to the communication parameters.
Specifically, in the method, the PC side production tool and the cloud side communicate through a bidirectional HTTPS protocol, and a safe and reliable communication mode is ensured through unidirectional and bidirectional identity verification. The PC side production tool sends a link application to the cloud side, the link application is a request for applying for production batches, HTTPS bidirectional authentication link can be established through the U-key and the server, the request for applying for production batches is sent to the cloud side, after the cloud side receives the request, the validity of the U-key and the production batches associated with the authentication U-key are verified, and a verification result is returned to the PC side production tool, wherein the verification result returns production batch information, and the production batch information comprises the number of the production batches, the residual available number and the like.
Further, authenticating a production lot associated with a U-key is by using the U-key as a mechanism for authentication and authorization to associate and confirm validity and legitimacy of the production lot in the request, for example, during production manufacturing, each production lot typically has a unique identifier, such as a lot number or a product serial number, and binding the U-key with production lot information, such as storing the unique identifier, such as a lot number or a product serial number, in the U-key, and when authentication or authorization operation is required for the lot, authenticating the identity and obtaining access rights to the lot through the U-key.
Further, the HTTPS (HTTP Secure) security protocol, which provides for encrypted and secure communications when transmitting data over the internet, is encapsulated over the HTTP protocol by the SSL/TLS protocol, thereby providing secure communications between the client and the server.
Specifically, in the present application, the PC-side production tool and the MCU communicate through a serial port, or communicate through other bidirectional communication interfaces, for example, the serial port of the MCU to be burned is first physically connected with the serial port of the PC-side production tool through a serial port line, and then the communication is performed using communication parameters agreed by both parties, such as baud rate, parity check, check bits, and the like.
Further, according to the communication between the PC end production tool and the cloud end through the bidirectional HTTPS protocol and the communication between the PC end production tool and the MCU through the serial port or other bidirectional communication interfaces, the PC end production tool is used for forwarding data, and further the safety communication between the MCU and the cloud end is established by using a bidirectional authentication mechanism, so that information in the MCU can be prevented from being leaked in the interaction process.
Specifically, the PC-side production tool sends authentication information of the MCU to be burned to the cloud, that is, sends a request for application software production data of the MCU to be burned to the cloud, where the application software production data includes SNB (Server Naming Bitmap) server naming mechanism, SE (security engine), OS (operating system), SE initialization information, SE key certificate, encryption firmware, encryption Matter production data, and the like, after authentication is performed according to the request for application software production data, the cloud returns an initialization security production link authentication to the PC-side production tool, the PC-side production tool forwards the returned initialization security production link authentication to the MCU to be burned, the temporary firmware of the MCU to be burned performs the initialization security production link authentication, and returns a result to the PC-side production tool, the PC-side production tool returns the result to the cloud, and after authentication is successful, sends software production data of the MCU to be burned to the PC-side production tool, and the PC-side production tool sends software production data of the MCU to be burned to the temporary firmware of the MCU to be burned.
Furthermore, the built-in equipment certificate of the MCU is a small amount of MCU with higher safety requirements; for the MCU without the equipment certificate, the MCU can be replaced by a mode of verifying the MCU UID; if MCU equipment without MCU UID is not provided, flash UID can be used for replacing the MCU UID; if there is no MCU with unique identification, the validity of MCU can be selected not to be verified, but the security performance is further reduced.
Furthermore, the connection between the PC side production tool and the cloud side can be realized through bi-directional HTTPS, for example, a U shield is used for identifying the user identity to prevent the user without authority from using, and especially when the MCU does not have equipment certificate and identifiable UID, the security can be increased to a certain extent through the U shield.
S130, the temporary firmware writes the production data of the MCU software to be burned into the Flash of the MCU to be burned.
In the invention, after the temporary firmware of the MCU to be recorded receives the software production data of the MCU to be recorded, the software production data of the MCU to be recorded is decrypted and then recorded into the Flash of the MCU to be recorded for subsequent use.
Further, the cloud end sends the software production data to the MCU to be burned, through the encrypted data with the MCU safety characteristic, flash encryption is started, safety starting is started, a debugging interface is closed, and the like, so that safety protection inside the MCU is further enhanced.
Specifically, the cloud end sends specific data or instructions to the MCU to be burned so as to enable the safety characteristic of the MCU, and the Flash encryption is enabled to protect the stored data in the MCU from being illegally read; the starting code of the MCU can be protected from being tampered by starting the safe starting; closing the debug interface can prevent hackers from attacking the MCU through the debug interface, and the security protection inside the MCU can be further enhanced through the security features.
According to the invention, cloud to MCU end is realized, and an end-to-end encryption mode is adopted, so that the data is ensured to be in a ciphertext form in the whole transmission process. Therefore, the data can be prevented from being stolen or illegally accessed in the transmission process, different contents can be burnt for different devices, the specific contents are controlled by the cloud, and the problem of one device-one data is solved.
Fig. 4 illustrates a physical schematic diagram of an electronic device, as shown in fig. 4, which may include: processor 810, communication interface (Communications Interface) 820, memory 830, and communication bus 840, wherein processor 810, communication interface 820, memory 830 accomplish communication with each other through communication bus 840. The processor 810 may call logic instructions in the memory 830 to perform steps of a method for implementing secure burning of MCU software production data. Further, the logic instructions in the memory 830 described above may be implemented in the form of software functional units and may be stored in a computer-readable storage medium when sold or used as a stand-alone product.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present invention, and not for limiting the same; 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 or all of the technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the invention.

Claims (10)

1. The safe burning method for realizing MCU software production data is characterized by comprising the following steps:
acquiring temporary firmware corresponding to an MCU to be burned, and burning the temporary firmware into the MCU to be burned;
acquiring the MCU software production data to be burned, and transmitting the MCU software production data to be burned to the temporary firmware through a secure channel;
and the temporary firmware writes the production data of the MCU software to be burned into the Flash of the MCU to be burned.
2. The method for safely burning the MCU software production data according to claim 1, wherein before obtaining the temporary firmware corresponding to the MCU to be burned, further comprises:
and creating temporary firmware corresponding to the MCU to be burned according to the model of the MCU to be burned.
3. The method for realizing safe burning of MCU software production data according to claim 1, wherein the safe channel comprises:
based on the link application, determining safety communication between the PC end production tool and the cloud end;
and determining the safety communication between the PC end production tool and the MCU according to the communication parameters.
4. The method for safely burning the MCU software production data according to claim 3, further comprising, before obtaining the MCU software production data to be burned:
creating a product to be burned, wherein the product to be burned uses the MCU to be burned;
creating a version of the product to be burned based on the product to be burned, wherein the version of the product to be burned comprises a plurality of software production data;
and creating a batch of the product to be burned based on the version of the product to be burned.
5. The method of claim 4, wherein the software production data comprises firmware, factory data, keys, certificates, and configuration information.
6. The method for safely burning the MCU software production data according to claim 1, wherein obtaining the MCU software production data to be burned comprises:
acquiring authentication information of the MCU to be burned;
and obtaining the MCU software production data to be burned based on the authentication information of the MCU to be burned.
7. The method for realizing safe burning of MCU software production data according to claim 1, wherein the temporary firmware writes the MCU software production data to be burned into Flash of the MCU to be burned, comprising:
the MCU software production data to be burned is data for enabling the safety characteristic, and the data for enabling the safety characteristic comprises any one of starting Flash encryption, enabling safe starting and closing a debugging interface.
8. The safe burning system for realizing MCU software production data is characterized by comprising the following components: cloud, PC end production instrument, write ware, MCU, interim firmware, wherein the cloud with PC end production instrument is connected, PC end production instrument with MCU connects, PC end production instrument with write ware connects, write ware with MCU passes through write interface connection, interim firmware is located MCU.
9. The system for realizing safe burning of MCU software production data according to claim 8, wherein the cloud end is connected with the PC end production tool through a network;
the PC end production tool is connected with the MCU through a serial port or a bidirectional communication interface;
the PC end production tool is connected with the burner through a USB;
the burner is connected with the MCU through a burning interface.
10. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor, when executing the program, realizes the steps of a method for realizing the secure burning of MCU software production data according to any of claims 1 to 8.
CN202311478482.7A 2023-11-07 2023-11-07 Method, system and equipment for realizing safe burning of MCU software production data Pending CN117492777A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202311478482.7A CN117492777A (en) 2023-11-07 2023-11-07 Method, system and equipment for realizing safe burning of MCU software production data

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202311478482.7A CN117492777A (en) 2023-11-07 2023-11-07 Method, system and equipment for realizing safe burning of MCU software production data

Publications (1)

Publication Number Publication Date
CN117492777A true CN117492777A (en) 2024-02-02

Family

ID=89677709

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202311478482.7A Pending CN117492777A (en) 2023-11-07 2023-11-07 Method, system and equipment for realizing safe burning of MCU software production data

Country Status (1)

Country Link
CN (1) CN117492777A (en)

Similar Documents

Publication Publication Date Title
CN107547571B (en) Method for managing access control and access control client provisioning server
WO2020093214A1 (en) Application program login method, application program login device and mobile terminal
US8966580B2 (en) System and method for copying protected data from one secured storage device to another via a third party
RU2289157C2 (en) Method and system for distributed program development for programmable portable information medium
KR101657613B1 (en) Backing up digital content that is stored in a secured storage device
US20030114144A1 (en) Application authentication system
CN109313690A (en) Self-contained encryption boot policy verifying
CN112673600B (en) Multiple security authentication system and method between mobile phone terminal and internet of things (IoT) device based on blockchain
CN103051451A (en) Encryption authentication of security service execution environment
WO2018090763A1 (en) Method and device for configuring terminal master key
WO2015019110A1 (en) Secure data storage
US20080126802A1 (en) Inter-system binding method and application based on hardware security unit
JP2008251021A (en) Application authentication system
CN111401901B (en) Authentication method and device of biological payment device, computer device and storage medium
WO2017166362A1 (en) Esim number writing method, security system, esim number server, and terminal
CN108491724A (en) A kind of hardware based computer interface encryption device and method
CN115129332A (en) Firmware burning method, computer equipment and readable storage medium
JPWO2006075355A1 (en) Peripheral device of programmable logic controller
JP5680617B2 (en) Secure data sharing system and execution method
CN1964272B (en) A method and device to safely exchange computer data
CN104104650A (en) Data file visit method and terminal equipment
TWI827906B (en) Message transmitting system, user device and hardware security module for use therein
KR101711024B1 (en) Method for accessing temper-proof device and apparatus enabling of the method
CN117492777A (en) Method, system and equipment for realizing safe burning of MCU software production data
CN115688120A (en) Secure chip firmware importing method, secure chip and computer readable storage medium

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