From c7fb9a6147b1c8ee3aa70061ac573a4040dbc207 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Tue, 18 Mar 2014 09:31:29 -0600 Subject: dev-manual: Read-through edits applied to "Models" chapter. Several items taken care of here. Of note are the retiring of three BSPs (Chief River, N450, and sys9* stuff). Also of note is that Kepler recommended version is now 4.3.2 and not 4.3. The interface changed a bit as well in the section for installing that stuff. (From yocto-docs rev: 61bf82c1e68156d32a81e4c76dbb29db14665ffb) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/dev-manual/dev-manual-model.xml | 41 ++++++++++++++------------- 1 file changed, 22 insertions(+), 19 deletions(-) diff --git a/documentation/dev-manual/dev-manual-model.xml b/documentation/dev-manual/dev-manual-model.xml index 59c392f9db..63a447d59b 100644 --- a/documentation/dev-manual/dev-manual-model.xml +++ b/documentation/dev-manual/dev-manual-model.xml @@ -161,10 +161,10 @@ mpc8315e, and routerstationpro. The recipes and configurations for these five BSPs are located and dispersed within the Source Directory. - On the other hand, BSP layers for Chief River, Crown Bay, + On the other hand, BSP layers for Crown Bay, Crystal Forest, Emenlow, Fish River Island 2, Haswell, - Jasper Forest, N450, NUC DC3217IYE, - Romley, sys940x, Sugar Bay, and tlk exist in their own separate layers + Jasper Forest, NUC DC3217IYE, + Romley, Sugar Bay, and tlk exist in their own separate layers within the larger meta-intel layer. When you set up a layer for a new BSP, you should follow a standard layout. This layout is described in the @@ -672,7 +672,7 @@ Installing the Eclipse IDE - It is recommended that you have the Kepler 4.3 version of + It is recommended that you have the Kepler 4.3.2 version of the Eclipse IDE installed on your development system. However, if you currently have the Juno 4.2 version installed and you do not want to upgrade the IDE, you can @@ -680,10 +680,10 @@ - If you do not have the Kepler 4.3 Eclipse IDE installed, you - can find the tarball at + If you do not have the Kepler 4.3.2 Eclipse IDE installed, + you can find the tarball at . - From that site, choose the Eclipse Standard 4.3 version + From that site, choose the Eclipse Standard 4.3.2 version particular to your development host. This version contains the Eclipse Platform, the Java Development Tools (JDT), and the Plug-in Development @@ -698,7 +698,7 @@ using the default name eclipse: $ cd ~ - $ tar -xzvf ~/Downloads/eclipse-standard-kepler-R-linux-gtk-x86_64.tar.gz + $ tar -xzvf ~/Downloads/eclipse-standard-kepler-SR2-linux-gtk-x86_64.tar.gz @@ -735,7 +735,7 @@ Expand the box next to "Mobile and Device Development" and select the following boxes: - C/C++ Remote Launch + C/C++ Remote Launch (Requires RSE Remote System Explorer) Remote System Explorer End-user Runtime Remote System Explorer User Actions Target Management Terminal @@ -744,7 +744,7 @@ Expand the box next to "Programming Languages" and select the - Autotools Support for CDT + C/C++ Autotools Support and C/C++ Development Tools boxes. Complete the installation and restart @@ -871,7 +871,8 @@ When the script finishes execution, it prompts you with instructions on how to run the build.sh script, which - is also in the scripts of + is also in the scripts + directory of the Git repository created earlier. Run the build.sh script @@ -896,7 +897,7 @@ Provide anything you want in the "Name" field. Click "Archive" and browse to the - ZIP file you built in step seven. + ZIP file you built in step eight. This ZIP file should not be "unzipped", and must be the *archive.zip file created by running the @@ -1016,7 +1017,7 @@ If you used the ADT Installer script and accepted the default installation directory, then the location is - /opt/poky/<release>. + /opt/poky/&DISTRO;. Additionally, when you use the ADT Installer script, the same location is used for the QEMU user-space tools and the NFS boot process. @@ -1031,7 +1032,9 @@ For information on how to install the toolchain and on how to extract and install the sysroot filesystem, see the - "Installing the ADT and Toolchains" section. + "Installing the ADT and Toolchains" + section in the Yocto Project Application + Developer's Guide. Select the Target Architecture: The target architecture is the type of hardware @@ -1059,7 +1062,7 @@ emulator, or you can choose to run your image on actual hardware. - QEMU: + QEMU: Select this option if you will be using the QEMU emulator. If you are using the emulator, you also need to @@ -1099,7 +1102,7 @@ configuration in the Sysroot Location: field. - External HW: + External HW: Select this option if you will be using actual hardware. @@ -1186,7 +1189,7 @@ individual project. By default, the Cross Compiler Options and Target Options for a project are inherited from settings you - provide using the Preferences Dialog as described + provided using the Preferences Dialog as described earlier in the "Configuring the Eclipse Yocto Plug-in" section. The Yocto Project Settings Dialog allows you to override @@ -1264,7 +1267,7 @@ Once the QEMU emulator is running the image, you can deploy - your application using the Eclipse IDE and use then use + your application using the Eclipse IDE and then use the emulator to perform debugging. Follow these steps to deploy the application. @@ -1349,7 +1352,7 @@ . You can also find more information on setting up and using this tool in the - "OProfile" + "oprofile" section of the Yocto Project Profiling and Tracing Manual. The oprofile-server is -- cgit v1.2.3-54-g00ecf