1 files changed, 192 insertions, 76 deletions

diff --git a/doc/book-enea-linux-user-guide/doc/using_enea_linux.xml b/doc/book-enea-linux-user-guide/doc/using_enea_linux.xml
index aba7c1d..db04d8f 100644
--- a/doc/book-enea-linux-user-guide/doc/using_enea_linux.xml
+++ b/doc/book-enea-linux-user-guide/doc/using_enea_linux.xml
@@ -5,9 +5,8 @@
   <section id="build_enealinux">
     <title>Building Enea Linux</title>
 
-    <para>Enea Linux is made available as sources, this allows for of building
-    various Enea Linux artifacts and is detailed in the following
-    sections:</para>
+    <para>Enea Linux is made available as sources, allowing for the building of 
+      various Enea Linux artifacts, detailed in the following sections.</para>
 
     <section id="build_images">
       <title>Building Real-Time images</title>
@@ -25,7 +24,7 @@
         </step>
 
         <step>
-          <para>Clone Enea Linux sources using Repo tool. Please refer to
+          <para>Clone Enea Linux sources using the Repo tool. Please refer to
           <xref linkend="getting_sources" /> for more details.</para>
 
           <programlisting>$ mkdir enea-linux
@@ -42,7 +41,7 @@ $ repo sync</programlisting>
 $ TEMPLATECONF=meta-el-rt/conf/template.&lt;machine&gt; \
 . ./oe-init-build-env &lt;build_dir&gt;</programlisting>
 
-          <para>Sourcing the build environment is needed everytime a new shell
+          <para>Sourcing the build environment is needed every time a new shell
           is used. However, sourcing using the <literal>TEMPLATECONF</literal>
           is only needed the first time around. After the first time, it is
           enough to source the build directory created before.</para>
@@ -77,8 +76,8 @@ $ cd &lt;build_dir&gt;/tmp/deploy/images/&lt;target&gt;/  # Here are the build b
           booting a physical target, according to how the build environment
           was set up before running bitbake.</para>
 
-          <para>Depending on the number of processors and cores, the amount or
-          RAM, the speed of your Internet connection and other factors, the
+          <para>Depending on the number of processors and cores, the amount of
+          RAM, the speed of your internet connection and other factors, the
           build process can take several hours the first time you run it.
           Subsequent builds run much faster since parts of the build are
           cached.</para>
@@ -86,8 +85,8 @@ $ cd &lt;build_dir&gt;/tmp/deploy/images/&lt;target&gt;/  # Here are the build b
           <note>
             <para>Make sure that the user running the build has access to the
             Git repositories on git.enea.com. The build process fetches
-            information from git.enea.com so the user running the build shall
-            have the ssh key properly configured. Please refer to <xref
+            information from git.enea.com so the user running the build needs to 
+              have the ssh key properly configured. Please refer to <xref
             linkend="getting_sources" /> for more details on how to get access
             to Enea Linux sources.</para>
           </note>
@@ -99,11 +98,11 @@ $ cd &lt;build_dir&gt;/tmp/deploy/images/&lt;target&gt;/  # Here are the build b
       <title>Building the SDK</title>
 
       <para>If you want to rebuild a cross-compilation toolchain to be used by
-      in application development, use the following steps:</para>
+      in application development, do the following:</para>
 
       <procedure>
         <step>
-          <para>Clone Enea Linux sources using Repo tool. Please refer to
+          <para>Clone Enea Linux sources using the Repo tool. Please refer to
           <xref linkend="getting_sources" /> for more details on how to do
           this.</para>
 
@@ -130,8 +129,8 @@ $ TEMPLATECONF=meta-el-rt/conf/template.&lt;machine&gt; \
             <para>The build directory may reside on an NFS mount, but the
             <literal>TMPDIR</literal>
             (<literal>&lt;build_dir&gt;/tmp</literal>) may not. Either build
-            all on a local disk, or update TMPDIR in conf/local.conf to point
-            to a local disk.</para>
+            all on a local disk, or update <literal>TMPDIR</literal> in 
+              <literal>conf/local.conf</literal> to point to a local disk.</para>
           </note>
         </step>
 
@@ -148,13 +147,13 @@ $ cd &lt;build_dir&gt;/tmp/deploy/sdk/  # Here is the SDK installer script</prog
             long, you need to move your build to obtain a shorter path.</para>
           </note>
 
-          <para>Generated SDK installer script is by default saved in
+          <para>The generated SDK installer script is by default saved in
           <literal>&lt;build_dir&gt;/tmp/deploy/sdk</literal>, where
           <literal>&lt;build_dir&gt;</literal> by default is the current
           working directory.</para>
 
-          <para>Depending on the number of processors and cores, the amount or
-          RAM, the speed of your Internet connection and other factors, the
+          <para>Depending on the number of processors and cores, the amount of
+          RAM, the speed of your internet connection and other factors, the
           build process can take several hours the first time you run it.
           Subsequent builds run much faster since parts of the build are
           cached.</para>
@@ -174,13 +173,13 @@ $ cd &lt;build_dir&gt;/tmp/deploy/sdk/  # Here is the SDK installer script</prog
     the artifacts availalbe, you may proceed to booting Enea Linux on
     target.</para>
 
-    <para>Enea Linux supports multiple booting methods so those will be
+    <para>Enea Linux supports multiple booting methods which will be
     described in the following sections.</para>
 
     <section id="enea-linux-x86-pxe">
       <title>Booting via PXE</title>
 
-      <para>Below you find an example of how to boot Enea Linux in a target
+      <para>Below is an example of how to boot Enea Linux on a target
       supporting PXE. The PXE boot is handled by the target BIOS.</para>
 
       <para>This requires the setup of DHCP, TFTP and NFS servers on the host.
@@ -194,31 +193,31 @@ $ cd &lt;build_dir&gt;/tmp/deploy/sdk/  # Here is the SDK installer script</prog
 
       <itemizedlist spacing="compact">
         <listitem>
-          <para>Host name</para>
+          <para>Host name.</para>
         </listitem>
 
         <listitem>
           <para>MAC hardware ethernet address (also available in the TFTP
-          configuration)</para>
+          configuration).</para>
         </listitem>
 
         <listitem>
-          <para>IP address, (assuming a fixed IP address is used)</para>
+          <para>IP address (assuming a fixed IP address is used).</para>
         </listitem>
 
         <listitem>
           <para>The TFTP server shall be defined as
-          <literal>next-server</literal></para>
+          <literal>next-server</literal>.</para>
         </listitem>
 
         <listitem>
           <para>The relative path in the TFTP server to the PXE file
-          <filename><literal>pxelinux.0</literal></filename></para>
+          <filename>pxelinux.0</filename>.</para>
         </listitem>
 
         <listitem>
           <para>The NFS server IP address and the path to the rootfs on the
-          NFS server, defined as <literal>option root-path</literal></para>
+          NFS server, defined as <literal>option root-path</literal>.</para>
         </listitem>
       </itemizedlist>
 
@@ -232,8 +231,8 @@ $ cd &lt;build_dir&gt;/tmp/deploy/sdk/  # Here is the SDK installer script</prog
     option root-path  "192.168.2.20:/export/intel-corei7-64_rootfs";
 }</programlisting>
 
-      <para>For the TFTP server, the TFTP path to the target's pxelinux.0 file
-      is given in the DHCP Configuration. Examples of files included in the
+      <para>For the TFTP server, the TFTP path to the target's <filename>pxelinux.0</filename>
+        file is given in the DHCP Configuration. Examples of files included in the
       TFTP subdirectory indicated by the DHCP configuration are:</para>
 
       <programlisting>pxelinux.0
@@ -311,6 +310,111 @@ label device01
       during BIOS power up tests. Look up the manufacturer's documentation for
       your board model to find the appropriate key.</para>
     </section>
