Abstract:
A system for booting a microprocessor controlled system wherein a basic interface between the processor and peripheral devices is copied from an application and file storage device into random access memory without usage of the microprocessor or need for a non-volatile code storage device.

Description:
FIELD OF THE INVENTION  
         [0001]    The field of the invention is microprocessor controlled devices, specifically the initialization or booting process of the devices.  
         BACKGROUND OF THE INVENTION  
         [0002]    A generic computing platform consists of various hardware and software components. A main processor which contains a central processing unit (CPU), e.g., a microprocessor, is connected to a non-volatile code storage device (CSD), non-volatile application and file storage device (AFSD), random access memory (RAM) and other peripheral devices. The hardware dependent software that is required to initialize various hardware components is stored in the code storage device. In personal computer (PC) architecture this software is known as the BIOS (Basic Input Output System). The BIOS provides an interface between the operating system and the hardware. The process of execution of initialization software by the CPU is known as the “boot” process. A CPU can boot directly from a CSD, or in order to achieve higher performance can boot from a copy of the content of the CSD in RAM.  
           [0003]    The background of the invention describes operation of a PC for illustrative purposes, but the invention relates more generally to starting operation of any intelligent device, and is not limited to PC architecture.  
           [0004]    Referring to FIG. 1, in a generic computing environment, two types of non-volatile storage devices are used. These non-volatile storage devices are used for code storage and for application and file storage. Typically a code storage device (CSD)  45  has a much smaller capacity than an application and file storage device (AFSD)  40 . In addition, a CSD is usually accessed after system power up or after system reset and its content is very infrequently updated by the computer system in comparison to an AFSD that is updated frequently by the applications or users of the operating system.  
           [0005]    Traditionally the CSD  45  is hardwired to the system bus and is mapped into a specific memory location. After the completion of system power up reset or system reset, the CPU  30  will look for its initialization code in this specific location of CSD  45 . This initialization code is dependent on system architecture or hardware, and in PC architecture is known as the BIOS. In other architectures this initialization code is referred to as initialization firmware, boot firmware etc . . . Examples of CSDs are EPROM, Flash ROM, and OTP PROM. An AFSD is used in order to store an operating system, application programs or general file and user data. An AFSD is a non volatile storage device such as solid state memory or a magnetic or optical drive  
           [0006]    The BIOS or booting firmware is normally stored in the CSD  45  in order for the CPU to execute its instructions. Traditionally if boot code is stored in the AFSD  40 , a small set of instructions, constituting the basic BIOS must be stored in the CSD  45  in order to copy the BIOS or booting firmware into system RAM  50 . In this invention, the requirement of the CSD for storing and executing these initialization instructions is eliminated.  
         SUMMARY OF THE INVENTION  
         [0007]    In the system of the present invention, without at using the microprocessor to execute a set of instructions or changing system architecture, a smart logical interface circuit controls the computer system in order for an Application and File Storage Device (AFSD) to substitute for the functionality of the Code Storage Device (CSD). The circuitry loads the BIOS from the AFSD into Random Access Memory (RAM). An AFSD is a non-volatile memory storage device such as a solid state memory or a magnetic or optical drive. Upon its completion, the microprocessor then takes over the control and completes the system initialization process. Therefore there will not be any need for a CSD to store the BIOS. This initial loading logic circuitry (LLC) controls the initial loading of boot code. The LLC copies at least a sufficient amount of programming instructions from an AFSD into RAM to then allow a microprocessor to read the instructions, interface with the hardware, and take over operation of the system. These instructions are known as the BIOS in the specific embodiment of the PC used to illustrate the operation of the present invention, however in other platforms it may be referred to as firmware. The subset of the BIOS copied by the LLC is referred to as the “BIOS loader”. However, the LLC has a much wider range of application than in PC architecture and the PC and its associated terms are only used for illustrative purposes. The LLC has applications in computing platforms ranging from small handheld devices such as digital cameras, personal audio players, personal digital assistants and sophisticated embedded systems such as telecommunication and networking equipment.  
           [0008]    When the device power is turned on or the user presses a reset button, the microprocessor of the system executes the BIOS or firmware starting at a designated location in the system memory. If the microprocessor receives a HOLD or HALT it releases control of the ADDRESS, DATA, and other control lines. In this invention, the HOLD is either generated immediately after or simultaneously with the RESET. After the microprocessor is put on hold, the LLC selects one of the multiple BIOS storage locations that is preset and stored in registers of the LLC. The BIOS storage location is defined by the LLC, and can easily be relocated for various processors that may require different BIOS storage locations. In addition, multiple BIOSs can be stored in the AFSD and accessed by the LLC, thus the user can select a different BIOS for a different purpose and the system can be configured differently upon startup for different purposes. Once the AFSD is enabled, the BIOS loader is copied from the AFSD into RAM. Thereafter, the LLC releases the HOLD/RESET of the microprocessor and the microprocessor can execute the BIOS loader from RAM. In addition, after completion of the booting process, the Loading Logic Circuitry activates its write protect circuitry for protecting the BIOS or boot code portion of the AFSD. This will protect the BIOS or boot code portion from accidental overwriting or erasing. This protection can be overridden only by an authorized user.  
           [0009]    Thus, a dedicated ROM chip can be eliminated from the system because the microprocessor need not access the BIOS instructions that are normally saved therein.  
           [0010]    The above process assumes there is a HOLD or HALT type of signal to the microprocessor and the microprocessor will make the ADDRESS, DATA and control lines tri-stated. If the required signals cannot be tri-stated or there is no HOLD or HALT function to the microprocessor, tri-state buffers may be used to isolate the system bus used by the microprocessor from the buses used for the copying process. 
       
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0011]    [0011]FIG. 1 is a prior art PC system using the conventional code storage device BIOS storage.  
         [0012]    [0012]FIG. 2 is a block diagram of the components of the system.  
         [0013]    [0013]FIG. 3 is a diagram of the Application and file storage device of FIG. 2.  
         [0014]    [0014]FIG. 4 is a flow chart of the operation of the system.  
         [0015]    [0015]FIG. 5 is a Detailed block diagram of loading logic circuitry  120  of FIG. 2.  
         [0016]    [0016]FIG. 6 is a Detailed block diagram of the write protect generator  128  of FIG. 5. 
     
    
     DESCRIPTION OF EXEMPLARY EMBODIMENTS  
       [0017]    Referring to FIGS.  2 - 6 , the operation of the system of the present invention will be shown. Operation of the system is illustrated by using an example of NAND flash memory for the non-volatile application and file storage device (AFSD)  140  of FIG. 2 for descriptive purposes, however, the invention encompasses any type of non-volatile memory. This exemplary embodiment illustrates the system implemented with PC architecture, however the system of the present invention encompasses the startup of any intelligent device. The system has applications in many types of personal electronic devices such as music players/recorders, digital cameras, digital organizers, cellular phones, and a variety of other sophisticated embedded systems such as Telecommunication and Networking equipment.  
         [0018]    In FIG. 2 the components of the system are illustrated. Loading Logic Circuitry (LLC)  120  is connected to reset button  105  and system power on reset circuit  110  by signal line  122 . LLC  120  has an internal counter  125 . System bus  115  is connected to LLC  120 , CPU  130 , AFSD  140 , volatile random access memory (RAM)  150 , peripherals  160 , and human interface devices  170 . Peripherals  160  can be printers or other output devices as well as additional drives and any other peripherals that are well known in the art. Human interface devices are things such as a keyboard, monitor, mouse, microphone or speakers and are likewise well known in the art. Control signal lines  132  connect LLC  120  with CPU  130 , and control signal lines  142  connect LLC  120  with AFSD  140 . In this illustrative example control signal lines  142  are connected to the control inputs of the NAND flash memory. Additional control signal lines  152  connect LLC  120  and RAM  150 . RAM  150  has a portion of memory allocated for storage of the BIOS  200  and the BIOS loader  200   a , a portion of the BIOS. The BIOS and the BIOS loader in RAM  150  is a copy of the BIOS and the BIOS loader in AFSD  140 .  
         [0019]    [0019]FIG. 3 shows AFSD  140  in more detail. AFSD  140  is used to store user files, such as documents, pictures or drawings, and music files as well as executable system files. This application and file storage device is also utilized to store BIOS  200  and the BIOS loader  200   a  of BIOS  200 . The remainder of AFSD  140  comprises file storage portion  210 . BIOS  200  only utilizes a relatively small proportion of AFSD  140  which has a capacity large enough to store a large number of files. For example AFSD  140  could have a capacity anywhere from 4 megabytes to several gigabytes.  
         [0020]    [0020]FIG. 4 shows the operation of the system components illustrated in FIG. 2. A system reset is triggered by either reset button  105  or by introducing or interrupting system power that triggers the system power on reset circuitry  110  in step  310 . Either pressing the reset button or turning on the power will trigger Loading Logic Circuitry (LLC)  120 . LLC  120  can also be triggered by other routines to reset the device. LLC 120  comprises a finite state machine that controls the operation of the basic initialization process through logic circuitry either on board level components, or on application specific integrated circuitry (ASIC) such as a field programmable gate array (FPGA) or programmable logic device (PLD). Control of the basic initialization operation is not through a microprocessor such as a CPU.  
         [0021]    After LLC  120  receives the system reset signal, it commences the RESET/HOLD process and suspends the operation of CPU  130  through control signal lines  132  in step  320 . After the operation of CPU  130  has been suspended, LLC  120  records the location of BIOS  200  in AFSD  140  in step  325 . LLC  120  then initiates and readies the AFSD  140  through control lines  142  for sending data over system bus  115  in step  330 . LLC  120  also readies the RAM  150  to receive data through control lines  152  in step  330 . Counter  125  is initialized to its preset initial value in step  330 .  
         [0022]    Next, LLC  120  copies the BIOS loader  200   a  from AFSD  140  over the system bus  115  into volatile RAM  150  in step  340 . Counter  125  is incremented after each copy of data from AFSD  140  to RAM  150  in step  340 . The BIOS loader  200   a  is an amount of the BIOS  200  sufficient to allow the CPU to start the boot operation. Thus, it must be sufficient to allow communications with and control over AFSD  140  and RAM  150 . This can range anywhere from less than one page to ten pages and is preferably only one page, or 512 bytes of BIOS  200 , when dealing with PC architecture. However, this amount could be on the order of tens of kilobytes in embedded systems. When BIOS loader  200   a  is more than 512 bytes error correction code can be used, whereas when BIOS loader  200   a  consists of one page (or less), error correction code is unnecessary because the integrity of the first page is generally assured because of pre-selection of the memory areas during manufacturing and testing. In applications where the integrity of a larger memory segment is assured a larger size of data can be copied without error correction. Furthermore, error correction code can be directly integrated and thus the integrity can be determined during the copying process, allowing even greater amounts of error free data to be copied. AFSD  140  can be any type of non-volatile, storage device such as a solid state memory, magnetic disk, optical disk, or tape drives.  
         [0023]    In the preferred embodiment, AFSD  140  is NAND flash memory (NFM) and a brief discussion of the controls signals of NFM follows. NFM has an 8-bit data bus and 7 control signals, i.e., CLE (Command Latch Enable), ALE (Address Latch Enable), CE (Chip Enable), WE (Write Enable), RE (Read Enable), RB (Ready_Busy), and WP (Write Protect). The DATA bus is connected to the system bus  115  and the control signals are transmitted via control lines  142 .  
         [0024]    To access the NFM, the CE signal has to be in active state before any other signal can become active. A COMMAND is then written into the NFM followed by an ADDRESS, if the ADDRESS is required. The COMMAND code and the ADDRESS are presented through the data bus, illustrated as a part of the system bus  115 . The RB (Ready_Busy) signal will indicate a busy state after writing of some commands or address. Subsequent operations are performed after RB indicates the ready state.  
         [0025]    The content of the data bus contains a command if the CLE is active and the ALE is inactive. The content in the data bus contains data if the CLE and the ALE are in an inactive state. The content of the data bus is an address if the CLE is inactive and the ALE is active. Writing of an address requires multiple cycles of the WE signal depending on the size of the NFM. Content in the data bus is stored into NFM on the trailing edge of the WE signal.  
         [0026]    To read data from the NFM, CLE and ALE are set to an inactive state before RE is set to an active state. When RE is active, the content from the NFM is presented to the data bus.  
         [0027]    As shown in FIG. 3, AFSD  140  is used not only to store BIOS  200 , but also to store various user files in file storage portion  210 . Copying of the data is achieved by sending a read enable (RE) signal to AFSD  140  and a write (WR) signal to RAM  150  over control signal lines  142  and  152  respectively. At the same time, an address counter  125  within LLC  120  is enabled. The address counter starts to count from a preset value and continues to increment with each clock. The clock signal has a low portion and a high portion. The low portion is used for the RE signal of AFSD  140  to enable data transfer to the system bus  115  from AFSD  140 , and at the same time is used for the WR signal of RAM  150 . During low to high transition of the clock (rising edge of the clock) the data on the system bus  115  is copied into RAM  150  and the address counter is incremented. This copying of the data continues until the address counter reaches 01FFh which corresponds to the 512 bytes of BIOS loader in this example. After the BIOS loader has been copied AFSD  140  and RAM  150  are disabled by setting the CE signal of AFSD  140  and the CS signal of RAM  150  to an inactive state.  
         [0028]    Upon the completion of copying of the BIOS loader into RAM  150 , LLC  120  releases hold of the CPU in step  350 . Thus all of the aforementioned activities were performed without involvement of the CPU.  
         [0029]    With the CPU now active again, it is important that BIOS  200  cannot be overwritten by the CPU. In step  355  LLC 120  enables a write protect generator to assure this cannot happen as will be described later with reference to FIG. 5.  
         [0030]    Finally, with the BIOS loader once stored in AFSD  140  now located in RAM  150 , in step  360  the CPU executes the BIOS loader and can now copy the remaining portion of BIOS  200  into RAM  150 .  
         [0031]    [0031]FIG. 5 is a detailed block diagram of loading logic circuitry (LLC)  120  of FIG. 2. LLC  120  comprises reset circuit (RC)  121 , AFSD code address selector (ACAS)  122   a , RAM load address selector (RLAS)  122   b , address register (AR)  123  for BIOS  200  storage blocks, sequencer  124  including AFSD &amp; RAM control circuit  124   a  and RAM address counter  124   b,  and write protect generator (WPG)  128  for the BIOS boot blocks in AFSD  140 .  
         [0032]    Reset Circuit  121  receives a reset signal over control line  122  from reset button  105  or system power on reset circuit  110  as shown in FIG. 2. After receiving a reset signal over control line  122 , reset circuit  121  generates and sends a signal or signals over control lines  132  depending on the type of microprocessor used. RC  121  sends signal(s) that will make the microprocessor  130  tri-state its data bus, address bus and some necessary control signals. After RC  121  releases the signal, the CPU  130  will start execution at a designated address. If a microprocessor  130  has no ability to tri-state its bus then tri-state buffers may be used in order to suspend operation of CPU  130  while LLC  120  controls the initialization sequencing.  
         [0033]    The BIOS stored in AFSD  140  can be located in one of multiple selectable locations using ACAS register  122   a . The selected storage location of the BIOS is latched into AR  123  during a reset generated by RC  121 . This latched value  123 lv is used by the sequencer  124  for the starting address of BIOS loader  200   a  and by WIPG  128  for the block value where the BIOS is located. The location of the BIOS in RAM is also hardware selectable through RAM load address selector (RLAS)  122   b.    
         [0034]    Sequencer  124  is the sequential state machine that is initiated to start copying the BIOS loader  200   a  from AFSD  140  into RAM  150  starting at address  123 lv specified by AR  123 . This sequencer  124  includes AFSD &amp; RAM control  124   a  and the RAM address counter  124   b.  The output of the RAM address counter  124   b  is used as the address to RAM  150  during the loading process. The output of the RAM address counter  124   b  is tri-stated at the completion of the load process. At the end of the copying, CPU  130  is released via signal lines  132 .  
         [0035]    [0035]FIG. 6 is a detailed block diagram of the write protect generator  128  of FIG. 5. WPG  128  comprises a command/control decoder  420 , page address register  430 , command code register  440 , write strobe generator  450 , and comparator logic  470  including boot code block address comparator  472  and command code comparator  474 .  
         [0036]    WPG  128  protects the data in the boot code blocks, i.e. where the BIOS  200  is located in AFSD  140  so that any file or application is not written in the blocks where BIOS  200  is located, as seen in FIG. 3. If an attempt is made to write or to erase the boot code blocks of the AFSD, this generator will disable the strobe of the write enable to AFSD  140 ; it invalidates the operation and the write or erase operation is not performed.  
         [0037]    Command/Control Decoder (CCD)  420  is a circuit that generates all necessary control signals to AFSD  140  over system bus  115 . CCD  420  receives control signals from CPU  130  over the system bus  115 , decodes the signals from the CPU, and sends the decoded signals over the control lines  142  to AFSD  140 .  
         [0038]    Page address register  430  maintains the address information for AFSD  140 . When CPU  130  of FIG. 1 sends a designated address to AFSD  140 , it is latched into this page address register  430 . When CPU  130  sends a command to the AFSD  140 , it is latched into the command code register  440 .  
         [0039]    Write strobe generator  450  controls the writing of the memory cells of AFSD  140 . When CPU  130  writes to AFSD  140 , whether the write is a command, an address or data, two write signals “WR_ 1 ” and “WR_ 2 ” are generated with one CPU write operation. WR_ 1  is generated first, then WR_ 2  is generated shortly after. WR_ 1  will latch the address and command code into the page register and command code register respectively for boot code block comparison. WR_ 2  is used as the WRITE ENABLE signal to AFSD  140 .  
         [0040]    Boot code block address comparator  472  compares the page address register  430  and the boot code block address  123 lv. If the result is identical, the command code comparator  474  is enabled.  
         [0041]    Command Code Comparator  474  checks the content of the command code register with the command “PROGRAM”, “ERASE” or other commands which will modify the content of AFSD  140 . If the content of the command code register is a “PROGRAM” or “ERASE” WR_ 2  will be disabled, and thus the program or erase operation will be prevented. Therefore, the BIOS  200  in AFSD  140  is protected from any modification.  
         [0042]    This system is advantageous in many ways over prior designs. The BIOS is stored on a storage device that is used for application or file storage, and more importantly, a portion of the BIOS is copied from an AFSD into RAM without using a microprocessor executing commands located on a special purpose ROM. Thus, a dedicated chip such as the ROM, commonly used to store the BIOS in PCs, can be eliminated resulting in a substantial cost saving, smaller board size, and simplified interface structures. Additionally, the BIOS can be more easily altered when it is stored in an AFSD.  
         [0043]    While an illustrative example of the invention has been shown and described, it will be apparent that other modifications, alterations and variations may be made by and will occur to those skilled in the art to which this invention pertains.  
         [0044]    It is therefore contemplated that the present invention is not limited to the embodiments shown and described and that any such modifications and other embodiments as incorporate those features which constitute the essential features of the invention are considered equivalents and within the true spirit and scope of the present invention.