Skip to main content

Octal xSPI Memory

Blazingly Fast. Low Power Consumption

  • High Bandwidth
  • Low Power
  • Execute-in-place
  • Read While Write
  • Security

With the need for greater processing performance at lower power, execute-in-place (XiP) is quickly becoming the architecture of choice for IoT devices. EcoXiP’s blazingly fast performance and low power consumption allow even time-critical software to be executed directly out of non-volatile memory, reducing boot time and system cost.

Best performance, best power

Performance
CoreMark® test on NXP’s i.MX RT1050 with 8 instruction cache
invalidations every ms to simulate task switching & interrupt handling.

Efficiency
CoreMark® score / power consumption.

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

EcoXiP Octal xSPI Memory

Density Product / Datasheet Speed Vcc range Interface Details Status Samples
               
128Mbit ATXP128 (up to 105°C) 150MHz 1.7V-1.95V SPI Octal SDR/DDR   ● Active Order Samples
64Mbit ATXP064B (up to 105°C) 170MHz 1.7V-1.95V SPI Octal SDR/DDR   ● Preview Order Samples
32Mbit ATXP032 (up to 105°C) 150MHz 1.7V-1.95V SPI Octal SDR/DDR   ● Active Order Samples
ATXP128 (up to 105°C) details
Ordering Code Package
ATXP128-CCUE-Y 24CC - 8x6
ATXP128-CCUE-T 24CC - 8x6
ATXP128-UUE-T WLCSP - Contact Adesto
ATXP128-DWF See Wafer-Die Solution Menu
ATXP032 (up to 105°C) details
Ordering Code Package
ATXP032-CCUE-Y 24CC - 8x6
ATXP032-CCUE-T 24CC - 8x6
ATXP032-UUE-T WLCSP - Contact Adesto
ATXP032-DWF See Wafer-Die Solution Menu
ATXP064B (up to 105°C) details
Ordering Code Samples
ATXP064B-CCUE-Y 24CC - 8x6
ATXP064B-CCUE-T 24CC - 8x6
ATXP064B-UUE-T WLCSP - Contact Adesto
ATXP064B-DWF See Wafer-Die Solution Menu

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
Product Briefs and Summaries
Name Date Version
EcoXiP – Product Overview (310.85 KB)
Application notes
Name Date Version
AN105 PCB Design and Layout Considerations (313.89 KB)
AN106 Using EcoXiP on the NXP i.MX RT1050 EVKB Board (1.76 MB)
AN113 Configuring STMicroelectronics STM32H7A/B to work with Adesto’s EcoXiP Octal NOR Flash memory (445.22 KB)
Software Resources
Name Date Version
Simulation Tools(29.68 KB)
User guides and manuals
Name Date Version
Dialog Flash Memory for Dialog SoC Products (184.91 KB) 23/07/2021
White Papers & Technical Articles
Name Date Version
AI on the Edge: Don’t Forget the Memories (1 MB)
RoHS and Reach
Name Date Version
Certifications and Statements (29.68 KB)
General
Name Date Version
EcoXiP Read While Write Overview (339.18 KB)
Longevity Program (29.68 KB)
Product Change Notifications (29.68 KB)
The Linley Processor Report; Adesto Execute-In-Place (536.46 KB)

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
Video thumbnail, click to open and play

Adesto EcoXiP Octal EVK Hardware Setup

Video thumbnail, click to open and play

Adesto EcoXiP Octal EVK Software Setup

Video thumbnail, click to open and play

Read While Write feature improves system performance

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

EcoXiP Octal xSPI Memory Products

Product Shop
ATXP128 (up to 105°C) Digikey Arrow Avnet US Mouser Future Electronics
ATXP064B (up to 105°C) Digikey Arrow Avnet US Mouser Future Electronics
ATXP032 (up to 105°C) Digikey Arrow Avnet US Mouser Future Electronics

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

Memory

2 months ago

AT25SF321 clock problem

Posted by nsanfa 35 points 4 replies
0 upvotes

Hi,

Currently I am working on a project that uses the memory AT25SF321. In some devices the flash operates at 40MHz perfectly and in other devices the flash does not work properly at clock frequencies higher than 33MHz (same hardware and firmware).

For instance, when I read the manufacturer and device ID at 40MHz I get the correct response (0x1F, 0x87, 0x01) from some devices  and from others I get 0x0F, 0xC3, 0x81. Bit wise it seems to be a shift, like the flash is not handling correctly the timing at the start of the response. If I reduce the clock frequency to 30MHz the flash works perfectly. 

The ID (on the chip) of a "faulty" flash and of one that works properly are the same: "adesto1949 25SF321 SSHD". 

Kind regards,

Noe

2 months ago

gordonmacnee 220 points

Hello Noe,

Just checking but do you mean the AT25SF321B - the AT25SF321 (without any suffix) is now End of Life. Either way both parts should have no problem running well in excess of 40MHz.

Would you let us know what voltage you are running these parts at and which micro controller you are using? 

Are you able to have a look at the signal lines with a 'scope and check that you have a fast enough rise and fall on your clock and signal lines and that they are making it above and below the thresholds for the voltage you are using. If you think that they are meeting daatsheet parameters, would you also post the 'scope captures here and we will dig a little deeper.    

2 months ago

Hi,

Thanks for the reply, here are some details:

- The flash is an AT25SF321 (not B).

- The flash memory is controlled by an ESP32-WROOM (configured with SPI full duplex at 40MHz).

- ESP32 and flash run at 3.3V.

- In this case the values read by the esp32 are [0x1F, 0xC7, 0x81] for the command 0x9F.

I attached some captures of the clock (yellow), MOSI (red) and MISO (blue) signals.  "ClkFreq" shows the frequency of the clock, "Clk_MOSI_MISO" shows the three signals (with the 0x9F commad on MOSI) and "MISO_signal" shows the flash response(I am sorry for the image quality, I connected the osciloscope to a screen to take the photos because the osciloscope screen was even worse).

If I set the SPI frequency to 30MHz the flash memory gives the correct ID ([0x1F, 0x87, 0x01]). Also, the devices that work at 40MHz have this problem at 50MHz (same response, same hardware and same firmware). 

After the 0x9F commad there are bytes in the MOSI channel, according to the datasheet the memory ignores the data after the command and it should not be a problem or ¿does it need a 0 after the last bit?

Kind regards.

Attachment Size
MISO channel, response of the flash 150.03 KB
Clock signal 116.47 KB
Clock(yellow), MISO(blue) and MOSI(red) signals (with the command 0x9F on MOSI) 150.41 KB

2 months ago

I managed to make the AT25SF321  flash work at 40MHz after adding a delay of 25ns before reading MISO. Also, the flash memories that work fine at 40MHz doesnt work at 50MHz because that is the upper limit (my mistake, I thought the limit was 55MHz).

accepted answer!

2 months ago

gordonmacnee 220 points

Hi Nsanfa,

The signals on the 'scope images look very rounded with the SCLK looking more like a sine wave... Can you change the output pins to give you a faster rise and fall time or a stronger drive? Looking at the "MISO channel response of the flash" trace and assuming that the first high is the '1' of the '1F' byre in the response then checking every falling edge I read 

...1 1111 1000 0111 0000 0001 = 1F 87 01

Might be the ESP32 is reading too early given the slow slew rate on the clk.

Once any "read" command is complete then any extra "data" sent on the MOSI line is ignored so it does not matter what is in the TX buffer after the command (and address etc) has been sent.