Method and system for controlling a device

Abstract

A system and method for controlling a device. Data that was encrypted using a first encryption scheme is decrypted, then re-encrypted using a second encryption scheme. The re-encrypted data is then decrypted.

Description

BACKGROUND

Various electronic devices provide characteristics that can be changed after production, including digital signal processors (DSP), field programmable gate arrays (FPGA), etc. For example, an FPGA is an integrated circuit device containing programmable logic components sometimes referred to as “logic blocks,” and programmable interconnects. Logic blocks can be programmed to perform the function of basic logic gates such as AND, and XOR, or more complex combinational functions such as decoders or simple mathematical functions. In most FPGAs, the logic blocks also include memory elements, which may be simple flip-flops or more complete blocks of memories. The logic blocks and interconnects can be programmed after the FPGA is manufactured (“field programmable”) to implement the desired functions.

Such devices may have a trustworthiness that is limited due to a lack of a root of trust at the start of the device lifecycle and throughout the subsequent lifecycle stages. Encryption is typically disabled in reconfigurable logic devices such as FPGAs when the FPGAs are manufactured. FPGA system integrators or equipment manufacturers have to enable encryption and program the encryption key into the FPGA. Accordingly, monitoring functions or audit mechanisms are lacking The manufacturing environment is inherently insecure and can be prone to attacks.

For these and other reasons, there is a need for the present invention.

SUMMARY

Embodiments of a system and method for controlling a device are disclosed. Data that was encrypted using a first encryption scheme is decrypted, then re-encrypted using a second encryption scheme. The re-encrypted data is then decrypted.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the invention are better understood with reference to the following drawings. The elements of the drawings are not necessarily to scale relative to each other. Like reference numerals designate corresponding similar parts.

FIG. 1 is a block diagram conceptually illustrating aspects of a device.

FIG. 2 is a block diagram conceptually illustrating aspects an embodiment of a FPGA system.

FIG. 3 illustrates aspects of the system of FIG. 2.

FIG. 4 is a block diagram conceptually illustrating aspects of another embodiment of a FPGA system.

DETAILED DESCRIPTION

In the following Detailed Description, reference is made to the accompanying drawings, which form a part hereof, and in which is shown by way of illustration specific embodiments in which the invention may be practiced. In this regard, directional terminology, such as “top,” “bottom,” “front,” “back,” “leading,” “trailing,” etc., is used with reference to the orientation of the Figure(s) being described. Because components of embodiments of the present invention can be positioned in a number of different orientations, the directional terminology is used for purposes of illustration and is in no way limiting. It is to be understood that other embodiments may be utilized and structural or logical changes may be made without departing from the scope of the present invention. The following detailed description, therefore, is not to be taken in a limiting sense, and the scope of the present invention is defined by the appended claims.

FIG. 1 is block diagram conceptually illustrating aspects of a device 100. In one embodiment, the device 100 is a integrated circuit device. Many types of integrated circuit devices have characteristics or programs that can be changed or require updating after production, such as various microprocessors or microcontrollers, digital signal processors (DSP), field programmable gate arrays (FPGA), etc.

Certain integrated circuit devices, such as FPGAs, may require updating or upgrading. The embodiments of the system 100 illustrated in FIG. 1 include a device 110 that may require such upgrading. A controller 112 is coupled to the device 110 and provides a trusted core for reconfiguring or upgrading aspects of the device 110, which is especially useful when the system 100 is deployed in an untrusted environment. The controller 112 communicates with and controls the configuration and operation of the device 110. In some embodiments, multiple devices are associated with a single controller 112, though in FIG. 1 and subsequent figures a single device 110 is illustrated for sake of simplicity. The terms “coupled,” “connected,” along with derivatives and other similar terms are meant to indicate that the relevant elements cooperate or interact with each other regardless of whether they are in direct physical or electrical contact.

The provision of the controller 112 enables trusted changes and upgrades for devices 110 on an individual basis. The controller 112 and the device 110 can be implemented on a single die or on multiple die in a suitable package such as a multi-chip module.

FIG. 2 illustrates aspects of an embodiment where the device 110 is a field programmable gate array (FPGA). In other embodiments, the device 110 could include other types of integrated circuit devices. In FIG. 2, information for programming or upgrading the device 110 is controlled by the secure microcontroller 112. Examples of suitable secure microcontrollers include a model SLE88CFX4002P microcontroller available from Infineon Technologies AG. The secure microcontroller 112 supports the secure operation of individual processes, enables convenient use for secure applications and allows secure encapsulation of a running process from other processes. For example, the secure microcontroller 112 provides execution of applications in compliance with specific trust criteria for different linked libraries. Specific features can include memory management and the provision of secure firewalls between security-sensitive partitions in an application.

Example embodiments of the secure microcontroller 112 include a central processing unit (CPU) 130 and memories such as ROM, RAM, Flash, etc. An operating system 132 is stored in a ROM, and a secure memory 134 is included in the illustrated embodiment. The secure microcontroller 112 also includes peripherals 136, such as a random number generator, interrupt module, crypto coprocessor, DES accelerator, UART, configurable internal control oscillator, and a suitable number of timers such as three timers. The CPU 130, operating system 132, secure memory 134, peripherals 136, and one or more interfaces (JTAG, USB, PCMCIA, ISO 7816, etc.) are coupled together via a bus system 138. The example secure microcontroller illustrated in FIG. 2 includes a first interface 150, such as an ISO7816 standard smartcard interface, and a second interface 152 such as a JTAG interface.

