1 files changed, 78 insertions, 36 deletions

diff --git a/doc/book-enea-linux-user-guide/doc/using_eclipse.xml b/doc/book-enea-linux-user-guide/doc/using_eclipse.xml
index 878b46b..f493d43 100644
--- a/doc/book-enea-linux-user-guide/doc/using_eclipse.xml
+++ b/doc/book-enea-linux-user-guide/doc/using_eclipse.xml
@@ -23,10 +23,17 @@
 
       <listitem>
         <para>In <emphasis role="bold">step 3</emphasis> from chapter
-        4.3.2.1.2. the correct option in the drop-down menu should look like:
+        4.3.2.1.2, the correct option in the drop-down menu should look like:
         <emphasis>Oxygen -
         http://download.eclipse.org/releases/oxygen</emphasis>.</para>
       </listitem>
+
+      <listitem>
+        <para>In <emphasis role="bold">step 5</emphasis> from chapter
+        4.3.2.1.2, under the category <emphasis role="bold">Mobile and Device
+        Development</emphasis>, select <emphasis role="bold">C/C++ GDB
+        Hardware Debugging</emphasis> as well.</para>
+      </listitem>
     </itemizedlist>
   </section>
 
@@ -36,21 +43,37 @@
     <para>Retrieve the archive containing the Yocto Plug-ins from the Enea
     Linux release location and save it on your local machine. The archive file
     has the following format:
-    <filename>org.yocto.sdk-&lt;release&gt;-&lt;date&gt;-archive.zip</filename>.
-    To install the Yocto Plugins in Eclipse, follow the instructions in <ulink
+    <filename>org.yocto.sdk-&lt;release&gt;-&lt;date&gt;-archive.zip</filename>.</para>
+
+    <para>To install the Yocto Plugins in Eclipse, follow the instructions in
+    <ulink
     url="http://www.yoctoproject.org/docs/2.3.2/sdk-manual/sdk-manual.html#adt-eclipse">chapter
     4.3.2.1.3.2</ulink>. of the Yocto Manual, starting with <emphasis
     role="bold">step 8</emphasis>. In <emphasis role="bold">step 12</emphasis>
     use the local archive that you downloaded previously.</para>
+
+    <para>To make sure that all required packages have been installed, go to
+    the menu <emphasis role="bold">Help &gt; Install New Software &gt; Eclipse
+    version</emphasis>, and select the version you use (e.g. Oxygen), to add
+    any missing packages. You can also check what packages are currently
+    installed by pressing the <emphasis role="bold">What is Already
+    Installed?</emphasis> link, as seen below.</para>
+
+    <mediaobject>
+      <imageobject>
+        <imagedata align="center" contentwidth="650"
+                   fileref="images/install_new_sw.svg" />
+      </imageobject>
+    </mediaobject>
   </section>
 
   <section id="eclipse_remote_connection">
     <title>Setting up a TCF Connection from Eclipse</title>
 
     <para>Eclipse supports several types of remote connections to reference
-    boards, among these is the TCF type of connection. Throughout this guide,
-    this information will be referenced as it is used by several
-    features.</para>
+    boards. Among these is the Target Communication Framework (TCF) type of
+    connection. This information will be referenced throughout this guide, as
+    it is used by several features.</para>
 
     <para><emphasis role="bold">How to set up a TCF connection to the target
     to be used later on</emphasis><remark>Should we add images to this
@@ -61,7 +84,7 @@
         <para>Make sure the <literal>tcf-agent</literal> is running on the
         target:</para>
 
-        <programlisting>aux | grep tcf-agent
+        <programlisting>ps aux | grep tcf-agent
 root 329 0.0 0.2 1864824 2600 ? Ssl 12:47 0:08 /usr/sbin/tcf-agent -d -L- -l0</programlisting>
       </listitem>
 
@@ -437,6 +460,12 @@ root 329 0.0 0.2 1864824 2600 ? Ssl 12:47 0:08 /usr/sbin/tcf-agent -d -L- -l0</p
 
           <itemizedlist>
             <listitem>
