Source: http://www.google.co.uk/patents/US9575768
Timestamp: 2017-09-22 17:15:16
Document Index: 284141531

Matched Legal Cases: ['Application No. 200980136849', 'Application No. 2011', 'Application No. 200980153758', 'Application No. 2011', 'Application No. 200980136849', 'Application No. 200980136849', 'Application No. 200980136849', 'Application No. 200980153758', 'Application No. 200980153758', 'Application No. 201280033662', 'Application No. 09803951', 'Application No. 09803951', 'Application No. 2011', 'Application No. 2011', 'Application No. 2011', 'Application No. 2011', 'Application No. 2011', 'Application No. 2011', 'Application No. 10', 'art 11', 'Application No. 09803951', 'art 11']

Patent US9575768 - Loading boot code from multiple memories - Google Patents
The present disclosure describes apparatuses and techniques for loading boot code from multiple memories. In some aspects a transfer operation transferring a portion of boot code from a memory of a first type is initiated prior to completion of another transfer operation transferring another portion...http://www.google.co.uk/patents/US9575768?utm_source=gb-gplus-sharePatent US9575768 - Loading boot code from multiple memories
Publication number US9575768 B1
Application number US 14/147,087
Priority date 8 Jan 2013
Publication number 14147087, 147087, US 9575768 B1, US 9575768B1, US-B1-9575768, US9575768 B1, US9575768B1
Inventors Myungque Kim
Patent Citations (253), Non-Patent Citations (117), Referenced by (1), Classifications (3), Legal Events (1)
US 9575768 B1
The present disclosure describes apparatuses and techniques for loading boot code from multiple memories. In some aspects a transfer operation transferring a portion of boot code from a memory of a first type is initiated prior to completion of another transfer operation transferring another portion of the boot code from another memory of the first type. This can be effective to enable concurrent transfers of boot code from multiple memories of the first type into a memory of a second type for execution. By so doing, a speed at which boot code is transferred into the memory of the second type is increased, which may result in decreased device boot times.
initiating, via a direct memory access (DMA) controller, a first transfer operation transferring a first portion of boot code from a first non-volatile memory of a device into a volatile memory of the device, the first portion of boot code including a first signature that indicates a presence of the first portion of boot code in the first non-volatile memory;
initiating, via the DMA controller and prior to completion of the first transfer operation, a second transfer operation that concurrently transfers a second portion of the boot code from a second non-volatile memory of the device into the volatile memory of the device, the second portion of boot code including a second signature that indicates a presence of the second portion of boot code in the second non-volatile memory; and
causing, after completion of at least the first transfer operation of the first portion of boot code, a processor of the device to execute of the first and second portions of the boot code from the volatile memory of the device effective to initiate boot operations of the device.
2. The method of claim 1, wherein initiating the first and second transfer operations comprises configuring the DMA controller to transfer the first portion of the boot code from the first non-volatile memory and transfer the second portion of the boot code from the second non-volatile memory, respectively.
3. The method of claim 1 further comprising selecting, from two or more non-volatile memories, the first and second non-volatile memories from which to transfer the boot code into the volatile memory.
4. The method of claim 3, wherein selecting the first and second non-volatile memories from the two or more non-volatile memories comprises determining, based on the first and second signatures, that the first and second non-volatile memories include the first and second portions of boot code.
5. The method of claim 1, wherein a data-transfer speed of the first transfer operation is different from a data-transfer speed of the second transfer operation.
6. The method of claim 1, wherein the first portion of boot code and the second portion of boot code are respective portions of a composite boot image that, responsive to execution, implements the boot operations of the device.
7. The method of claim 1, wherein the first non-volatile memory or the second non-volatile memory comprises one of a serial peripheral interface (SPI) Flash memory, electronically-erasable programmable read-only memory (EEPROM), NAND Flash, embedded Flash, or embedded multimedia card (eMMC) device.
8. One or more hardware-based computer-readable memory devices storing processor-executable instructions that, responsive to execution by a processor of a device, implement a boot manager to:
initiate, via a direct memory access (DMA) controller, a first transfer operation transferring a first portion of boot code from a first non-volatile memory of the device into a volatile memory of the device, the first portion of boot code including a first signature that indicates a presence of the first portion of boot code in the first non-volatile memory;
initiate, via the DMA controller and prior to completion of the first transfer operation, a second transfer operation that concurrently transfers a second portion of the boot code from a second non-volatile memory of the device into the volatile memory of the device, the second portion of the boot code including a second signature that indicates a presence of the second portion of the boot code in the second non-volatile memory; and
execute, via the processor and after completion of at least the first transfer operation of the first portion of boot code, the first and second portions of the boot code from the volatile memory of the device.
9. The one or more hardware-based computer-readable memory devices of claim 8, wherein the boot manager is further implemented to initiate the first transfer operation or the second transfer operation in response to respectively determining, based on the first signature or the second signature, that the first non-volatile memory includes the first portion of the boot code or the second non-volatile memory includes the second portion of the boot code.
10. The one or more hardware-based computer-readable memory devices of claim 8, wherein a data-transfer speed of the first non-volatile memory is different from a data-transfer speed of the second non-volatile memory.
11. The one or more hardware-based computer-readable memory devices of claim 10, wherein a size of the first portion of boot code is different from a size of the second portion of boot code, and a larger of the two portions of boot code is stored in the non-volatile memory having a higher of the two data-transfer speeds.
12. The one or more hardware-based computer-readable memory devices of claim 8, wherein the first and second portions of the boot code are interleaved portions of a composite boot image formed by the boot code, the first and second portions of boot code interleaved on a per-byte, per-page, or per-block basis.
13. The one or more hardware-based computer-readable memory devices of claim 8, wherein the first non-volatile memory or the second non-volatile memory comprise one of a serial peripheral interface (SPI) Flash memory, electronically-erasable programmable read-only memory (EEPROM), NAND Flash, embedded Flash, or embedded multimedia card (eMMC) device.
a processor configured to execute code to boot and implement functionalities of a device;
volatile memory from which boot code is executable by the processor;
a memory controller configured to enable concurrent access of multiple non-volatile memories; and
a boot manager configured to:
determine, based on signatures within the boot code, which of the multiple non-volatile memories include a respective portion of boot code;
initiate, via the memory controller, a direct memory access (DMA) transfer operation transferring one of the respective portions of boot code from one of the multiple non-volatile memories into the volatile memory;
initiate, via the memory controller and prior to completion of the transfer operation, at least one other DMA transfer operation that simultaneously transfers another respective portion of the boot code from another of the multiple non-volatile memories into the volatile memory; and
causing, responsive to completion of at least one of the DMA transfer operations, the processor to initiate execution of the respective portions of the boot code from the volatile memory.
15. The System-on-Chip of claim 14, wherein the multiple non-volatile memories are external non-volatile memories associated with the System-on-Chip via multiple respective memory interfaces.
16. The System-on-Chip of claim 15, wherein a data-transfer speed of the DMA transfer operation is different from a data-transfer speed of the other DMA transfer operation.
17. The System-on-Chip of claim 15, wherein the memory controller includes or is implemented as a DMA controller to implement the DMA transfer operation and the other DMA transfer operation.
18. The System-on-Chip of claim 14, wherein the boot manager is further configured to initiate, prior to completion of the transfer operation, at least two other DMA transfer operations that simultaneously transfer two other portions of the boot code from respective ones of the multiple non-volatile memories, the respective portion and at least two other respective portions of the boot code being transferred into the volatile memory via a system bus or memory bus of the System-on-Chip.
19. The System-on-Chip of claim 14, wherein a size of the respective portion of boot code is different from a size of the other respective portion of boot code.
20. The System-on-Chip of claim 14, wherein the non-volatile memory and the other non-volatile memory are different types of non-volatile memory.
This present disclosure claims priority to U.S. Provisional Patent Application Ser. No. 61/750,222 filed Jan. 8, 2013, the disclosure of which is incorporated by reference herein in its entirety.
Computing and electronic devices often execute an operating system or applications to implement functionalities of the device. An operating system or applications of a device, however, are unable to execute until boot code is used to configure and boot the device for operation. When booting a device, the boot code is typically copied from a non-volatile memory to a volatile memory of the device for execution. Once the boot code is copied into the volatile memory, a processor executes the boot code in order to configure the components of the device for operation.
The details of one or more implementations are set forth in the accompanying drawings and the description below. Other features and advantages will be apparent from the description and drawings. As such, this Summary should not be considered to describe essential features nor used to limit the scope of the claimed subject matter.
A method is described for initiating, via a direct memory access (DMA) controller, a first transfer operation transferring a first portion of boot code from a first memory of a first type into a memory of a second type. The method then initiates, via the DMA controller and prior to completion of the first transfer operation, a second transfer operation transferring a second portion of the boot code from a second memory of the first type into the memory of the second type. After completion of the first and second transfer operations, a processor is caused to execute the first and second portions of the boot code from the memory of the second type.
Another method is described for receiving, via a first data interface, a first portion of boot code from a first memory of a first type and receiving, via a second data interface, a second portion of boot code from a second memory of the first type. The first and second portions of boot code are then transmitted, via a system bus, to a memory of a second type for execution by a processor.
A System-on-Chip is described that includes a boot manager that is configured to load boot code from multiple non-volatile memory devices. The boot manager determines whether each respective non-volatile memory includes a portion of boot code. For each of the multiple non-volatile memories determined to include a portion of boot code, the boot manager configures, without waiting for a previously configured DMA operation to complete, a DMA operation to copy the respective portions of the boot code to a volatile memory. The boot manager then initiates execution of the boot code after completion of the DMA operations.
FIG. 2 illustrates an example system architecture of a computing device accordance with one or more aspects.
FIG. 3 illustrates a method for initiating multiple transfer operations from multiple respective memories.
FIG. 4 illustrates an example allocation of a composite boot image in accordance with one or more aspects.
FIG. 5 illustrates a method for transferring multiple portions of boot code to a volatile memory via a system bus.
FIG. 6 illustrates a method for configuring multiple DMA operations for transferring boot code.
Conventional techniques for loading boot code sequentially copy the boot code from individual non-volatile memories into a volatile memory for execution. For example, when a first block of boot code is detected in a non-volatile memory, the first block of boot code is transferred into the volatile memory before determining whether another non-volatile memory contains additional blocks of boot code. Thus, the boot process is delayed while the first and any other blocks of boot code are individually transferred into the volatile memory. Additionally, data-transfer speeds of non-volatile memories are often slower than those of other data buses of a device, resulting in under-utilization of other system resources during the boot process. Accordingly, sequentially loading boot code delays other boot operations and is inefficient with respect to utilization of other system resources, resulting in prolonged device boot-up times.
This disclosure describes apparatuses and techniques for loading boot code from multiple memories, which enable portions of boot code to be concurrently transferred from multiple non-volatile memories. The portions of boot code are transferred to a volatile memory via a system bus, which has a more bandwidth than respective interfaces of the multiple non-volatile memories from which the portions of boot code are received. By so doing, the portions of boot code can be transferred without waiting for individual transfers to complete and with higher utilization of other system resources. This can be effective reduce delays in the boot process, increase system resource efficiency, or reduce an overall boot time of the device.
FIG. 1 illustrates an example of an operating environment 100 having computing devices 102, each of which are capable of communicating, accessing, presenting, or processing various data. Computing devices 102 include smart-phone 104, tablet computer 106, multi-function printer 108, and fax machine 110, and internet-protocol enabled television 112 (IP TV 112). Although not shown, other configurations of computing devices 102 are also contemplated such as a desktop computer, server, mobile-internet device (MID), camera, netbook, ultra-book, gaming console, appliances, mobile hotspot, networked media player, and so on.
Generally, computing devices 102 have operational states ranging from an “off” state to an “on” state. These states may include a fully off state (mechanical off), suspend state, sleep state, hibernation state, idle state, active state, and the like. When transitioning from a lower operational state to a higher operational state (e.g., from an off state to an active state), computing device 102 is booted. Booting computing device 102 includes transferring and/or executing low-level code (e.g., boot code) to configure components of computing device 102 for operation.
Each computing device 102 includes processor core 114 (e.g. an application processor core) and computer-readable storage media 116 (CRM 116). Although shown as a single core, processor core 114 may be one of any suitable number and/or type of processing cores, which may be configured in any suitable manner (e.g., a heterogeneous multi-core application processor). CRM 116 includes volatile memory 118 and non-volatile memory 120, which may include any suitable type, combination, or number of memory devices. In this particular example, volatile memory 118 includes static random access memory 122 (SRAM 122) and synchronous dynamic random-access memory 124 (DRAM 124). Alternately or additionally, volatile memory 118 may include other suitable types of memory, such as random-access memory (RAM), asynchronous dynamic RAM, double-data-rate RAM (DDR), and the like.
Non-volatile memory 120 includes serial-peripheral interface (SPI) Flash 126, electronically-erasable programmable read-only-memory (EEPROM) 128, and NAND Flash 130. Other non-volatile memories contemplated include non-volatile RAM (NVRAM), read-only memory (ROM), embedded multimedia card (eMMC) devices, NOR Flash, single-level cell (SLC) Flash, multi-level cell (MLC) Flash, and the like. Each non-volatile memory communicates via a respective data interface, which can be configured as a serial, parallel, or multi-bit interface implementing any suitable communication protocol. Alternately or additionally, each non-volatile memory may communicate at a different respective data-transfer rate. For example, SPI Flash 126, EEPROM 128, NAND Flash 130 may communicate at 100 MB/s, 10 MB/s, and 50 MB/s, respectively.
Non-volatile memory 120 stores data of computing device 102 persistently when powered-down or suspended. Boot code of computing device 102 is stored in one or more non-volatile memory components, such as SPI Flash 126 and NAND Flash 130. Operating systems, applications, or user data (not shown) of computing device 102 may be stored by, or executed from, volatile memory 118, non-volatile memory 120, or any other suitable type of CRM 116. Alternately or additionally, operating systems and/or applications of computing device 102 may be embodied as firmware or other processor-executable instructions, binaries, or code. Operating systems and applications of device 102 are executable by processor core 114 to provide a user interface, various functionalities, and/or services of computing device 102.
CRM 116 also contains boot manager 132, which in this particular example, is embodied as processor-executable instructions that are executable by processor core 114 to implement various functionalities. Alternately or additionally, boot manager 132 may be implemented, in part or whole, via firmware or hardware (not shown) or any suitable combination thereof. In some cases, boot manager 132 is hard-coded into a one-time programmable (OTP) memory during fabrication (e.g., manufacturing) of the OTP memory or a chip on which the OTP memory resides. Boot manager 132 may enable concurrent transfers of portions of boot code from non-volatile memory 120 to volatile memory 118. The implementation and use of boot manager 132 varies and is described below.
Computing device 102 also includes direct memory access (DMA) controller 134, which is a memory controller that enables DMA operations between various memories of computing device 102, such as SRAM 122, SPI Flash 126, or NAND Flash 130. Computing device 102 may also include other non-DMA-capable memory controllers (not shown) associated with volatile memory 118 or non-volatile memory 120. DMA operations transfer data from a source memory to a destination memory without involving a higher-level controller or processor (e.g., processor core 114). These DMA operations may include single operation DMA algorithms or advanced DMA operations, such as scatter gather DMA algorithms. Non-volatile memory 120 is accessible via DMA controller 134, which enables DMA controller 134 to transfer boot code from non-volatile memory 120 using DMA operations.
Computing device 102 may also include I/O ports 136, display 138, or network interface(s) 140. I/O ports 136 allow computing device 102 to interact with other devices or users. I/O ports 136 may include any combination of internal or external ports, such as USB ports, audio ports, Serial ATA (SATA) ports, PCI-express based ports or card-slots, secure digital input/output (SDIO) slots, and/or other legacy ports. Various peripherals may be operatively coupled with I/O ports 136, such as human-input devices (HIDs), external computer-readable storage media, or other peripherals.
Display 138 may present a user interface or rendered graphics associated with an operating system or application of computing device 102. Display 138 may include a touch-input sensor (not shown), such as a touch screen or touch-sensitive overlay. Network interface(s) 140 provides connectivity to one or more networks and other devices connected therewith. Data communicated over network interfaces 140 may be packetized or framed depending on a communication protocol or standard by which computing device 102 is communicating. Network interfaces 140 may include wired interfaces, such as Ethernet or fiber optic interfaces for communication over a local network, intranet, or the Internet. Network interfaces 140 may also include wireless interfaces that facilitate communication over wireless networks, such as wireless LANs, cellular networks, or wireless personal-area-networks (WPANs).
FIG. 2 illustrates an example system architecture of a computing device 102 generally at 200. Processor core 114, DRAM 124, and DMA controller 134 communicate via system bus 202, which may be configured as a high-speed bus, memory bus, system crossbar, or interconnect fabric. Communication between each of the components may be direct or indirect, such as through an intermediary component (e.g., memory controller). In some cases, processor core 114, DRAM 124, and DMA controller 134 are implemented as components of a System-on-Chip. Generally, when booting computing device 102 from an off, sleep, or hibernation state, boot code is copied from non-volatile memory devices into DRAM 124 via system bus 202.
In this example, the non-volatile memory devices include SPI Flash 126, EEPROM 128, NAND Flash 130, and quad-SPI Flash 204, which communicates over a multi-bit SPI interface. Each of these non-volatile memories may include a portion of boot code useful to boot computing device 102. In some cases, the boot code is structured as a boot image or composite boot image formed from multiple portions of boot code. The boot code may be portioned or partitioned at any suitable data granularity, such as by byte, page, block, or sector of data. Boot code of different portions may also be interleaved on a per-byte, per-page, or per-block basis. For example, even bytes of boot code can be stored in one portion boot code and odd bytes of the boot can be stored in another portion of the boot code.
In some aspects, an amount of boot code allocated to each non-volatile memory is based on a respective data-transfer speed of the device. For example, if a data-transfer rate of SPI Flash 126 (e.g., 100 MB/s) is twice that of NAND Flash 130 (e.g., 50 MB/s), then approximately twice an amount of the boot code (67%) can be allocated to SPI Flash 126 than an amount (33%) allocated to NAND Flash 130. This can be effective to increase efficiency of a boot process because concurrent transfers of the allocated boot code from these non-volatile devices may complete at approximately a same time.
DMA controller 134 accesses boot code stored in the non-volatile memories via memory interfaces 206 (206-1 through 206-4), each of which may be configured as any suitable type of data bus or data interface. In this example, memory interface 206-1 is configured as a SPI bus for communicating with SPI Flash 126 and memory interface 206-2 is configured as an inter-integrated circuit (I2C) bus for communicating with EEPROM 128. Other suitable data bus or data interface configurations may include secure digital input-output (SDIO), multimedia card (MMC), Open NAND Flash Interface (ONFI), NOR Flash interconnects, and the like.
Each memory interface 206 may also include a respective crypto block 208 (208-1 through 208-4) for performing encryption or hash operations when accessing data stored by the non-volatile memories. In some cases, boot code stored in the non-volatile memories is encrypted or signed to prevent altered or unauthorized boot code from being executed by computing device 102. In such cases, the boot code can be encrypted in accordance with the data encryption standard (DES) or advanced encryption standard (AES). Alternately or additionally, the boot code can be signed with a hash signature that enables a hash calculation to determine whether the boot code has been altered by unauthorized parties.
A signature in a first block of the code may also indicate that a particular non-volatile memory includes boot code or how many blocks of boot code are stored in the non-volatile memory. A first portion of boot code may also include other data useful to copy or transfer the boot code, such as initialization data, headers, address tables, descriptors, hash tables, configuration instructions, and the like. Alternately or additionally, this data may be stored in other locations of the non-volatile memory or a location external to the non-volatile memory. In some cases, boot manager 132 uses this information to configure transfer and link descriptors that cause DMA controller 134 to transfer boot code from the non-volatile memory.
Transfer descriptors typically include a destination address, a length indicator specifying an amount of data to transfer, and various attribute fields (e.g., descriptor type, validity, end, interrupt action). In this particular example, configuring a set of transfer descriptors enables DMA controller 134 to concurrently transfer boot code from multiple non-volatile memories into DRAM 124 for execution.
Techniques of Loading Boot Code from Multiple Memories
The following discussion describes techniques of loading boot code from multiple memories. These techniques can be implemented using the previously described environment or entities, such as boot manager 132 or DMA controller 134 of FIG. 1 embodied on a computing device 102. These techniques include methods illustrated in FIGS. 3, 5, and 6, each of which is shown as a set of operations performed by one or more entities. These methods are not necessarily limited to the orders shown for performing the operations. Further, these methods may be used in conjunction with one another, in whole or in part, whether performed by the same entity, separate entities, or any combination thereof. In portions of the following discussion, reference will be made to operating environment 100 of FIG. 1 and entities of FIGS. 2 and 4 by way of example. Such reference is not to be taken as limited to operating environment 100 but rather as illustrative of one of a variety of examples.
FIG. 3 depicts a method 300 for initiating multiple transfer operations from multiple respective memories, including operations performed by boot manager 132 of FIG. 1.
At 302, a first transfer operation is initiated to transfer a first portion of boot code from a first non-volatile memory. The first transfer operation transfers the first portion of boot code to a volatile memory of a device. The first portion of boot code may include any suitable amount of data, such as a block or page of the boot code. In some cases, the first non-volatile memory includes an indicator indicating a presence of the first portion of boot code. In such cases, the first non-volatile memory can be selected for boot code loading based on this indicator.
The first transfer operation may be a DMA transfer implemented by a DMA controller configured to copy the first portion of boot code from the first non-volatile memory. In some cases, the DMA transfer is initiated by setting up the transfer, which may include configuring a DMA command or transfer descriptor that specifies the first non-volatile memory as a source of the first portion of boot code and the volatile memory as a destination.
As an example, consider a user powering-on fax machine 110 of FIG. 1. Assume here that fax machine 110 is transitioning to an “on” state from an “off” state in which power was removed from volatile memory 118 and other various components of fax machine 110. As shown in FIG. 4, fax machine 110 includes boot image 402, which includes three portions of boot code: boot code block-1 404, boot code block-2 406, and boot code block-3, each of which is stored on a respective non-volatile memory. Here, boot manager 132 examines contents of SPI Flash 126 for an indication (e.g., boot code signature) as to whether SPI Flash 126 stores a first portion of boot image 402. In response to detecting a signature of boot code block-1 404, boot manager 132 configures a first DMA transfer command for DMA controller 134, which is effective to initiate a DMA transfer of boot code block-1 404 from SPI Flash 126.
At 304, a second transfer operation is initiated to transfer a second portion of boot code from a second non-volatile memory. This second transfer operation is initiated prior to completion of the first transfer operation. The second transfer operation transfers the second portion of boot code to the volatile memory of a device. The second portion of boot code may include any suitable amount of data, such as a block or page of the boot code. The second transfer operation may be another DMA transfer that is initiated by setting up the DMA transfer, which is then executed by the DMA controller. In some cases, this includes configuring a DMA command or transfer descriptor that specifies the second non-volatile memory as a source of the second portion of boot code and the volatile memory as a destination.
In the context of the present example, assume that boot manager 132 is configured to attempt initiation of boot code transfers from each non-volatile memory in a top-to-bottom order with reference to FIG. 2, starting with SPI Flash 126 and ending at quad-SPI Flash 204. Also assume that boot manager 132 does not detect an indication of boot code in EEPROM 128 and thus proceeds to NAND Flash 130. Here, boot manager 132 detects a signature of boot code block-2 406, which is stored by NAND Flash 130. Boot manger 132 then configures a second DMA transfer command for DMA controller 134, which is effective to initiate a DMA transfer of boot code block-2 406 from NAND Flash 130.
Optionally at 306, an additional transfer operation is initiated to transfer additional boot code from another non-volatile memory. This additional transfer operation is initiated prior to completion of the first and second transfer operations. Thus, two or more transfer operations may be initiated to concurrently transfer boot code from two or more respective non-volatile memories. The additional transfer operation may be another DMA transfer initiated by setting up the other DMA transfer as described above. Although illustrated as a single operation, operation 306 may be repeated to initiate any suitable number of transfer operations for transferring boot code from non-volatile memories to the volatile memory.
Continuing the ongoing example, after initiating a DMA transfer of boot code block-2 406, boot manager 132 proceeds to quad-SPI Flash 208. Here, boot manager 132 detects a signature of boot code block-3 408, which is stored by quad-SPI Flash 208. Boot manger 132 then configures a third DMA transfer command for DMA controller 134, which is effective to initiate a DMA transfer of boot code block-3 408 from quad-SPI Flash 208. In the context of this example, boot manager 132 has initiated three respective DMA transfers for transferring boot code block-1 404, boot code block-2 406, and boot code block-3 to DRAM 124.
As described above, boot code can be allocated to different non-volatile memories based on a respective data-transfer rate of each different device. Assume here that boot image 402 includes 8 MB of boot code and data-transfer rates of SPI Flash 126, NAND Flash 130, and Quad SPI Flash 208 are 100 MB/s, 100 MB/s, and 200 MB/s, respectively. Accordingly, to maximize transfer efficiencies, a system designer can allocate 4 MB of boot image 402 to boot code block-1 404, 2 MB of boot image 402 to boot code block-2 406, and 2 MB of boot image 402 to boot code block-3 408. By so doing, the three respective DMA transfers of boot code block-1 404, boot code block-2 406, and boot code block-3 may complete at approximately a same time.
At 308, a processor of the device is caused to execute the boot code after at least one of the transfer operations complete. For example, the processor may begin execution of the boot code once any of the transfer operations copy a portion of the boot code into the volatile memory. In some cases, the processor is caused to execute the boot code after two or more of the transfer operations complete. This can be effective to advance a boot process of the device to operations that are dependent on execution of the boot code. In some cases, control of the boot process is transferred to a boot loader or other entity implemented by executing the boot code. Alternately or additionally, other sources can be queried for additional boot code, such as a USB or Ethernet connection.
Concluding the present example, boot manager 132 monitors the three respective DMA transfers of boot code block-1 404, boot code block-2 406, and boot code block-3 into DRAM 124 of fax machine 110. When boot manager 132 determines that boot image 402 is completely transferred, boot manager 132 causes processor core 114 to execute boot image 402 from DRAM 124 to complete boot operations of fax machine 110. Because boot code block-1 404, boot code block-2 406, and boot code block-3 are concurrently loaded into DRAM 124 via respective DMA transfers, fax machine 110 is capable of booting up faster than if implementing a sequential boot code loading process.
FIG. 5 depicts a method 500 for transferring multiple portions of boot code to a volatile memory via a system bus, including operations performed by DMA controller 134 of FIG. 1.
At 502, a first portion of boot code is received via a first data interface. The first portion of boot code is received from a first non-volatile memory. The first portion of boot code may be received at a DMA controller executing a DMA transfer of the first portion of boot code. In some cases, the first non-volatile memory is external to the DMA controller, which features multiple data interfaces to external non-volatile memories. In such cases, the first data interface may be configured to communicate with any suitable type of non-volatile memory, such as SPI Flash, NAND Flash, EEPROM, and the like. From operation 502, method 500 may proceed to operation 504 or to operation 506, at which decryption of the first portion of boot code may be performed.
At 504, a second portion of boot code is received via a second data interface. The second portion of boot code is received from a second non-volatile memory. At least some of the second portion of boot code is received while the first portion of boot code is being received from the first non-volatile memory. The second portion of boot code may also be received at the DMA controller executing a DMA transfer of the second portion of boot code. In some cases, the second non-volatile memory is external to the DMA controller that features multiple data interfaces to external non-volatile memories. In such cases, the second data interface may be configured to communicate with any suitable type of non-volatile memory, such as SPI Flash, NAND Flash, EEPROM, and the like. Alternately or additionally, the first and second data interfaces may be configured differently from each other and implement different bit-widths, clock speeds, transfer protocols, topologies, or communication protocols.
Optionally at 506, the first portion of boot code or the second portion of boot code is decrypted. In some cases, the first portion of boot code is decrypted independently from the second portion of boot code. In such cases, the decryption of the first portion of boot code may be performed while the second portion of boot code is received from the second data interface or decrypted via another decryption engine. The encrypted boot code can be decrypted using a cryptographic module associated with the DMA controller or data interface thereof. Alternately or additionally, a signature hash can be generated to verify authenticity of the boot code before permitting subsequent transfer of the boot code. By decrypting and verifying the boot code, execution of unauthorized or altered boot code can be prevented, which can increase device security or prevent access to protected resources of the device.
At 508, the first and second portions of boot code are transferred to a volatile memory via a system bus. The first and second portions of boot code are then executed in the volatile memory by a processor to boot the device. The system bus has a higher data-transfer rate than respective data-transfer rates of the first and second non-volatile memories. In some cases, the system bus can accommodate multiple concurrent transfers of respective portions of boot codes. In such cases, transferring the multiple respective portions of the boot code concurrently, rather than sequentially, can decrease an amount of time consumed while the boot code loads. This can be effective to reduce an amount of time consumed by a boot code loading process, resulting in faster device boot up.
FIG. 6 depicts a method 600 for configuring multiple DMA operations for transferring boot code, including operations performed by boot manager 132 of FIG. 1.
At 602, a determination is made as to whether a first memory of a device includes boot code. The first memory may be a non-volatile memory device storing a portion of the boot code. The determination is based on an indicator in data of the first memory that indicates a presence of the boot code, such as a signature or hash in a first block of the data. From operation 602, method 600 proceeds to operation 604 if the first memory includes a portion of boot code or directly to operation 606 if the first memory does not include a portion of boot code.
At 604, a DMA operation is configured to copy the boot code from the first memory to another memory of the device for execution. Configuring the DMA operation may include setting up a DMA command or descriptor that, when executed by a DMA controller, copies the boot code from the first memory. In some cases, the DMA operation is a first DMA operation transferring a first portion of boot code from the first memory. The other memory is a volatile memory from which the boot code is executed to boot the device. Once the DMA operation is configured, method 600 proceeds from operation 604 to operation 606.
At 606, a determination is made as to whether a second memory of the device includes boot code. The second memory may be a non-volatile memory device storing a portion of the boot code. The determination is based on an indicator in data of the second memory that indicates a presence of the boot code, such as a signature or hash in a first block of the data. From operation 606, method 600 proceeds to operation 608 if the second memory includes a portion of boot code or directly to operation 610 if the second memory does not include a portion of boot code.
At 608, a DMA operation is configured to copy the boot code from the second memory to the other memory of the device for execution. Configuring the DMA operation may include setting up a DMA command or descriptor that, when executed by a DMA controller, copies the boot code from the first memory. In some cases, this DMA operation is a second DMA operation transferring a second portion of boot code from the second memory. In such cases, the first and second DMA operations are performed concurrently to increase an efficiency of a boot code loading process. Once the DMA operation is configured, method 600 proceeds from operation 608 to operation 610.
At 610, a determination is made as to whether a third memory of the device includes boot code. The third memory may be a non-volatile memory device storing a portion of the boot code. The determination is based on an indicator in data of the third memory that indicates a presence of the boot code, such as a signature or hash in a first block of the data. From operation 610, method 600 proceeds to operation 612 if the third memory includes a portion of boot code or directly to operation 614 if the third memory does not include a portion of boot code.
At 612, a DMA operation is configured to copy the boot code from the third memory to the other memory of the device for execution. Configuring the DMA operation may include setting up a DMA command or descriptor that, when executed by a DMA controller, copies the boot code from the first memory. In some cases, this DMA operation is a third DMA operation transferring a third portion of boot code from the third memory. In such cases, the first, second, and third DMA operations are performed concurrently to increase an efficiency of a boot code loading process. Once the DMA operation is configured, method 600 proceeds from operation 612 to operation 614.
At 614, boot operations of the device are initiated after at least one of the DMA operations complete. In some cases, the boot operations are initiated after multiple DMA operations complete, such as when the boot code of multiple non-volatile memories is interleaved. These boot operations may include assembly or integration of two or more portions of boot code, which are then executed from the other memory. In some cases, control of a boot process is transferred to an entity implemented by execution of the boot code, such as a boot loader. By using multiple DMA operations to transfer the boot code into the other memory, an amount of time consumed by boot operations of the device is reduced. This can be effective to significantly reduce a boot up time of a device, which may improve an overall user experience.
FIG. 7 illustrates a System-on-Chip (SoC) 700, which can implement various aspects of loading boot code from multiple memories. A SoC can be implemented in any suitable device, such as a video game console, IP-enabled television, smart-phone, desktop computer, laptop computer, access point, wireless router, cellular broadband router, tablet computer, server, network-enabled printer, set-top box, printer, scanner, camera, picture frame, home appliance, thermostat, home automation device, and/or any other type of electronic device.
In this example, SoC 700 includes various components such as an input-output (I/O) logic control 702 (e.g., to include electronic circuitry) and microprocessor 704. SoC 700 also includes memory 706, which can be any type and/or combination of RAM, SRAM, DRAM, Flash, low-latency nonvolatile memory, ROM, one-time programmable (OTP) memory, and/or other suitable electronic data storage. Alternately or additionally, SoC 700 may comprise data interfaces (not shown) for accessing additional or external off-chip memory, such as external SRAM, DRAM, or Flash memory. Although not shown, the external memory (or memory 706) may include multiple non-volatile memory devices storing multiple respective portions of boot code, as described with reference to FIGS. 2 and 5. SoC 700 can also include various firmware and/or software, such as operating system(s) 708, which can be computer-executable instructions maintained by memory 706 and executed by microprocessor 704. SoC 700 may also include other various communication interfaces and components embodied as hardware, firmware, software, or any suitable combination thereof.
SoC 700 also includes boot manager 132 and DMA controller 134 (either of which may embodied as disparate or combined components). Examples of these various components, functions, and/or entities, and their corresponding functionality, are described with reference to the respective components of the environment 100 and various configurations as illustrated by FIGS. 2 and 4. Boot manager 132, either independently or in combination with other entities (e.g., DMA controller 134), can be implemented as computer-executable instructions maintained by memory 706 and executed by microprocessor 704 to implement various embodiments and/or features described herein. Boot manager 132 may also be provided integral with other entities of the SoC, such as integrated a memory controller associated with memory 706 or another suitable software, firmware, or hardware component within SoC 700. Alternatively or additionally, boot manager 132 and the other components can be implemented as hardware, firmware, fixed logic circuitry, or any combination thereof that is implemented in connection with the I/O logic control 702 and/or other signal processing and control circuits of SoC 700.
US5155833 11 May 1987 13 Oct 1992 At&T Bell Laboratories Multi-purpose cache memory selectively addressable either as a boot memory or as a cache memory
US5696989 25 Jun 1991 9 Dec 1997 Nec Corporation Microcomputer equipped with DMA controller allowed to continue to perform data transfer operations even after completion of a current data transfer operation
US5991519 3 Oct 1997 23 Nov 1999 Atmel Corporation Secure memory having multiple security levels
US6145069 26 Apr 1999 7 Nov 2000 Interactive Silicon, Inc. Parallel decompression and compression system and method for improving storage density and access speed for non-volatile memory and embedded memory devices
US6216230 31 Jul 1998 10 Apr 2001 Durango Corporation Notebook security system (NBS)
US6473861 3 Dec 1998 29 Oct 2002 Joseph Forte Magnetic optical encryption/decryption disk drive arrangement
US6678790 9 Jun 1997 13 Jan 2004 Hewlett-Packard Development Company, L.P. Microprocessor chip having a memory that is reconfigurable to function as on-chip main memory or an on-chip cache
US6799271 22 Apr 2003 28 Sep 2004 Canon Kabushiki Kaisha Method and system for authenticating user and providing service
US6901298 30 Sep 2002 31 May 2005 Rockwell Automation Technologies, Inc. Saving and restoring controller state and context in an open operating system
US7117352 20 Dec 2002 3 Oct 2006 Lsi Logic Corporation Debug port disable mechanism
US7206940 24 Jun 2002 17 Apr 2007 Microsoft Corporation Methods and systems providing per pixel security and functionality
US7210038 2 Aug 2004 24 Apr 2007 Silverbrook Research Pty Ltd Method for validating an authentication chip
US7370349 3 Sep 2003 6 May 2008 Peoplechart Corporation Method and system for protecting information on a computer system
US7373506 19 Jan 2001 13 May 2008 Sony Corporation Data authentication system
US7511636 27 Aug 2007 31 Mar 2009 Ricoh Company, Ltd. Data conversion unit, data conversion method, and electronic apparatus using the data conversion unit
US7536558 27 Aug 2004 19 May 2009 Tgbw Inc. Flash memory distribution of digital content
US7549056 20 Dec 2002 16 Jun 2009 Broadcom Corporation System and method for processing and protecting content
US7620784 9 Jun 2006 17 Nov 2009 Microsoft Corporation High speed nonvolatile memory device using parallel writing among a plurality of interfaces
US7725738 25 Jan 2005 25 May 2010 Altera Corporation FPGA configuration bitstream protection using multiple keys
US7725818 8 Dec 2005 25 May 2010 International Business Machines Corporation Parallel composition of electronic responses to electronic requests
US7743260 15 May 2007 22 Jun 2010 Richard Fetik Firewall+storage apparatus, method and system
US7835725 1 May 2007 16 Nov 2010 Sony Corporation Wireless communication system, terminal, processing method for use in the terminal, and program for allowing the terminal to execute the method
US7865733 25 Mar 2005 4 Jan 2011 Fujitsu Semiconductor Limited Secure processor and a program for a secure processor
US7898857 20 Mar 2008 1 Mar 2011 Micron Technology, Inc. Memory structure having volatile and non-volatile memory portions
US7900060 17 Feb 2006 1 Mar 2011 Vudu, Inc. Method and system for securing a disk key
US7991943 26 Oct 2007 2 Aug 2011 Standard Microsystems Corporation Implementation of one time programmable memory with embedded flash memory in a system-on-chip
US8094822 3 Feb 2004 10 Jan 2012 Sony Corporation Broadcast encryption key distribution system
US8117478 29 Dec 2006 14 Feb 2012 Intel Corporation Optimizing power usage by processor cores based on architectural events
US8166309 1 May 2007 24 Apr 2012 Infosys Technologies, Ltd. System and method for a secure multi-level network access mechanism using virtual service set identifier broadcast
US8418242 10 Jan 2011 9 Apr 2013 Chengdu Huawei Symantec Technologies Co., Ltd. Method, system, and device for negotiating SA on IPv6 network
US8423789 22 May 2008 16 Apr 2013 Marvell International Ltd. Key generation techniques
US8483718 28 Feb 2007 9 Jul 2013 West Corporation UMA network controller that provides access point identifiers to a location system
US8694782 3 May 2012 8 Apr 2014 Marvell World Trade Ltd. Wireless authentication using beacon messages
US9009778 28 Jul 2006 14 Apr 2015 Rpx Clearinghouse Llc Segmented network identity management
US9220012 15 Jan 2014 22 Dec 2015 Marvell International Ltd. Systems and methods for provisioning devices
US9398455 14 Mar 2013 19 Jul 2016 Marvell World Trade Ltd. System and method for generating an identification based on a public key of an asymmetric key pair
US20020065834 30 Nov 2000 30 May 2002 Kevin Wiggen Maintenance of data integrity during transfer among computer networks
US20020103930 31 Oct 2001 1 Aug 2002 Navic Systems, Inc. Protocol for throttling high volume messages
US20030188162 29 Mar 2002 2 Oct 2003 Brant Candelore Locking a hard drive to a host
US20040015621 20 Mar 2003 22 Jan 2004 Tomonori Tanaka System for and method of controlling multiple direct memory access (DMA) controllers
US20040054898 28 Aug 2002 18 Mar 2004 International Business Machines Corporation Authenticating and communicating verifiable authorization between disparate network domains
US20040103272 27 Nov 2002 27 May 2004 Zimmer Vincent J. Using a processor cache as RAM during platform initialization
US20040184343 21 Jan 2004 23 Sep 2004 Micron Technology, Inc. Write and erase protection in a synchronous memory
US20040193875 27 Mar 2003 30 Sep 2004 Microsoft Corporation Methods and systems for authenticating messages
US20040250057 * 7 May 2004 9 Dec 2004 International Business Machines Corporation Startup system and method using boot code
US20050015602 2 Apr 2004 20 Jan 2005 Rees Robert Thomas Owen Method and apparatus for passing data securely between parties
US20050177674 11 Feb 2004 11 Aug 2005 Infineon Technologies, Inc. Configurable embedded processor
US20050185596 28 Mar 2005 25 Aug 2005 Navic Systems, Inc. Load balancing in set top cable box environment
US20050210290 17 May 2004 22 Sep 2005 Chiyo Ono Contents transmitter apparatus, contents reciever apparatus and contents transmitting method
US20060004946 30 Jun 2004 5 Jan 2006 Shah Shrikant M Apparatus and method for high performance volatile disk drive memory access using an integrated DMA engine
US20060036897 9 Nov 2004 16 Feb 2006 Chanson Lin Data storage device
US20060059372 10 Sep 2004 16 Mar 2006 International Business Machines Corporation Integrated circuit chip for encryption and decryption having a secure mechanism for programming on-chip hardware
US20060104243 4 Oct 2005 18 May 2006 Samsung Electronics Co., Ltd. Method and apparatus for securing media access control (MAC) addresses
US20060209595 22 May 2006 21 Sep 2006 L-3 Integrated Systems Company Systems and methods for write protection of non-volatile memory devices
US20060233149 6 Apr 2006 19 Oct 2006 Viresh Rustagi Secure conditional access and digital rights management in a multimedia processor
US20060253704 16 Mar 2006 9 Nov 2006 James Kempf Multi-key cryptographically generated address
US20060253716 31 Oct 2005 9 Nov 2006 Gaurav Dhiman Apparatus and method for entering and exiting low power mode
US20060259656 10 May 2005 16 Nov 2006 Sullivan Mark J Simulating multiple virtual channels in switched fabric networks
US20060285686 1 Dec 2003 21 Dec 2006 Koninklijke Philips Electronics N.V. Apparatus and method for processing streams
US20070073915 29 Sep 2005 29 Mar 2007 P.A. Semi, Inc. Functional DMA
US20070098178 28 Oct 2005 3 May 2007 Amit Raikar Method and apparatus for automatic and secure distribution of an asymmetric key security credential in a utility computing environment
US20070136523 * 8 Dec 2006 14 Jun 2007 Bonella Randy M Advanced dynamic disk memory module special operations
US20070136792 5 Dec 2005 14 Jun 2007 Ting David M Accelerating biometric login procedures
US20070150756 21 Dec 2006 28 Jun 2007 Nagracard S.A. Secure system-on-chip
US20070174602 * 23 Jan 2006 26 Jul 2007 Rom-Shen Kao Method of system booting with a direct memory access in a new memory architecture
US20070180271 2 Feb 2006 2 Aug 2007 Ibm Corporation Apparatus and method for providing key security in a secure processor
US20070186105 5 Feb 2007 9 Aug 2007 Bailey Daniel V Wireless Authentication Methods and Apparatus
US20070220501 12 Mar 2007 20 Sep 2007 Canon Kabushiki Kaisha Image processing apparatus, method therefor, and storage medium
US20070242643 14 Apr 2006 18 Oct 2007 Microsoft Corporation Using a wireless beacon broadcast to provide a media message
US20080005549 27 Jun 2007 3 Jan 2008 Haibin Ke Method for Accelerating BIOS Running
US20080043508 18 Aug 2006 21 Feb 2008 Po-Yin Chao Method for Programming one-time Programmable Memory of Integrated Circuit
US20080084547 3 Oct 2007 10 Apr 2008 Canon Kabushiki Kaisha Exposure apparatus and device manufacturing method
US20080091944 17 Oct 2006 17 Apr 2008 Von Mueller Clay W Batch settlement transactions system and method
US20080165952 7 Jan 2007 10 Jul 2008 Michael Smith Secure Booting A Computing Device
US20080295157 22 May 2007 27 Nov 2008 Cisco Technology, Inc. Authentication Server With Link State Monitor and Credential Cache
US20090024846 11 Apr 2006 22 Jan 2009 Vvond, Inc. Secured seeding of data in a distributed environment
US20090059841 10 Jan 2007 5 Mar 2009 Rajiv Laroia Wireless communication methods and apparatus using beacon signals
US20090077618 28 Jul 2006 19 Mar 2009 Identity Engines, Inc. Segmented Network Identity Management
US20090080389 26 Sep 2007 26 Mar 2009 Motorola, Inc. Method, system and a data frame for communication in a wireless communication system
US20090131061 27 Jun 2008 21 May 2009 Qualcomm Incorporated Beacon-based control channels
US20090217043 26 Feb 2008 27 Aug 2009 Motorola, Inc. Method and system for mutual authentication of nodes in a wireless communication network
US20090222675 29 Feb 2008 3 Sep 2009 Microsoft Corporation Tamper resistant memory protection
US20090254771 13 Nov 2008 8 Oct 2009 Advanced Micro Devices, Inc. USB Power Conservation Method and Apparatus
US20090310489 17 Jun 2008 17 Dec 2009 Bennett Andrew M Methods and apparatus using a serial data interface to transmit/receive data corresponding to each of a plurality of logical data streams
US20090323972 24 Nov 2008 31 Dec 2009 University Of Washington Privacy-preserving location tracking for devices
US20100039864 12 Aug 2008 18 Feb 2010 Micron Technology, Inc. Methods of erase verification for a flash memory device
US20100122017 * 13 Mar 2008 13 May 2010 Masayuki Toyama Memory controller, non-volatile memory system, and host device
US20100146157 28 Sep 2009 10 Jun 2010 Electronics And Telecommunications Research Institute Multi-radio interfacing and direct memory access based data transferring methods and sink node for performing the same in wireless sensor network
US20100217935 11 Feb 2010 26 Aug 2010 Sung-Goo Cho System on chip and electronic system having the same
US20110039592 13 Aug 2009 17 Feb 2011 Qualcomm Incorporated Methods and apparatus for deriving, communicating and/or verifying ownership of expressions
US20110066837 * 16 Nov 2010 17 Mar 2011 Super Talent Electronics Inc. Single-Chip Flash Device with Boot Code Transfer Capability
US20110211564 24 Mar 2011 1 Sep 2011 Seijiro Yoneyama Communication apparatus
US20110231649 30 Jul 2010 22 Sep 2011 F5 Networks, Inc. Aggressive rehandshakes on unknown session identifiers for split ssl
US20110231652 29 Jul 2010 22 Sep 2011 F5 Networks, Inc. Proxy ssl authentication in split ssl for client-side proxy agent resources with content insertion
US20120284517 3 May 2012 8 Nov 2012 Lambert Paul A Wireless authentication using beacon messages
US20120287337 9 May 2011 15 Nov 2012 Purushotam Kumar Updating Non-Shadow Registers in Video Encoder
US20130031346 18 Jul 2012 31 Jan 2013 Premanand Sakarda Switching Between Processor Cache and Random-Access Memory
US20130124844 14 Nov 2012 16 May 2013 Marvell World Trade Ltd. Dynamic Boot Image Streaming
US20130246792 14 Mar 2013 19 Sep 2013 Marvell World Trade Ltd. Key centric identity
US20140122810 25 Oct 2012 1 May 2014 Texas Instruments Incorporated Parallel processing of multiple block coherence operations
US20140189340 30 Mar 2012 3 Jul 2014 Ted A. Hadley Secure boot information with validation control data specifying a validation technique
US20140258724 6 Mar 2014 11 Sep 2014 Marvell World Trade Ltd. Secure simple enrollment
US20150039876 25 Jun 2014 5 Feb 2015 Marvell World Trade Ltd. Parallelizing Boot Operations
US20150071438 10 Sep 2014 12 Mar 2015 Marvell World Trade Ltd. Secure device bootstrap identity
CN88102647A 10 May 1988 28 Dec 1988 美国电话电报公司 Multi-purpose memory
CN101097522A 30 Jun 2006 2 Jan 2008 联想(北京)有限公司 Method for accelerating BIOS operation
CN102272734B 11 Dec 2009 10 Sep 2014 马维尔国际贸易有限公司 Method and system for hibernation or suspend using a non-volatile-memory device
GB2407239B Title not available
JP2006285738A Title not available
WO2013019423A1 19 Jul 2012 7 Feb 2013 Marvell World Trade Ltd. Switching between processor cache and random-access memory
WO2013074797A1 15 Nov 2012 23 May 2013 Marvell World Trade Ltd. Dynamic boot image streaming
2 "Board Opinion", CN Application No. 200980136849.9, Aug. 28, 2015, 18 Pages.
3 "Corrected Notice of Allowance", U.S. Appl. No. 13/676,701, May 18, 2016, 2 pages.
4 "Examiner's Answer to Appeal Brief", U.S. Appl. No. 13/958,101, Apr. 8, 2016, 9 pages.
5 "Extensions to Direct Link Setup (DLS) Comments", IEEE, P802.11z, Jul. 2009, pp. 1-3.
6 "Final Office Action", U.S. Appl. No. 12/098,254, May 18, 2011, 11 pages.
7 "Final Office Action", U.S. Appl. No. 12/101,668, May 10, 2012, 8 pages.
8 "Final Office Action", U.S. Appl. No. 12/125,670, May 24, 2011, 11 pages.
9 "Final Office Action", U.S. Appl. No. 12/125,693, Jun. 9, 2011, 9 pages.
10 "Final Office Action", U.S. Appl. No. 12/178,268, May 25, 2011, 13 pages.
11 "Final Office Action", U.S. Appl. No. 12/541,731, May 31, 2012, 11 pages.
12 "Final Office Action", U.S. Appl. No. 13/552,421, Mar. 16, 2015, 10 pages.
13 "Final Office Action", U.S. Appl. No. 13/804,425, Nov. 21, 2014, 17 pages.
14 "Final Office Action", U.S. Appl. No. 13/804,425, Nov. 6, 2015, 9 pages.
15 "Final Office Action", U.S. Appl. No. 13/863,079, Jan. 15, 2015, 7 pages.
16 "Final Office Action", U.S. Appl. No. 13/863,079, May 7, 2014, 7 pages.
17 "Final Office Action", U.S. Appl. No. 13/958,101, Dec. 19, 2014, 17 pages.
18 "Final Office Action", U.S. Appl. No. 14/205,196, Aug. 25, 2016, 16 pages.
19 "Final Office Action", U.S. Appl. No. 14/315,019, Sep. 15, 2016, 21 pages.
20 "Foreign Decision to Grant", JP Application No. 2011-544456, May 20, 2014, 2 pages.
21 "Foreign Notice of Allowance", CN Application No. 200980153758.6, Jul. 15, 2014, 4 Pages.
22 "Foreign Notice of Allowance", JP Application No. 2011-527899, Jan. 28, 2014, 1 Page.
23 "Foreign Office Action", CN Application No. 200980136849.9, Feb. 7, 2014, 15 Pages.
24 "Foreign Office Action", CN Application No. 200980136849.9, May 19, 2014, 11 Pages.
25 "Foreign Office Action", CN Application No. 200980136849.9, May 24, 2013, 20 Pages.
26 "Foreign Office Action", CN Application No. 200980153758.6, Apr. 27, 2013, 14 pages.
27 "Foreign Office Action", CN Application No. 200980153758.6, Dec. 30, 2013, 8 pages.
28 "Foreign Office Action", CN Application No. 201280033662.8, May 3, 2016, 26 pages.
29 "Foreign Office Action", European Patent Application No. 09803951.4, Dec. 13, 2012, 6 pages.
30 "Foreign Office Action", European Patent Application No. 09803951.4, May 24, 2012, 3 pages.
31 "Foreign Office Action", JP Application No. 2011-527899, Apr. 16, 2013, 5 pages.
32 "Foreign Office Action", JP Application No. 2011-527899, Aug. 13, 2013, 2 pages.
33 "Foreign Office Action", JP Application No. 2011-527899, Nov. 6, 2012, 4 pages.
34 "Foreign Office Action", JP Application No. 2011-544456, Dec. 3, 2013, 2 pages.
35 "Foreign Office Action", JP Application No. 2011-544456, Jan. 29, 2013, 7 pages.
36 "Foreign Office Action", JP Application No. 2011-544456, Jul. 9, 2013, 6 pages.
37 "Foreign Office Action", KR Application No. 10-2011-7008700, Jun. 16, 2015, 13 Pages.
38 "IEEE Standard for Information Technology-Telecommunications and Information Exchange between Systems-Local and Metropolitan Area Networks-Specific Requirements", Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications; IEEE Std. 802.11-2012, Mar. 29, 2012, 2793 pages.
39 "Intent to Grant", EP Application No. 09803951.4, May 14, 2013, 13 Pages.
40 "International Search Report and Written Opinion", Application No. PCT/IB2014/02221, Dec. 11, 2014, 8 Pages.
41 "International Search Report and Written Opinion", Application No. PCT/US2009/056973, Nov. 4, 2009, 13 pages.
42 "International Search Report and Written Opinion", Application No. PCT/US2009/067767, Mar. 26, 2010, 12 pages.
43 "International Search Report and Written Opinion", Application No. PCT/US2012/047426, Oct. 19, 2012, 7 pages.
44 "International Search Report and Written Opinion", Application No. PCT/US2012/065290, May 2, 2013, 9 pages.
45 "International Search Report and Written Opinion", PCT Application No. PCT/US2013/031545, Mar. 14, 2015, 11 pages.
46 "International Search Report and Written Opinion", PCT Application PCT/US2012/036236, Jul. 6, 2012, 9 pages.
47 "International Search Report", Application No. PCT/US2008/078343, May 18, 2009, 5 pages.
48 "International Search Report", Application No. PCT/US2008/078343, Partial International Search, Mar. 5, 2009, 2 pages.
49 "Marketing Requirements Document for Interoperability Testing & Certification of Device Provisioning Protocol", Wi-Fi Alliance Device Provisioning Protocol Marketing Task Group; Version 1.2, 2012, 34 pages.
50 "Non-Final Office Action", U.S. Appl. No. 12/098,254, Jan. 14, 2011, 8 pages.
51 "Non-Final Office Action", U.S. Appl. No. 12/101,668, Apr. 5, 2011, 7 pages.
52 "Non-Final Office Action", U.S. Appl. No. 12/101,668, Aug. 9, 2012, 8 pages.
53 "Non-Final Office Action", U.S. Appl. No. 12/125,670, Dec. 13, 2011, 11 pages.
54 "Non-Final Office Action", U.S. Appl. No. 12/125,670, Dec. 7, 2010, 9 pages.
55 "Non-Final Office Action", U.S. Appl. No. 12/125,670, Jun. 4, 2012, 12 pages.
56 "Non-Final Office Action", U.S. Appl. No. 12/125,693, Dec. 20, 2010, 7 pages.
57 "Non-Final Office Action", U.S. Appl. No. 12/125,693, Oct. 3, 2011, 7 pages.
58 "Non-Final Office Action", U.S. Appl. No. 12/178,268, Dec. 21, 2011, 13 pages.
59 "Non-Final Office Action", U.S. Appl. No. 12/178,268, Dec. 22, 2010, 10 pages.
60 "Non-Final Office Action", U.S. Appl. No. 12/271,761, Oct. 3, 2011, 6 pages.
61 "Non-Final Office Action", U.S. Appl. No. 12/541,731, Oct. 21, 2011, 9 pages.
62 "Non-Final Office Action", U.S. Appl. No. 12/541,731, Sep. 4, 2012, 11 pages.
63 "Non-Final Office Action", U.S. Appl. No. 12/559,987, Nov. 9, 2011, 10 pages.
64 "Non-Final Office Action", U.S. Appl. No. 12/636,558, Jan. 10, 2012, 6 pages.
65 "Non-Final Office Action", U.S. Appl. No. 12/636,558, May 29, 2012, 8 pages.
66 "Non-Final Office Action", U.S. Appl. No. 13/252,416, Mar. 13, 2013, 16 pages.
67 "Non-Final Office Action", U.S. Appl. No. 13/333,551, Apr. 6, 2012, 5 pages.
68 "Non-Final Office Action", U.S. Appl. No. 13/462,972, May 22, 2013, 10 pages.
69 "Non-Final Office Action", U.S. Appl. No. 13/552,421, Sep. 30, 2014, 23 pages.
70 "Non-Final Office Action", U.S. Appl. No. 13/598,282, Oct. 16, 2013, 6 pages.
71 "Non-Final Office Action", U.S. Appl. No. 13/657,511, Mar. 28, 2013, 13 pages.
72 "Non-Final Office Action", U.S. Appl. No. 13/676,701, Jul. 31, 2015, 12 pages.
73 "Non-Final Office Action", U.S. Appl. No. 13/683,056, Nov. 8, 2013, 5 pages.
74 "Non-Final Office Action", U.S. Appl. No. 13/804,425, Jul. 18, 2014, 14 pages.
75 "Non-Final Office Action", U.S. Appl. No. 13/804,425, May 4, 2015, 15 pages.
76 "Non-Final Office Action", U.S. Appl. No. 13/863,079, Apr. 9, 2015, 7 pages.
77 "Non-Final Office Action", U.S. Appl. No. 13/863,079, Aug. 27, 2014, 6 pages.
78 "Non-Final Office Action", U.S. Appl. No. 13/863,079, Jun. 20, 2013, 10 pages.
79 "Non-Final Office Action", U.S. Appl. No. 13/863,079, Oct. 1, 2013, 9 pages.
80 "Non-Final Office Action", U.S. Appl. No. 13/874,201, Jun. 5, 2015, 10 pages.
81 "Non-Final Office Action", U.S. Appl. No. 13/958,101, Apr. 8, 2015, 16 pages.
82 "Non-Final Office Action", U.S. Appl. No. 13/958,101, Jun. 6, 2014, 14 pages.
83 "Non-Final Office Action", U.S. Appl. No. 14/205,196, Feb. 5, 2016, 14 pages.
84 "Non-Final Office Action", U.S. Appl. No. 14/315,019, May 20, 2016, 17 pages.
85 "Notice of Allowance", U.S. Appl. No. 12/098,254, Dec. 14, 2011, 4 pages.
86 "Notice of Allowance", U.S. Appl. No. 12/098,254, Sep. 28, 2011, 4 pages.
87 "Notice of Allowance", U.S. Appl. No. 12/101,668, Jan. 11, 2013, 6 pages.
88 "Notice of Allowance", U.S. Appl. No. 12/125,670, Dec. 11, 2012, 8 pages.
89 "Notice of Allowance", U.S. Appl. No. 12/178,268, Jul. 2, 2012, 4 pages.
90 "Notice of Allowance", U.S. Appl. No. 12/271,761, Jan. 3, 2012, 6 pages.
91 "Notice of Allowance", U.S. Appl. No. 12/541,731, Apr. 2, 2013, 8 pages.
92 "Notice of Allowance", U.S. Appl. No. 12/559,987, Jun. 15, 2012, 5 pages.
93 "Notice of Allowance", U.S. Appl. No. 12/636,558, Jan. 9, 2013, 4 pages.
94 "Notice of Allowance", U.S. Appl. No. 13/252,416, Sep. 27, 2013, 10 pages.
95 "Notice of Allowance", U.S. Appl. No. 13/333,551, May 30, 2012, 4 pages.
96 "Notice of Allowance", U.S. Appl. No. 13/552,421, Jun. 10, 2015, 5 pages.
97 "Notice of Allowance", U.S. Appl. No. 13/552,421, May 12, 2015, 4 pages.
98 "Notice of Allowance", U.S. Appl. No. 13/598,282, May 6, 2014, 4 pages.
99 "Notice of Allowance", U.S. Appl. No. 13/657,511, Nov. 4, 2013, 9 pages.
100 "Notice of Allowance", U.S. Appl. No. 13/676,701, Feb. 10, 2016, 5 pages.
101 "Notice of Allowance", U.S. Appl. No. 13/683,056, May 9, 2014, 4 pages.
102 "Notice of Allowance", U.S. Appl. No. 13/804,425, Mar. 21, 2016, 9 pages.
103 "Notice of Allowance", U.S. Appl. No. 13/874,201, Sep. 25, 2015, 6 pages.
104 "Part 11-Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications", Information Technology-Telecommunications & Information Exchange Between Systems . . . International Standard, ISO/IEC 8802-11, First Ed., 1999, pp. 1-531.
105 "Public Key Cryptography for the Financial Services Industry: Elliptic Curve Key Agreement and Key Transport Schemes", Working Draft; Version 2.0, Jul. 5, 1998, 125 pages.
106 "Restriction Requirement", U.S. Appl. No. 12/101,668, Sep. 22, 2011, 6 pages.
107 "Restriction Requirement", U.S. Appl. No. 13/676,701, Feb. 12, 2015, 7 pages.
108 "Specification Requirements Document (SRD) for Devise Provisioning Protocol", Wi-Fi Alliance Device Provisioning Protocol Marketing Task Group; Version 1.1, 2013, 13 pages.
109 "Supplemental Notice of Allowance", U.S. Appl. No. 12/101,668, Feb. 8, 2013, 4 Pages.
110 "Supplemental Notice of Allowance", U.S. Appl. No. 13/333,551, Oct. 23, 2012, 2 pages.
111 "Wi-Fi Peer-to-Peer (P2P) Technical Specification", WiFi Alliance; Version 1.5, 2014, 183 pages.
112 Anderson,"HDD Based Full Disc Encryption", In Proceedings of THIC Conference 2006, Mar. 2006, 12 pages.
113 Cooper,"Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (SRL) Profile", Network Working Group; RFC 5280, May 2008, 152 pages.
114 Harkins,"Synthetic Initialization Vecor (SIV) Authenticated Encryption Using the Advanced Encryption Standard (AES)", Network Working Group; RFC 5297; Aruba Networks, Oct. 2008, 27 pages.
115 Krawczyk,"HMAC-based Extract-and-Expand Key Derivation Function (HKDF)", Internet Engineering Task Forct (IETF); RFC 5869, May 2010, 15 pages.
116 McGrew,"Fundamental Elliptic Curve Cryptography Algorithms", Internet Engineering Task Force (IETF); RFC 6090; Fundamental Elliptic Cryptography Algorithms, Feb. 2011, 35 pages.
117 Van"Crypto Based Host Identifiers", Internet Draft; draft-van-beijnum-multi6-cbhi-00.txt; ISSN: 0000-0004; XP15036389A, Jan. 1, 2004, 9 pages.
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:KIM, MYUNGQUE;REEL/FRAME:035269/0073
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MARVELL SEMICONDUCTOR, INC.;REEL/FRAME:035269/0099