PSD913F2
PSD934F2 PSD954F2
Flash In-System Programmable (ISP) Peripherals
For 8-bit MCUs
FEATURES SUMMARY
■Single Supply Voltage:
–5 V±10% for PSD9xxF2
–3.3 V±10% for PSD9xxF2-V
■Up to 2Mbit of Primary Flash Memory (8 uniform sectors)
■256Kbit Secondary Flash Memory (4 uniform sectors)
■Up to 256Kbit SRAM
■Over 2,000 Gates of PLD: DPLD
■27 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
PRELIMINARY DATA
Figure 1. Packages
PQFP52 (T)
PLCC52 (K)
January 2002 |
1/3 |
This is preliminary information on a new product now in development or undergoing evaluation. Details are subject to change without notice.
PSD9XX Family |
||
PSD913F2 |
PSD934F2 |
PSD954F2 |
Configurable Memory System on a Chip for 8-Bit Microcontrollers |
||
|
Table of Contents |
|
Introduction.................................................................................................................................................................... |
|
1 |
In-System Programming (ISP) JTAG.................................................................................................................... |
|
2 |
In-Application Programming (IAP) ........................................................................................................................ |
|
2 |
Key Features ................................................................................................................................................................. |
|
3 |
Block Diagram ............................................................................................................................................................... |
|
4 |
PSD9XX Family............................................................................................................................................................. |
|
5 |
Architectural Overview................................................................................................................................................... |
|
6 |
Memory................................................................................................................................................................. |
|
6 |
Page Register ....................................................................................................................................................... |
|
6 |
PLDs ..................................................................................................................................................................... |
|
6 |
I/O Ports................................................................................................................................................................ |
|
7 |
Microcontroller Bus Interface ................................................................................................................................ |
|
7 |
JTAG Port ............................................................................................................................................................. |
|
7 |
In-System Programming ....................................................................................................................................... |
|
8 |
Power Management Unit ...................................................................................................................................... |
|
8 |
Development System .................................................................................................................................................... |
|
9 |
Pin Descriptions........................................................................................................................................................... |
|
10 |
Register Description and Address Offset .................................................................................................................... |
|
14 |
Functional Blocks ........................................................................................................................................................ |
|
15 |
Memory Blocks ................................................................................................................................................... |
|
15 |
Main Flash and Secondary Flash Memory Description................................................................................. |
15 |
|
SRAM............................................................................................................................................................ |
|
27 |
Memory Chip Selects .................................................................................................................................... |
|
27 |
Page Register ............................................................................................................................................... |
|
30 |
PLDs ................................................................................................................................................................... |
|
31 |
Decode PLD (DPLD)..................................................................................................................................... |
|
33 |
General Purpose PLD (GPLD)...................................................................................................................... |
|
33 |
Microcontroller Bus Interface .............................................................................................................................. |
|
35 |
Interface to a Multiplexed 8-bit Bus............................................................................................................... |
|
35 |
Interface to a Non-multiplexed 8-bit Bus ....................................................................................................... |
35 |
|
Microcontroller Interface Examples............................................................................................................... |
|
37 |
I/O Ports.............................................................................................................................................................. |
|
42 |
General Port Architecture.............................................................................................................................. |
|
42 |
Port Operating Modes ................................................................................................................................... |
|
44 |
Port Configuration Registers (PCRs) ............................................................................................................ |
|
47 |
Port Data Registers....................................................................................................................................... |
|
49 |
Ports A and B – Functionality and Structure ................................................................................................. |
49 |
|
Port C – Functionality and Structure ............................................................................................................. |
|
51 |
Port D – Functionality and Structure ............................................................................................................. |
|
51 |
For additional information,
Call 800-832-6974
Fax: 510-657-8495
Web Site: http://www.psdst.com
E-mail: ask.psd@st.com
i
|
PSD9XX Family |
|
||
|
PSD913F2 |
PSD934F2 |
PSD954F2 |
|
Configurable Memory System on a Chip for 8-Bit Microcontrollers |
|
|||
|
|
Table of Contents |
|
|
Power Management............................................................................................................................................ |
|
|
54 |
|
Automatic Power Down (APD) Unit and Power Down Mode |
........................................................................ |
54 |
||
Other Power Savings Options....................................................................................................................... |
|
|
58 |
|
Reset and Power On Requirement ............................................................................................................... |
|
|
59 |
|
Programming In-Circuit using the JTAG Interface .............................................................................................. |
|
60 |
||
Standard JTAG Signals................................................................................................................................. |
|
|
61 |
|
JTAG Extensions .......................................................................................................................................... |
|
|
61 |
|
Security and Flash Memories Protection ...................................................................................................... |
|
61 |
||
Absolute Maximum Ratings......................................................................................................................................... |
|
|
62 |
|
Operating Range ......................................................................................................................................................... |
|
|
|
62 |
Recommended Operating Conditions ......................................................................................................................... |
|
|
62 |
|
AC/DC Parameters...................................................................................................................................................... |
|
|
|
63 |
Example of Typical Power Calculation at Vcc = 5..0 V ....................................................................................... |
|
64 |
||
Example of Typical Power Calculation at Vcc = 5..0 V in Turbo .........................................................Off Mode |
65 |
|||
DC Characteristics (5 V ± 10% versions) .................................................................................................................... |
|
|
66 |
|
Microcontroller Interface – AC/DC Parameters (5 V ± 10% versions)......................................................................... |
|
67 |
||
Read Timing ....................................................................................................................................................... |
|
|
|
68 |
Write Timing........................................................................................................................................................ |
|
|
|
69 |
PLD Combinatorial Timing.................................................................................................................................. |
|
|
69 |
|
Power Down Timing............................................................................................................................................ |
|
|
70 |
|
Vstbyon Timing ................................................................................................................................................... |
|
|
|
70 |
Reset Pin Timing |
................................................................................................................................................ |
|
|
70 |
Flash Program, Write and Erase Times.............................................................................................................. |
|
|
71 |
|
ISC Timing .......................................................................................................................................................... |
|
|
|
71 |
PSD9XXFV DC Characteristics (3.0 V to 3.6 V Versions) Advance Information....................................................... |
72 |
|||
Microcontroller Interface – AC/DC Parameters (3 V versions) .................................................................................... |
|
73 |
||
Read Timing (3 V versions) ................................................................................................................................ |
|
|
73 |
|
Write Timing (3 V versions) ................................................................................................................................ |
|
|
74 |
|
PLD Combinatorial Timing (3 V versions) |
........................................................................................................... |
|
74 |
|
Power Down Timing (3 V Versions).................................................................................................................. |
|
|
75 |
|
Vstbyon Timing |
(3 V Versions) ......................................................................................................................... |
|
|
75 |
Reset Pin Timing |
(3 V Versions)....................................................................................................................... |
|
|
75 |
Flash Program, Write and Erase Times |
(3 V Versions).................................................................................... |
|
76 |
|
ISC Timing (3 V Versions) ................................................................................................................................ |
|
|
76 |
For additional information,
Call 800-832-6974
Fax: 510-657-8495
Web Site: http://www.psdst.com
E-mail: ask.psd@st.com
ii
PSD9XX Family |
||
PSD913F2 |
PSD934F2 |
PSD954F2 |
Configurable Memory System on a Chip for 8-Bit Microcontrollers |
||
|
Table of Contents |
|
Timing Diagrams ......................................................................................................................................................... |
|
77 |
Pin Capacitance .......................................................................................................................................................... |
|
81 |
AC Testing Input/Output Waveforms........................................................................................................................... |
|
81 |
AC Testing Load Circuit............................................................................................................................................... |
|
81 |
Programming ............................................................................................................................................................... |
|
81 |
Pin Assignments.......................................................................................................................................................... |
|
82 |
Package Information.................................................................................................................................................... |
|
84 |
Selector Guide............................................................................................................................................................. |
|
87 |
Part Number Construction ........................................................................................................................................... |
|
87 |
Ordering Information.................................................................................................................................................... |
|
88 |
Document Revisions.................................................................................................................................................... |
|
89 |
For additional information,
Call 800-832-6974
Fax: 510-657-8495
Web Site: http://www.psdst.com
E-mail: ask.psd@st.com
iii
PSD913F2, PSD934F2, PSD954F2
Configurable Memory System
on a Chip for 8-Bit Microcontrollers
Preliminary Information
1.0 |
The PSD9XX family of Programmable System Devices (for 8-bit microcontrollers) brings |
Introduction |
In-System-Programmability (ISP) to Flash memory and programmable logic. The result is a |
|
simple and flexible solution for embedded designs. PSD9XX devices combine many of the |
|
peripheral functions found in MCU based applications: |
|
• Up to 2 Mbit of Flash memory |
|
• A secondary 256 Kbit Flash memory |
|
• Over 2,000 gates of Flash programmable logic |
|
• Up to 256 Kbit SRAM |
|
• Reconfigurable I/O ports |
|
• Programmable power management. |
|
|
|
|
|
|
1
PSD9XX Family |
Preliminary Information |
1.0 Introduction
(Cont.)
The PSD9XX family offers two methods to program PSD Flash memory while the PSD is soldered to a circuit board.
In-System Programming (ISP) JTAG
An IEEE 1149.1 compliant JTAG 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 time? JTAG is the answer, program the PSD while blank with no MCU involvement.
•Inventory build-up of pre-programmed devices – How do I maintain an accurate count 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 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 – I have only a 64K-byte address space to start with. How can I map these two memories efficiently? A Programmable Decode PLD is the answer. 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 64K-byte 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 MCU 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 Express – 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 Express 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 PSD9XX is available in 52-pin PLCC and PQFP packages as well as a 64-pin TQFP package.
2
Preliminary Information |
PSD9XX Family |
2.0A simple interface to 8-bit microcontrollers that use either multiplexed or
Key Features |
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 8031, 80196, 80186, 80C251
•Motorola 68HC11, 68HC16, 68HC12, and 683XX
•Philips 8031 and 8051XA
•Zilog Z80, Z8, and Z180
Internal 1 or 2 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 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.
16, 64 or 256 Kbit SRAM. The SRAM’s contents can be protected from a power failure by connecting an external battery.
General Purpose PLD (GPLD) with 19 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.
27 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.
•16 of the 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 PSD9XX into Power Down Mode.
Erase/Write cycles:
•Flash memory – 100,000 minimum
•PLD – 1,000 minimum
•Data Retention: 15 years
3
4
ADDRESS/DATA/CONTROL BUS
PLD
INPUT
BUS
PAGE |
1 OR 2 MBIT MAIN FLASH |
|
MEMORY |
||
REGISTER |
||
EMBEDDED |
|
|
ALGORITHM |
8 SECTORS |
CNTL0, |
|
|
SECTOR |
256 KBIT SECONDARY |
|
CNTL1, |
|
|
FLASH MEMORY |
||
PROG. |
|
SELECTS |
|||
CNTL2 |
FLASH DECODE |
(BOOT OR DATA) |
|||
MCU BUS |
|
||||
|
PLD (DPLD) |
|
4 SECTORS |
||
|
INTRF. |
|
|||
|
|
|
|
||
|
57 |
|
SECTOR |
|
|
|
|
|
|
||
|
|
|
SELECTS |
|
|
|
|
|
SRAM SELECT |
16, 64 OR 256 KBIT BATTERY |
|
|
|
|
BACKUP SRAM |
||
|
|
|
|
||
AD0 – AD15 |
ADIO |
|
CSIOP |
RUNTIME CONTROL |
|
|
|
|
AND I/O REGISTERS |
||
|
PORT |
|
|
|
|
|
57 |
FLASH ISP PLD |
|
|
|
|
|
(GPLD) |
|
GPLD OUTPUT |
|
|
|
|
|
GPLD OUTPUT |
|
|
|
|
|
GPLD OUTPUT |
|
|
GLOBAL |
|
|
|
|
|
CONFIG. & |
|
I/O PORT PLD INPUT |
|
|
|
SECURITY |
|
|
||
|
|
|
|
PLD, CONFIGURATION |
|
|
|
JTAG |
& FLASH MEMORY |
|
|
|
SERIAL |
|
|
|
||
LOADER |
|
|
|
CHANNEL |
|
|
|
|
|
POWER |
|
VSTDBY |
|
MANGMT |
|
||
UNIT |
|
(PC2) |
|
|
|
|
|
|
|
|
|
PROG.
PORT PA0 – PA7
PORT
A
PROG. |
|
PORT |
PB0 – PB7 |
PORT |
|
B |
|
|
|
|
|
PROG. |
|
PORT |
PC0 – PC7 |
PORT |
|
C |
|
|
|
|
|
PROG. |
|
PORT |
PD0 – PD2 |
PORT |
|
D |
|
|
|
PSD9XX .1 Figure |
Family PSD9XX |
Diagram Block |
|
Information Preliminary
Preliminary Information |
PSD9XX Family |
4.0
PSD9XX Family
There are 2 variants in the PSD9XX family. All PSD9XX devices provide these base features: 1 or 2 Mbit main Flash Memory, JTAG port, GPLD, DPLD, power management, and 27 I/O pins. The following table summarizes all the devices in the PSD9XX family. Additional devices will be introduced.
Table 1. PSD9XX Product Matrix
Part # |
|
|
|
|
Flash |
Secondary |
|
|
|
|
|
|
|
Serial ISP |
Main Memory |
Flash Memory |
|
|
|
|
|
|
|
|
|
|
|||
PSD9XX |
|
I/O |
No. of |
JTAG/ISC |
Kbit |
Kbit |
SRAM |
Turbo |
Supply |
Family |
Device |
Pins |
GPLD Output |
Port |
(8 Sectors) |
(4 Sectors) |
Kbit |
Mode |
Voltage |
|
|
|
|
|
|
|
|
|
|
PSD9XX |
PSD913F2 |
27 |
19 |
Yes |
1024 |
256 |
16 |
Yes |
3V/5V |
|
|
|
|
|
|
|
|
|
|
|
PSD934F2 |
27 |
19 |
Yes |
2048 |
256 |
64 |
Yes |
3V/5V |
|
|
|
|
|
|
|
|
|
|
|
PSD954F2 |
27 |
19 |
Yes |
2048 |
256 |
256 |
Yes |
3V/5V |
|
|
|
|
|
|
|
|
|
|
5
PSD9XX Family |
Preliminary Information |
5.0
PSD9XX Architectural Overview
PSD9XX devices contain several major functional blocks. Figure 1 shows the architecture of the PSD9XX 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.
5.1 Memory
The PSD9XX contains the following memories:
•A 1 or 2 Mbit Flash
•A secondary 256 Kbit Flash memory
•16, 64 or 256 Kbit SRAM.
Each of the memories is briefly discussed in the following paragraphs. A more detailed discussion can be found in section 9.
The 1 or 2 Mbit Flash is the main memory of the PSD9XX. 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. This memory can hold boot code or data.
The 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 PSD9XX’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.
5.2 Page Register
The 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 IAP.
5.3 PLDs
The device contains two combinatorial 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 PSD9XX 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.
Table 2. PLD I/O Table
Name |
Abbreviation |
Inputs |
Outputs |
Product Terms |
|
|
|
|
|
Decode PLD |
DPLD |
57 |
15 |
39 |
|
|
|
|
|
General Purpose PLD |
GPLD |
57 |
19 |
114 |
|
|
|
|
|
6
Preliminary Information |
PSD9XX Family |
PSD9XX Architectural Overview
(cont.)
5.4 I/O Ports
The PSD9XX has 27 I/O pins divided among four ports (Port A, B, C, and D). Each I/O pin can be individually configured for different functions. Ports A, B, C and D 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 C for In-System Programming (ISP).
Port A can also be configured as a data port for a non-multiplexed bus.
5.5 Microcontroller Bus Interface
The PSD9XX easily interfaces with most 8-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.
5.6 JTAG Port
In-System Programming can be performed through the JTAG pins on Port C. This serial interface allows complete programming of the entire PSD9XX device. A blank device can be completely programmed. The JTAG signals (TMS, TCK, TSTAT, TERR, TDI, TDO) are enabled on Port C when selected or when a device is blank. Table 3 indicates the JTAG signals pin assignments.
Table 3. JTAG Signals on Port C
Port C Pins |
JTAG Signal |
||||
|
|
|
|
|
|
PC0 |
|
|
TMS |
||
|
|
|
|
|
|
PC1 |
|
|
TCK |
||
|
|
|
|
||
PC3 |
|
TSTAT |
|||
|
|
|
|
|
|
PC4 |
|
|
|
|
|
|
|
TERR |
|
|
|
|
|
|
|
|
|
PC5 |
|
|
TDI |
||
|
|
|
|
|
|
PC6 |
|
|
TDO |
||
|
|
|
|
|
|
7
PSD9XX Family |
Preliminary Information |
PSD9XX Architectural Overview
(cont.)
5.7 In-System Programming
Using the JTAG signals on Port C, the entire PSD9XX device can be programmed or erased without the use of the microcontroller (ISP). 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 (IAP). The Secondary Flash memory can be programmed the same way by executing out of the main Flash memory. The PLD logic
or other PSD9XX configuration can be programmed through the JTAG port or a device programmer. Table 4 indicates which programming methods can program different functional blocks of the PSD9XX.
Table 4. Methods of Programming Different Functional Blocks of the PSD9XX
|
|
Device |
|
Functional Block |
JTAG-ISP |
Programmer |
IAP |
|
|
|
|
Main Flash Memory |
Yes |
Yes |
Yes |
|
|
|
|
Secondary Flash Memory |
Yes |
Yes |
Yes |
|
|
|
|
PLD Array (DPLD and GPLD) |
Yes |
Yes |
No |
|
|
|
|
PSD Configuration |
Yes |
Yes |
No |
5.8 Power Management Unit
The Power Management Unit (PMU) in the PSD9XX 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 PSD9XX also has some bits that are configured at run-time by the MCU to reduce power consumption of the PLD. The turbo bit in the PMMR0 register can be turned off and the PLD will latch its outputs and go to sleep 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 PLD to reduce power consumption. See section 9.5.
8
Preliminary Information |
PSD9XX Family |
6.0 Development System
The PSD9XX family is supported by PSDsoft Express, 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 to define PSD pin functions and memory map information. The general design flow is shown in Figure 2 below. PSDsoft Express is available free from our web site (www.psdst.com) or the Literature CD.
PSDsoft Express 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 PSD9XX is also supported by third party device programmers, see web site for current list.
Figure 2. PSDsoft Development Tools
Choose MCU and PSD |
|
|
|
Automatically configures MCU |
|
|
|
bus interface and other PSD |
|
|
|
attributes. |
|
|
|
Define PSD Pin and |
|
C Code |
|
Node Functions |
|
||
|
Generation |
||
|
|
||
Point and click definition of PSD |
|
Generate C Code |
|
pin functions, internal nodes, and |
|
specific to PSD |
|
MCU system memory map. |
|
functions. |
|
Merge MCU Firmware |
|
|
|
with PSD Configuration |
MCU Firmware |
User's choice of |
|
|
|||
|
Microcontroller |
||
A composite object file is created |
Hex or S-Record |
||
Compiler/Linker |
|||
containing MCU firmware and |
Format |
|
|
PSD configuration. |
|
|
|
*.OBJ File |
|
|
|
ST PSD |
*.OBJ file |
|
|
Programmer |
|
||
available for 3rd party |
|
||
|
|
||
|
programmers. |
|
|
PSDPro or |
(conventional or |
|
|
FlashLINK (JTAG) |
JTAG-ISC) |
|
9
PSD9XX Family |
Preliminary Information |
7.0 Table 5. PSD9XX Pin
Descriptions
The following table describes the pin names and pin functions of the PSD9XX. Pins that have multiple names and/or functions are defined using PSDsoft.
Pin Name |
Pin* |
Type |
|
|
|
|
|
|
|
|
Description |
|
(PLCC) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
ADIO0-7 |
30-37 |
I/O |
This is the lower Address/Data port. Connect your MCU |
||||||||
|
|
|
address or address/data bus according to the following rules: |
||||||||
|
|
|
1. |
If your MCU has a multiplexed address/data bus where |
|||||||
|
|
|
|
the data is multiplexed with the lower address bits, |
|||||||
|
|
|
|
connect AD[0:7] to this port. |
|||||||
|
|
|
2. |
If your MCU does not have a multiplexed address/data |
|||||||
|
|
|
|
bus, or you are using an 80C251 in page mode, connect |
|||||||
|
|
|
|
A[0:7] to this port. |
|||||||
|
|
|
3. |
If you are using an 80C51XA in burst mode, connect |
|||||||
|
|
|
|
A4/D0 through A11/D7 to this port. |
|||||||
|
|
|
ALE or AS latches the address. The PSD drives data out only |
||||||||
|
|
|
if the read signal is active and one of the PSD functional |
||||||||
|
|
|
blocks was selected. The addresses on this port are passed |
||||||||
|
|
|
to the PLDs. |
||||||||
|
|
|
|
|
|
|
|
|
|
|
|
ADIO8-15 |
39-46 |
I/O |
This is the upper Address/Data port. Connect your MCU |
||||||||
|
|
|
address or address/data bus according to the following rules: |
||||||||
|
|
|
1. |
If your MCU has a multiplexed address/data bus where |
|||||||
|
|
|
|
the data is multiplexed with the lower address bits, |
|||||||
|
|
|
|
connect A[8:15] to this port. |
|||||||
|
|
|
2. |
If your MCU does not have a multiplexed address/data |
|||||||
|
|
|
|
bus, connect A[8:15] to this port. |
|||||||
|
|
|
3. |
If you are using an 80C251 in page mode, connect |
|||||||
|
|
|
|
AD[8:15] to this port. |
|||||||
|
|
|
4. |
If you are using an 80C51XA in burst mode, connect |
|||||||
|
|
|
|
A12/D8 through A19/D15 to this port. |
|||||||
|
|
|
ALE or AS latches the address. The PSD drives data out only |
||||||||
|
|
|
if the read signal is active and one of the PSD functional |
||||||||
|
|
|
blocks was selected. The addresses on this port are passed |
||||||||
|
|
|
to the PLDs. |
||||||||
|
|
|
|
|
|
|
|
|
|
|
|
CNTL0 |
47 |
I |
The following control signals can be connected to this port, |
||||||||
|
|
|
based on your MCU: |
||||||||
|
|
|
1. |
|
|
|
|
|
|
|
|
|
|
|
|
WR |
— active-low write input. |
||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2. |
|
R_W — active-high read/active low write input. |
||||||
|
|
|
This pin is connected to the PLDs. Therefore, these signals |
||||||||
|
|
|
can be used in decode and other logic equations. |
||||||||
|
|
|
|
|
|
|
|
|
|
|
|
CNTL1 |
50 |
I |
The following control signals can be connected to this port, |
||||||||
|
|
|
based on your MCU: |
||||||||
|
|
|
1. |
|
|
|
|
|
|||
|
|
|
|
RD |
— active-low read input. |
||||||
|
|
|
2. |
|
E — E clock input. |
||||||
|
|
|
3. |
|
|
|
|||||
|
|
|
|
|
DS |
— active-low data strobe input. |
|||||
|
|
|
|
|
|
|
|
||||
|
|
|
4. |
|
PSEN — connect PSEN to this port when it is being used |
||||||
|
|
|
|
|
as an active-low read signal. For example, when the |
||||||
|
|
|
|
|
80C251 outputs more than 16 address bits, PSEN is |
||||||
|
|
|
|
|
actually the read signal. |
||||||
|
|
|
|
|
This pin is connected to the PLDs. Therefore, these |
||||||
|
|
|
|
|
signals can be used in decode and other logic equations. |
||||||
|
|
|
|
|
|
|
|
|
|
|
|
10
Preliminary Information |
PSD9XX Family |
Table 5.
PSD9XX Pin
Descriptions
(cont.)
Pin Name |
Pin* |
Type |
|
Description |
||||
|
|
|
(PLCC) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||
CNTL2 |
49 |
I |
This pin can be used to input the PSEN (Program Select |
|||||
|
|
|
|
|
Enable) signal from any MCU that uses this signal for code |
|||
|
|
|
|
|
exclusively. If your MCU does not output a Program Select |
|||
|
|
|
|
|
Enable signal, this port can be used as a generic input. This |
|||
|
|
|
|
|
port is connected to the PLDs. |
|||
|
|
|
|
|
|
|
|
|
|
48 |
I |
Active low reset input. Resets I/O Ports and some of the |
|||||
|
Reset |
|
||||||
|
|
|
|
|
configuration registers. Must be active at power up. |
|||
|
|
|
|
|
|
|
|
|
|
PA0 |
29 |
I/O |
These pins make up Port A. These port pins are configurable |
||||
|
PA1 |
28 |
|
and can have the following functions: |
||||
|
PA2 |
27 |
|
1. |
MCU I/O — write to or read from a standard output or |
|||
|
PA3 |
25 |
|
|
input port. |
|||
|
|
2. |
General Purpose PLD outputs. |
|||||
|
PA4 |
24 |
|
|||||
|
|
3. |
Inputs to the PLDs. |
|||||
|
PA5 |
23 |
|
|||||
|
|
4. |
Latched address outputs (see Table 6). |
|||||
|
PA6 |
22 |
|
|||||
|
|
5. |
Address inputs. For example, PA0-3 could be used for |
|||||
|
PA7 |
21 |
|
|||||
|
|
|
A[0:3] when using an 80C51XA in burst mode. |
|||||
|
|
|
|
|
|
|||
|
|
|
|
|
6. |
As the data bus inputs D[0:7] for non-multiplexed |
||
|
|
|
|
|
|
address/data bus MCUs. |
||
|
|
|
|
|
7. |
D0/A16-D3/A19 in M37702M2 mode. |
||
|
|
|
|
|
Note: PA0-3 can only output CMOS signals with an option |
|||
|
|
|
|
|
for high slew rate. However, PA4-7 can be configured as |
|||
|
|
|
|
|
CMOS or Open Drain Outputs. |
|||
|
|
|
|
|
|
|
|
|
|
PB0 |
7 |
I/O |
These pins make up Port B. These port pins are configurable |
||||
|
PB1 |
6 |
|
and can have the following functions: |
||||
|
PB2 |
5 |
|
1. |
MCU I/O — write to or read from a standard output or |
|||
|
PB3 |
4 |
|
|
input port. |
|||
|
3 |
|
2. |
General Purpose PLD outputs. |
||||
|
PB4 |
|
||||||
|
2 |
|
3. |
Inputs to the PLDs. |
||||
|
PB5 |
|
||||||
|
52 |
|
4. |
Latched address outputs (see Table 6). |
||||
|
PB6 |
|
||||||
|
51 |
|
Note: PB0-3 can only output CMOS signals with an option |
|||||
|
PB7 |
|
||||||
|
|
|
for high slew rate. However, PB4-7 can be configured as |
|||||
|
|
|
|
|
||||
|
|
|
|
|
CMOS or Open Drain Outputs. |
|||
|
|
|
|
|
|
|
|
|
|
PC0 |
20 |
I/O |
PC0 pin of Port C. This port pin can be configured to have |
||||
|
|
|
|
|
the following functions: |
|||
|
|
|
|
|
1. |
MCU I/O — write to or read from a standard output or |
||
|
|
|
|
|
|
input port. |
||
|
|
|
|
|
2. |
Input to the PLDs. |
||
|
|
|
|
|
3. |
TMS Input for the JTAG Interface. |
||
|
|
|
|
|
This pin can be configured as a CMOS or Open Drain output. |
|||
|
|
|
|
|
|
|
|
|
|
PC1 |
19 |
I/O |
PC1 pin of Port C. This port pin can be configured to have |
||||
|
|
|
|
|
the following functions: |
|||
|
|
|
|
|
1. |
MCU I/O — write to or read from a standard output or |
||
|
|
|
|
|
|
input port. |
||
|
|
|
|
|
2. |
Input to the PLDs. |
||
|
|
|
|
|
3. |
TCK Input for the JTAG Interface. |
||
|
|
|
|
|
This pin can be configured as a CMOS or Open Drain output. |
|||
|
|
|
|
|
|
|
|
|
11
PSD9XX Family |
Preliminary Information |
Table 5.
PSD9XX Pin
Descriptions
(cont.)
Pin Name |
Pin* |
Type |
|
|
|
Description |
|
(PLCC) |
|
|
|
|
|
|
|
|
|
|
|
|
PC2 |
18 |
I/O |
PC2 pin of Port C. This port pin can be configured to have |
|||
|
|
|
the following functions: |
|||
|
|
|
1. |
MCU I/O — write to or read from a standard output or |
||
|
|
|
|
input port. |
||
|
|
|
2. |
Input to the PLDs. |
||
|
|
|
3. |
Vstby — SRAM standby voltage input for SRAM battery |
||
|
|
|
|
backup. |
||
|
|
|
This pin can be configured as a CMOS or Open Drain output. |
|||
|
|
|
|
|
|
|
PC3 |
17 |
I/O |
PC3 pin of Port C. This port pin can be configured to have |
|||
|
|
|
the following functions: |
|||
|
|
|
1. |
MCU I/O — write to or read from a standard output or |
||
|
|
|
|
input port. |
||
|
|
|
2. |
Input to the PLDs. |
||
|
|
|
|
|
|
|
|
|
|
3. |
TSTAT output for the JTAG interface. |
||
|
|
|
4. |
Rdy/Bsy output for in-system parallel programming. |
||
|
|
|
This pin can be configured as a CMOS or Open Drain output. |
|||
|
|
|
|
|
|
|
PC4 |
14 |
I/O |
PC4 pin of Port C. This port pin can be configured to have |
|||
|
|
|
the following functions: |
|||
|
|
|
1. |
MCU I/O — write to or read from a standard output or |
||
|
|
|
|
input port. |
||
|
|
|
2. |
Input to the PLDs. |
||
|
|
|
|
|
|
|
|
|
|
3. |
TERR output for the JTAG interface. |
||
|
|
|
4. |
Vbaton — battery backup indicator output. Goes high |
||
|
|
|
|
when power is being drawn from an external battery. |
||
|
|
|
This pin can be configured as a CMOS or Open Drain output. |
|||
|
|
|
|
|
|
|
PC5 |
13 |
I/O |
PC5 pin of Port C. This port pin can be configured to have |
|||
|
|
|
the following functions: |
|||
|
|
|
1. |
MCU I/O — write to or read from a standard output or |
||
|
|
|
|
input port. |
||
|
|
|
2. |
Input to the PLDs. |
||
|
|
|
3. |
TDI input for the JTAG interface. |
||
|
|
|
This pin can be configured as a CMOS or Open Drain output. |
|||
|
|
|
|
|
|
|
PC6 |
12 |
I/O |
PC6 pin of Port C. This port pin can be configured to have |
|||
|
|
|
the following functions: |
|||
|
|
|
1. |
MCU I/O — write to or read from a standard output or |
||
|
|
|
|
input port. |
||
|
|
|
2. |
Input to the PLDs. |
||
|
|
|
3. |
TDO output for the JTAG interface. |
||
|
|
|
This pin can be configured as a CMOS or Open Drain output. |
|||
|
|
|
|
|
|
|
12
Preliminary Information |
PSD9XX Family |
Table 5.
PSD9XX Pin
Descriptions
(cont.)
Pin Name |
Pin* |
Type |
|
|
Description |
|
|
(PLCC) |
|
|
|
|
|
PC7 |
11 |
I/O |
PC7 pin of Port C. This port pin can be configured to have |
|
||
|
|
|
the following functions: |
|
||
|
|
|
1. |
MCU I/O — write to or read from a standard output or |
|
|
|
|
|
|
input port. |
|
|
|
|
|
2. |
Input to the PLDs. |
|
|
|
|
|
3. |
DBE — active-low Data Byte Enable input from 68HC912 |
|
|
|
|
|
|
type MCUs. |
|
|
|
|
|
This pin can be configured as a CMOS or Open Drain output. |
|
||
|
|
|
|
|
|
|
PD0 |
10 |
I/O |
PD0 pin of Port D. This port pin can be configured to have |
|
||
|
|
|
the following functions: |
|
||
|
|
|
1. |
ALE/AS input latches address output from the MCU. |
|
|
|
|
|
2. |
MCU I/O — write or read from a standard output or input |
|
|
|
|
|
|
port. |
|
|
|
|
|
3. |
Input to the PLDs. |
|
|
|
|
|
4. |
General Purpose PLD output. |
|
|
|
|
|
|
|
|
|
PD1 |
9 |
I/O |
PD1 pin of Port D. This port pin can be configured to have |
|
||
|
|
|
the following functions: |
|
||
|
|
|
1. |
MCU I/O — write to or read from a standard output or |
|
|
|
|
|
|
input port. |
|
|
|
|
|
2. |
Input to the PLDs. |
|
|
|
|
|
3. |
General Purpose PLD output |
|
|
|
|
|
4. |
CLKIN — clock input to the automatic power-down |
|
|
|
|
|
|
unit’s power-down counter, and the PLD AND array. |
|
|
|
|
|
|
|
|
|
PD2 |
8 |
I/O |
PD2 pin of Port D. This port pin can be configured to have |
|
||
|
|
|
the following functions: |
|
||
|
|
|
1. |
MCU I/O — write to or read from a standard output or |
|
|
|
|
|
|
input port. |
|
|
|
|
|
2. |
Input to the PLDs. |
|
|
|
|
|
3. |
General Purpose PLD output. |
|
|
|
|
|
4. |
CSI |
— chip select input. When low, the MCU can access |
|
|
|
|
|
the PSD memory and I/O. When high, the PSD memory |
|
|
|
|
|
|
blocks are disabled to conserve power. |
|
|
|
|
|
|
|
|
|
VCC |
15, 38 |
|
Power pins |
|
||
GND |
1,16,26 |
|
Ground pins |
|
||
|
|
|
|
|
|
|
*The pin numbers in this table are for the PLCC package only. See the package information section for pin numbers on other package types.
Table 6. I/O Port Latched Address Output Assignments*
|
Port A |
Port B |
|||
Microcontroller |
Port A (3:0) |
Port A (7:4) |
Port B (3:0) |
Port B (7:4) |
|
|
|
|
|
|
|
8051XA (8-bit) |
N/A |
Address [7:4] |
Address [11:8] |
N/A |
|
|
|
|
|
|
|
80C251 (page mode) |
N/A |
N/A |
Address [11:8] |
Address [15:12] |
|
|
|
|
|
|
|
All other 8-bit |
Address [3:0] |
Address [7:4] |
Address [3:0] |
Address [7:4] |
|
multiplexed |
|||||
|
|
|
|
||
|
|
|
|
|
|
8-bit non-multiplexed |
N/A |
N/A |
Address [3:0] |
Address [7:4] |
|
bus |
|||||
|
|
|
|
N/A = Not Applicable
**Refer to the I/O Port Section on how to enable the Latched Address Output function.
13
PSD9XX Family |
Preliminary Information |
8.0
PSD9XX
Register Description and Address Offset
Table 7 shows the offset addresses to the PSD9XX 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 PSD9XX registers. Table 7 provides brief descriptions of the registers in CSIOP space. For a more detailed description, refer to section 9.
Table 7. Register Address Offset
Register Name |
Port A |
Port B |
Port C |
Port D |
Other* |
Description |
Data In |
00 |
01 |
10 |
11 |
|
Reads Port pin as input, |
|
MCU I/O input mode |
|||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Control |
02 |
03 |
|
|
|
Selects mode between |
|
|
|
MCU I/O or Address Out |
|||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Stores data for output |
Data Out |
04 |
05 |
12 |
13 |
|
to Port pins, MCU I/O |
|
|
|
|
|
|
output mode |
|
|
|
|
|
|
|
Direction |
06 |
07 |
14 |
15 |
|
Configures Port pin as |
|
input or output |
|||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Configures Port pins as |
|
|
|
|
|
|
either CMOS or Open |
Drive Select |
08 |
09 |
16 |
17 |
|
Drain on some pins, while |
|
|
|
|
|
|
selecting high slew rate |
|
|
|
|
|
|
on other pins. |
|
|
|
|
|
|
|
Flash Protection |
|
|
|
|
C0 |
Read only – Flash Sector |
|
|
|
|
Protection |
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Secondary Flash |
|
|
|
|
|
Read only – PSD Security |
|
|
|
|
C2 |
and Secondary Flash |
|
Protection |
|
|
|
|
||
|
|
|
|
|
Sector Protection |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
PMMR0 |
|
|
|
|
B0 |
Power Management |
|
|
|
|
Register 0 |
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
PMMR2 |
|
|
|
|
B4 |
Power Management |
|
|
|
|
Register 2 |
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Page |
|
|
|
|
E0 |
Page Register |
|
|
|
|
|
|
|
|
|
|
|
|
|
Places PSD memory |
VM |
|
|
|
|
E2 |
areas in Program and/or |
|
|
|
|
Data space on an |
||
|
|
|
|
|
|
|
|
|
|
|
|
|
individual basis. |
|
|
|
|
|
|
|
*Other registers that are not part of the I/O ports.
14
Preliminary Information |
PSD9XX Family |
9.0 The PSD9XX
Functional Blocks
As shown in Figure 1, the PSD9XX consists of six major types of functional blocks:
Memory Blocks
PLD Blocks
Bus Interface
I/O Ports
Power Management Unit
JTAG 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 PSD9XX 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 8 summarizes which versions of the PSD9XX contain which memory blocks.
Table 8. Memory Blocks
|
Main Flash |
Secondary Flash Block |
|
||
Device |
Flash Size |
Sector Size |
Block Size |
Sector Size |
SRAM |
PSD913F2 |
128KB |
16KB |
32KB |
8KB |
2KB |
|
|
|
|
|
|
PSD934F2 |
256KB |
32KB |
32KB |
8KB |
8KB |
|
|
|
|
|
|
PSD954F2 |
256KB |
32KB |
32KB |
8KB |
32KB |
|
|
|
|
|
|
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 byte-by-byte. 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 C3. This pin is set up using PSDsoft.
15
PSD9XX Family |
Preliminary Information |
The PSD9XX Functional Blocks
(cont.)
9.1.1.1 Memory Block Selects
The decode PLD in the PSD9XX 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 with separate Program and Data space, these flexible select signals allow dynamic re-mapping of sectors from one space to the other when used with the VM Register (see section 9.1.3.1).
9.1.1.2 The Ready/Busy Pin (PC3)
Pin PC3 can be used to output the Ready/Busy status of the PSD9XX. 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.
9.1.1.3 Memory Operation
The main Flash and secondary Flash memories are addressed through the microcontroller interface on the PSD9XX 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 9.
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 byte directly to Flash memory as one would write a byte to RAM. To program a byte 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 (PC3).
The Flash memory can also be read by using special instructions to retrieve particular Flash device information (sector protect status and ID).
16
Preliminary Information |
PSD9XX Family |
The PSD9XX Functional Blocks
(cont.)
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 PSD9XX main Flash and Secondary Flash support these instructions (see Table 9):
Erase memory by chip or sector
Suspend or resume sector erase
Program a byte
Reset to read array mode
Read Main Flash Identifier value
Read sector protection status
Bypass Instruction (PSD934F2 and PSD954F2 only)
These instructions are detailed in Table 9. 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 AAh to address X555h during the first cycle and data 55h to address XAAAh during the second cycle. 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.
17
PSD9XX Family |
Preliminary Information |
The PSD9XX Functional Blocks
(cont.)
Table 9. Instructions
|
FS0-7 |
|
|
|
|
|
|
|
|
or |
|
|
|
|
|
|
|
Instruction |
CSBOOT0-3 |
Cycle 1 |
Cycle 2 |
Cycle 3 |
Cycle 4 |
Cycle5 |
Cycle 6 |
Cycle 7 |
|
|
|
|
|
|
|
|
|
Read (Note 5) |
1 |
“Read” |
|
|
|
|
|
|
|
|
RA RD |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Read Main Flash ID |
1 |
AAh |
55h |
90h |
“Read” |
|
|
|
(Notes 6,13) |
|
@555h |
@AAAh |
@555h |
ID |
|
|
|
|
|
|
|
|
@x01h |
|
|
|
|
|
|
|
|
|
|
|
|
Read Sector Protection |
1 |
AAh |
55h |
90h |
“Read” |
|
|
|
(Notes 6,8,13) |
|
@555h |
@AAAh |
@555h |
00h or 01h |
|
|
|
|
|
|
|
|
@x02h |
|
|
|
|
|
|
|
|
|
|
|
|
Program a Flash Byte |
1 |
AAh |
55h |
A0h |
PD@PA |
|
|
|
|
|
@555h |
@AAAh |
@555h |
|
|
|
|
|
|
|
|
|
|
|
|
|
Erase One Flash Sector |
1 |
AAh |
55h |
80h |
AAh |
55h |
30h |
30h |
|
|
@555h |
@AAAh |
@555h |
@555h |
@AAAh |
@SA |
@next SA |
|
|
|
|
|
|
|
|
(Note 7) |
|
|
|
|
|
|
|
|
|
Erase Flash Block |
1 |
AAh |
55h |
80h |
AAh |
55h |
10h |
|
(Bulk Erase) |
|
@555h |
@AAAh |
@555h |
@555h |
@AAAh |
@555h |
|
|
|
|
|
|
|
|
|
|
Suspend Sector Erase |
1 |
B0h |
|
|
|
|
|
|
(Note 11) |
|
@xxxh |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Resume Sector Erase |
1 |
30h |
|
|
|
|
|
|
(Note 12) |
|
@xxxh |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Reset (Note 6) |
1 |
F0 @ any |
|
|
|
|
|
|
|
|
address |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Unlock Bypass |
1 |
AAh |
55h |
20h |
|
|
|
|
(Note 14) |
|
@555h |
@AAAh |
@555h |
|
|
|
|
|
|
|
|
|
|
|
|
|
Unlock Bypass Program |
1 |
A0h |
PD@PA |
|
|
|
|
|
(Note 9,14) |
|
@xxxh |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Unlock Bypass Reset |
1 |
90h |
00h |
|
|
|
|
|
(Note 10,14) |
|
@xxxh |
@xxxh |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
X = Don’t Care.
RA = Address of the memory location to be read.
RD = Data read from location RA during read operation.
PA = Address of the memory location to be programmed. Addresses are latched on the falling edge of the WR# (CNTL0) pulse.
PD = Data to be programmed at location PA. Data is latched o the rising edge of WR# (CNTL0) pulse.
SA = 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:
1.All bus cycles are write bus cycle except the ones with the “read” label.
2.All values are in hexadecimal.
3.FS0-7 and CSBOOT0-3 are active high and are defined in PSDsoft.
4.Only Address bits A11-A0 are used in Instruction decoding. A15-12 (or A16-A12) are don’t care.
5.No unlock or command cycles required when device is in read mode.
6.The Reset command is required to return to the read mode after reading the Flash ID, Sector Protect status or if DQ5 (error flag) goes high.
7.Additional sectors to be erased must be entered within 80µs.
8.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).
9.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 block when reading the Sector Protection Status of the main Flash.
14.Available to PSD934F2 and PSD954F2 devices only.
18
Preliminary Information |
PSD9XX Family |
The PSD9XX Functional Blocks
(cont.)
9.1.1.4 Power-Up Condition
The PSD9XX Flash memory 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 a byte 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 Secondary Flash memories are placed in the read array mode after power-up, chip reset, or a Reset Flash instruction (see Table 9). 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 9). During the read operation,
address bits A6, A1, and A0 must be 0,0,1, respectively, and the appropriate sector select signal (FSi) must be active. The PSD9XX main Flash memory ID is E7h (PSD934/954F2) and E4h (PSD913F2).
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 9). During the read operation, address bits A6, A1, and A0 must be 0,1,0, respectively, while the chip select (FSi or CSBOOTi) designates the Flash sector whose protection has to be verified. 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 Secondary Flash 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 PSD9XX 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 10. The status bits can be read as many times as needed.
Table 10. Status Bits
|
FSi/ |
|
|
|
|
|
|
|
|
|
|
CSBOOTi |
DQ7 |
DQ6 |
DQ5 |
DQ4 |
DQ3 |
DQ2 |
DQ1 |
DQ0 |
|
|
|
Data |
Toggle |
Error |
|
Erase |
|
|
|
|
Flash |
VIH |
X |
Time- |
X |
X |
X |
||||
Polling |
Flag |
Flag |
||||||||
|
|
|
|
|
|
out |
|
|
|
NOTES: 1. X = Not guaranteed value, can be read either 1 or 0.
2.DQ7-DQ0 represent the Data Bus bits, D7-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. See section 9.1.1.7 for details.
19
PSD9XX Family |
Preliminary Information |
The PSD9XX Functional Blocks
(cont.)
9.1.1.5.5 Data Polling Flag DQ7
When Erasing or Programming the Flash memory bit DQ7 outputs the complement of the bit being entered for Programming/Writing on DQ7. Once the Program instruction or the Write operation is completed, the true logic value is read on DQ7 (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 outputs a ‘0’. After completion of the instruction, DQ7 will output the last bit programmed (it is a ‘1’ after erasing).
If the byte to be programmed is in a protected Flash sector, the instruction is ignored.
If all the Flash sectors to be erased are protected, DQ7 will be set to ‘0’ for about 100 µs, and then return to the previous addressed byte. No erasure will be performed.
9.1.1.5.6 Toggle Flag DQ6
The PSD9XX 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 will toggle from ‘0’ to ‘1’ and ‘1’ to ‘0’ on subsequent attempts to read any byte of the memory.
When the internal cycle is complete, the toggling will stop and the data read on the Data Bus D0-7 is the addressed memory byte. 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 byte to be programmed belongs to a protected Flash sector, the instruction is ignored.
If all the Flash sectors selected for erasure are protected, DQ6 will toggle to ‘0’ for about 100 µs and then return to the previous addressed byte.
9.1.1.5.7 Error Flag DQ5
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 byte 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 byte.
In case of an error in Flash sector erase or byte program, the Flash sector in which the error occurred or to which the programmed byte belongs must no longer be used. Other Flash sectors may still be used. The Error bit resets after the Reset instruction.
9.1.1.5.8Erase Time-out Flag DQ3
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 is set to ‘1’.
20
Preliminary Information |
PSD9XX Family |
The PSD9XX Functional Blocks
(cont.)
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, but not byte-by-byte. A byte of Flash memory erases to all logic ones (FF hex), and its bits are programmed to logic zeros. Although erasing Flash memory occurs on a sector basis, programming Flash memory occurs on a byte basis.
The PSD9XX main Flash and Secondary Flash memories require the MCU to send an instruction to program a byte or perform an erase function (see Table 9).
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 PSD9XX 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 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 PSD9XX begins. The MCU then reads the location of the byte to be programmed in Flash to check status. Data bit DQ7 of this location becomes the compliment of data bit 7of the original data byte to be programmed. The MCU continues to poll this location, comparing DQ7 and monitoring the Error bit on DQ5. When the DQ7 matches data bit 7 of the original data, and the Error bit at DQ5 remains ‘0’, then the embedded algorithm is complete.
If the Error bit at DQ5 is ‘1’, the MCU should test DQ7 again since DQ7 may have changed simultaneously with DQ5 (see Figure 3).
The Error bit at DQ5 will be set if either an internal timeout occurred while the embedded algorithm attempted to program the byte 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 byte that was written to Flash with the byte that was intended to be written.
When using the Data Polling method after an erase instruction, Figure 3 still applies. However, DQ7 will be ‘0’ until the erase operation is complete. A ‘1’ on DQ5 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 and DQ5.
PSDsoft will generate ANSI C code functions which implement these Data Polling algorithms.
21
PSD9XX Family |
Preliminary Information |
The PSD9XX Functional Blocks
(cont.)
Figure 3. Data Polling Flow Chart
START
READ DQ5 & DQ7
at Valid Address
|
DQ7 |
YES |
||
|
= |
|
|
|
|
DATA7 |
|
|
|
|
|
NO |
|
|
|
|
|
|
|
NO |
|
|
|
|
DQ5 |
|
|
||
|
=1 |
|
|
|
|
|
YES |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
READ DQ7 |
|
|
|
|
|
|
|
|
DQ7 |
YES |
|
|
|||
= |
|
|
|
|
|
|
|
|
|
|
|
||
DATA |
|
|
|
|
||
|
NO |
|
|
|
|
|
|
|
|
|
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
FAIL |
|
|
PASS |
|||
Program/Erase |
|
|
||||
|
|
Program/Erase |
||||
Operation Not |
|
|
||||
|
|
Operation is |
||||
Complete, Issue |
|
|||||
|
Complete |
|||||
Reset Instruction |
|
|||||
|
|
|
||||
|
|
|
|
|
|
|
9.1.1.6.2 Data Toggle
Checking the Data Toggle bit on DQ6 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 PSD9XX begins. The MCU then reads the location of the byte to be programmed in Flash to check status. Data bit DQ6 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 and monitoring the Error bit on DQ5. When DQ6 stops toggling (two consecutive reads yield the same value), and the Error bit on DQ5 remains ‘0’, then the embedded algorithm is complete. If the Error bit on DQ5 is ‘1’, the MCU should test DQ6 again, since DQ6 may have changed simultaneously with DQ5 (see Figure 4).
The Error bit at DQ5 will be set if either an internal timeout occurred while the embedded algorithm attempted to program the byte, or if the MCU attempted to program a ‘1’ to a bit that was not erased (not erased is logic ‘0’).
22
Preliminary Information |
PSD9XX Family |
The PSD9XX Functional Blocks
(cont.)
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 byte that was written to Flash with the byte that was intended to be written.
When using the Data Toggle method after an erase instructin, Figure 4 still applies. DQ6 will toggle until the erase operation is complete. A ‘1’ on DQ5 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 DQ6 and DQ5.
PSDsoft will generate ANSI C code functions which implement these Data Toggling algorithms.
Figure 4. Data Toggle Flow Chart
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
START |
|
|
|
|
|
|
|
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
READ |
|
|
|
|
|
|
||||
|
|
|
|
DQ5 & DQ6 |
|
|
|
|
|
|
||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|||
|
|
|
|
DQ6 |
NO |
|
|
|
|
|||||
|
|
|
= |
|
|
|
|
|
|
|||||
|
|
|
|
TOGGLE |
|
|
|
|
|
|
|
|||
|
|
|
|
|
|
YES |
|
|
|
|
|
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|||
|
NO |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
DQ5 |
|
|
|
|
|
|
||||||
|
|
|
|
|
|
|
|
|
|
|||||
|
|
|
|
=1 |
|
|
|
|
|
|
|
|
||
|
|
|
|
|
|
YES |
|
|
|
|
|
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
READ DQ6 |
|
|
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|
|
|
|||
|
|
|
|
DQ6 |
NO |
|
|
|
|
|||||
|
|
|
= |
|
|
|
|
|
|
|||||
|
|
|
|
TOGGLE |
|
|
|
|
|
|
|
|||
|
|
|
|
|
|
YES |
|
|
|
|
|
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|
|
||||
|
|
|
|
FAIL |
|
|
PASS |
|
||||||
|
|
|
Program/Erase |
|
|
|
||||||||
|
|
|
|
|
Program/Erase |
|
||||||||
|
|
|
|
Operation Not |
|
|
|
|||||||
|
|
|
|
|
|
Operation is |
|
|||||||
|
|
|
Complete, Issue |
|
|
|
||||||||
|
|
|
|
|
Complete |
|
||||||||
|
|
|
Reset Instruction |
|
|
|||||||||
|
|
|
|
|
|
|
|
|||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
23
PSD9XX Family |
Preliminary Information |
The PSD9XX Functional Blocks
(cont.)
9.1.1.7 Unlock Bypass Instruction (PSD934F2 and PSD954F2 only)
The unlock bypass feature allows the system to program bytes 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 9). 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 requiredc in the standard program instruction, resulting in faster total programming 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 falsh 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 9. 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, as detailed in section 9.1.1.6. The Error bit (DQ5) 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 PSD9XX 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 9. 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 (Erase time-out bit). If DQ3 is ‘0’, the Sector Erase instruction has been received and the timeout is counting. If DQ3 is ‘1’, the timeout has expired and the PSD9XX 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 PSD9XX will do this automatically before erasing (byte=FFh).
During a Sector Erase, the memory status may be checked by reading status bits DQ5, DQ6, and DQ7, 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.
24
Preliminary Information |
PSD9XX Family |
The PSD9XX 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 address when an appropriate Chip Select (FSi or CSBOOTi) is true. (See Table 9). 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 PSD9XX 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 PSD9XX 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 address while an appropriate Chip Select (FSi or CSBOOTi) is true. (See Table 9.)
9.1.1.9 Specific Features
9.1.1.9.1 Flash and Secondary Flash Sector Protect
Each Flash and Secondary Flash sector 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 through the JTAG Port or a Device Programmer.
Sector protection can be selected for each sector using the PSDsoft Configuration 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 be read by the MCU through the Flash protection and Secondary Flash protection registers (CSIOP). See Table 11.
25