diff --git a/doc/nanosoc_configuration_manual.pdf b/doc/nanosoc_configuration_manual.pdf
index 3f3fc5cb84ad76f8101abc573606d4313be11047..6156bc79c2413fa0d517043a1a9fd2f293a2d1cd 100644
Binary files a/doc/nanosoc_configuration_manual.pdf and b/doc/nanosoc_configuration_manual.pdf differ
diff --git a/doc/nanosoc_datasheet.pdf b/doc/nanosoc_datasheet.pdf
index b405d7aa890748bd4084abbaddf70af631ef2917..53db1f080f53e2e2085b75c83abe991433b24248 100644
Binary files a/doc/nanosoc_datasheet.pdf and b/doc/nanosoc_datasheet.pdf differ
diff --git a/doc/tex/nanosoc_configuration_manual.tex b/doc/tex/nanosoc_configuration_manual.tex
index 583f17962069af819316b20b15bf1c4f573f1db2..3d8d5de6911c22eaa9799ef5727d471197d4e040 100644
--- a/doc/tex/nanosoc_configuration_manual.tex
+++ b/doc/tex/nanosoc_configuration_manual.tex
@@ -220,6 +220,7 @@ To add your own testcodes to run on nanosoc in the simulation environment, you c
     \item Copy the makefile from one of the example testcodes to your test code directory
     \item Edit the TESTNAME variable in the new makefile to the name of your test
     \item If you want to run any ADP code before your test, add an adp.cmp file (example in the adp\_v4\_cmd\_tests)
+    \item If you want to preload expansion memories, add an expram\_l.hex and/or expram\_h.hex
     \item Add the name of your test to the accelerator-project/system/software\_list.txt file 
 \end{enumerate}
 
@@ -252,6 +253,18 @@ For more detailed C code templates, please see the firmware in the
 accelerator-project/nanosoc\_tech/software/common/validation.
 These are also the testcodes used for validating nanoSoC.
 
+\subsection{Preloading expansion memories}
+You may want to load test vectors directly into the expansion memories to run your tests. Doing this can save space in the 
+instruction memory space as you then don't have to load data in as arrays or vectors in your testcode. Instead you can use the simulator
+to automatically load these memories at the start of simulation.
+
+To do this, simply add an "expram\_l.hex" file and/or "expram\_h.hex" file to your testcode directory. These files will then 
+be loaded to the EXPRAM\_L or EXPRAM\_H region repectively. These can then be addressed in your testcode from 0x80000000 for EXPRAM\_L 
+and 0x90000000 for EXPRAM\_H. 
+
+The expram\_l.hex files must be ASCII text files with a single byte per line. They will look very similar to the .hex files that are used
+to preload the instruction memory.
+
 
 \chapter{FPGA Flow}
 \section{Summary}