+              <para>Retrieve the debug sources from the target, and store them
+              in a dedicated folder on the local host. They are found in
+              <literal>/usr/src/debug</literal> in the target rootfs.</para>
+            </listitem>
+
+            <listitem>
               <para>Set a path mapping your debug configuration. In the
               <emphasis role="bold">Source</emphasis> tab, click <emphasis
               role="bold">Add</emphasis>, select <emphasis role="bold">Path
@@ -447,10 +476,9 @@ root 329 0.0 0.2 1864824 2600 ? Ssl 12:47 0:08 /usr/sbin/tcf-agent -d -L- -l0</p
                 <filename>/usr/src/debug</filename></member>
 
                 <member><emphasis role="bold">Local file system
-                path</emphasis>: <filename>(&lt;path to build
-                directory&gt;/tmp/work/&lt;target&gt;-enea-linux/&lt;image
-                name&gt;/&lt;version&gt;/rootfs/usr/src/debug)----------NEEDS
-                TO BE CONFIRMED</filename></member>
+                path</emphasis> (path to the debug sources retrieved from the
+                target):<filename>
+                &lt;path_to_chosen_folder&gt;/usr/src/debug</filename></member>
               </simplelist>
             </listitem>
 
@@ -579,11 +607,19 @@ root 329 0.0 0.2 1864824 2600 ? Ssl 12:47 0:08 /usr/sbin/tcf-agent -d -L- -l0</p
         them. The current thread filter in Eclipse is ineffective.</para>
       </note>
 
-      <para>Use the run/debug configuration to connect the Eclipse GDB client
-      to the remote target:</para>
+      <para><emphasis role="bold">Use the run/debug configuration to connect
+      the Eclipse GDB client to the remote target</emphasis>:</para>
 
       <orderedlist>
         <listitem>
+          <para>Go to <emphasis role="bold">Window &gt; Preferences &gt;
+          Run/Debug &gt; Launching &gt; Default Launchers</emphasis>. Under
+          <emphasis role="bold">C/C++ Attach to Applicaton &gt;
+          Debug</emphasis> select the checkbox <emphasis role="bold">GDB (DSF)
+          Attach to Process via TCF/TE Launcher</emphasis>.</para>
+        </listitem>
+
+        <listitem>
           <para>Select <emphasis role="bold">Run &gt; Debug Configurations...
           </emphasis> from the menu and choose the run/debug configuration
           from the instances under <literal>C/C++ Attach to
@@ -592,9 +628,15 @@ root 329 0.0 0.2 1864824 2600 ? Ssl 12:47 0:08 /usr/sbin/tcf-agent -d -L- -l0</p
         </listitem>
 
         <listitem>
-          <para>In the lower part of the dialog, make sure that <emphasis
-          role="bold">Using GDB (DSF) Attach to Process Launcher</emphasis> is
-          selected.</para>
+          <para>If you followed <emphasis role="bold">step 1</emphasis>, in
+          the lower part of the dialog you will see that <emphasis
+          role="bold">Using GDB (DSF) Attach to Process via TCF/TE
+          Launcher</emphasis> is selected. If not, redo <emphasis
+          role="bold">step 1</emphasis> or click the <emphasis
+          role="bold">Select Other...</emphasis> link, and use configuration
+          specific settings by selecting the checkbox <emphasis
+          role="bold">GDB (DSF) Attach to Process via TCF/TE
+          Launcher</emphasis>.</para>
         </listitem>
 
         <listitem>
@@ -679,7 +721,7 @@ root 329 0.0 0.2 1864824 2600 ? Ssl 12:47 0:08 /usr/sbin/tcf-agent -d -L- -l0</p
     </section>
 
     <section id="eclipse_postmortem">
-      <title>Using Postmortem Debugger</title>
+      <title>Using the Postmortem Debugger</title>
 
       <para>When a program crashes<indexterm>
           <primary>post-mortem debugging</primary>
@@ -721,8 +763,9 @@ root 329 0.0 0.2 1864824 2600 ? Ssl 12:47 0:08 /usr/sbin/tcf-agent -d -L- -l0</p
 
       <para>The next step is to specify the core pattern which defines the
       core dump file pattern name. The core pattern is defined in the
-      <literal>/proc/sys/kernel/core_pattern</literal>. The format of a core
-      pattern follows certain rules:</para>
+      <literal>/proc/sys/kernel/core_pattern</literal>.</para>
+
+      <para>The format of a core pattern follows certain rules:</para>
 
       <itemizedlist>
         <listitem>
@@ -774,15 +817,17 @@ root 329 0.0 0.2 1864824 2600 ? Ssl 12:47 0:08 /usr/sbin/tcf-agent -d -L- -l0</p
           <literal>core_uses_pid</literal> is set, and no
           <literal>core_pattern</literal> is defined.</para>
         </listitem>
-
-        <listitem>
-          <para>To make the core dump file name permanent across a reboot,
-          configure this choice in <filename>/etc/sysctl.conf</filename>. An
-          example:
-          <literal>kernel.core_pattern=&lt;suitable_directory&gt;/core.%e.%p.%h.%t</literal></para>
-        </listitem>
       </itemizedlist>
 
+      <para>Specify a core pattern by writing it to
+      <literal>/proc/sys/kernel/core_pattern</literal>. For example:
+      <programlisting><literal>echo "&lt;suitable_directory&gt;/core.%e.%p.%h.%t" &gt; /proc/sys/kernel/core_pattern</literal></programlisting></para>
+
+      <para>To make the core dump file name permanent across a reboot,
+      configure <filename>/etc/sysctl.conf</filename>. to reflect this choice,
+      by adding a line like in the following example:
+      <literal>kernel.core_pattern=&lt;suitable_directory&gt;/core.%e.%p.%h.%t</literal>.</para>
+
       <para>How to use the Eclipse post mortem debug configuration in order to
       view the call trace, for the core dump in the Eclipse GDB
       interface:</para>
@@ -851,11 +896,11 @@ root 329 0.0 0.2 1864824 2600 ? Ssl 12:47 0:08 /usr/sbin/tcf-agent -d -L- -l0</p
     <para>In this section you learn to set up Eclipse for KGDB<indexterm>
         <primary>KGDB</primary>
       </indexterm> kernel debugging over the serial port, with examples for
-    the <literal>p2020rdb</literal> target. This is only given as an example,
-    your Enea Linux distribution may contain other targets. The corresponding
-    instruction for debugging outside Eclipse is available in Debugging the
-    Linux Kernel (KGDB) from Command Line.<remark>LATER: Merge the two
-    instructions to shrink the amount of text; most of it is the
+    the <literal>raspberrypi3</literal> target. This is only given as an
+    example, your Enea Linux distribution may contain other targets. The
+    corresponding instruction for debugging outside Eclipse is available in
+    Debugging the Linux Kernel (KGDB) from Command Line.<remark>LATER: Merge
+    the two instructions to shrink the amount of text; most of it is the
     same.</remark></para>
 
     <para>How to set up Eclipse for KGDB kernel debugging over a serial
@@ -883,11 +928,8 @@ root 329 0.0 0.2 1864824 2600 ? Ssl 12:47 0:08 /usr/sbin/tcf-agent -d -L- -l0</p
 
         <para>If you are using the default kernel delivered with Enea Linux,
         you can find it in the rootfs under the <literal>/boot</literal>
-        folder, or in the SDK under
-        <filename>&lt;extsdkdir&gt;/tmp/sysroots/x86_64-linux/usr/bin/&lt;arch&gt;-enea-linux/&lt;arch&gt;-enea-linux-gdb-------------------------<remark>are
-        there supposed to be so many hyphens in this arch
-        name?</remark></filename>. If you build your own kernel using bitbake,
-        it should be available in your build folder. For example, located in:
+        folder. If you build your own kernel using bitbake, it should be
+        available in your build folder. Located in, for example:
         <filename><filename>tmp/work/raspberrypi3_64-enea-linux/linux-raspberrypi/1_4.9.59+gitAUTOINC+meta_machine-r0/image/boot/vmlinux-4.9.59</filename></filename></para>
       </listitem>