The FPGA 110 includes a user programmable area 140 and secure storage, such as a hardwired area 142. A secure microcontroller interface 150 is connectable to the corresponding interface in the secure microcontroller 112 via an appropriate link. FIG. 3 illustrates further aspects of the hardwired area 142 of the FPGA 110. An encryption/decryption engine 144 and a programming interface 146 are provided in the hardwired area 142, among other things. The hardwired area 142 further includes a JTAG interface 152 connected to the JTAG interface 152 of the secure microcontroller 112.

The secure microcontroller 112 generates and stores one or more keys 160 in exemplary embodiments. In this disclosure, a “key” is intended to include one or more keys and can refer to any suitable data that can be used to control access to the relevant device. In certain embodiments, the format of the key is compatible with a symmetrical cryptography algorithm, such as the Advanced Encryption Standard (AES) or the Triple Data Encryption Standard (TDES). In other embodiments, the key includes a block of any suitable predetermined data or random data. For example, an FPGA programming key 160 is stored in the secure memory 134 of the secure microcontroller 112. The FPGA programming key 160 is further stored in the hardwired area 142 of the FPGA 110 in some embodiments.

To program or reconfigure the FPGA 110, a secure or trusted communication channel is established between the external system 114 and the secure microcontroller 112 via mutual authentication. In the system of FIG. 2, the external system is an external host system. After establishing a communication channel via the interface 150 of the secure microcontroller 112, the host 114 sends encrypted data, such as an encrypted image, to the FPGA system 100. More specifically, the encrypted data are sent to the secure microcontroller 112 of the FPGA system 100 in exemplary embodiments. The data sent from the host 114 to the secure microcontroller 112 is encrypted using a first encryption scheme, for example, an asymmetric encryption scheme. In embodiments where the first encryption scheme is an asymmetric scheme, the decrypting the data includes using a private key of the secure microcontroller 112.

The secure microcontroller 112 decrypts the encrypted image received from the host 114, and then re-encrypts the data using the FPGA key 160. In certain embodiments, the data is re-encrypted using a second encryption scheme, such as a symmetric encryption scheme wherein the FPGA key 160 would be a symmetric key. In other embodiments, the first encryption scheme is a symmetric encryption scheme and the second encryption scheme is an asymmetric encryption scheme. In still further embodiments, both the first and second encryption schemes are asymmetric, or both the first and second encryption schemes are symmetric encryption schemes.

In the embodiment illustrated in FIG. 2, the re-encrypted data is sent to the FPGA encryption/decryption engine 144 via the JTAG interface 152. In one embodiment, the image is received by the secure microcontroller in small pieces of data, or records. The decryption engine 144 decrypts the encrypted data using the key 160 stored in the secure memory 134 and/or within the hardwired area 142 of the FPGA 110.

The decrypted data can then be used to program the device 110. For example, the decrypted data is used to reconfigure desired portions of the FPGA 110 in certain embodiments. Further, the secure microcontroller 112 can be programmed to create a digital signature or CRC using the configuration data. The digital signature or CRC can be stored in the secure microcontroller 112, for example, in the secure memory 134. The next time the FPGA 110 is reconfigured, the digital signature or CRC may be verified by the secure microcontroller 112. The digital signature ensures the integrity of the FPGA image and ensures that the device has not been reconfigured during the intervening period. In response to verifying the signature, the FPGA 110 is programmed. If the digital signature cannot be verified, the secure microcontroller 112 can report back to the host system 114 that the trust level of the system 100 has been changed. In this situation, the host 114 can decide whether to complete the reconfiguration.

The secure microcontroller 112 can control the reconfiguration of any suitable number of logic cells in the FPGA 110, the reconfiguration of two or more FPGAs 110, or the reconfiguration of two or more partitions within an FPGA 110.

FIG. 4 illustrates another embodiment where the external system 114 includes a generic microcontroller 115, which includes an external interface 170 for coupling to an external host or other system as desired. In FIG. 4, the programming, updating, etc. is controlled through the generic microcontroller 115. The secure microcontroller 112 of the embodiment illustrated in FIG. 4 is similar to that illustrated in FIG. 2, but it does not include a JTAG interface. Instead, the generic microcontroller 115 has a JTAG interface 152 that is connectable to the corresponding interface of the FPGA 110.

Accordingly, the trusted communication channel is established between the external host 114, through the generic microcontroller 115, and the secure microcontroller 112 via mutual authentication. The generic microcontroller 115 forwards the encrypted data, or image from an external system connected to the interface 170, to the secure microcontroller 112.

In some embodiments, the FPGA 110 does not include the secure storage 142. If the FPGA 110 uses volatile memory, such as an SRAM FPGA, to store programming code, the programming code needs to be loaded into the FPGA 110 each time the FPGA 110 is powered up. In this case, the microcontroller 112 stores the programming code in the secure memory 134, and securely transfers the programming code to the FPGA 110 in the manner disclosed above when it is powered up.

