INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH INTEL PRODUCTS. NO LICENSE , E XPRESS OR IMPLIED, BY ESTOPPEL OR
OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN INTEL'S TERMS AND CONDITIONS
OF SALE FOR SUCH PRODUCTS, INTEL ASSUMES NO LIABILITY WHATSOEVER AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELA TING
TO SALE AND/OR USE OF INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE,
MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT.
A "Mission Critical Application" is any application in which failure of the Intel Product could result, directly or indirectly, in personal injury or death.
SHOULD YOU PURCHASE OR USE INTEL'S PRODUCTS FOR ANY SUCH MISSION CRITICAL APPLICATION, YOU SHALL INDEMNIFY AND HOLD INTEL AND
ITS SUBSIDIARIES, SUBCONTRACTORS AND AFFILIATES, AND THE DIRECTORS, OFFICERS, AND EMPLOYEES OF EACH, HARMLESS AGAINST ALL
CLAIMS COSTS, DAMAGES, AND EXPENSES AND REASONABLE ATTORNEYS' FEES ARISING OUT OF , DIRECTL Y OR INDIRECTL Y, ANY CLAIM OF PRODUCT
LIABILITY, PERSONAL INJURY, OR DEATH ARISING IN ANY WAY OUT OF SUCH MISSION CRITICAL APPLICATION, WHETHER OR NOT INTEL OR ITS
SUBCONTRACTOR WAS NEGLIGENT IN THE DESIGN, MANUFACTURE, OR WARNING OF THE INTEL PRODUCT OR ANY OF ITS PARTS.
Intel may make changes to specifications and product descriptions at any time, without notice. Designers must not rely on the absence or characteristics
of any features or instructions marked "reserved" or "undefined". Intel reserves these for future definition and shall have no responsibility whatsoever
for conflicts or incompatibilities arising from future changes to them. The information here is subject to change without notice. Do not finalize a design
with this information.
The products described in this document may contain design defects or errors known as errata which may cause the product to deviate from published
specifications. Current characterized errata are available on request.
Contact your local Intel sales office or your distributor to obtain the latest specifications and before placing your product order.
Copies of documents which have an order number and are referenced in this document, or other Intel literature, may be obtained by calling 1-800-548-
4725, or go to: http://www.intel.com/design/literature.htm
Any software source code reprinted in this document is furnished for informational purposes only and may only be used or copied and no license, express
or implied, by estoppel or otherwise, to any of the reprinted source code is granted by this document.
Intel processor numbers are not a measure of performance. Processor numbers differentiate features within each processor family, not across different
processor families. Go to: http://www.intel.com/products/processor_number/
Code Names are only for use by Intel to identify products, platforms, programs, services, etc. (“products”) in development by Intel that have not been
made commercially available to the public, i.e., announced, launched or shipped. They are never to be used as “commercial” names for products. Also,
they are not intended to function as trademarks.
This manual describes the embedded Intel® Quark SoC X1000 Core. It is intended for
use by hardware designers familiar with the principles of embedded microprocessors
and with the Intel® Quark SoC X1000 Core architecture.
1.1Manual Contents
Table 1 summarizes the contents of the remaining chapters and appendixes. The
remainder of this chapter describes notation conventions and special terminology used
throughout the manual and provides references to related documentation.
Provides an overview of the current embedded Intel
including product features, system components, system architecture, and
applications. This chapter also lists product frequency, voltage, and package
offerings.
®
Describes the Intel
overview of the processor’s functional units.
Details the Intel
architecture registers, system-level registers, debug and t est registers, and Intel
Quark SoC X1000 Core Model Specific Registers (MSRs).
When the Intel
Mode, which is described in this chapter.
Describes Protected Mode, including segmentation, protection, and paging.
The Intel
cache. This chapter describes its functionality.
Describes the System Management Mode architecture of the Intel
X1000 Core, including System Management Mode interrupt processing and
programming.
Describes the hardware interface of the Intel
signal descriptions, interrupt interfaces, write buffers, reset and initialization, and
clock control.
Describes the features of the processor bus, including bus cycle handling,
interrupt and reset signals, cache control, and floating-point error control.
Describes the Intel
breakpoint instruction, single-step trap, and debug registers.
Describes the Intel
each field within the instructions.
®
Quark SoC X1000 Core contains an on-chip cache, also known as L1
Quark SoC X1000 Core internal architecture, with an
®
Quark SoC X1000 Core register set, including the base
®
Quark SoC X1000 Core is powered-up, it is initialized in Real
®
Quark SoC X1000 Core debugging support, including the
®
Quark SoC X1000 Core instruction set and the encoding of
®
Quark SoC X1000 Core,
®
Quark SoC
®
Quark SoC X1000 Core, including
®
October 2013Developer’s Manual
Order Number: 329679-001US17
Intel® Quark SoC X1000 Core
Table 1.Manual Contents (Sheet 2 of 2)
ChapterDescription
Appendix A, “Signal
Descriptions”
Appendix B, “Testability”
Appendix C, “Feature
Determination”
Lists each Intel
Describes the testability of the Intel
cache testing, translation lookaside buffer (TLB) testing, and JTAG.
Documents the CPUID function, which is used to determine the Intel
X1000 Core identification and processor-specific information.
1.2Notation Conventions
The following notations are used throughout this manual.
#The pound symbol (#) appended to a signal name indicates that
the signal is active low.
VariablesVariables are shown in italics. Variables must be replaced with
New TermsNew terms are shown in italics.
InstructionsInstruction mnemonics are shown in upper case. When you are
NumbersHexadecimal numbers are represented by a string of
Units of MeasureThe following abbreviations are used to represent units of
correct values.
programming, instructions are not case-sensitive. Y ou ma y use
either upper or lower case.
hexadecimal digits followed by the character H. A zero prefix is
added to numbers that begin with A through F . (F or example, FF
is shown as 0FFH.) Decimal and binary numbers are
represented by their customary notations. (That is, 255 is a
decimal number and 1111 1111 is a binary number. In some
cases, the letter B is added for clarity.)
measure:
Intel® Quark Core—About this Manual
®
Quark SoC X1000 Core signal and describes its function.
Register BitsWhen the text refers to more that one bit, the range of bits is
Register NamesRegister names are shown in upper case. If a register name
Signal NamesSignal names are shown in upper case. When several signals
®
Quark Core
µFmicrofarads
pFpicofarads
Vvolts
represented by the highest and lowest numbered bits,
separated by a colon (example: A[15:8]). The first bit shown
(15 in the example) is the most-significant bit and the second
bit shown (8) is the least-significant bit.
contains a lower case, italic character, it represents more than
one register. For example, PnCFG represents three registers:
P1CFG, P2CFG, and P3CFG.
share a common name, an individual signal is represented by
the signal name followed by a number, whereas the group is
represented by the signal name followed by a variable (n). For
example, the lower chip select signals are named CS0#, CS1#,
CS2#, and so on; they are collectively called CSn#. A pound
symbol (#) appended to a signal name identifies an active-low
signal. Port pins are represented by the port abbreviation, a
period, and the pin number (e.g., P1.0, P1.1).
1.3Special Terminology
The following terms have special meanings in this manual.
Assert and De-assertThe terms assert and de-assert refer to the act of making a
signal active and inactive, respectively. The active polarity
(high/low) is defined by the signal name. Active-low signals are
designated by the pound symbol (#) suffix; active-high signals
have no suffix. To assert RD# is to drive it low; to assert HOLD
is to drive it high; to de-assert RD# is to drive it high; to deassert HOLD is to drive it low.
DOS I/O AddressPeripherals compatible with PC/AT system architecture can be
mapped into DOS (or PC/AT) addresses 0H–03FFH. In this
manual, DOS address and PC/AT address are synonymous.
Expanded I/O Address All peripheral registers reside at I/O addresses 0F000H–0FFFFH.
PC/AT-compatible integrated peripherals can also be mapped
into DOS (or PC/AT) address space (0H–03FFH).
PC/AT AddressIntegrated peripherals that are compatible with PC/AT system
architecture can be mapped into PC/AT (or DOS) addresses 0H–
03FFH. In this manual, the terms DOS address and PC/AT
address are synonymous.
Set and ClearThe terms set and clear refer to the value of a bit or the act of
giving it a value. If a bit is set, its value is “1”; setting a bit gives
it a “1” value. If a bit is clear, its value is “0”; clearing a bit gives
it a “0” value.
October 2013Developer’s Manual
Order Number: 329679-001US19
Intel® Quark SoC X1000 Core
1.4Related Documents
Intel® Quark Core—About this Manual
The following Intel documents contain additional information on designing systems that
incorporate the Intel
The Intel® Quark Core enables a range of low-cost, high-performance embedded
system designs capable of running applications written for the Intel architecture. The
Intel® Quark Core integrates a 16-Kbyte unified cache and floating-point hardware onchip for improved performance. For further details, including the Intel
feature list, see Chapter 2 in the Intel
Manual.
2.1Intel® Quark Core Architecture
Figure 1 shows how the Intel® Quark Core is implemented in the Intel® Quark SoC
X1000.
Figure 1.Intel® Quark SoC X1000 Core used in Intel® Quark SoC X1000
®
Quark SoC X1000 Core Hardware Reference
®
Quark Core
October 2013Developer’s Manual
Order Number: 329679-001US21
Intel® Quark SoC X1000 Core
3.0Architectural Overview
3.1Internal Architecture
Intel® Quark Core—Architectural Overview
The Intel® Quark Core has a 32-bit architecture with on-chip memory management
and cache and floating-point units. The Intel
sizing for the external data bus; that is, the bus size can be specified as 8-, 16-, or 32bits wide.
Note:The implementation of Intel
®
dynamic bus sizing. Bus width is fixed at 32 bits.
®
Intel
Quark Core functional units are listed below:
• Bus Interface Unit (BIU)
•Cache Unit
• Instruction Prefetch Unit
• Instruction Decode Unit
• Control Unit
• Integer (Datapath) Unit
• Floating-Point Unit
• Segmentation Unit
• Paging Unit
For further details, see Chapter 3 in the Intel
Reference Manual.
3.2System Architecture
®
Quark Core also supports dynamic bus
Quark Core on Intel® Quark SoC X1000 does not support
®
Quark SoC X1000 Core Hardware
Intel® Quark Core System Architecture includes the following:
• Memory Organization
• I/O Space
• Addressing Modes
• Data Types
• Interrupts
3.3Memory Organization
Memory on the Intel® Quark SoC X1000 Core is divided up into 8-bit quantities (bytes),
16-bit quantities (words), and 32-bit quantities (dwords). Words are stored in two
consecutive bytes in memory with the low-order byte at the lowest address, the high
order byte at the high address. Dwords are stored in four consecutive bytes in memory
with the low-order byte at the lowest address, the high-order byte at the highest
address. The address of a word or dword is the byte address of the low-order byte.
In addition to these basic data types, the Intel® Quark SoC X1000 Core supports two
larger units of memory: pages and segments. Memory can be divided up into one or
more variable-length segments, which can be swapped to disk or shared between
programs. Memory can also be organized into one or more 4-Kbyte pages. Both
segmentation and paging can be combined, gaining the advantages of both systems.
The Intel
®
Quark SoC X1000 Core supports both pages and segments in order to
provide maximum flexibility to the system designer. Segmentation and paging are
complementary. Segmentation is useful for organizing memory in logical modules, and
as such is a tool for the application programmer, while pages are useful for the system
programmer for managing the physical memory of a system.
3.3.1Address Spaces
The Intel® Quark SoC X1000 Core has three distinct address spaces: logical, linear , and
physical. A logical address (also known as a virtual address) consists of a selector and
an offset. A selector is the contents of a segment register. An offset is formed by
summing all of the addressing components (BASE, INDEX, DISPLACEMENT) discussed
in Section 3.5.3 into an effective address. Because each task on the Intel® Quark SoC
X1000 Core has a maximum of 16 K (2
32
(2
bits), this gives a total of 246 bits or 64 terabytes of logical address space per task.
The programmer sees this virtual address space.
The segmentation unit translates the logical address space into a 32-bit linear address
space. If the paging unit is not enabled then the 32-bit linear address corresponds to
the physical address. The paging unit translates the linear address space into the
physical address space. The physical address is what appears on the address pins.
14
- 1) selectors, and offsets can be 4 Gbytes
The primary difference between Real Mode and Protected Mode is how the
segmentation unit performs the translation of the logical address into the linear
address. In Real Mode, the segmentation unit shifts the selector left four bits and adds
the result to the offset to form the linear address. While in Protected Mode every
selector has a linear base address associated with it. The linear base address is stored
in one of two operating system tables (i.e., the Local Descriptor Table or Global
Descriptor Table). The selector's linear base address is added to the offset to form the
final linear address.
Figure 2 shows the relationship between the various address spaces.
October 2013Developer’s Manual
Order Number: 329679-001US23
Intel® Quark SoC X1000 Core
Figure 2.Address Translation
A5158-01
Effective
Address
32
Physical
Address
32
32
Segmentation
Unit
Selector
R
P
L
Logical or
Virtual Address
13
Descriptor Index
03215
Segment Register
Linear
Address
Paging Unit
(optional use)
Physical
Memory
BE3#–BE0#
A31–A2
031
Effective Address Calculation
Displacement
Index
Base
Scale
1, 2, 3, 4
X
+
Intel® Quark Core—Architectural Overview
3.3.2Segment Register Usage
The main data structure used to organize memory is the segment. On the Intel® Quark
SoC X1000 Core, segments are variable sized blocks of linear addresses which have
certain attributes associated with them. There are two main types of segments: code
and data. The segments are of variable size and can be as small as 1 byte or as large
as 4 Gbytes (2
In order to provide compact instruction encoding, and increase Intel
32
bytes).
®
Quark SoC
X1000 Core performance, instructions do not need to explicitly specify which segment
register is used. A default segment register is automatically chosen according to the
rules of Table 3. In general, data references use the selector contained in the DS
register; stack references use the SS register and Instruction fetches use the CS
register. The contents of the Instruction Pointer provide the offset. Special segment
override prefixes allow the explicit use of a given segment register, and override the
implicit rules listed in Table 3. The override prefixes also allow the use of the ES, FS and
GS segment registers.
There are no restrictions regarding the overlapping of the base addresses of any
segments. Thus, all 6 segments could have the base address set to zero and create a
system with a 4-Gbyte linear address space. This creates a system where the virtual
address space is the same as the linear address space. Further details of segmentation
are discussed in Chapter 6.0, “Protected Mode Architecture.”
The Intel® Quark SoC X1000 Core allows 64 K+3 bytes to be addressed within the I/O
space. The Host Bridge propagates the Intel
without any translation on to the destination bus and, therefore, provides
addressability for 64 K+3 byte locations. Note that the upper three locations can be
accessed only during I/O address wrap-around when processor bus A16# address
signal is asserted. A16# is asserted on the processor bus when an I/O access is made
to 4 bytes from address 0FFFDh, 0FFFEh, or 0FFFFh. A16# is also asserted when an I/O
access is made to 2 bytes from address 0FFFFh.
Table 3.Segment Register Selection Rules
Type of Memory Reference
Code FetchCSNone
Destination of PUSH, PUSHF, INT, CALL, PUSHA
Instructions
Source of POP, POPA, POPF, IRET, RET instructionsSSNone
Destination of STOS, MOVS, REP STOS, REP MOVS
Instructions (DI is Base Register)
Other Data References, with Effective Address using
The I/O ports are accessed via the IN and OUT I/O instructions, with the port address
supplied as an immediate 8-bit constant in the instruction or in the DX register. All 8and 16-bit port addresses are zero extended on the upper address lines. The I/O
instructions cause the M/IO# pin to be driven low.
I/O port addresses 00F8H through 00FFH are reserved for use by Intel.
I/O instruction code is cacheable.
I/O data is not cacheable.
I/O transfers (data or code) can be bursted.
3.5Addressing Modes
3.5.1Addressing Modes Overview
The Intel® Quark SoC X1000 Core provides a total of 11 addressing modes for
instructions to specify operands. The addressing modes are optimized to allow the
efficient execution of high-level languages such as C and FOR TRAN, and they co ver the
vast majority of data references needed by high-level languages.
October 2013Developer’s Manual
Order Number: 329679-001US25
Intel® Quark SoC X1000 Core
3.5.2Register and Immediate Modes
The following two addressing modes provide for instructions that operate on register or
immediate operands:
• Register Operand Mode: The operand is located in one of the 8-, 16- or 32-bit
general registers.
• Immediate Operand Mode: The operand is included in the instruction as part of the
opcode.
3.5.332-Bit Memory Addressing Modes
The remaining modes provide a mechanism for specifying the effective address of an
operand. The linear address consists of two components: the segment base address
and an effective address. The effective address is calculated by using combinations of
the following four address elements:
• DISPLACEMENT: An 8-, or 32-bit immediate value, following the instruction.
• BASE: The contents of any general purpose register. The base registers are
generally used by compilers to point to the start of the local variable area.
• INDEX: The contents of any general purpose register except for ESP. The index
registers are used to access the elements of an array, or a string of characters.
• SCALE: The index register's value can be multiplied by a scale factor, either 1, 2, 4
or 8. Scaled index mode is especially useful for accessing arrays or structures.
Intel® Quark Core—Architectural Overview
Combinations of these 4 components make up the 9 additional addressing modes.
There is no performance penalty for using any of these addressing combinations,
because the effective address calculation is pipelined with the execution of other
instructions. The one exception is the simultaneous use of Base and Index components,
which requires one additional clock.
As shown in Figure 3, the effective address (EA) of an operand is calculated according
to the following formula:
EA = Base Reg + (Index Reg * Scaling) + Displacement
Direct Mode: The operand’s offset is contained as part of the instruction as an 8-, 16or 32-bit displacement.
Example: INC Word PTR [500]
Register Indirect Mode: A BASE register contains the address of the operand.
Example: MOV [ECX], EDX
Based Mode: A BASE register's contents is added to a DISPLACEMENT to form the
operand's offset.
Example: MOV ECX, [EAX+24]
Index Mode: An INDEX register’s contents is added to a DISPLACEMENT to form the
operand's offset.
Example: ADD EAX, TABLE[ESI]
Scaled Index Mode: An INDEX register's contents is multiplied by a scaling factor
which is added to a DISPLACEMENT to form the operand's offset.
Example: IMUL EBX, TABLE[ESI*4],7
Based Index Mode: The contents of a BASE register is added to the contents of an
INDEX register to form the effective address of an operand.
Based Scaled Index Mode: The contents of an INDEX register is multiplied by a
SCALING factor and the result is added to the contents of a BASE register to obtain the
operand's offset.
Example: MOV ECX, [EDX*8] [EAX]
Figure 3.Addressing Mode Calculations
October 2013Developer’s Manual
Order Number: 329679-001US27
Based Index Mode with Displacement: The contents of an INDEX Register and a
BASE register's contents and a DISPLACEMENT are all summed together to form the
operand offset.
Example: ADD EDX, [ESI] [EBP+00FFFFF0H]
Based Scaled Index Mode with Displacement: The contents of an INDEX register
are multiplied by a SCALING factor, the result is added to the contents of a BASE
register and a DISPLACEMENT to form the operand’s offset.
Example: MOV EAX, LOCALTABLE[EDI*4] [EBP+80]
Intel® Quark SoC X1000 Core
Intel® Quark Core—Architectural Overview
3.5.4Differences Between 16- and 32-Bit Addresses
In order to provide software compatibility with older processors, the Intel® Quark SoC
X1000 Core can execute 16-bit instructions in Real and Protected Modes. The processor
determines the size of the instructions it is executing by examining the D bit in the CS
segment Descriptor. If the D bit is 0 then all operand lengths and effective addresses
are assumed to be 16 bits long. If the D bit is 1 then the default length for operands
and addresses is 32 bits. In Real Mode the default size for operands and addresses is
16-bits.
Regardless of the default precision of the operands or addresses, the Intel
X1000 Core is able to execute either 16- or 32-bit instructions. This is specified via the
use of override prefixes. Two prefixes, the Operand Size Prefix and the Address Length
Prefix, override the value of the D bit on an individual instruction basis. These prefixes
are automatically added by Intel assemblers.
Example: The Intel
programmer needs to access the EAX registers. The assembler code for this might be
MOV EAX, 32-bit MEMORY OP. The Macro Assembler automatically determines that an
Operand Size Prefix is needed and generates it.
Example: The D bit is 0, and the programmer wishes to use Scaled Index addressing
mode to access an array. The Address Length Prefix allows the use of MOV DX,
TABLE[ESI*2]. The assembler uses an Address Length Prefix because, with D=0, the
default addressing mode is 16-bits.
®
Quark SoC X1000 Core is executing in Real Mode and the
®
Quark SoC
Example: The D bit is 1, and the program wants to store a 16-bit quantity . The Operand
Length Prefix is used to specify only a 16-bit value; MOV MEM16, DX.
The OPERAND LENGTH and Address Length Prefixes can be applied separately or in
combination to any instruction. The Address Length Prefix does not allow addresses
over 64 Kbytes to be accessed in Real Mode. A memory address which exceeds FFFFH
will result in a General Protection Fault. An Address Length Prefix only allows the use of
the additional Intel
When executing 32-bit code, the Intel
®
Quark SoC X1000 Core addressing modes.
®
Quark SoC X1000 Core uses either 8-, or 32-bit
displacements, and any register can be used as base or index registers. When
executing 16-bit code, the displacements are either 8, or 16 bits, and the base and
index register are as listed in Table 4 below.
Table 4.BASE and INDEX Registers for 16- and 32-Bit Addresses
16-Bit Addressing32-Bit Addressing
BASE REGISTERBX,BPAny 32-bit GP Register
INDEX REGISTERSI,DIAny 32-bit GP Register Except ESP
SCALE FACTORnone1, 2, 4, 8
DISPLACEMENT0, 8, 16 bits0, 8, 32 bits
3.6Data Types
3.6.1Data Types
The Intel® Quark SoC X1000 Core can support a wide-variety of data types. In the
following descriptions, the processor consists of the base architecture registers.
The least significant bit (LSB) in a byte is bit 0, and the most significant bit is 7.
All signed data types assume 2's complement notation. The signed data types contain
two fields, a sign bit and a magnitude. The sign bit is the most significant bit (MSB).
The number is negative if the sign bit is 1. If the sign bit is 0, the number is positive.
The magnitude field consists of the remaining bits in the number. (Refer to Figure 5.)
October 2013Developer’s Manual
Order Number: 329679-001US29
Quark SoC X1000 Core only support 8-, 16- and 32-bit
integers. See Section 3.6.1.4 for details.
3.6.1.3BCD Data Types
The Intel® Quark SoC X1000 Core supports packed and unpacked binary coded decimal
(BCD) data types. A packed BCD data type contains two digits per byte, the lower digit
is in bits 3:0 and the upper digit in bits 7:4. An unpacked BCD data type contains 1
digit per byte stored in bits 3:0.
The Intel® Quark SoC X1000 Core supports 8-bit packed and unpacked BCD data
types. (Refer to Figure 5.)
3.6.1.4Floating-Point Data Types
In addition to the base registers, the Intel® Quark SoC X1000 Core on-chip floatingpoint unit consists of the floating-point registers. The floating-point unit data type
contain three fields: sign, significand, and exponent. The sign field is one bit and is the
MSB of the floating-point number. The number is negative if the sign bit is 1. If the sign
bit is 0, the number is positive. The significand gives the significant bits of the number.
The exponent field contains the power of 2 needed to scale the significand, see
Figure 5.
Intel® Quark Core—Architectural Overview
Only the FPU supports floating-point data types.
Single Precision Real:23-bit significand and 8-bit exponent. 32 bits total.
Double Precision Real:52-bit significand and 11-bit exponent. 64 bits total.
Extended Precision Real: 64-bit significand and 15-bit exponent. 80 bits total.
Floating-Point Unsigned Data Types
The on-chip FPU does not support unsigned data types. (Refer to Figure 5.)
Floating-Point Signed Data Types
The on-chip FPU only supports 16-, 32- and 64-bit integers.
Floating-Point BCD Data Types
The on-chip FPU only supports 80-bit packed BCD data types.
3.6.1.5String Data Types
A string data type is a contiguous sequence of bits, bytes, words or dwords. A string
may contain between 1 byte and 4 Gbytes. (Refer to Figure 6.)
String data types are only supported by the CPU section of the Intel
Core.
Byte String:Contiguous sequence of bytes.
Word String:Contiguous sequence of words.
Dword String:Contiguous sequence of dwords.
Bit String:A set of contiguous bits. In the Intel