diff options
author | Sandeep Nair | 2011-11-08 08:53:58 -0600 |
---|---|---|
committer | Sandeep Nair | 2011-11-08 08:53:58 -0600 |
commit | 35b661f68134e0de9a0e3201eb6f45ed47a60576 (patch) | |
tree | 1ce08a754c2737707aa59ec52ef7b03749bb59c9 | |
parent | e90c26bb8b63c99b833c9e8c915bdead0c4ba9d3 (diff) | |
download | mad-utils-35b661f68134e0de9a0e3201eb6f45ed47a60576.tar.gz mad-utils-35b661f68134e0de9a0e3201eb6f45ed47a60576.tar.xz mad-utils-35b661f68134e0de9a0e3201eb6f45ed47a60576.zip |
Updates to README's
-rw-r--r-- | mad-loader/README.txt | 19 | ||||
-rw-r--r-- | map-tool/README.txt | 11 |
2 files changed, 26 insertions, 4 deletions
diff --git a/mad-loader/README.txt b/mad-loader/README.txt index c33fbd5..c2c6579 100644 --- a/mad-loader/README.txt +++ b/mad-loader/README.txt | |||
@@ -6,7 +6,7 @@ Contents: | |||
6 | 6 | ||
7 | Build instructions: | 7 | Build instructions: |
8 | NOTE FOR BUILDING ON WINDOWS ENVIRONMENT: For building on windows environment GNU utilities like | 8 | NOTE FOR BUILDING ON WINDOWS ENVIRONMENT: For building on windows environment GNU utilities like |
9 | "make" would be required. The following build procedure should also work on MINGW-MSYS Bourne shell. | 9 | "make" would be required. MINGW-MSYS installation is required for Windows build environment. |
10 | 10 | ||
11 | Before starting the build following environment setup has to be done | 11 | Before starting the build following environment setup has to be done |
12 | 1) variable C_DIR should be set to the top directory of the Code Generation tools e.g. | 12 | 1) variable C_DIR should be set to the top directory of the Code Generation tools e.g. |
@@ -20,11 +20,24 @@ NOTE FOR BUILDING ON WINDOWS ENVIRONMENT: For building on windows environment GN | |||
20 | MSYS bash shell: | 20 | MSYS bash shell: |
21 | export PATH=/c/Program\ Files/Texas\ Instruments/C6000\ Code\ Generation\ Tools\ 7.2.4/bin:$PATH | 21 | export PATH=/c/Program\ Files/Texas\ Instruments/C6000\ Code\ Generation\ Tools\ 7.2.4/bin:$PATH |
22 | 22 | ||
23 | Sample build scripts are provided in the current directory to build MAD loader. | ||
24 | Modify the above mentioned environment variables in the build scripts to | ||
25 | adjust to existing build environment. | ||
26 | 1. build_loader_lnx.sh: Script to build MAD loader in Linux bash shell | ||
27 | 2. build_loader_msys.sh: Script to build MAD loader in MSYS bash shell | ||
28 | |||
29 | For little endian build the script is invoked as: | ||
30 | - ./build_loader_lnx.sh device_name | ||
31 | For big endian build the script is invoked as: | ||
32 | - ./build_loader_lnx.sh device_name big | ||
33 | where device name can be C6670 or C6678 | ||
34 | |||
35 | |||
23 | Example applications: | 36 | Example applications: |
24 | Each of the applications have a makefile which should be used to build the application. | 37 | Each of the applications have a makefile which should be used to build the application. |
25 | The examples can be built as dynamic relocatable objects with shared library to test the MAD | 38 | The examples can be built as dynamic relocatable objects with shared library to test the MAD |
26 | flow or can be built as a static executable to test in prelinker bypass mode. | 39 | flow or can be built as a static executable to test MAD flow in prelinker bypass mode. |
27 | A build script is available in "./examples" directory to build the examples. | 40 | A sample build script is available in "./examples" directory to build the examples. |
28 | 41 | ||
29 | MAD loader library: | 42 | MAD loader library: |
30 | The makefile for building the MAD loader library is in the directory "mal/malLib/build" | 43 | The makefile for building the MAD loader library is in the directory "mal/malLib/build" |
diff --git a/map-tool/README.txt b/map-tool/README.txt index baef04b..f2b5dc8 100644 --- a/map-tool/README.txt +++ b/map-tool/README.txt | |||
@@ -18,7 +18,7 @@ example invokation of MAP tool on Windows Command shell is as follows: | |||
18 | maptool.py config-files\maptoolCfg_C6678_windows.json | 18 | maptool.py config-files\maptoolCfg_C6678_windows.json |
19 | 19 | ||
20 | bypass-prelink: | 20 | bypass-prelink: |
21 | In bypass-prelink mode MAD infrastructure is used as a multicore ELF loader | 21 | In bypass-prelink mode, MAD infrastructure is used as a multicore ELF loader |
22 | only. In this mode it is assumed that the applications are linked to their | 22 | only. In this mode it is assumed that the applications are linked to their |
23 | runtime address and that the application has taken of multicore aspects while | 23 | runtime address and that the application has taken of multicore aspects while |
24 | doing address allocation. | 24 | doing address allocation. |
@@ -28,3 +28,12 @@ MAP tool in ELF loader only mode is invoked as: | |||
28 | example invokation of MAP tool on Linux bash shell in prelinker bypass mode is as follows: | 28 | example invokation of MAP tool on Linux bash shell in prelinker bypass mode is as follows: |
29 | python maptool.py config-files/maptoolCfg_C6670_bypass_prelink.json bypass-prelink | 29 | python maptool.py config-files/maptoolCfg_C6670_bypass_prelink.json bypass-prelink |
30 | 30 | ||
31 | Output: | ||
32 | The output of the MAP tool run is placed the ./images directory. | ||
33 | Following are the output of a MAP tool run: | ||
34 | 1. ROMFS binary image | ||
35 | 2. A CCS GEL file to enable symbolic debugging of the prelinked images on | ||
36 | target. This GEL file is not produced/required when the MAP tool is invoked in | ||
37 | "bypass-prelink" mode. | ||
38 | 3. The original application images in the directory "./images/appImages" | ||
39 | |||