Part Number Hot Search : 
100135FC 5740E 74F32 AN520 4ALVCH1 OP02N 35021 3TRG1
Product Description
Full Text Search
 

To Download CY14B256P-SFXIT Datasheet File

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


  Datasheet File OCR Text:
  cy14b256p 256-kbit (32 k 8) serial (spi) nvsram with real time clock cypress semiconductor corporation ? 198 champion court ? san jose , ca 95134-1709 ? 408-943-2600 document number: 001-53881 rev. *f revised july 19, 2011 256-kbit (32 k 8) serial (spi) nvsram with real time clock features 256-kbit nonvolatile static random access memory (nvsram) ? internally organized as 32 k 8 ? store to quantumtrap nonvolatile elements initiated automatically on power-down (aut ostore) or by user using hsb pin (hardware store) or spi instruction (software store) ? recall to sram initiated on power-up (power-up recall) or by spi instruction (software recall) ? automatic store on power-down with a small capacitor high reliability ? infinite read, write, and recall cycles ? 1 million store cycles to quantumtrap ? data retention: 20 years real time clock (rtc) ? full-featured rtc ? watchdog timer ? clock alarm with programmable interrupts ? capacitor or battery backup for rtc ? backup current of 0.35 a (typical) high-speed serial peripheral interface (spi) ? 40-mhz clock rate ? sram memory access ? 25-mhz clock rate ? rtc memory access ? supports spi mode 0 (0,0) and mode 3 (1,1) write protection ? hardware protection using write protect (wp ) pin ? software protection using write disable instruction ? software block protection fo r 1/4, 1/2, or entire array low power consumption ? single 3 v +20%, ?10% operation ? average active current of 10 ma at 40 mhz operation industry standard configurations ? industrial temperature ? 16-pin small outline integrated circuit (soic) package ? restriction of hazardous s ubstances (rohs) compliant overview the cypress cy14b256p combines a 256-kbit nvsram [1] with a full-featured real time clock in a monolithic integrated circuit with serial spi interface. the memory is organized as 32 k words of 8 bits each. the embedded nonvolatile elements incorporate the quantumtrap technology, creating the world?s most reliable nonvolatile memory. the sram provides infinite read and write cycles, while the quantumtrap ce lls provide highly reliable nonvolatile storage of data. data transfers from sram to the nonvolatile elements (store operation) takes place automatically at power-down. on power-up, data is restored to the sram from the nonvolatile memory (recall operation). the store and recall operations can also be initiated by the user through spi instruction. instruction register address decoder data i/o register status register power control store/recall control instruction decode write protect control logic quantumtrap store recall si sck v cc v cap so hsb 32 k x 8 sram array 32 k x 8 rtc x x int mux a0-a14 d0-d7 hold cs wp out in logic block diagram note 1. this device will be referred to as nvsram throughout the document. for evaluation samples only. production will be supported with the next revision silicon in soic package.
cy14b256p document number: 001-53881 rev. *f page 2 of 36 contents pinouts .............................................................................. 3 device operation .............................................................. 4 sram write.................................................................. 4 sram read ................................................................ 4 store operation ....................................................... 4 autostore operation .................................................... 4 software store operation ........................................ 5 hardware store and hsb pin operation ................. 5 recall operation...................................................... 5 hardware recall (power-up) .................................. 5 software recall ....................................................... 5 disabling and enabling autostore............................... 5 noise considerations....................................................... 5 serial peripheral interface ............................................... 6 spi overview ............................................................... 6 spi modes ......................................................................... 7 spi operating features..................................................... 8 power-up .................................................................... 8 power on reset .......................................................... 8 power-down ................................................................ 8 active power and stand ................... by power modes 8 spi functional description....... ............ ...................... ..... 8 status register ................................................................. 9 read status register (rdsr) instruction ................... 9 write status register (wrsr) instruction .................. 9 write protection and block protection ......................... 10 write enable (wren) instruction .............................. 10 write disable (wrdi) instruction .............................. 10 block protection ........................................................ 10 hardware write protection (wp pin)......................... 11 memory access .............................................................. 11 read sequence (read) instruction .......................... 11 write sequence (write) instru ction ............. ........... 11 rtc access ..................................................................... 13 read rtc (rdrtc) instruction .............................. 13 write rtc (wrtc) instruction ............................... 13 software store (store) instruction ...................... 14 software recall (recall) instruction .................. 14 autostore enable (asenb) in struction ....... .............. 14 autostore disable (asdisb) in struction ................... 15 hold pin operation ................................................. 15 real time clock operation............................................. 16 nvtime operation...................................................... 16 clock operations ....................................................... 16 reading the clock ...... ........................................... .... 16 setting the clock ....................................................... 16 backup power ........................................................... 16 stopping and starting the oscillator .......................... 16 calibrating the clock ................................................. 17 alarm ......................................................................... 17 watchdog timer ........................................................ 17 power monitor ........................................................... 18 interrupts ................................................................... 18 flags register ........................................................... 18 accessing the real time clock through spi............. 19 best practices................................................................. 24 maximum ratings ........................................................... 25 dc electrical characteristics ........................................ 25 data retention and endurance ..................................... 26 capacitance .................................................................... 26 thermal resistance........................................................ 26 ac test conditions ........................................................ 26 rtc characteristics ....................................................... 27 ac switching characteristics ....................................... 27 autostore or power-up recall .................................. 29 software controlled store/recall cycles .............. 30 hardware store cycle ................................................. 31 ordering information ...................................................... 32 ordering code definition........ ................................... 32 package diagram ............................................................ 33 acronyms ........................................................................ 34 document conventions ................................................. 34 units of measure ....................................................... 34 document history page ................................................. 35 sales, solutions, and legal information ...................... 36 worldwide sales and design supp ort............. .......... 36 products .................................................................... 36 psoc solutions ......................................................... 36 for evaluation samples only. production will be supported with the next revision silicon in soic package.
cy14b256p document number: 001-53881 rev. *f page 3 of 36 pinouts figure 1. pin diagram C 16-pin soic table 1. pin definitions pin name i/o type description cs input chip select. activates the device when pulled low. driving this pin high puts the device in low power standby mode. sck input serial clock. runs at speeds up to maximum of f sck . serial input is latched at the rising edge of this clock. serial output is driven at the falling edge of the clock. si input serial input. pin for input of all spi instructions and data. so output serial output. pin for output of data through spi. wp input write protect. implements hardware write protection in spi. hold input hold pin. suspends serial operation. hsb input/output hardware store busy: output: indicates bu sy status of nvsram when low. after each hardware and software store operation hsb is driven high for a short time (t hhhd ) with standard output high current and then a weak internal pull-up resistor keeps this pin hi gh (external pull-up resistor connection optional). input: hardware store implemented by pulling this pin low externally. v cap power supply autostore capacitor. supplies power to the nvsram during power loss to store data from the sram to nonvolatile elements. if autostore is not needed, this pin must be left as no connect. it must never be connected to ground. v rtccap power supply capacitor backup for rtc. left unconnected if v rtcbat is used. v rtcbat power supply battery backup for rtc. left unconnected if v rtccap is used. xout output crystal output connecti on. drives crystal on start up. xin input crystal input connection. for 32.768 khz crystal. int output interrupt output. programmable to respond to the clock alarm, the watchdog timer, and the power monitor. also programmable to either active high (push or pull) or low (open drain). nc no connect no connect. this pin is not connected to the die. v ss power supply ground v cc power supply power supply (2.7 v to 3.6 v) int wp v cap 1 2 3 4 5 6 7 8 9 10 11 12 13 nc 16 15 14 v cc so si sck cs hsb hold to p vi e w not to scale v rtcbat x out x in v rtccap v ss for evaluation samples only. production will be supported with the next revision silicon in soic package.
cy14b256p document number: 001-53881 rev. *f page 4 of 36 device operation cy14b256p is a 256-kbit nvsr am memory with integrated rtc and spi interface. all the read s and writes to nvsram happen to the sram which gives nvsram the unique capability to handle infinite writes to the memory. the data in sram is secured by a store sequence that transfers the data in parallel to the nonvolatile quantumtrap cells. a small capacitor (v cap ) is used to autostore the sram data in nonvolatile cells when power goes down providing power-down data security. the quantumtrap nonvolatile elements built in the reliable sonos technology make nvsram the ideal choice for secure data storage. in cy14b256p, the 256-kbit memory array is organized as 32 k words 8 bits. the memory is accessed through a standard spi interface that enables very high clock speeds up to 40 mhz with zero cycle delay read and write cycles. cy14b256p supports spi modes 0 and 3 (cpo l, cpha = 0, 0 and 1, 1) and operates as spi slave. the device is enabled using the chip select (cs ) pin and accessed through serial input (si), serial output (so), and serial clock (sck) pins. cy14b256p provides the feature for hardware and software write protection through the wp pin and wrdi instruction. cy14b256p also provides mechanisms for block write protection (quarter, half, or full array) using bp0 and bp1 pins in the status register . further, the hold pin is used to suspend any serial communication without resetting the serial sequence. cy14b256p uses the standard spi opcodes for memory access. in addition to the general spi in structions for read and write, cy14b256p provides four special instructions that allow access to four nvsram specific functions: store, recall, autostore disable (asdisb), and au tostore enable (asenb). the major benefit of nvsram over serial eeproms is that all reads and writes to nvsram are performed at the speed of spi bus with zero cycle delay. theref ore, no wait ti me is required after any of the memory accesses. the store and recall operations need finite time to complete and all memory accesses are inhibited during this time. while a store or recall operation is in progress, the busy status of the device is indicated by the hardware store busy (hsb ) pin and also reflected on the rdy bit of the status register. sram write all writes to nvsram are carried out on the sram and do not use up any endurance cycles of the nonvolatile memory. this enables the user to perform infinite write operations. a write cycle is performed through the write instruction. the write instruction is issued through the si pin of the nvsram and consists of the write opcode, two bytes of address, and one byte of data. write to nvsram is done at spi bus speed with zero cycle delay. cy14b256p allows burst mode writes to be performed through spi. this enables write operati ons on consecutive addresses without issuing a new write inst ruction. when the last address in memory is reached in burst mode, the address rolls over to 0x0000 and the device continues to write. the spi write cycle sequence is defined in the memory access section of spi protocol description. sram read a read cycle in cy14b256p is performed at the spi bus speed and the data is read out with zero cycle delay after the read instruction is executed. the r ead instruction is issued through the si pin of the nvsram and c onsists of the read opcode and two bytes of address. the data is read out on the so pin. cy14b256p allows burst mode reads to be performed through spi. this enables reads on consecutive addresses without issuing a new read instruction. when the last address in memory is reached in burst mode read, the address rolls over to 0x0000 and the device continues to read. the spi read cycle sequenc e is defined in the memory access section of spi protocol description. store operation store operation transfers the data from the sram to the nonvolatile quantumtrap cells. the cy14b256p stores data to the nonvolatile cells using one of the three store operations: autostore, activated on device power-down; software store, activated by a store instruction; and hardware store, activated by the hsb . during the store cycle, an erase of the previous nonvolatile data is first performed, followed by a program of the nonvolatile elements. after a store cycle is initiated, read/write to cy14b256p is inhibited until the cycle is completed. the hsb signal or the rdy bit in the status register can be monitored by the system to detect if a store or software recall cycle is in progress. the busy status of nvsram is indicated by hsb being pulled low or rdy bit being set to ?1?. to avoid unnecessary nonvolatile stores, autostore and hardware store operations are ignored unless at least one write operation has taken place since the most recent store or recall cycle. however, software initiated store cycles are performed regardless of whether a write operation has taken place. autostore operation the autostore operation is a unique feature of nvsram which automatically stores the sram data to quantumtrap cells during power-down. this store makes use of an external capacitor (v cap ) and enables the device to safely store the data in the nonvolatile memory when power goes down. during normal operation, the device draws current from v cc to charge the capacitor connected to the v cap pin. when the voltage on the v cc pin drops below v switch during power-down, the device inhibits all memory accesses to nvsram and automatically performs a conditional store operation using the charge from the v cap capacitor. the autostore operation is not initiated if no write cycle was performed since the last recall . note if a capacitor is not connected to v cap pin, autostore must be disabled by issuing the autostore disable instruction specified in autostore enable (asenb) instruction on page 14 . if autostore is enabled without a capacitor on v cap pin, the device attempts an autostore operation without sufficient charge to complete the store. this corrupts the data stored in the nvsram and status register. to resume normal functionality, the wrsr instruction must be issued to update the nonvolatile bits bp0, bp1 and wpen in the status register. for evaluation samples only. production will be supported with the next revision silicon in soic package.
cy14b256p document number: 001-53881 rev. *f page 5 of 36 figure 2 shows the proper connection of the storage capacitor (v cap ) for autostore operation. refer to dc electrical characteristics on page 25 for the size of the v cap . figure 2. autostore mode software store operation software store allows the user to trigger a store operation through a special spi instruction. store operation is initiated by executing store instruction irrespective of whether a write has been performed since the last nv operation. a store cycle takes t store time to complete, during which all the memory accesses to nvsram are inhibited. the rdy bit of the status register or the hsb pin may be polled to find the ready/busy status of the nvsram. after the t store cycle time is completed, the sram is activated again for read and write operations. hardware store and hsb pin operation the hsb pin in cy14b256p is used to control and acknowledge store operations. if no store/recall is in progress, this pin can be used to request a ha rdware store cycle. when the hsb pin is driven low, the cy14b256p conditionally initiates a store operation after t delay duration. an actual store cycle starts only if a write to the sram is performed since the last store or recall cycle. reads and writes to the memory are inhibited for t store duration or as long as hsb pin is low. the hsb pin also acts as an open drain driver (internal 100 k weak pull-up resistor) that is internally driven low to indicate a busy condition when the store (initiated by any means) is in progress. note after each hardware and software store operation hsb is driven high for a short time (t hhhd ) with standard output high current and then remains high by an internal 100 k pull-up resistor. note for successful last data byte store, a hardware store should be initiated at least one clock cycle afte r the last data bit d0 is received. upon completion of the store operation, the nvsram memory access is inhibited for t lzhsb time after hsb pin returns high. the hsb pin must be left unconnected if not used. recall operation a recall operation transfers th e data stored in the nonvolatile quantumtrap elements to the sram. in cy14b256p, a recall may be initiated in two ways: hardware recall, initiated on power-up; and software recall, initiated by a spi recall instruction. internally, recall is a two step procedure. first, the sram data is cleared. next, the nonvolatile information is transferred into the sram cells. all memory accesses are inhibited while a recall cycle is in progress. the recall operation does not alter the data in the nonvolatile elements. hardware recall (power-up) during power-up, when v cc crosses v switch , an automatic recall sequence is initiated, which transfers the content of nonvolatile memory on to the sram. a power-up recall cycle takes t fa time to complete and the memory access is disabled during this time. hsb pin is used to detect the ready status of the device. software recall software recall allows the user to initiate a recall operation to restore the content of nonvola tile memory on to the sram. in cy14b256p, this can be done by issuing a recall instruction in spi. a software recall takes t recall time to complete during which all memory accesses to nvsram are inhibited. the controller must provide sufficient delay for the recall operation to complete before issuing any memory access instructions. disabling and enabling autostore if the application does not require the autostore feature, it can be disabled in cy14b256p by using the asdisb instruction. if this is done, the nvsram does not perform a store operation at power-down. note cy14b256p comes from the factory with autostore enabled. autostore can be re-enabled by using the asenb instruction. however, these operations are not nonvolatile and if the user needs this setting to survive th e power cycle, a store operation must be performed following autostore disable or enable operation. note if autostore is disabled and v cap is not required, then the v cap pin must be left open. the v cap pin must never be connected to ground. the po wer-up recall operation cannot be disabled in any case. noise considerations refer to cy application note an1064 . 0.1 uf v cc 10 kohm v cap cs v cap v ss v cc for evaluation samples only. production will be supported with the next revision silicon in soic package.
cy14b256p document number: 001-53881 rev. *f page 6 of 36 serial peripheral interface spi overview the spi is a four-pin interface with chip select (cs ), serial input (si), serial output (so), and serial clock (sck) pins. cy14b256p provides serial access to nvsram through spi interface. the spi bus on cy14b256p can run at speeds of up to 40 mhz for all instructions except rdrtc which runs at 25 mhz. the spi is a synchronous serial interface which uses clock and data pins for memory access and supports multiple devices on the data bus. a device on spi bus is activated using the cs pin. the relationship between chip select, clock, and data is dictated by the spi mode. cy14b256p supports spi modes 0 and 3. in both these modes, data is clocke d into the nvsram on the rising edge of sck starting from the first rising edge after cs goes active. the spi protocol is controlled by opcodes. these opcodes specify the commands from the bus master to the slave device. after cs is activated the first byte transferred from the bus master is the opcode. following the opcode, any addresses and data are then transferred. the cs must go inactive after an operation is complete and before a new opcode can be issued. the commonly used terms used in spi protocol are as follows. spi master the spi master device controls the operations on a spi bus. a spi bus may have only one master with one or more slave devices. all the slaves share the same spi bus lines and the master may select any of the slave devices using the cs pin. all the operations must be initiated by the master activating a slave device by pulling the cs pin of the slave low. the master also generates the sck and all the data transmission on si and so lines are synchronized with this clock. spi slave the spi slave device is activated by the master through the chip select line. a slave device gets the sck as an input from the spi master and all the communication is synchronized with this clock. spi slave never initiates a communication on the spi bus and acts on the instruction from the master. cy14b256p operates as a slave device and may share the spi bus with multiple cy14b256p devices or other spi devices. chip select (cs ) for selecting any slave device, the master needs to pull-down the corresponding cs pin. any instruction can be issued to a slave device only when the cs pin is low. the cy14b256p is selected when the cs pin is low. when the device is not selected, data through the si pin is ignored and the serial output pin (so) remains in a high-impedance state. note a new instruction must begin with the falling edge of cs . therefore, only one opcode can be issued for each active chip select cycle. serial clock (sck) serial clock is generated by the spi master and the communication is synchronized with this clock after cs goes low. cy14b256p allows spi modes 0 and 3 for data communication. in both these modes, the inputs are latched by the slave device on the rising edge of sck and outputs are issued on the falling edge. therefore, the first rising edge of sck signifies the arrival of the first bit (msb) of spi instru ction on the si pin. further, all data inputs and outputs are synchronized with sck. data transmission si and so spi data bus consists of two lines, si and so, for serial data communication. the si is also re ferred to as master out slave in (mosi) and so is referred to as master in slave out (miso). the master issues instructions to the slave through the si pin, while the slave responds through the so pin. multiple slave devices may share the si and so lines as described earlier. cy14b256p has two separate pins for si and so which can be connected with the master as shown in figure 3 on page 7 . most signific ant bit (msb) the spi protocol requires that the first bit to be transmitted is the most significant bit (msb). this is valid for both address and data transmission. the 256-kbit serial nvsram requires a 2-byte address for any read or write operation. howeve r, because the address is only 15 bits, it implies that the first msb which is fed in is ignored by the device. although this bit is ?don?t care?, cypress recommends that this bit is treated as 0 to enable seamless transition to higher memory densities. serial opcode after the slave device is selected with cs going low, the first byte received is treated as the opcode for the intended operation. cy14b256p uses the standard opcodes for memory accesses. in addition to the memory accesses, cy14b256p provides additional opcodes for the nvsram specific functions: store, recall, autostore enable, and autostore disable. refer to table 2 on page 8 for details on opcodes. invalid opcode if an invalid opcode is received, the opcode is ignored and the device ignores any additional serial data on the si pin till the next falling edge of cs and the so pin remains tri-stated. status register cy14b256p has an 8-bit status register. the bits in the status register are used to configur e the spi bus. these bits are described in the table 4 on page 9 . for evaluation samples only. production will be supported with the next revision silicon in soic package.
cy14b256p document number: 001-53881 rev. *f page 7 of 36 spi modes cy14b256p device may be driven by a microcontroller with its spi peripheral running in either of these two modes: spi mode 0 (cpol=0, cpha=0) spi mode 3 (cpol=1, cpha=1) for both these modes, the input data is latched in on the rising edge of sck starting from the first rising edge after cs goes active. if the clock starts from a high state (in mode 3), the first rising edge after the clock toggles is considered. the output data is available on the falling edge of sck. the two spi modes are shown in figure 4 and figure 5 . the status of clock when the bus ma ster is in standby mode and not transferring data is: sck remains at 0 for mode 0 sck remains at 1 for mode 3 cpol and cpha bits must be set in the spi controller for the either mode 0 or mode 3. cy 14b256p detects the spi mode from the status of sck pin when the device is selected by bringing the cs pin low. if sck pin is low when the device is selected, spi mode 0 is assumed and if sck pin is high, cy14b256p works in spi mode 3. figure 3. system configuration using spi nvsram p652b41yc p652b41yc ucontroller sck mosi miso si so o sis kc ss c k cs hold hold cs cs1 cs2 hold1 hold2 figure 4. spi mode 0 lsb msb 765432 10 cs sck si 0 1 2 3 4 5 6 7 figure 5. spi mode 3 cs sck si 765432 10 lsb msb 0 1 2 3 4 5 6 7 for evaluation samples only. production will be supported with the next revision silicon in soic package.
cy14b256p document number: 001-53881 rev. *f page 8 of 36 spi operating features power-up power-up is defined as the condition when the power supply is turned on and v cc crosses vswitch voltage. during this time, the cs must be enabled to follow the v cc voltage. therefore, cs must be connected to v cc through a suitable pull-up resistor. as a built in safety feature, cs is both edge-sensitive and level-sensitive. after power-up, the device is not selected until a falling edge is detected on cs . this ensures that cs must have been high, before going low to start the first operation. as described earlier, nvsram performs a power-up recall operation after power-up and therefore, all memory accesses are disabled for t fa duration after power-up. the hsb pin can be probed to check the ready/busy status of nvsram after power-up. power on reset a power on reset (por) circuit is included to prevent inadvertent writes. at power-up, the device does not respond to any instruction until the v cc reaches the por threshold voltage (v switch ). after v cc transitions the por threshold, the device is internally reset and performs an power-up recall operation. during power-up recall all device accesses are inhibited. the device is in the following state after por: deselected (after power-up, a falling edge is required on cs before any instructio ns are started). standby power mode not in the hold condition status register state: ? write enable (wen) bit is reset to ?0?. ? wpen, bp1, bp0 unchanged from previous store operation ? don?t care bits 4-6 are reset to ?0?. the wpen, bp1, and bp0 bits of the status register are nonvolatile bits and remain unchanged from the previous store operation. prior to selecting and issuing instructions to the memory, a valid and stable v cc voltage must be applied. this voltage must remain valid until the end of the instruction transmission. power-down at power-down (continuous decay of v cc ), when v cc drops from the normal operating voltage and below the v switch threshold voltage, the device stops responding to any instruction sent to it. if a write cycle is in progress and the last data bit d0 has been received when the power goes down, it is allowed t delay time to complete the write. after this, all memory accesses are inhibited and a conditional autostore operation is performed (autostore is not performed if no writes have happened since the last recall cycle). this feature prevents inad vertent writes to nvsram from happening during power-down. however, to avoid the possibility of inadvertent writes during power-down, ensure that the device is deselected and is in standby power mode, and the cs follows the voltage applied on v cc . active power and standby power modes when cs is low, the device is selected and is in the active power mode. the device consumes i cc current, as specified in dc electrical characteristics on page 25 . when cs is high, the device is deselected and the device goes into the standby power mode if a store or recall cycl e is not in progress. if a store/recall cycle is in progre ss, the device goes into the standby power mode after the store/recall cycle is completed. in the standby power mode, the current drawn by the device drops to i sb . spi functional description the cy14b256p uses an 8-bit instruction register. instructions and their operation codes are listed in table 2 . all instructions, addresses, and data are transferr ed with the msb first and start with a high to low cs transition. there are, in all, 12 spi instructions that provide acce ss to most of the functions in nvsram. further, the wp , hold and hsb pins provide additional functionality driven through hardware. the spi instructions in cy14b 256p are divided based on their functionality in the following types: ? status register access: rds r and wrsr instructions ? write protection functions: wr en and wrdi instructions along with wp pin and wen, bp0, and bp1 bits ? sram memory access: read and write instructions ? rtc access: rdrtc and wrtc instructions ? nvsram special instructions: store, recall, asenb, and asdisb table 2. instruction set instruction category instruction name opcode operation status register instructions wren 0000 0110 set write enable latch wrdi 0000 0100 reset write enable latch rdsr 0000 0101 read status register wrsr 0000 0001 write status register sram read/write instructions read 0000 0011 read data from memory array write 0000 0010 write data to memory array rtc read/write instructions rdrtc 0001 0011 read rtc registers wrtc 0001 0010 write rtc registers special nv instructions store 0011 1100 software store recall 0110 0000 software recall asenb 0101 1001 autostore enable asdisb 0001 1001 autostore disable reserved - reserved - 0001 1110 for evaluation samples only. production will be supported with the next revision silicon in soic package.
cy14b256p document number: 001-53881 rev. *f page 9 of 36 status register the status register bits are listed in ta b l e 3 . the status register consists of a ready bit (rdy ) and data protection bits bp1, bp0, wen, and wpen. the rdy bit can be polled to check the re ady/busy status while a nvsram store or software recall cycle is in progress. the status register can be m odified by wrsr instruction and read by rdsr instruction. however, only the wpen, bp1, and bp0 bits of the status register can be modified by using th e wrsr instruction. the wrsr in struction has no effect on wen an d rdy bits. the default value shipped from the factory for wen, bp0, bp1, bits 4-6 and wpen bits is ?0?. read status register (rdsr) instruction the read status register (rds r) instruction provides access to the status register. this instru ction is used to probe the write enable status of the device or the ready status of the device. rdy bit is set by the device to ?1? whenever a store or software recall cycle is in progress. the block protection and wpen bits indicate the extent of protection employed. this instruction is issued after the falling edge of cs using the opcode for rdsr. write status register (wrsr) instruction the wrsr instruction enables the user to write to the status register. however, this instruction cannot be used to modify bit 0 and bit 1 (rdy and wen). the bp0 and bp1 bits can be used to select one of four levels of block protection. further, wpen bit must be set to ?1? to enable the use of write protect (wp ) pin. wrsr instruction is a write instruction and needs writes to be enabled (wen bit set to ?1?) using the wren instruction before it is issued. the instruction is issued after the falling edge of cs using the opcode for wrsr followed by eight bits of data to be stored in the status register. si nce only bits 2, 3, and 7 can be modified by wrsr instruction, it is recommended to leave the bits 4-6 as ?0? while writing to the status register. note in cy14b256p, the values writ ten to status register are saved to nonvolatile memory only after a store operation. if autostore is disabled, any modifications to the status register must be secured by performing a software store operation. table 3. status register format bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 wpen (0) x (0) x (0) x (0) bp1 (0) bp0 (0) wen (0) rdy table 4. status register bit definition bit definition description bit 0 (rdy ) ready read only bit indicates the ready status of device to perform a memory access. this bit is set to ?1? by the device while a store or software recall cycle is in progress. bit 1 (wen) write enable wen indicates if the device is wr ite enabled. this bit defaults to ?0? (disabled) on power-up. wen = '1' --> write enabled wen = '0' --> write disabled bit 2 (bp0) block protect bit ?0? used for block protection. for details see table 5 on page 10 . bit 3 (bp1) block protect bit ?1? used for block protection. for details see table 5 on page 10 . bit 4-6 don?t care bits are writable and volati le. on power-up, bits are written with ?0?. bit 7 (wpen) write protect enable bit used for enabling the function of write protect pin (wp ). for details see table 6 on page 11 . figure 6. read status regi ster (rdsr) instruction timing cs sck so 01234567 si 0000 01 0 0 1 msb lsb hi-z 012345 67 data lsb d0d1 d2 d3 d4 d5d6 msb d7 for evaluation samples only. production will be supported with the next revision silicon in soic package.
cy14b256p document number: 001-53881 rev. *f page 10 of 36 write protection and block protection cy14b256p provides features for both software and hardware write protection using wrdi instruction and wp . additionally, this device also provides block protection mechanism through bp0 and bp1 pins of the status register. the write enable and disable stat us of the device is indicated by wen bit of the status register . the write instructions (wrsr, write, and wrtc) and nvsram special instruction (store, recall, asenb, asdisb) need the write to be enabled (wen bit = 1) before they can be issued. write enable (wren) instruction on power-up, the device is always in the write disable state. the following write, wrsr, wrtc, or nvsram special instruction must therefore be preceded by a write enable instruction. if the device is not write enabled (wen = ?0?), it ignores the write instructions and returns to the standby state when cs is brought high. a new cs falling edge is required to re-initiate serial communication. the instruction is issued following the falling edge of cs . when this instruction is used, the wen bit of status register is set to ?1?. wen bi t defaults to ?0? on power-up. note after completion of a write instruction (wrsr, write, or wrtc) or nvsram special instruction (store, recall, asenb, asdisb) instruction, wen bi t is cleared to ?0?. this is done to provide protection from any inadvertent writes. therefore, wren instruction must be used before a new write instruction is issued. write disable (wrdi) instruction write disable instruction disables the write by clearing the wen bit to ?0? to protect the device against inadvertent writes. this instruction is issued following the falling edge of cs followed by opcode for wrdi instruction. the wen bit is cleared on the rising edge of cs following a wrdi instruction. block protection block protection is provided usi ng the bp0 and bp1 pins of the status register. these bits can be set using wrsr instruction and probed using the rdsr instru ction. the nvsram is divided into four array segments. one-quarter, one-half, or all of the memory segments can be protected. any data within the protected segment is read only. ta b l e 5 shows the function of block protect bits. figure 7. write status regi ster (wrsr) instruction timing cs sck so 0123 4567 si 0000000 1 msb lsb d2 d3 d7 hi-z 012345 67 opcode data in xxx x x figure 8. wren instruction 0 0 0 0 0 1 1 0 cs sck si so hi-z 0 1 2 3 4 5 6 7 figure 9. wrdi instruction table 5. block write protect bits level status register bits array addresses protected bp1 bp0 0 0 0 none 1 (1/4) 0 1 0x6000-0x7fff 2 (1/2) 1 0 0x4000-0x7fff 3 (all) 1 1 0x0000-0x7fff 0 0 0 0 0 1 0 0 cs sck si so hi-z 0 1 2 3 4 5 6 7 for evaluation samples only. production will be supported with the next revision silicon in soic package.
cy14b256p document number: 001-53881 rev. *f page 11 of 36 hardware write protection (wp pin) the write protect pin (wp ) is used to provide hardware write protection. wp pin allows all normal read and write operations when held high. when the wp pin is brought low and wpen bit is ?1?, all write operations to the status register are inhibited. the hardware write protection f unction is blocked when the wpen bit is ?0?. this allows the user to install the cy14b256p in a system with the wp pin tied to ground, and still write to the status register. wp pin can be used along with wpen and block protect bits (bp1 and bp0) of the status register to inhibit writes to memory. when wp pin is low and wpen is set to ?1?, any modifications to the status register are dis abled. therefore, the memory is protected by setting the bp0 and bp1 bits and the wp pin inhibits any modification of the status register bits, providing hardware write protection. note wp going low when cs is still low has no effect on any of the ongoing write operations to the status register. ta b l e 6 summarizes all the protection features provided in the cy14b256p. memory access all memory accesses are done using the read and write instructions. these instructions cannot be used while a store or recall cycle is in progress. a store cycle in progress is indicated by the rdy bit of the status register and the hsb pin. read sequence (read) instruction the read operations on cy14b256p are performed by giving the instruction on the si pin and re ading the output on so pin. the following sequence needs to be followed for a read operation: after the cs line is pulled low to select a device, the read opcode is transmitted through the si line followed by two bytes of address. the msb bit (a15) of the address is a ?don?t care?. after the last address bit is transmitted on the si pin, the data (d7-d0) at the specific address is shifted out on the so line on the falling edge of sck starting with d7. any other data on si line after the last address bit is ignored. cy14b256p allows reads to be performed in bursts through spi which can be used to read consecutive addresses without issuing a new read instruction. if only one byte is to be read, the cs line must be driven high after one byte of data comes out. however, the read sequence may be continued by holding the cs line low and the address is automatically incremented and data continues to shift out on so pin. when the last data memory address (0x7fff) is reached, the address rolls over to 0x0000 and the device continues to read. write sequence (write) instruction the write operations on cy14b256p are performed through the si pin. to perform a write oper ation cy14b256p, if the device is write disabled, then the device must first be write enabled through the wren instruction. when the writes are enabled (wen = ?1?), write instruction is issued after the falling edge of cs . a write instruction constitutes transmitting the write opcode on si line followed by 2 bytes of address and the data (d7-d0) which is to be written. the msb bit (a15) of the address is a ?don?t care?. cy14b256p allows writes to be performed in bursts through spi which can be used to write consecutive addresses without issuing a new write instruction. if only one byte is to be written, the cs line must be driven high after the d0 (lsb of data) is transmitted. however, if more bytes are to be written, cs line must be held low and address is incremented automatically. the following bytes on the si line are treated as data bytes and written in the successive addre sses. when the last data memory address (0x7fff) is reached, the address rolls over to 0x0000 and the device continues to write. the wen bit is reset to ?0? on completion of a write sequence. note when a burst write reaches a protected block address, it continues the address increment into the protected space but does not write any data to the protected memory. if the address roll over takes the burst write to unprotected space, it resumes writes. the same operation is true if a burst write is initiated within a write protected block. table 6. write protection operation wpen wp wen protected blocks unprotected blocks status register x x 0 protected protected protected 0 x 1 protected writable writable 1 low 1 protected writable protected 1 high 1 protected writable writable figure 10. read instruction timing ~ ~ cs sck so 012345 67 0 765432 1 12131415012345 67 msb lsb data si ~ ~ op-code 0000001 x141312 11 9 1 10 8 3 1 2 0 15-bit address msb lsb d0 d1 d2 d3 d4d5d6d7 hi-z for evaluation samples only. production will be supported with the next revision silicon in soic package.
cy14b256p document number: 001-53881 rev. *f page 12 of 36 figure 11. burst mode read instruction timing figure 12. write instruction timing figure 13. burst mode write instruction timing cs sck so lsb si op-code 15-bit address msb lsb ~ ~ ~ ~ ~ ~ 01 2 3 456 7 0 765432 1 12 13 14 15 01234567 01234567 ~ ~ 0 7 0000 00 1 1 x 1413121110 9 8 321 0 d0 d1 d2d3 d4d5d6d7 data byte 1 data byte n msb lsb msb d0 d1 d2d3 d4d5d6d7 d0d7 hi-z ~ ~ cs sck so 01234 5 6 7 0 765432 1 1213141501234567 msb lsb data d0d1 d2 d3 d4 d5d6d7 si ~ ~ op-code 00 00001 x141312 11 9 0 10 83 12 0 15-bit address msb lsb hi-z ~ ~ cs sck so msb lsb si op-code 15-bit address msb lsb ~ ~ ~ ~ 01 234567 0 76 5 432 1 12 13 14 15 01 234567 01 234567 ~ ~ 0 7 0 00000 1 0 x 1413121110 9 8 3210 hi-z data byte 1 data byte n d0 d1 d2d3 d4 d5 d6 d7 d0 d1 d2d3 d4 d5 d6 d7 d0d7 for evaluation samples only. production will be supported with the next revision silicon in soic package.
cy14b256p document number: 001-53881 rev. *f page 13 of 36 rtc access cy14b256p uses 16 registers for rtc. these registers can be read out or written to by accessi ng all 16 registers in burst mode or accessing each register, one at a time. the rdrtc and wrtc instructions are used to access the rtc. all the rtc registers can be read in burst mode by issuing the rdrtc instruction and reading all 16 bytes without bringing the cs pin high. the ?r? bit must be set while reading the rtc timekeeping registers to ensure that transitional values of time are not read. writes to the rtc register are performed using the wrtc instruction. writing rtc timekeeping registers and control registers, except for the flags r egister needs the ?w? bit of the flags register to be set to ?1?. the internal counters are updated with the new date and time setting when the ?w? bit is cleared to ?0?. all the rtc registers can also be written in burst mode using the wrtc instruction. read rtc (rdrtc) instruction read rtc (rdrtc) instruction allows the user to read the contents of rtc registers. reading the rtc registers through the so pin requires the following sequence: after the cs line is pulled low to select a device, the rdrtc opcode is transmitted through the si line followed by eight address bits for selecting the register. any data on the si line after the address bits is ignored. the data (d7-d0) at the specified address is then shifted out onto the so line. rdrtc also allows burst mode read operation. when reading multiple bytes from rtc registers, the address rolls over to 0x00 after the last rtc register address (0x0f) is reached. the ?r? bit in rtc flags register must be set to '1' before reading rtc time keeping registers to avoid reading transitional data. modifying the rtc flags register requires a write rtc cycle. the r bit must be cleared to '0' after completion of the read operation. the easiest way to read rtc registers is to perform rdrtc in burst mode. the read may start from the first rtc register (0x00) and the cs must be held low to allow the data from all 16 rtc registers to be transmitted through the so pin. note read rtc (rdrtc) instruct ion operates at a maximum clock frequency of 25 mhz. the opcode cycles, address cycles and data out cycles need to run at 25 mhz for the instruction to work properly. write rtc (wrtc) instruction write rtc (wrtc) instruction allows the user to modify the contents of rtc registers. the wrtc instruction requires the wen bit to be set to '1' before it can be issued. if wen bit is '0', a wren instruction needs to be issued before using wrtc. writing rtc registers requires t he following sequence: after the cs line is pulled low to select a device, wrtc opcode is transmitted through the si line followed by eight address bits identifying the register which is to be written to and one or more bytes of data. wrtc allows bur st mode write operation. when writing more than one registers in burst mode, the address rolls over to 0x00 after the last rtc address (0x0f) is reached. note that writing to rtc ti mekeeping and control registers require the w bit to be set to '1'. the values in these rtc registers take effect only after the ?w? bit is cleared to '0'. write enable bit (wen) is automatically cleared to ?0? after completion of the wrtc instruction. figure 14. read rtc ( rdrtc) instruction timing cs sck so 012345 67 0 3 2 1 45 67012345 67 msb lsb data si op-code 000 1 001 0000 1 a3 a1a2 a0 msb lsb d0 d1 d2d3 d4 d5 d6 d7 figure 15. write rtc (wrtc) instruction timing cs sck so 012345 67 0 3 2 1 45 67012345 67 si op-code 000 1 00 1 00 00 0 a3 a1a2 a0 4-bit address msb lsb msb lsb data hi-z d0 d1 d2 d3 d4 d5 d6 d7 for evaluation samples only. production will be supported with the next revision silicon in soic package.
cy14b256p document number: 001-53881 rev. *f page 14 of 36 nvsram special instructions cy14b256p provides four special instructions that allow access to the nvsram specific functions: store, recall, asdisb, and asenb. table 7 lists these instructions. software store (store) instruction when a store instruction is ex ecuted, cy14b256p performs a software store operation. the store operation is performed irrespective of whether a write has taken place since the last store or recall operation. to issue this instruction, the device must be write enabled (wen bit = ?1?).the instruction is performed by transmitting the store opcode on the si pin following the falling edge of cs . the wen bit is cleared on the positive edge of cs following the store instruction. software recall (recall) instruction when a recall instruction is executed, cy14b256p performs a software recall operation. to issue this instruction, the device must be write enabled (wen = ?1?). the instruction is performed by transmitting the recall opcode on the si pin following the falling edge of cs . the wen bit is cleared on the positive edge of cs following the recall instruction. autostore enable (asenb) instruction the autostore enable instruction enables the autostore on cy14b256p. this setting is not nonvolatile and needs to be followed by a store sequence if this is desired to survive the power cycle. to issue this instruction, the device must be write enabled (wen = ?1?). the instruction is pe rformed by transmitting the asenb opcode on the si pin following the falling edge of cs . the wen bit is cleared on the positive edge of cs following the asenb instruction. table 7. nvsram special instructions function name opcode operation store 0011 1100 software store recall 0110 0000 software recall asenb 0101 1001 au tostore enable asdisb 0001 1001 autostore disable figure 16. software store operation 0 0 1 1 1 1 0 0 cs sck si so hi-z 0 1 2 3 4 5 6 7 figure 17. software recall operation figure 18. autostore enable operation 0 1 1 0 0 0 0 0 cs sck si 0 1 2 3 4 5 6 7 so hi-z 0 1 0 1 1 0 0 1 cs sck si so hi-z 0 1 2 3 4 5 6 7 for evaluation samples only. production will be supported with the next revision silicon in soic package.
cy14b256p document number: 001-53881 rev. *f page 15 of 36 autostore disable (asdisb) instruction autostore is enabled by default in cy14b256p. the autostore disable instruction disables the autostore on cy14b256p. this setting is not nonvolatile and needs to be followed by a store sequence if this is desired to survive the power cycle. to issue this instruction, the device must be write enabled (wen = ?1?). the instruction is performed by transmitting the asdisb opcode on the si pin following the falling edge of cs . the wen bit is cleared on the positive edge of cs following the asdisb instruction. . hold pin operation the hold pin is used to pause the serial communication. when the device is selected and a serial sequence is underway, hold is used to pause the serial co mmunication with t he master device without resetting the ongoing se rial sequence. to pause, the hold pin must be brought low when the sck pin is low. cs pin must remain low along with hold pin to pause serial communication. while the device serial communication is paused, inputs to the si pin are ig nored and the so pin is in the high impedance state. to resume serial communication, the hold pin must be brought high when the sck pin is low (sck may toggle during hold ). figure 19. autostore disable operation 0 0 0 1 1 0 0 1 cs sck si so hi-z 0 1 2 3 4 5 6 7 figure 20. hold operation ~ ~ cs sck hold so for evaluation samples only. production will be supported with the next revision silicon in soic package.
cy14b256p document number: 001-53881 rev. *f page 16 of 36 real time clock operation nvtime operation the cy14b256p offers internal registers that contain clock, alarm, watchdog, interrupt, and control functions. the rtc registers occupy a separate address space from nvsram and are accessible through read rtc (rdrtc) and write rtc (wrtc) instructions on register addresses 0x00 to 0x0f. internal double buffering of the clock and the timer information registers prevents accessing transitional internal clock data during a read or write operation. double buffering also circumvents disrupting normal timing counts or the clock accuracy of the internal clock when accessing clock data. clock and alarm registers store data in bcd format. clock operations the clock registers maintain time up to 9,999 years in one-second increments. the time can be set to any calendar time and the clock automatically keeps track of days of the week and month, leap years, and cent ury transitions. there are eight registers dedicated to the clock functions, which are used to set time with a write cycle and to read time during a read cycle. these registers contain the time of day in bcd format. bits defined as ?0? are currently not used and are reserved for future use by cypress. reading the clock the double buffered rtc register structure reduces the chance of reading incorrect data from the clock. the user must stop internal updates to the cy14b256p time keeping registers before reading clock data, to prev ent reading of data in transition. stopping the register updates does not affect clock accuracy. the updating process is stopped by writing a ?1? to the read bit ?r? (in the flags register at 0x00), and does not restart until a ?0? is written to the read bit. the rt c registers are read while the internal clock continues to run. af ter a ?0? is written to the read bit (?r?), all rtc registers are simultaneously updated within 20 ms. setting the clock setting the write bit ?w? (in the flag s register at 0x00) to a ?1? stops updates to the time keeping regi sters and enables the time to be set. the correct day, date, and time is then written into the registers and must be in 24-hour bcd format. the time written is referred to as the ?base ti me?. this value is stored in nonvolatile registers and used in the calculation of the current time. resetting the write bit to ?0? transfers the values of timekeeping registers to the actual clock counters, after which the clock resumes normal operation. if the time written to the timekeeping registers is not in the correct bcd format, each invalid nibble of the rtc registers continue counting to 0xf before rolling over to 0x0 after which rtc resumes normal operation. note after the ?w? bit is set to ?0?, values written into the timekeeping, alarm, calibration, and interrupt registers are transferred to the rtc time keeping counters in t rtcp time. these counter values must be saved to nonvolatile memory either by initiating a software/hardware store or autostore operation. while working in autostore disabled mode, perform a store operation after t rtcp time while writing into the rtc registers for the modifications to be correctly recorded. backup power the rtc in the cy14b256p is intended for permanently powered operation. the v rtccap or v rtcbat pin is connected depending on whether a capacitor or battery is chosen for the application. when the primary power, v cc , fails and drops below v switch the device switches to the backup power supply. the clock oscillator uses very little current, which maximizes the backup time available from the backup source. regardless of the clock operation with the primary source removed, the data stored in the nvsram is secure, having been stored in the nonvolatile elements when power was lost. during backup operation, the cy14b256p consumes 0.35 a (typical) at room temperature. the user must choose capacitor or battery values accord ing to the application. backup time values based on maximum current specifications are shown in the following table. nominal backup times are approximately two times longer. using a capacitor has the obvious advantage of recharging the backup source each time the syst em is powered up. if a battery is used, a 3-v lithium is recommended and the cy14b256p sources current only from the battery when the primary power is removed. however, the battery is not recharged at any time by the cy14b256p. the battery capacity must be chosen for the total anticipated cumulative down time required over the life of the system. stopping and starting the oscillator the oscen bit in the calibration register at 0x08 controls the enable and disable of the oscillator. this bit is nonvolatile and is shipped to customers in the ?e nabled? (set to ?0?) state. to preserve the battery life when t he system is in storage, oscen must be set to ?1?. this turns of f the oscillator circuit, extending the battery life. if the oscen bit goes from disabled to enabled, it takes approximately one second (two seconds maximum) for the oscillator to start. while system power is off, if the voltage on the backup supply (v rtccap or v rtcbat ) falls below their resp ective minimum level, the oscillator may fail. the cy14b256p has the ability to detect oscillator failure when system powe r is restored. this is recorded in the oscillator fail flag (oscf) of the flags register at the address 0x00. when the device is powered on (v cc goes above v switch ) the oscen bit is checked for ?enabled? status. if the oscen bit is enabled and the oscillator is not active within the first 5 ms, the oscf bit is set to ?1?. the system must check for this condition and then write ?0? to clear the flag. note that in addition to setting the oscf flag bit, the time registers are reset to the ?base time? (see setting the clock on page 16 ), which is the value last written to the timekeeping registers. the control or calibration registers and the oscen bit are not affected by the ?oscillator failed? condition. table 8. rtc backup time capacitor value backup time 0.1 f 72 hours 0.47 f 14 days 1.0 f 30 days for evaluation samples only. production will be supported with the next revision silicon in soic package.
cy14b256p document number: 001-53881 rev. *f page 17 of 36 the value of oscf must be reset to ?0? when the time registers are written for the first time. this initializes the state of this bit, which may have become set when the system was first powered on. to reset oscf, set the write bit ?w? (in the flags register at 0x00) to a ?1? to enable writes to the flags register. write a ?0? to the oscf bit and then reset the write bit to ?0? to disable writes. calibrating the clock the rtc is driven by a quartz controlled crystal with a nominal frequency of 32.768 khz. clock accuracy depends on the quality of the crystal and calibration. the crystals available in the market typically have an error of + 20 ppm to + 35 ppm. however, cy14b256p employs a calibration circuit that improves the accuracy to +1/?2 ppm at 25 c. this implies an error of +2.5 seconds to ?5 seconds per month. the calibration circuit adds or subt racts counts from the oscillator divider circuit to achieve this accuracy. the number of pulses that are suppressed (subtracted, negative calibration) or split (added, positive calibration) depends upon the value loaded into the five calibration bits found in cali bration register at 0x08. the calibration bits occupy the five lo wer order bits in the calibration register. these bits are set to represent any value between ?0? and 31 in binary form. bit d5 is a sign bit, where a ?1? indicates positive calibration and a ?0? indicates negative calibration. adding counts speeds the clock up and subtracting counts slows the clock down. if a binary ?1? is loaded into the register, it corresponds to an adjustment of 4.068 or ?2.034 ppm offset in oscillator error, depending on the sign. calibration occurs within a 64-minute cycl e. the first 62 minutes in the cycle may, once every minute, have one second shortened by 128 or lengthened by 256 oscillator cycles. if a binary ?1? is loaded into the register, only the first two minutes of the 64-minute cycle are modified. if a binary 6 is loaded, the first 12 are affected, and so on. therefore, each calibration step has the effect of adding 512 or subtracting 256 oscillator cycles for every 125,829,120 actual oscillator cycles , that is, 4.068 or ?2.034 ppm of adjustment per calibration step in the calibration register. to determine the required calibration, the cal bit in the flags register (0x00) must be set to ?1?. this causes the int pin to toggle at a nominal frequency of 512 hz. any deviation measured from the 512 hz indicates the degree and direction of the required correction. for example, a reading of 512.01024 hz indicates a +20 ppm error. hence, a decimal value of ?10 (001010b) must be loaded into the calibration register to offset this error. note setting or changing the calibration register does not affect the test output frequency. to set or clear cal, set the write bit ?w? (in the flags register at 0x00) to ?1? to enable writes to the flags register. write a value to cal, and then reset the write bit to ?0? to disable writes. alarm the alarm function compares user programmed values of alarm time and date (stored in the registers 0x01-5) with the corresponding time of day and date values. when a match occurs, the alarm internal flag (af) is set and an interrupt is generated on int pin if alarm interrupt enable (aie) bit is set. there are four alarm match fields: date, hours, minutes, and seconds. each of these fields has a match bit that is used to determine if the field is used in the alarm match logic. setting the match bit to ?0? indicates that the corresponding field is used in the match process. depending on the match bits, the alarm occurs as specifically as once a month or as frequently as once every minute. selecting none of the match bits (all 1s) indicates that no match is required and therefore, alarm is disabled. selecting all match bits (all 0s) causes an exact time and date match. there are two ways to detect an alarm event: by reading the af flag or monitoring the int pin. the af flag in the flags register at 0x00 indicates that a date or time match has occurred. the af bit is set to ?1? when a match occurs. reading the flags register clears the alarm flag bit (and all others). a hardware interrupt pin may also be used to detect an alarm event. to set, clear or enable an alarm, set the ?w? bit (in the flags register ? 0x00) to ?1? to enable writes to alarm registers. after writing the alarm value, clear the ?w? bit back to ?0? for the changes to take effect. note cy14b256p requires the alarm match bit for seconds (0x02 - d7) to be set to ?0? for proper operation of alarm flag and interrupt. watchdog timer the watchdog timer is a free running down counter that uses the 32-hz clock (31.25 ms) derived from the crystal oscillator. the oscillator must be running for the watchdog to function. it begins counting down from the value loaded in the watchdog timer register. the timer consists of a loadable register and a free running counter. on power-up, the watchdog time out value in register 0x07 is loaded into the counter load register. counting begins on power-up and restarts from the loadable value any time the watchdog strobe (wds) bit is set to ?1?. the counter is compared to the terminal value of ?0?. if the counter reaches this value, it causes an internal flag and an optional interrupt output. you can prevent the time out interrupt by setting wds bit to ?1? prior to the counter reaching ?0?. this caus es the counter to reload with the watchdog time out value and to be restarted. as long as the user sets the wds bit prior to the counter reaching the terminal value, the interrupt and wdt flag never occur. new time out values are written by setting the watchdog write bit to ?0?. when the wdw is ?0?, new writes to the watchdog time out value bits d5-d0 are enabled to modify the time out value. when wdw is ?1?, writes to bits d5-d0 are ignored. the wdw function enables a user to set the wds bit without concern that the watchdog timer value is modified. a logical diagram of the watchdog timer is shown in figure 21 on page 18 . note that setting the watchdog time out value to ?0? disables the watchdog function. the output of the watchdog timer is the flag bit wdf that is set if the watchdog is allowed to time out. if the watchdog interrupt enable (wie) bit in the interrupt register is set, a hardware interrupt on int pin is also gen erated on watchdog timeout. the flag and the hardware interrupt are both cleared when the user reads the flags register. for evaluation samples only. production will be supported with the next revision silicon in soic package.
cy14b256p document number: 001-53881 rev. *f page 18 of 36 . power monitor the cy14b256p provides a power management scheme with the power fail interrupt capability. it also controls the internal switch to backup power for the clock and protects the memory from low v cc access. the power monitor is based on an internal band gap reference circuit that compares the v cc voltage to v switch threshold. as described in the section autostore operation on page 4 , when v switch is reached as v cc decays from power loss, a data store operation is initiated from sram to the nonvolatile elements, securing the last sram data state. power is also switched from v cc to the backup supply (battery or capacitor) to operate the rtc oscillator. when operating from the backup source, read and write operations to nvsram are inhibited and the rtc functions are not available to the user. the rtc clock continues to operate in the background. the updated rtc time keeping registers data are available to the user after v cc is restored to the device (see autostore or power-up recall on page 29 ). interrupts the cy14b256p has a flags register, interrupt register, and interrupt logic that can signal interrupt to the microcontroller. there are three potential sources for interrupt: watchdog timer, power monitor, and alarm timer. each of these can be individually enabled to drive the int pin by appropriate setting in the interrupt register (0x06). in addition, each has an associated flag bit in the flags register (0x00) that the host processor uses to determine the cause of the interrupt. the in t pin driver has two bits that specify its behavior when an interrupt occurs. an interrupt is raised only if both a flag is raised by one of the three sources and the respective interrupt enable bit in interrupts register is enabled (set to ?1?). af ter an interrupt source is active, two programmable bits, h/l and p/l, determine the behavior of the output pin driver on int pin. these two bits are located in the interrupt register and can be us ed to drive level or pulse mode output from the int pin. in pulse mode, the pulse width is internally fixed at approximatel y 200 ms. this mode is intended to reset a host microcontroller. in the level mode, the pin goes to its active polarity until the flags register is read by the user. this mode is used as an interrupt to a host microcontroller. the control bits are summarized in the following section. interrupts are only generated while working on normal power and are not triggered when system is running in backup power mode. note cy14b256p generates valid interrupts only after the power-up recall sequence is comple ted. all events on int pin must be ignored for t fa duration after powerup. interrupt register watchdog interrupt enable (wie) : when set to ?1?, the watchdog timer drives the int pin and an internal flag when a watchdog time out occurs. when wie is set to ?0?, the watchdog timer only affects the wdf flag in flags register. alarm interrupt enable (aie) : when set to ?1?, the alarm match drives the int pin and an internal flag. when aie is set to ?0?, the alarm match only affects the af flag in flags register. power fail interr upt enable (pfe) : when set to ?1?, the power fail monitor drives the pin and an internal flag. when pfe is set to ?0?, the power fail monitor only affects the pf flag in flags register. high/low (h/l) : when set to a ?1?, the int pin is active high and the driver mode is push pull. the int pin drives high only when v cc is greater than v switch . when set to a ?0?, the int pin is active low and the drive mode is open drain. the int pin must be pulled up to vcc by a 10 k resistor while using the interrupt in active low mode. pulse/level (p/l) : when set to a ?1? and an interrupt occurs, the int pin is driven for approximately 200 ms. when p/l is set to a ?0?, the int pin is driven high or low (determined by h/l) until the flags register is read. when an enabled interrupt source activates the int pin, an external host reads the flags r egisters to determine the cause. remember that all flags are cleared when the register is read. if the int pin is programmed for level mode, then the condition clears and the int pin returns to it s inactive state. if the pin is programmed for pulse mode, then reading the flag also clears the flag and the pin. the pulse does not complete its specified duration if the flags register is read. if the int pin is used as a host reset, the flags register is not read during a reset. flags register the flags register has three flag bits, wdf, af, and pf, which can be used to generate an interrupt. these flags are set by the watchdog timeout, alarm match, or power fail monitor respectively. the processor can either poll this register or enable interrupts to be informed when a flag is set. these flags are automatically reset after the regist er is read. the flags register is automatically loaded with the value 0x00 on power-up (except for the oscf bit. see stopping and starting the oscillator on page 16 ) figure 21. watchdog timer block diagram 1 hz oscillator clock divider counter zero compare wdf wds load register wdw d q q watchdog register write to watchdog register 32 hz 32,768 khz for evaluation samples only. production will be supported with the next revision silicon in soic package.
cy14b256p document number: 001-53881 rev. *f page 19 of 36 accessing the real time clock through spi cy14b256p uses 16 registers for rtc. these registers can be read out or written to by accessi ng all 16 registers in burst mode or accessing each register, one at a time. the rdrtc and wrtc instructions are used to access the rtc. all the rtc registers can be read in burst mode by issuing the rdrtc instruction and reading all 16 bytes without bringing the cs pin high. the ?r? bit must be set while reading the rtc timekeeping registers to ensure that transitional values of time are not read. writes to the rtc register are performed using the wrtc instruction. writing rtc time keeping registers and control registers, except for the flags r egister needs the ?w? bit of the flags register to be set to ?1?. the internal counters are updated with the new date and time setting when the ?w? bit is cleared to ?0?. all the rtc registers can al so be written in burst mode using the wrtc instruction. figure 22. rtc recommended component configuration figure 23. interrupt block diagram recommended values y1 = 32.768 khz (12.5 pf) c 1 = 10 pf c 2 = 67 pf x out x in y1 c2 c1 note: the recommended values for c1 and c2 include board trace capacitance. watchdog timer power monitor clock alarm vint wdf wie pf pfe af aie p/l pin driver h/l int v cc v ss wdf - watchdog timer flag wie - watchdog interrupt pf - power fail flag pfe - power fail enable af - alarm flag aie - alarm interrupt enable p/l - pulse level h/l - high/low enable for evaluation samples only. production will be supported with the next revision silicon in soic package.
cy14b256p document number: 001-53881 rev. *f page 20 of 36 table 9. rtc register map [2, 3] register bcd format data function/range d7 d6 d5 d4 d3 d2 d1 d0 0x0f 10s years years years: 00?99 0x0e 0 0 0 10s months months months: 01?12 0x0d 0 0 10s day of month day of month day of month: 01?31 0x0c 0 0 0 0 0 day of week day of week: 01?07 0x0b 0 0 10s hours hours hours: 00?23 0x0a 0 10s minutes minutes minutes: 00?59 0x09 0 10s seconds seconds seconds: 00?59 0x08 oscen (0) 0 cal sign (0) calibration (00000) calibration values [4] 0x07 wds (0) wdw (0) wdt (000000) watchdog [4] 0x06 wie (0) aie (0) pfe (0) 0 h/l (1) p/l (0) 0 0 interrupts [4] 0x05 m (1) 0 10s alarm date alarm, day alarm, day of month: 01?31 0x04 m (1) 0 10s alarm hours alarm, hours alarm, hours: 00?23 0x03 m (1) 10s alarm minutes alarm, minutes alarm, minutes: 00?59 0x02 m (1) 10s alarm seconds alarm, seconds alarm, seconds: 00?59 0x01 10s centuries centuries centuries: 00?99 0x00 wdf af pf oscf [5] 0 cal (0) w (0) r (0) flags [4] notes 2. ( ) designates values shipped from the factory. 3. the unused bits of rtc registers are reserved for future use and should be set to ?0?. 4. this is a binary value, not a bcd value. 5. when user resets oscf flag bit, the flags register will be updated after t rtcp time. for evaluation samples only. production will be supported with the next revision silicon in soic package.
cy14b256p document number: 001-53881 rev. *f page 21 of 36 table 10. register map detail register description 0x0f time keeping - years d7 d6 d5 d4 d3 d2 d1 d0 10s years years contains the lower two bcd digits of t he year. lower nibble (four bits) contains the value for years; upper nibble (four bits) contains the value for 10s of years. each nibble operates from 0 to 9. the range for the register is 0?99. 0x0e time keeping - months d7 d6 d5 d4 d3 d2 d1 d0 0 0 0 10s month months contains the bcd digits of the month. lower nibble (four bits ) contains the lower digit and operates from 0 to 9; upper nibble (one bit) contains the upper digit and operate s from 0 to 1. the range for the register is 1?12. 0x0d time keeping - date d7 d6 d5 d4 d3 d2 d1 d0 0 0 10s day of month day of month contains the bcd digits for the date of the month. lower ni bble (four bits) contains the lower digit and operates from 0 to 9; upper nibble (two bits) contains the 10s digit and operat es from 0 to 3. the range for the register is 1?31. leap years are automatically adjusted for. 0x0c time keeping - day d7 d6 d5 d4 d3 d2 d1 d0 0 0 0 0 0 day of week lower nibble (three bits) contains a value that correlates to day of the week. day of the week is a ring counter that counts from 1 to 7 then returns to 1. the user must assign meaning to the day value, beca use the day is not integrated with the date. 0x0b time keeping - hours d7 d6 d5 d4 d3 d2 d1 d0 0 0 10s hours hours contains the bcd value of hours in 24 hour format. lower ni bble (four bits) contains the lower digit and operates from 0 to 9; upper nibble (two bits) contains the upper digit and operates from 0 to 2. the r ange for the register is 0?23. 0x0a time keeping - minutes d7 d6 d5 d4 d3 d2 d1 d0 0 10s minutes minutes contains the bcd value of minutes. lower nibble (four bits) contains the lower digit and operates from 0 to 9; upper nibble (three bits) contains the upper minutes digit and oper ates from 0 to 5. the range for the register is 0?59. 0x09 time keeping - seconds d7 d6 d5 d4 d3 d2 d1 d0 0 10s seconds seconds contains the bcd value of seconds. lower nibble (four bits ) contains the lower digit and operates from 0 to 9; upper nibble (three bits) contains the upper digit and operat es from 0 to 5. the range for the register is 0?59. 0x08 calibration/control d7 d6 d5 d4 d3 d2 d1 d0 oscen 0 calibration sign calibration oscen oscillator enable. when set to ?1?, the oscillator is stop ped. when set to ?0?, the oscillator runs. disabling the oscilla tor saves battery or capacitor power during storage. calibration sign determines if the calibration adjustment is applied as an a ddition (1) to or as a subtraction (0) from the time-base. calibration these five bits control the calibration of the clock. for evaluation samples only. production will be supported with the next revision silicon in soic package.
cy14b256p document number: 001-53881 rev. *f page 22 of 36 0x07 watchdog timer d7 d6 d5 d4 d3 d2 d1 d0 wds wdw wdt wds watchdog strobe. setting this bit to ?1? reloads and restarts the watchdog timer. setting the bit to ?0? has no effect. the bit is cleared automatically after the watchdog timer is reset. the wds bit is write only. reading it always returns a ?0?. wdw watchdog write enable. setting this bit to ?1? disables any write to the watchdog timeout value (d5?d0). this enables the user to set the watchdog strobe bit without disturbing the ti meout value. setting this bit to ?0? allows bits d5?d0 to be written to the watchdog regist er when the next write cycle is complete. this function is explained in more detail in watchdog timer on page 17 . wdt watchdog timeout selection. the watchdog timer interval is se lected by the 6-bit value in this register. it represents a multiplier of the 32 hz count (31.25 ms). the range of timeout value is 31.25 ms (a setting of 1) to 2 seconds (setting of 3 fh). setting the watchdog timer register to ?0? disables the timer. these bits can be written only if the wdw bit was set to 0 on a previous cycle. 0x06 interrupt status/control d7 d6 d5 d4 d3 d2 d1 d0 wie aie pfe 0 h/l p/l 0 0 wie watchdog interrupt enable. when set to ?1? and a watchdog timeout occurs, the watchdog timer drives the int pin and the wdf flag. when set to ?0?, the watc hdog timeout affects only the wdf flag. aie alarm interrupt enable. when set to ?1?, the alarm match drives the int pin and the af flag. when set to ?0?, the alarm match only affects the af flag. pfe power fail enable. when set to ?1?, t he alarm match drives the int pin and the pf flag. when set to ?0?, the power fail monitor affects only the pf flag. 0 reserved for future use h/l high/low. when set to ?1?, the int pin is driven active high. when set to ?0?, the int pin is open drain, active low. p/l pulse/level. when set to ?1?, the int pin is driven active (determined by h/l) by an interrupt source for approximately 200 ms. when set to ?0?, the int pin is driven to an active level (as set by h/l) until the flags register is read. 0x05 alarm - day d7 d6 d5 d4 d3 d2 d1 d0 m 0 10s alarm date alarm date contains the alarm value for the date of the month and the mask bit to select or deselect the date value. m match. when this bit is set to ?0?, the date value is used in the alarm match. setting this bit to ?1? causes the match circui t to ignore the date value. 0x04 alarm - hours d7 d6 d5 d4 d3 d2 d1 d0 m 0 10s alarm hours alarm hours contains the alarm value for the hours and the ma sk bit to select or de select the hours value. m match. when this bit is set to ?0?, the hours value is used in the alarm match. setting this bit to ?1? causes the match circuit to ignore the hours value. 0x03 alarm - minutes d7 d6 d5 d4 d3 d2 d1 d0 m 10s alarm minutes alarm minutes contains the alarm value for the minutes and the ma sk bit to select or deselect the minutes value. m match. when this bit is set to ?0?, the minutes value is used in the alarm match. setting this bit to ?1? causes the match circuit to ignore the minutes value. table 10. register map detail (continued) register description for evaluation samples only. production will be supported with the next revision silicon in soic package.
cy14b256p document number: 001-53881 rev. *f page 23 of 36 0x02 alarm - seconds d7 d6 d5 d4 d3 d2 d1 d0 m 10s alarm seconds alarm seconds contains the alarm value for the seconds and the ma sk bit to select or deselect the seconds? value. m match. when this bit is set to ?0?, the seconds value is used in the alarm match. setting this bit to ?1? causes the match circuit to ignore the seconds value. 0x01 time keeping - centuries d7 d6 d5 d4 d3 d2 d1 d0 10s centuries centuries contains the bcd value of centuries. lower nibble contains the lower digit and operates from 0 to 9; upper nibble contains the upper digit and operates from 0 to 9. the range for the register is 0-99 centuries. 0x00 flags d7 d6 d5 d4 d3 d2 d1 d0 wdf af pf oscf 0 cal w r wdf watchdog timer flag. this read only bit is set to ?1? when the watchdog timer is allowed to reach 0 without being reset by the user. it is cleared to ?0? when the flags register is read or on power-up af alarm flag. this read only bit is set to ?1? when the time and date match the values stored in the alarm registers with the match bits = ?0?. it is cleared when the flags register is read or on power-up. pf power fail flag. this read only bit is set to ?1? when power falls below the power fail threshold v switch . it is cleared to 0 when the flags register is read or on power-up. oscf oscillator fail flag. set to ?1? on power-up if the oscillato r is enabled and not running in the first 5 ms of operation. t his indicates that rtc backup power failed and clock value is no longer valid. this bit survives the power cycle and is never cleared internally by the chip. the user must check for this condition and write '0' to clear this flag. when user resets oscf flag bit, the bit will be updated after t rtcp time. cal calibration mode. when set to ?1?, a 512 hz square wave is output on the int pin. when set to ?0?, the int pin resumes normal operation. this bit defaults to 0 (disabled) on power-up. w write enable: setting the ?w? bit to ?1? freezes updates of the rtc registers. the user can then write to rtc registers, alarm registers, calibration register, interrupt register and flags register. setting the ?w? bit to ?0? causes the contents of the rtc registers to be transferred to the time keeping counters if the time has changed. this transfer process takes t rtcp time to complete. this bit defaults to 0 on power-up. r read enable: setting ?r? bit to ?1?, stops clock updates to us er rtc registers so that clo ck updates are not seen during the reading process. set ?r? bit to ?0? to resume clock updates to the holding register. setting this bit does not require ?w? bit to be set to ?1?. this bit defaults to 0 on power-up. table 10. register map detail (continued) register description for evaluation samples only. production will be supported with the next revision silicon in soic package.
cy14b256p document number: 001-53881 rev. *f page 24 of 36 best practices nvsram products have been used effectively for over 27 years. while ease-of-use is one of t he product?s main system values, experience gained working with hundreds of applications has resulted in the following suggestions as best practices: the nonvolatile cells in this nvsram product are delivered from cypress with 0x00 written in all cells. incoming inspection routines at customer or c ontract manufacturer?s sites sometimes reprogram these values. final nv patterns are typically repeating patterns of aa, 55, 00, ff, a5, or 5a. end product?s firmware should not assume an nv array is in a set programmed state. routines that check memory content values to determine first time system configuration, cold or warm boot status, and so on should always program a unique nv pattern (that is, complex 4 byte pattern of 46 e6 49 53 hex or more random bytes) as part of the final system manufacturing test to ensure these system routines work consistently. power up boot firmware routines should rewrite the nvsram into the desired state (for example, autostore enabled). while the nvsram is shipped in a pres et state, best practice is to again rewrite the nvsram into the desired state as a safeguard against events that might flip the bit inadvertently such as program bugs and incoming inspection routines. the v cap value specified in this data sheet includes a minimum and a maximum value size. best practice is to meet this requirement and not exceed the maximum v cap value because the nvsram internal algorithm calculates v cap charge and discharge time based on this maximum v cap value. customers that want to use a larger v cap value to make sure there is extra store charge and store time should discuss their v cap size selection with cypress to understand any impact on the v cap voltage level at the end of a t recall period. when base time is updated, th ese updates are transferred to the time keeping registers when ?w? bit is set to ?0?. this transfer takes t rtcp time to complete. it is recommended to initiate software store or hardware store after t rtcp time to save the base time into nonvolatile memory. for evaluation samples only. production will be supported with the next revision silicon in soic package.
cy14b256p document number: 001-53881 rev. *f page 25 of 36 maximum ratings exceeding maximum ratings may s horten the useful life of the device. these user guidelines are not tested. storage temperature ..... ............ ............... ?65 c to +150 c maximum accumulated storage time at 150 c ambient temperature........ ............... 1000 h at 85 c ambient temperature..................... 20 years ambient temperature with power applied ..... ............................ .......... ?55 c to +150 c supply voltage on v cc relative to v ss ..........?0.5 v to +4.1 v dc voltage applied to outputs in high z state ...................................... ?0.5 v to v cc + 0.5 v input voltage ........................................ ?0.5 v to v cc + 0.5 v transient voltage (< 20 ns) on any pin to ground potential .................. ?2.0 v to v cc + 2.0 v package power dissipation capability (t a = 25 c) .................................................. 1.0 w surface mount lead soldering temperature (3 seconds)......... ............................ ..... +260 c dc output current (1 output at a time, 1 s duration). ... 15 ma static discharge voltage.......................................... > 2001 v (per mil-std-883, method 3015) latch up current..................................................... > 200 ma operating range range ambient temperature v cc industrial ?40 c to +85 c 2.7 v to 3.6 v dc electrical characteristics over the operating range parameter description test conditions min typ [6] max unit v cc power supply voltage 2.7 3.0 3.6 v i cc1 average v cc current at f sck = 40 mhz. values obtained without output loads (i out = 0 ma) ??10ma i cc2 average v cc current during store all inputs don?t care, v cc = max average current for duration t store ??10ma i cc4 average v cap current during autostore cycle all inputs don?t care. average current for duration t store ??5ma i sb v cc standby current cs > (v cc ? 0.2 v). v in < 0.2 v or > (v cc ? 0.2 v). w bit set to ?0?. standby current level after nonvolatile cycle is complete. inputs are static. f = 0 mhz. ??5ma i ix [7] input leakage current (except hsb ) v cc = max, v ss < v in < v cc ?1 ? +1 a input leakage current (for hsb ) v cc = max, v ss < v in < v cc ?100 ? +1 a i oz off state output leakage current v cc = max, v ss < v out < v cc ?1 ? +1 a v ih input high voltage 2.0 ? v cc + 0.5 v v il input low voltage v ss ? 0.5 ? 0.8 v v oh output high voltage i out = ?2 ma 2.4 ? v v ol output low voltage i out = 4 ma ? ? 0.4 v v cap [8] storage capacitor between v cap pin and v ss , 5 v rated 61 68 180 f notes 6. typical values are at 25 c, v cc = v cc (typ). not 100% tested. 7. the hsb pin has i out = ?2 a for v oh of 2.4 v when both active high and low drivers are disabled. when they are enabled standard v oh and v ol are valid. this parameter is characterized but not tested. 8. min v cap value guarantees that there is a sufficient charge available to complete a successful autostore operation. max v cap value guarantees that the capacitor on v cap is charged to a minimum voltage during a power-up recall cycle so that an immediate power-down cycle can co mplete a successful autostore. therefore it is always recommended to use a capacitor within the specified min and max limits. refer application note an43593 for more details on v cap options. for evaluation samples only. production will be supported with the next revision silicon in soic package.
cy14b256p document number: 001-53881 rev. *f page 26 of 36 ac test conditions input pulse levels.................................................... 0 v to 3 v input rise and fall times (10% to 90%)......................... < 3 ns input and output timing reference levels........................ 1.5 v data retention and endurance over the operating range parameter description min unit data r data retention 20 years nv c nonvolatile store operations 1,000 k capacitance parameter [9] description test conditions max unit c in input capacitance t a = 25 c, f = 1 mhz, v cc = v cc (typ) 6pf c out output pin capacitance 8 pf thermal resistance parameter [9] description test conditions 16-soic unit ja thermal resistance (junction to ambient) test conditions follow standard test methods and procedures for measuring thermal impedance, per eia / jesd51. 55.17 c/w jc thermal resistance (junction to case) 2.64 c/w figure 24. ac test loads and waveforms 3.0 v output 5 pf r1 r2 789 3.0 v output 30 pf r1 r2 789 577 577 note 9. these parameters are guaranteed by design and are not tested. for evaluation samples only. production will be supported with the next revision silicon in soic package.
cy14b256p document number: 001-53881 rev. *f page 27 of 36 rtc characteristics over the operating range parameter description min typ [10] max units v rtcbat rtc battery pin voltage 1.8 3.0 3.6 v i bak [11] rtc backup current t a (min) ? ? 0.35 a 25 c ? 0.35 ? a t a (max) ? ? 0.5 a v rtccap [12] rtc capacitor pin voltage t a (min) 1.6 ? 3.6 v 25 c 1.5 3.0 3.6 v t a (max) 1.4 ? 3.6 v tocs rtc oscillator time to start ? 1 2 sec t rtcp rtc processing time from end of ?w? bit set to ?0? ? ? 350 s r bkchg rtc backup capacitor charge current-limiting resistor 350 ? 850 ac switching characteristics over the operating range [13] cypress parameter alt. parameter description 40 mhz 25 mhz (rdrtc instruction) [14] unit min max min max f sck f sck clock frequency, sck ? 40 ? 25 mhz t cl t wl clock pulse width low 11 ? 18 ? ns t ch t wh clock pulse width high 11 ? 18 ? ns t cs t ce cs high time 20 ? 20 ? ns t css t ces cs setup time 10 ? 10 ? ns t csh t ceh cs hold time 10 ? 10 ? ns t sd t su data in setup time 5 ? 5 ? ns t hd t h data in hold time 5 ? 5 ? ns t hh t hd hold hold time 5 ? 5 ? ns t sh t cd hold setup time 5 ? 5 ? ns t co t v output valid ? 9 ? 15 ns t hhz [15] t hz hold to output high z ? 15 ? 15 ns t hlz [15] t lz hold to output low z ? 15 ? 15 ns t oh t ho output hold time 0 ? 0 ? ns t hzcs t dis output disable time ? 25 25 ns notes 10. typical values are at 25 c, v cc = v cc (typ). not 100% tested. 11. current drawn from either v rtccap or v rtcbat when v cc < v switch. 12. if v rtccap > 0.5 v or if no capacitor is connected to v rtccap pin, the oscillator starts in tocs time. if a backup capacitor is connected and v rtccap < 0.5 v, the capacitor must be allowed to charge to 0.5 v for oscillator to start. 13. test conditions assume signal transition time of 3 ns or less, timing reference levels of v cc /2, input pulse levels of 0 to v cc (typ), and output loading of the specified i ol /i oh and load capacitance shown in figure 24 . 14. applicable for rtc opcode cycles, address cycles, and dataout cycles. 15. these parameters are guaranteed by design and are not tested. for evaluation samples only. production will be supported with the next revision silicon in soic package.
cy14b256p document number: 001-53881 rev. *f page 28 of 36 figure 25. synchronous data timing (mode 0) figure 26. hold timing hi-z valid in hi-z cs sck si so t cl t ch t css t sd t hd t co t oh t cs t csh t hzcs ~ ~ cs sck hold so t sh t hhz t hlz t hh t sh t hh ~ ~ for evaluation samples only. production will be supported with the next revision silicon in soic package.
cy14b256p document number: 001-53881 rev. *f page 29 of 36 autostore or power-up recall over the operating range parameter description cy14b256p unit min max t fa [16] power-up recall duration ? 20 ms t store [17] store cycle duration ? 8 ms t delay [18] time allowed to complete sram write cycle ? 25 ns v switch low voltage trigger level ? 2.65 v t vccrise [19] v cc rise time 150 ? s v hdis [19] hsb output disable voltage ? 1.9 v t lzhsb [19] hsb high to nvsram active time ? 5 s t hhhd [19] hsb high active time ? 500 ns switching waveforms figure 27. autostor e or power-up recall [20] v switch v hdis t vccrise t store t store t hhhd t hhhd t delay t delay t lzhsb t lzhsb t fa t fa hsb out autostore power- up recall read & write inhibited (rwi) power-up recall read & write brown out autostore power-up recall read & write power down autostore note note note note v cc 17 17 21 21 notes 16. t fa starts from the time v cc rises above v switch. 17. if an sram write has not taken place since the last nonvo latile cycle, no autostore or hardware store takes place. 18. on a hardware store and autostore initiation, sram write operation continues to be enabled for time t delay . 19. these parameters are guaranteed by design and are not tested. 20. read and write cycles are ignored during store, recall, and while v cc is below v switch. 21. during power up and power down, hsb glitches when hsb pin is pulled up through an external resistor. for evaluation samples only. production will be supported with the next revision silicon in soic package.
cy14b256p document number: 001-53881 rev. *f page 30 of 36 software controlled store/recall cycles over the operating range parameter description cy14b256p unit min max t recall recall duration ? 200 s t ss [22, 23] soft sequence processing time ? 100 s figure 28. software store cycle [23] figure 29. software recall cycle [23] figure 30. autostore enable cycle figure 31. autostore disable cycle 0 0 1 1 1 1 0 0 cs sck si rwi hi-z 0 1 2 3 4 5 6 7 rdy t store 0 1 1 0 0 0 0 0 cs sck si 0 1 2 3 4 5 6 7 rwi hi-z rdy t recall 0 1 0 1 1 0 0 1 cs sck si 0 1 2 3 4 5 6 7 rwi hi-z rdy t ss 0 0 0 1 1 0 0 1 sck si 0 1 2 3 4 5 6 7 rwi hi-z rdy cs t ss notes 22. this is the amount of time it takes to take action on a soft sequence command. vcc power must re main high to effectively reg ister command. 23. commands such as store and recall lock out i/o until operati on is complete which further increases this time. see the specif ic command. for evaluation samples only. production will be supported with the next revision silicon in soic package.
cy14b256p document number: 001-53881 rev. *f page 31 of 36 hardware store cycle over the operating range parameter description cy14b256p unit min max t phsb hardware store pulse width 15 ? ns figure 32. hardware store cycle [24] ~ ~ hsb (in) hsb (out) rwi hsb (in) hsb (out) rwi t hhhd t store t phsb t delay t lzhsb t delay t phsb hsb pin is driven high to v cc only by internal 100 k: resistor, hsb driver is disabled sram is disabled as long as hsb (in) is driven low. write latch not set write latch set ~ ~ ~ ~ ~ ~ note 24. if an sram write has not taken place since the last nonvolatile cycle, no au tostore or hardware store takes place. for evaluation samples only. production will be supported with the next revision silicon in soic package.
cy14b256p document number: 001-53881 rev. *f page 32 of 36 ordering code definition ordering information ordering code package diagram package type operating range CY14B256P-SFXIT 51-85022 16-pin soic industrial cy14b256p-sfxi all the above parts are pb-free. option: t - tape and reel blank - std. p - serial (spi) nvsram with rtc density: 256 - 256 kb voltage: b - 3.0 v cypress cy 14 b 256 p - sf x i t 14 - nvsram pb-free package: sf - 16 soic temperature: i - industrial (?40 c to 85 c) for evaluation samples only. production will be supported with the next revision silicon in soic package.
cy14b256p document number: 001-53881 rev. *f page 33 of 36 package diagram figure 33. 16-pin (300 mil) soic package 51-85022 *c for evaluation samples only. production will be supported with the next revision silicon in soic package.
cy14b256p document number: 001-53881 rev. *f page 34 of 36 acronyms document conventions units of measure acronym description bcd binary coded decimal cmos complementary metal oxide semiconductor crc cyclic redundancy check cpha clock phase cpol clock polarity eeprom electrically erasable programmable read-only memory eia electronic industries alliance i/o input/output jedec joint electron devices engineering council nvsram nonvolatile static random access memory rohs restriction of hazardous substances rwi read and write inhibited soic small outline integrated circuit sonos silicon-oxide-nitride-oxide-silicon spi serial peripheral interface symbol unit of measure c degree celsius hz hertz k kilo ohm a micro amperes f micro farad s micro second ma milli amperes mhz mega hertz ns nano seconds ohm pf pico farad vv o l t s wwatts for evaluation samples only. production will be supported with the next revision silicon in soic package.
cy14b256p document number: 001-53881 rev. *f page 35 of 36 document history page document title: cy14b256p 256-kbit (32 k x 8) serial (spi) nvsram with real time clock document number: 001-53881 revision ecn orig. of change submission date description of change ** 2733272 gvch/aesa 07/16/09 new datasheet *a 2758444 gvch 09/01/09 moved data sheet status from preliminary to final removed commercial temperature related specs added thermal resistance values for 16-soic package added note to write sequence (write) description changed v rtcbat max value from 3.3 v to 3.6 v changed r bkchg min value from 450 to 350 updated footnote 8 *b 2839453 gvch/pyrs 01/06/10 changed store cycles to quantumtrap from 200 k to 1 million updated figure 2 updated i bak rtc backup current spec unit from na to a added contents *c 3008637 gvch 08/16/10 changed ground naming convention from gnd to v ss ta b l e 1 : added more clarity on hsb pin operation hardware store and hsb pin operation : added more clarity on hsb pin operation updated power-down description power on reset : added status of bits 4-6 ta b l e 4 : added definition of bits 4-6 updated figure 7 , figure 25 , figure 26 , and figure 27 updated footnote 19 added figure 30 and figure 31 removed t dhsb parameter updated figure 32 updated package diagram added acronyms and document conventions . *d 3033665 gvch 09/24/10 added watermark as ?for evaluation samples only. production will be supported with the next revision silicon in soic package.? updated hold pin operation , figure 20 and figure 26 to indicate that cs pin must remain low along with hold pin to pause serial communication. *e 3143330 gvch 01/17/11 hardware store and hsb pin operation : added more clarity on hsb pin operation updated setting the clock description updated ?w? bit description in register map detail table updated best practices added t rtcp parameter to rtc characteristics table updated t lzhsb parameter description fixed typo in figure 27 . *f 3320715 gvch 07/19/11 added footnote 8 and 13. for evaluation samples only. production will be supported with the next revision silicon in soic package.
document number: 001-53881 rev. *f revised july 19, 2011 page 36 of 36 all products and company names mentioned in this document may be the trademarks of their respective holders. cy14b256p ? cypress semiconductor corporation, 2009-2011. the information contained herein is subject to change without notice. cypress s emiconductor corporation assumes no responsibility for the use of any circuitry other than circuitry embodied in a cypress product. nor does it convey or imply any license under patent or other rights. cypress products are not warranted nor intended to be used for medical, life support, life saving, critical control or safety applications, unless pursuant to an express written agreement wi th cypress. furthermore, cypress does not authorize its products for use as critical components in life-support systems where a malfunction or failure may reasonably be expected to result in significant injury to the user. the inclusion of cypress products in life-support systems application implies that the manufacturer assumes all risk of such use and in doing so indemnifies cypress against all charges. any source code (software and/or firmware) is owned by cypress semiconductor corporation (cypress) and is protected by and subj ect to worldwide patent protection (united states and foreign), united states copyright laws and internatio nal treaty provisions. cypress hereby grants to licensee a personal, non-exclusive, non-transferable license to copy, use, modify, create derivative works of, and compile the cypress source code and derivative works for the sole purpose of creating custom software and or firmware in su pport of licensee product to be used only in conjunction with a cypress integrated circuit as specified in the applicable agreement. any reproduction, modification, translation, compilation, or repre sentation of this source code except as specified above is prohibited without the express written permission of cypress. disclaimer: cypress makes no warranty of any kind, express or implied, with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. cypress reserves the right to make changes without further notice to t he materials described herein. cypress does not assume any liability arising out of the application or use of any product or circuit described herein. cypress does not authori ze its products for use as critical components in life-support systems where a malfunction or failure may reasonably be expected to result in significant injury to the user. the inclusion of cypress? prod uct in a life-support systems application implies that the manufacturer assumes all risk of such use and in doing so indemnifies cypress against all charges. use may be limited by and subject to the applicable cypress software license agreement. sales, solutions, and legal information worldwide sales and design support cypress maintains a worldwide network of offices, solution center s, manufacturer?s representatives, and distributors. to find t he office closest to you, visit us at cypress locations . products automotive cypress.co m/go/automotive clocks & buffers cypress.com/go/clocks interface cypress. com/go/interface lighting & power control cypress.com/go/powerpsoc cypress.com/go/plc memory cypress.com/go/memory optical & image sensing cypress.com/go/image psoc cypress.com/go/psoc touch sensing cyp ress.com/go/touch usb controllers cypress.com/go/usb wireless/rf cypress.com/go/wireless psoc solutions psoc.cypress.com/solutions psoc 1 | psoc 3 | psoc 5 for evaluation samples only. production will be supported with the next revision silicon in soic package.


▲Up To Search▲   

 
Price & Availability of CY14B256P-SFXIT

All Rights Reserved © IC-ON-LINE 2003 - 2022  

[Add Bookmark] [Contact Us] [Link exchange] [Privacy policy]
Mirror Sites :  [www.datasheet.hk]   [www.maxim4u.com]  [www.ic-on-line.cn] [www.ic-on-line.com] [www.ic-on-line.net] [www.alldatasheet.com.cn] [www.gdcy.com]  [www.gdcy.net]


 . . . . .
  We use cookies to deliver the best possible web experience and assist with our advertising efforts. By continuing to use this site, you consent to the use of cookies. For more information on cookies, please take a look at our Privacy Policy. X