+
+    <section id="boot_from_ram">
+      <title>Boot from RAM</title>
+
+      <para>This example requires that a TFTP server is set up at IP address
+      <literal>&lt;tftp_server_ip&gt;</literal>, and that the server stores
+      the Enea Linux image files, kernel image, device tree blob and root
+      filesystem, in <literal>/tftpboot/&lt;download_directory&gt;.</literal>
+      Please refer to <xref linkend="prebuiltprereq" /> for more details on
+      how to install and configure the TFTP server.</para>
+
+      <para>Once you have that in place, run the following commands on the
+      target:</para>
+
+      <programlisting>## set tftp server IP
+U-Boot&gt; setenv serverip &lt;tftp_server_ip&gt;
+
+## tftp the image files on the target machine
+U-Boot&gt; tftpboot 0x01000000 Image  
+U-Boot&gt; tftpboot 0x02000000 Image-bcm2837-rpi-3-b.dtb 
+U-Boot&gt; tftpboot 0x03000000 enea-image-standard-raspberrypi3-64.ext2.gz.u-boot
+
+## add any other bootargs values if necessary 
+U-Boot&gt; setenv bootargs "8250.nr_uarts=1 root=/dev/ram rw ramdisk_size=500000 ip=dhcp \
+console=ttyS0,115200"
+
+## Start boot sequence
+U-Boot&gt; booti 0x01000000 0x03000000 0x02000000</programlisting>
+    </section>
+
+    <section id="boot_from_sd">
+      <title>Boot from SD card</title>
+
+      <para>Copy the
+      <filename>enea-image-standard-raspberrypi3-64.rpi-sdimg</filename> image
+      to the SD card using the Linux dd tool or Win32DiskImager in Windows,
+      and insert it into the RPi. The Raspberry Pi will not start without a
+      properly formatted SD Card, containing the bootloader, kernel image and
+      rootfs.</para>
+
+      <para>Below you can find two methods of how to format an SD Card:</para>
+
+      <itemizedlist>
+        <listitem>
+          <para><emphasis role="bold">Format and copy images to the SD card
+          using the Linux dd command line</emphasis></para>
+
+          <para>The <command>dd</command> command copies a file, converting
+          the format of the data in the process, according to the operands
+          specified:</para>
+
+          <programlisting>sudo dd bs=4M if=enea-image-standard-sdk-raspberrypi3-64.rpi-sdimg of=/dev/sdg</programlisting>
+
+          <note>
+            <para>Use <command>dd</command> cautiously - improper usage or
+            entering the wrong values could inadvertently wipe, destroy, or
+            overwrite the data on your hard drive.</para>
+          </note>
+        </listitem>
+
+        <listitem>
+          <para><emphasis role="bold">Format the SD card using the
+          Win32DiskImager program</emphasis></para>
+
+          <orderedlist>
+            <listitem>
+              <para>Download and unzip <ulink
+              url="https://sourceforge.net/projects/win32diskimager/">Win32DiskImager</ulink>.</para>
+            </listitem>
+
+            <listitem>
+              <para>Run <filename>Win32DiskImager.exe</filename>.</para>
+            </listitem>
+
+            <listitem>
+              <para>Select the drive of your SD card.</para>
+            </listitem>
+
+            <listitem>
+              <para>Select the image
+              <filename>enea-image-standard-raspberrypi3-64.rpi-sdimg</filename>.</para>
+            </listitem>
+
+            <listitem>
+              <para>Click "Write" and wait for the write to complete.</para>
+            </listitem>
+
+            <listitem>
+              <para>Exit the imager and eject the SD Card.</para>
+            </listitem>
+
+            <listitem>
+              <para>Plug the card into your Raspberry Pi.</para>
+            </listitem>
+          </orderedlist>
+
+          <note>
+            <para>Be careful to select the correct drive. If you choose the
+            wrong one you may destroy your HDD data. If you are using an SD
+            Card slot and can't see the drive in the Win32DiskImager window,
+            try using an affordable external adapter in a USB slot.</para>
+          </note>
+        </listitem>
+      </itemizedlist>
+    </section>
   </section>
 
   <section id="custom_enealinux">
@@ -700,26 +804,26 @@ $ ./enea-*-toolchain-&lt;version&gt;.sh</programlisting>
     Project Mega Manual</ulink>. If needed replace the Yocto version in the
     link.</para>
 
-    <section id="apt_pktmgmt">
-      <title>APT Package Management (DEB Packages)</title>
+    <section id="rpm_pktmgmt">
+      <title>RPM Package Management (RPM Packages)</title>
 
-      <para>Enea Linux provides DEB packages on <ulink
+<!--      <para>Enea Linux provides RPM packages on <ulink
       url="http://linux.enea.com/EneaLinux8.0/">linux.enea.com</ulink> site,
       in directory
-      <literal><literal>&lt;release&gt;/&lt;target&gt;/deb</literal>/</literal>.</para>
+      <literal><literal>&lt;release&gt;/&lt;target&gt;/rpm</literal>/</literal>.</para>
+-->
+      <para>The application for performing runtime package management of RPM
+      packages on the target is called <filename>rpm</filename>.</para>
 
-      <para>The application for performing runtime package management of DEB
-      packages on the target is called <filename>apt-get</filename>.</para>
-
-      <para>Use the <literal>apt-get</literal> command to install, upgrade, or
-      remove packages. Before using any apt-get options that require network
+      <para>Use the <literal>rpm</literal> command to install, upgrade, or
+      remove packages. Before using any rpm options that require network
       access, please check that the network is configured and working
       properly.</para>
 
-      <para>The <literal>apt-get</literal> command is by default included in
+      <para>The <literal>rpm</literal> command is by default included in
       Enea Linux images.</para>
 
-      <section id="apt_config">
+      <!--<section id="apt_config">
         <title>Configuring</title>
 
         <para>APT relies on the concept of repositories in order to find
@@ -735,73 +839,85 @@ $ ./enea-*-toolchain-&lt;version&gt;.sh</programlisting>
 # echo "deb [trusted=yes]  http://server-address/path/to/the/package/directory ./" | \
 tee -a /etc/apt/sources.list.d/repos.list</programlisting>
 
-        <para>Run <literal>apt-get update</literal> to fetch information from
+        <para>Run <literal>createrepo --><!--update path_to_repo</literal> to fetch information from
         the new repository:</para>
 
-        <programlisting># apt-get update</programlisting>
+        <programlisting># createrepo --><!--update repo</programlisting>
+      </section>-->
+
+      <section id="rpm_preparation">
+        <title>Preparation</title>
+
+        <para>RPM packages need to first be downloaded on target. 
+        <programlisting># wget https://rpmfind.net/linux/fedora/linux/development/rawhide/Everything/
+aarch64/os/Packages/v/vim-common-8.1.2120-1.fc32.aarch64.rpm</programlisting>
+        They can be copied either from public maintained repositories or from locally maintained collections of useful RPMs. 
+        <programlisting># wget http://linux.enea.com/RPM/aarch64/vim-common-7.4.481-r0.0.aarch64.rpm</programlisting>
+        </para>
+
+        <para>
+        RPM is also identifying and checking for package dependencies. It warns if the package can not be installed correctly and lists what needs to be done.
+        </para>
+
       </section>
 
-      <section id="apt_install">
+      <section id="rpm_install">
         <title>Installing</title>
-
-        <para>DEB packages typically have file names like
-        foo-1.0.1-r0.0_arm64.deb The file name includes the package name
+     
+        <para>RPM packages typically have file names like
+        foo-1.0.1-r0.0_arm64.rpm The file name includes the package name
         (foo), version (1.0.1), revison (r0.0), and architecture (arm64). To
         install a package, log in as root and type the following command at a
         shell prompt:</para>
 
