Dialog Improves System Performance
Non-volatile memory (NVM) is a key component at the heart of every system design. It holds critical data, controls how the system boots, and affects overall performance. Choosing the right NVM is key. We’re here to help. Our wide range of NVM products offer an array of features designed to help tune and optimize your system.
xSPI (8x SPI)
SPI, Dual, Quad
1.8V, 3.0V. Wide VCC
Ultra-low Energy, Low Power
Known Good Die program
Up to 125°C operating temperature
All voltage levels
- Wide Voltage 1.65V to 3.6V
Renesas Memory Products
2 weeks ago
AT25SL128A went into protected sector statePosted by ArunH 95 points 7 replies
I have a design based on AT25SL128A. I started with the standardflash.c and tests for it from the Adesto github website and all tests pass. So I assume my SPI integration is fine on my MCU.
I then set it running for a longer test so that it would keep writing/reading back data and then wrap around to the start of memory. Then I erase the 4K sector to reclaim it for writing.
However when I read back data after the wrap followed by 4K erase, I found I was always reading all 0s. Further check revealed that Status Register 1 value was 0xFC which means all the protect bits were set to 1.
Q1: This was not done by me, so I am wondering if you have any suggestions on whether the flash might go into this state on its own due to any trigger?
Q2: Or can it only happen if the MCU wrote this value to it?
Note1: I was able to recover back to working state by writing a new value to Status Register 1 but I want to check how to avoid this in the future.
Note2: Status Register 2 was 0x00, which is the default value. It did not change.