STM32 Development and Remote Debugging - Revision history

Joachim at 20:12, 16 June 2022

2022-06-16T20:12:55Z

← Older revision		Revision as of 20:12, 16 June 2022
Line 159:		Line 159:

	Et voila: longer source code (that you can pack into a function) but only 5k flash.		Et voila: longer source code (that you can pack into a function) but only 5k flash.

			=== CH32F103 Clones ===

			On job4 there is a ch32f103-blink and a ch32F103-stepper project that runs in STM32CubeIDE
			* blink example tested with flash and debugging. Led is inverted at pc13. uses openocd
			* stepper example only tested with flash, used MX config target STM32F103C6, SYS Debug -> Serial Wire, uses standard debug config

			* Both don't need the boot0 jumper changed.
			* Both need swclk, swdio, gnd and nrst connected to st-link for flashing (no manual reset needed)

			Maybe I changed STM32 system files to make debug work...
			see file ch32f103 Debug.cfg in bilink project:

			source [find interface/stlink-dap.cfg]
			set WORKAREASIZE 0x5000
			transport select "dapdirect_swd"
			set CHIPNAME STM32F103C8Tx
			set BOARDNAME genericBoard
			set ENABLE_LOW_POWER 1
			set STOP_WATCHDOG 1
			set CLOCK_FREQ 8000
			reset_config srst_only srst_nogate connect_assert_srst
			set CONNECT_UNDER_RESET 1
			set CORE_RESET 0
			set AP_NUM 0
			set GDB_PORT 3333
			source [find target/stm32f1x.cfg]

Joachim: /* Flashing */

2022-03-22T01:16:53Z

Flashing

← Older revision		Revision as of 01:16, 22 March 2022
Line 74:		Line 74:
	* CONNECT_UNDER_RESET 1: press reset, start openocd, then release reset (boot0 not needed)		* CONNECT_UNDER_RESET 1: press reset, start openocd, then release reset (boot0 not needed)
	* CPUTAPID 0: ignore chip type to allow clones		* CPUTAPID 0: ignore chip type to allow clones

			Looks like STM32CubeIDE just got downgraded to a project start code generator (clones actively blocked).
			At least for boards that are supported by PlatformIO/VSCode.

	=== Debugging ===		=== Debugging ===

Joachim: /* Debugging */

2022-03-22T01:10:29Z

Debugging

← Older revision		Revision as of 01:10, 22 March 2022
Line 77:		Line 77:
	=== Debugging ===		=== Debugging ===

	To debug your code, select Debug (the small green bug) instead of run.		To debug your code in STM32CubeIDE, select Debug (the small green bug) instead of run.
	The code will be flashed, started and then paused before the first instruction in main(): HAL_Init()		The code will be flashed, started and then paused before the first instruction in main(): HAL_Init()
	Some options:		Some options:
Line 86:		Line 86:
	* Suspend -> Pause code wherever it is right now		* Suspend -> Pause code wherever it is right now
	While the execution is suspended, you can examine variables, memory and registers - no need for printf :)		While the execution is suspended, you can examine variables, memory and registers - no need for printf :)

			This also works with VSCode. No special config in platformio.ini is needed.
			For STM32F103C8 I needed to change reset_config to none in ~/.platformio/packages/tool-openocd/scripts/target/stm32f1x.cfg

	=== Hints ===		=== Hints ===

Joachim: /* Flashing */

2022-03-22T01:00:13Z

Flashing

← Older revision		Revision as of 01:00, 22 March 2022
Line 60:		Line 60:

	=== Flashing ===		=== Flashing ===
	I ~~could not yet build for ch32f103c8~~ clones with ~~platformio, but~~ flashing elf files ~~that were built~~ with ~~stm32cubeide~~ works:		I cannot make flashing clones (e.g. CH32F103C8) work with STM32CubeIDE (1.9.0).
			But flashing the elf files with platformio openocd works fine:

	elf="/home/joachim/STM32CubeIDE/workspace_1.3.0/ch32f103-blink/Debug/ch32f103-blink.elf"		elf="/home/joachim/STM32CubeIDE/workspace_1.3.0/ch32f103-blink/Debug/ch32f103-blink.elf"

Joachim at 00:46, 22 March 2022

2022-03-22T00:46:37Z

← Older revision		Revision as of 00:46, 22 March 2022
Line 64:		Line 64:
	elf="/home/joachim/STM32CubeIDE/workspace_1.3.0/ch32f103-blink/Debug/ch32f103-blink.elf"		elf="/home/joachim/STM32CubeIDE/workspace_1.3.0/ch32f103-blink/Debug/ch32f103-blink.elf"
	/home/joachim/.platformio/packages/tool-openocd/bin/openocd -d2 \		/home/joachim/.platformio/packages/tool-openocd/bin/openocd -d2 \
	-c "set CPUTAPID 0" \		-c "set CONNECT_UNDER_RESET 1; set CPUTAPID 0" \
	-s /home/joachim/.platformio/packages/tool-openocd/scripts -f interface/stlink.cfg \		-s /home/joachim/.platformio/packages/tool-openocd/scripts -f interface/stlink.cfg \
	-c "transport select hla_swd" \		-c "transport select hla_swd" \
