Changes between Version 1 and Version 2 of Arch/Soclib/Tutorial
- Timestamp:
- Dec 3, 2009, 2:36:13 PM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Arch/Soclib/Tutorial
v1 v2 22 22 === Getting SoCLib === 23 23 24 We now need to have a working SoCLib install. SoCLib installation is explained here: https://www.soclib.fr/trac/dev/wiki/InstallationNotes24 We now need to have a working SoCLib install. SoCLib installation is explained here: soclib:InstallationNotes 25 25 26 26 === SoCLib platform description === 27 27 28 28 The SoCLib source tree contains a platform dedicated to this tutorial: 29 {{{soclib/soclib/platform/topcells/caba-vgmn-mutekh_soclib_tutorial/}}} 29 [soclib:source:trunk/soclib/soclib/platform/topcells/caba-vgmn-mutekh_soclib_tutorial/] 30 30 31 31 === Getting the cross-compilers === … … 86 86 === Writing the MutekH configuration === 87 87 88 The MutekH configuration for the 4 Mips processors platformis in the [source:trunk/mutekh/examples/hello/config examples/hello/config] file.88 The MutekH configuration for the hello application is in the [source:trunk/mutekh/examples/hello/config examples/hello/config] file. 89 89 90 90 This file only holds information about the application (here a simple pthread application) and relies upon files in the [source:trunk/mutekh/examples/common@1183 examples/common] directory for the platform definitions. … … 98 98 The MutekH software uses hardware enumeration to get details about available hardware in the platform, so the `CONFIG_ARCH_DEVICE_TREE` token is defined in the [source:trunk/mutekh/examples/common/platforms-soclib.conf@1183 examples/common/platforms-soclib.conf] configuration file. It will let the kernel get the platform layout description from a FlattenedDeviceTree which will be built into the kernel. 99 99 100 The refore, the build also compiles the correct FlattenedDeviceTree from the platform name.100 The build system also compiles the correct FlattenedDeviceTree from the platform name, see [source:trunk/mutekh/examples/common/Makefile@1183 examples/common/Makefile]. 101 101 102 The current FlattenedDeviceTree source file is 103 [source:trunk/mutekh/examples/common/pf_soclib_tutorial_ppc.dts examples/common/pf_soclib_tutorial_ppc.dts], 104 [source:trunk/mutekh/examples/common/pf_soclib_tutorial_arm.dts (for arm)], 105 [source:trunk/mutekh/examples/common/pf_soclib_tutorial_mips.dts (for mips)]. 102 The used FlattenedDeviceTree source file are in 103 [source:trunk/mutekh/examples/common/ examples/common/]: 104 [source:trunk/mutekh/examples/common/pf_soclib_tutorial_ppc.dts pf_soclib_tutorial_ppc.dts], 105 [source:trunk/mutekh/examples/common/pf_soclib_tutorial_arm.dts pf_soclib_tutorial_arm.dts], 106 [source:trunk/mutekh/examples/common/pf_soclib_tutorial_mips.dts pf_soclib_tutorial_mips.dts]. 106 107 107 === Co mpiling the application along with MutekH ===108 === Configuring the application along with MutekH === 108 109 109 110 The MutekH kernel and the application may be built out of the source tree. … … 121 122 MutekH build option list (target architecture, cpu type, …) 122 123 123 See the `config.mk` file in the tutorial platform directory for more information. 124 These variables are already set in the `config.mk` file to target the hello demo application. 125 126 Inside `config.mk`, you'll also find a `CPU` variable that determines which CPU to use in the simulator platform. 127 128 See the comments in `config.mk` for more information. 129 130 === Compiling the application along with MutekH === 131 132 To compile the kernel with the application, just run `make` with the path to MutekH source directory: 124 133 125 134 {{{ … … 128 137 }}} 129 138 130 This will build the MutekH kernel along with the application. 131 You can still build MutekH separately as explained in the first part. The simulator can then be built using: 132 133 {{{ 134 $ cd soclib/soclib/platform/topcells/caba-vgmn-mutekh_tutorial 135 $ make system.x 136 }}} 139 This will build the MutekH kernel along with the application, and the correct simulator. 137 140 138 141 == Execution == 139 142 140 You can optionally pass an alternative kernel to the simulator, but this defaults to the correct kernel name if you followed the tutorial until here. 143 Simply run the simulator: 141 144 {{{ 142 $ ./s ystem.x mutekh/kernel-soclib-ppc.out145 $ ./simulation.x 143 146 }}} 144 147