From ffb8f38a9afa09c3c39730bc2dd408c725f57912 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=89der=20Ferreira=20Zulian?= <fzeder@rhrk.uni-kl.de>
Date: Tue, 21 Apr 2015 15:51:07 +0200
Subject: [PATCH] Added more information about configuration files.

---
 README.md | 42 ++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 42 insertions(+)

diff --git a/README.md b/README.md
index 3607b6fb..37e41f12 100644
--- a/README.md
+++ b/README.md
@@ -9,38 +9,80 @@ In a terminal window execute the commands that follow (the '$' symbolizes the
 terminal prompt).
 
 Go to your home directory.
+
+```
 $ cd
+```
 
 Create a directory for your projects.
+
+```
 $ mkdir projects
+```
 
 Clone the repository (in case of doubts about which repository you should
 clone ask your supervisor).
+
+```
 $ git clone https://<user>@git.rhrk.uni-kl.de/<user>/dram.vp.system.git
+```
 
 Go to the projetct directory
+
+```
 $ cd dram.vp.system
+```
 
 Execute the script that follows.
+
+```
 $ install_prerequisites.sh
+```
+
 
 ## With QTCreator
 Execute the *qtcreator*.
+
+```
 $ qtcreator &
+```
 
 Use the menu bar and open the DRAMSys project.
+
 **File -> Open Project -> dram.vp.sys/dram/dramSys/dramSys.pro**
 
 When you open the project for the first time a configuration window pops-up.
 Then click in **Configure Project** and after that **Build** the project.
 
+Repeat this procedure and build the trace analyser project.
+
+**File -> Open Project -> dram.vp.sys/analyser/analyser/traceAnalizer.pro**
+
 
 ## Without QTCreator
 
+```
 $ cd dram
 $ mkdir build
 $ cd build
 $ qmake ../dramSys/dramSys.pro
 $ make
+```
+
+ 
+# DRAMSys Resources
+
+The simulator's config is done via several files. One can find such configuration files in the directory below.
+
+```
+$ cd /projects/dram.vp.system/dram/resources
+```
+
+* resources
+  * configs - XML files used for configurate specific details of the simulation.
+  * scripts - useful tools (debuging, configuration, etc.).
+  * simulations - global configs for simulations (debug mode, power analysis and database recording, etc.)
+  * traces - trace files for simulations. They contain accesses to memory in certain known scenarios.
+