512Kb SRAM expansion for the Arduino Mega (software)

The final part of this series of blog posts will present some open source software that you can use to exploit the new memory space. You can download the library source code from my downloads page.

The xmem library

I’ve put together a collection of functions into a library that you can use to manage access to the extended memory. The aim of the library is to enable the existing memory allocation functions such as malloc, free, new and delete to work with the extended memory.

The xmem functions are contained in a namespace called xmem so you need to prefix your calls to these functions with xmem::, for example xmem::begin(…). The functions are declared in xmem.h, so you must include that header file like this:

#include "xmem.h"

Installation instructions for the Arduino IDE

  1. Download the library zip file from my downloads page.
  2. Browse to the libraries subdirectory of your Arduino installation. For example, for me that would be C:\Program Files (x86)\arduino-1.0.1\libraries.
  3. Unzip the download into that directory. It should create a new folder called xmem with two files in it.
  4. Start up the Arduino IDE and use the Tools -> Import Library -> xmem option to add the library to your project

xmem functions

void begin(bool heapInXmem_)

This function must be called before you do anything with the extended memory. It sets up the AVR registers for external memory access and selects bank zero as the current bank.

If you set the heapInXmem_ parameter to true (recommended) then the heap used by malloc et. al. will be located in external memory should you use it.


void setMemoryBank(uint8_t bank_,bool switchHeap_=true);

Use this function to switch to another memory bank. bank_ must be a number between zero and seven. If switchHeap_ is true (the default) then the current state of the heap is saved before the bank is switched and the saved state of the new bank is made active. This heap management means that you can freely switch between banks calling malloc et. al. to make optimum use of the external memory.


// use the memory in bank zero


// use the memory in bank one

SelfTestResults selfTest();

This is a diagnostic function that can be used to check that the hardware is functioning correctly. It will write a bit pattern to every byte in every bank and will then read back those bytes to ensure that all is OK. Because it overwrites the entire external memory space you do not want to call it during normal program operation.

This function returns a structure that contains the results of the self test. The structure is defined as follows.

struct SelfTestResults {
  bool succeeded;
  volatile uint8_t *failedAddress;
  uint8_t failedBank;

If the self-test succeeded then succeeded is set to true. If it fails it is set to false and the failed memory location is stored in failedAddress together with the failed bank number in failedBank.

  xmem::SelfTestResults results;



Some common scenarios

In this section I’ll outline some common scenarios and how you can configure the external memory to achieve them.

Default heap, default global data, external memory directly controlled

In this scenario the malloc heap and global data remain in internal memory and you take direct control over the external memory by declaring pointers into it.

Memory layout for direct access

Your code could declare pointers into the external memory and use them directly. This is the simplest scenario.

#include <xmem.h>

void setup() {
  // initialise the memory

void loop() {
  // declare some pointers into external memory
  int *intptr=reinterpret_cast<int *>(0x2200);
  char *charptr=reinterpret_cast<char *>(0x2200);

  // store integers in bank 0

  // store characters in bank 1

Default global data, heaps in external memory

In this scenario we move the malloc heap into external memory. Furthermore we maintain separate heap states when switching banks so you effectively have eight independent 56Kb heaps that you can play with.

Memory layout for external heaps

This is a powerful scenario that opens up the possibility of using memory-hungry libraries such as the STL that I ported to the Arduino.

Example 1, using c-style malloc and free to store data in the external memory.

#include <xmem.h>

byte *buffers[8];

void setup() {
  uint8_t i;


  // setup 8 50K buffers, one per bank

  for(i=0;i<8;i++) {
    buffers[i]=(byte *)malloc(50000);

void loop() {

  uint16_t i,j;

  // fill each allocated bank with some data

  for(i=0;i<8;i++) {




Example 2. Using the standard template library to store some vectors in external memory. This is the slowest option but undoubtedly the most flexible. vectors only scratch the surface of what’s possible. maps and sets are all perfectly feasible with all this memory available.

#include <xmem.h>
#include <iterator>
#include <vector>
#include <new.cpp>

byte *buffers[8];

void setup() {

void loop() {

  std::vector<byte> *testVectors[8];
  uint16_t i,j;

  for(i=0;i<8;i++) {

    testVectors[i]=new std::vector<byte>();


  for(i=0;i<8;i++) {


    delete testVectors[i];

 * flash the on-board LED if something goes wrong
void fail() {
  for(;;) {

Other articles in this series

512Kb SRAM expansion for the Arduino Mega (design)
512Kb SRAM expansion for the Arduino Mega (build)

Schematics, PCB CAD and Gerbers

I don’t have any more boards left to sell, but you can now print and build your own by downloading the package from my downloads page. Good luck!

  • edward

    Hi, thanks for putting together xmem. Any idea how one could go about creating a struct in external memory (quadram in this case) with xmem?

    Looking to implement something like the following:

    typedef struct {

    bool on;
    int x;
    int y;

    } coordinate;

    grid coordinate[50];

    Thanks in advance!!

    • I would use a heap in a bank of external memory, described in "Default global data, heaps in external memory" above. So your example would require in setup():


      Then you could allocate your array thus:

      coordinate *grid;
      grid=(coordinate *)malloc(sizeof(coordinate)*50);"

      To verify that your array is in external memory, print out the the base pointer to the Serial port:


      The value printed should be between 0x2200 and 0xFFFF.

      Hope I could help.

  • Robert Woodcock

    We are using the freeMemory() library to monitor the internal memory; when we active xmem::begin(true) freeMemory() begins giving unreliable readings? Can you help … it is useful to know what the internal available memory is?

  • Really glad you put this together for us. I only need a maximum of 2KBytes external space, but it has been a real big help in my project. I plan to use your library for many future projects as well. I just can’t believe how incredible the Arduino Mega has turned out to be.

    • I’m glad I could help. Good luck with your projects.

  • Nicolai Mathiasen

    I was looking for an example of adding external memory and found your page which looks good.

    I havent fiddled with it yet since I need to purchase some memory first. Since I dont want to throw away a lot of memory (the botton 8KB) – I plan to only use the upper 32-64KB memory area – and then add another page select signal connected to the SRAM A15. The pages will only be 32KB but twice as many.

    What do you think about this idea?

    • I understand your goal but not how you’re going to achieve it. What size SRAM are you planning to use and, referring to section 9.1 of the ATMega1280 datasheet, which addressing scheme will allow you to access the lower 8Kb of your external memory?

      • Nicolai Mathiasen

        Hi Andy. Thanks for responding. Since I have only just started looking at external memory yesterday I wasnt aware that 0x9100 to 0xFFFF was “Do not use”.

        I thought the Xmem was available from 0x2200 to 0xFFFF in one regular continuous block seen from the software.

        Actually I am wondering a little about this strange arrangements. I didnt find an answer why the 0x9100 to 0xFFFF was do not use. In the Figure 9-1 it looks like 0x2200 to 0xFFFF is one long continuous block and I therefore assumed I could use the upper sector completely and just let 0x2200 to 0x7FFF empty. But looking at figure 9-7 I can see a strange “twisted” memory map. 🙂 :-/

        Thanks for pointing this out to me. I suppose one has to use a GAL/PAL circuit or some 74HC logic to make it happen without losing something?

  • Ken Kloster


    Andy: I now have one of your memory cards running on my Mega. Seems to work well. I will be using it to store very large 2 dimensional array. I don’t see any issues with that.

    I would like to know how to check to see how much memory is used and how much is left.

    Should I initialize the memory with say 0xff in each mem location at boot time and before using the RAM??

    I thought about initialize that RAM with 0x00 or 0xff and count them remaining ones but that won’t work as most of the data I will be storing will be XBM graphic files an very likely could have lots of 0x00s and 0xffs.


    • The simplest method would be to place the heap in the external memory and use malloc/free to perform the usage management.

      • Ken Kloster

        Thanks for your input. I will take that into consideration.