Skip to main content


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.

Octal xSPI Memory


xSPI (8x SPI)

High bandwidth

Low power

eXecute-in-Place (XiP)



See More

Dual / Quad SPI Memory


SPI, Dual, Quad

1.8V, 3.0V. Wide VCC

Ultra-low Energy, Low Power

7nA sleep

Battery monitor


See More

DataFlash SPI Memory

Fast Flexible Robust

Concurrent programming

Easy to use

Power fail protection

Data integrity

Low power modes


See More

Wafer KGD

Known Good Die program

Up to 125°C operating temperature

All voltage levels

  • 1.8V
  • 3.0V
  • Wide Voltage 1.65V to 3.6V

See More

Verified Memory for NXP

Low Power and high-speed SPI Flash solutions for NXP i.MX RT MCUs

See More

Verified Memory for ST Microelectronics

Dialog SPI Flash solutions verified on over 30 STM32 MCUs

See More

CBRAM Technology

CBRAM is a resistive RAM technology that provides power, speed, and cost benefits over other non-volatile memory technologies. It is well suited for battery powered devices, edge computing, and AI applications.

See More

Stay connected

Get in touch with us directly through our worldwide sales offices, or contact one of our global distributors and representatives.

Inquiries Distributors and Representatives Register for newsletters
Back to results


3 weeks ago

AT25SL128A Data Corruption on Write

Posted by MortenSchmidt 10 points 1 reply

We are using AT25SL128A and have a problem with data corruption. We use 8MHz plain SPI mode and have also tried 4MHz clock. We operate in SPI mode 3, verified with logic analyzer the SPI format is valid.

One in about 10-50 writes fail our readback test. Subsequent reads produce consistent output, the problem is isolated to the write operations.

The corruption also always results in one or two bits that should be 1 being corrupted to 0. Never the other way around.

The corruption always occurs in the 2nd last byte in a block.

Most of the time only one bit is corrupted but we have sometimes seen two, and when this happens they are two adjacent bits.

We have verified signal integrity. MISO from AT25SL128A has rise and fall times just about 2.2ns without ringing and CLK+MOSI have rise/fall times just about 7ns without ringing. Traces are quite short. Further the fact we have seen two 1's in a row corrupted to two 0's steers suspicion away from a signal integrity problem.

We have also experimented with improved power supply decoupling and even external 1.8V from an independent 1.8V supply, none of this has made any difference.

What could possibly be the problem here?

3 weeks ago

gordonmacnee 60 points

My first thought would be ringing or over/undershoot on the signal lines but you have discounted this. 8MHz SPI Clk is considered a slow clock so that should not be a problem. Can you share some more details of your circuit like uController, schematic, Scope captures of the signal lines etc.(send them to so as not to share them on a public forum). Is there anything else on the SPI bus?

How many parts have you tested?

How many boards is this problem being seen on? 

Please use my email to send any info you do not wish to share on the forum.

Note that this is a VERY popular parts with millions of units shipping per quarter and we have not had similar problems reported so we are keen to see if we can resolve this quickly.