[bootlin/training-materials updates] master: labs/sysdev-application-development-and-debugging: minor improvements (94f36bba)

[Michael Opdenacker]

Repository : https://github.com/bootlin/training-materials
On branch  : master
Link       : https://github.com/bootlin/training-materials/commit/94f36bba519d28320cc3918a8c991ee6eedda61c

>---------------------------------------------------------------

commit 94f36bba519d28320cc3918a8c991ee6eedda61c
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date:   Mon Nov 28 18:03:05 2022 +0100

    labs/sysdev-application-development-and-debugging: minor improvements
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>


>---------------------------------------------------------------

94f36bba519d28320cc3918a8c991ee6eedda61c
 .../sysdev-application-development-and-debugging.tex       | 14 ++++++++++----
 1 file changed, 10 insertions(+), 4 deletions(-)

diff --git a/labs/sysdev-application-development-and-debugging/sysdev-application-development-and-debugging.tex b/labs/sysdev-application-development-and-debugging/sysdev-application-development-and-debugging.tex
index 74420611..54194652 100644
--- a/labs/sysdev-application-development-and-debugging/sysdev-application-development-and-debugging.tex
+++ b/labs/sysdev-application-development-and-debugging/sysdev-application-development-and-debugging.tex
@@ -242,7 +242,7 @@ simple:
 
 \begin{itemize}
   \item If you don't have an SSH key yet (look at \code{~/.ssh/},
-	generate one with the \code{ssh-keygen} command.
+	generate a password-less one with the \code{ssh-keygen} command.
 	By defaults, this creates two files in \code{~/.ssh/}:
 	\code{id_rsa} (private key) and \code{id_rsa.pub} (public key).
   \item Then create the \code{/root/.ssh} directory {\bf on the target}
@@ -262,6 +262,12 @@ Then, you can test that SSH works without a password:
 ssh root at 192.168.0.100
 \end{bashinput}
 
+If you face trouble, you can check the Dropbear logs on the target:
+
+\begin{bashinput}
+journalctl -ju dropbear
+\end{bashinput}
+
 \subsection{Compiling and debugging the program from VS Code}
 
 The \code{appdev} directory already contains a \code{prep-debug.sh}
@@ -283,7 +289,7 @@ Here are these files:
 	 target IP address if necessary.
 \end{itemize}
 
-First, from the \code{appdev} directory, start VS Code:
+First, start VS Code:
 
 \begin{bashinput}
 $ code
@@ -296,7 +302,7 @@ The first thing to do is to make sure the \code{C/C++} extension from Microsoft
 (\code{ms-vscode.cpptools}) is installed. Do this using the
 \code{Extensions} vertical tab:
 
-\includegraphics[width=2cm]{labs/sysdev-application-development-and-debugging/vscode-extensions-tab.png}
+\includegraphics[width=4cm]{labs/sysdev-application-development-and-debugging/vscode-extensions-tab.png}
 
 Then click on the \code{nunchuk-mpd-client.c} file in the left
 column to open it in VS Code.
@@ -311,7 +317,7 @@ Last but not least, you can start debugging the program by clicking on
 the \code{Run and Debug} tab, and then on the \code{gdb (Launch)} at the
 top:
 
-\includegraphics[width=2cm]{labs/sysdev-application-development-and-debugging/vscode-run-debug-tab.png}
+\includegraphics[width=4cm]{labs/sysdev-application-development-and-debugging/vscode-run-debug-tab.png}
 
 In the debug console, you should see that debugging has started. The
 bottom line of the interface should turn orange too: