TW201342238A - System-on-chip and booting method thereof - Google Patents

Abstract

A system-on-chip(SoC) and a booting method using the same are provided, the SoC is coupled to an external memory, and includes a ROM and a processor. The ROM is configured to store a first firmware image. The processor is coupled to the ROM, and is configured to access the first firmware image from the ROM and check state of the first firmware image. The CPU accesses a second firmware image from the external memory if the first firmware image is damaged, and check whether the second firmware image is legal. The processor accesses and executes the second firmware image to performs a booting process if the second firmware image is checked successfully.

Description

System single chip and booting method thereof

The present invention relates to a wafer, and more particularly to a system-on-chip (SoC) and a method of starting the same.

In general, a system-on-a-chip or system-level integration (SLI) refers to placing a complete computer system into a single chip or integrated circuit. For example, a common system single chip may include a central processing unit (CPU), a memory, and peripheral circuits and the like. The main concept of the system single chip is to reduce and/or modularize the circuit of a certain application field, so that most of the functions of this application field are integrated into one chip or integrated circuit, so as to reduce the size of the product and / or easy to carry.

During the booting of the system single chip, the central processing unit of the system single chip will obtain a unique firmware image from a storage medium and execute the firmware image for booting. However, when the firmware image is corrupted or cannot be completely read, it may cause the system single chip to fail to boot properly.

The invention provides a system single chip and a booting method thereof, which can effectively improve the flexibility of using the firmware when the system single chip is turned on.

The invention provides a system single chip, the system single chip is coupled to an external memory, and the system single chip comprises a read-only memory and a processor. The read-only memory is used to store a first firmware image. The processor is coupled to the read-only memory for reading a first firmware image from the read-only memory and verifying whether the first firmware image has been corrupted.

If the first firmware image is a normal firmware image, the processor executes the first firmware image to boot the program. If the first firmware image is corrupted, the processor reads a second firmware image from the external memory and verifies whether the second firmware image is a legal firmware image. If the second firmware image is successfully verified, the processor executes the second firmware image to start the program.

From another point of view, the present invention also proposes a booting method, which is applicable to a system single chip, the system single chip includes a processor, and the booting method includes: providing a read-only memory, wherein the read-only memory Storing a first firmware image; providing an external memory, wherein the external memory stores a second firmware image; the processor reads the first firmware image from the read-only memory, and verifies the first Whether the firmware image file is damaged; if the first firmware image is a normal firmware image, execute the first firmware image to start the program; if the first firmware image is damaged, read from the external memory. Take the second firmware image and verify that the second firmware image is legal; if the second firmware image is successfully verified, execute the second firmware image. The file is booted.

Based on the above, the system single chip of the present invention and the booting method thereof can provide two or more firmware images in advance to load a legal and/or complete firmware image during the booting of the system single chip. File to complete the boot process.

The above described features and advantages of the invention will be apparent from the following description.

10‧‧‧ boot system

11‧‧‧External memory

12‧‧‧System Single Chip

122‧‧‧Read-only memory

124‧‧‧Data Memory

126‧‧‧Programmable memory

128‧‧‧Central Processing Unit

31‧‧‧First storage area

32‧‧‧Second storage area

312, 322‧‧‧ wafer function storage area

314, 324‧‧‧ firmware image file storage area

316, 326‧‧‧ firmware information storage area

41‧‧‧Image length field

42‧‧‧Image stall code field

43‧‧‧Signature field

44‧‧‧Check the sum field

45‧‧‧ check code field

S202~S218, S502~S528‧‧‧ steps

FIG. 1 is a schematic diagram of a system for booting a single wafer of a system according to an embodiment of the invention.

FIG. 2 illustrates a booting method according to an embodiment of the invention.

FIG. 3 is a schematic diagram of an external memory storage firmware image file according to an embodiment of the invention.

4 is a schematic diagram of a format of a firmware image file according to an embodiment of the invention.

FIG. 5 is a flowchart of a booting method according to an embodiment of the invention.

FIG. 1 is a schematic diagram of a system on a chip (SoC) booting system according to an embodiment of the invention. Referring to FIG. 1, the system single-chip booting system 10 includes an external memory 11 and a system single chip 12. External memory The body 11 is, for example, a flash memory or a variety of storage media that can be used to store data. The system single chip 12 is a single chip integrated by electronic circuits such as a processor and a memory, for example, a system single chip suitable for processing signals of a universal serial bus (USB) 2.0 or USB 3.0, and the like, and The invention does not limit the type of system single wafer 12. The external memory 11 and the system single chip 12 are coupled to each other by, for example, various bus bars such as a serial peripheral interface (SPI) bus.

The system single chip 12 includes a read only memory (ROM) 122, a data memory 124, a programmable memory 126, and a processor 128. The read-only memory 122 can be used to store data previously written by the system single chip 12 from the factory. The data memory 124 and the programmable memory 126 are, for example, random access memory (RAM). In particular, since the programmable memory 126 is mainly used to store a binary code, and the data memory 124 is mainly used to store other various data, the data memory 124 needs to have a faster read. The writing speed is not limited, and the read/write speed of the programmable memory 126 is not limited. The processor 128 is the core component of the system single chip 12, and is responsible for the overall operation of the system single chip 12, and provides arithmetic and data processing functions.

In this embodiment, the read-only memory 122 stores a first firmware image, the external memory 11 stores a second firmware image, and the two firmware images can respectively have a system. Setting and/or driving of individual components or electronic circuits in the single wafer 12. The first firmware image may or may not be the same as the second firmware image. For example, the second firmware image may be the first firmware Backup of the image file. Alternatively, the first firmware image and the second firmware image may also be different versions of the firmware image (for example, different driver versions, etc.), depending on practical requirements.

When the first firmware image stored in the read-only memory 122 is corrupted or the processor 128 cannot completely read the first firmware image, the processor 128 reads the second in the external memory 11 instead. The firmware image file is used to boot the system single chip 11 using the second firmware image.

FIG. 2 is a schematic diagram of a booting method according to an embodiment of the present disclosure. The method will be described in detail below with the system single-chip booting system 10 in conjunction with FIG. 2. Referring to FIG. 1 and FIG. 2 simultaneously, in step S202, a read-only memory 122 is provided, wherein the read-only memory 122 stores a first firmware image. In step S204, the external memory 11 is provided, wherein the external memory 11 stores a second firmware image.

In step S206, when the processor 128 detects a power-on signal or detects that the system single chip 12 is powered on, the processor 128 can read the first firmware image from the read-only memory 122. Then, in step S208, the processor 128 verifies whether the first firmware image is a normal or complete firmware image.

If the first firmware image is a normal firmware file or is complete, in step S210, the processor 128 reads the first firmware image for booting. If the first firmware image has corrupted or incomplete firmware image, the processor 128 can continue to read and execute the second firmware image from the external memory 11 in step S212.

Then, in step S214, the processor 128 verifies whether the second firmware image is legal or complete. If the second firmware image is legal or complete, in step In step S214, the processor 128 executes the second firmware image to perform the booting process.

In step S216, if the second firmware image is an incomplete or illegal firmware image, the processor 128 may execute a basic boot process stored in the read-only memory 122 to be under limited conditions. The system single chip 12 is powered on. In particular, if the processor 128 only turns on the system single chip 12 using the basic boot process, most of the components and/or electronic circuits in the system single chip 12 may not be fully driven (because of detailed settings and/or drivers). The information is defined in the firmware image and greatly reduces the functionality that the system single chip 12 can provide.

FIG. 3 is a schematic diagram of a storage firmware image file according to an embodiment of the present disclosure. Referring to FIG. 3, the first storage area 31 is located in the read-only memory 122, and the second storage area 32 is located in the external memory 11. The first storage area 31 is configured to store the first firmware image and the first auxiliary information, and the second storage area 32 is configured to store the second firmware image and the second auxiliary information.

In detail, the first storage area 31 may include a wafer function storage area 312, a firmware image storage area 314, and a firmware information storage area 316. The wafer function storage area 312 is used to store some additional setting information of the system single chip 12, such as power settings of various components in the system single chip 12, and the like. The firmware image storage area 314 is used to store the first firmware image. The firmware information storage area 316 is used to store user-defined information related to the first firmware image, such as a user name, a user-defined string, and/or a time out setting. and many more.

The chip function storage area 312 and the firmware information storage area 316 store the first auxiliary information. Similarly, the second storage area 32 may also include a wafer function storage area. 322. The firmware image storage area 324 and the firmware information storage area 326, wherein the chip function storage area 322 is used to store some additional setting information of the system single chip 12, and the firmware image storage area 324 is used to store the second firmware. The image file and the firmware information storage area 326 are used to store user-defined information related to the second firmware image. The chip function storage area 322 and the firmware information storage area 326 store the second auxiliary information. However, the embodiments of the present invention are not limited thereto.

In the present case, the read-only memory 122 and/or the external memory 11 may also include other storage areas for storing other firmware images (eg, third firmware images) and/or auxiliary information (eg, Three auxiliary information) and so on.

In addition, FIG. 4 is a schematic diagram of a format of a firmware image file according to an embodiment of the present disclosure. Referring to FIG. 4, for example, the firmware image storage area 314 storing the first firmware image includes the image length field 41 and the binary code field. 42. Signature field 43, checksum field 44 and check code field 45.

The image length field 41 is used to store the length information of the first firmware image, and the length information can be used to query information of other fields (for example, the starting address or the number of bits of each field). The bit code field 42 is used to store the image file bit code of the first firmware image (hereinafter collectively referred to as the first image file bit code), that is, the program body of the first firmware image file. The signature field 43 is used to store the signature of the first firmware image (hereinafter collectively referred to as the first signature), and the checksum field 44 is used to store the checksum of the first firmware image and the check code column. Bit 45 is used to store the check code of the first firmware image (hereinafter collectively referred to as the first check code). In this embodiment, the check code is for example It is a Cyclic Redundancy Check (CRC), but the type of check code is changed according to the requirements of the actual practice. In this embodiment, the firmware image storage area 314 and the length of each field can be adjusted according to practical requirements.

In particular, the signature of the first firmware image in the signature field 43, the sum of the checks of the first firmware image in the sum field 44, and the first firmware image in the check code field 45. The check code can be used simultaneously or separately to verify that the first firmware image is legal or complete. In addition, the format of the second firmware image file and the firmware image file storage area 324 can be analogized from the first firmware image file and the firmware image file storage area 314, and details are not described herein.

In detail, FIG. 5 is a flowchart of a booting method according to an embodiment of the present disclosure. Referring to FIG. 1 and FIG. 5 simultaneously, in step S502, the processor 128 detects a boot signal or verifies whether the system single chip 12 is powered. If the processor 128 detects the power-on signal or the system single chip 12 is powered on, the processor 128 can read the first signature in the first firmware image from the read-only memory 122 (eg, from the signature of FIG. 4) Field 43).

Taking FIG. 3 as an example, the processor 128 can read the information in the firmware image storage area 314 from the address 0X0080 in the read-only memory 122. Next, in step S506, the processor 128 reads a pre-stored verification signature from the read-only memory 122 and verifies whether the first signature is identical to the verification signature. If the first signature is the same as the verification signature, in step S508, the processor 128 reads the first verification code and the first image file in the first firmware image from the read-only memory 122. (for example, from the check code field 45 of Figure 4 and the image file size field 42), the first school will be The code is stored in the data memory 124, and the first image file is stored in the programmable memory 126.

Then, in step S510, the processor 128 calculates a first evaluation code based on the first mapped gear bit code. Next, in step S512, the processor 128 verifies whether the first evaluation code is the same as the first verification code. If the first evaluation code is the same as the first verification code, it indicates that the first firmware image is a normal firmware image or is complete. Therefore, in step S514, the processor 128 executes the storage in the programmable memory 126. The first image file of the first firmware image is booted.

In addition, in step S506, if the first signature is different from the verification signature, or in step S512, if the first evaluation code is different from the first verification code, it indicates that the first firmware image is damaged or complete. of. Therefore, in step S516, the processor 128 can continue to read the signature in the second firmware image from the external memory 11 (hereinafter collectively referred to as the second signature), and store the second signature in the data memory. 124.

Taking FIG. 3 as an example, the processor 128 can read the information in the firmware image storage area 324 from the address 0X10080 in the external memory 11. Then, in step S518, the processor 128 also verifies whether the second signature is identical to the verification signature previously stored in the read-only memory 122. If the first signature is the same as the verification signature, the processor 128 reads the verification code (hereinafter collectively referred to as the second verification code) in the second firmware image from the external memory 11 in step S520. The image file element code (hereinafter collectively referred to as the second image file bit code) stores the second check code in the data memory 124 and stores the second image file in the programmable memory 126.

Then, in step S522, the processor 128 is based on the second image file bit. The code calculates a second evaluation code. Next, in step S524, the processor 128 verifies whether the second evaluation code is the same as the second verification code. If the second evaluation code is the same as the second verification code, indicating that the second firmware image is legal or complete, therefore, in step S526, the processor 128 executes the second firmware image stored in the programmable memory 126. The second image file of the file is used to start the program.

In addition, in step S518, if the second signature is different from the verification signature, or in step S524, if the second evaluation code is different from the second verification code, indicating that the second firmware image verification fails or is not Complete, therefore, in step S528, the processor 128 executes the basic boot process stored in the read only memory 122.

In this embodiment, the processor 128 also records a number of retries in the data memory 124, and initializes the number of retries each time the power-on signal is detected or the system single chip 12 is powered on (for example, zeroing) ). In the verification phase of the first firmware image, if the processor 128 verifies that the first firmware image has been corrupted, the processor 128 may determine, according to the number of retries, that the verification of the first firmware image is repeated. Or switch to the verification phase of the second firmware image. In the verification phase of the second firmware image, the processor 128 can also determine, based on the number of retries, whether the verification of the second firmware image is repeated or to perform the basic boot process.

In addition, in this embodiment, if the processor 128 determines to execute the first firmware image to perform the booting process, the processor 128 may also read the first auxiliary data from the read-only memory 122, according to the first auxiliary. The data performs a first set operation for the system single chip 12. Taking FIG. 3 as an example, the first auxiliary data is, for example, data stored in the chip function storage area 312 and/or the firmware information storage area 316.

If the processor 128 determines to execute the second firmware image to perform the boot process, the processor 128 may also read the second auxiliary data from the external memory 11 to execute the second for the system single chip 12 according to the second auxiliary data. Set the operation. For example, in FIG. 3, the second auxiliary material is, for example, data stored in the chip function storage area 322 and/or the firmware information storage area 326. In addition, the first setting operation and the second setting operation are, for example, additional settings for hardware related resources such as power supply of the system single chip 12, or adding a user-defined name or string or the like to the system.

In addition, in an embodiment, the external memory 11 can also store a third firmware image. If the processor 128 verifies the second firmware image and the verification fails, the processor 128 can read the third firmware image from the external memory 11 and verify whether the third firmware image is legal or complete. of.

If the third firmware image is legal or complete, the processor 128 executes the third firmware image to perform the boot process. If the processor 128 verifies that the third firmware image is also failed to verify or is complete, then the basic boot process is performed.

In this embodiment, the processor 128 can also receive an update command from an input interface, and update the second firmware image stored in the external memory 11 according to the update command, or add a third firmware image. In the external memory 11. For example, assuming that the system single chip 12 is a system single chip supporting USB 3.0, the system single chip 12 will include a USB interface, and the processor 128 can receive an update command from the USB interface. For example, the update command can include a write command and a new firmware image.

After the processor 128 receives the update instruction, the processor 128 may root One or more firmware images in the external memory 11 are selected in accordance with the write command in the update command, and the selected one or more firmware images are updated with the new firmware image. Taking FIG. 3 as an example, if the write command specifies to update the firmware image stored in the firmware image storage area 324 of the external memory 11 with a new firmware image, the processor 128 can externally memorize. Address 0x10080 in volume 11 begins to overlay this new firmware image in firmware image file storage area 314.

In addition, the processor 128 can also update the information stored in the chip function storage area 322, the firmware image storage area 324, and/or the firmware information storage area 326 of the external memory 11 simultaneously or separately according to the update instruction. The elasticity of use of the present invention.

It is worth mentioning that the address of the first firmware image and the second firmware image stored in the external memory 11 and/or the read-only memory 122 may also be the boot process of the system single chip 12. The processor 128 is adaptively determined. In other words, taking FIG. 3 as an example, the processor 128 can actually treat the firmware image stored in the first storage area 31 as the first firmware image and the firmware image stored in the second storage area 32. Considered as the second firmware image. Alternatively, the processor 128 may also regard the firmware image stored in the second storage area 32 as the first firmware image and the firmware image stored in the first storage area 31 as the second firmware image. File, depending on the situation, can have different options.

For example, in an embodiment, when the processor 128 updates the firmware image stored in the external memory 11, the processor 128 can synchronously update a firmware update information stored in the external memory 11. Then, on the system single chip 12 During the process, the processor 128 can query the firmware update information, and determine the address of the first firmware image and the second firmware image according to the firmware update information. For example, by querying the firmware update information, the processor 128 may select the firmware version file with the latest version or the highest reading priority from the one or more firmware images in the read-only memory 122 as the first toughness. The image file is preferentially read and verified, and the firmware image with the latest version or the highest reading priority is selected from one or more firmware images in the external memory 11 as the second firmware image, etc. Wait. After the verification of the first and/or second firmware image with the latest version or the highest read priority, the processor 128 can also read other firmware images according to the firmware update information, and repeat the above verification. Actions are not repeated here.

In addition, the firmware update information may also be set by the processor 128 according to the user's operation, such as defining a read priority order of each firmware image file, and the like.

In particular, the firmware update information may further include various identification information such as an update time of the firmware image file in each firmware image storage area. In this way, the processor 128 can use the firmware update file in the external memory 11 as the second firmware image as the second firmware image according to the firmware update information, and update the firmware in the external memory 11 with an earlier update time. The image file is the third firmware image file read after the failure of the second firmware image verification, and the like, and the present invention is not limited thereto.

In summary, the system single chip of the present invention and the booting method thereof can provide two or more firmware images in advance to load legal and/or complete toughness during the booting process of the system single chip. The image file is used to complete the boot process.

Although the present invention has been disclosed in the above embodiments, it is not intended to limit the present invention, and any one of ordinary skill in the art can make some changes and refinements without departing from the spirit and scope of the present invention. The scope of the invention is defined by the scope of the appended claims.

S202~S218‧‧‧Steps

Claims (17)

A system single chip coupled to an external memory, the system single chip includes: a read-only memory for storing a first firmware image; and a processor coupled to the read-only memory for self- The read-only memory reads the first firmware image and verifies the state of the first firmware image. If the first firmware image is in a normal state, the processor executes the first firmware image. To perform a booting process, if the first firmware image is in a corrupted state, the processor reads a second firmware image from the external memory, and verifies whether the second firmware image is legal; The second firmware image is verified to be legitimate, and the processor executes the second firmware image to execute the boot process. The system single chip of claim 1, wherein the processor reads a first signature in the first firmware image from the read-only memory, and determines whether the first signature is The preset verification signature is the same. If the first signature is different from the verification signature, the processor determines that the first firmware image is a corrupted firmware image. The system single chip of claim 2, wherein if the first signature is the same as the verification signature, the processor reads a first one of the first firmware images from the read-only memory. a check code and a first image file bit code, calculating a first evaluation code according to the first image file bit code, and verifying whether the first evaluation code is the same as the first verification code, wherein The first evaluation code is the same as the first verification code, and the processor determines that The first firmware image is a normal firmware image. The system single chip of claim 1, wherein the processor reads a second signature from the external firmware from the external memory and verifies whether the second signature is The verification signature is the same, wherein if the second signature is different from the verification signature, the processor determines that the second firmware image verification fails. The system single chip of claim 4, wherein if the second signature is the same as the verification signature, the processor reads a second one of the second firmware images from the external memory. a check code and a second image file bit code, calculating a second evaluation code according to the second image file bit code, and determining whether the second evaluation code is the same as the second verification code, wherein the first The second evaluation code is the same as the second verification code, and the processor determines that the second firmware image is successfully verified. The system single chip of claim 1, wherein the processor further updates the second firmware image stored in the external memory according to an update command, or adds a third firmware image. In the external memory. The system single chip of claim 1, wherein the read-only memory has a first storage area, the first storage area stores the first firmware image and a first auxiliary material, the external The memory has a second storage area, and the second storage area stores the second firmware image and a second auxiliary data, wherein if the processor executes the first firmware image to execute the booting process, the The processor reads the first auxiliary data from the read-only memory to perform a first setting operation on the single-chip of the system according to the first auxiliary data, If the processor executes the booting process by executing the second firmware image, the processor further reads the second auxiliary data from the external memory to perform one for the single chip of the system according to the second auxiliary data. The second setting operation. The system single chip of claim 1, wherein the external memory stores a third firmware image, wherein the processor reads from the external memory if the second firmware image fails to be verified. The third firmware image file and verifying whether the third firmware image file is legal. If the third firmware image file is successfully verified, the processor executes the third firmware image file to execute the booting process. A booting method is applicable to a system single chip, the system single chip includes a processor, the booting method includes: providing a read-only memory, wherein the read-only memory stores a first firmware image; providing an external a memory, wherein the external memory stores a second firmware image; the processor reads the first firmware image from the read-only memory, and verifies the state of the first firmware image; The first firmware image is in a normal state, and the first firmware image is executed to perform a booting process; if the first firmware image is in a damaged state, the second firmware is read from the external memory. An image file and verifying whether the second firmware image file is legal; and if the second firmware image file is successfully verified, executing the second firmware image file execution The boot process. The booting method of claim 9, wherein the processor reads the first firmware image from the read-only memory and verifies whether the first firmware image has been damaged: The read-only memory reads a first signature in the first firmware image; verifies whether the first signature is the same as a preset verification signature; and if the first signature is signed with the verification signature The chapter is different, and it is determined that the first firmware image has been corrupted. The booting method of claim 10, wherein the step of reading, by the processor, the first firmware image from the read-only memory and verifying whether the first firmware image has been corrupted further comprises If the first signature is the same as the verification signature, reading a first verification code and a first mapping location code in the first firmware image from the read-only memory; Calculating a first evaluation code by an image gear bit code; verifying whether the first evaluation code is the same as the first verification code; and determining the first toughness if the first evaluation code is the same as the first verification code The body image is a normal firmware image. The booting method of claim 9, wherein the step of reading the second firmware image from the external memory and verifying whether the second firmware image is legal comprises: from the external memory Reading a second signature in the second firmware image; verifying whether the second signature is the same as a preset verification signature; If the second signature is different from the verification signature, it is determined that the verification of the second firmware image fails. The booting method of claim 12, wherein the step of reading the second firmware image from the external memory and verifying whether the second firmware image is legal further comprises: if the The second signature is the same as the verification signature, and reads a second verification code and a second image location code in the second firmware image from the external memory; according to the second image file bit The code calculates a second evaluation code; verifies whether the second evaluation code is the same as the second verification code; and if the second evaluation code is the same as the second verification code, determines that the second firmware image is successfully verified of. The booting method of claim 9, further comprising: updating the second firmware image stored in the external memory according to an update command, or adding a third firmware image to the external In memory. For example, the booting method described in claim 14 further includes: synchronously updating a firmware update information; and querying the firmware update information during the booting of the single chip of the system, to determine the firmware update information according to the firmware update information. The address of the first firmware image file and the second firmware image file. The booting method of claim 9, wherein the step of executing the first firmware image to execute the booting process comprises: reading a first auxiliary material from the read-only memory, according to the first auxiliary Capital Performing a first setting operation for the single chip of the system, wherein performing the second firmware image to perform the booting process comprises: reading a second auxiliary material from the external memory, according to the second auxiliary The data performs a second set operation for the single wafer of the system. The booting method of claim 9, further comprising: if the second firmware image fails to be verified, reading a third firmware image from the external memory, and verifying the third firmware image Whether the file is legal; and if the third firmware image is successfully verified, executing the third firmware image to execute the booting process.