1 \documentclass[a4paper, 11pt]{article}
11 \title{Using STM32 discovery kits with open source tools}
12 \author{STLINK development team}
19 \addtocontents{toc}{\protect\setcounter{tocdepth}{1}}
26 This guide details the use of STMicroelectronics STM32 discovery kits in
27 an opensource environment.
32 \section{Installing a GNU toolchain}
34 Any toolchain supporting the cortex m3 should do. You can find the necessary
35 to install such a toolchain here:\\
37 \begin{lstlisting}[frame=tb]
38 https://github.com/esden/summon-arm-toolchain
43 Details for the installation are provided in the topmost README file.
44 This documentation assumes the toolchains is installed in a \$TOOLCHAIN\_PATH.
49 \section{Installing STLINK}
51 STLINK is an opensource software to program and debug the discovery kits. Those
52 kits have an onboard chip that translates USB commands sent by the host PC into
53 JTAG commands. This chip is called STLINK, which is confusing since the software
54 has the same name. It comes into 2 versions (STLINK v1 and v2). From a software
55 point of view, those versions differ only in the transport layer used to communicate
56 (v1 uses SCSI passthru commands, while v2 uses raw USB).
59 Before continuing, the following dependencies must be met:
62 \item libsgutils2 (optionnal)
66 STLINK should run on any system meeting the above constraints.
69 The STLINK software source code is retrieved using:\\
71 \begin{lstlisting}[frame=tb]
72 $> git clone https://github.com/texane/stlink stlink.git
77 Everything can be built from the top directory:\\
79 \begin{lstlisting}[frame=tb]
81 $> make CONFIG_USE_LIBSG=0
86 \item a communication library (stlink.git/libstlink.a),
87 \item a GDB server (stlink.git/gdbserver/st-util),
88 \item a flash manipulation tool (stlink.git/flash/flash).
94 \section{Building and running a program}
95 A simple LED blinking example is provided in the example directory. It is built using:\\
97 \begin{lstlisting}[frame=tb]
98 # update the make option accordingly to your architecture
99 cd stlink.git/example/blink ;
100 PATH=$TOOLCHAIN_PATH/bin:$PATH make
103 This builds three files, one for each of the Discovery boards currently
107 A GDB server must be started to interact with the STM32. Depending on the discovery kit you
108 are using, you must run one of the 2 commands:\\
110 \begin{lstlisting}[frame=tb]
111 # STM32VL discovery kit (onboard ST-link)
112 $> sudo ./st-util --stlinkv1 [-d /dev/sg2]
114 # STM32L or STM32F4 discovery kit (onboard ST-link/V2)
117 # Full help for other options (listen port, version)
123 Then, GDB can be used to interact with the kit:\\
125 \begin{lstlisting}[frame=tb]
126 $> $TOOLCHAIN_PATH/bin/arm-none-eabi-gdb
131 From GDB, connect to the server using:\\
133 \begin{lstlisting}[frame=tb]
134 $> target extended localhost:4242
139 By default, the program was linked such that the base address is 0x20000000. From the architecture
140 memory map, GDB knows this address belongs to SRAM. To load the program in SRAM, simply use:\\
142 \begin{lstlisting}[frame=tb]
148 GDB automatically set the PC register to the correct value, 0x20000000 in this case. Then, you
149 can run the program using:\\
151 \begin{lstlisting}[frame=tb]
157 The board BLUE and GREEN leds should be blinking (those leds are near the user and reset buttons).
161 \section{Reading and writing to flash}
163 Flash memory reading and writing is done by a separate tool. A binary running in flash is assumed to
164 be linked against address 0x8000000. The flash tool is then used as shown below:\\
166 \begin{lstlisting}[frame=tb]
167 # change to the flash tool directory
168 $> cd stlink.git/flash ;
170 # stlinkv1 command to read 4096 from flash into out.bin
171 $> ./flash read /dev/sg2 out.bin 0x8000000 4096
174 $> ./flash read out.bin 0x8000000 4096
176 # stlinkv1 command to write the file in.bin into flash
177 $> ./flash write /dev/sg2 in.bin 0x8000000
180 $> ./flash write in.bin 0x8000000
188 \subsection{Disassembling THUMB code in GDB}
190 By default, the disassemble command in GDB operates in ARM mode. The programs running on CORTEX-M3
191 are compiled in THUMB mode. To correctly disassemble them under GDB, uses an odd address. For instance,
192 if you want to disassemble the code at 0x20000000, use:\\
194 \begin{lstlisting}[frame=tb]
195 $> disassemble 0x20000001
200 \subsection{libstm32l\_discovery}
202 The repository includes the STM32L discovery library source code from ST original firmware packages,
205 \begin{lstlisting}[frame=tb]
206 http://www.st.com/internet/evalboard/product/250990.jsp#FIRMWARE
213 \begin{lstlisting}[frame=tb]
214 $> cd stlink.git/example/libstm32l_discovery/build
220 An example using the library can be built using:\\
222 \begin{lstlisting}[frame=tb]
223 $> cd stlink.git/example/lcd
228 \subsection{STM32VL support}
230 It seems support for STM32VL is quite broken. If it does not work, try build STLINK using libsg:
232 \begin{lstlisting}[frame=tb]
234 $> make CONFIG_USE_LIBSG=1
242 \item http://www.st.com/internet/mcu/product/248823.jsp\\
243 documentation related to the STM32L mcu
244 \item http://www.st.com/internet/evalboard/product/250990.jsp\\
245 documentation related to the STM32L discovery kit