View PSD913F1_5016722.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

1/3 preliminary data january 2002 this is preliminary information on a new product now in development or undergoing evaluation. details are subject to change wit hout notice. PSD913F1 flash in-system programmable (isp) peripherals for 8-bit mcus features summary single supply voltage: C 5 v10% for PSD913F1 C 3.3 v10% for PSD913F1-v up to 1mbit of primary flash memory (8 uniform sectors) 256kbit secondary eeprom (4 uniform sectors) up to 16kbit sram over 2,000 gates of pld: dpld 27 reconfigurable i/o ports enhanced jtag serial port programmable power management high endurance: C 100,000 erase/write cycles of flash memory C 10,000 erase/write cycles of eeprom C 1,000 erase/write cycles of pld figure 1. packages plcc52 (k) pqfp52 (t)
1 1.0 introduction preliminary programmable peripheral revision a flash psd PSD913F1 flash in-system-programmable microcontroller peripherals the PSD913F1 family 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. PSD913F1 devices combine many of the peripheral functions found in mcu based applications: 1 mbit of flash memory a second eeprom memory over 2,000 gates of flash programmable logic up to 16kbit sram reconfigurable i/o ports programmable power management.
PSD913F1 preliminary 2 1.0 introduction (cont.) the PSD913F1 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 (flash memory, eeprom, 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 memory arrays (flash and eeprom) 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 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 or eeprom memory while it resides in ?rogram?space during field firmware updates, my mcu won? allow it! the flash psd provides means to ?eclassify?flash or eeprom memory as ?ata?space during iap, then back to ?rogram?space when complete. psdsoft express ?sts 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 genera- tion 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 PSD913F1 is available in 52-pin plcc and pqfp packages as well as a 64-pin tqfp package.
preliminary PSD913F1 3 a simple interface to 8-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 8031, 80196, 80186, 80c251, and 80386ex motorola 68hc11, 68hc16, 68hc12, and 683xx philips 8031 and 8051xa zilog z80 and z8 internal 1 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 eeprom 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 kbit scratchpad sram. the srams contents can be protected from a power failure by connecting an external battery. optional 64 byte one time programmable (otp) memory that can be used for product configuration and calibration. 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, 25 a for 3 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 PSD913F1 into power down mode. erase/write cycles: flash memory ?100,000 minimum eeprom ?10,000 minimum pld ?1,000 minimum data retention: 15 year minimum at 90 degrees celsius (for main flash, boot, pld and configuration bits). 2.0 key features
PSD913F1 preliminary 4 prog. mcu bus intrf. adio port cntl0, cntl1, cntl2 ad0 ad15 pld input bus prog. port port a prog. port port b power mangmt unit 1 or 2 mbit main flash memory 8 sectors vstdby pa0 pa7 pb0 pb7 prog. port port c prog. port port d pc0 pc7 pd0 pd2 address/data/control bus 57 57 256 kbit secondary eeprom memory (boot or data) 4 sectors 16 kbit battery backup sram runtime control and i/o registers sram select i/o port pld input gpld output gpld output gpld output csiop flash isp pld (gpld) flash decode pld ( dpld ) pld, configuration & flash memory loader jtag serial channel ( pc2 ) page register embedded algorithm sector selects sector selects global config. & security figure 1. PSD913F1 block diagram
preliminary PSD913F1 5 3.0 general information the PSD913F1 series architecture allows in-system programming of all memory, pld logic and device configuration.the devices eliminate the need for discrete ?lue?logic, and allow the development of entire systems using only a few highly integrated devices. 4.0 PSD913F1 family all PSD913F1 devices provide these base features: 1 mbit main flash memory, jtag port, gpld, dpld, power management, and 27 i/o pins. the PSD913F1 also adds 64 bytes of otp memory for any use (product serial number, calibration constants, etc.). once written, the otp memory can never be altered. the following table summarizes the PSD913F1: part # flash additional no. of serial isp main memory memory for PSD913F1 i/o gpld jtag/isc kbit boot and/or data sram turbo supply family device pins output port (8 sectors) (4 sectors) kbit mode voltage PSD913F1 PSD913F1 27 19 yes 1024 256 kbit eeprom 16 yes 5v PSD913F1v PSD913F1v 27 19 yes 1024 256 kbit eeprom 16 yes 3v table 1. PSD913F1 product matrix
PSD913F1 preliminary 6 PSD913F1 devices contain several major functional blocks. figure 1 on page 3 shows the architecture of the PSD913F1 device. the functions of each block are described briefly in the following sections. many of the blocks perform multiple functions and are user config- urable. 5.1 memory the PSD913F1 contains the following memories: a 1 mbit flash a secondary 256 kbit eeprom memory a 16 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 mbit flash is the main memory of the PSD913F1. it is divided into eight equally-sized sectors that are individually selectable. the 256 kbit eeprom or flash is divided into four equally-sized sectors. each sector is individually selectable. the 16 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 PSD913F1s 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 for in-circuit reprogramming. 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 PSD913F1 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 (zpsd only) 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 zpsd features. 5.0 PSD913F1 architectural overview name abbreviation inputs outputs product terms decode pld dpld 57 15 39 general purpose pld gpld 57 19 114 table 2. pld i/o table
preliminary PSD913F1 7 PSD913F1 architectural overview (cont.) 5.4 i/o ports the PSD913F1 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 PSD913F1 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 microcontrollers 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 PSD913F1 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. port c pins jtag signal pc0 tms pc1 tck pc3 tstat pc4 terr pc5 tdi pc6 tdo table 3. jtag signals on port c
PSD913F1 preliminary 8 5.7 in-system programming using the jtag signals on port c, the entire PSD913F1 device can be programmed or erased without the use of the microcontroller. the main flash memory can also be programmed in-system by the microcontroller executing the programming algorithms out of the eeprom or sram. the eeprom can be programmed the same way by executing out of the main flash memory. the pld logic or other PSD913F1 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 PSD913F1. PSD913F1 architectural overview (cont.) jtag device in-system parallel functional block programming programmer programming main flash memory yes yes yes eeprom memory yes yes yes pld array (dpld and gpld) yes yes no psd configuration yes yes no optional otp row no yes yes table 4. methods of programming different functional blocks of the PSD913F1 5.8 power management unit the power management unit (pmu) in the PSD913F1 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 PSD913F1 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 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 gpld to reduce power consumption. see section 9.5.
preliminary PSD913F1 9 6.0 development system define psd pin and node functions merge mcu firmware with psd configuration st psd programmer *.obj file point and click definition of psd pin functions, internal nodes, and mcu system memory map. psdpro or flashlink (jtag) a composite object file is created containing mcu firmware and psd configuration. choose mcu and psd automatically configures mcu bus interface and other psd attributes. c code generation generate c code specific to psd functions. user's choice of microcontroller compiler/linker *.obj file available for 3rd party programmers. (conventional or jtag-isc) mcu firmware hex or s-record format figure 2. psdsoft development tool the PSD913F1 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 PSD913F1 is also supported by third party device programmers, see web site for current list.
PSD913F1 preliminary 10 the following table describes the pin names and pin functions of the PSD913F1. pins that have multiple names and/or functions are defined using psdsoft. 7.0 table 5. PSD913F1 pin descriptions 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.
preliminary PSD913F1 11 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. reset 48 i active low reset input. resets i/o ports and some of the 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. pa4 24 2. general purpose pld outputs. pa5 23 3. inputs to the plds. pa6 22 4. latched address outputs (see table 6). pa7 21 5. address inputs. for example, pa0-3 could be used for 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. pb4 3 2. general purpose pld outputs. pb5 2 3. inputs to the plds. pb6 52 4. latched address outputs (see table 6). pb7 51 note: pb0-3 can only output cmos signals with an option 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. table 5. PSD913F1 pin descriptions (cont.)
PSD913F1 preliminary 12 table 5. PSD913F1 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.
preliminary PSD913F1 13 table 5. PSD913F1 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 units 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. v cc 15, 38 power pins gnd 1,16,26 ground pins 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 multiplexed address [3:0] address [7:4] address [3:0] address [7:4] 8-bit non-multiplexed bus n/a n/a address [3:0] address [7:4] table 6. i/o port latched address output assignments* n/a = not applicable * * refer to the i/o port section on how to enable the latched address output function. * * the pin numbers in this table are for the plcc package only. see the package information section for pin numbers on other package types.
PSD913F1 preliminary 14 table 7 shows the offset addresses to the PSD913F1 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 PSD913F1 registers. table 7 provides brief descriptions of the registers in csiop space. for a more detailed description, refer to section 9. 8.0 PSD913F1 register description and 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 psd/ee read only ?psd security protection c2 and eeprom 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. table 7. register address offset * other registers that are not part of the i/o ports.
preliminary PSD913F1 15 9.0 the PSD913F1 functional blocks as shown in figure 1, the PSD913F1 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 PSD913F1 has the following memory blocks: the main flash memory secondary eeprom memory sram. the memory select signals for these blocks originate from the decode pld (dpld) and are user-defined in psdsoft. table 8 summarizes the PSD913F1 memory blocks. device main flash eeprom sram PSD913F1 128kb 32kb 2kb table 8. memory blocks 9.1.1 main flash and secondary eeprom the 1 mbit main flash memory block is divided evenly into eight 16 kbyte sectors. the eeprom 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. eeprom may be programmed byte-by-byte or sector-by-sector, and erasing is automatic and transparent. the integrity of the data can be secured with the help of software data protection (sdp). any write operation to the eeprom is inhibited during the first five milliseconds following power-up. during a program or erase of flash, or during a write of the eeprom, the status can be output on the rdy/bsy pin of port c3. this pin is set up using psdsoft.
PSD913F1 preliminary 16 9.1.1.1 memory block selects the decode pld in the PSD913F1 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 eeprom memory sectors have a select signal (ees0-3 or 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 registers (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 PSD913F1. the output on the pin will be a ??(busy) when flash or eeprom memory blocks are being written to, or when the flash memory block is being erased. the output will be a ??(ready) when no write or erase operation is in progress. 9.1.1.3 memory operation the main flash and eeprom memory are addressed through the microcontroller interface on the PSD913F1 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 or eeprom 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). the eeprom is a bit different. data can be written to eeprom memory using write operations, like writing to a ram device, but the status of each write event must be checked by the microcontroller. a write event can be one to 64 contiguous bytes. the status test is very similar to that used for flash memory (read operation or rdy/busy). optionally, the eeprom memory may be put into a software data protect (sdp) mode where it requires instructions, rather than operations, to alter its contents. sdp mode makes writing to eeprom much like writing to flash memory. the PSD913F1 functional blocks (cont.)
preliminary PSD913F1 17 the PSD913F1 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). an invalid combination or time-out while addressing the eeprom block will cause the offending byte to be interpreted as a single operation. the PSD913F1 supports these instructions (see table 9): flash memory: erase memory by chip or sector suspend or resume sector erase program a byte reset to read array mode read flash identifier value read sector protection status eeprom: write data to otp row read data from otp row power down memory enable software data protect (sdp) disable sdp return from read otp row read mode or power down mode. 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? cares during the instruction write cycles. however, the appropriate sector select signal (fsi or eesi) must be selected.
PSD913F1 preliminary 18 flash eeprom sector sector select select (fsi) instruction (eesi) (note 2) cycle 1 cycle 2 cycle 3 cycle 4 cycle5 cycle 6 cycle 7 read read aah 55h 90h identifier flash 01 @x555h @xaaah @x555h with identifier (a6,a1,a0 (note 3, 5) at 0,0,1) read otp row 1 0 aah 55h 90h read read read (note 4) @x555h @xaaah @x555h byte 1 byte 2 byte n read read sector aah 55h 90h identifier protection 01 @x555h @xaaah @x555h with status (a6,a1,a0 (notes 3, 5) at 0,1,0) program a 0 1 aah 55h a0h data flash byte @x555h @xaaah @x555h @ address (note 5) erase one aah 55h 80h aah 55h 30h 30h flash sector 0 1 @x555h @xaaah @x555h @x555h @xaaah @ sector @ sector (note 5) address address(1) erase the 0 1 aah 55h 80h aah 55h 10h whole flash @x555h @xaaah @x555h @x555h @xaaah @x555h (note 5) suspend sector b0h erase 0 1 @ any (note 5) address resume 30h sector erase 0 1 @ any (note 5) address eeprom power 10 aah 55h 30h down (note 4) @x555h @xaaah @x555h sdp enable/ 1 0 aah 55h a0h write write write eeprom write @x555h @xaaah @x555h byte 1 byte 2 byte n (note 4) sdp disable 1 0 aah 55h 80h aah 55h 20h (note 4) @x555h @xaaah @x555h @x555h @xaaah @x555h write in otp 1 0 aah 55h b0h write write write row (notes 4, 6) @x555h @xaaah @x555h byte 1 byte 2 byte n return (from otp f0h @ read or eeprom 1 0 any power-down) address (note 4) aah 55h f0h reset 01 @x555h @xaaah @ any (notes 3, 5) address reset f0h (short instruction) 0 1 @ any (note 5) address table 9. instructions notes: 1. additional sectors to be erased must be entered within 80 s. a sector address is any address within the sector. 2. flash and eeprom sector selects are active high. addresses a15-a12 are don? cares in instruction bus cycles. 3. the reset instruction is required to return to the normal read array mode if dq5 goes high or after reading the flash identifier or protection status. 4. the mcu cannot invoke these instructions while executing code from eeprom. the mcu must be operating from some other memory when these instructions are performed. 5. the mcu cannot invoke these instructions while executing code from the same flash memory for which the instruction is intended. the mcu must operate from some other memory when these instructions are executed. 6. writing to otp row is allowed only when sdp mode is disabled. the PSD913F1 functional blocks (cont.)
preliminary PSD913F1 19 the PSD913F1 functional blocks (cont.) 9.1.1.4 power down instruction and power up condition 9.1.1.4.1 eeprom power down instruction the eeprom can enter power down mode with the help of the eeprom power down instruction (see table 9). once the eeprom power down instruction is decoded, the eeprom memory cannot be accessed unless a return instruction (also in table 9) is decoded. alternately, this power down mode will automatically occur when the apd circuit is triggered (see section 9.5.1). therefore, this instruction is not required if the apd circuit is used. 9.1.1.4.2 power-up condition the PSD913F1 flash memory is reset upon power-up to the read array mode. any write operation to the eeprom is inhibited during the first 5 msec following power-up. the fsi and eesi 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 v cc is below vlko. 9.1.1.5 read under typical conditions, the microcontroller may read the flash or eeprom memory 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 is 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 eeprom 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 flash id is e3h for the PSD913F1. the mcu can read the id only when it is executing from the eeprom. 9.1.1.5.3 read the main flash memory sector protection status the main 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 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 eeprom) can be read by the microcontroller accessing the flash protection and psd/ee protection registers in psd i/o space. see section 9.1.1.9.1 for register definitions.
PSD913F1 preliminary 20 9.1.1.5.4 read the otp row there are 64 bytes of one-time-programmable (otp) memory that reside in eeprom. these 64 bytes are in addition to the 32 kbytes of eeprom memory. a read of the otp row is done with an instruction composed of at least 4 operations: 3 specific write operations and one to 64 read operations (see table 9). during the read operation(s), address bit a6 must be zero, while address bits a5-a0 define the otp row byte to be read while any eeprom sector select signal (eesi) is active. after reading the last byte, an eeprom return instruction must be executed (see table 9). 9.1.1.5.5 read the erase/program status bits the PSD913F1 provides several status bits to be used by the microcontroller to confirm the completion of an erase or programming instruction of flash memory. bits are also available to show the status of writes to eeprom. 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. fsi/ csbooti eesi dq7 dq6 dq5 dq4 dq3 dq2 dq1 dq0 data toggle error erase flash v ih v il polling flag flag x time- x x x out eeprom v il v ih data toggle xxxxxx polling flag table 10. status bit 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 and eesi are active high. the PSD913F1 functional blocks (cont.) 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. for eeprom not in sdp mode, the microcontroller can perform a read operation to obtain these status bits just after a data write operation. the microcontroller may write one to 64 bytes before reading the status bits. see section 9.1.1.6 for details. for eeprom in sdp mode, the microcontroller will perform a read operation to obtain these status bits while an sdp write instruction is being executed by the embedded algorithm. see section 9.1.1.1.3 for details.
preliminary PSD913F1 21 the PSD913F1 functional blocks (cont.) 9.1.1.5.6 data polling flag dq7 when erasing or programming the flash memory (or when writing into the eeprom 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 ?? after completion of the instruction, dq7 will output the last bit programmed (it is a ??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 ??for about 100 s, and then return to the previous addressed byte. no erasure will be performed. 9.1.1.5.7 toggle flag dq6 the PSD913F1 offers another way for determining when the eeprom write or the flash memory program instruction is completed. during the internal write operation and when either the fsi or eesi is true, the dq6 will toggle from ??to ??and ??to ??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 ??for about 100 s and then return to the previous addressed byte. 9.1.1.5.8 error flag dq5 during a correct program or erase, the error bit will set to ?? this bit is set to ??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.9 erase time-out flag dq3 (flash memory only) the erase timer bit reflects the time-out period allowed between two consecutive sector erase instructions. the erase timer bit is set to ??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 ??
PSD913F1 preliminary 22 9.1.1.6 writing to the eeprom data may be written a byte at a time to the eeprom using simple write operations, much like writing to an sram. unlike sram though, the completion of each byte write must be checked before the next byte is written. to speed up this process, the PSD913F1 offers a page write feature to allow writing of several bytes before checking status. to prevent inadvertent writes to eeprom, the PSD913F1 offers a software data protect (sdp) mode. once enabled, sdp forces the mcu to ?nlock?the eeprom before altering its contents, much like flash memory programming. 9.1.1.6.1 write a byte to eeprom a write operation is initiated when an eeprom select signal (eesi) is true and the write strobe signal (wr) into the PSD913F1 is true. if the PSD913F1 detects no additional writes within 120 sec, an internal storage operation is initiated. internal storage to eeprom memory technology typically takes a few milliseconds to complete. the status of the write operation is obtained by the mcu reading the data polling or toggle bits (as detailed in section 9.1.1.5), or the ready/busy output pin (section 9.1.1.2). keep in mind that the mcu does not need to erase a location in eeprom before writing it. erasure is performed automatically as an internal process. 9.1.1.6.2 write a page to eeprom writing data to eeprom using page mode is more efficient than writing one byte at a time. the PSD913F1 eeprom has a 64 byte volatile buffer that the mcu may fill before an internal eeprom storage operation is initiated. page mode timing approaches a 64:1 advantage over the time it takes to write individual bytes. to invoke page mode, the mcu must write to eeprom locations within a single page, with no more than 120 sec between individual byte writes. a single page means that address lines a14 to a6 must remain constant. the mcu may write to the 64 locations on a page in any order, which is determined by address lines a5 to a0. as soon as 120 sec have expired after the last page write, the internal eeprom storage process begins and the mcu checks programming status. status is checked the same way it is for byte writes, described above. note: be aware that if the upper address bits (a14 to a6) change during page write operations, loss of data may occur. ensure that all bytes for a given page have been successfully stored in the eeprom before proceeding to the next page. correct management of mcu interrupts during eeprom page write operations is essential. 9.1.1.6.3 eeprom software data protect (sdp) the sdp feature is useful for protecting the contents of eeprom from inadvertent write cycles that may occur during uncontrolled mcu bus conditions. these may happen if the application software gets lost or when v cc is not within normal operating range. instructions from the mcu are used to enable and disable sdp mode (see table 9). once enabled, the mcu must write an instruction sequence to eeprom before writing data (much like writing to flash memory). sdp mode can be used for both byte and page writes to eeprom. the device will remain in sdp mode until the mcu issues a valid sdp disable instruction. PSD913F1 devices are shipped with sdp mode disabled. however, within psdsoft, sdp mode may be enabled as part of programming the device with a device programmer (psdpro). the PSD913F1 functional blocks (cont.)
preliminary PSD913F1 23 write aah to address 555h write 55h to address aaah write a0h to address 555h page write instruction sdp is set write aah to address 555h write 55h to address aaah write a0h to address 555h write data to be written in any address page write instruction sdp set sdp not set write in memory write data + sdp set after twc (write cycle time) write is enabled sdp enable algorithm figure 3. eeprom sdp enable flowcharts the PSD913F1 functional blocks (cont.) 9.1.1.6.3 eeprom software data protect (sdp) (cont.) to enable sdp mode at run time, the mcu must write three specific data bytes at three specific memory locations, as shown in figure 3. any further writes to eeprom when sdp is set will require this same sequence, followed by the byte(s) to write. the first sdp enable sequence can be followed directly by the byte(s) to be written. to disable sdp mode, the mcu must write specific bytes to six specific locations, as shown in figure 4. the mcu must not be executing code from eeprom when these instructions are invoked. the mcu must be operating from some other memory when enabling or disabling sdp mode. the state of sdp mode is not changed by power on/off sequences (nonvolatile). when either the sdp enable or sdp disable instructions are issued from the mcu, the mcu must use the toggle bit (status bit dq6) or the ready/busy output pin to check programming status. the ready/busy output is driven low from the first write of aah @ 555h until the completion of the internal storage sequence. data polling (status bit dq7) is not supported when issuing the sdp enable or sdp disable commands. note: using the sdp sequence (enabling, disabling, or writing data) is initiated when specific bytes are written to addresses on specific pages of eeprom memory, with no more than 120 sec between writes. the addresses 555h and aaah are located on different pages of eeprom. this is how the PSD913F1 distinguishes these instruction sequences from ordinary writes to eeprom, which are expected to be within a single eeprom page.
PSD913F1 preliminary 24 figure 4. software data protection disable flow chart 9.1.1.6.4 write otp row writing to the otp row (64 bytes) can only be done once per byte, and is enabled by an instruction. this instruction is composed of three specific write operations of data bytes at three specific memory locations followed by the data to be stored in the otp row (refer to table 9). during the write operations, address bit a6 must be zero, while address bits a5-a0 define the otp row byte to be written while any eeprom sector select signal (eesi) is active. writing the otp row is allowed only when sdp mode is not enabled. 9.1.1.7 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 PSD913F1 main flash and optional boot flash require the mcu to send an instruction to program a byte or perform an erase function (see table 9). this differs from eeprom, which can be programmed with simple mcu bus write operations (unless eeprom sdp mode is enabled). 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 PSD913F1 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. write aah to address 555h write 55h to address aaah write 80h to address 555h write aah to address 555h write 55h to address aaah write 20h to address 555h page write instruction unprotected state after twc (write cycle time) the PSD913F1 functional blocks (cont.)
preliminary PSD913F1 25 the PSD913F1 functional blocks (cont.) 9.1.1.7.1 data polling polling on dq7 is a method of checking whether a program or erase instruction is in progress or has completed. figure 5 shows the data polling algorithm. when the mcu issues a programming instruction, the embedded algorithm within the PSD913F1 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 5). 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 5 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. figure 5. data polling flow chart start read dq5 & dq7 at valid address yes yes yes no no no dq7 = data7 dq5 =1 dq7 = data read dq7 fail pass
PSD913F1 preliminary 26 9.1.1.7.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 6 shows the data toggle algorithm. when the mcu issues a programming instruction, the embedded algorithm within the PSD913F1 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 6). 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 toggle method after an erase instructin, figure 6 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. the PSD913F1 functional blocks (cont.) figure 6. data toggle flow chart start read dq5 & dq6 no yes no yes yes no dq6 = toggle dq5 =1 dq6 = toggle read dq6 fail pass
preliminary PSD913F1 27 the PSD913F1 functional blocks (cont.) 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.7. 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 PSD913F1 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 PSD913F1 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 PSD913F1 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.7. 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. 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) 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 PSD913F1 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 PSD913F1 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.
PSD913F1 preliminary 28 bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 sec7_prot sec6_prot sec5_prot sec4_prot sec3_prot sec2_prot sec1_prot sec0_prot flash protection register 9.1.1.9.2 reset instruction the reset instruction resets the internal memory logic state machine in a few milliseconds. reset is an instruction of either one write operation or three write operations (refer to table 9). bit definitions: sec_prot 1 = flash is write protected. sec_prot 0 = flash is not write protected. bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 security_ *** sec3_prot sec2_prot sec1_prot sec0_prot bit psd/ee protection register bit definitions: sec_prot 1 = eeprom boot sector is write protected. sec_prot 0 = eeprom 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 11. sector protection/security bit definition *: not used. the PSD913F1 functional blocks (cont.) 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) is true. (see table 9.) 9.1.1.9 flash and eeprom memory specific features 9.1.1.9.1 flash and eeprom sector protect each flash and eeprom 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 and eeprom 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 or eeprom 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 psd/ee protection registers (csiop). see table 11.
preliminary PSD913F1 29 the PSD913F1 functional blocks (cont.) 9.1.2 sram the sram is a 16 kbit (2k x 8) memory. the sram is enabled when rs0 the sram chip select output from the dpld is high. rs0 can contain up to two 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 (pc2). if you have an external battery connected to the PSD913F1, 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 pc4 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 battery voltage and the battery on pc2 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), eeprom (eesi), and sram (rs0) memory select signals are all outputs of the dpld. they are setup by entering equations for them in psdsoft. the following rules apply to the equations for the internal chip select signals: 1. flash memory and eeprom memory sector select signals must not be larger than the physical sector size. 2. any main flash memory sector must not be mapped in the same memory space as another flash sector. 3. an eeprom memory sector must not be mapped in the same memory space as another eeprom sector. 4. sram, i/o, and peripheral i/o spaces must not overlap. 5. an eeprom memory sector may overlap a main flash memory sector. in case of overlap, priority will be given to the eeprom. 6. sram, i/o, and peripheral i/o spaces may overlap any other memory sector. priority will be given to the sram, i/o, or peripheral i/o. example fs0 is valid when the address is in the range of 8000h to bfffh, ees0 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 ees0 greater than 87ffh (and less than 9fffh) will automatically address eeprom 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 eeprom 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 7 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.
PSD913F1 preliminary 30 level 1 sram, i /o level 2 eeprom memory highest priority lowest priority level 3 flash memory figure 7. priority level of memory and i/o components 9.1.3.1. memory select configuration for mcus with separate program and data spaces the 8031 and compatible family of microcontrollers, which includes the 80c51, 80c151, 80c251, 80c51xa, and the c500 family, have separate address spaces for code memory (selected using psen) and data memory (selected using rd). any of the memories within the PSD913F1 can reside in either space or both spaces. this is controlled through manip- ulation 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, i may wish to have sram and flash in data space at boot, and eeprom in program space at boot, and later swap eeprom and flash. 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 12 describes the vm register. bit 7* bit 6* bit 5* bit 4 bit 3 bit 2 bit 1 bit 0 fl_data ee_data fl_code ee_code sram_code *** 0 = rd 0 = rd 0 = psen 0 = psen 0 = psen can t can t can t can t can t access access access access access flash eeprom flash eeprom sram *** 1 = rd 1 = rd 1 = psen 1 = psen 1 = psen access access access access access flash eeprom flash eeprom sram table 12. vm register note: bits 5-7 are not used, should set to 0 . the PSD913F1 functional blocks (cont.)
preliminary PSD913F1 31 the PSD913F1 functional blocks (cont.) flash dpld eeprom sram rs0 ees0-3 fs0-7 cs cs cs oe oe rd psen oe figure 8. 8031 memory modes ?separate space mode flash dpld eeprom sram rs0 ees0-3 fs0-7 rd cs cs cs rd oe oe vm reg bit 2 psen vm reg bit 0 vm reg bit 1 vm reg bit 3 vm reg bit 4 oe figure 9. 80c31 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 flash memory, while the rd signal is used to access data from the eeprom, 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, eeprom, 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 80c31 memory map example see application notes for examples.
PSD913F1 preliminary 32 reset d0-d7 r/w d0 q0 q1 q2 q3 q4 q5 q6 q7 d1 d2 d3 d4 d5 d6 d7 page register pgr0 pgr1 pgr2 pgr3 dpld and gpld internal selects and logic flash pld pgr4 pgr5 pgr6 pgr7 figure 10. page register the PSD913F1 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 and can be included in the flash memory, eeprom, 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 note. figure 10 shows the page register. the eight flip flops in the register are connected to the internal data bus d0-d7. the microcontroller can write to or read from the page register. the page register can be accessed at address location csiop + e0h.
preliminary PSD913F1 33 the PSD913F1 functional blocks (cont.) 9.2 plds the plds bring programmable logic functionality to the PSD913F1. after specifying the chip selects or logic equations for the plds in psdsoft, the logic is programmed into the device and available upon power-up. the PSD913F1 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 11 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 19 outputs that are connected to ports a, b and d. the and array is used to form product terms. these product terms are specified using pssoft. an input bus consisting of 57 signals is connected to the plds. the signals are shown in table 13. the complement of the 57 signals are also available as input to the and array. input source input name number of signals mcu address bus a[15:0] * 16 mcu control signals cntl[2:0] 3 reset rst 1 power down pdn 1 port a input pa[7-0] 8 port b input pb[7-0] 8 port c input pc[7-0] 8 port d inputs pd[2:0] 3 page register pgr(7:0) 8 flash programming status bit rdy/bsy 1 table 13. dpld and gpld inputs note: the address inputs are a[19:4] in 80c51xa mode. the turbo bit the plds in the PSD913F1 can minimize power consumption by switching off 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.
PSD913F1 preliminary 34 pld input bus 8 csiop select sram select pld out 8 port a pld input 8 port c pld input 8 port b pld input 8 port d pld input 3 eeprom selects decode pld general purpose pld page register gpld port a port b port d port c flash memory selects data bus 8 4 1 1 57 57 pld out 8 pld out 3 figure 11. pld block diagrams (inputs) (24) (16) (1) pdn (apd output) i /o ports (port a,b,c) (8) pgr0 - pgr7 a [ 15:0 ] * (3) (3) pd [ 2:0 ] (ale,clkin,csi) cntrl [ 2:0 ] ( read/write control signals) (1) (1) reset rd_bsy rs0 csiop 8 flash memory sector selects 4 eeprom sector selects sram select i/o decoder select ees 0 ees 1 ees 2 ees 3 fs0 fs7 3 3 3 3 3 3 3 3 3 3 3 3 2 figure 12. dpld logic array * note: the address inputs are a[19:4] in 80c51xa mode.
preliminary PSD913F1 35 the PSD913F1 functional blocks (cont.) each of the two plds has unique characteristics suited for its applications they are described in the following sections. 9.2.1 decode pld (dpld) the dpld, shown in figure 12, is used for decoding the address for internal psd components. the dpld can generate the following chip selects: 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 (two 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 or d. 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 13 shows how the gpld is connected to the i/o ports. the gpld has 19 outputs and each are routed to a port pin. the port pin can also be configured as input tot eh gpld. when it is not used as gpld output or input, the pin can be configured to perform other i/o functions. the gpld outputs are identical except in the number of available product terms for logic implementation. select the pin that can best meet the product term requirement of your logic function or chip selects. the outputs can be configured as active high or low outputs. table 14 shows the number of product terms that are assigned to the pld outputs on the i/o ports. when PSD913F1 is connected to a mcu with non-multiplexed bus, port a will be configured as the data port and the gpld outputs will not be available. gpld output on port pin number of product terms port a, pins pa0-3 3 port a, pins pa4-7 9 port b, pins pb0-3 4 port b, pins pb4-7 7 port d, pins pd0-2 1 table 14. gpld output product term
PSD913F1 preliminary 36 pld output product term * product terms * product terms * general purpose pld (gpld) i/o port * pin pa0-3 has 3 pt pin pa4-7 has 9 pt * pin pb0-3 has 4 pt pin pb4-7 has 7 pt * pin pd0-2 has 1 pt polarity select pld input bus and array pld output polarity select and array pld output pld input pld input pld input polarity select other i/o functions other i/o functions other i/o functions and array mux mux mux port a port b port d represents a single pin from each i /o port figure 13. the general purpose pld and i/o port
preliminary PSD913F1 37 the PSD913F1 functional blocks (cont.) 9.3 microcontroller bus interface the no-glue logic PSD913F1 microcontroller bus interface can be directly connected to most popular microcontrollers and their control signals. key 8-bit microcontrollers with their bus types and control signals are shown in table 15. the interface type is specified using the psdsoft. data bus mcu width cntl0 cntl1 cntl2 pc7 pd0** adio0 pa3-pa0 pa7-pa4 8031/8051 8 wr rd psen * ale a0 ** 80c51xa 8 wr rd psen * ale a4 a3-a0 * 80c251 8 wr psen ** ale a0 ** 80c251 8 wr rd psen * ale a0 ** 80198 8 wr rd ** ale a0 ** 68hc11 8 r/w e ** as a0 ** 68hc05c0 8 wr rd ** as a0 ** 68hc912 8 r/w e * dbe as a0 ** z80 8 wr rd *** a0 d3-d0 d7-d4 z8 8 r/w ds ** as a0 ** 68330 8 r/w ds ** as a0 ** m37702m2 8 r/w e ** ale a0 d3-d0 d7-d4 table 15. microcontrollers and their control signals * * unused cntl2 pin can be configured as pld input. other unused pins (pc7, pd0, pa3-0) can be ** configured for other i/o functions. ** ale/as input is optional for microcontrollers with a non-multiplexed bus 9.3.1. PSD913F1 interface to a multiplexed 8-bit bus figure 14 shows an example of a system using a microcontroller with an 8-bit multiplexed bus and a PSD913F1. the adio port on the PSD913F1 is connected directly to the microcontroller address/data bus. ale latches the address lines internally. latched addresses can be brought out to port a or b. the PSD913F1 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 d may be used as additional address inputs. 9.3.2. PSD913F1 interface to a non-multiplexed 8-bit bus figure 15 shows an example of a system using a microcontroller with an 8-bit non-multiplexed bus and a PSD913F1. the address bus is connected to the adio port, and the data bus is connected to port a. port a is in tri-state mode when the PSD913F1 is not accessed by the microcontroller. should the system address bus exceed sixteen bits, ports b, c, or d may be used for additional address inputs.
PSD913F1 preliminary 38 the PSD913F1 functional blocks (cont.) micro - controller wr rd bhe ale reset ad [ 7:0 ] a [ 15:8 ] a [ 15: 8 ] a [ 7: 0 ] adio port port a port b port c wr ( cntrl0 ) rd ( cntrl1 ) bhe ( cntrl2 ) rst ale ( pd0 ) port d ( optional ) ( optional ) PSD913F1 figure 14. an example of a typical 8-bit multiplexed bus interface micro - controller wr rd bhe ale reset d [ 7:0 ] a [ 15:0 ] a [ 23:16 ] d [ 7:0 ] adio port port a port b port c wr ( cntrl0 ) rd ( cntrl1 ) bhe ( cntrl2 ) rst ale ( pd0 ) port d (optional) PSD913F1 figure 15. an example of a typical 8-bit non-multiplexed bus interface
preliminary PSD913F1 the PSD913F1 functional blocks (cont.) 39 9.3.3 microcontroller interface examples figures 16 through 20 show examples of the basic connections between the PSD913F1 and some popular microcontrollers. the PSD913F1 control input pins are labeled as to the microcontroller function for which they are configured. the mcu interface is specified using the psdsoft. 9.3.3.1 80c31 figure 16 shows the interface to the 80c31, which has an 8-bit multiplexed address/data bus. the lower address byte is multiplexed with the data bus. the microcontroller control signals psen, rd, and wr may be used for accessing the internal memory components and i/o ports. the ale input (pin pd0) latches the address. 9.3.3.2 80c251 the intel 80c251 microcontroller features a user-configurable bus interface with four possible bus configurations, as shown in table 16. configuration 1 is 80c31 compatible, and the bus interface to the PSD913F1 is identical to that shown in figure 16. configurations 2 and 3 have the same bus connection as shown in figure 17. there is only one read input (psen) connected to the cntl1 pin on the PSD913F1. the a16 connection to the pa0 pin allows for a larger address input to the PSD913F1. configuration 4 is shown in figure 18. the rd signal is connected to cntl1 and the psen signal is connected to the cntl2. the 80c251 has two major operating modes: page mode and non-page mode. in non-page mode, the data is multiplexed with the lower address byte, and ale is active in every bus cycle. in page mode, data d[7:0] is multiplexed with address a[15:8]. in a bus cycle where there is a page hit, the ale signal is not active and only addresses a[7:0] are changing. the PSD913F1 supports both modes. in page mode, the psd bus timing is identical to non-page mode except the address hold time and setup time with respect to ale is not required. the psd access time is measured from address a[7:0] valid to data in valid.
PSD913F1 preliminary 40 the PSD913F1 functional blocks (cont.) configuration 80c251 connecting to page mode read/write PSD913F1 pins pins wr cntl0 non-page mode, 80c31 compatible 1 rd cntl1 a [ 7:0 ] multiplex with d [ 7:0 } psen cntl2 2 wr cntl0 non-page mode psen only cntl1 a [ 7:0 ] multiplex with d [ 7:0 } 3 wr cntl0 page mode psen only cntl1 a [ 15:8 ] multiplex with d [ 7:0 } 4 wr cntl0 page mode rd cntl1 a [ 15:8 ] multiplex with d [ 7:0 } psen cntl2 table 16. 80c251 configurations 9.3.3.3 80c51xa the philips 80c51xa microcontroller family supports an 8- or 16-bit multiplexed bus that can have burst cycles. address bits a[3:0] are not multiplexed, while a[19:4] are multiplexed with data bits d[15:0] in 16-bit mode. in 8-bit mode, a[11:4] are multiplexed with data bits d[7:0]. the 80c51xa can be configured to operate in eight-bit data mode. (shown in figure 19). the 80c51xa improves bus throughput and performance by executing burst cycles for code fetches. in burst mode, address a19-4 are latched internally by the PSD913F1, while the 80c51xa changes the a3-0 lines to fetch up to 16 bytes of code. the psd access time is then measured from address a3-a0 valid to data in valid. the psd bus timing requirement in burst mode is identical to the normal bus cycle, except the address setup and hold time with respect to ale does not apply. 9.3.3.4 68hc11 figure 20 shows an interface to a 68hc11 where the PSD913F1 is configured in 8-bit multiplexed mode with e and r/w settings. the dpld can generate the read and wr signals for external devices.
preliminary PSD913F1 41 ea/vp x1 x2 reset reset int0 int1 t0 t1 p1.0 p1.1 p1.2 p1.3 p1.4 p1.5 p1.6 p1.7 p0.0 p0.1 p0.2 p0.3 p0.4 p0.5 p0.6 p0.7 pa0 pa1 pa2 pa3 pa4 pa5 pa6 pa7 pb0 pb1 pb2 pb3 pb4 pb5 pb6 pb7 pc0 pc2 pc1 pc3 pc4 pc5 pc6 pc7 p2.0 p2.1 p2.2 p2.3 p2.4 p2.5 p2.6 p2.7 adio0 adio1 adio2 adio3 adio4 adio5 adio6 adio7 adio8 adio9 adio10 adio11 adio12 adio13 adio14 adio15 cntl0 (wr) cntl1(rd) cntl2 (psen) pd0-ale pd1 pd2 reset rd wr psen ale/p txd rxd reset 29 28 27 25 24 23 22 21 30 39 31 19 18 9 12 13 14 15 1 2 3 4 5 6 7 8 38 37 36 35 34 33 32 ad0 ad1 ad2 ad3 ad4 ad5 ad6 ad7 ad0 ad1 ad2 ad3 ad4 ad5 ad6 ad7 31 32 33 34 35 36 37 39 40 41 42 43 44 45 46 47 48 50 49 10 9 8 7 6 5 4 3 2 52 51 PSD913F1 80c31 ad [ 7:0 ] ad [ 7:0 ] 21 22 23 24 25 26 27 28 17 16 29 30 a8 a9 a10 a11 a12 a13 a14 a15 rd wr psen ale 11 10 reset 20 19 18 17 14 13 12 11 figure 16. interfacing the PSD913F1 with an 80c31 adio0 adio1 adio2 adio3 adio4 adio5 adio6 adio7 adio8 adio9 adio10 adio11 adio12 adio13 adio14 adio15 cntl0 ( wr ) cntl1 ( rd ) cntl 2(psen) pd0-ale pd1 pd2 reset 32 26 43 42 41 40 39 38 37 36 24 25 27 28 29 30 31 33 a0 a1 a2 a3 a4 a5 a6 a7 ad8 ad9 ad10 ad14 ad15 ad13 ad11 ad12 a0 a1 a2 a3 a4 a5 a6 a7 ad8 ad9 ad10 ad11 ad15 ale wr a16 rd ad14 ad12 ad13 14 9 2 3 4 5 6 7 8 21 20 11 13 p1.0 p1.1 p1.2 p1.3 p1.4 p1.5 p1.6 p1.7 p3.0/rxd p3.1/txd p3.2/int0 x2 x1 p3.3/int1 rst ea a16 * a17 * a17 p0.1 p0.0 p0.2 p0.3 p0.4 p0.5 p0.6 p0.7 p2.0 p2.1 p2.2 p2.3 p2.4 p2.5 p2.6 p2.7 ale psen wr rd/a16 pc0 pc1 pc3 pc4 pc5 pc6 pc7 19 18 30 31 32 33 34 35 36 37 39 40 41 42 43 44 45 46 48 8 9 10 49 50 47 29 28 27 25 24 23 22 21 20 19 18 17 14 13 12 11 pb0 pb1 pb2 pb3 pb4 pb5 pb6 pb7 pa0 pa1 pa2 pa3 pa4 pa5 pa6 pa7 7 6 5 4 3 2 52 51 80c251sb PSD913F1 reset reset 35 p3.4/t0 p3.5/t1 16 15 17 10 reset pc2 figure 17. interfacing the PSD913F1 to the 80c251, with one read input * *connection is optional. **non-page mode: ad[7:0] - adio[7:0].
PSD913F1 preliminary 42 adio0 adio1 adio2 adio3 adio4 adio5 adio6 adio7 adio8 adio9 adio10 adio11 adio12 adio13 adio14 adio15 cntl0 ( wr ) cntl1 ( rd ) cntl 2(psen) pd0- ale pd1 pd2 reset 32 26 43 42 41 40 39 38 37 36 24 25 27 28 29 30 31 33 a0 a1 a2 a3 a4 a5 a6 a7 ad8 ad9 ad10 ad14 ad15 ad13 ad11 ad12 a0 a1 a2 a3 a4 a5 a6 a7 ad8 ad9 ad10 ad11 ad15 ale wr psen rd ad14 ad12 ad13 14 9 2 3 4 5 6 7 8 21 20 11 13 p1.0 p1.1 p1.2 p1.3 p1.4 p1.5 p1.6 p1.7 p3.0/rxd p3.1/txd p3.2/int0 x2 x1 p3.3/int1 rst ea p0.1 p0.0 p0.2 p0.3 p0.4 p0.5 p0.6 p0.7 p2.0 p2.1 p2.2 p2.3 p2.4 p2.5 p2.6 p2.7 ale psen wr rd/a16 pc0 pc1 pc3 pc4 pc5 pc6 pc7 19 18 30 31 32 33 34 35 36 37 39 40 41 42 43 44 45 46 48 8 9 10 49 50 47 29 28 27 25 24 23 22 21 20 19 18 17 14 13 12 11 pb0 pb1 pb2 pb3 pb4 pb5 pb6 pb7 pa0 pa1 pa2 pa3 pa4 pa5 pa6 pa7 7 6 5 4 3 2 52 51 80c251sb PSD913F1 reset reset 35 p3.4/t0 p3.5/t1 16 15 17 10 reset pc2 figure 18. interfacing the PSD913F1 to the 80c251, with read and psen inputs adio0 adio1 adio2 adio3 ad104 ad105 adio6 adio7 adio8 adio9 adio10 adio11 ad1012 ad1013 adio14 adio15 cntl0 ( wr ) cntl1 ( rd ) cntl 2 (psen) pd0-ale pd1 pd2 reset 31 33 36 2 3 4 5 43 42 41 40 39 38 37 24 25 26 27 28 29 30 a4d0 a5d1 a6d2 a7d3 a8d4 a9d5 a10d6 a11d7 a12 a13 a14 a18 a19 a17 a15 a16 a0 a1 a2 a3 a4d0 a5d1 a6d2 a7d3 a8d4 a9d5 a10d6 a11d7 a12 a16 a17 a18 a19 a15 a13 a14 txd1 t2ex t2 t0 rst ea/wait busw a1 a0/wrh a2 a3 a4d0 a5d1 a6d2 a7d3 a8d4 a9d5 a10d6 a11d7 a12d8 a13d9 a14d10 a15d11 a16d12 a17d13 a18d14 a19d15 psen rd wrl pc0 pc1 pc3 pc4 pc5 pc6 pc7 ale psen rd wr ale 32 19 18 30 31 32 33 34 35 36 37 39 40 41 42 43 44 45 46 48 8 9 10 49 50 47 7 9 8 16 xtal1 xtal2 rxd0 txd0 rxd1 21 20 11 13 6 29 28 27 25 24 23 22 21 20 19 18 17 14 13 12 11 pb0 pb1 pb2 pb3 pb4 pb5 pb6 pb7 pa0 pa1 pa2 pa3 pa4 pa5 pa6 pa7 7 6 5 4 3 2 52 51 a0 a1 a2 a3 80c51xa PSD913F1 reset reset 35 17 int0 int1 14 10 15 pc2 figure 19. interfacing the PSD913F1 to the 80c51xa, 8-bit data bus
preliminary PSD913F1 43 9 10 11 12 13 14 15 16 adio0 adio1 adio2 adio3 ad104 ad105 adio6 adio7 adio8 adio9 adio10 adio11 ad1012 ad1013 adio14 adio15 cntl0 (r _ w) cntl1(e) cntl 2 pd0 as pd1 pd2 reset 20 21 22 23 24 25 3 5 4 6 42 41 40 39 38 37 36 35 ad0 ad0 ad1 ad2 ad3 ad4 ad5 ad6 ad7 a8 a9 a10 a14 a15 a13 a11 a12 ad1 ad2 ad3 ad4 ad5 ad6 ad7 e as r/w xt ex reset irq xirq pa0 pa1 pa2 pe0 pe1 pe2 pe3 pe4 pe5 pe6 pe7 vrh vrl pa3 pa4 pa5 pa6 pa7 pb0 pb1 pb2 pb3 pb4 pb5 pb6 pb7 pa0 pa1 pa2 pa3 pa4 pa5 pa6 pa7 pc0 pc1 pc2 pc3 pc4 pc5 pc6 pc7 pc0 pc1 pc3 pc4 pc5 pc6 pc7 pd0 pd1 pd2 pd3 pd4 pd5 moda e as r/w 31 30 31 32 33 34 35 36 37 39 40 41 42 43 44 45 46 48 8 9 10 49 50 47 8 7 17 19 18 34 33 32 43 44 45 46 47 48 49 50 52 51 30 29 28 27 29 28 27 25 24 23 22 21 20 19 18 17 14 13 12 11 pb0 pb1 pb2 pb3 pb4 pb5 pb6 pb7 7 6 5 4 3 2 52 51 modb 2 68hc11 PSD913F1 reset reset ad[7:0] ad[7:0] pc2 figure 20. interfacing the PSD913F1 with a 68hc11
PSD913F1 preliminary 44 the PSD913F1 functional blocks (cont.) 9.4 i/o ports there are four programmable i/o ports: ports a, b, c, and d. each of the ports is eight bits except port d, which is 3 bits. each port pin is individually user configurable, thus allow- ing multiple functions per port. the ports are configured using psdsoft or by the microcon- troller writing to on-chip registers in the csiop address space. the topics discussed in this section are: general port architecture port operating modes port configuration registers port data registers individual port functionality. 9.4.1 general port architecture the general architecture of the i/o port is shown in figure 21. individual port architectures are shown in figures 22 through 24. in general, once the purpose for a port pin has been defined, that pin will no longer be available for other purposes. exceptions will be noted. as shown in figure 21, the ports contain an output multiplexer whose selects are driven by the configuration bits in the control registers (ports a and b only) and psdsoft. inputs to the multiplexer include the following: output data from the data out register latched address outputs general purpose pld (gpld) outputs (external chip selects) the port data buffer (pdb) is a tri-state buffer that allows only one source at a time to be read. the pdb is connected to the internal data bus for feedback and can be read by the microcontroller. the data out, direction and control registers, and port pin input are all connected to the pdb. the contents of these registers can be altered by the microcontroller. the pdb feedback path allows the microcontroller to check the contents of the registers.
preliminary PSD913F1 45 internal data bus data out reg. dq d g q dq dq wr wr wr address gpld output ale read mux p d b pld - input control reg. dir reg. data in output select output mux port pin data out address figure 21. general i/o port architecture the PSD913F1 functional blocks (cont.)
PSD913F1 preliminary 46 the PSD913F1 functional blocks (cont.) 9.4.2 port operating modes the i/o ports have several modes of operation. some modes can be defined in psdsoft, some by the microcontroller writing to the control registers in csiop space, and some by both. the modes that can only be defined using psdsoft must be programmed into the device and cannot be changed unless the device is reprogrammed. the modes that can be changed by the microcontroller can be done so dynamically at run-time. the pld i/o, data port, and address input, are the only modes that must be defined before programming the device. all other modes can be changed by the microcontroller at run-time. table 17 summarizes which modes are available on each port. table 20 shows how and where the different modes are configured. each of the port operating modes are described in the following subsections. port mode port a port b port c port d mcu i/o yes yes yes yes pld outputs yes yes no yes pld inputs yes yes yes yes address out yes (a7 0) yes (a7 0) no no or a15 8) address in yes yes yes yes data port yes (d7 0) no no no jtag isp no no yes no table 17. port operating modes
preliminary PSD913F1 47 the PSD913F1 functional blocks (cont.) control direction defined in register register mode psdsoft setting setting at run-time at run-time mcu i/o declare pins only 0 1 = output, 0 = input, pld i/o logic or chip na select equations data port selected for mcu na na (port a) with non-mux bus address out declare pins only 1 1 (port a,b) address in declare pins only na na (port a,b,c,d) jtag isp declare pins only na na table 18. port operating mode settings * na = not applicable 9.4.2.1 mcu i/o mode in the mcu i/o mode, the microcontroller uses the PSD913F1 ports to expand its own i/o ports. by setting up the csiop space, the ports on the PSD913F1 are mapped into the microcontroller address space. the addresses of the ports are listed in table 7. a port pin can be put into mcu i/o mode by writing a 0 to the corresponding bit in the control register. the mcu i/o direction may be changed by writing to the corresponding bit in the direction register. see the subsection on the direction register in the port registers section. when the pin is configured as an output, the content of the data out register drives the pin. when configured as an input, the microcontroller can read the port input through the data in buffer. ports c and d do not have control registers, and are in mcu i/o mode by default. they can be used for pld i/o if they are specified in psdsoft. 9.4.2.2 pld i/o mode the pld i/o mode uses a port as an input to the plds, and/or as an output from the gpld. the corresponding bit in the direction register must not be set to 1 if the pin is defined as a pld input pin in psdsoft. the pld i/o mode is specified in psdsoft by declar- ing the port pins, and then specifying an equation in psdsoft.
PSD913F1 preliminary 48 the PSD913F1 functional blocks (cont.) 9.4.2.4 address in mode for microcontrollers that have more than 16 address lines, the higher addresses can be connected to port a, b, c, and d. the address input can be latched by the address strobe (ale/as). any input that is included in the dpld equations for the main flash, secondary flash, or sram is considered to be an address input. 9.4.2.5 data port mode port a can be used as a data bus port for a microcontroller with a non-multiplexed address/data bus. the data port is connected to the data bus of the microcontroller. the general i/o functions are disabled in port a if the port is configured as a data port. 9.4.2.6 jtag isp port c is jtag compliant, and can be used for in-system programming (isp). for more information on the jtag port, refer to section 9.6. 9.4.2.3 address out mode for microcontrollers with a multiplexed address/data bus, address out mode can be used to drive latched addresses onto the port pins. these port pins can, in turn, drive external devices. either the output enable or the corresponding bits of both the direction register and control register must be set to a 1 for pins to use address out mode. this must be done by the mcu at run-time. see table 19 for the address output pin assignments on ports a and b for various mcus. for non-multiplexed 8 bit bus mode, address lines a[7:0] are available to port b in address out mode. note: do not drive address lines with address out mode to an external memory device if it is intended for the mcu to boot from the external device. the mcu must first boot from psd memory so the direction and control register bits can be set. 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 n/a n/a address (11:8) address (15:12) (page mode) all other address (3:0) address (7:4) address (3:0) address (7:4) 8-bit multiplexed 8-bit n/a n/a address [3:0] address [7:4] non-multiplexed bus table 19. i/o port latched address output assignments n/a = not applicable.
preliminary PSD913F1 49 the PSD913F1 functional blocks (cont.) 9.4.3 port configuration registers (pcrs) each port has a set of pcrs used for configuration. the contents of the registers can be accessed by the microcontroller through normal read/write bus cycles at the addresses given in table 7. the addresses in table 7 are the offsets in hex from the base of the csiop register. the pins of a port are individually configurable and each bit in the register controls its respective pin. for example, bit 0 in a register refers to bit 0 of its port. the three pcrs, shown in table 20, are used for setting the port configurations. the default power-up state for each register in table 20 is 00h. register name port mcu access control a,b write/read direction a,b,c,d write/read drive select* a,b,c,d write/read table 20. port configuration registers * note: see table 27 for drive register bit definition. 9.4.3.1 control register any bit set to 0 in the control register sets the corresponding port pin to mcu i/o mode, and a 1 sets it to address out mode. the default mode is mcu i/o. only ports a and b have an associated control register. 9.4.3.2 direction register the direction register controls the direction of data flow in the i/o ports. any bit set to 1 in the direction register will cause the corresponding pin to be an output, and any bit set to 0 will cause it to be an input. the default mode for all port pins is input. figures 22 and 23 show the port architecture diagrams for ports a, b and c, respectively. the direction of data flow for ports a, b, and c are controlled by the direction register. an example of a configuration for a port with the three least significant bits set to output and the remainder set to input is shown in table 22. since port d only contains three pins, the direction register for port d has only the three least significant bits active. direction register bit port pin mode 0 input 1 output table 21. port pin direction control bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0 0000 111 table 22. port direction assignment example
PSD913F1 preliminary 50 the PSD913F1 functional blocks (cont.) drive bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 register port a open open open open slew slew slew slew drain drain drain drain rate rate rate rate port b open open open open slew slew slew slew drain drain drain drain rate rate rate rate port c open open open open open open open open drain drain drain drain drain drain drain drain port d na na na na na slew slew slew rate rate rate table 23. drive register pin assignment note: na = not applicable. 9.4.3.3 drive select register the drive select register configures the pin driver as open drain or cmos for some port pins, and controls the slew rate for the other port pins. an external pull-up resistor should be used for pins configured as open drain. a pin can be configured as open drain if its corresponding bit in the drive select register is set to a 1 . the default pin drive is cmos. aside: the slew rate is a measurement of the rise and fall times of an output. a higher slew rate means a faster output response and may create more electrical noise. a pin operates in a high slew rate when the corresponding bit in the drive register is set to 1 . the default rate is slow slew. table 23 shows the drive register for ports a, b, c, and d. it summarizes which pins can be configured as open drain outputs and which pins the slew rate can be set for.
preliminary PSD913F1 51 the PSD913F1 functional blocks (cont.) 9.4.4 port data registers the port data registers, shown in table 24, are used by the microcontroller to write data to or read data from the ports. table 24 shows the register name, the ports having each register type, and microcontroller access for each register type. the registers are described below. 9.4.4.1 data in port pins are connected directly to the data in buffer. in mcu i/o input mode, the pin input is read through the data in buffer. 9.4.4.2 data out register stores output data written by the mcu in the mcu i/o output mode. the contents of the register are driven out to the pins if the direction register or the output enable product term is set to 1 . the contents of the register can also be read back by the microcontroller. register name port mcu access data in a,b,c,d read input on pin data out a,b,c,d write/read table 24. port data registers 9.4.5 ports a and b ? functionality and structure ports a and b have similar functionality and structure, as shown in figure 22. the two ports can be configured to perform one or more of the following functions: mcu i/o mode gpld output combinatorial pld outputs can be connected to port a or port b. pld input input to the plds. latched address output provide latched address output per table 19. address in additional high address inputs, may be latched by ale. open drain/slew rate pins pa[3:0] and pb[3:0] can be configured to fast slew rate, pins pa[7:4] and pb[7:4] can be configured to open drain mode. data port port a only, connect to non-multiplexed 8-bit data bus.
PSD913F1 preliminary 52 the PSD913F1 functional blocks (cont.) internal data bus data out reg. dq d g q dq dq wr wr wr address gpld output ale read mux p d b control reg. dir reg. data in pld input output select output mux port a or b pin data out address a [ 7:0 ] or a [ 15:8 ] figure 22. ports a and b structure
preliminary PSD913F1 53 the PSD913F1 functional blocks (cont.) 9.4.6 port c ? functionality and structure port c can be configured to perform one or more of the following functions (see figure 23): mcu i/o mode pld input input to the plds. address in additional high address inputs using the input micro ? cells. in-system programming jtag port can be enabled for programming/erase of the PSD913F1 device. (see section 9.6 for more information on jtag programming.) pins that are configured as jtag pins in psdsoft will not be available for other i/o functions. open drain port c pins can be configured in open drain mode battery backup features pc2 can be configured as a battery input (vstby) pin. pc4 can be configured as a battery on indicator output pin, indicating when vcc is less than vbat. port c does not support address out mode, and therefore no control register is required. pin pc7 may be configured as the dbe input in certain microcontroller interfaces. 9.4.7 port d ? functionality and structure port d has three i/o pins. see figure 24. this port does not support address out mode, and therefore no control register is required. port d can be configured to perform one or more of the following functions: mcu i/o mode gpld output combinatorial pld output (external chip selects) pld input direct input to plds slew rate pins can be set up for fast slew rate port d pins can be configured in psdsoft as input pins for other dedicated functions: pd0 ale, as address strobe input pd1 clkin, as clock input to the pld and apd counter pd2 csi, as active low chip select input. a high input will disable the flash/sram and csiop.
PSD913F1 preliminary 54 the PSD913F1 functional blocks (cont.) internal data bus data out reg. dq dq wr wr read mux p d b pld- input * jtag isp or battery back-up. dir reg. special function * special function * configuration bit data in output select output mux port c pin data out figure 23. port c structure
preliminary PSD913F1 55 the PSD913F1 functional blocks (cont.) internal data bus data out reg. dq dq wr wr gpld output read mux p d b pld - input dir reg. data in output select output mux port d pin data out figure 24. port d structure
PSD913F1 preliminary 56 9.5 power management the PSD913F1 offers configurable power saving options. these options may be used individually or in combinations, as follows: all memory types in a psd (flash, eeprom, and sram) are built with zero-power technology. in addition to using special silicon design methodology, zero-power technology puts the memories into standby mode when address/data inputs are not changing (zero dc current). as soon as a transition occurs on an input, the affected memory wakes up , changes and latches its outputs, then goes back to standby. the designer does not have to do anything special to achieve memory standby mode when no inputs are changing it happens automatically. the pld sections can also achieve standby mode when its inputs are not changing, see pmmr registers below. like the zero-power feature, the automatic power down (apd) logic allows the psd to reduce to standby current automatically. the apd will block mcu address/data signals from reaching the memories and plds. this feature is available on all PSD913F1 devices. the apd unit is described in more detail in section 9.5.1. built in logic will monitor the address strobe of the mcu for activity. if there is no activity for a certain time period (mcu is asleep), the apd logic initiates power down mode (if enabled). once in power down mode, all address/data signals are blocked from reaching psd memories and plds, and the memories are deselected internally. this allows the memories and plds to remain in standby mode even if the address/data lines are changing state externally (noise, other devices on the mcu bus, etc.). keep in mind that any unblocked pld input signals that are changing states keeps the pld out of standby mode, but not the memories. the psd chip select input (csi) on all families can be used to disable the internal memories, placing them in standby mode even if inputs are changing. this feature does not block any internal signals or disable the plds. this is a good alternative to using the apd logic, especially if your mcu has a chip select output. there is a slight penalty in memory access time when the csi signal makes its initial transition from deselected to selected. the pmmr registers can be written by the mcu at run-time to manage power. PSD913F1 supports blocking bits in these registers that are set to block designated signals from reaching both plds. current consumption of the plds is directly related to the composite frequency of the changes on their inputs (see figures 28 and 28a). significant power savings can be achieved by blocking signals that are not used in pld logic equations. the PSD913F1 has a turbo bit in the pmmr0 register. this bit can be set to disable the turbo mode feature (default is turbo mode on). while turbo mode is disabled, the plds can achieve standby current when no pld inputs are changing (zero dc current). even when inputs do change, significant power can be saved at lower frequencies (ac current), compared to when turbo mode is enabled. when the turbo mode is enabled, there is a significant dc current component and the ac component is higher. 9.5.1 automatic power down (apd) unit and power down mode the apd unit, shown in figure 25, puts the psd into power down mode by monitoring the activity of the address strobe (ale/as). if the apd unit is enabled, as soon as activity on the address strobe stops, a four bit counter starts counting. if the address strobe remains inactive for fifteen clock periods of the clkin signal, the power down (pdn) signal becomes active, and the psd will enter into power down mode, discussed next. the PSD913F1 functional blocks (cont.)
preliminary PSD913F1 57 the PSD913F1 functional blocks (cont.) access 5v v cc , pld memory recovery time typical propagation access to normal standby mode delay time access current power down normal tpd no access tlvdv 50 a (note 1) (note 2) table 26. PSD913F1 timing and standby current during power down mode notes: 1. power down does not affect the operation of the pld. the pld operation in this mode is based only on the turbo bit. 2. typical current consumption assuming no pld inputs are changing state and the pld turbo bit is off. port function pin level mcu i/o no change pld out no change address out undefined data port three-state peripheral i/o three-state table 25. power down modes effect on ports 9.5.1 automatic power down (apd) unit and power down mode (cont.) power down mode by default, if you enable the psd apd unit, power down mode is automatically enabled. the device will enter power down mode if the address strobe (ale/as) remains inactive for fifteen clkin (pin pd1) clock periods. the following should be kept in mind when the psd is in power down mode: if the address strobe starts pulsing again, the psd will return to normal operation. the psd will also return to normal operation if either the csi input returns low or the reset input returns high. the mcu address/data bus is blocked from all memories and plds. various signals can be blocked (prior to power down mode) from entering the plds by setting the appropriate bits in the pmmr registers. the blocked signals include mcu control signals and the common clock (clkin). note that blocking clkin from the plds will not block clkin from the apd unit. all psd memories enter standby mode and are drawing standby current. however, the plds and i/o ports do not go into standby mode because you don t want to have to wait for the logic and i/o to wake-up before their outputs can change. see table 29 for power down mode effects on psd ports. typical standby current is 50 a for 5 v devices, and 25 a for 3 v devices. these standby current values assume that there are no transitions on any pld input. hc11 (or compatible) users note the hc11 turns off its e clock when it sleeps. therefore, if you are using an hc11 (or compatible) in your design, and you wish to use the power down, you must not connect the e clock to the clkin input (pd1). you should instead connect an independent clock signal to the clkin input. the clock frequency must be less than 15 times the frequency of as. the reason for this is that if the frequency is greater than 15 times the frequency of as, the PSD913F1 will keep going into power down mode.
PSD913F1 preliminary 58 apd en pmmr0 bit 1=1 ale reset csi clkin transition detection edge detect apd counter power down ( pdn ) disable bus interface eeprom select flash select sram select pd clr pd disable flash/eeprom/sram pld select figure 25. apd logic block the PSD913F1 functional blocks (cont.) enable apd set pmmr0 bit 1 = 1 psd in power down mode ale/as idle for 15 clkin clocks? reset yes no optional disable desired inputs to pld by setting pmmr0 bits 4 and pmmr2 bits 2 through 6. figure 26. enable power down flow chart
preliminary PSD913F1 59 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 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 *** pld pld * apd * array clk turbo enable 1 = off 1 = off 1 = on table 27. power management mode registers (pmmr0, pmmr2)** pmmr0 ** * bits 0, 2, 6, and 7 are not used, and should be set to 0, bit 5 should be set to 1. * ** the pmmr0, and pmmr2 register bits are cleared to zero following power up. *** subsequent reset pulses will not clear the registers. bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 * pld pld pld pld pld ** array array array array array dbe ale cntl2 cntl1 cntl0 1 = off 1 = off 1 = off 1 = off 1 = off pmmr2 bit 2 0 = cntl0 input to the pld and array is connected. 1 = cntl0 input to pld and array is disconnected, saving power. bit 3 0 = cntl1 input to the pld and array is connected. 1 = cntl1 input to pld and array is disconnected, saving power. bit 4 0 = cntl2 input to the pld and array is connected. 1 = cntl2 input to pld and array is disconnected, saving power. bit 5 0 = ale input to the pld and array is connected. 1 = ale input to pld and array is disconnected, saving power. bit 6 0 = dbe input to the pld and array is connected. 1 = dbe input to pld and array is disconnected, saving power. * unused bits should be set to 0. the PSD913F1 functional blocks (cont.)
PSD913F1 preliminary 60 apd ale enable bit pd polarity ale level apd counter 0 x x not counting 1 x pulsing not counting 1 1 1 counting (generates pdn after 15 clocks) 1 0 0 counting (generates pdn after 15 clocks) table 28. apd counter operation the PSD913F1 functional blocks (cont.) 9.5.2 other power saving options the PSD913F1 offers other reduced power saving options that are independent of the power down mode. except for the sram standby and csi input features, they are enabled by setting bits in the pmmr0 and pmmr2 registers. 9.5.2.1 zero power pld the power and speed of the plds are controlled by the turbo bit (bit 3) in the pmmr0. by setting the bit to 1 , the turbo mode is disabled and the plds consume zero power current when the inputs are not switching for an extended time of 70 ns. the propagation delay time will be increased by 10 ns after the turbo bit is set to 1 (turned off) when the inputs change at a composite frequency of less than 15 mhz. when the turbo bit is set to a 0 (turned on), the plds run at full power and speed. the turbo bit affects the pld s d.c. power, ac power, and propagation delay. note: blocking mcu control signals with pmmr2 bits can further reduce pld ac power consumption. 9.5.2.2 sram standby mode (battery backup) the PSD913F1 supports a battery backup operation that retains the contents of the sram in the event of a power loss. the sram has a vstby pin (pc2) that can be connected to an external battery. when v cc becomes lower than vstby then the psd will automatically connect to vstby as a power source to the sram. the sram standby current (istby) is typically 0.5 a. the sram data retention voltage is 2 v minimum. the battery-on indicator (vbaton) can be routed to pc4. this signal indicates when the v cc has dropped below the vstby voltage. 9.5.2.3 the csi input pin pd2 of port d can be configured in psdsoft as the csi input. when low, the signal selects and enables the internal flash, eeprom, sram, and i/o for read or write operations involving the PSD913F1. a high on the csi pin will disable the flash memory, eeprom, and sram, and reduce the psd power consumption. however, the pld and i/o pins remain operational when csi is high. note: there may be a timing penalty when using the csi pin depending on the speed grade of the psd that you are using. see the timing parameter t slqv in the ac/dc specs. 9.5.2.4 input clock the PSD913F1 provides the option to turn off the clkin input to the pld and array to save ac power consumption. during power down mode, or, if the clkin input is not being used as part of the pld logic equation, the clock should be disabled to save ac power. the clkin will be disconnected from the pld and array by setting bits 4 to a 1 in pmmr0. 9.5.2.5 input control signals the PSD913F1 provides the option to turn off the input control signals (cntl0-2, ale, and dbe) to the pld to save ac power consumption. these control signals are inputs to the pld and array. during power down mode, or, if any of them are not being used as part of the pld logic equation, these control signals should be disabled to save ac power. they will be disconnected from the pld and array by setting bits 2, 3, 4, 5, and 6 to a 1 in the pmmr2.
preliminary PSD913F1 61 the PSD913F1 functional blocks (cont.) 9.5.3 reset and power on requirement power on reset upon power up the PSD913F1 requires a reset pulse of tnlnh-po (minimum 1ms) after v cc is steady. during this time period the device loads internal configurations, clears some of the registers and sets the flash or eeprom into operating mode. after the rising edge of reset, the PSD913F1 remains in the reset state for an additional topr (minimum 120 ns) nanoseconds before the first memory access is allowed. the PSD913F1 flash or eeprom memory is reset to the read array mode upon power up. the fsi and eesi select signals along with the write strobe signal must be in the false state during power-up reset for maximum security of the data contents and to remove the possi- bility of a byte being written on the first edge of a write strobe signal. the psd automatically prevents write strobes from reaching the eeprom memory array for about 5 ms (teehwl). any flash memory write cycle initiation is prevented automatically when v cc is below vlko. warm reset once the device is up and running, the device can be reset with a much shorter pulse of tnlnh (minimum 150 ns). the same topr time is needed before the device is operational after warm reset. figure 27 shows the timing of the power on and warm reset. operating level power on reset v cc reset t nlnh po t opr t nlnh t opr warm reset figure 27. power on and warm reset timing i/o pin, register and pld status at reset table 29 shows the i/o pin, register and pld status during power on reset, warm reset and power down mode. pld outputs are always valid during warm reset, and they are valid in power on reset once the internal psd configuration bits are loaded. this loading of psd is completed typically long before the v cc ramps up to operating level. once the pld is active, the state of the outputs are determined by the psdsoft equations.
PSD913F1 preliminary 62 the PSD913F1 functional blocks (cont.) port c pin jtag signals description pc0 tms mode select pc1 tck clock pc3 tstat status pc4 terr error flag pc5 tdi serial data in pc6 tdo serial data out table 30. jtag port signals 9.6 programming in-circuit using the jtag interface the jtag interface on the PSD913F1 can be enabled on port c (see table 30). all memory (flash and secondary flash block), pld logic, and psd configuration bits may be programmed through the jtag interface. a blank part can be mounted on a printed circuit board and programmed using jtag. the standard jtag signals (ieee 1149.1) are tms, tck, tdi, and tdo. two additional signals, tstat and terr, are optional jtag extensions used to speed up program and erase operations. * sr_cod bit in the vm register are always cleared to zero on power on or warm reset. ** port configuration power on reset warm reset power down mode mcu i/o input mode input mode unchanged pld output valid after internal valid depend on inputs to psd configuration pld (address are bits are loaded blocked in pd mode) address out tri-stated tri-stated not defined data port tri-stated tri-stated tri-stated table 29. status during power on reset, warm reset and power down mode register power on reset warm reset power down mode pmmr0, 2 cleared to 0 unchanged unchanged vm register* initialized based on initialized based on unchanged the selection in the selection in psdsoft psdsoft configuration menu. configuration menu. all other registers cleared to 0 cleared to 0 unchanged by default, on a blank psd (as shipped from factory or after erasure), four pins on port c are enabled for the basic jtag signals tms, tck, tdi, and tdo. see application note 54 for more details on jtag in-system-programming.
preliminary PSD913F1 63 9.6.1 standard jtag signals the jtag configuration bit (non-volatile) inside the psd can be set by the user in the psdsoft. once this bit is set and programmed in the psd, the jtag pins are dedicated to jtag at all times and is in compliance with ieee 1149.1. after power up the standard jtag signals (tdi, tdo tck and tms) are inputs, waiting for a serial command from an external jtag controller device (such as flashlink or automated test equipment). when the enabling command is received from the external jtag controller, tdo becomes an output and the jtag channel is fully functional inside the psd. the same command that enables the jtag channel may optionally enable the two additional jtag pins, tstat and terr. the PSD913F1 supports jtag in-system-configuration (isc) commands, but not boundary scan. st s psdsoft software tool and flashlink jtag programming cable implement these jtag-isc commands. 9.6.2 jtag extensions tstat and terr are two jtag extension signals enabled by a jtag command received over the four standard jtag pins (tms, tck, tdi, and tdo). they are used to speed programming and erase functions by indicating status on psd pins instead of having to scan the status out serially using the standard jtag channel. see application note 54. terr will indicate if an error has occurred when erasing a sector or programming a byte in flash memory. this signal will go low (active) when an error condition occurs, and stay low until a special jtag command is executed or a chip reset pulse is received after an isc-disable command. tstat behaves the same as the rdy/bsy signal described in section 9.1.1.2. tstat will be high when the PSD913F1 device is in read array mode (flash memory and boot block contents can be read). tstat will be low when flash memory programming or erase cycles are in progress, and also when data is being written to the secondary flash block. tstat and terr can be configured as open-drain type signals with a jtag command. 9.6.3 security and flash memories protection when the security bit is set, the device cannot be read on a device programmer or through the jtag port. when using the jtag port, only a full chip erase command is allowed. all other program/erase/verify commands are blocked. full chip erase returns the part to a non-secured blank state. the security bit can be set in psdsoft. all flash memory and eeprom sectors can individually be sector protected against erasures. the sector protect bits can be set in psdsoft. the PSD913F1 functional blocks (cont.)
PSD913F1 preliminary 64 symbol parameter condition min max unit t stg storage temperature pldcc 65 + 125 c commercial 0 + 70 c operating temperature industrial 40 + 85 c voltage on any pin with respect to gnd 0.6 + 7 v v pp device programmer supply voltage with respect to gnd 0.6 + 14 v v cc supply voltage with respect to gnd 0.6 + 7 v esd protection > 2000 v absolute maximum ratings note: stresses above those listed under absolute maximum ratings may cause permanent damage to the device. this is a stress rating only and functional operation of the device at these or any other conditions above those indicated in the operational sections of this specification is not recommended. exposure to absolute maximum rating conditions for extended periods of time may affect device reliability. symbol parameter condition min typ max unit v cc supply voltage all speeds 4.5 5 5.5 v v cc supply voltage v-versions 3.0 3.6 v all speeds recommended operating conditions range temperature v cc tolerance commercial 0 c to +70 c + 5 v 10% industrial 40 c to +85 c + 5 v 10% commercial 0 c to +70 c 3 v to 3.6 v industrial 40 c to +85 c 3 v to 3.6 v operating range
preliminary PSD913F1 65 ac/dc parameters the following tables describe the ad/dc parameters of the PSD913F1 family: dc electrical specification ac timing specification pld timing combinatorial timing microcontroller timing read timing write timing power down and reset timing following are issues concerning the parameters presented: in the dc specification the supply current is given for different modes of operation. before calculating the total power consumption, determine the percentage of time that the PSD913F1 is in each mode. also, the supply power is considerably different if the turbo bit is "off". the ac power component gives the pld, flash memory, eeprom, and sram ma/mhz specification. figure 28 shows the pld ma/mhz as a function of the number of product terms (pt) used. in the pld timing parameters, add the required delay when turbo bit is "off". figure 28. pld i cc /frequencyconsumption (v cc = 5 v 10%) 0 10 20 30 40 60 70 80 90 100 110 v cc = 5v 50 01015 5 20 25 highest composite frequency at pld inputs (mhz) i cc (ma) turbo on (100%) turbo on (25%) turbo off turbo off pt 100% pt 25%
PSD913F1 preliminary 66 ac/dc parameters (cont.) conditions highest composite pld input frequency (freq pld) = 8 mhz mcu ale frequency (freq ale) = 4 mhz % flash access = 80% % sram access = 15% % i/o access = 5% (no additional power above base) operational modes % normal = 10% % power down mode = 90% number of product terms used (from fitter report) = 45 pt % of total product terms = 45/153 = 29.4% turbo mode = on calculation (typical numbers used) i cc total = ipwrdown x %pwrdown + %normal x ( i cc (ac) + i cc (dc) ) = ipwrdown x %pwrdown + % normal x (%flash x 2.5 ma/mhz x freq ale + %sram x 1.5 ma/mhz x freq ale + % pld x 2 ma/mhz x freq pld + #pt x 400 a/pt = 50 a x 0.90 + 0.1 x (0.8 x 2.5 ma/mhz x 4 mhz + 0.15 x 1.5 ma/mhz x 4 mhz +2 ma/mhz x 8 mhz + 45 x 0.4 ma/pt) = 45 a + 0.1 x (8 + 0.9 + 16 + 18 ma) = 45 a + 0.1 x 42.9 = 45 a + 4.29 ma = 4.34 ma this is the operating power with no flash writes or erases. calculation is based on i out = 0 ma. example of PSD913F1 typical power calculation at v cc = 5.0 v figure 28a. pld i cc /frequency consumption (PSD913F1v versions, v cc = 3 v) 0 10 20 30 40 50 60 v cc = 3v 01015 5 20 25 i cc (ma) turbo on (100%) turbo on (25%) turbo off turbo off highest composite frequency at pld inputs (mhz) pt 100% pt 25%
preliminary PSD913F1 67 conditions highest composite pld input frequency (freq pld) = 8 mhz mcu ale frequency (freq ale) = 4 mhz % flash access = 80% % sram access = 15% % i/o access = 5% (no additional power above base) operational modes % normal = 10% % power down mode = 90% number of product terms used (from fitter report) = 45 pt % of total product terms = 45/153 = 29.4% turbo mode = off calculation (typical numbers used) i cc total = ipwrdown x %pwrdown + %normal x ( i cc (ac) + i cc (dc) ) = ipwrdown x %pwrdown + % normal x ( %flash x 2.5 ma/mhz x freq ale + %sram x 1.5 ma/mhz x freq ale + % pld x (from graph using freq pld) ) = 50 a x 0.90 + 0.1 x (0.8 x 2.5 ma/mhz x 4 mhz + 0.15 x 1.5 ma/mhz x 4 mhz + 24 ma) = 45 a + 0.1 x (8 + 0.9 + 24) = 45 a + 0.1 x 32.9 = 45 a + 3.29 ma = 3.34 ma this is the operating power with no flash writes or erases. calculation is based on i out = 0 ma. example of typical power calculation at v cc = 5.0 v in turbo off mode ac/dc parameters (cont.)
PSD913F1 preliminary 68 note: 1. reset input has hysteresis. v il1 is valid at or below .2v cc ?1. v ih1 is valid at or above .8v cc . 2. csi deselected or internal power down mode is active. 3. pld is in non-turbo mode and none of the inputs are switching 4. refer to figure 32 for pld current calculation. 5. i out = 0 ma symbol parameter conditions min typ max unit v cc supply voltage all speeds 4.5 5 5.5 v v ih high level input voltage 4.5 v < v cc < 5.5 v 2 v cc +.5 v v il low level input voltage 4.5 v < v cc < 5.5 v .5 0.8 v v ih1 reset high level input voltage (note 1) .8 v cc v cc +.5 v v il1 reset low level input voltage (note 1) ?5 .2 v cc ?1 v v hys reset pin hysteresis 0.3 v v lko v cc min for flash erase and program 2.5 4.2 v v ol output low voltage i ol = 20 a, v cc = 4.5 v 0.01 0.1 v i ol = 8 ma, v cc = 4.5 v 0.25 0.45 v v oh output high voltage except v stby on i oh = 20 a, v cc = 4.5 v 4.4 4.49 v i oh = 2 ma, v cc = 4.5 v 2.4 3.9 v v oh 1 output high voltage v stby on i oh 1 = 1 a v sby ?0.8 v v sby sram standby voltage 2.0 v cc v i sby sram standby current (v stby pin) v cc = 0 v 0.5 1 a i idle idle current (v stby pin) v cc > v sby 0.1 0.1 a v df sram data retention voltage only on v stby 2v i sb standby supply current for power csi > v cc ?.3 v 50 200 a down mode (notes 2 and 3) i li input leakage current v ss < v in < v cc ? .1 1 a i lo output leakage current 0.45 < v in < v cc ?0 5 10 a zpld_turbo = off, 0ma f = 0 mhz (note 5) zpld only zpld_turbo = on, f = 0 mhz 400 700 a/pt i cc (dc) operating supply during flash or eeprom, (note 5) current flash or write/erase only 15 30 ma eeprom read only, f = 0 mhz 0 0 ma sram f = 0 mhz 0 0 ma zpld ac adder fig.28 i cc (ac) (note 4) (note 5) flash or eeprom ac adder 2.5 3.5 ma/mhz sram ac adder 1.5 3.0 ma/mhz PSD913F1 dc characteristics (5 v 10% versions)
preliminary PSD913F1 69 ac symbols for pld timing. example: t avlx ? time from address valid to ale invalid. signal letters a address input c ceout output d input data e e input l ale input n reset input or output p port signal output q output data r wr, uds, lds, ds, iord, psen inputs s chip select input t r/w input w internal pdn signal b vstby output signal behavior t time l logic level low or ale h logic level high v valid x no longer a valid logic level z float pw pulse width microcontroller interface ac/dc parameters (5v 10% versions)
PSD913F1 preliminary 70 notes: 1. rd timing has the same timing as ds, lds, uds, and psen signals. 2. rd and psen have the same timing. 3. any input used to select an internal PSD913F1 function. 4. in multiplexed mode, latched addresses generated from adio delay to address output on any port. 5. rd timing has the same timing as ds, lds, and uds signals. 6. in turbo off mode, add 10ns to t avqv . -90 -12 -15 turbo symbol parameter conditions min max min max min max off unit t lvlx ale or as pulse width 20 22 28 ns t avlx address setup time (note 3) 6 8 10 ns t lxax address hold time (note 3) 8 9 11 ns t avqv address valid to data valid (notes 3 and 6) 90 120 150 add 10 ns t slqv cs valid to data valid 100 135 150 ns rd to data valid 8-bit bus (note 5) 32 35 40 ns t rlqv rd or psen to data valid 8-bit bus, 8031, 80251 (note 2) 38 42 45 ns t rhqx rd data hold time (note 1) 0 0 0 ns t rlrh rd pulse width (note 1) 32 35 38 ns t rhqz rd to data high-z (note 1) 25 29 33 ns t ehel e pulse width 32 36 38 ns t theh r/w setup time to enable 10 13 18 ns t eltl r/w hold time after enable 0 0 0 ns t avpv address input valid to (note 4) 25 28 30 ns address output delay read timing (5 v 10% versions) microcontroller interface ? PSD913F1 ac/dc parameters (5v 10% versions)
preliminary PSD913F1 71 -90 -12 -15 symbol parameter conditions min max min max min max unit t lvlx ale or as pulse width 20 22 28 t avlx address setup time (note 1) 6 8 10 ns t lxax address hold time (note 1) 8 9 11 ns t avwl address valid to leading edge of wr (notes 1 and 3) 20 25 30 ns t slwl cs valid to leading edge of wr (note 3) 25 30 35 ns t dvwh wr data setup time (note 3) 35 40 45 ns t whdx wr data hold time (note 3) 5 5 5 ns t wlwh wr pulse width (note 3) 35 40 45 ns t whax 1 trailing edge of wr to address invalid (note 3) 8 9 10 ns t whax 2 trailing edge of wr to dpld address input invalid (notes 3 and 4) 0 0 0 ns t whpv trailing edge of wr to port output valid using i/o port data register (note 3) 30 35 38 ns t avpv address input valid to address (note 2) 25 28 30 ns output delay write timing (5 v 10% versions) notes: 1. any input used to select an internal PSD913F1 function. 2. in multiplexed mode, latched addresses generated from adio delay to address output on any port. 3. wr timing has the same timing as e, lds, uds, wrl, and wrh signals. 4. address hold time for dpld inputs that are used to generate chip selects for internal psd memory. microcontroller interface ? PSD913F1 ac/dc parameters (5v 10% versions) note: 1. fast slew rate output available on pa[3:0], pb[3:0], and pd[2:0]. -90 -12 -15 turbo slew symbol parameter conditions min max min max min max off (note 1) unit pld input pin/feedback t pd to pld combinatorial 25 30 32 add 10 sub 2 ns output t ard pld array delay 16 18 22 ns pld combinatorial timing (5 v 10%)
PSD913F1 preliminary 72 symbol parameter conditions min typ max unit t nlnh warm reset active low time (note 1) 150 ns t opr reset high to operational device 120 ns t nlnh-po power on reset active low time 1ms (note 2) reset timing (5 v 10%) note: 1. t clcl is the clkin clock period. microcontroller interface ? PSD913F1 ac/dc parameters (5v 10% versions) symbol parameter conditions min typ max unit t bvbh vstby detection to vstbyon output high 20 s t bxbl v stby off detection to v stbyon output low 20 s v stbyon timing (5 v 10%) -90 -12 -15 symbol parameter conditions min max min max min max unit t lvdv ale access time from power down 90 120 150 ns maximum delay from t clwh apd enable to internal using clkin input 15 * t clcl (note 1) s pdn valid signal power down timing (5 v 10%) note: 1. reset will not reset flash or eeprom programming/erase cycles. 2. tnlnh-po is 10 ms for devices manufactured before rev. a.
preliminary PSD913F1 73 -90 -12 -15 symbol parameter conditions min max min max min max unit t isccf tck clock frequency (except for pld) (note 1) 18 16 14 mhz t iscch tck clock high time (note 1) 26 29 31 ns t isccl tck clock low time (note 1) 26 29 31 ns t isccf-p tck clock frequency (for pld only) (note 2) 2 2 2 mhz t iscch-p tck clock high time (for pld only) (note 2) 240 240 240 ns t isccl-p tck clock low time (for pld only) (note 2) 240 240 240 ns t iscpsu isc port set up time 8 10 10 ns t iscph isc port hold up time 5 5 5 ns t iscpco isc port clock to output 23 24 25 ns t iscpzv isc port high-impedance to valid output 23 24 25 ns t iscpvz isc port valid output to high-impedance 23 24 25 ns isc timing (5 v 10%) microcontroller interface ? PSD913F1 ac/dc parameters (5v 10% versions) symbol parameter min typ max unit flash bulk erase (preprogrammed) (note 1) 3 30 sec flash bulk erase (not preprogrammed) 5 sec t whqv3 sector erase (preprogrammed) 1 30 sec t whqv2 sector erase (not preprogrammed) 2.2 sec t whqv1 byte program 14 1200 s program/erase cycles (per sector) 100,000 cycles t whwlo sector erase time-out 100 s t q7vqv dq7 valid to output (dq7-0) valid 30 ns (data polling) (note 2) flash program, write and erase times (5 v 10%) notes: 1. programmed to all zeros before erase. 2. the polling status dq7 is valid t q7vqv ns, before the data byte dq0-7 is valid for reading. symbol parameter min typ max unit t eehwl write protect after power up 5 msec t blc eeprom byte load cycle timing (note 1) 0.2 120 sec t wcb eeprom byte write cycle time 4 10 msec t wcp eeprom page write cycle time (note 2) 6 30 msec program/erase cycles (per sector) 10,000 cycles eeprom write times (5 v 10%) notes: 1. if the maximum time has elapsed between successive writes to an eeprom page, the transfer of this data to eeprom cells will begin. also, bytes cannot be written (loaded) to a page any faster than the indicated minimum type. 2. these specifications are for writing a page to eeprom cells. notes: 1. for ?on-pld?programming, erase or in isc by-pass mode. 2. for program or erase pld only.
PSD913F1 preliminary 74 symbol parameter conditions min typ max unit v cc supply voltage all speeds 3.0 3.6 v v ih high level input voltage 3.0 v < v cc < 3.6 v .7 v cc v cc +.5 v v il low level input voltage 3.0 v < v cc < 3.6 v .5 0.8 v v ih1 reset high level input voltage (note 1) .8 v cc v cc +.5 v v il1 reset low level input voltage (note 1) ?5 .2 v cc ?1 v v hys reset pin hysteresis 0.3 v v lko v cc min for flash erase and program 1.5 2.2 v v ol output low voltage i ol = 20 a, v cc = 3.0 v 0.01 0.1 v i ol = 4 ma, v cc = 3.0 v 0.15 0.45 v v oh output high voltage except v stby on i oh = 20 a, v cc = 3.0 v 2.9 2.99 v i oh = 1 ma, v cc = 3.0 v 2.7 2.8 v v oh 1 output high voltage v stby on i oh 1 = 1 a v sby ?0.8 v v sby sram standby voltage 2.0 v cc v i sby sram standby current v cc = 0 v 0.5 1 a i idle idle current (v stby pin) v cc > v sby 0.1 0.1 a v df sram data retention voltage only on v stby 2v i sb standby supply current csi >v cc ?.3 v (note 2) 25 100 a for power down mode i li input leakage current v ss < v in < v cc ? .1 1 a i lo output leakage current 0.45 < v in > v cc ?0 5 10 a zpld_turbo = off, f = 0 mhz (note 3) 0ma zpld only zpld_turbo = on, i cc (dc) operating f = 0 mhz 200 400 a/pt (note 3) supply current during flash or flash or eeprom eeprom write/erase only 10 25 ma read only, f = 0 mhz 0 0 ma sram f = 0 mhz 0 0 ma zpld ac adder figure 28a i cc (ac) flash or (note 3) eeprom 1.5 2.0 ma/mhz ac adder sram ac adder 0.8 1.5 ma/mhz PSD913F1v dc characteristics (3.0 v to 3.6 v versions) notes: 1. reset input has hysteresis. v il1 is valid at or below .2v cc ?1. v ih1 is valid at or above .8v cc . 2. csi deselected or internal pd is active. 3. i out = 0 ma
preliminary PSD913F1 75 ac symbols for pld timing. example: t avlx ? time from address valid to ale invalid. signal letters a address input c ceout output d input data e e input l ale input n reset input or output p port signal output q output data r wr, uds, lds, ds, iord, psen inputs s chip select input t r/w input w internal pdn signal b vstby output signal behavior t time l logic level low or ale h logic level high v valid x no longer a valid logic level z float pw pulse width microcontroller interface PSD913F1v ac/dc parameters (3.0 v to 3.6 v versions)
PSD913F1 preliminary 76 -15 -20 turbo symbol parameter conditions min max min max off unit t lvlx ale or as pulse width 26 30 ns t avlx address setup time (note 3) 10 12 ns t lxax address hold time (note 3) 12 14 ns t avqv address valid to data valid (notes 3 and 6) 150 200 add 20 ns t slqv cs valid to data valid 150 200 ns rd to data valid 8-bit bus (note 5) 35 40 ns t rlqv rd or psen to data valid 8-bit bus, 8031, 80251 (note 2) 50 55 ns t rhqx rd data hold time (note 1) 0 0 ns t rlrh rd pulse width (also ds, lds, uds) 40 45 ns rd or psen pulse width (8031, 80251) 55 60 ns t rhqz rd to data high-z (note 1) 40 45 ns t ehel e pulse width 45 52 ns t theh r/w setup time to enable 18 20 ns t eltl r/w hold time after enable 0 0 ns t avpv address input valid to (note 4) 35 40 ns address output delay read timing (3.0 v to 3.6 v versions) microcontroller interface ? PSD913F1v ac/dc parameters (3.0 v to 3.6 v versions) notes: 1. rd timing has the same timing as ds, lds, uds, and psen signals. 2. rd and psen have the same timing for 8031. 3. any input used to select an internal PSD913F1 function. 4. in multiplexed mode latched address generated from adio delay to address output on any port. 5. rd timing has the same timing as ds, lds, and uds signals. 6. in turbo off mode, add 20ns to t avqv .
preliminary PSD913F1 77 -15 -20 symbol parameter conditions min max min max unit t lvlx ale or as pulse width 26 30 t avlx address setup time (note 1) 10 12 ns t lxax address hold time (note 1) 12 14 ns t avwl address valid to leading edge of wr (notes 1 and 3) 20 25 ns t slwl cs valid to leading edge of wr (note 3) 20 25 ns t dvwh wr data setup time (note 3) 45 50 ns t whdx wr data hold time (note 3) 8 10 ns t wlwh wr pulse width (note 3) 48 53 ns t whax 1 trailing edge of wr to address invalid (note 3) 12 17 ns t whax2 trailing edge of wr to dpld address input invalid (notes 3 and 6) 0 0 ns t whpv trailing edge of wr to port output valid using i/o port data register (note 3) 45 50 ns t wlmv wr valid to port output valid using micro ? cell register preset/clear (notes 3 and 4) 90 100 ns t dvmv data valid to port output valid using micro ? cell register preset/clear (notes 3 and 5) 90 100 ns t avpv address input valid to address (note 2) 48 55 ns output delay write, erase and program timing (3.0 v to 3.6 v versions) notes: 1. any input used to select an internal PSD913F1 function. 2. in multiplexed mode, latched addresses generated from adio delay to address output on any port. 3. wr timing has the same timing as e, lds, uds, wrl, and wrh signals. 4. assuming data is stable before active write signal. 5. assuming write is active before data becomes valid. 6. address hold time for dpld inputs that are used to generate chip selects for internal psd memory. microcontroller interface ? PSD913F1v ac/dc parameters (3.0 v to 3.6 v versions) note: 1. fast slew rate output available on pa[3:0], pb[3:0], and pd[2:0]. -15 -20 turbo slew symbol parameter conditions min max min max off (note 1) unit t pd pld input pin/feedback to 48 55 add 20 sub 6 ns pld combinatorial output t ard pld array delay 29 33 ns pld combinatorial timing (3.0 v to 3.6 v versions)
PSD913F1 preliminary 78 -15 -20 symbol parameter conditions min max min max unit t lvdv ale access time from power down 150 200 ns maximum delay from apd enable t clwh to internal pdn valid signal using clkin input 15 * t clcl (note 1) s power down timing (3.0 v to 3.6 v versions) symbol parameter conditions min typ max unit t nlnh warm reset active low time (note 1) 300 ns t opr reset high to operational device 300 ns t nlnh-po power on reset active low time 1ms (note 2) reset timing (3.0 v to 3.6 v versions) note: 1. t clcl is the clkin clock period. microcontroller interface ? PSD913F1v ac/dc parameters (3.0 v to 3.6 v versions) symbol parameter conditions min typ max unit t bvbh v stby detection to v stbyon output high 2.0 s t bxbl v stby off detection to v stbyon output low 2.0 s v stbyon timing (3.0 v to 3.6 v versions) note: 1. reset will not reset flash or eeprom programming/erase cycles. 2. tnlnh-po is 10 ms for devices manufactured before the rev. a.
preliminary PSD913F1 79 microcontroller interface ? PSD913F1v ac/dc parameters (3.0 v to 3.6 v versions) symbol parameter min typ max unit flash bulk erase (preprogrammed) (note 1) 3 30 sec flash bulk erase (not preprogrammed) 5 sec t whqv3 sector erase (preprogrammed) 1 30 sec t whqv2 sector erase (not preprogrammed) 2.2 sec t whqv1 byte program 14 1200 s program/erase cycles (per sector) 100,000 cycles t whwlo sector erase time-out 100 s t q7vqv dq7 valid to output (dq7-0) valid (data polling) (note 2) 30 ns flash program, write and erase times (3.0 v to 3.6 v versions) -15 -20 symbol parameter conditions min max min max unit t isccf tck clock frequency (except for pld) (note 1) 10 9 mhz t iscch tck clock high time (note 1) 45 51 ns t isccl tck clock low time (note 1) 45 51 ns t isccf-p tck clock frequency (for pld only) (note 2) 2 2 mhz t iscch-p tck clock high time (for pld only) (note 2) 240 240 ns t isccl-p tck clock low time (for pld only) (note 2) 240 240 ns t iscpsu isc port set up time 13 15 ns t iscph isc port hold up time 10 10 ns t iscpco isc port clock to output 36 40 ns t iscpzv isc port high-impedance to valid output 36 40 ns t iscpvz isc port valid output to high-impedance 36 40 ns isc timing (3.0 v to 3.6 v versions) notes: 1. programmed to all zeros before erase. 2. the polling status dq7 is valid t q7vqv ns before the data byte dq0-7 is valid for reading. symbol parameter min typ max unit t eehwl write protect after power up 5 msec t blc eeprom byte load cycle timing (note 1) 0.2 120 sec t wcb eeprom byte write cycle time 4 10 msec t wcp eeprom page write cycle time (note 2) 6 30 msec program/erase cycles (per sector) 10,000 cycles eeprom write times (3.0 v to 3.6 v versions) notes: 1. if the maximum time has elapsed between successive writes to an eeprom page, the transfer of this data to eeprom cells will begin. also, bytes cannot be written (loaded) to a page any faster than the indicated minimum type. 2. these specifications are for writing a page to eeprom cells. notes: 1. for ?on-pld?programming, erase or in isc by-pass mode. 2. for program or erase pld only.
PSD913F1 preliminary 80 figure 29. read timing t avlx t lxax * t lvlx t avqv t slqv t rlqv t rhqx trhqz t eltl t ehel t rlrh t theh t avpv address valid address valid data valid data valid address out ale /as a/d multiplexed bus address non-multiplexed bus data non-multiplexed bus csi rd (psen, ds) e r/w * t avlx and t lxax are not required for 80c251 in page mode or 80c51xa in burst mode.
preliminary PSD913F1 81 figure 30. write timing t avlx t lxax t lvlx t avwl t slwl t whdx t whax t eltl t ehel t wlmv t wlwh t dvwh t theh t avpv address valid address valid data valid data valid address out t whpv standard mcu i/o out ale/as a/d multiplexed bus address non-multiplexed bus data non-multiplexed bus csi wr (ds) e r/ w
PSD913F1 preliminary 82 figure 31. combinatorial timing ? pld t pd cpld input cpld output figure 32. isc timing iscch tck tdi/tms isc outputs/tdo isc outputs/tdo t isccl t iscph t iscpsu t iscpvz t iscpzv t iscpco t
preliminary PSD913F1 83 figure 33. reset timing figure 34. key to switching waveforms operating level power on reset v cc reset t nlnh po t opr t nlnh t opr warm reset waveforms inputs outputs steady input may change from hi to lo may change from lo to hi don't care outputs only steady output will be changing from hi to lo will be changing lo to hi changing, state unknown center line is tri-state
PSD913F1 preliminary 84 symbol parameter 1 conditions typical 2 max unit c in capacitance (for input pins only) v in = 0 v 4 6 pf c out capacitance (for input/output pins) v out = 0 v 8 12 pf c vpp capacitance (for cntl2/v pp )v pp = 0 v 18 25 pf notes: 1. these parameters are only sampled and are not 100% tested. 2. typical values are for t a = 25 c and nominal supply voltages. t a = 25 ?, f = 1 mhz pin capacitance figure 35. ac testing input/output waveform figure 36. ac testing load circuit programming 3.0v 0v test point 1.5v device under test 2.01 v 195 c l = 30 pf (including scope and jig capacitance) upon delivery from st, the PSD913F1 device has all bits in the plds and memories in the 1 or high state. the configuration bits are in the 0 or low state. the code, configuration, and plds logic are loaded through the procedure of programming. information for programming the device is available directly from st. please contact your local sales representative. (see the last page.)
preliminary PSD913F1 85 PSD913F1 pin assignments pin no. pin assignments pin no. pin assignments 1 gnd 27 pa2 2 pb5 28 pa1 3 pb4 29 pa0 4 pb3 30 ad0 5 pb2 31 ad1 6 pb1 32 ad2 7 pb0 33 ad3 8 pd2 34 ad4 9 pd1 35 ad5 10 pd0 36 ad6 11 pc7 37 ad7 12 pc6 38 v cc 13 pc5 39 ad8 14 pc4 40 ad9 15 v cc 41 ad10 16 gnd 42 ad11 17 pc3 43 ad12 18 pc2 (vstby) 44 ad13 19 pc1 45 ad14 20 pc0 46 ad15 21 pa7 47 cntl0 22 pa6 48 reset 23 pa5 49 cntl2 24 pa4 50 cntl1 25 pa3 51 pb7 26 gnd 52 pb6 52-pin plastic leaded chip carrier (pldcc) (package type j)
PSD913F1 preliminary 86 pin no. pin assignments pin no. pin assignments 1 pd2 27 ad4 2 pd1 28 ad5 3 pd0 29 ad6 4 pc7 30 ad7 5 pc6 31 vcc 6 pc5 32 ad8 7 pc4 33 ad9 8 vcc 34 ad10 9 gnd 35 ad11 10 pc3 36 ad12 11 pc2 37 ad13 12 pc1 38 ad14 13 pc0 39 ad15 14 pa7 40 cntl0 15 pa6 41 reset 16 pa5 42 cntl2 17 pa4 43 cntl1 18 pa3 44 pb7 19 gnd 45 pb6 20 pa2 46 gnd 21 pa1 47 pb5 22 pa0 48 pb4 23 ad0 49 pb3 24 ad1 50 pb2 25 ad2 51 pb1 26 ad3 52 pb0 PSD913F1 pin assignments 52-pin plastic quad flatpack (pqfp) (package type m)
preliminary PSD913F1 87 PSD913F1 package information 1 pb0 pb1 pb2 pb3 pb4 pb5 gnd pb6 pb7 cntl1 cntl2 reset cntl0 pa7 pa6 pa5 pa4 pa3 gnd pa2 pa1 pa0 ad0 ad1 ad2 ad3 51 50 49 48 47 52 46 45 44 43 42 41 40 39 38 37 36 35 34 8 9 10 11 12 13 14 15 16 17 18 19 20 765432 v cc pd2 pd1 pd0 pc7 pc6 pc5 pc4 gnd pc3 pc2 (vstby) pc1 pc0 ad15 ad14 ad13 ad12 ad11 ad10 v cc ad8 ad9 ad7 ad6 ad5 ad4 21 22 23 24 25 26 27 28 29 30 31 32 33 figure 37. drawing j7 ? 52-pin plastic leaded chip carrier (pldcc) (package type j) gnd pb6 pb7 cntl1 cntl2 reset pa6 v cc v cc ad15 ad14 cntl0 ad13 ad12 ad11 ad10 gnd pc3 pc1 pc0 pa7 pa5 pa4 pa3 pc2 gnd pa2 1 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 pc4 pc5 pc6 pc7 pd0 pd1 pd2 pb0 pb1 pb2 pb3 pb4 pb5 pa1 pa0 ad0 ad1 ad2 ad3 ad4 ad5 ad6 ad7 ad8 ad9 figure 38. drawing m3 ? 52-pin plastic quad flatpack (pqfp) (package type m)
PSD913F1 preliminary 88 family: plastic leaded chip carrier millimeters inches symbol min max notes min max notes a 4.19 4.57 0.165 0.180 a1 2.54 2.79 0.100 0.110 a2 3.66 3.86 0.144 0.152 b 0.33 0.53 0.013 0.021 b1 0.66 0.81 0.026 0.032 c 0.246 0.261 0.0097 0.0103 d 19.94 20.19 0.785 0.795 d1 19.05 19.15 0.750 0.754 d2 17.53 18.54 0.690 0.730 d3 15.24 reference 0.600 reference e 19.94 20.19 0.785 0.795 e1 19.05 19.15 0.750 0.754 e2 17.53 18.54 0.690 0.730 e3 15.24 reference 0.600 reference e1 1.27 reference 0.050 reference n52 52 020197r1 figure 37a. drawing j7 ? 52-pin plastic leaded chip carrier (pldcc) (package type j) e1 e 52 51 1 2 3 d1 d view a r .025 .045 d3 b1 b a1 a d2 a2 c e3 e1 view a e2
preliminary PSD913F1 89 figure 38a. drawing m3 ? 52-pin plastic quad flatpack (pqfp) (package type m) d d1 d3 e3 e1 e index mark standoff: 0.05 mm min. lead coplanarity: 0.1mm max. l c a2 b 52 1 2 3 e1 a family: plastic quad flatpack (pqfp) millimeters inches symbol min max notes min max notes 0 7 0 7 a 2.35 0.093 a2 1.95 2.10 0.077 0.083 b 0.22 0.38 reference 0.009 0.015 c 0.23 0.009 d 1 2 . 9 5 13. 4 5 0.5 10 0.5 30 d1 9.9 0 10. 10 0.39 0 0.39 8 d3 7.80 reference 0.307 reference e 1 2 . 9 5 13. 4 5 0.51 0 0.5 30 e1 9.9 0 10. 10 0.39 0 0.39 8 e3 7.80 reference 0.307 reference e1 0.65 reference 0.026 reference l 0.73 1.03 0.029 0.041 n52 52 060198r0
PSD913F1 preliminary 90 part # mcu plds/decoders i/o memory other psd psd data path pld inputs ports flash program store jtag @ @ interface input micro ? cells otp eprom boot parallel isp 5 v 3 v output eeprom/eeprom boot isp flash micro ? cells 2nd flash boot isp cpld pld outputs sram periph. mode page (w/bb) security reg. pmu apd psd813f1 psd813f1v 8 plus1 73 24 16 19 8-bit 27 1024kb 256kb 16kb x x x x x x x x PSD913F1 PSD913F1v 8 plus1 57 0 0 19 8-bit 27 1024kb 256kb 16kb x x x x x x x x selector guide ?psd813f1 and PSD913F1 family legend: zpsd = zero power version available at 4.5 v to 5.5 v v cc (example: zpsd311-15j). zpsdv = zero power version available at 2.7 v to 5.5 v v cc (example: zpsd311v-25j). 2.7 v to 3.6 v v cc on psd8xxf family. std = standard mcu interfaces supported (multiplexed and non-multiplexed). std-m = standard mcu interfaces supported (multiplexed only). plus = new intel 80c251 and philips 80c51xa supported plus all standard mcus. w/bb = battery backed-up sram. apd = automatic power down. selector guide
preliminary PSD913F1 91 operating speed temperature part number (ns) package type range PSD913F1-90j 90 52 pin pldcc comm? PSD913F1-90ji 90 52 pin pldcc industrial PSD913F1-90m 90 52 pin pqfp comm? PSD913F1-90mi 90 52 pin pqfp industrial PSD913F1-12ji 120 52 pin pldcc industrial PSD913F1-12mi 120 52 pin pqfp industrial PSD913F1v-15j 150 52 pin pldcc comm? PSD913F1v-15m 150 52 pin pqfp comm? PSD913F1v-20ji 200 52 pin pldcc industrial PSD913F1v-20mi 200 52 pin pqfp industrial part number construction ordering information temperature (blank = commercial, i = industrial, m = military) package type speed (-70 = 70ns, -90 = 90ns, -15 = 150ns -20 = 200ns, -25 = 250ns) revision (blank = no revision) supply voltage (blank = 5v, v = 3 volt) base part number - see selector guide psd (st programmable system device) fam. psd -a -20 j i 413a2 v
PSD913F1-a 2/3 revision history table 1. document revision history date rev. description of revision aug-2000 1.0 document written in the wsi format 04-jan-2002 1.1 front page, and back two pages, in st format, added to the pdf file references to waferscale, wsi, easyflash and psdsoft 2000 updated to st, st, flash+psd and psdsoft express
3/3 PSD913F1-a information furnished is believed to be accurate and reliable. however, stmicroelectronics assumes no responsibility for the co nsequences of use of such information nor for any infringement of patents or other rights of third parties which may result from its use. no license is granted by implication or otherwise under any patent or patent rights of stmicroelectronics. specifications mentioned in this publicati on are subject to change without notice. this publication supersedes and replaces all information previously supplied. stmicroelectronics prod ucts are not authorized for use as critical components in life support devices or systems without express written approval of stmicroelectro nics. the st logo is registered trademark of stmicroelectronics all other names are the property of their respective owners ? 2002 stmicroelectronics - all rights reserved stmicroelectronics group of companies australia - brazil - canada - china - finland - france - germany - hong kong - india - israel - italy - japan - malaysia - malta - morocco - singapore - spain - sweden - switzerland - united kingdom - unit ed states. www.st.com

▲Up To Search▲

Price & Availability of PSD913F1

	To Download PSD913F1 Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .