PSD4135G2V-C-70UI ,Flash In-System-Programmable Peripherals for 16-Bit MCUsAbsolute Maximum Ratings ....61Operating Range...61Recommended Operating Conditions.......61AC/DC P ..
PSD413A1-C-70J ,Low Cost Field Programmable Microcontroller PeripheralsTable of Contents1 Introduction ..12 Key
PSD4235G2-70U ,Flash In-System Programmable (ISP) Peripherals for 16-bit MCUs (5V Supply)FEATURES SUMMARY■ DUAL BANK FLASH MEMORIES Figure 1. Package– 4 Mbit of Primary Flash Memory (8 uni ..
PSD4235G290UI ,Flash In-System Programmable (ISP) Peripherals for 16-bit MCUs (5V Supply)Features Summary . 1Figure 1. Package . . . . . . . 1Summary Description . . . ..
PSD4235G290UI ,Flash In-System Programmable (ISP) Peripherals for 16-bit MCUs (5V Supply)Block Diagram . . . . . 15PSD Architectural Overview 16Memory . . . . . . 16PLDs ..
PSD4235G2V-90U ,FLASH IN-SYSTEM PROGRAMMABLE (ISP) PERIPHERALS FOR 16-BIT MCUS (3.3V SUPPLY)TABLE OF CONTENTSSummary Description . . . . . . 5In-System Programming (ISP) via JTAG . ..
QK006L5 , Triacs (0.8 A to 35 A)
QK006LH4 , Alternistor Triacs (6 A to 40 A)
QK006N5 , Triacs (0.8 A to 35 A)
QK006NH4 , Alternistor Triacs (6 A to 40 A)
QK006R5 , Triacs (0.8 A to 35 A)
QK006RH4 , Alternistor Triacs (6 A to 40 A)
PSD4135G2V-12UI-PSD4135G2V-C-70UI
Flash In-System-Programmable Peripherals for 16-Bit MCUs
1/3
PRELIMINARY DATAJanuary 2002
PSD4135G2Flash In-System-Programmable Peripherals
for 16-Bit MCUs
FEATURES SUMMARY 5 V±10% Single Supply Voltage: Up to 4 Mbit of Primary Flash Memory (8
uniform sectors) 256Kbit Secondary Flash Memory (4 uniform
sectors) Up to 64 Kbit SRAM Over 3,000 Gates of PLD: DPLD and CPLD 52 Reconfigurable I/O ports Enhanced JTAG Serial Port Programmable power management High Endurance: 100,000 Erase/Write Cycles of Flash Memory 1,000 Erase/Write Cycles of PLD
Figure 1. Packages
PSD4000 Series
PSD4135G2
Flash In-System-Programmable Peripherals for 16-Bit MCUs
Table of ContentsIntroduction........................................................................................................................................................................................1
In-System Programming (ISP) JTAG .......................................................................................................................................2
In-Application re-Programming (IAP) .......................................................................................................................................2
Key Features......................................................................................................................................................................................3
PSD4000 Family................................................................................................................................................................................3
Block Diagram....................................................................................................................................................................................4
Architectural Overview.......................................................................................................................................................................5
Memory ....................................................................................................................................................................................5
PLDs.........................................................................................................................................................................................5
I/O Ports ...................................................................................................................................................................................5
Microcontroller Bus Interface....................................................................................................................................................5
ISP via JTAG Port....................................................................................................................................................................6
In-System Programming (ISP) .................................................................................................................................................6
In-Application re-Programming (IAP) .......................................................................................................................................6
Page Register...........................................................................................................................................................................6
Power Management Unit..........................................................................................................................................................6
Development System.........................................................................................................................................................................7
Pin Descriptions.................................................................................................................................................................................8
Register Description and Address Offset.........................................................................................................................................11
Register Bit Definition ......................................................................................................................................................................12
Functional Blocks.............................................................................................................................................................................15
Memory Blocks.......................................................................................................................................................................15
Main Flash and Secondary Flash Memory Description ...................................................................................................15
SRAM...............................................................................................................................................................................26
Memory Select Signals....................................................................................................................................................26
Page Register..................................................................................................................................................................29
Memory ID Registers .......................................................................................................................................................30
PLDs.......................................................................................................................................................................................31
Decode PLD (DPLD)........................................................................................................................................................33
General Purpose PLD (GPLD).........................................................................................................................................33
Microcontroller Bus Interface..................................................................................................................................................36
Interface to a Multiplexed Bus..........................................................................................................................................36
Interface to a Non-multiplexed Bus..................................................................................................................................36
Data Byte Enable Reference ...........................................................................................................................................38
Microcontroller Interface Examples..................................................................................................................................39
I/O Ports .................................................................................................................................................................................44
General Port Architecture ................................................................................................................................................44
Port Operating Modes......................................................................................................................................................44
Port Configuration Registers (PCRs)...............................................................................................................................48
Port Data Registers..........................................................................................................................................................49
Ports A, B and C – Functionality and Structure ...............................................................................................................50
Port D – Functionality and Structure................................................................................................................................51
Port E – Functionality and Structure................................................................................................................................51
Port F – Functionality and Structure ................................................................................................................................52
Port G – Functionality and Structure................................................................................................................................52
PSD4000 Series
PSD4135G2
Flash In-System-Programmable Peripherals for 16-Bit MCUs
Table of ContentsPower Management ...............................................................................................................................................................53
Automatic Power Down (APD) Unit and Power Down Mode ...........................................................................................53
Other Power Savings Options..........................................................................................................................................57
Reset and Power On Requirement..................................................................................................................................58
Programming In-Circuit using the JTAG-ISP Interface...........................................................................................................59
Standard JTAG Signals ...................................................................................................................................................60
JTAG Extensions .............................................................................................................................................................60
Security and Flash Memories Protection .........................................................................................................................60
Absolute Maximum Ratings .............................................................................................................................................................61
Operating Range..............................................................................................................................................................................61
Recommended Operating Conditions..............................................................................................................................................61
AC/DC Parameters ..........................................................................................................................................................................62
Example of Typical Power Calculation at Vcc = 5..0 V...........................................................................................................63
Example of Typical Power Calculation at Vcc = 5..0 V in Turbo Off Mode.............................................................................64
DC Characteristics (5 V ± 10% versions).........................................................................................................................................65
Microcontroller Interface – AC/DC Parameters (5 V ± 10% versions) .............................................................................................67
DC Characteristics (3.0 V to 3.6 V versions) ...................................................................................................................................71
Microcontroller Interface – AC/DC Parameters (3.0 V to 3.6 V versions) .......................................................................................73
Timing Diagrams..............................................................................................................................................................................77
Pin Capacitance...............................................................................................................................................................................81
AC Testing Input/Output Waveforms ...............................................................................................................................................81
AC Testing Load Circuit ...................................................................................................................................................................81
Programming ...................................................................................................................................................................................81
Pin Assignments ..............................................................................................................................................................................82
Package Information........................................................................................................................................................................83
Selector Guide .................................................................................................................................................................................85
Part Number Construction ...............................................................................................................................................................86
Ordering Information........................................................................................................................................................................86
Document Revisions........................................................................................................................................................................87
Worldwide Sales, Service and Technical Support ...........................................................................................................................88
1.0
Introduction
Preliminary Information
PSD4000 Series
PSD4135G2
Configurable Memory System on a Chip
for 16-Bit MicrocontrollersThe PSD4000 series of Programmable Microcontroller (MCU) Peripherals brings
In-System-Programmability (ISP) to Flash memory and programmable logic. The result is a
simple and flexible solution for embedded designs. PSD4000 devices combine many of the
peripheral functions found in MCU based applications: 4 Mbit of Flash memory A secondary Flash memory for boot or data Over 3,000 gates of Flash programmable logic 64 Kbit SRAM Reconfigurable I/O ports Programmable power management.
PSD4000 Series Preliminary Information
Introduction
(Cont.)The PSD4135G2 device offers two methods to program PSD Flash memory while the PSD
is soldered to a circuit board.
In-System Programming (ISP) via JTAGAn IEEE 1149.1 compliant JTAG-ISP interface is included on the PSD enabling the
entire device (both flash memories, the PLD, and all configuration) to be rapidly
programmed while soldered to the circuit board. This requires no MCU participation,
which means the PSD can be programmed anytime, even while completely blank.
The innovative JTAG interface to flash memories is an industry first, solving key
problems faced by designers and manufacturing houses, such as:
First time programming – How do I get firmware into the flash the very first timeJTAG is the answer, program the PSD while blank with no MCU involvement.
Inventory build-up of pre-programmed devices – How do I maintain an accuratecount of pre-programmed flash memory and PLD devices based on customer
demand How many and what version JTAG is the answer, build your hardware
with blank PSDs soldered directly to the board and then custom program just before
they are shipped to customer. No more labels on chips and no more wasted
inventory.
Expensive sockets – How do I eliminate the need for expensive and unreliable sockets JTAG is the answer. Solder the PSD directly to the circuit board. Program
first time and subsequent times with JTAG. No need to handle devices and bend the
fragile leads.
In-Application re-Programming (IAP)Two independent flash memory arrays are included so the MCU can execute code
from one memory while erasing and programming the other. Robust product firmware
updates in the field are possible over any communication channel (CAN, Ethernet,
UART, J1850, etc) using this unique architecture. Designers are relieved of these
problems:
Simultaneous read and write to flash memory – How can the MCU program the same memory from which it is executing code It cannot. The PSD allows the MCU
to operate the two flash memories concurrently, reading code from one while erasing
and programming the other during IAP.
Complex memory mapping – How can I map these two memories efficiently A Programmable Decode PLD is embedded in the PSD. The concurrent PSD
memories can be mapped anywhere in MCU address space, segment by segment
with extremely high address resolution. As an option, the secondary flash memory
can be swapped out of the system memory map when IAP is complete. A built-in
page register breaks the MCU address limit.
Separate program and data space – How can I write to flash memory while it resides in “program” space during field firmware updates, my 80C51XA won’t allow it
The flash PSD provides means to “reclassify” flash memory as “data” space during
IAP, then back to “program” space when complete.
PSDsoft – ST’s software development tool – guides you through the design process step-
by-step making it possible to complete an embedded MCU design
capable of ISP/IAP in just hours. Select your MCU and PSDsoft will take you through
the remainder of the design with point and click entry, covering...PSD selection, pin
definitions, programmable logic inputs and outputs, MCU memory map definition, ANSI C
code generation for your MCU, and merging your MCU firmware with the PSD design.
When complete, two different device programmers are supported directly from PSDsoft –
FlashLINK (JTAG) and PSDpro.
The PSD4135G2 is available in an 80-pin TQFP package.
Preliminary Information PSD4000 Series A simple interface to 16-bit microcontrollers that use either multiplexed or
non-multiplexed busses. The bus interface logic uses the control signals generated by
the microcontroller automatically when the address is decoded and a read or write is
performed. A partial list of the MCU families supported include: Intel 80196, 80296, 80186, and 80386EX Motorola 68HC16, 68HC12, 683XX, and MC2001 Philips 80C51XA Infineon C16X devices Hitachi H8 4 Mbit Flash memory. This is the main Flash memory. It is divided into eight
equal-sized blocks that can be accessed with user-specified addresses. Internal secondary 256 Kbit Flash boot memory. It is divided into four equal-sized
blocks that can be accessed with user-specified addresses. This secondary memory
brings the ability to execute code and update the main Flash concurrently. 64 Kbit SRAM. The SRAM’s contents can be protected from a power failure by
connecting an external battery. General Purpose PLD (GPLD) with 24 outputs. The GPLD may be used to implement
external chip selects or combinatorial logic function. Decode PLD (DPLD) that decodes address for selection of internal memory blocks. 52 individually configurable I/O port pins that can be used for the following functions: MCU I/Os PLD I/Os Latched MCU address output Special function I/Os. I/O ports may be configured as open-drain outputs. Standby current as low as 50 µA for 5 V devices. Built-in JTAG compliant serial port allows full-chip In-System Programmability (ISP).
With it, you can program a blank device or reprogram a device in the factory or the field. Internal page register that can be used to expand the microcontroller address space
by a factor of 256. Internal programmable Power Management Unit (PMU) that supports a low power
mode called Power Down Mode. The PMU can automatically detect a lack of
microcontroller activity and put the PSD4000 into Power Down Mode. Erase/Write cycles: Flash memory – 100,000 minimum PLD – 1,000 minimum 15 year data retention
Key Features
3.0 PSD4000
Series
Table 1. PSD4000 Product Matrix*See PSD4235G2 Data Sheet.
PSD4000 Series Preliminary Information
Figure 1. PSD4000 Block Diagram
Preliminary Information PSD4000 SeriesPSD4000 devices contain several major functional blocks. Figure 1 on page 3 shows the
architecture of the PSD4000 device family. The functions of each block are described
briefly in the following sections. Many of the blocks perform multiple functions and are user
configurable.
4.1 MemoryThe PSD4000 contains the following memories: 4 Mbit Flash A secondary 256 Kbit Flash memory for boot or data 64 Kbit SRAM.
Each of the memories is briefly discussed in the following paragraphs. A more detailed
discussion can be found in section 9.
The 4 Mbit Flash is the main memory of the PSD4000. It is divided into eight equally-sized
sectors that are individually selectable.
The 256 Kbit secondary Flash memory is divided into four equally-sized sectors. Each
sector is individually selectable.
The 64 Kbit SRAM is intended for use as a scratchpad memory or as an extension to the
microcontroller SRAM. If an external battery is connected to the PSD4000’s Vstby pin, data
will be retained in the event of a power failure.
Each block of memory can be located in a different address space as defined by the user.
The access times for all memory types includes the address latching and DPLD decoding
time.
4.2 PLDsThe device contains two PLD blocks, each optimized for a different function, as shown in
Table 2. The functional partitioning of the PLDs reduces power consumption, optimizes
cost/performance, and eases design entry.
The Decode PLD (DPLD) is used to decode addresses and generate chip selects for
the PSD4000 internal memory and registers. The General Purpose PLD (GPLD) can
implement user-defined external chip selects and logic functions. The PLDs receive their
inputs from the PLD Input Bus and are differentiated by their output destinations, number
of Product Terms.
The PLDs consume minimal power by using Zero-Power design techniques. The speed
and power consumption of the PLD is controlled by the Turbo Bit in the PMMR0 register
and other bits in the PMMR2 registers. These registers are set by the microcontroller at
runtime. There is a slight penalty to PLD propagation time when invoking the non-Turbo
bit.
4.3 I/O PortsThe PSD4000 has 52 I/O pins divided among seven ports (Port A, B, C, D, E, F and G).
Each I/O pin can be individually configured for different functions. Ports can be configured
as standard MCU I/O ports, PLD I/O, or latched address outputs for microcontrollers using
multiplexed address/data busses.
The JTAG pins can be enabled on Port E for In-System Programming (ISP). Ports F and
G can also be configured as a data port for a non-multiplexed bus.
4.4 Microcontroller Bus InterfaceThe PSD4000 easily interfaces with most 16-bit microcontrollers that have either
multiplexed or non-multiplexed address/data busses. The device is configured to respond
to the microcontroller’s control signals, which are also used as inputs to the PLDs. Section
9.3.5 contains microcontroller interface examples.
4.0
PSD4000
Architectural
Overview
Table 2. PLD I/O Table
PSD4000
Architectural
Overview
(cont.)
4.5 ISP via JTAG PortIn-System Programming can be performed through the JTAG pins on Port E. This serial
interface allows complete programming of the entire PSD4000 device. A blank device can
be completely programmed. The JTAG signals (TMS, TCK, TSTAT, TERR, TDI, TDO) can
be multiplexed with other functions on Port E. Table 3 indicates the JTAG signals pin
assignments.
4.6 In-System Programming (ISP)Using the JTAG signals on Port E, the entire PSD4000 (memory, logic, configuration)
device can be programmed or erased without the use of the microcontroller.
Table 3. JTAG Signals on Port E
PSD4000 Series Preliminary Information
4.7 In-Application re-Programming (IAP)The main Flash memory can also be programmed in-system by the microcontroller
executing the programming algorithms out of the secondary Flash memory, or SRAM.
Since this is a sizable separate block, the application can also continue to operate. The
secondary Flash boot memory can be programmed the same way by executing out of the
main Flash memory. Table 4 indicates which programming methods can program different
functional blocks of the PSD4000.
Table 4. Methods of Programming Different Functional Blocks of the PSD4000
4.8 Page RegisterThe eight-bit Page Register expands the address range of the microcontroller by up to
256 times.The paged address can be used as part of the address space to access
external memory and peripherals or internal memory and I/O. The Page Register can also
be used to change the address mapping of blocks of Flash memory into different memory
spaces for IAP.
4.9 Power Management UnitThe Power Management Unit (PMU) in the PSD4000 gives the user control of the
power consumption on selected functional blocks based on system requirements. The
PMU includes an Automatic Power Down unit (APD) that will turn off device functions due
to microcontroller inactivity. The APD unit has a Power Down Mode that helps reduce
power consumption.
The PSD4000 also has some bits that are configured at run-time by the MCU to reduce
power consumption of the GPLD. The turbo bit in the PMMR0 register can be turned off
and the GPLD will latch its outputs and go to standby until the next transition on its inputs.
Additionally, bits in the PMMR2 register can be set by the MCU to block signals from
entering the GPLD to reduce power consumption. See section 9.5.
Preliminary Information PSD4000 Series
Figure 2. PSDsoft Development Tool
Development
SystemThe PSD4000 series is supported by PSDsoft a Windows-based (95, 98, NT) software
development tool. A PSD design is quickly and easily produced in a point and click
environment. The designer does not need to enter Hardware Definition Language (HDL)
equations (unless desired) to define PSD pin functions and memory map information. The
general design flow is shown in Figure 2 below. PSDsoft is available from our web site
(www.psdst.com) or other distribution channels.
PSDsoft directly supports two low cost device programmers from ST, PSDpro and
FlashLINK (JTAG). Both of these programmers may be purchased through your local
rep/distributor, or directly from our web site using a credit card. The PSD4000 is also
supported by third party device programmers, see web site for current list.
PSD4000 Series Preliminary InformationThe following table describes the pin names and pin functions of the PSD4000. Pins that
have multiple names and/or functions are defined using PSDsoft.
6.0
Table 5.
PSD4000
Pin
Descriptions
Preliminary Information PSD4000 Series
Table 5.
PSD4000
Pin
Descriptions
(cont.)
PSD4000 Series Preliminary Information
Table 5.
PSD4000
Pin
Descriptions
(cont.)
Preliminary Information PSD4000 SeriesTable 6 shows the offset addresses to the PSD4000 registers relative to the CSIOP base
address. The CSIOP space is the 256 bytes of address that is allocated by the user to the
internal PSD4000 registers. Table 6 provides brief descriptions of the registers in CSIOP
space. For a more detailed description, refer to section 9.
7.0 PSD4000
Register
Description and
Address Offset
Table 6. Register Address Offset
PSD4000 Series Preliminary Information
Data In Registers – Port A, B, C, D, E, F and G
Register Bit
DefinitionAll the registers in the PSD4000 are included here for reference. Detail description of the
registers are found in the Functional Block section of the Data Sheet.
Bit definitions:Read only registers, read Port pin status when Port is in MCU I/O input Mode.
Data Out Registers – Port A, B, C, D, E, F and G
Bit definitions:Latched data for output to Port pin when pin is configured in MCU I/O output mode.
Direction Registers – Port A, B, C, D, E, F and G
Bit definitions:Set Register Bit to 0 = configure corresponding Port pin in Input mode (default).
Set Register Bit to 1 = configure corresponding Port pin in Output mode.
Control Registers – Ports E, F and G
Bit definitions:Set Register Bit to 0 = configure corresponding Port pin in MCU I/O mode (default).
Set Register Bit to 1 = configure corresponding Port pin in Latched Address Out mode.
Drive Registers – Ports A, B, D, E, and G
Bit definitions:Set Register Bit to 0 = configure corresponding Port pin in CMOS output driver (default).
Set Register Bit to 1 = configure corresponding Port pin in Open Drain output driver.
Drive Registers – Ports C and F
Bit definitions:Set Register Bit to 0 = configure corresponding Port pin as CMOS output driver (default).
Set Register Bit to 1 = configure corresponding Port pin in Slew Rate mode.
Flash Protection Register
Bit definitions: Read Only RegisterSec
_Prot 1 = Flash Sector is write protected.
Sec_Prot 0 = Flash Sector is not write protected.
Preliminary Information PSD4000 Series
Register Bit
Definition
(cont.)
Flash Boot Protection Register
Bit definitions:
Sec_Prot 1 = Boot Block Sector is write protected.
Sec_Prot 0 = Boot Block Sector is not write protected.
Security_Bit 0 = Security Bit in device has not been set.
1 = Security Bit in device has been set.
Page Register
Bit definitions:
Configure Page input to PLD. Default Pgr[7:0] = 00.
PMMR0 Register
Bit definitions: (default is 0)
Bit 1 0 = Automatic Power Down (APD) is disabled.
1 = Automatic Power Down (APD) is enabled.
Bit 3 0 = PLD Turbo is on.
1 = PLD Turbo is off, saving power.
Bit 4 0 = CLKIN input to the PLD AND array is connected.
Every CLKIN change will power up the PLD when Turbo bit is off.
1 = CLKIN input to PLD AND array is disconnected, saving power.
Bit 5 0 = CLKIN input to the PLD Micro⇔Cells is connected.
1 = CLKIN input to the PLD Micro⇔Cells is disconnected, saving power.
*Not used bit should be set to zero.
PMMR2 Register
Bit definitions (defauld is 0):
Bit 0 0 = Address A[7:0] are connected into the PLD array.
1 = Address A[7:0] are blocked from the PLD array, saving power.
Note: in XA mode, A3-0 come from PF3-0 and A7-4 come from ADIO7-4.
Bit 2 0 = Cntl0 input to the PLD AND array is connected.
1 = Cntl0 input to the PLD AND array is disconnected, saving power.
Bit 3 0 = Cntl1 input to the PLD AND array is connected.
1 = Cntl1 input to the PLD AND array is disconnected, saving power.
Bit 4 0 = Cntl2 input to the PLD AND array is connected.
1 = Cntl2 input to the PLD AND array is disconnected, saving power.
Bit 5 0 = Ale input to the PLD AND array is connected.
1 = Ale input to the PLD AND array is disconnected, saving power.
Bit 6 0 = WRh/DBE input to the PLD AND array is connected.
1 = WRh/DBE input to the PLD AND array is disconnected, saving power.
*Not used bit should be set to zero.
PSD4000 Series Preliminary Information
Register Bit
Definition
(cont.)
VM Register
Bit definitions:
Bit 0 0 = PSEN can’t access SRAM in 80C51XA modes.
1 = PSEN can access SRAM in 80C51XA modes.
Bit 1 0 = PSEN can’t access Boot in 80C51XA modes.
1 = PSEN can access Boot in 80C51XA modes.
Bit 2 0 = PSEN can’t access main Flash in 80C51XA modes.
1 = PSEN can access main Flash in 80C51XA modes.
Bit 3 0 = RD can’t access Boot in 80C51XA modes.
1 = RD can access Boot in 80C51XA modes.
Bit 4 0 = RD can’t access main Flash in 80C51XA modes.
1 = RD can access main Flash in 80C51XA modes.
Note: Upon reset, Bit1-Bit4 are loaded to configurations selected by the user in PSDsoft. Bit 0 is always cleared
by reset. Bit 0 to Bit 4 are active only when the device is configured in Philips 80C51XA mode. Not used
bit should be set to zero.
Memory_ID0 Register
Bit definitions:
F_size[3:0] = 4h, main Flash size is 2M bit.
F_size[3:0] = 5h, main Flash size is 8M bit.
S_size[3:0] = 0h, SRAM size is 0K bit.
S_size[3:0] = 1h, SRAM size is 16K bit.
S_size[3:0] = 3h, SRAM size is 64K bit.
Memory_ID1 Register
Bit definitions:
B_size[3:0] = 0h, Boot block size is 0K bit.
B_size[3:0] = 2h, Boot block size is 256K bit.
B_type[1:0] = 0h, Boot block is Flash memory.
*Not used bit should be set to zero.
Preliminary Information PSD4000 Series
The
PSD4000
Functional
Blocks
As shown in Figure 1, the PSD4000 consists of six major types of functional blocks: Memory Blocks PLD Blocks Bus Interface I/O Ports Power Management Unit JTAG-ISP Interface
The functions of each block are described in the following sections. Many of the blocks
perform multiple functions, and are user configurable.
9.1 Memory Blocks
The PSD4000 has the following memory blocks: The main Flash memory Secondary Flash memory SRAM.
The memory select signals for these blocks originate from the Decode PLD (DPLD) and
are user-defined in PSDsoft.
Table 7 summarizes which versions of the PSD4000 contain which memory blocks.
Table 7. Memory Blocks
9.1.1 Main Flash and Secondary Flash Memory Description
The main Flash memory block is divided evenly into eight sectors. The secondary Flash
memory is divided into four sectors of eight Kbytes each. Each sector of either memory
can be separately protected from program and erase operations.
Flash memory may be erased on a sector-by-sector basis and programmed word-by-word.
Flash sector erasure may be suspended while data is read from other sectors of memory
and then resumed after reading.
During a program or erase of Flash, the status can be output on the Rdy/Bsy pin of Port
PE4. This pin is set up using PSDsoft.
9.1.1.1 Memory Block Selects
The decode PLD in the PSD4000 generates the chip selects for all the internal memory
blocks (refer to the PLD section). Each of the eight Flash memory sectors have a
Flash Select signal (FS0-FS7) which can contain up to three product terms. Each of the
four Secondary Flash memory sectors have a Select signal (CSBOOT0-3) which can
contain up to three product terms. Having three product terms for each sector select signal
allows a given sector to be mapped in different areas of system memory. When using a
microcontroller (80C51XA) with separate Program and Data space, these flexible select
signals allow dynamic re-mapping of sectors from one space to the other before and after
IAP.
9.1.1.2 The Ready/Busy Pin (PE4)
Pin PE4 can be used to output the Ready/Busy status of the PSD4000. The output on the
pin will be a ‘0’ (Busy) when Flash memory blocks are being written to, or when the Flash
memory block is being erased. The output will be a ‘1’ (Ready) when no write or erase
operation is in progress.
PSD4000 Series Preliminary Information
9.1.1.3 Memory Operation
The main Flash and secondary Flash memories are addressed through the microcontroller
interface on the PSD4000 device. The microcontroller can access these memories in one
of two ways: The microcontroller can execute a typical bus write or read operation just as it would
if accessing a RAM or ROM device using standard bus cycles. The microcontroller can execute a specific instruction that consists of several write
and read operations. This involves writing specific data patterns to special addresses
within the Flash to invoke an embedded algorithm. These instructions are summarized
in Table 8.
Typically, Flash memory can be read by the microcontroller using read operations, just
as it would read a ROM device. However, Flash memory can only be erased and
programmed with specific instructions. For example, the microcontroller cannot write a
single word directly to Flash memory as one would write a word to RAM. To program a
word into Flash memory, the microcontroller must execute a program instruction sequence,
then test the status of the programming event. This status test is achieved by a read
operation or polling the Rdy/Busy pin (PE4).
The Flash memory can also be read by using special instructions to retrieve particular
Flash device information (sector protect status and ID).
9.1.1.3.1 Instructions
An instruction is defined as a sequence of specific operations. Each received byte is
sequentially decoded by the PSD and not executed as a standard write operation. The
instruction is executed when the correct number of bytes are properly received and the
time between two consecutive bytes is shorter than the time-out value. Some instructions
are structured to include read operations after the initial write operations.
The sequencing of any instruction must be followed exactly. Any invalid combination of
instruction bytes or time-out between two consecutive bytes while addressing Flash
memory will reset the device logic into a read array mode (Flash memory reads like a
ROM device).
The PSD4000 main Flash and secondary Flash support these instructions (see Table 8): Erase memory by chip or sector Suspend or resume sector erase Program a word Reset to read array mode Read Main Flash Identifier value Read sector protection status Bypass Instruction
These instructions are detailed in Table 8. For efficient decoding of the instructions, the
first two bytes of an instruction are the coded cycles and are followed by a command byte
or confirmation byte. The coded cycles consist of writing the data byte AAh to address
XAAAh during the first cycle and data byte 55h to address X554h during the second cycle
(unless the Bypass Instruction feature is used. See 9.1.1.7). Address lines A15-A12 are
don’t care during the instruction write cycles. However, the appropriate sector select signal
(FSi or CSBOOTi) must be selected.
The main Flash and the secondary Flash Block have the same set of instructions (except
Read main Flash ID). The chip selects of the Flash memory will determine which Flash will
receive and execute the instruction. The main Flash is selected if any one of the FS0-7 is
active, and the secondary Flash Block is selected if any one of the CSBOOT0-3 is active.
The
PSD4000
Functional
Blocks
(cont.)
Preliminary Information PSD4000 Series
Table 8. Instructions= Don’t Care. “xxxh” address in the above table must be an even address.= Address of the memory location to be read.= Data read from location RA during read operation.= Address of the memory location to be programmed. Addresses are latched on the falling edge of the WR#
(CNTL0) pulse. PA is an even address for PSD in word programming mode.= Data (word) to be programmed at location PA. Data is latched on the rising edge of WR# (CNTL0) pulse.= Address of the sector to be erased or verified. The chip select (FS0-7 or CSBOOT0-3) of the sector to be
erased must be active (high).
NOTES: All bus cycles are write bus cycle except the ones with the “read” label. All values are in hexadecimal. FS0-7 and CSBOOT0-3 are active high and are defined in PSDsoft. Only Address bits A11-A0 are used in Instruction decoding. No unlock or command cycles required when device is in read mode. The Reset command is required to return to the read mode after reading the Flash ID, Sector Protect status
or if DQ5 (DQ13) goes high. Additional sectors to be erased must be entered within 80µs. The data is 00h for an unprotected sector and 01h for a protected sector. In the fourth cycle, the sector chip
select is active and (A1 = 1, A0 = 0). The Unlock Bypass command is required prior to the Unlock Bypass Program command.
10. The Unlock Bypass Reset command is required to return to reading array data when the device is in the
Unlock Bypass mode.
11. The system may read and program functions in non-erasing sectors, read the Flash ID or read the Sector
Protect status, when in the Erase Suspend mode. The erase Suspend command is valid only during a sector
erase operation.
12. The Erase Resume command is valid only during the Erase Suspend mode.
13. The MCU cannot invoke these instructions while executing code from the same Flash memory for which the
instruction is intended. The MCU must fetch, for example, codes from the Secondary Flash memory when
reading the Sector Protection Status of the main Flash.
14. All write bus cycles in an instruction are byte write to even address (XA4Ah or X554h). Flash Programming
bys cycle is writing a word to even address.
The
PSD4000
Functional
Blocks
(cont.)
PSD4000 Series Preliminary Information
The
PSD4000
Functional
Blocks
(cont.)
9.1.1.4 Power-Up Condition
The PSD4000 internal logic is reset upon power-up to the read array mode. The FSi and
CSBOOTi select signals, along with the write strobe signal, must be in the false state
during power-up for maximum security of the data contents and to remove the possibility of
data being written on the first edge of a write strobe signal. Any write cycle initiation is
locked when VCC is below VLKO.
9.1.1.5 Read
Under typical conditions, the microcontroller may read the Flash, or secondary Flash
memories using read operations just as it would a ROM or RAM device. Alternately, the
microcontoller may use read operations to obtain status information about a program or
erase operation in progress. Lastly, the microcontroller may use instructions to read
special data from these memories. The following sections describe these read functions.
9.1.1.5.1 Read the Contents of Memory
Main Flash and secodary Flash memories are placed in the read array mode after
power-up, chip reset, or a Reset Flash instruction (see Table 8). The microcontroller can
read the memory contents of main Flash or secondary Flash by using read operations any
time the read operation is not part of an instruction sequence.
9.1.1.5.2 Read the Main Flash Memory Identifier
The main Flash memory identifier is read with an instruction composed of 4 operations:
3 specific write operations and a read operation (see Table 8). The PSD4000 main Flash
memory ID is E8h. The Secondary Flash does not support this instruction.
9.1.1.5.3 Read the Flash Memory Sector Protection Status
The Flash memory sector protection status is read with an instruction composed of 4
operations: 3 specific write operations and a read operation (see Table 8). The read
operation will produce 01h if the Flash sector is protected, or 00h if the sector is not
protected.
The sector protection status for all NVM blocks (main Flash or secondary Flash) can also
be read by the microcontroller accessing the Flash Protection and Flash Boot Protection
registers in PSD I/O space. See section 9.1.1.9.1 for register definitions.
9.1.1.5.4 Read the Erase/Program Status Bits
The PSD4000 provides several status bits to be used by the microcontroller to confirm
the completion of an erase or programming instruction of Flash memory. These status bits
minimize the time that the microcontroller spends performing these tasks and are defined
in Table 9. The status byte resides in even location and can be read as many times as
needed. Please note DQ15-8 is even byte for Motorola MCUs with 16 bit data bus.
Table 9. Status Bits
NOTES:1. X = Not guaranteed value, can be read either 1 or 0. DQ15-DQ0 represent the Data Bus bits, D15-D0.
3. FSi/CSBOOTi are active high.
For Flash memory, the microcontroller can perform a read operation to obtain these status
bits while an erase or program instruction is being executed by the embedded algorithm.
Table 9A. Status Bits for Motorola
Preliminary Information PSD4000 Series
The
PSD4000
Functional
Blocks
(cont.)
9.1.1.5.5 Data Polling Flag DQ7 (DQ15 for Motorola)
When Erasing or Programming the Flash memory bit DQ7 (DQ15) outputs the complement
of the bit being entered for Programming/Writing on DQ7 (DQ15). Once the Program
instruction or the Write operation is completed, the true logic value is read on DQ7 (DQ15)
(in a Read operation). Flash memory specific features: Data Polling is effective after the fourth Write pulse (for programming) or after the
sixth Write pulse (for Erase). It must be performed at the address being programmed
or at an address within the Flash sector being erased. During an Erase instruction, DQ7 (DQ15) outputs a ‘0’. After completion of the
instruction, DQ7 (DQ15) will output the last bit programmed (it is a ‘1’ after erasing). If the location to be programmed is in a protected Flash sector, the instruction is
ignored. If all the Flash sectors to be erased are protected, DQ7 (DQ15) will be set to ‘0’ for
about 100 µs, and then return to the previous addressed location. No erasure will be
performed.
9.1.1.5.6 Toggle Flag DQ6 (DQ14 for Motorola)
The PSD4000 offers another way for determining when the Flash memory Program
instruction is completed. During the internal Write operation and when either the FSi or
CSBOOTi is true, the DQ6 (DQ14) will toggle from ‘0’ to ‘1’ and ‘1’ to ‘0’ on subsequent
attempts to read any word of the memory.
When the internal cycle is complete, the toggling will stop and the data read on the
Data Bus is the addressed memory location. The device is now accessible for a new
Read or Write operation. The operation is finished when two successive reads yield the
same output data. Flash memory specific features: The Toggle bit is effective after the fourth Write pulse (for programming) or after the
sixth Write pulse (for Erase). If the location to be programmed belongs to a protected Flash sector, the instruction
is ignored. If all the Flash sectors selected for erasure are protected, DQ6 (DQ14) will toggle to
‘0’ for about 100 µs and then return to the previous addressed location.
9.1.1.5.7 Error Flag DQ5 (DQ14 for Motorola)
During a correct Program or Erase, the Error bit will set to ‘0’. This bit is set to ‘1’ when
there is a failure during Flash programming, Sector erase, or Bulk Erase.
In the case of Flash programming, the Error Bit indicates the attempt to program a Flash
bit(s) from the programmed state (0) to the erased state (1), which is not a valid operation.
The Error bit may also indicate a timeout condition while attempting to program a word.
In case of an error in Flash sector erase or word program, the Flash sector in which the
error occurred or to which the programmed location belongs must no longer be used.
Other Flash sectors may still be used. The Error bit resets after the Reset instruction. A
reset instruction is required after detecting the error bit.
9.1.1.5.8 Erase Time-out Flag DQ3 (DQ11 for Motorola)
The Erase Timer bit reflects the time-out period allowed between two consecutive Sector
Erase instructions. The Erase timer bit is set to ‘0’ after a Sector Erase instruction for a
time period of 100 µs + 20% unless an additional Sector Erase instruction is decoded.
After this time period or when the additional Sector Erase instruction is decoded, DQ3
(DQ11) is set to ‘1’. A reset instruction is required after detecting the erase timer bit.
PSD4000 Series Preliminary Information
9.1.1.6 Programming Flash Memory
Flash memory must be erased prior to being programmed. The MCU may erase Flash
memory all at once or by-sector. Flash memory sector erases to all logic ones, and its bits
are programmed to logic zeros. Although erasing Flash memory occurs on a sector or chip
basis, programming Flash memory occurs on a word basis.
The PSD4000 main Flash and secondary Flash memories require the MCU to send an
instruction to program a word or perform an erase function (see Table 8).
Once the MCU issues a Flash memory program or erase instruction, it must check for the
status of completion. The embedded algorithms that are invoked inside the PSD4000
support several means to provide status to the MCU. Status may be checked using any of
three methods: Data Polling, Data Toggle, or the Ready/Busy output pin.
9.1.1.6.1 Data Polling
Polling on DQ7 (DQ15) is a method of checking whether a Program or Erase instruction is
in progress or has completed. Figure 3 shows the Data Polling algorithm.
When the MCU issues a programming instruction, the embedded algorithm within the
PSD4000 begins. The MCU then reads the location of the word to be programmed in Flash
to check status. Data bit DQ7 (DQ15) of this location becomes the compliment of data bit
7of the original data word to be programmed. The MCU continues to poll this location,
comparing DQ7 (DQ15) and monitoring the Error bit on DQ5 (DQ13). When the DQ7
(DQ15) matches data bit 7 of the original data, and the Error bit at DQ5 (DQ13) remains
‘0’, then the embedded algorithm is complete. If the Error bit at DQ5 is ‘1’, the MCU should
test DQ7 (DQ15) again since DQ7 (DQ15) may have changed simultaneously with DQ5
(DQ13) (see Figure 3).
The Error bit at DQ5 (DQ13) will be set if either an internal timeout occurred while the
embedded algorithm attempted to program the location or if the MCU attempted to
program a ‘1’ to a bit that was not erased (not erased is logic ‘0’).
It is suggested (as with all Flash memories) to read the location again after the embedded
programming algorithm has completed to compare the word that was written to Flash with
the word that was intended to be written.
When using the Data Polling method after an erase instruction, Figure 3 still applies.
However, DQ7 (DQ15) will be ‘0’ until the erase operation is complete. A ‘1’ on DQ5
(DQ13) will indicate a timeout failure of the erase operation, a ‘0’ indicates no error.
The MCU can read any location within the sector being erased to get DQ7 (DQ15) and
DQ5 (DQ13) .
PSDsoft generates ANSI C code functions which implement these Data Polling
algorithms.
The
PSD4000
Functional
Blocks
(cont.)
Preliminary Information PSD4000 Series
Figure 3. Data Polling Flow Chart
The
PSD4000
Functional
Blocks
(cont.)
9.1.1.6.2 Data Toggle
Checking the Data Toggle bit on DQ6 (DQ14) is a method of determining whether a
Program or Erase instruction is in progress or has completed. Figure 4 shows the Data
Toggle algorithm.
When the MCU issues a programming instruction, the embedded algorithm within the
PSD4000 begins. The MCU then reads the location to be programmed in Flash to check
status. Data bit DQ6 (DQ14) of this location will toggle each time the MCU reads this
location until the embedded algorithm is complete. The MCU continues to read this
location, checking DQ6 (DQ14) and monitoring the Error bit on DQ5 (DQ13) . When
DQ6 (DQ14) stops toggling (two consecutive reads yield the same value), and the Error bit
on DQ5 (DQ13) remains ‘0’, then the embedded algorithm is complete. If the Error bit on
DQ5 (DQ13) is ‘1’, the MCU should test DQ6 (DQ14) again, since DQ6 (DQ14) may have
changed simultaneously with DQ5 (DQ13) (see Figure 4).
The Error bit at DQ5 (DQ13) will be set if either an internal timeout occurred while the
embedded algorithm attempted to program, or if the MCU attempted to program a ‘1’ to a
bit that was not erased (not erased is logic ‘0’).
PSD4000 Series Preliminary Information
9.1.1.6.2 Data Toggle (cont.)
It is suggested (as with all Flash memories) to read the location again after the embedded
programming algorithm has completed to compare the word that was written to Flash with
the word that was intended to be written.
When using the Data Toggle method after an erase instructin, Figure 4 still applies. DQ6
(DQ14) will toggle until the erase operation is complete. A ‘1’ on DQ5 (DQ13) will indicate
a timeout failure of the erase operation, a ‘0’ indicates no error. The MCU can read any
even location within the sector being erased to get DQ6 (DQ14) and DQ5 (DQ13) .
PSDsoft generates ANSI C code functions which implement these Data Toggling
algorithms.
The
PSD4000
Functional
Blocks
(cont.)
Figure 4. Data Toggle Flow Chart
Preliminary Information PSD4000 Series
The
PSD4000
Functional
Blocks
(cont.)
9.1.1.7 Unlock Bypass Instruction
The unlock bypass feature allows the system to program words to the flash memories
faster than using the standard program instruction. The unlock bypass instruction is
initiated by first writing two unlock cycles. This is followed by a third write cycle containing
the unlock bypass command, 20h (see Table 8). The flash memory then enters the unlock
bypass mode. A two-cycle Unlock Bypass Program instruction is all that is required to
program in this mode. The first cycle in this instruction contains the unlock bypass
programm command, A0h; the second cycle contains the program address and data.
Additional data is programmed in the same manner. This mode dispenses with the initial
two unlock cycles required in the standard program instruction, resulting in faster total pro-
gramming time. During the unlock bypass mode, only the Unlock Bypass Program and
Unlock Bypass Reset instructions are valid. To exit the unlock bypass mode, the system
must issue the two-cycle unlock bypass reset instruction. The first cycle must contain the
data 90h; the second cycle the data 00h. Addresses are don’t care for both cycles. The
flash memory then returns to reading array data mode.
9.1.1.8 Erasing Flash Memory
9.1.1.8.1. Flash Bulk Erase Instruction
The Flash Bulk Erase instruction uses six write operations followed by a Read operation of
the status register, as described in Table 8. If any byte of the Bulk Erase instruction is
wrong, the Bulk Erase instruction aborts and the device is reset to the Read Flash memory
status.
During a Bulk Erase, the memory status may be checked by reading status bits DQ5, DQ6,
and DQ7 (DQ13, DQ14, DQ15), as detailed in section 9.1.1.6. The Error bit (returns a ‘1’ if
there has been an Erase Failure (maximum number of erase cycles have been executed).
It is not necessary to program the array with 00h because the PSD4000 will automatically
do this before erasing to 0FFh.
During execution of the Bulk Erase instruction, the Flash memory will not accept any
instructions.
9.1.1.8.2 Flash Sector Erase Instruction
The Sector Erase instruction uses six write operations, as described in Table 8. Additional
Flash Sector Erase confirm commands and Flash sector addresses can be written
subsequently to erase other Flash sectors in parallel, without further coded cycles, if the
additional instruction is transmitted in a shorter time than the timeout period of about
100 μs. The input of a new Sector Erase instruction will restart the time-out period.
The status of the internal timer can be monitored through the level of DQ3 (DQ11) (Erase
time-out bit). If DQ3 (DQ11) is ‘0’, the Sector Erase instruction has been received and the
timeout is counting. If DQ3 (DQ11) is ‘1’, the timeout has expired and the PSD4000 is busy
erasing the Flash sector(s). Before and during Erase timeout, any instruction other than
Erase suspend and Erase Resume will abort the instruction and reset the device to Read
Array mode. It is not necessary to program the Flash sector with 00h as the PSD4000 will
do this automatically before erasing.
During a Sector Erase, the memory status may be checked by reading status bits DQ5,
DQ6, and DQ7 (DQ13, DQ14, DQ15), as detailed in section 9.1.1.6.
During execution of the erase instruction, the Flash block logic accepts only Reset and
Erase Suspend instructions. Erasure of one Flash sector may be suspended, in order to
read data from another Flash sector, and then resumed.
PSD4000 Series Preliminary Information
The
PSD4000
Functional
Blocks
(cont.)
9.1.1.8.3 Flash Erase Suspend Instruction
When a Flash Sector Erase operation is in progress, the Erase Suspend instruction will
suspend the operation by writing 0B0h to any even address when an appropriate Chip
Select (FSi or CSBOOTi) is true. (See Table 8). This allows reading of data from another
Flash sector after the Erase operation has been suspended. Erase suspend is accepted
only during the Flash Sector Erase instruction execution and defaults to read array
mode. An Erase Suspend instruction executed during an Erase timeout will, in addition to
suspending the erase, terminate the time out.
The Toggle Bit DQ6 stops toggling when the PSD4000 internal logic is suspended. The
toggle Bit status must be monitored at an address within the Flash sector being erased.
The Toggle Bit will stop toggling between 0.1 μs and 15 μs after the Erase Suspend
instruction has been executed. The PSD4000 will then automatically be set to Read Flash
Block Memory Array mode.
If an Erase Suspend instruction was executed, the following rules apply: Attempting to read from a Flash sector that was being erased will output invalid data. Reading from a Flash sector that was not being erased is valid. The Flash memory cannot be programmed, and will only respond to Erase Resume
and Reset instructions (read is an operation and is OK). If a Reset instruction is received, data in the Flash sector that was being erased will
be invalid.
9.1.1.8.4 Flash Erase Resume Instruction
If an Erase Suspend instruction was previously executed, the erase operation may be
resumed by this instruction. The Erase Resume instruction consists of writing 030h to any
even address while an appropriate Chip Select (FSi or CSBOOTi) is true. (See Table 8.)
9.1.1.9 Specific Features
9.1.1.9.1 Main Flash and Secondary Flash Sector Protect
Each sector of Main Flash and Secondary Flash memory can be separately protected
against Program and Erase functions. Sector Protection provides additional data
security because it disables all program or erase operations. This mode can be activated
(or deactivated) through the JTAG-ISP Port or a Device Programmer.
Sector protection can be selected for each sector using the PSDsoft program. This will
automatically protect selected sectors when the device is programmed through the JTAG
Port or a Device Programmer. Flash sectors can be unprotected to allow updating of their
contents using the JTAG Port or a Device Programmer. The microcontroller can read (but
cannot change) the sector protection bits.
Any attempt to program or erase a protected Flash sector will be ignored by the device.
The Verify operation will result in a read of the protected data. This allows a guarantee of
the retention of the Protection status.
The sector protection status can either be read by the MCU through the Flash protection
and secondary Flash protection registers (CSIOP), or use the Read Sector Protection
instruction (Table 8).
Preliminary Information PSD4000 Series
The
PSD4000
Functional
Blocks
(cont.)
Flash Protection Register
9.1.1.9.2 Reset Instruction
The Reset instruction consists of one write cycle (see Table 8). It can also be optionally
preceded by the standard two write decoding cycles (writing AAh to AAAh and 55h to
554h).
The Reset instruction must be executed after: Reading the Flash Protection status or Flash ID using the Flash instruction. When an error condition occurs (DQ5 (DQ13) goes high) during a Flash programming
or erase cycle.
The Reset instruction will reset the Flash to normal Read Mode immediately. However, if
there is an error condition (DQ5 (DQ13) goes high), the Flash memory will return to the
Read Mode in 25 μSeconds after the Reset instruction is issued.
The Reset instruction is ignored when it is issued during a Flash programming or Bulk
Erase cycle. The Reset instruction will abort the on going sector erase cycle and return the
Flash memory to normal Read Mode in 25 μSeconds.
9.1.1.9.3 Reset Pin Input
The reset pulse input from the pin will abort any operation in progress and reset the Flash
memory to Read Mode. When the reset occurs during a programming or erase cycle, the
Flash memory will take up to 25 μSeconds to return to Read Mode. It is recommended that
the reset pulse (except power on reset, see Reset Section) be at least 25 μSeconds such
that the Flash memory will always be ready for the MCU to fetch the boot code after reset
is over.
Bit Definitions:
Sec_Prot 1 = Main Flash Sector is write protected.
Sec_Prot 0 = Main Flash Sector is not write protected.
Flash Boot Protection Register
Bit Definitions:
Sec_Prot 1 = Flash Boot Sector is write protected.
Sec_Prot 0 = Flash Boot Sector is not write protected.
Security_Bit 0 = Security Bit in device has not been set.
1 = Security Bit in device has been set.
Table 10. Sector Protection/Security Bit Definition Not used.
PSD4000 Series Preliminary Information
The
PSD4000
Functional
Blocks
(cont.)
9.1.2 SRAM
The SRAM is enabled when RS0—the SRAM chip select output from the DPLD—is high.
RS0 can contain up to three product terms, allowing flexible memory mapping.
The SRAM can be backed up using an external battery. The external battery should be
connected to the Vstby pin (PE6). If you have an external battery connected to the
PSD4000, the contents of the SRAM will be retained in the event of a power loss. The
contents of the SRAM will be retained so long as the battery voltage remains at 2V or
greater. If the supply voltage falls below the battery voltage, an internal power switchover
to the battery occurs.
Pin PE7 can be configured as an output that indicates when power is being drawn from the
external battery. This Vbaton signal will be high with the supply voltage falls below the bat-
tery voltage and the battery on PE6 is supplying power to the internal SRAM.
The chip select signal (RS0) for the SRAM, Vstby, and Vbaton are all configured using
PSDsoft.
9.1.3 Memory Select Signals
The main Flash (FSi), secondary Flash (CSBOOTi), and SRAM (RS0) memory select
signals are all outputs of the DPLD. They are defined using PSDsoft. The following rules
apply to the equations for the internal chip select signals: Main Flash memory and secondary Flash memory sector select signals must not be
larger than the physical sector size. Any main Flash memory sector must not be mapped in the same memory space as
another Main Flash sector. A secondary Flash memory sector must not be mapped in the same memory space as
another Flash Boot sector. SRAMand I/O spaces must not overlap. A secondary Flash memory sector may overlap a main Flash memory sector. In case of
overlap, priority will be given to the Flash Boot sector. SRAM, I/O, and Peripheral I/O spaces may overlap any other memory sector. Priority
will be given to the SRAM, and I/O.
Example
FS0 is valid when the address is in the range of 8000h to BFFFh, CSBOOT0 is valid from
8000h to 9FFFh, and RS0 is valid from 8000h to 87FFh. Any address in the range of RS0
will always access the SRAM. Any address in the range of CSBOOT0 greater than 87FFh
(and less than 9FFFh) will automatically address Boot memory segment 0. Any address
greater than 9FFFh will access the Flash memory segment 0. You can see that half of the
Flash memory segment 0 and one-fourth of Boot segment 0 can not be accessed in this
example. Also note that an equation that defined FS1 to anywhere in the range of 8000h to
BFFFh would not be valid.
Figure 5 shows the priority levels for all memory components. Any component on a higher
level can overlap and has priority over any component on a lower level. Components on
the same level must not overlap. Level one has the highest priority and level 3 has the
lowest.
Preliminary Information PSD4000 Series
The
PSD4000
Functional
Blocks
(cont.)
Figure 5. Priority Level of Memory and I/O Components
9.1.3.1. Memory Select Configuration for MCUs with Separate Program and Data Spaces
The 80C51XA and compatible family of microcontrollers, can be configured to have
separate address spaces for code memory (selected using PSEN) and data memory
(selected using RD). Any of the memories within the PSD4000 can reside in either space
or both spaces. This is controlled through manipulation of the VM register that resides in
the PSD’s CSIOP space.
The VM register is set using PSDsoft to have an initial value. It can subsequently be
changed by the microcontroller so that memory mapping can be changed on-the-fly.
For example, you may wish to have SRAM and main Flash in Data Space at boot, and
secondary Flash memory in Program Space at boot, and later swap main and secondary
Flash memory. This is easily done with the VM register by using PSDsoft to configure it for
boot up and having the microcontroller change it when desired.
Table 11 describes the VM Register.
Table 11. VM Register
NOTE: Bits 6-5 are not used.
The
PSD4000
Functional
Blocks
(cont.)
Figure 6. 80C51XA Memory Modes – Separate Space Mode
Figure 7. 80C51XA Memory Mode – Combined Space Mode
9.1.3.2 Configuration Modes for MCUs with Separate Program and Data Spaces
9.1.3.2.1 Separate Space Modes
Code memory space is separated from data memory space. For example, the PSEN
signal is used to access the program code from the main Flash Memory, while the RD
signal is used to access data from the secondary Flash memory, SRAM and I/O Ports.
This configuration requires the VM register to be set to 0Ch.
9.1.3.2.2 . Combined Space Modes
The program and data memory spaces are combined into one space that allows the main
Flash Memory, secondary Flash memory, and SRAM to be accessed by either PSEN or
RD. For example, to configure the main Flash memory in combined space mode, bits 2
and 4 of the VM register are set to “1”.
9.1.3.3 80C51XA Memory Map Example
See Application Notes for examples.
PSD4000 Series Preliminary Information
Preliminary Information PSD4000 Series
Figure 8. Page Register
The
PSD4000
Functional
Blocks
(cont.)
9.1.4 Page Register
The eight bit Page Register increases the addressing capability of the microcontroller by a
factor of up to 256. The contents of the register can also be read by the microcontroller.
The outputs of the Page Register (PGR0-PGR7) are inputs to the PLD decoder and
can be included in the Flash Memory, secondary Flash memory, and SRAM chip select
equations.
If memory paging is not needed, or if not all 8 page register bits are needed for memory
paging, then these bits may be used in the PLD for general logic. See Application
Notes.
Figure 8 shows the Page Register. The eight flip flops in the register are connected to the
internal data bus. The microcontroller can write to or read from the Page Register. The
Page Register can be accessed at address location CSIOP + E0h.
PSD4000 Series Preliminary Information
The
PSD4000
Functional
Blocks
(cont.)
9.1.5 Memory ID Registers
The 8-bit read only memory status registers are included in the CSIOP space. The user
can determine the memory configuration of the PSD device by reading the Memory ID0
and Memory ID1 registers. The content of the registers are defined as follow:
Memory_ID0 Register
Bit Definition
Memory_ID1 Register
*Not used bit should be set to zero.
Bit Definition
Preliminary Information PSD4000 Series
The
PSD4000
Functional
Blocks
(cont.)
9.2 PLDs
The PLDs bring programmable logic functionality to the PSD4000. After specifying the
logic for the PLDs in PSDsoft, the logic is programmed into the device and available upon
power-up.
The PSD4000 contains two PLDs: the Decode PLD (DPLD), and the General Purpose
PLD (GPLD). The PLDs are briefly discussed in the next few paragraphs, and in more
detail in sections 9.2.1 and 9.2.2. Figure 10 shows the configuration of the PLDs.
The DPLD performs address decoding for internal components, such as memory,
registers, and I/O port selects.
The GPLD can be used to generate external chip selects, control signals or logic functions.
The GPLD has 24 outputs that are connected to Port A, B and C.
The AND array is used to form product terms. These product terms are specified using
PSDsoft. An Input Bus consisting of 66 signals is connected to the PLDs. The signals are
shown in Table 12. The complement of the 66 signals are also available as inputs to the
AND array.
Table 12. DPLD and GPLD Inputs
NOTE: The address inputs are A[19:4] in 80C51XA mode.
The Turbo Bit
The PLDs in the PSD4000 can minimize power consumption by switching to standby
when inputs remain unchanged for an extended time of about 70 ns. Setting the Turbo
mode bit to off (Bit 3 of the PMMR0 register) automatically places the PLDs into standby if
no inputs are changing. Turbo-off mode increases propagation delays while reducing
power consumption. Refer to the Power Management Unit section on how to set the Turbo
Bit. Additionally, five bits are available in the PMMR2 register to block MCU control signals
from entering the PLDs. This reduces power consumption and can be used only when
these MCU control signals are not used in PLD logic equations.
PSD4000 Series Preliminary Information
Figure 9. PLD Block Diagram
Preliminary Information PSD4000 Series
The
PSD4000
Functional
Blocks
(cont.)
9.2.1 Decode PLD (DPLD)
The DPLD, shown in Figure 10, is used for decoding the address for internal components.
The DPLD can generate the following decode signals: 8 sector selects for the main Flash memory (three product terms each) 4 sector selects for the Secondary Flash memory (three product terms each) 1 internal SRAM select (three product terms) 1 internal CSIOP select (select PSD registers, one product term)
Inputs to the DPLD chip selects may include address inputs, Page Register inputs and
other user defined external inputs from Ports A, B, C, D or F.
9.2.2 General Purpose PLD (GPLD)
The General Purpose PLD implements user defined system combinatorial logic function
or chip selects for external devices. Figure 11 shows how the GPLD is connected to the
I/O Ports. The GPLD has 24 outputs and each are routed to a port pin. The port pin can
also be configured as input to the GPLD. When it is not used as GPLD output or input, the
pin can be configured to perform other I/O functions.
All GPLD outputs are identical except in the number of available product terms (PTs) for
logic implementation. Select the pin that can best meet the PT requirement of your logic
function or chip select. In general, a PT is consumed for each logic “OR” function that you
specify in PSDsoft. However, certain logic functions can consume more than one PT even
if no logic “OR” is specified (such as specifying an address range with boundaries of high
granularity).
Table 13 shows the number of “native” PTs for each GPLD output pin. A native PT means
that a particular PT is dedicated to an output pin. For example, Table 13 shows that PSD
Port A pin PA0 has 3 native product terms. This means a guaranteed minimum of 3 PTs is
available to implement logic for that pin.
PSD silicon and PSDsoft can include additional PTs beyong the native PTs to implement
logic. This is a transparent operation that occurs as needed through PT expansion
(internal feedback) or PT allocation (internal borrowing). You may notice in the fitter report
generated by PSDsoft that for a given GPLD output pin, more PTs were used to implement
logic than the number of native PTs available for that pin. This is because PSDsoft has
called on unused PTs from other GPLD output pins to make your logic design fit (PT
allocation or PT expansion). For optimum results, choose a GPLD output pin with a large
number of native PTs for complicated logic.
Table 13. GPLD Product Term Availability
PSD4000 Series Preliminary Information
Figure 10. DPLD Logic Array
Preliminary Information PSD4000 Series
Figure 11. The Micro⇔Cell and I/O Port
PSD4000 Series Preliminary Information
The
PSD4000
Functional
Blocks
(cont.)
9.3 Microcontroller Bus Interface
The “no-glue logic” PSD4000 Microcontroller Bus Interface can be directly connected to
most popular microcontrollers and their control signals. Key 16-bit microcontrollers with
their bus types and control signals are shown in Table 14. The MCU interface type is
specified using the PSDsoft.
Table 14. Microcontrollers and their Control Signals
***Unused CNTL2 pin can be configured as GPLD input. Other unused pins (PD3-0, PF3-0) can be
***configured for other I/O functions.
***ALE/AS input is optional for microcontrollers with a non-multiplexed bus.
***This configuration is for 68C812A4_EC at 5MHz, 3V only.
9.3.1. PSD4000 Interface to a Multiplexed Bus
Figure 16 shows an example of a system using a microcontroller with a 16-bit multiplexed
bus and a PSD4000. The ADIO port on the PSD4000 is connected directly to the
microcontroller address/data bus. ALE latches the address lines internally. Latched
addresses can be brought out to Port E, F or G. The PSD4000 drives the ADIO data bus
only when one of its internal resources is accessed and the RD input is active. Should the
system address bus exceed sixteen bits, Ports A, B, C, or F may be used as additional
address inputs.
9.3.2. PSD4000 Interface to a Non-Multiplexed Bus
Figure 17 shows an example of a system using a microcontroller with a 16-bit
non-multiplexed bus and a PSD4000. The address bus is connected to the ADIO Port, and
the data bus is connected to Port F and G. Port F and G are in tri-state mode when the
PSD4000 is not accessed by the microcontroller. Should the system address bus exceed
sixteen bits, Ports A, B or C may be used for additional address inputs.
Preliminary Information PSD4000 Series
The
PSD4000
Functional
Blocks
(cont.)
Figure 12. An Example of a Typical 16-Bit Multiplexed Bus Interface
Figure 13. An Example of a Typical 16-Bit Non-Multiplexed Bus Interface
PSD4000 Series Preliminary Information
9.3.3 Data Byte Enable Reference
Microcontrollers have different data byte orientations. The following tables show how the
PSD4135G2 interprets byte/word operation in different bus write configurations. Even-byte
refers to locations with address A0 equal to zero and odd byte as locations with A0 equal
to one.
9.3.4 Microcontroller Interface Examples
Figures 14 through 17 show examples of the basic connections between the PSD4135G2
and some popular microcontrollers. The PSD4135G2 Control input pins are labeled as the
microcontroller function for which they are configured. The MCU interface is specified using
PSDsoft. The PE6 pin should be grounded if Vstby is not used.
9.3.4.1 80C196 and 80C186
In Figure 14, the Intel 80C196 microcontroller, which has a multiplexed sixteen-bit bus, is
shown connected to a PSD4135G2. The WR and RD signals are connected to the
CNTL0-1 pins. The BHE signal is used for high data byte selection. If BHE is not used, the
PSD can be configured to receive the WRL and WRH from the MCU. Higher address
inputs (A16-A19) can be routed to Port A, B or C as inputs to the PLD.
The AMD 80186 family has the same bus connection to the PSD as the 80C196.
Table 15. 16-Bit Data Bus with BHE
The
PSD4000
Functional
Blocks
(cont.)
Table 16. 16-Bit Data Bus with WRH and WRL
Table 17. 16-Bit Data Bus with SIZ0, A0 (Motorola MCU)
Table 18. 16-Bit Data Bus with UDS, LDS (Motorola MCU)
Preliminary Information PSD4000 Series
The
PSD4000
Functional
Blocks
(cont.)
9.3.4.2 MC683XX and 68HC16
Figure 15 shows a Motorola MC68331 with non-multiplexed sixteen-bit data bus and 24-bit
address bus. The data bus from the MC68331 is connected to Port F (D0-7) and Port G
(D8-D15). The SIZ0 and A0 inputs determine the high/low byte selection. The R/W, DS
and SIZ0 are connected to the CNTL0-2 pins.
The 68HC16 and other members of the 683XX family have the same connection as the
68331 shown in Figure 15.
9.3.4.3 80C51XA
The Philips 80C51XA microcontroller has a 16-bit multiplexed bus with burst cycles.
Address bits A[3:1] are not multiplexed while A[19:4] are multiplexed with data bits D[15:0].
The PSD4135G2 supports the 80C51XA burst mode. The WRH signal is connected to the
PD3 and the WRL is connected to CNTL0 pin. The RD and PSEN signal is connected to
CNTL1-2 pins. Figure 15 shows the XA schematic.
The 80C51XA improves bus throughput and performance by issuing Burst cycles to fetch
codes from memory. In Burst cycles, addresses A19-4 are latched internally by the PSD,
while the 80C51XA drives the A3-1 lines to sequentially fetch up to 16 bytes of code. The
PSD access time is then measured from address A3-A1 valid to data in valid. The PSD
bus timing requirement in Burst cycle is identical to the normal bus cycle except the
address set up or hold time with respect to ALE is not required.
9.3.4.4 H8/300
Figure 16 shows a Hitachi H8/2350 with non-multiplexed sixteen-bit data bus and 24-bit
address bus. The H8 data bus is connected to Port F (D0-7) and Port G (D8-15).
The WRL, WRH and RD signals are connected to the CNTL0, PD3 and CNTL1 pins
respectively. The AS connection is optional and is required if the address are to be
latched.
9.3.4.5 MMC2001
The Motorola MCORE MMC2001 microcontroller has a MOD input pin that selects internal
or external boot ROM. The PSD4000 can be configured as the external flash boot ROM or
as extension to the internal ROM.
The MMC2001 has a 16-bit external data bus and 20 address lines with external Chip
Select signals. The Chip Select Control Registers allow the user to customize the bus
interface and timing to fit the individual system requirement. A typical interface configura-
tion to the PSD4000 is shown in Figure 18. The MMC2001’s R/W signal is connected to
the cntl0 pin, while EB0 and EB1 (enable byte0 and byte1) are connected to the cntl1
(UDS) and cntl2 (LDS) pins. The WEN bit in the Chip Select Control Register should set to
1 to terminate the EB[0:1] earlier to provide the write data hold time for the PSD. The WSC
and WWS bits in the Control Register are set to wait states that meet the PSD access time
requirement.
Another option is to configure the EB0 and EB1 as WRL and WRH signals. In this case the
PSD4000 control setting will be: OE, WRL, WRH where OE is the read signal from the
MMC2001.
9.3.4.6 C16X Family
The PSD4000 supports Infineon’s C16X family of microcontrollers (C161-C167) in both the
multiplexed and non-multiplexed bus configuration. In Figure 19 the C167CR is shown
connected to the PSD4000 in a multiplexed bus configuration. The control signals from the
MCU are WR, RD, BHE and ALE and are routed to the corresponding PSD pins.
The C167 has another control signal setting (RD, WRL, WRH, ALE) which is also
supported by the PSD4000.
PSD4000 Series Preliminary Information
Figure 14. Interfacing the PSD4135G2 with an 80C196
Preliminary Information PSD4000 Series
Figure 15. Interfacing the PSD4135G2 with an MC68331
PSD4000 Series Preliminary Information
Figure 16. Interfacing the PSD4135G2 with a 80C51XA-G3
Preliminary Information PSD4000 Series
Figure 17. Interfacing a PSD4135G2 with a H83/2350
PSD4000 Series Preliminary Information
Figure 18. Interfacing a PSD4135G2 with a MMC2001
