kits have an onboard chip that translates USB commands sent by the host PC into
JTAG commands. This chip is called STLINK, which is confusing since the software
has the same name. It comes into 2 versions (STLINK v1 and v2). From a software
-point of view, those version differ only in the transport layer used to communicate
+point of view, those versions differ only in the transport layer used to communicate
(v1 uses SCSI passthru commands, while v2 uses raw USB).
+
+\paragraph{}
+Before continuing, the following dependencies are required:
+\begin{itemize}
+\item libusb-1.0
+\item libsg2
+\end{itemize}
+
\paragraph{}
The STLINK software source code is retrieved using:\\
\begin{small}
The GDB server is called st-util and is built using:\\
\begin{small}
\begin{lstlisting}[frame=tb]
-$> cd stlink.git; make ;
+$> cd stlink.git;
+$> make ;
+$> cd gdbserver ;
+$> make ;
\end{lstlisting}
\end{small}
\end{small}
\paragraph{}
-A GDB server must be start to interact with the STM32.
-Depending on the discovery kit you are using, you must
-run one of the 2 commands:\\
+A GDB server must be start to interact with the STM32. Depending on the discovery kit you
+are using, you must run one of the 2 commands:\\
\begin{small}
\begin{lstlisting}[frame=tb]
# STM32VL discovery kit
\end{small}
\paragraph{}
-To load the program, use:\\
+By default, the program was linked such that the base address is 0x20000000. From the architecture
+memory map, GDB knows this address belongs to SRAM. To load the program in SRAM, simply use:\\
\begin{small}
\begin{lstlisting}[frame=tb]
$> load blink.elf
\end{small}
\paragraph{}
-Then, you can run the program using:\\
+GDB automatically set the PC register to the correct value, 0x20000000 in this case. Then, you
+can run the program using:\\
\begin{small}
\begin{lstlisting}[frame=tb]
-$> run
+$> continue
\end{lstlisting}
\end{small}
+\paragraph{}
+The board BLUE and GREEN leds should be blinking (those leds are near the user and reset buttons).
+
\newpage
\section{References}