add arduino target in trace doc

boconwork-k37A · Oct 2, 2021 · 6a31e6e · 6a31e6e
1 parent c9adb1f
commit 6a31e6e
Showing 1 changed file with 7 additions and 2 deletions.
diff --git a/documentation/manual/traces.tex b/documentation/manual/traces.tex
@@ -94,6 +94,7 @@ \subsection{Target specific part}
 \subsubsection{Posix target}
 The posix target is the simplest one, as there is no problem to get back the trace. The trace can be saved in \texttt{json} mode only. The generated file is always called \texttt{trace.json}.
 
+
 \subsubsection{MSP430 target}
 For the MSP430 format, different methods can be implemented to retrieve the trace:
 \begin{description}
@@ -103,9 +104,9 @@ \subsubsection{MSP430 target}
 	\item[\texttt{SIZE}] the size of the dump in bytes;
 	\item[\texttt{ADDRESS}] the base address.
 \end{description} It should not be used if the throughput is too high!
-(not implemented yet).
+(\emph{not implemented yet}).
 
-	\item[\texttt{SD}] the embedded SD card (not implemented yet).
+	\item[\texttt{SD}] the embedded SD card (\emph{not implemented yet}).
 \end{description}
 
 In all cases, a trace event should take as low place as possible, and is stored in binary format (see section \ref{sec:traceBinFormat}).
@@ -129,6 +130,10 @@ \subsubsection{STM32 target}
 
 \end{lstlisting}
 
+\subsubsection{Arduino Uno target}
+On Arduino UNO, the Serial target is implemented (using the arduino Serial driver).
+There is a full example in \texttt{examples/avr/arduinoUno/trace}
+
 \section{Using the tracing subsystem}
 
 The trace are generated by trampoline on the target. We then need to retrieve the information on the host system.