Cypress Perform

Home > Design Support > Cypress Developer CommunityTM > Cypress Forums > Memory > Questions about nonvolatile store on CY14B256LA

Cypress Developer CommunityTM
Forums | Videos | Blogs | Training | Rewards Program | Community Components



Questions about nonvolatile store on CY14B256LA

Summary: 6330 Views, 2 Replies, Latest reply by psr on 07 Jun 2010 02:28 AM PST

Verified Answers: 0

Post Reply


RonW posted on 02 Jun 2010 3:47 PM PST
Member
3 Forum Posts

The datasheet for the CY14B256LA mentions 20-year data retention. Other nvSRAM products list 100 years. Is that 20 years from the most recent store operation, or 20 years total over the life of the chip?

Is there any way of reading the option status from the chip?

If AutoStore is disabled, does disabling it again count as a write as far as the life of the chip goes? For example, if the device containing the chip automatically disables AutoStore every time it turns on, does each disable operation contribute to "wearing out" the chip by eating into the 1,000,000 store count?

Does disabling AutoStore set the chip's "dirty bit" thus causing a store when /HSB is asserted?

If the dirty bit is set, are ALL bytes stored when /HSB is asserted, or only those bytes whose SRAM value differs from its stored value?

Thank you.



 

psr posted on 07 Jun 2010 11:58 PM PST
Cypress Employee
10 Forum Posts

Hi,

You seem to be calling the internal "write latch" which gets set whenever a write happens, as dirty bit. Which implies that you want to write into the SRAM but you do not want the written data to be Stored when HSB/ is asserted. If this is what you desire, is there any reason you cannot leave the HSB/ open?

Also, why is the application disabling AutoStore at every power up. You can do it once and do a SW store to make it endure power cycles. Fom then on, Stores will happen only when you do a software Store (HW store if HSB is asserted when write has happened).

I have placed my answers to your questions inline marked ##.

Q: The datasheet for the CY14B256LA mentions 20-year data retention. Other nvSRAM products list 100 years. Is that 20 years from the most recent store operation, or 20 years total over the life of the chip?

## The 20 year data retention in the CY14B256LA is guaranteed at 85C. The 100 years in the old technology part (0.8u parts) is guaranteed at 55C. If comparison is made at the same temperatures, the new parts have 4 times the data retention of the older part.. We have stated this in the app note AN55662.

## The data retention is over the life of the part. 20 years is the accumulated data retention time.

Q: Is there any way of reading the option status from the chip?

If AutoStore is disabled, does disabling it again count as a write as far as the life of the chip goes? For example, if the device containing the chip automatically disables AutoStore every time it turns on, does each disable operation contribute to "wearing out" the chip by eating into the 1,000,000 store count?

## Unfortunately there is no way to check the enable/disable status of AutoStore in a part.

## AutoStore disabling does not count as a write nor does it affect the 1M store count.

- Autostore anable or disable is done through a specific sequence of reads. There is no write cycle involved.

- Read/write cycles are done to the SRAM portion of the nvSRAM. The SRAM has infinite read/write endurance.

- Only Store cycles count for endurance. Since you are disabling autostore, I assume you will be performing a software store or hardware store when you want to save the data to NV portion of the nvSRAM. Only those stores will count for endurance.

Q: Does disabling AutoStore set the chip's "dirty bit" thus causing a store when /HSB is asserted?

## No. As discussed earlier, the write latch is not set when  you perform reads. I assume you are considering the internal write latch as "dirty bit" though I do not understand why you consider it so. The internal write latch is what prevents unwanted Store when there is no writes (and thus no change in the content). I assume you do not want Store to happen when HSB/ is asserted. If so, Store will not happen if you have performed only reads. However, if you have done writes, and do not want data to be Stored, you need to ensure HSB/ is not asserted. Or, you can leave HSB/ open.

If the dirty bit is set, are ALL bytes stored when /HSB is asserted, or only those bytes whose SRAM value differs from its stored value? “

## When Store happens it will happen to ALL bytes. The Store process consists of erasing the complete NV memory and storing the complete SRAM content into the NV memory.

Ravi, nvSRAM Apps Manager


psr posted on 07 Jun 2010 02:28 AM PST
Cypress Employee
10 Forum Posts

1) The 20 year data retention in theCY14B256LA is guaranteed at 85C while the 100 years in the old technology part is at 55C. At the same temperatures, the new parts have 4 times the data retention of the older part (See app note AN55662).

2) The data retention is over the life of the part. 20 years is the accumulated data retention time

3) Unfortunately there is no way to check the enable/disable status of AutoStore in a part.

4) AutoStore disabling does not count as a write nor does it affect the 1M store count.

- Autostore anable or disable is done through a specific sequence of reads. The is no write cycle involved.

- Read/write cycles are done to the SRAM portion of the nvSRAM and SRAM has infinite read/write endurance.

- Only Store cycles count for endurance. Since you are disabling autostore, I assume you will be performing a software store or hardware store when you want to save the data to NV portion of the nvSRAM. Only those stores will count for endurance. 

5) The write latch is not set when you perform reads. The internal write latch is what prevents unwanted Store when there is no writes (and thus no change in the content). If you do not want Store to happen even with writes, either do not assert HSB/ or leave HSB/ open.

6) When Store happens it will happen to ALL bytes. The Store process consists of erasing the complete NV memory and storing the complete SRAM content into the NV memory.



 

Post Reply






ALL CONTENT AND MATERIALS ON THIS SITE ARE PROVIDED "AS IS". CYPRESS SEMICONDUCTOR AND ITS RESPECTIVE SUPPLIERS MAKE NO REPRESENTATIONS ABOUT THE SUITABILITY OF THESE MATERIALS FOR ANY PURPOSE AND DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THESE MATERIALS, INCLUDING BUT NOT LIMITED TO, ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT OF ANY THIRD PARTY INTELLECTUAL PROPERTY RIGHT. NO LICENSE, EITHER EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, IS GRANTED BY CYPRESS SEMICONDUCTOR. USE OF THE INFORMATION ON THIS SITE MAY REQUIRE A LICENSE FROM A THIRD PARTY, OR A LICENSE FROM CYPRESS SEMICONDUCTOR.

Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Terms and Conditions of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Terms and Conditions of this site. Cypress Semiconductor and its suppliers reserve the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.

Spec No: None; Sunset Owner: KXP; Secondary Owner: VWA; Sunset Date: 06/15/20