Cypress Perform

Home > Design Support > Cypress Developer CommunityTM > Cypress Forums > Memory > unable to write last 2 blocks of CY14B108K

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



unable to write last 2 blocks of CY14B108K
Moderator:
PRIT

Post Reply
Follow this topic



unable to write last 2 blocks of CY14B108K

engrprabhu posted on 21 Nov 2011 9:55 PM PST

1 Forum Post

unable to write in the alternative locations after 0xFFFEO in CY14B108K nvRAM.. attached the screen shot..

please help me how to resolve this...

Thanks.




Re: unable to write last 2 blocks of CY14B108K

zsk posted on 23 Nov 2011 02:37 AM PST
Cypress Employee
19 Forum Posts

Hi Prabhu,

CY14B108K is an 8 Mbit, x8 nvSRAM with RTC. Last 16 address locations (0xFFFF0 to 0xFFFFF) have been allocated for storing the RTC data.These last 16 address loactions are not writable until write "w" bit is set to "1" in the flag register @ location 0xFFFF0 before writing any data bytes in the RTC registers.  Most of the RTC registers store data in BCD (Binary Coded Digit) format, therefore a few bits in some RTC registers are always set to a "0" and can't be programmed with the user data. 

Actual data memory (SRAM for storing user data) in CY14B108K device is 0x00000 to 0xFFFF0. To check whether RTC update are correct or not,  you can write the following data byte and read back. If you don't clear the "w" bit to "0", you can read back the same data you have written otherwise if you have cleared the "w" bit to "0" then you will find Second register (0xFFFF9) updating, if the crystal is connected across X1 and X2 and it is oscillating.

                                                       0xFFFF0 - 0x02 -Set the "w" bit

0xFFFF1 - 0x20

0xFFFF2 - 0x00

0xFFFF3 - 0x00

0xFFFF4 - 0x00

0xFFFF5 - 0x00

0xFFFF6 - 0x00

0xFFFF7 - 0x00

0xFFFF8 - 0x00

0xFFFF9 -0x00

0xFFFFA -0x00

0xFFFFB -0x00

0xFFFFC -0x03

0xFFFFD -0x23

        0xFFFFE -0x11

0xFFFFF -0x11

Log report sent by you also shows that data read is failing for locations 0xFFFFE0 to 0xFFFFEF which is not likely to happen since its part of user memory. Please try writing data (0x55 or 0xAA) again only in memory locations 0xFFFFE0 to 0xFFFFEF, read back and verify whether failure is repeating?

Thanks,

Shivendra 

Cypress Semiconductor






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