ARM Embedded Tutorial - Entry FPC and STM32: what changed

Revision 1 to 2. Removed lines have a minus sign; added lines have a plus sign.

Old	New		Line
1	1		# Introduction to STM32 and FPC
2	2
3	3		This tutorial was tested using 64 bit Linux Mint.
4	4
5	5		## Driver for ST-LINK V2
6	6
7	7		### Linux
8	8
9	9		Download the package as a zip with clone or download from <https://github.com/texane/stlink>
10	10
11	11		Follow the instructions at <https://github.com/texane/stlink/blob/master/doc/compiling.md>
12	12
13	13		The following packages must be installed:
14	14
15	15		- CMake (minimum v2.8.7)
16	16		- C compiler (gcc, clang, mingw)
17	17		- Libusb 1.0 (minimum v1.0.9)
18	18
19	19		``` bash
20	20		sudo apt-get install cmake
21	21		sudo apt-get install gcc
22	22		sudo apt-get install libusb-1.0-0.dev
23	23		// sudo apt-get install libusb-dev // ???
24	24		```
25	25
26	26		Compile and install stlink:
27	27
28	28		``` bash
29	29		$ make release
30	30		$ make debug
31	31
32	32		$ mkdir build # may already exist.
33	33		$ cd build
34	34		$ cmake -DCMAKE_BUILD_TYPE = Debug ..
35	35		$ make
36	36		```
37	37
38	38		To install in your home directory:
39	39
40	40		``` bash
41	41		$ cd build/release
42	42		$ make install DESTDIR=$HOME
43	43		```
44	44
45	45		To install for all users:
46	46
47	47		``` bash
48	48		$ cd build/release
49	49		$ sudo make install
50	50		```
51	51
52	52		Reboot or:
53	53
54	54		``` bash
55	55		$ sudo udevadm control --reload-rules
56	56		$ sudo udevadm trigger
57	57		```
58	58
59	59		Then there should be a device file /dev/stlinkv2_3 or similar.
60	60
61	61		Run the following as a test:
62	62
63	63		` st-util`
64	64
65	65		This should produce several lines of information, including how much SRAM the controller has. You can then cancel it with Ctrl+C.
66	66
67	67		If st-util aborts with the following error:
68	68
69	69		` st-util: error while loading shared libraries: libstlink.so.1: cannot open shared object file: No such file or directory`
70	70
71	71		This is probably the problem: <https://github.com/texane/stlink/issues/700> so run the following:
72	72
73	73		``` bash
74	74		$ sudo ldconfig
75	75		```
76	76
77	77		### Windows/macOS
78	78
79	79		` `[`https://github.com/texane/stlink/releases/tag/1.3.0`](https://github.com/texane/stlink/releases/tag/1.3.0)` (not tested) `
80	80
81	81		## Hardware connections
82	82
83	83		Connect the ST-LINK V2 to the STM32F103C as follows:
84	84
85	85		\| ST LINK V2 \| -\> \| STM32F103C \|
86	86		\|------------\|-----\|------------\|
87	87		\| SWDIO \| -\> \| SWO \|
88	88		\| GND \| -\> \| GND \|
89	89		\| SWCLK \| -\> \| SWCLK \|
90	90		\| 3.3V \| -\> \| 3.3V \|
91	91
92	92		## Set up Arduino IDE (optimal)
93	93
94	94		This is not absolutely necessary, but it has the advantage that you can look up how problems have been solved there, eg I²C access.
95	95
96	96		Note the following page (does not work with Sloeber (Eclipse for Arduino))
97	97
98	98		` `[`https://github.com/stm32duino/Arduino_Core_STM32`](https://github.com/stm32duino/Arduino_Core_STM32)` `
99	99
100	100		JSON link:
101	101
102	102		` `[`https://github.com/stm32duino/BoardManagerFiles/raw/master/STM32/package_stm_index.json`](https://github.com/stm32duino/BoardManagerFiles/raw/master/STM32/package_stm_index.json)` `
103	103
104	104		The following JSON also works with Sloeber. Insert this JSON link in the Arduino IDE under File \> Preferences:
105	105
106	106		` `[`http://dan.drown.org/stm32duino/package_STM32duino_index.json`](http://dan.drown.org/stm32duino/package_STM32duino_index.json)` (Version 2018.4.2 has been tested.) `
107	107
108	108		It is also best to activate the detailed output for compilation and upload. Then you can see any error uploading. Attention: Uploading is completed with the green bar which is displayed, even if an error occurred in the detailed report.
109	109
110	110		Install the following in the board management:
111	111
112	112		` stm32duino/STM32F1xx ... `
113	113
114	114		Configure the board under Tools:
115	115
116	116		- Board Generic STM32F103 series
117	117		- Serial Interface No Serial
118	118		- Upload method STLINK
119	119
120	120		## First start
121	121
122	122		Upload the Arduino blink sketch, then the LED PC13 should blink. Possibly. Set port to PC13.
123	123
124	124		## Build Lazarus with FPCUPdeluxe
125	125
126	126		### Build trunk
127	127
128	128		Download FPCUPdeluxe-\[OS\] from <https://github.com/newpascal/fpcupdeluxe/releases> It is best to copy the download of FPCUPdeluxe into a new empty folder and then start the copied file in the file manager with a double click. Linux asks if the file should be made executable, answer yes. The FPCUPdeluxe GUI should then start.
129	129
130	130		- Set the top left list boxes FPC version and Lazarus version to trunk or embedded which are both in the Basic tab.
131		-	~~- Build the Lazarus base trunk/embedded version with <span class="kbd">Install/update FPC+Laz</span>.~~
	131	+	- Build the Lazarus base trunk/embedded version with `Install/update FPC+Laz`.
132	132
133	133		If everything goes through without errors you get the current trunk from FPC and Lazarus. Normal desktop applications can now be created with this. There should be an icon for Lazarus_fpcupdeluxe on the Desktop.
134	134
135	135		> Note: Note: SVN repositories may experience difficulties. If so, don't give up, just try again later ;-) What also helps, run FPCUPdeluxe twice in a row. An out of date FPCUPdeluxe can also cause difficulties. If something doesn't work, you can ask in the [Lazarus forum](https://forum.lazarus.freepascal.org/index.php/topic,34645.0.html), the author is very helpful.
136	136
137	137		### Build ARM cross compiler
138	138
139		-	~~Press the <span class="kbd">Setup+</span> button in the Cross tab to open a dialog with further options. Set the following there:~~
	139	+	Press the `Setup+` button in the Cross tab to open a dialog with further options. Set the following there:
140	140
141	141		- "Use jobs for GNU make": Remove hooks.
142	142		- CPU: arm
143	143		- OS: embedded
144	144		- Cross SubArch Overide: armv7m
145	145		- Close dialog with Ok .
146	146
147	147		Select the following check boxes in the Cross tab:
148	148
149	149		- CPU: arm
150	150		- OS: embedded
151	151
152		-	~~Press the <span class="kbd">Install cross compiler</span> button, the cross compiler will be built. If everything worked correctly, exit FPCUPdeluxe.~~
	152	+	Press the `Install cross compiler` button, the cross compiler will be built. If everything worked correctly, exit FPCUPdeluxe.
153	153
154	154		## Prepare Lazarus
155	155
156		-	~~### Start with <span class="kbd">F9</span>~~
	156	+	### Start with `F9`
157	157
158		-	~~If you try to start with <span class="kbd">F9</span>, you always get an error message. You can prevent this. Change the following in Lazarus:~~
	158	+	If you try to start with `F9`, you always get an error message. You can prevent this. Change the following in Lazarus:
159	159
160	160		- "Tools \> Settings ... \> Keyboard layout \> Commands from the menu 'Start' \> Start program", set to Unknown.
161	161		- "Tools \> Settings ... \> Keyboard layout \> Commands from the menu 'Start' \> Start without debugger", remove the ticks from Shift and Ctrl.
162	162
163		-	~~Now you can upload and start a program normally with <span class="kbd">F9</span>, but consider that the debugger is also disabled if you then write a normal PC program with Lazarus!~~
	163	+	Now you can upload and start a program normally with `F9`, but consider that the debugger is also disabled if you then write a normal PC program with Lazarus!
164	164
165	165		### Code tools
166	166
167	167		It may be that the code tools does not find the stm32f103xb unit. If so, then the following step is necessary:
168	168
169	169		- "Tools \> Reread FPC source code directory"
170	170
171	171		### Readable ASM code creation
172	172
173	173		If you want to see the source as assembler code, the following step is necessary:
174	174
175	175		- Enter "Project \> Project Settings ... \> User-defined settings \> User-defined settings" -al, this creates an *.s file that contains the program as ASM code.
176	176
177	177		### Faulty optimization
178	178
179	179		I have experienced a program not working properly because the compiler incorrectly optimised the code. So you should switch off code optimization with {\$O-} at the beginning of the program.
180	180
181	181		## First project
182	182
183	183		### Create a new project
184	184
185	185		- "File -\> New ... \> Simple Program" - create a new project.
186	186		- "Project \> Project Settings ... \> Configuration and Goals" - set the following:
187	187		- Target operating system (-T): Embedded
188	188		- Target CPU family (-P): arm
189	189		- Target processor (-Cp): ARMV7M
190	190		- "Project \> Project Settings ... \> Debug" : Remove the check mark "Generate debugger information for GDB" .
191	191		- "Project \> Project settings ... \> User-defined settings -\> User-defined settings still enter -WpSTM32F103X8.
192	192		- "Project \> Project Settings ... \> Compiler Commands -\> Execute After"
193	193		- Remove the Compile and Recompile ticks.
194	194		- Enter the following into the command: st-flash write stm32Blink.bin 0x8000000
195	195
196	196		> Note: The paths still have to be adapted to your own installations.
197	197
198	198		As a recommendation, I would take this project as a template and build all new projects on top of it. Setting the whole thing up for a new project each time is a bit tedious.
199	199
200	200		### Start project
201	201
202		-	Nothing should now be standing in the way of your first blink program (source below). Compile and upload the program with <span class="kbd">F9</span>. If everything worked, the LED at pin 13 should flash about every second.
	202	+	Nothing should now be standing in the way of your first blink program (source below). Compile and upload the program with `F9`. If everything worked, the LED at pin 13 should flash about every second.
203	203
204	204		``` pascal
205	205		program stm32Blink;
206	206
207	207		{$O-}
208	208
209	209		procedure delay;
210	210		var
211	211		i : uint32;
212	212		begin
213	213		for i := 0 to 500000 do
214	214		begin
215	215		asm
216	216		nop // empty instruction
217	217		end;
218	218		end;
219	219		end;
220	220
221	221		begin
222	222		// turn on Port C
223	223		RCC.APB2ENR := RCC.APB2ENR or (%1 shl 4);
224	224
225	225		// Pin 13 from Port C to Output
226	226		PortC.CRH := $00300000;
227	227
228	228		// Note: The LED lights up at LOW.
229	229		while true do
230	230		begin
231	231		// Pin 13 - High
232	232		PortC.BSRR := 1 shl 13;
233	233		Delay;
234	234
235	235		// Pin 13 - Low
236	236		PortC.BRR := 1 shl 13;
237	237		Delay;
238	238		end;
239	239		end.
240	240		```
241	241
242	242		## Manually with make
243	243
244	244		Not tested.
245	245
246	246		``` bash
247	247		make clean all OS_TARGET=embedded CPU_TARGET=arm SUBARCH=armv7m
248	248		```
249	249
250	250		## MSEide and MSEgui
251	251
252	252		As an alternative to Lazarus you can also use the MSEide and MSEgui.
253	253
254	254		The following tools are necessary:
255	255
256	256		- <https://developer.arm.com/open-source/gnu-toolchain/gnu-rm/downloads> - GNU Arm Embedded Toolchain (gcc for ARM)
257	257		- <https://sourceforge.net/projects/mseide-msegui/files/fpccrossarmembedded/> - cross-compiler for ARM Embedded.
258	258		- <https://sourceforge.net/projects/mseide-msegui/files/mseide-msegui/4.6/> - mseGUI (download bin and sources)
259	259		- <https://gitlab.com/mseide-msegui/mseuniverse/tree/master/samples/embedded/arm/stm32l100c> - demo project
260	260
261	261		Unzip these archives into a folder, eg /home/tux/STM3-FPC
262	262
263	263		Start MSEide under /home/tux/STM32-FPC/msegui/bin.
264	264
265	265		- Settings \> Configure MSEide
266	266		- adjust the following path: \${MSEDIR} - /home/tux/STM32-FPC/msegui/
267	267		- Project \> open - Open the demo project in the extracted folder. (/home/tux/STM32-FPC/samples/embedded/arm/stm32l100c/stm32l100c.prj)
268	268		- Project \> Options \> Macros, adjust the following paths:
269	269		- TOOLCHAINDIR - /home/tux/STM32-FPC/gcc-arm-none-eabi-7-2017-q4-major/
270	270		- CROSSFPCDIR - / home/tux/STM32-FPC/crossfpc-x86_64_linux_eabi_embedded_3_1_1/
271	271
272		-	~~If a red break point is set in the left column, deactivate it with a click. Start the program with <span class="kbd">F9</span>. If everything went well, this should work without errors.~~
	272	+	If a red break point is set in the left column, deactivate it with a click. Start the program with `F9`. If everything went well, this should work without errors.
273	273
274	274		# See also
275	275
276	276		- [[ARM Embedded Tutorials]] - Overview
277	277
278	278		---
279	279		From the Free Pascal wiki, page "ARM Embedded Tutorial - Entry FPC and STM32", as it stood on 2021-02-01 after a change by Trev, out of the wiki's dump of 2024-05-26. Copyright stays with the author who wrote it, according to the old wiki's [[Licensing]] page. If you have concerns about this material, [message the admin](/wiki-contact).
280	280		Category: ARM
281	281		Category: Embedded
282	282		Category: Tutorials

Back to history