Update README.md

1 files changed, 4 insertions, 32 deletions

diff --git a/README.md b/README.md
index 49482a2..4606f16 100644
--- a/README.md
+++ b/README.md
@@ -6,23 +6,9 @@ This simple host/trusted application serves the purpose of measuring the perform
 Building and running the applications on QEMU
 ---
 #### Building
-Easiest way to test this is to run the script [setup_qemu_optee.sh](https://github.com/kong1191/optee_benchmark/blob/master/script/setup_qemu_optee.sh). This script will setup the complete environment needed to run OP-TEE on QEMU.
+Easiest way to test this is to run the script [setup_qemu_optee.sh](script/setup_qemu_optee.sh). This script will setup the complete environment needed to run OP-TEE on QEMU.
 
-After finish executing setup_qemu_optee.sh, there is the script [build_app.sh](build_app.sh) which we recommend that you use when build, since that sets the needed flags and points to the correct folders. You can of course call make directly on the commandline, but you will have to point out all the other things mentioned in "build_app.sh" in any case. When this has been setup, you should be able to build the applications.
-
-Next step is to get the newly built applications into the filesystem that is used when booting QEMU. To do this you need to edit the file ```gen_rootfs/filelist-tee.txt``adding lines telling where to find and where to store the test binary and the Trusted Application, like this:
-
-```
-# TA's
-....
-file /lib/teetz/99e937a0-8f3e-11e4-8b8f0002a5d5c51b.ta /home/johndoe/devel/qemu_optee_benchmark/optee_benchmark/ta/out-client-aarch32/99e937a0-8f3e-11e4-8b8f0002a5d5c51b.ta 444 0 0
-
-# OP-TEE Tests
-...
-file /bin/simple_client /home/johndoe/devel/qemu_optee_benchmark/optee_benchmark/host/simple_client 755 0 0
-```
-
-When that has been done and the files has been saved, you need to regenerate the filesystem. That could be done by running the script ```build.sh```. For you who wonder about the strange name of the Trusted Application, we can mention that this is coming from the UUID for the particular Trusted Application.
+When that has been done and the files has been saved, you need to regenerate the filesystem. That could be done by running the script ```build.sh```.
 
 #### Running
 1. Run ```serial_0.sh``` and ```serial_1.sh``` in different console.
@@ -44,23 +30,9 @@ When that has been done and the files has been saved, you need to regenerate the
 Building and running the applications on FVP
 ---
 #### Building
-Easiest way to test this is to run the script [setup_fvp_optee.sh](https://github.com/kong1191/optee_benchmark/blob/master/script/setup_fvp_optee.sh). This script will setup the complete environment needed to run OP-TEE on FVP.
-
-After finishing executing setup_fvp_optee.sh, there is the script [build_app.sh](build_app.sh) which we recommend that you use when build, since that sets the needed flags and points to the correct folders. You can of course call make directly on the commandline, but you will have to point out all the other things mentioned in "build_app.sh" in any case. When this has been setup, you should be able to build the applications.
-
-Next step is to get the newly built applications into the filesystem that is used when booting FVP. To do this you need to edit the file ```gen_rootfs/filelist-tee.txt``adding lines telling where to find and where to store the test binary and the Trusted Application, like this:
-
-```
-# TA's
-....
-file /lib/teetz/99e937a0-8f3e-11e4-8b8f0002a5d5c51b.ta /home/johndoe/devel/fvp_optee_benchmark/optee_benchmark/ta/out-client-aarch64/99e937a0-8f3e-11e4-8b8f0002a5d5c51b.ta 444 0 0
-
-# OP-TEE Tests
-...
-file /bin/simple_client /home/johndoe/devel/fvp_optee_benchmark/optee_benchmark/host/simple_client 755 0 0
-```
+Easiest way to test this is to run the script [setup_fvp_optee.sh](script/setup_fvp_optee.sh). This script will setup the complete environment needed to run OP-TEE on FVP.
 
-When that has been done and the files has been saved, you need to regenerate the filesystem. That could be done by running the script ```build_secure.sh``` and ```build_normal.sh```. For you who wonder about the strange name of the Trusted Application, we can mention that this is coming from the UUID for the particular Trusted Application.
+When that has been done and the files has been saved, you need to regenerate the filesystem. That could be done by running the script ```build_secure.sh``` and then ```build_normal.sh```. 
 
 #### Running