Classifications

• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F8/00—Arrangements for software engineering
  • G06F8/40—Transformation of program code
  • G06F8/54—Link editing before load time
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F9/00—Arrangements for program control, e.g. control units
  • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
  • G06F9/44—Arrangements for executing specific programs
  • G06F9/4401—Bootstrapping
  • G06F9/4403—Processor initialisation
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F9/00—Arrangements for program control, e.g. control units

Definitions

• the present invention relates to the booting of microprocessor controlled devices.
• Non volatile flash memory in particular, is now widely used due to its ability to retain information without power and to be rapidly erased and reprogrammed.
• flash memory is a portion of firmware code stored on the device. Usage of flash memory to store bootcode is advantageous because the firmware, including the bootcode can easily be modified and updated.
• a microprocessor Upon booting or startup, a microprocessor reads the code in a specified location of a storage device.
• Typical microprocessors are generally configured to access and execute code in linear storage devices.
• the data in linear storage devices is accessed by reading a location specified by, speaking in general terms, a linear address consisting of the row and column of the data.
• Each memory cell, byte, or bit of data is accessed by specifying its is row and column.
• the processor will sequentially specify linear addresses from which to read.
• the protocol to transfer data from the memory to the host is as follows: 1) select the memory device by asserting the chip select line; 2) select the address from which to read by asserting the address of the address bus; 3) assert the read signal. The memory device will respond with the data asserted on the data bus.
• a typical program contains instruction data that are stored in various different areas of the memory that are not contiguous or adjacent.
• the processor may first execute an instruction from an address in one area and then execute an address from a second (and third etc%) distant or non adjacent area.
• the processor may first execute an instruction from an address in one area and then execute an address from a second (and third etc%) distant or non adjacent area.
• Each program may execute from different areas according to its own particular routines.
• NAND and AND type flash memory are not linearly addressable. This means that the processor cannot read or execute code from them upon bootup.
• the storage space in NAND memory is broken up into discrete groups of data referred to as pages. In order to retrieve the data, the page must first be specified, then the location of the data on the page, specified as an offset from the beginning of the page, must also be specified.
• byte number 255 cannot be read without first reading the preceding 254 bytes.
• reading just one byte is a relatively more complicated procedure that does not follow the typical timing requirements of linear memory. This has, until now, made booting from non linear memory an impossible task.
• the system and method of booting from a non linear storage device has many applications in the startup of electronic devices that employ non linear storage devices. It can be used to boot up any microprocessor controlled device, such as but not limited to cellular phones, portable organizers, computers, global positioning systems, and smart appliances. Waiting for a device to boot-up is extremely f ustrating, whether it be a cellular phone, a computer, portable organizer, or any other smart device.
• the time required for the boot code to start executing with the present invention is significantly faster than in prior devices that relied on shadowing of the boot code before execution.
• the cost of devices made in accordance with the present invention is also reduced compared to devices using a dedicated code storage device to store the boot code.
• a first aspect of the invention is a method for booting a microprocessor controlled device including a non linear storage device.
• the method comprises receiving a system reset signal and initializing the non linear storage device such that the non linear storage device points to system boot code within the non linear storage device. It further comprises executing a first portion of the system boot code from the non linear storage device with the microprocessor.
• a second aspect of the invention is a microprocessor controlled device comprising a microprocessor, volatile RAM, a non linear memory, and a linear memory emulator operable to translate code in the non linear memory into a linear format for execution by the microprocessor.
• Another aspect of the invention is a microprocessor based system comprising a microprocessor operable to read linear storage devices, a non linear storage device, and means for executing code on the non linear storage device with the microprocessor operable to read linear storage devices.
• FIG. 1A is a schematic diagram of system 100.
• FIG. IB is a conceptual illustration of the operation of system 100.
• FIG. 2 is an illustration of the storage space of non linear storage device 140 of system 100.
• FIG. 3 is a table of signals utilized in system 100 and referred to in the description.
• FIG. 4 is a flow chart of the general boot up sequence.
• the system and method of booting from a non linear storage device has many applications in the startup of electronic devices that employ non linear storage devices. While the system and method of the present invention encompasses startup of any device incorporating any type of non linear storage device, for purposes of illustrating the invention, NAND flash memory will be described.
• the time required for the boot code to start executing with the present invention is approximately the access time of the non linear storage device. In the NAND example, this is approximately 15 microseconds, whereas shadowing takes several hundred milliseconds before execution may even begin in past systems.
• FIG. 1A illustrates system 100.
• Processor 130 is connected via system bus 115 to a number of other devices.
• System bus 115 is connected to non linear storage device (NLSD) 140, non linear storage device interface (NLI) 120, processor 130, volatile random access memory (RAM) 150, peripherals 160, and human interface devices 170.
• Control lines 142 connect NLSD 140 and NLI 120.
• NLI 120 comprises a programmable logic device or application specific integrated circuit or logic gates incorporated into a chip sometimes described as a system in a chip. It also comprises the logic implemented in the aforementioned devices.
• 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. As the present invention will be especially advantageous with portable devices such as cellular telephones, the peripherals and human interface devices may all be integrated in one package, however they may also be traditional individual components.
• NLSD 140 comprises NAND type flash memory.
• boot code 146 Stored within NLSD 140 is boot code 146.
• Boot loader 144 may be considered part of boot code 146, or alternatively may be considered as separate.
• Each of the connections with system bus 115 are capable of two way communication and may comprise several lines although simply illustrated as a single line for clarity. Although the transfer of data to and from NLSD 140 occurs over system bus 115, a conceptual illustration of the data flow is provided in FIG. IB in order to emphasize that boot loader 144 is executed directly from NLSD 140 through interface 120.
• NLSD 140 is a multipurpose storage device used to store all sorts of user files as well as the boot code used to start system 100 upon bootup.
• File storage portion 210 may have a capacity from a few kilobytes to many gigabytes.
• User files such as digital images, songs, programs, and other data files, may be stored in file storage portion 210.
• Boot code 146 and boot loader 144 are stored in dedicated areas of NLSD 140 such that they cannot inadvertently be overwritten. For more information on this, please refer to co-pending U.S. Patent Application No. 09/923874 filed on August 6, 2001, which is hereby incorporated in its entirety by this reference.
• boot code 146 and boot loader 144 may easily be updated from time to time if desired.
• Boot loader 144 preferably comprises one page of data in the NAND memory. Page length often varies slightly in different memory structures. In this example it is 512 bytes.
• the flash memory may be packaged in any form, such as but not limited to a prom, integrated on chip memory, Compact Flash cards, and serial non linear flash such in MutliMedia Cards (MMC) and Secure Digital (SD) cards.
• MMC MutliMedia Cards
• SD Secure Digital
• NAND flash memory has many advantages which has led to its widespread usage, the non linear nature of the data stored in the memory has heretofore prevented execution of the data directly by microprocessors, which are designed to execute data that is linearly addressable. Previously, the data had to first be copied to RAM before it could be executed by the microprocessor. With the present invention, boot loader 144 is directly executed by the processor, i.e. it is not shadowed into RAM before execution. Reading directly from the NAND memory is quite fast, on the order of 15 microseconds. This direct execution saves precious time during the startup of system lOO.This is done with non linear interface 120, which will further be described below with reference to the flow chart of FIG. 4.
• FIG. 3 is a table of signals or commands utilized by interface 120 that will be referred to in the description of the flow chart of FIG. 4.
• FIG. 4 is a flowchart of the overall startup sequence of a device such as that exemplified as system 100 seen in FIG. 1.
• the microprocessor is initialized in step 202 after a system reset signal is received by either processor 130 or interface 120. This type of triggering reset can be either a hard or a soft reset.
• step 202 the microprocessor executes boot loader 144 seen in FIGS. 1 and 2 directly from NLSD 140, through interface 120.
• boot loader 100 comprises instructions within the first page of the NAND memory.
• the instructions follow each other in a sequential manner. That is to say, that the first instruction to be executed has an address in the fist area to be read and the second instruction to be executed has an address in the second area, contiguous to the first area, and so on. This is important because in NAND flash memory, and in other non linear memory, one area, byte 255 for example, cannot be read without first reading all the other area before it (the first 254 bytes).
• the critical registers of the microprocessor 130 are set up in step 210A. This comprises disabling the interrupts of the microprocessor, defining the location of the destination memory, and initializing the destination memory.
• the destination in the example of system 100 is RAM 150.
• the destination memory may be may be one or more individual RAM chips, may be within processor 130, or may be any type of memory located elsewhere within the smart device that is being booted.
• the registers of the microprocessor are set as follows for an 8 bit system incorporating NAND flash memory as the non linear storage device.
• Reading from NLSD 140 comprises monitoring the microprocessor address lines with NLI 120 for an address change, and then pulsing a read line to NLSD 140 when NLI 120 detects an address change. The data is then put out on data bus 115 and goes to NLI 120 where it is intern transferred again over data bus 115 to microprocessor 130. More specifically, as an example, in non-hnear memory with 528 bytes/page, transfer of a specific byte generally follows the four main steps below.
• Interface 120 calculates the location (address) of the byte within the page. This address is divided into a minimum of three bytes. For a 512Mbit device, four bytes must be read.
• Interface 120 selects from one of three commands (First 256, Second 256, or spare area).
• Interface 120 writes the command in step 2 to the NLSD 140 as follows:
• Interface 120 then sends the address as follows:
• m Asserts NLSD 140 write enable (WE) line for the minimum specified time (typically 50ns or more);
• n De-asserts NLSD 140 WE
• NLSD 140 will assert that it is busy with a delay of up to 200ns, and that each time NLSD 140 issues a CE signal, the CE signal must remain asserted while NLSD 140 is busy.
• Microprocessor 120 can only read data, in a sequential manner, from NLSD 140 when NLSD 140 is ready.
• boot loader 144 within the instructions of boot loader 144 are instructions that once read and executed will copy the remainder of boot code 146 into RAM 150. When these instructions are read and executed by the microprocessor directly from NLSD 140, they will then copy the boot code 146 to RAM 150 in step 210B. In step 214, the microprocessor executes the copied portion of boot code 146
• the interface 120 can use a very low cost programmable logic device, ASIC, or may be incorporated into the processor in a system on chip design.
• ASIC programmable logic device
• the system was designed to have the maximum possible access speed, therefore minimizing the startup time of any device incorporating the system or method of the present invention. It provides a simple register based access model to make the system easy to use and incorporate by programmers. It also supports different system configurations and platforms. For example, 8 , 16, 32 or other bit systems can be supported.

