diff --git a/tools/hdltool_readme.txt b/tools/hdltool_readme.txt
index 6fa6ebcc4fa16d88b251fce3ccded61b8d0c4f2e..fb04a4363913c6d0c68335b4352be9d949741a16 100644
--- a/tools/hdltool_readme.txt
+++ b/tools/hdltool_readme.txt
@@ -8,11 +8,12 @@ Contents:
   c) Tool environment setup scripts
   d) Compiling the Altera libraries for simulation with Modelsim
   e) Quartus user_components.ipx
-  f) Tool start scripts
-  g) How to start Modelsim for RadioHDL
-  h) How to start Quartus for RadioHDL
-  i) How to start Modelsim for UNB
-  j) How to start Quartus for UNB
+  f) Generate IP
+  g) Tool start scripts
+  h) How to start Modelsim for RadioHDL
+  i) How to start Quartus for RadioHDL
+  j) How to start Modelsim for UNB
+  k) How to start Quartus for UNB
   
 3) HDL environment configuration files
   a) Tools and libraries
@@ -156,7 +157,27 @@ In a Unix system this goes to the personal folder at ~ (= $HOME):
 Maybe coping the user_components.ipx from SVN location to the personal ~ location avoids having to copy it into the installation location.
 
 
-f) Tool start scripts
+f) Generate IP
+
+The IP needs to be generated before it can be simulated or synthesized. The Quartus IP is generated using Qsys or the Megawizard.
+Initialy the GUI was used to create and generate the IP, but once it works and is stable then the IP can be generated uisng a script.
+Therefore each library with IP has a dedicated generate_ip.sh, for example:
+
+  > cd $RADIOHDL/libraries/technology/ip_stratixiv/mac_10g
+  > ./generate_ip.sh
+ 
+The IP for all libraries of a certain FPGA technology can also be generated automatically in one command using:
+  
+  # ip_stratixiv 
+  > cd $RADIOHDL/libraries/technology/ip_stratixiv
+  > ./generate-all-ip.sh
+
+  # ip_arria10
+  > cd $RADIOHDL/libraries/technology/ip_arria10
+  > ./generate-all-ip.sh
+
+
+g) Tool start scripts
 
 The definitions for actually running Modelsim and Quartus are not kept in the ~/.bashrc file or the setup script but are
 set in a tool start script:
@@ -171,7 +192,7 @@ the advantages of using a seperate tool start script is:
     only apply to the started tool environment
 
 
-g) How to start Modelsim for RadioHDL
+h) How to start Modelsim for RadioHDL
 
 To start Modelsim for RadioHDL do:
 
@@ -198,7 +219,7 @@ The commands.do defines the following extra commands that can be used at the Mod
   . ds        : delete all signals from the wave window
   
   
-h) How to start Quartus for RadioHDL
+i) How to start Quartus for RadioHDL
 
 To start Quartus for RadioHDL do:
 
@@ -219,7 +240,7 @@ Now only the toolsets 'unb1' and 'unb2' are defined
 The Quartus unb_* bash commands for $UNB have also been ported to $RADIOHDL. They use quartus 11.1 so they only support Stratix IV and UniBoard1.
 For Arria10 and UniBoard2 these commands will have to be ported to an equivalent in Python. The following Quartus run_* bash commands are kept in
 $RADIOHDL/tools/quartus. These run_* bash commands can be used in $RADIOHDL. The run_* bash commands assume that the design library
-projects are in the central $HDL_BUILD_DIR = $RADIOHDL/build/quartus:
+projects are in the central $HDL_BUILD_DIR = $RADIOHDL/build:
 
 For building a SOPC system use:
   > run_sopc      unb1 unb1_minimal_sopc
@@ -240,7 +261,7 @@ For building a QSYS system use:
   > run_sof       unb1 unb1_minimal_qsys 0
 
 
-i) How to start Modelsim for UNB
+j) How to start Modelsim for UNB
 
 GUI:
 
@@ -251,7 +272,7 @@ GUI:
 See the setup_unb.sh environment script and ASTRON_RP_1354_unb_minimal.pdf for more description.
 
 
-j) How to start Quartus for UNB
+k) How to start Quartus for UNB
 
 GUI: