µBGA* package, SSOP, and
TSOP (16 Mbit)
µBGA* package and SSOP (32 Mbit)
CC
PP
ADVANCE INFORMATION
n
Cross-Compatible Command Support
Intel Standard Command Set
Common Flash Interface (CFI)
Scaleable Command Set (SCS)
n
100,000 Block Erase Cycles
n
Enhanced Data Protection Features
Absolute Protection with VPP = GND
Flexible Block Locking
Block Erase/Program Lockout
during Power Transitions
n
Configurable x8 or x16 I/O
n
Automation Suspend Options
Program Suspend to Read
Block Erase Suspend to Program
Block Erase Suspend to Read
n
ETOX™ V Nonvolatile Flash
Technology
Intel’s Word-Wide FlashFile™ m emory fam ily prov ides high-dens ity, low-cost , non-volat ile, read/ write st orage
solutions for a wide range of applications. The Word-Wide FlashFile memories are available at various
densities in the same pac kage type. Thei r symmet rically-bloc ked architec ture, flex ible voltage, and ext ended
cycling provide highly flexible components suitable for resident flash arrays, SIMMs, and memory cards.
Enhanced suspend capabilities provide an ideal soluti on for code or data storage applications. For secure
code storage applications, such as networking, where code is either directly executed out of flash or
downloaded to DRAM, the Word-Wide FlashFile memories offer three levels of prot ect ion: absolut e protec ti on
with V
alternatives give designers ultimate control of their code security needs.
This family of product s is manufactured on Intel’s 0.4 µm ETOX™ V process technology. It c omes in the
industry-standard 56-lead SSOP and µBGA packages. In addition, the 16-Mb device is available in the
industry-standard 56-lead TSOP package.
at GND, selective block locking, and program/erase lockout during power transitions. These
PP
June 1997Order Number: 290608-001
Information in this document is provided in connection with Intel products. No license, express 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, relating 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. Intel products are not intended for use in medical, life
saving, or life sustaining applications.
Intel may make changes to specifications and product descriptions at any time, without notice.
The 28F160S3 and 28F320S3 may contain design defects or errors known as errata. 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 ordering number and are referenced in this document, or other Intel literature, may be
obtained from:
Intel Corporation
P.O. Box 7641
Mt. Prospect, IL 60056-7641
This datasheet contains 16- and 32-Mbit WordWide FlashFile
28F320S3) specifications. Section 1 provides a
flash memory overview. Sections 2, 3, 4, and 5
describe the memory organizat ion and f unctional ity.
Section 6 covers electrical specifications for
extended temperature product offerings.
TM
memory (28F160S3 and
1.1New Features
The Word-Wide FlashFile memory family maintains
basic compatibility with Intel’s 28F016SA and
28F016SV. Key enhancements include:
•Common Flash Interface (CFI) Support
• Scaleable Command Set (SCS) Support
• Low Voltage Technology
•Enhanced Suspend Capabilities
They share a compatible Status Register, basic
software commands, and pinout . These similarities
enable a clean migration from the 28F016SA or
28F016SV. When upgrading, it is important to note
the following differences:
•Because of new feature and density options,
the devices have different manufacturer and
device identifier codes. This allows for soft ware
optimization.
•New software commands.
•To take advantage of low voltage on the
28F160S3 and 28F320S3, allow V
connection to VCC. The 28F160S3 and
28F320S3 do not support a 12V V
option.
PP
PP
1.2Product Overview
The Word-Wide FlashFile memory family provides
density upgrades with pinout compatibility for the
16- and 32-Mbit densities. They are highperformance memories arranged as 1 Mword and
2 Mwords of 16 bits or 2 Mbyte and 4 Mbyte of
8 bits. This data is grouped in thirty-two and s ixtyfour 64-Kbyte blocks that can be erased, locked
and unlocked in-system. Figure 1 shows the block
diagram, and Figure 5 illustrates the memory
organization.
This family of product s are optimized for fast factory
programming and low power designs. Specifically
designed for 3V systems, the 28F160S3 and
28F320S3 support read operations at 2.7V–3.6V
Vcc with block erase and program operations at
2.7V–3.6V and 5V V
performance is achieved through highly-optimized
write buffers. A 5V V
faster factory programm ing. For a si mple l ow power
design, V
Additionally, the dedic ated V
data protection when V
Internal V
configures the device for optimized write
operations.
A Common Flash Interface (CFI) permits OEMspecified software algori thms to be used for entire
families of devices. This allows device-independent,
JEDEC ID-independent, and forward- and
backward-compatible software support for the
specified flash device families. Flash vendors can
standardize their existing interfaces for long-term
compatibility.
Scaleable Command Set (SCS) allows a single,
simple software driver in all host systems to work
with all SCS-compliant flash memory devices,
independent of system-level packaging (e.g.,
memory card, SIMM, or direc t-to-board placement).
Additionally, SCS provides the highest
system/device data transfer rates and minimizes
device and system-level implementation costs.
A Command User Interface (CUI) serves as the
interface between the system processor and
internal device operation. A valid command
sequence written to the CUI initiates device
automation. An internal Write State M ac hi ne (WSM)
automatically executes the algorithms and timings
necessary for block erase, program, and lock-bit
configuration operations.
A block erase operation erases one of the device’s
64-Kbyte blocks typically within t
independent of other blocks. Each block can be
independently erased 100,000 times. Block erase
suspend mode allows system software to suspend
block erase to read or write data from any other
block.
Data is programmed in byte, word or page
increments. Program suspend mode enables the
system to read data or execute code from any other
flash memory array location.
and VPP can be tied to 2.7V.
CC
detection circuitry automatically
PP
. High programming
PP
option is available for ev en
PP
pin gives complet e
PP
≤ V
PPLK
.
WHQV2/EHQV2
PP
ADVANCE INFORMATION
5
28F160S3, 28F320S3E
The device incorporates two Write Buffers of 32
bytes (16 words) to allow optimum-performance
data programming. This feature can improve
system program performance by up to four times
over non-buffer programming.
Individual block loc king us es a c ombi nation of bl ock
lock-bits to lock and unlock blocks. Block lock-bits
gate block erase, full chi p erase, program and write
to buffer operations. Lock-bit configuration
operations (Set Block Lock-Bit and Clear Block
Lock-Bits commands) set and clear lock-bits.
The Status Register and the STS pin in RY/BY#
mode indicate whether or not the device is busy
executing an operation or ready for a new
command. Polling the Status Register, system
software retrieves WSM f eedback. STS in RY/BY#
mode gives an additional indicator of WSM ac tivity
by providing a hardware status signal. Like the
Status Register, RY/BY#-low indicates that the
WSM is performing a block erase, program , or l ock bit operation. RY/BY#-high indicat es that the WSM
is ready for a new command, block erase is
suspended (and program is inactive), program is
suspended, or the device is in deep power-down
mode.
The Automatic Power Savings (APS) feature
substantially reduces active current when the
device is in static mode (addresses not switching).
The BYTE# pin allows either x 8 or x16 read/writes
to the device. BYTE# at logic low selects 8-bit
mode with address A
byte and high byte. BYTE# at logic high enables
16-bit operation with address A
lowest order address. Addres s A
bit mode.
When one of the CE
pins are at V
CC
selecting between the low
0
becoming the
1
is not used in 16-
0
# pins (CE0#, CE1#) and RP#
X
, the component enters a CMOS
standby mode. Driving RP# t o GND enables a deep
power-down mode which significantly reduces
power consumption, provides write protection,
resets the device, and cl ears the St atus Regis ter. A
reset time (t
) is required from RP# switching
PHQV
high until outputs are valid. Likewise, the device
has a wake time (t
) from RP#-high until writes
PHEL
to the CUI are recognized.
1.3Pinout and Pin Description
The 16-Mbit device is available in the 56-lead
TSOP, 56-lead SSOP and µBGA packages. The
32- Mb device is available i n the 56-lead S SOP and
µBGA packages. The pinouts are shown in Figures
2, 3 and 4.
DQ0 - DQ
15
16-Mbit: A0- A
32-Mbit: A
0 - A21
20
Input Buffer
Address
Latch
Address
Counter
Y-Decoder
X-Decoder
Output Buffer
Output
Multiplexer
Comparator
16-Mbit: Thirty-two
32-Mbit: Sixty-four
Query
Identifier
Register
Status
Register
Data
Y-Gating
64-Kbyte Blocks
Input Buffer
Data
Register
Multiplexer
V
STS
CC
BYTE#
CE#
WE#
OE#
RP#
WP#
V
PP
V
CC
GND
I/O Logic
Command
User
Interface
Write Buffer
Write State
Machine
Program/Erase
Voltage Switch
Figure 1. Block Diagram
6
ADVANCE INFORMATION
E28F160S3, 28F320S3
Table 1. Pin Descriptions
SymTypeName and Function
A0–A
DQ
–
DQ
15
CE0#,
CE
#
1
RP#INPUTRESET/DEEP POWER-DOWN: When driven low, RP# inhibits write operations
OE#INPUTOUTPUT ENABLE: Gates the device’s outputs during a read cycle.
WE#INPUTWRITE ENABLE: Controls writes to the CUI and array blocks. Addresses and data
STSOPEN
WP#INPUTWRITE PROTECT: Master control for block locking. When VIL, locked blocks
BYTE#INPUTBYTE ENABLE: Configures x8 mode (low) or x16 mode (high).
V
PP
V
CC
GNDSUPPLY GROUND: Do not float any ground pins.
NCNO CONNECT: Lead is not internally connected; it may be driven or floated.
INPUTADDRESS INPUTS: Address inputs for read and write operations are internally
21
INPUT/
OUTPUT
INPUTCHIP ENABLE: Activates the device’s control logic, input buffers, decoders, and
DRAIN
OUTPUT
SUPPLY BLOCK ERASE, PROGRAM, LOCK-BIT CONFIGURATION POWER SUPPLY:
SUPPLY DEVICE POWER SUPPLY: Do not float any power pins. Do not attempt block
latched during a write cycle. A
In x16 mode, A
DATA INPUTS/OUTPUTS: Inputs data and commands during CUI write cycles;
outputs data during memory array, Status Register, query and identifier code read
cycles. Data pins float to high-impedance when the chip is deselected or outputs
are disabled. Data is internally latched during a write cycle.
sense amplifiers. With CE0# or CE1# high, the device is deselected and power
consumption reduces to standby levels. Both CE
the device. Device selection occurs with the latter falling edge of CE
first rising edge of CE
which provides data protection during system power transitions, puts the device in
deep power-down mode, and resets internal automation. RP#-high enables normal
operation. Exit from deep power-down sets the device to read array mode.
are latched on the rising edge of the WE# pulse.
STATUS: Indicates the status of the internal state machine. When configured in
level mode (default), it acts as a RY/BY# pin. For this and alternate configurations
of the STATUS pin, see the Configuration command. Tie STS to V
resistor.
cannot be erased or programmed, and block lock-bits cannot be set or cleared.
Necessary voltage to perform block erase, program, and lock-bit configuration
operations. Do not float any power pins.
erase, program, or block-lock configuration with invalid V
is not used; input buffer is off.
0
16-Mbit → A
0–A20
# or CE1# disables the device.
0
selects high or low byte when operating in x8 mode.
3. More information on µBGA* packages is available by contacting your Intel/Distribution sales office.
This is the view of the package as surface mounted on
the board. Note that the signal s are mirror imaged.
GNDA10VPPCE0A14VCC
NCNCBYTE#DQ7WP#WE#
DQ0DQ9DQ2DQ11DQ4DQ13DQ14 STS
VCCDQ10 GNDVCCDQ5GND
Figure 4. µBGA* Package Pinout
A4A7A9A11A12A15A17A19
A5A6A8RP#A13A16A21A20
A2A1A3A18CE1NC
A0DQ8DQ1DQ3DQ12DQ6DQ15OE#
2.0PRINCIPLES OF OPERATION
The word-wide memories include an on-chip
Write State Machine (WSM) to manage block
erase, program, and lock-bit configuration
functions. It allows for: 100% TTL-level control
inputs, fixed power suppli es duri ng block erasure,
programming, lock-bit c onfiguration, and minimal
processor overhead with RAM-like interface
timings.
After initial device power-up or return from deep
power-down mode (see Bus Operations), the
10
device defaults to read array mode. Manipul ation
of external memory control pins all ow array read,
standby, and output disable operations.
Read Array, Status Regis ter, query , and identif ier
codes can be accessed through the CUI
independent of the V
programming voltage on V
voltage. Proper
PP
enables successful
PP
block erasure, program, and lock-bit
configuration. All functions associated with
altering memory contents—bloc k erase, program,
lock-bit configuration—are acces sed via the CUI
and verified through the Status Register.
ADVANCE INFORMATION
E28F160S3, 28F320S3
Commands are written using standard microprocessor write timings. The CUI c ontents serve
as input to the WSM that controls the block
erase, programming, and lock-bit configuration.
The internal algorithms are regulated by the
WSM, including pulse repetition, internal
verification, and margining of data. Addresses
and data are internally latched during write
cycles. Writing the appropriate command outputs
array data, identifier codes, or Status Register
data.
Interface software that initiates and polls
progress of block erase, program ming, and lockbit configuration can be stored in any bl ock. This
code is copied to and executed from system
RAM during flash memory updates. After
successful com pletion, reads are again possible
via the Read Array command. Block erase
suspend allows system software to suspend a
block erase to read or write dat a from any other
block. Program suspend all ows system software
to suspend a program to read data from any
other flash memory array location.
2.1Data Protection
Depending on the application, the system
designer may choose to make the V
supply switchable or hardwired to V
device supports either design practice, and
encourages optimization of the processormemory interface.
When V
altered. When high voltage is appli ed to V
two-step block erase, program, or lock-bit
configuration command sequences provide
protection from unwanted operations. All write
functions are disabled when V
the write lockout v oltage V
V
IL
provides additional protection from inadvertent
code or data alteration.
≤ V
PP
. The device’s block locking capability
, memory contents cannot be
PPLK
voltage is below
CC
or when RP# is at
LKO
PP
PPH1/2
power
. The
, the
PP
ADVANCE INFORMATION
Figure 5. Memory Map
11
28F160S3, 28F320S3E
3.0BUS OPERATION
The local CPU reads and writes fl ash m emory i nsystem. All bus cycles to or from the flash
memory conform to standard mic roprocessor bus
cycles.
3.1Read
Block information, query information, identifier
codes and Status Registers can be read
independent of the V
voltage.
PP
The first task is to place the device into the
desired read mode by writing the appropriate
read-mode command (Read Array, Query, Read
Identifier Codes, or Read Stat us Register) to t he
CUI. Upon initial device power-up or after exit
from deep power-down mode, the device
automatically reset s to read array mode. Control
pins dictate the data flow in and out of the
component. CE
active to obtain data at the outputs. CE
CE
# are the device selection controls, and,
1
#, CE1# and OE# must be driven
0
# and
0
when both are active, enable the selected
memory device. OE# is the data output (DQ
DQ
) control: When active it drives the selected
15
0
memory data onto the I/O bus. WE# must be at
V
and RP# must be at VIH. Figure 17 illustrates
IH
a read cycle.
3.2Output Disable
With OE# at a logic-high level (VIH), the device
outputs are disabled. Output pins DQ
–DQ15 are
0
placed in a high-impedance state.
3.3Standby
CE0# or CE1# at a logic-high level (VIH) places
the device in standby mode, substantially
reducing device power consumption. DQ
(or DQ0– DQ7 in x8 mode) outputs are placed in
a high-impedance state independent of OE#. If
deselected during block erase, programming, or
lock-bit configuration, the device continues
functioning and consuming act ive power until the
operation completes.
–DQ
0
3.4Deep Power-Down
RP# at VIL initiates the deep power-down mode.
In read mode, RP#-low deselects the memory,
places output drivers in a high-impedance state,
and turns off all internal circuits. RP# must be
held low for time t
PLPH
. Time t
is required
PHQV
after return from power-down until initial memory
access outputs are valid. After this wake-up
interval, normal operation is restored. The CUI
resets to read array mode, and the Status
Register is set to 80H.
During block erase, programming, or lock-bit
configuration modes, RP#-low will abort the
operation. STS in RY/BY# mode remains low
until the reset operation is complete. Memory
contents being altered are no longer valid; the
data may be partially corrupted after
programming or partially altered af ter an erase or
lock-bit configuration. Time t
RP# goes to logic-high (V
command can be written.
is required after
PHWL
) before another
IH
It is important in any automated system to assert
–
RP# during system reset. When the system
comes out of reset, it expects to read from the
flash memory. Automated flash memories
provide status informat ion when access ed during
block erase, programming, or lock-bit
configuration modes. I f a CPU reset occurs with
no flash memory reset , proper CPU initialization
may not occur because the f las h memory may be
providing status inform ati on inst ead of array data.
Intel’s Flash memories allow proper CPU
initialization following a system reset through the
use of the RP# input. In t his application, RP# is
controlled by the same RESET# signal that
resets the system CPU.
3.5Read Query Operation
15
The read query operation outputs block status,
Common Flash Interface (CFI) ID string, system
interface, device geometry, and Intel-specific
extended query information.
12
ADVANCE INFORMATION
E28F160S3, 28F320S3
3.6Read Identifier Codes
Operation
The read-identifier codes operation outputs the
manufacturer code, devic e code, and block lock
configuration codes for each block configuration
(see Figure 6). Using the manufacturer and
device codes, the system software can
automatically match the device with its proper
algorithms. The block-lock configuration codes
identify each block’s lock-bit setting.
3.7Write
Writing commands to the CUI enables reading of
device data, query, identifier codes, inspection
and clearing of the Status Register. Additionally,
when V
and lock-bit configuration can also be performed.
The Block Erase command requires appropriate
command data and an address within the block
to be erased. The Byte/Word Write command
requires the command and address of the
location to be written. Set Block Lock-Bit
commands require the command and address
within the block to be locked. The Clear Block
Lock-Bits command requires the command and
an address within the device.
The CUI does not occupy an addressable
memory location. I t is written when WE#, CE
and CE
and data needed to execute a command are
latched on the rising edge of WE# or CE
(CE
Standard microprocessor writ e timings are used.
Figure 18 illustrates a write operation.
= V
PP
# are active and OE# = VIH. The address
1
#, CE1#), whichever goes high first.
0
, block erasure, programming,
PPH1/2
0
X
4.0COMMAND DEFINITIONS
VPP voltage ≤ V
from the Status Register, identifier codes, or
memory blocks. Placing V
successful bloc k erase, programming, and lockbit configuration operations.
enables read operations
PPLK
on VPP enables
PPH1/2
#,
#
Figure 6. Device Identifier Code Memory Map
ADVANCE INFORMATION
Device operations are selec ted by writ ing spec ifi c
commands into the CUI. and Table 3 define
these commands.
13
28F160S3, 28F320S3E
Table 2. Bus Operations
ModeNotes RP#CE0#CE1# OE#
Read1,2V
Output DisableV
StandbyV
Reset/Power-
10V
Down Mode
Read Identifier
4VIHV
Codes
Read Query5V
Write3,6,7V
V
IH
IL
V
IH
IL
V
IH
IL
V
IH
V
IH
XXXXXXHigh Z High Z
IL
IL
V
IH
IL
V
IH
IL
V
IL
V
IL
V
IH
V
IL
V
IH
V
IL
V
IL
V
IL
(11)
V
IL
V
IH
XXXXHigh ZX
V
IL
V
IL
V
IH
NOTES:
1. Refer to Table 19. When V
2. X can be V
or VIH for control and address input pins and V
IL
≤ V
PP
, memory contents can be read, but not altered.
PPLK
PPLK
voltages.
3. STS in level RY/BY# mode (default) is V
configuration algorithms. It is V
OH
when the WSM is executing internal block erase, programming, or lock-bit
OL
when the WSM is not busy, in block erase suspend mode (with programming inactive),
program suspend mode, or deep power-down mode.
4. See Section 4.3 for read identifier code data.
5. See Section 4.2 for read query data.
6. Command writes involving block erase, write, or lock-bit configuration are reliably executed when V
V
= V
CC
7. Refer to Table 3 for valid D
8. DQ refers to DQ
9. High Z will be V
(see Section 6.2).
CC1/2
if BYTE# is low and DQ
0–7
with an external pull-up resistor.
OH
during a write operation.
IN
if BYTE# is high.
0–15
10. RP# at GND ± 0.2V ensures the lowest deep power-down current.
11. OE# = V
and WE# = VIL concurrently is an undefined state and should not be attempted.
IL
(11)
WE#
V
IH
V
IH
V
IH
AddressV
PP
XXD
XXHigh ZX
See
XD
Figure 6
VIHSee Table 6XD
or V
V
PPH1/2
IL
XV
PPH1/2
for VPP. See Table 19, for V
(8)
DQ
OUT
OUT
OUT
D
IN
and V
PPLK
= V
PP
PPH1/2
and
STS
High Z
High Z
PPH1/2
(3)
X
X
(9)
(9)
(9)
14
ADVANCE INFORMATION
E28F160S3, 28F320S3
Table 3. Word-Wide FlashFile™ Memory Command Set Definitions
CommandScaleable
Read ArraySCS/BCS1WriteXFFH
Read Identifier CodesSCS/BCS≥25WriteX90HReadIAID
Read QuerySCS≥ 2WriteX98HReadQAQD
Read Status RegisterSCS/BCS2WriteX70HReadXSRD
Clear Status RegisterSCS/BCS1WriteX50H
Write to BufferSCS> 28, 9, 10WriteBAE8HWriteBAN
Word/Byte ProgramSCS/BCS26,7WriteX40H
Program Resume
STS pin ConfigurationSCS2WriteXB8HWriteXCC
Set Block Lock-BitSCS211WriteX60HWriteBA01H
Clear Block Lock-BitsSCS212WriteX60HWriteXD0H
Full Chip EraseSCS210WriteX30HWriteXD0H
or Basic
Command
Set
SCS/BCS16WriteXB0H
SCS/BCS16WriteXD0H
(14)
Bus
Cycles
Req'd
NotesFirst Bus CycleSecond Bus Cycle
Oper
(1)
Addr
(2)
Data
10H
(3,4)
or
(13)
(1)
Oper
WritePAPD
Addr
(2)
Data
(3,4)
ADVANCE INFORMATION
15
28F160S3, 28F320S3E
NOTES:
1. Bus operations are defined in Table 2.
2. X = Any valid address within the device.
BA = Address within the block being erased or locked.
IA = Identifier Code Address: see Table 12.
QA = Query database Address.
PA = Address of memory location to be programmed.
3. ID = Data read from Query database.
SRD = Data read from Status Register. See Table 15 for a description of the Status Register bits.
PD = Data to be programmed at location PA. Data is latched on the rising edge of WE#.
CC = Configuration Code. (See Table 14.)
4. The upper byte of the data bus (DQ
5. Following the Read Identifier Codes command, read operations access manufacturer, device, and block-lock codes. See
Section 4.3 for read identifier code data.
6. If a block is locked (i.e., the block’s lock-bit is set to 0), WP# must be at V
suspend operations. Attempts to issue a block erase, program and suspend operation to a locked block while WP# is V
will fail.
7. Either 40H or 10H are recognized by the WSM as the byte/word program setup.
8. After the Write to Buffer command is issued, check the XSR to make sure a Write Buffer is available.
9. N = byte/word count argument such that the number of bytes/words to be written to the input buffer = N + 1. N = 0 is 1
byte/word length, and so on. Write to Buffer is a multi-cycle operation, where a byte/word count of N + 1 is written to the
correct memory address (WA) with the proper data (WD). The Confirm command (D0h) is expected after exactly N + 1 write
cycles; any other command at that point in the sequence aborts the buffered write. Writing a byte/word count outside the
buffer boundary causes unexpected results and should be avoided.
10. The write to buffer, block erase, or full chip erase operation does not begin until a Confirm command (D0h) is issued.
Confirm also reactivates suspended operations.
11. A block lock-bit can be set only while WP# is V
12. WP# must be at V
to clear block lock-bits. The clear block lock-bits operation simultaneously clears all block lock-bits.
IH
13. Commands other than those shown above are reserved for future use and should not be used.
14. The Basic Command Set (BCS) is the same as the 28F008SA Command Set or Intel Standard Command Set. The
Scaleable Command Set (SCS) is also referred to as the Intel Extended Command Set.
) during command writes is a “Don’t Care” in x16 operation.
8–15
in order to perform block erase, program and
IH
.
IH
IL
16
ADVANCE INFORMATION
Loading...
+ 36 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.