Landscapes

• Engineering & Computer Science (AREA)
• Software Systems (AREA)
• Theoretical Computer Science (AREA)
• General Engineering & Computer Science (AREA)
• Physics & Mathematics (AREA)
• General Physics & Mathematics (AREA)
• Computer Security & Cryptography (AREA)
• Stored Programmes (AREA)
• Read Only Memory (AREA)
• Debugging And Monitoring (AREA)

Priority Applications (4)

Applications Claiming Priority (2)

Publications (2)

Family

ID=32042021

Family Applications (1)

Country Status (7)

Cited By (5)

Families Citing this family (28)

Family Cites Families (31)

• 2002
  • 2002-10-02 US US10/263,576 patent/US7082525B2/en not_active Expired - Lifetime
• 2003
  • 2003-09-30 EP EP03799369A patent/EP1546875A2/en not_active Ceased
  • 2003-09-30 WO PCT/US2003/031010 patent/WO2004031942A2/en not_active Ceased
  • 2003-09-30 AU AU2003277165A patent/AU2003277165A1/en not_active Abandoned
  • 2003-09-30 KR KR1020057005808A patent/KR100974561B1/ko not_active Expired - Fee Related
  • 2003-09-30 JP JP2004541974A patent/JP2006502482A/ja active Pending
  • 2003-09-30 CN CN038246791A patent/CN1698032B/zh not_active Expired - Lifetime
• 2006
  • 2006-05-24 US US11/420,202 patent/US7310726B2/en not_active Expired - Lifetime

Also Published As

Similar Documents

Legal Events