Although specific embodiments have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art that a variety of alternate and/or equivalent implementations may be substituted for the specific embodiments shown and described without departing from the scope of the present invention. This application is intended to cover any adaptations or variations of the specific embodiments discussed herein. Therefore, it is intended that this invention be limited only by the claims and the equivalents thereof.

Claims

1. A method of controlling a secure FPGA system comprising a secure microcontroller and an FPGA, the method comprising: decrypting data that was encrypted using a first encryption scheme via the secure microcontroller;re-encrypting the data using a second encryption scheme via the secure microcontroller;sending the encrypted data to the FPGA coupled to the secure microcontroller; anddecrypting the encrypted data by a decryption engine in the FPGA,wherein the FPGA has a programmable area and a hardwired area,wherein the secure microcontroller and the FPGA are implemented on a single die or on multiple die in a package with a first secure interface between the secure microcontroller and the FPGA programmable area and a second interface between the secure microcontroller the FPGA hardwired area.

2. The method of claim 1, wherein the encrypted data are sent to the FPGA on each start-up of the FPGA.

3. The method of claim 1 comprising: storing the data within the secure microcontroller.

4. The method of claim 1 comprising: programming the FPGA using the data.

5. The method of claim 1, wherein the first encryption scheme is an asymmetric encryption scheme and the second encryption scheme is a symmetric encryption scheme or wherein the first encryption scheme is a symmetric encryption scheme and the second encryption scheme is an asymmetric encryption scheme or wherein the first and second encryption schemes are symmetric encryption schemes or wherein the first and second encryption schemes are asymmetric encryption schemes.

6. The method of claim 5, wherein decrypting the data comprises using a private key, and wherein re-encrypting the data comprises using a symmetric key.

7. The method of claim 1 comprising: establishing a secure communications channel between the secure microcontroller and an external system.

8. The method of claim 7, wherein establishing a secure communications channel includes authentication between the secure microcontroller and the external system.

9. The method of claim 1 comprising: verifying a digital signature of the data; andprogramming the secure FPGA system in response to verifying the digital signature.

10. The method of claim 1 comprising: sending the re-encrypted data to the FPGA via a generic controller coupled to the secure microcontroller and to the FPGA.

11. The method of claim 1, wherein sending the encrypted data to the FPGA comprises sending the encrypted data via a JTAG interface.

12. A secure FPGA system, comprising: a FPGA having a programmable area and a hardwire area; anda secure microcontroller coupled to the FPGA, the secure microcontroller configured to decrypt data that was encrypted using a first encryption scheme, re-encrypt the data using a second encryption scheme, and send the re-encrypted data to the FPGA,wherein the secure microcontroller and the FPGA are implemented on a single die or on multiple die in a package with a first secure interface between the secure microcontroller and the FPGA programmable area and a second interface between the secure microcontroller the FPGA hardwired area, andwherein the FPGA comprises a decryption engine configured to decrypt the encrypted data, and wherein the decrypted data is used to reconfigure one or more portions of the FPGA.

13. The secure FPGA system of claim 12, wherein the secure microcontroller comprises a memory configured to store one or more keys corresponding to the first encryption scheme and/or the second encryption scheme.

14. The secure FPGA system of claim 12, wherein the FPGA comprises a memory configured to store one or more keys corresponding to the second encryption scheme.

15. The secure FPGA system of claim 12 comprising: a generic controller coupled to the secure microcontroller and the FPGA, wherein the secure microcontroller is configured to send the encrypted data to the FPGA via the generic controller.

16. The secure FPGA system of claim 12, wherein the secure microcontroller includes an external interface and a JTAG interface, and wherein the encrypted information is received via the external interface and the re-encrypted information is sent to the FPGA via the JTAG interface.

17. The secure FPGA system of claim 16, wherein the first encryption scheme is an asymmetric encryption scheme and the second encryption scheme is a symmetric encryption scheme.

18. A method for controlling a device, comprising: providing a controller having a processor, a memory, a first interface, and a second interface;providing a programmable device having a user programmable area and a hardwired area, the hardwired area coupled to the second interface, wherein the controller and the programmable device are implemented on a single die or on multiple die in a package;receiving data that was encrypted using a first encryption scheme via the first interface;decrypting the data that was encrypted using the first encryption scheme by the controller;re-encrypting the data using a second encryption scheme by the controller;sending the re-encrypted data from the controller to the hardwired area of the programmable device via the second interface of the controller; anddecrypting the re-encrypted data by a decryption engine in the hardwired area of the programmable device.

19. The method of claim 18, wherein the first encryption scheme is an asymmetric encryption scheme and the second encryption scheme is a symmetric encryption scheme or wherein the first encryption scheme is a symmetric encryption scheme and the second encryption scheme is an asymmetric encryption scheme or wherein the first and second encryption schemes are symmetric encryption schemes or wherein the first and second encryption schemes are asymmetric encryption schemes.

20. The method of claim 18, comprising: establishing a secure communications channel between the controller and an external system.