Line 70:		Line 70:
	-c "reset_config none" \		-c "reset_config none" \
	-c "program {$elf} verify reset; shutdown;"		-c "program {$elf} verify reset; shutdown;"

			* CONNECT_UNDER_RESET 1: press reset, start openocd, then release reset (boot0 not needed)
			* CPUTAPID 0: ignore chip type to allow clones

	=== Debugging ===		=== Debugging ===

Joachim at 00:22, 22 March 2022

2022-03-22T00:22:25Z

← Older revision		Revision as of 00:22, 22 March 2022
Line 58:		Line 58:

	Code should get compiled, flashed and started now: the LED blinks		Code should get compiled, flashed and started now: the LED blinks

			=== Flashing ===
			I could not yet build for ch32f103c8 clones with platformio, but flashing elf files that were built with stm32cubeide works:

			elf="/home/joachim/STM32CubeIDE/workspace_1.3.0/ch32f103-blink/Debug/ch32f103-blink.elf"
			/home/joachim/.platformio/packages/tool-openocd/bin/openocd -d2 \
			-c "set CPUTAPID 0" \
			-s /home/joachim/.platformio/packages/tool-openocd/scripts -f interface/stlink.cfg \
			-c "transport select hla_swd" \
			-f target/stm32f1x.cfg \
			-c "reset_config none" \
			-c "program {$elf} verify reset; shutdown;"

	=== Debugging ===		=== Debugging ===

Joachim: /* Prepare the STM32 chip */

2022-02-23T10:01:05Z

Prepare the STM32 chip

← Older revision		Revision as of 10:01, 23 February 2022
Line 26:		Line 26:

	* Pull down Pin 1 (Boot0) to Gnd (10k)		* Pull down Pin 1 (Boot0) to Gnd (10k)
	* ~~Connect your STLink~~ (mine is on a Nucleo F401RE, Connectors CN4 and JP1) to your STM32, Ground first:		* Prepare ST-Link (mine is on a Nucleo F401RE
			* Remove jumpers from CN2 (1,2) and (3,4)
			* Switch 5V from the STM32F401 on the nucleo board to external J5 from U5V to E5V
			* Connect your STLink (mine has Connectors CN4 for data and JP1 for power) to your STM32, Ground first:
	* CN4-3 - 9 (VSS aka ground)		* CN4-3 - 9 (VSS aka ground)
	* CN4-2 - 14 (SWCLK)		* CN4-2 - 14 (SWCLK)

Joachim: /* UART */

2020-03-13T19:26:29Z

UART

← Older revision		Revision as of 19:26, 13 March 2020
Line 133:		Line 133:
	LL_LPUART_Disable(LPUART1);		LL_LPUART_Disable(LPUART1);

	Et voila: only 5k flash.		Et voila: longer source code (that you can pack into a function) but only 5k flash.

Joachim: /* UART */

2020-03-13T19:24:07Z

UART

← Older revision		Revision as of 19:24, 13 March 2020
Line 106:		Line 106:
	==== UART ====		==== UART ====

	Uarts are the serial ports. ~~Youcan~~ send any data over one line and receive over another. Blocking or asynchronous. Here is just the simplest form: blocking send.		Uarts are the serial ports. You can send any data over one line and receive over another. Blocking or asynchronous. Here is just the simplest form: blocking send.
	* Enable LPUART1 or USART2 or whatever port you want and does not collide with already used pins in CubeMX (Pinout & Configuration, Conectivity)		* Enable LPUART1 or USART2 or whatever port you want and does not collide with already used pins in CubeMX (Pinout & Configuration, Conectivity)
	* As Mode select Half Duplex (can send/receive synchronously)		* As Mode select Half Duplex (can send/receive synchronously)

Joachim: /* UART */

2020-03-13T19:23:51Z

UART

← Older revision		Revision as of 19:23, 13 March 2020
Line 106:		Line 106:
	==== UART ====		==== UART ====

	...		Uarts are the serial ports. Youcan send any data over one line and receive over another. Blocking or asynchronous. Here is just the simplest form: blocking send.
			* Enable LPUART1 or USART2 or whatever port you want and does not collide with already used pins in CubeMX (Pinout & Configuration, Conectivity)
			* As Mode select Half Duplex (can send/receive synchronously)
			* In Parameter Settings select communication parameters like (common values in parantheses)
			** Baud Rate (115200)
			** Word Length (8)
			** Parity (None)
			** Stop Bits (1)
			** Data Direction (For sending only debug prints "Transmit Only" is enough)
			* Generate the code adds a in MX_LPUART1_UART_Init() to your main()
			* To send over lpuart1, just call
			HAL_UART_Transmit(&hlpuart1, buffer, bufferlength, HAL_MAX_DELAY);

			Again, quite resource hungry. Just the HAL init and one send is near the 8k flash limit.
			So let's try LL API:

			* In CubeMX Project manager switch LPUART driver from HAL to LL
			* Regenerate sources and change in HAL_UART_Transmit(&hlpuart1, "Hello, serial world!\n", 21, HAL_MAX_DELAY); to its LL equivalent:
			LL_LPUART_Enable(LPUART1);
			const char *str = "Hello, serial world!\n";
			while( *str ) {
			while( !LL_LPUART_IsActiveFlag_TXE(LPUART1) ) ;
			LL_LPUART_TransmitData8(LPUART1, *str++);
			}
			while( !LL_LPUART_IsActiveFlag_TC(LPUART1) ) ;
			LL_LPUART_Disable(LPUART1);

			Et voila: only 5k flash.