changed encoding to "ISO-8859-1".

Replaced enea-linux-gdb with aarch64-enea-linux-gdb

Signed-off-by: Sona Sarmadi <sona.sarmadi@enea.com>

4 files changed, 17 insertions, 16 deletions

diff --git a/doc/book-enea-nfv-access-guide/doc/eltf_params_updated.xml b/doc/book-enea-nfv-access-guide/doc/eltf_params_updated.xml
index 4278d78..a246acd 100644
--- a/doc/book-enea-nfv-access-guide/doc/eltf_params_updated.xml
+++ b/doc/book-enea-nfv-access-guide/doc/eltf_params_updated.xml
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="UTF-8"?>
+<?xml version="1.0" encoding="ISO-8859-1"?>
 <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
 <section id="eltf_created_params">
@@ -162,4 +162,4 @@ repo sync</programlisting></para>
         </informaltable></para>
     </section>
   </section>
-</section>
\ No newline at end of file
+</section>
diff --git a/doc/book-enea-nfv-access-guide/doc/getting_started.xml b/doc/book-enea-nfv-access-guide/doc/getting_started.xml
index 5972a90..65888bf 100644
--- a/doc/book-enea-nfv-access-guide/doc/getting_started.xml
+++ b/doc/book-enea-nfv-access-guide/doc/getting_started.xml
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="UTF-8"?>
+<?xml version="1.0" encoding="ISO-8859-1"?>
 <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
 <chapter id="plat-release-content">
@@ -342,4 +342,4 @@ ssh root@&lt;target_ip&gt; "cd /mnt/sda6; tar -zxf -"</programlisting>
       </note>
     </section>
   </section>
-</chapter>
\ No newline at end of file
+</chapter>
diff --git a/doc/book-enea-nfv-access-guide/doc/overview.xml b/doc/book-enea-nfv-access-guide/doc/overview.xml
index 2ab3a9c..e19d4c4 100644
--- a/doc/book-enea-nfv-access-guide/doc/overview.xml
+++ b/doc/book-enea-nfv-access-guide/doc/overview.xml
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="UTF-8"?>
+<?xml version="1.0" encoding="ISO-8859-1"?>
 <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
 <chapter id="overview">
@@ -145,4 +145,4 @@
       </listitem>
     </itemizedlist>
   </section>
-</chapter>
\ No newline at end of file
+</chapter>
diff --git a/doc/book-enea-nfv-access-guide/doc/using_nfv_access_sdks.xml b/doc/book-enea-nfv-access-guide/doc/using_nfv_access_sdks.xml
index 9995594..116106e 100644
--- a/doc/book-enea-nfv-access-guide/doc/using_nfv_access_sdks.xml
+++ b/doc/book-enea-nfv-access-guide/doc/using_nfv_access_sdks.xml
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="UTF-8"?>
+<?xml version="1.0" encoding="ISO-8859-1"?>
 <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
 <chapter id="workflow">
@@ -292,10 +292,10 @@ MODULE_LICENSE("GPL");</programlisting>
   <section id="crossdebugging">
     <title>Cross-Debugging on Enea NFV Access</title>
 
-    <para>The cross-debugger (<literal>enea-linux-gdb</literal>) is created
-    when installing the SDK on the development machine. It is helpful for
-    debugging both the kernel and user-applications. In order to perform this
-    task, we need the following tools to be available on the target
+    <para>The cross-debugger (<literal>aarch64-enea-linux-gdb</literal>) is
+    created when installing the SDK on the development machine. It is helpful
+    for debugging both the kernel and user-applications. In order to perform
+    this task, we need the following tools to be available on the target
     machine:</para>
 
     <itemizedlist>
@@ -325,7 +325,7 @@ MODULE_LICENSE("GPL");</programlisting>
       with GDB and the name of your program:<programlisting># gdbserver :&lt;port_no&gt; /tmp/helloworld</programlisting>The
       target will now be listening on the port given as a parameter to the
       gdbserver. On the development machine, from the
-      <literal>&lt;sdkdir&gt;</literal>, start the cross-gdb:<programlisting>$ enea-linux-gdb &lt;path_to_the_program&gt;/helloworld</programlisting>Connect
+      <literal>&lt;sdkdir&gt;</literal>, start the cross-gdb:<programlisting>$ aarch64-enea-linux-gdb &lt;path_to_the_program&gt;/helloworld</programlisting>Connect
       the GDB to the target: <programlisting>(gdb) target remote &lt;target_ip_address&gt;:&lt;port_no&gt;</programlisting>Now
       remote debugging is started and the GDB commands are available to debug
       your program from the target machine.</para>
@@ -400,7 +400,7 @@ ip route add default via 192.168.122.1 dev enp0s2</programlisting></para>
 
         <listitem>
           <para>On the development machine, from the<filename>
-          &lt;sdkdir&gt;</filename>, start the cross-gdb:<programlisting>$ enea-linux-gdb &lt;path_to_the_program&gt;/helloworld</programlisting></para>
+          &lt;sdkdir&gt;</filename>, start the cross-gdb:<programlisting>$ aarch64-enea-linux-gdb &lt;path_to_the_program&gt;/helloworld</programlisting></para>
         </listitem>
 
         <listitem>
@@ -450,8 +450,9 @@ ip route add default via 192.168.122.1 dev enp0s2</programlisting></para>
           kernel image as a parameter. The image is located in
           <filename>&lt;sdkdir&gt;/sysroots/corei7-64-enea-linux/boot/</filename>
           and should be the same as the image found in the
-          <literal>/boot</literal> directory from the target.<programlisting>$ enea-linux-gdb /
-./sysroots/aarch64-enea-linux/boot/vmlinux-4.9.0-octeontx.sdk.6.1.0.p3.build.22-cavium-tiny</programlisting></para>
+          <literal>/boot</literal> directory from the target.<programlisting>$ aarch64-enea-linux-gdb /
+    ./sysroots/aarch64-enea-linux/boot/ \
+     vmlinux-4.9.0-octeontx.sdk.6.1.0.p3.build.22-cavium-tiny</programlisting></para>
         </listitem>
 
         <listitem>
@@ -465,4 +466,4 @@ ip route add default via 192.168.122.1 dev enp0s2</programlisting></para>
       application program.</para>
     </section>
   </section>
-</chapter>
\ No newline at end of file
+</chapter>