Abstract:
A boot code may be segmented to allow separate and independent storage of the code segments in a manner that may enable secure system boot by autonomous fetching and assembling of the boot code by a security sub-system. The code fetching may need to be done without the main CPU running on the chip for security reasons. Because the boot code may be stored in memory devices that require special software application to account for non-contiguous storage of data and/or code, for example a NAND flash memory which would require such an application as Bad Block Management, code segments stored in areas guaranteed to be usable may enable loading remaining segment separately and independently. Each of the code segments may be validated, wherein validation of the code segments may comprise use of hardware-based signatures.

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS/INCORPORATION BY REFERENCE 
       [0001]    This patent application makes reference to, claims priority to and claims benefit from U.S. Provisional Patent Application Ser. No. 60/828,544 filed on Oct. 6, 2006. 
         [0002]    The above stated application is hereby incorporated by reference in its entirety. 
     
    
     FIELD OF THE INVENTION 
       [0003]    Certain embodiments of the invention relate to system security. More specifically, certain embodiments of the invention relate to a method and system for NAND flash support in an autonomously loaded secure reprogrammable system. 
       BACKGROUND OF THE INVENTION 
       [0004]    In an increasingly security-conscious world, protecting access to information and/or to systems from unwanted discovery and/or corruption is a major issue for both consumers and businesses. 
         [0005]    The growth of system connectivity has been one of the major developments in recent years. Fewer and fewer systems are operating as stand-alone boxes, and most of today&#39;s systems are increasingly becoming elements of complex networks. This growth in networking allows improved performance and increased flexibility. However, with this growth in system distribution, system security, and protection against unwanted access and/or corruption, has become a major concern for systems owners and/or operators. Many consumers and systems owners and/or operators may be vulnerable to unwanted access when the level of security provided within the system is insufficient for providing the appropriate protection. In that regard, many deployed systems, may incorporate the use of architectures that enable and improve security management in order to provide the necessary protection from unwanted access. 
         [0006]    Many systems have dedicated security sub-systems, which in addition to monitoring the system security throughout its operations, may also function to ensure that the systems are initially loaded securely. These systems may also comprise processing units, which may be required to perform general processing functions including, but not limited to, loading code and/or data, performing code validation, executing code instructions, and performing memory manipulations. If the system is to be loaded securely, such processing unit need to be assured that it is executing clean code. Therefore, such processing unit may not be running during initial boot stages, and consequently, some of the functionality provided by the processing unit, including, but not limited to, memory operations, may not be available during early boot stages. 
         [0007]    Secure system boot would require loading boot code sets that may be stored in memory. Some memory devices, including for example NAND flash memory devices, may utilize block structure, wherein internal space within these devices may be segmented into block causing data stored in these memory devices that may exceed block size to be stored in different blocks. Also, with such memory devices, some of these blocks may be unusable causing data stored in these devices to span non-contiguous blocks at times. Typically such situations are remedied using specific software operations that mask the internal storing details of these memory devices. 
         [0008]    For example, a NAND flash memory, which may utilize internal block structure, may be arranged in block sizes from 8 k to 128 k (currently), and only the first block is guaranteed to be useable. When data is stored in NAND flash memory, and the size of data exceeds available space in a single block, the data may be stored in multiple blocks that may not necessarily be contiguous. A MIPS-based system incorporating a NAND flash memory for example may use specific software management scheme to manage such NAND flash memory limitations. One such software management scheme is Bad Block Management (BBM) wherein a mapping of different block locations associated with some data is maintained by a software application allowing the system to load the data as a whole regardless of the detail of the storage within the NAND flash memory (which blocks are actually used to store the different parts). Therefore, an application such as BBM would mask the fragmented details of storage within a memory device such as a NAND flash memory allowing the system to operate as if the data was being loaded as a whole. 
         [0009]    Such approach, while practical in most situations, poses a problem during secure system boots. As stated above, during early phases of secure system boots it may be necessary to prevent and/or limit the processing unit operation while the integrity and security of the system is assured. It may be possible the boot code set necessary to allow the system to boot up and perform security operations during early phases of secure system boot may exceed the available area in such the guaranteed block in the NAND flash memory, and some of this boot code set may be stored in other, non-contiguous, blocks. Without the processing unit, the software applications that would allow use of Bad Block Management, for example, may not be available. Therefore, security code that need be loaded to assure the system security and integrity may not be available without the use of the processing unit that may not available during these early phases of secure system boots. 
         [0010]    Further limitations and disadvantages of conventional and traditional approaches will become apparent to one of skill in the art, through comparison of such systems with some aspects of the present invention as set forth in the remainder of the present application with reference to the drawings. 
       BRIEF SUMMARY OF THE INVENTION 
       [0011]    A system and/or method is provided for an autonomously loaded secure system, substantially as shown in and/or described in connection with at least one of the figures, as set forth more completely in the claims. 
         [0012]    These and other advantages, aspects and novel features of the present invention, as well as details of an illustrated embodiment thereof, will be more fully understood from the following description and drawings. 
     
    
     
       BRIEF DESCRIPTION OF SEVERAL VIEWS OF THE DRAWINGS 
         [0013]      FIG. 1  is a block diagram illustrating an exemplary memory, in connection with an embodiment of the invention. 
           [0014]      FIG. 2  is a block diagram illustrating an exemplary memory storage situation, in connection with an embodiment of the invention. 
           [0015]      FIG. 3  is a block diagram illustrating an exemplary structuring of a boot code set within a guaranteed area of a NAND flash memory, which may be utilized in accordance with an embodiment of the invention. 
           [0016]      FIG. 4  is a block diagram illustrating an exemplary system with a NAND flash memory, which may be utilized in accordance with an embodiment of the invention. 
       
    
    
     DETAILED DESCRIPTION OF THE INVENTION 
       [0017]    Certain embodiments of the invention may be found in a method and system for NAND flash support in an autonomously loaded secure reprogrammable system. Exemplary aspects of a method and system for ensuring secure system boot, may comprise segmenting a boot code into various segments that may be stored and validated separately. The segmented boot code may be stored in a memory, such as a NAND flash memory  402 . Since NAND flash memory devices incorporate block structure, with only the first block guaranteed to be usable, only some of the segments of the boot code may be stored in the guaranteed area of the NAND flash memory. The segments stored in the guaranteed area of the NAND flash memory may comprise information that enable locating and validating remaining segments separately. These remaining segments may not be stored in guaranteed areas of the NAND flash memory, and may be stored in non-contiguous blocks. 
         [0018]    During secure system boots, a main CPU may be restricted while the system&#39;s security may be assured. A security sub-system may load the boot code necessary to perform system boot in a secure manner by fetching block  0  of the NAND flash memory, which is always guaranteed to be usable, and using segments of boot code stored in block  0 , the guaranteed area, to assemble the boot code. Using the segments in the guaranteed area may enable the security sub-system to locate each of remaining segments of boot code that may be stored in other blocks of the NAND flash memory, and validate these segments separately. 
         [0019]      FIG. 1  is a block diagram illustrating an exemplary NAND flash memory, in connection with an embodiment of the invention. Referring to  FIG. 1 , there is shown a memory device  100 , a block ( 0 )  102 , a block ( 1 )  104 , and a block (n)  106 . 
         [0020]    The memory device  100  may comprise suitable logic, circuitry and/or code that may enable storage of code and data. The internal space of memory device  100  is segmented into blocks; block ( 0 ), block ( 1 ), . . . , block (n). 
         [0021]    In operation, the memory device  100  utilizes a block architecture wherein internal storage space within the memory device  100  is segmented into blocks; block ( 0 ), block ( 1 ), . . . , block (n). Only one block is always guaranteed to be usable for storing. Block ( 0 ) is a guaranteed block. Data and/or code stored in memory device  100  that may not fit in block ( 0 ) are stored in one or more other blocks. Software management of memory may be needed to track and determine where specific data and/or code may be stored (in which blocks). 
         [0022]      FIG. 2  is a block diagram illustrating an exemplary memory storage situation, in connection with an embodiment of the invention. Referring to  FIG. 2 , there is shown a memory device  202 , a block ( 0 )  204 , a block ( 1 )  206 , a block (n)  208 , a code set  210 , a code set-part ( 1 )  212 , a code set-part ( 2 )  214 , and a code set-part ( 3 )  216 . 
         [0023]    The memory device  202  may comprise suitable logic, circuitry and/or code that may enable storage of code and data. The internal space of memory device  202  may utilize block structure, and may comprise block ( 0 )  204 , block ( 1 )  206 , . . . , block (n)  208 . The code set  210  may comprise a set of code instructions and/or necessary data that may perform a task. The code set-part ( 1 )  212  comprises critical data in connection with code set  206 . The code set-part ( 1 )  212  may comprise a sub-set of code set  206 , and may also comprise additional data, which may include information that enables locating other code set parts, and may also enable validating each part of code set separately and independently. The code set-part ( 2 )  214  comprises a sub-set of code set  206 . The code set-part ( 3 )  216  comprises a sub-set of code set  206 . 
         [0024]    In operation, the memory device  202  performs as the memory device  100  described in  FIG. 1 . 
         [0025]    As demonstrated, the code set  206  may not fit completely into block ( 0 )  204 , which is the only guaranteed block in memory device  202 . The code set  206  may be partitioned onto code set-part ( 0 )  212 , code set-part ( 1 )  214 , and code set-part ( 2 )  216 . The code set-part ( 0 ) may be stored in block ( 0 )  204 , which is a guaranteed area in memory device  202 . 
         [0026]    When code set-part ( 0 )  212  is loaded from block ( 0 )  204 , the critical data may be used to locate remaining parts of the code set  206 —i.e., code set-part ( 2 )  214  and code set-part ( 3 )  216 . The critical data may also allow validating the code sub-set in code set-part ( 1 )  212 , the code set-part ( 2 )  214 , and code set-part ( 3 )  216  independently and separately. Therefore, accessing the guaranteed block, block ( 0 )  204 , would allow autonomous loading of code set  206 —i.e., without use of specific software application to account for block structure of memory device  202 . 
         [0027]      FIG. 3  is a block diagram illustrating an exemplary structuring of a security code set within a guaranteed area of a NAND flash memory, which may be utilized in accordance with an embodiment of the invention. Referring to  FIG. 3 , there is shown a NAND flash memory  300 , a block ( 0 )  302 , a fixed boot sector (part  1 )  306 , a fixed boot sector (part  2 )  308 , a fixed boot sector (part  1 ) signature  310 , a fixed boot sector (part  2 ) signature  312 , a variable boot code sector key  314 , a variable boot code sector size  316 , a variable boot code sector (pointer  1 )  320 , a variable boot code sector (pointer n)  322 , a variable boot code sector (part  1 )  324 , and a variable boot code sector (part n)  326 . 
         [0028]    NAND flash memory  300  may comprise suitable logic, circuitry and/or code that may enable storage of code and data. The internal space of the NAND flash memory  300  may utilize block structure, and may comprise block ( 0 )  302 . Block ( 0 )  302  may comprise the guaranteed block of the NAND flash memory  300 —i.e., the only block always guaranteed to be usable. 
         [0029]    The fixed boot sector (part  1 )  306 , the fixed boot sector (part  2 )  308 , the boot sector (part  1 )  324 , . . . , the variable boot code sector (part n)  326  may cumulatively comprise the boot code set, which may comprise instructions and/or necessary data that may allow booting up a system and/or device and performing necessary security operations. The fixed boot sector (part  1 ) signature  310  comprises information that may allow validating the fixed boot sector (part  1 )  306 . The fixed boot sector (part  2 ) signature  312  comprises information that may allow validating the fixed boot sector (part  2 )  308 . The variable boot code sector size  316  may comprise information that may allow determining size of variable code set sector—i.e., combined sizes of all parts of the variable boot code—i.e., the variable boot code sector (part  1 )  324 , . . . , the variable boot code sector (part  1 )  326 . The variable boot code sector (pointer  1 )  320  comprises information that may allowing locating the variable boot code sector (part  1 )  324 —i.e., a block in the NAND flash memory  300  where the variable boot code sector (part  1 )  324  is stored. The variable boot code sector (pointer n)  322  comprises information that may allowing locating the variable boot code sector (part n)  326 —i.e., a block in the NAND flash memory  300  where the variable boot code sector (part n)  326  is stored. 
         [0030]    In operation, block ( 0 )  302  may be loaded autonomously because it is the guaranteed block in the NAND flash memory  300 —i.e., block ( 0 )  302  is always usable. The fixed boot code sector (part  1 )  306  may be validated using the fixed boot code sector (part  1 ) signature  310 . The fixed boot code sector (part  2 )  308  may be validated using the fixed boot code sector (part  2 ) signature  312 . The variable boot code sector, which comprises remaining boot code sector parts stored in the NAND flash memory  300 , but not in the block ( 0 )  302 , may be assembled by using the variable boot code sector size  316 , and the variable boot code sector (pointer  1 )  320 , . . . , the variable boot code sector (pointer n)  322 , to locate the variable boot code sector (part  1 )  324 , . . . , the variable boot code sector (part n)  326 . The variable boot code sector may be validated by using the variable boot code sector key  314 . Once the variable boot code sector and the fixed boot code sector are validated, they may be combined to obtain the boot code set. 
         [0031]      FIG. 4  is a block diagram illustrating an exemplary system with a NAND flash memory, which may be utilized in accordance with an embodiment of the invention. Referring to  FIG. 4 , there is shown a NAND flash memory  402 , a processor system  404 , a main-CPU  406 , and a security sub-system  408 . 
         [0032]    The NAND flash memory  402  may comprise suitable logic, circuitry and/or code that may enable storage of code and data used by the processor system  404 . The processing system  404  may comprise a main-CPU  406 , a security sub-system  408 , and suitable logic, circuitry and/or code that may enable processing operations. The invention may not be limited to a specific processor, but may comprise for example, a general purpose processor, a specialized processor or any combination of suitable hardware, firmware, software and/or code, which may be enabled to provide NAND flash support for secure and autonomous boot code loading in accordance with the various embodiments of the invention. 
         [0033]    The main-CPU  406  may comprise suitable logic, circuitry and/or code that may enable said processing operations. The security sub-system  408  may comprise suitable hardware, firmware, software and/or code, which may be enabled to provide security operations. 
         [0034]    In operations, the NAND flash memory  402  operates similar to NAND flash memory  300  described in  FIG. 3 . The processor system  404  may perform various processing operations, which may include, but is not limited to, memory operations. 
         [0035]    The security sub-system  408  may perform security operations that restrict and control the processor system  404  in certain security situation, including, but not limited to, secure and autonomous boot code loading. 
         [0036]    The security sub-system  408  may load code and/or data from the guaranteed block in the NAND flash memory. The security sub-system  408  may load a boot code from the NAND flash memory. The security sub-system  408  may assemble the boot code by loading the boot code sectors either directly from the guaranteed block of the NAND flash memory, or by using the pointers stored in the guaranteed block to locate the parts stored in non-guaranteed blocks. The security sub-system  408  may use the signatures stored in the guaranteed block to validate the code set sectors separately. The security sub-system may execute the boot code to assure system security and integrity. 
         [0037]    Various embodiments of the invention may comprise a method and system for ensuring secure system boot, and may comprise segmenting a boot code into various segments that may be stored and validated separately. The segmented boot code may be stored in a memory, such as a NAND flash memory  402 . Because NAND flash memory devices incorporate block structure, with only the first block guaranteed to be usable, only some of the segments of the boot code may be stored in the guaranteed area of the NAND flash memory  402 . The segments stored in the guaranteed area of the NAND flash memory  402  comprise information that enable locating and validating remaining segments separately. These remaining segments may not be stored in guaranteed areas of the NAND flash memory  402 , and may be stored in non-contiguous blocks. During secure system boots, the main CPU  406  may be restricted while the system&#39;s security may be assured. A security sub-system  408  may load the boot code necessary to perform system boot in secure manner by fetching block  0  of the NAND flash memory  402 , which is always guaranteed to be usable, and using segments of boot code stored in block  0 , the guaranteed area, to assemble the boot code. Using the segments in the guaranteed area may enable the security sub-system  408  to locate each of remaining segments of boot code that may be stored in other blocks of the NAND flash memory, and validate these segments separately. 
         [0038]    Accordingly, the present invention may be realized in hardware, software, or a combination of hardware and software. The present invention may be realized in a centralized fashion in at least one computer system, or in a distributed fashion where different elements are spread across several interconnected computer systems. Any kind of computer system or other apparatus adapted for carrying out the methods described herein is suited. A typical combination of hardware and software may be a general-purpose computer system with a computer program that, when being loaded and executed, controls the computer system such that it carries out the methods described herein. 
         [0039]    The present invention may also be embedded in a computer program product, which comprises all the features enabling the implementation of the methods described herein, and which when loaded in a computer system is able to carry out these methods. Computer program in the present context means any expression, in any language, code or notation, of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or after either or both of the following: a) conversion to another language, code or notation; b) reproduction in a different material form. 
         [0040]    While the present invention has been described with reference to certain embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted without departing from the scope of the present invention. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the present invention without departing from its scope. Therefore, it is intended that the present invention not be limited to the particular embodiment disclosed, but that the present invention will include all embodiments falling within the scope of the appended claims.