-        <programlisting># apt-get install foo</programlisting>
+        <programlisting># rpm -i vim-common-8.1.1017-r0.0.aarch64.rpm
+user.notice [RPM][351]: Transaction ID 5d836e00 started
+user.notice [RPM][351]: install vim-common-8.1.1017-r0.0.aarch64: success
+user.notice [RPM][351]: install vim-common-8.1.1017-r0.0.aarch64: success
+user.notice [RPM][351]: Transaction ID 5d836e00 finished: 0</programlisting>
 
-        <para>The <literal>apt-get install</literal> command will install one
-        or more packages in the system.</para>
       </section>
 
-      <section id="apt_upgrade">
+      <section id="rpm_upgrade">
         <title>Upgrading</title>
 
-        <para>The <literal>apt-get upgrade</literal> command will upgrade one
-        or more packages which are currently installed in the system. If no
-        packages are given, all installed packages will be checked.</para>
-
-        <programlisting># apt-get upgrade foo</programlisting>
+        <para>The <literal>rpm -U</literal> command will upgrade one
+        or more packages which are currently installed in the system.
+        </para>
+
+        <programlisting># rpm -U vim-common-8.1.1518-r0.0.aarch64.rpm
+user.notice [RPM][346]: Transaction ID 5d836d54 started
+user.notice [RPM][346]: erase vim-common-8.1.1017-r0.0.aarch64: success
+user.notice [RPM][346]: install vim-common-8.1.1518-r0.0.aarch64: success
+user.notice [RPM][346]: erase vim-common-8.1.1017-r0.0.aarch64: success
+user.notice [RPM][346]: install vim-common-8.1.1518-r0.0.aarch64: success
+user.notice [RPM][346]: Transaction ID 5d836d54 finished: 0</programlisting>
       </section>
 
-      <section id="apt_rm">
+      <section id="rpm_rm">
         <title>Removing</title>
 
-        <para>The <literal>apt-get remove</literal> command will remove one or
-        more packages which are currently installed in the system.
+        <para>The <literal>rpm -e</literal> command will remove the
+        package which is currently installed in the system.
         Example:</para>
 
-        <programlisting># apt-get remove ptest-runner
-Reading package lists... Done
-Building dependency tree
-Reading state information... Done
-The following packages were automatically installed and are no longer required:
-  libc6-dbg libc6-dev libc6-extra-nss libc6-thread-db libcidn1
-  linux-libc-headers-dev
-Use 'apt autoremove' to remove them.
-The following packages will be REMOVED:
-  ptest-runner
-0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
-After this operation, 0 B of additional disk space will be used.
-Do you want to continue? [Y/n] y
-(Reading database ... 5766 files and directories currently installed.)
-Removing ptest-runner (2.0.2+git0+6d2872116c-r0.0) ...
+        <programlisting># rpm -e vim-common
+user.notice [RPM][350]: Transaction ID 5d836dc9 started
+user.notice [RPM][350]: erase vim-common-8.1.1518-r0.0.aarch64: success
+user.notice [RPM][350]: erase vim-common-8.1.1518-r0.0.aarch64: success
+user.notice [RPM][350]: Transaction ID 5d836dc9 finished: 0
 </programlisting>
       </section>
 
-      <section id="pm_searching">
+      <section id="rpm_searching">
         <title>Searching</title>
 
-        <para>The <literal>apt-cache search</literal> allows searching for the
+        <para>The <literal>rpm -q</literal> allows searching for the
         given expressions in the name, summary and description of known
         packages. Example:</para>
 
-        <programlisting># apt-cache search ptest-runner
-ptest-runner - A C program to run all installed ptests
-ptest-runner-dbg - A C program to run all installed ptests - Debugging files
-ptest-runner-dev - A C program to run all installed ptests - Development files</programlisting>
+        <programlisting># rpm -q vim-common
+vim-common-8.1.1017-r0.0.aarch64</programlisting>
       </section>
     </section>
   </section>