STM32F4 Labs

STM32F4 Labs
T.O.M.A.S – Technically Oriented Microcontroller Application Services

V1.09
1 System Peripherals 2
1. GPIO & EXTI (1.1)

1. GPIO lab (1.1.1)
2. EXTI lab (1.1.2)
2. PWR (1.2)
1. SLEEP lab (1.2.1)
2. STOP lab (1.2.2)
3. STANDBY lab (1.2.3)
3. DMA (1.3)
1. DMA Poll lab (1.3.1)
2. DMA Interrupt lab (1.3.2)
2 Basic communication peripherals 3
1. UART (2.1)
1. UART Poll lab (2.1.1)
2. UART Interrupt lab (2.1.2)
3. UART DMA lab (2.1.3)
2. SPI (2.2)
1. SPI Poll lab (2.2.1)
2. SPI Interrupt lab (2.2.2)
3. SPI DMA lab (2.2.3)
3. I2C (2.3)
1. I2C Poll lab (2.3.1)
2. I2C Interrupt lab (2.3.2)
3. I2C DMA lab (2.3.3)
4. I2C Memory mode lab (2.3.4)
3 Timing peripherals 4
1. RTC (3.1)
1. RTC Alarm lab (3.1.1)
2. TIM (3.2)
1. TIM Interrupt lab (3.2.1)
2. TIM PWM out lab (3.2.2)
3. TIM DMA lab (3.2.3)
4. TIM Counter lab (3.2.4)
3. WDGs (3.3)
1. WWDG lab (3.3.1)
2. IWDG lab (3.3.2)
4 Analog peripherals 5
1. DAC (4.1)
1. DAC wave generation lab (4.1.1)
2. ADC (4.2)
1. ADC Poll lab (4.2.1)
2. ADC Interrupt lab (4.2.2)
3. ADC DMA lab (4.2.3)
5 5. BSP package 6
1. FMC SDRAM BSP lab (5.1)

2. LCD BSP Print text lab (5.2)
3. I2C BSP EEPROM lab (5.3)
4. SPI BSP GYROSCOPE lab (5.4)
STM32F42xx Technical Training 02/08/2016

1.1.1 GPIO Lab
1.1.1 Configure GPIO for LED toggling 11
• Objective
• Learn how to setup pin and GPIO port in CubeMX
• How to Generate Code in CubeMX and use HAL functions
• Goal
• Configure GPIO pin in CubeMX and Generate Code
• Add in to project HAL_Delay function and HAL_GPIO_Toggle function
• Verify the correct functionality on toggling LED
• Create project in CubeMX

• Menu > File > New Project
• Select STM32F4 > STM32F429/439 > LQFP144 > STM32F439ZITx
• Configure LED pin as GPIO_Output

• For debug purpose is recommended to select debug pins

SWD or JTAG
• Select can be done in TAB>Pinout>SYS
• On discovery is available only SWD option
• If SWD/JTAG is not selected and the Set all free pins as analog
(MENU>Project>Settings>TAB>Code Generator) is selected, debug is not possible
Clock Configuration overview 10

• External clock enabling
• TAB>Pinout
• Select HSE and LSE clocks
• Bypass or crystal
1. Set HSE crystal
2. CubeMX reserve pins

• In order to run on maximum frequency, setup clock system

• GPIO Configuration
• TAB>Configuration>System>GPIO
• GPIO(Pin) Configuration
• Select Push Pull mode
• No pull-up and pull-down
• Output speed to HIGH
Is important for faster
peripheries like SPI, USART
• Button OK
• GPIO(Pin) output speed configuration

• Change the rising and falling edge when pin change state from high to low or low to high
• Higher GPIO speed increase EMI noise from STM32 and increase STM32 consumption
• It is good to adapt GPIO speed with periphery speed. Ex.: Toggling GPIO on 1Hz is LOW
optimal settings, but SPI on 45MHz the HIGH must be set
GPIO output LOW speed GPIO output MEDIUM speed

LOW LOW
HIGH HIGH
GPIO output FAST speed GPIO output HIGH speed
LOW LOW
HIGH HIGH
• Now we set the project details for generation

• Menu > Project > Project Settings
• Set the project name
• Project location
• Type of toolchain
• Now we can Generate Code

• Menu > Project > Generate Code
• Now we open the project in our IDE

• The functions we want to put into main.c
• Between /* USER CODE BEGIN 3 */ and /* USER CODE END 3 */ tags
• Into infinite loop while(1){ }
• For toggling we need to use this functions

• HAL_HAL_Delay which create specific delay
• HAL_GPIO_WritePin or HAL_GPIO_TogglePin

• Into infinite loop while(1){ }
• For toggling we need to use this functions

• HAL_HAL_Delay which create specific delay
• HAL_GPIO_WritePin or HAL_GPIO_TogglePin
/* USER CODE BEGIN 3 */

/* Infinite loop */
while (1)
{
HAL_GPIO_WritePin(GPIOG, GPIO_PIN_14, GPIO_PIN_SET);
HAL_Delay(500);
HAL_GPIO_WritePin(GPIOG, GPIO_PIN_14, GPIO_PIN_RESET);

HAL_Delay(500);
}
/* USER CODE END 3 */
1.1.2 EXTI lab

1.1.2 Configure EXTI to turn on LED 23
• Objective
• Learn how to setup input pin with EXTI in CubeMX
• Goal
• Configure GPIO and EXTI pin in CubeMX and Generate Code
• Add into project Callback function and function which turn on led
• Verify the correct functionality by pressing button which turns on LED


• Configure Button pin as GPIO_EXTIX


• Configure Button pin as GPIO_EXTIX

• Details in lab 0
• GPIO Configuration
• TAB>Configuration>System>GPIO
• GPIO(Pin) Configuration
• Select External Interrupt Mode with Rising edge trigger detection
• No pull-up or pull-down
• PG14 can be let in default
settings
• Button OK
• NVIC Configuration
• We need to enable interrupts for EXTI
• TAB>Configuration>System>NVIC
• NVIC Configuration
• Enable interrupt for
EXTI Line0
• Button OK


HAL Library work flow 1
Peripheral Initializations
including peripheral interrupt NVIC
initializations Generated by
CubeMX
Configure the GPIO to generate interrupt on
rising or falling edge
HAL_EXTI0_IRQHandler EXTI0_IRQHandler
Edge detection callback

HAL_GPIO_EXTI_Callback
initializations MX_GPIO_Init
inside main.c

HAL Library working flow 3
initializations inside
stm32f4xx_it.c

initializations


User must define Callback

it is declared by default as
empty weak
initializations


Usually in main.c between

/* USER CODE BEGIN */
tags
HAL Library work flow summary

3. create
edge
1. init NVIC
initializations
2. init GPIO
rising or falling edge 5. HAL EXTI 4. EXTI interrupt
interrupt handler handler

HAL_GPIO_EXTI_Callback HAL files clearing
6. HAL EXTI flags, check errors,
callback …

• We create function which will handle the EXTI interrupts
• The HAL callback function for EXTI

• void HAL_GPIO_EXTI_Callback(uint16_t GPIO_Pin)
• For LED turn on we need to use this functions

• HAL_GPIO_WritePin

• We create function which will handle the EXTI interrupts
• The HAL callback function for EXTI

• void HAL_GPIO_EXTI_Callback(uint16_t GPIO_Pin)
• For LED turn on we need to use this functions

• HAL_GPIO_WritePin

void HAL_GPIO_EXTI_Callback(uint16_t GPIO_Pin)
{
if(GPIO_Pin == GPIO_PIN_0) {
} else {
__NOP();
}
}
1.2.1 Low Power mode SLEEP
lab

1.2.1 Use SLEEP mode with EXTI 41
• Objective
• We use the EXTI setup from lab 1
• Learn how to setup SLEEP in HAL
• Create simple project with SLEEP mode with wake up on pin press
• Goal
• Use project from EXTI lab
• Learn how to setup the SLEEP in HAL, and which events can wake up
MCU
• Verify the correct functionality by measuring consumption
1.2.1 SLEEP Mode
GPIO’s
Core
FLASH • Core is stopped
CM4
RTC/backup reg. RAM • Peripherals are running
IWDG DMA
Clock
GP timers HSI
SPI HSE
USB LSI USART
LSE
DAC I2C
Reset
ADC
Power
regulator

4. create
edge
1. init NVIC
initializations
2. init GPIO
rising or falling edge 5. EXTI interrupt
handler
3. Use WFI
Enter into SLEEP mode(WFI)
6. HAL EXTI
interrupt handler

callback …

• Function to enter SLEEP

• HAL_PWR_EnterSLEEPMode(uint32_t Regulator, uint8_t SLEEPEntry)
• We can measure consumption
To be able to reprogram
the STM32 which is in
LP mode, use
connection during
reset option


• HAL_PWR_EnterSLEEPMode(uint32_t Regulator, uint8_t SLEEPEntry)

/* Infinite loop */
while (1)
{
HAL_Delay(1000);
HAL_PWR_EnterSLEEPMode(PWR_LOWPOWERREGULATOR_ON,PWR_SLEEPENTRY_WFI);
}
• Consumption still to high?

• Is STM32 really in SLEEP?
• Is the Systick disabled?

/* Infinite loop */
while (1)
{
HAL_Delay(1000);
HAL_SuspendTick();
HAL_PWR_EnterSLEEPMode(PWR_LOWPOWERREGULATOR_ON,PWR_SLEEPENTRY_WFI);
HAL_ResumeTick();
}
• Is this better?
1.2.2 Low Power mode STOP lab

1.2.2 Use STOP mode with EXTI 48
• Objective
• We use the EXTI setup from lab 1
• Learn how to setup STOP in HAL
• Create simple project with STOP mode with wake up on pin press
• Goal
• Use project from EXTI lab
• Learn how to setup the STOP in HAL, which events can wake up you
1.2.2 STOP Mode
• Core is stopped
GPIO’s
Core
FLASH • HSE, MSI clocks are OFF
CM4
RTC/backup reg. RAM
• SRAM and registers
IWDG DMA content is preserved
• Peripherals with HSI, LSI,
Clock
LSE clock option can be
GP timers HSE ON
HSI
SPI
• GPIO’s keep their setup
USB LSI USART
LSE
DAC I2C
ADC Reset
Power
regulator

4. create
edge
1. init NVIC
initializations
2. init GPIO
rising or falling edge 5. EXTI interrupt
handler
3. Use WFI
Enter into STOP mode(WFI) HAL_EXTI0_IRQHandler EXTI0_IRQHandler
8. Reconfigure 6. HAL EXTI

Clock reconfigure clock after interrupt handler
wakeup

callback …


• HAL_PWR_EnterSTOPMode(uint32_t Regulator, uint8_t STOPEntry)
• HAL_PWREx_EnterUnderDriveSTOPMode(uint32_t Regulator, uint8_t STOPEntry)
LP mode, use
connection during
reset option



/* Infinite loop */
while (1)
{
HAL_Delay(1000);
HAL_PWR_EnterSTOPMode(PWR_LOWPOWERREGULATOR_ON,PWR_STOPENTRY_WFI);
SystemClock_Config();
}
• Or different function (for STM32F42X/43X)

/* Infinite loop */
while (1)
{
HAL_Delay(1000);
HAL_PWREx_EnterUnderDriveSTOPMode(PWR_LOWPOWERREGULATOR_UNDERDRIVE_ON,PWR_STOPENTRY_WFI);
SystemClock_Config();
}
1.2.3 Low Power mode STANDBY
lab

1.2.3 Use STANDBY mode 55
• Objective
• For this lab create CubeMX project
• For testing purpose enable LED on PG14
• Learn how to setup STANDBY in HAL
• Create simple project with STANDBY mode with wake up on pin press
• Goal
• Learn how to setup the STANDBY in HAL, which events can wake up you
1.2.3 STANDBY Mode
• Core and all peripherals
GPIO’s FLASH
Core are OFF, except RTC and
CM4
RTC/backup reg. RAM IWDG if enabled
IWDG DMA • HSE, HSI clocks are OFF,

LSI LSE can be ON
Clock • SRAM and registers

GP timers HSE content is lost, except
SPI RTC, and standby circuitry
HSI
USB LSI USART • GPIO’s are in high Z,
LSE
DAC I2C except Reset, RTC OUT
ADC Reset and WKUP 1,2,3
Power
regulator
Reset RTC OUT WKUP 1,2,3


1. init NVIC
initializations
2. Standby
Enable Wake-up pin
4. create
3. Use WFI edge
Enter into STANDBY mode(WFI)
5. Wake up
Reset
STM with reset

• For Wake up we need to setup wake up pin

• HAL_PWR_EnableWakeUpPin(uint32_t WakeUpPinx)
• Function to enter STANDBY

• HAL_PWR_EnterSTANDBYMode();
LP mode, use
connection during
reset option



/* Infinite loop */
while (1)
{
HAL_GPIO_TogglePin(GPIOG, GPIO_PIN_14);
HAL_Delay(2000);
HAL_PWR_EnableWakeUpPin(PWR_WAKEUP_PIN1);
HAL_PWR_EnterSTANDBYMode();
}
• We cannot go into STANDBY again?

• Try to clear wake up flag
• __HAL_PWR_CLEAR_FLAG(PWR_FLAG_WU);
__HAL_PWR_CLEAR_FLAG(PWR_FLAG_WU);
1.3.1 Data transfer over DMA lab

1.3.1 Use DMA in M2M transfer 62
• Objective
• Learn how to setup DMA transfer in CubeMX
• Create simple DMA memory to memory transfer from RAM to RAM
• Goal
• Use CubeMX and Generate Code with DMA
• Learn how to setup the DMA in HAL
• Verify the correct functionality by comparing transferred buffers
CORTEX-M4 Ethernet High Speed Dual Port Dual Port

CCM 168MHz 10/100 USB2.0 DMA1 DMA2
data RAM w/ FPU & MPU
64KB Master 5 Master 4 Master 2 Master 3
Master 1
FIFO/DMA FIFO/DMA FIFO/8 Streams FIFO/8 Streams
Dual Port
S-Bus
D-Bus
I-Bus
AHB1-APB2
AHB1
Dual Port
AHB1-APB1
AHB2
SRAM1
112KB
SRAM2
16KB
FSMC
Accelerator
I-Code FLASH
ART
D-Code
1Mbytes
Multi-AHB Bus Matrix


• For DMA we don’t need to configure any pins


• DMA configuration
• TAB>Configuration
• System>DMA
• TAB>DMA2
1. TAB >
• Button ADD
Configuration
2. System DMA
3. TAB>DMA 2
4. Add DMA
channel
• Select MEMTOMEM
1. MEMTOMEM
DMA request
• Normal mode
• Increment source and
destination address
• FIFO setup
• Byte data width 3. Increment
• Burst size 5. Data width and addresses
• Button OK Burst
2. Normal
mode
4. FIFO setup
6. OK


• Start process DMA (same for TIM, ADC)

• Non blocking start process
• The end of the process must be checked by polling
1. init DMA
Peripheral
Initializations
2. Start DMA
Start Process
(HAL_DMA_Start)
3. DMA transfer data
Poll for process complete

(HAL_DMA_PollForTransfer)
4. Check if transfer is complete
• Return values
• Most of CubeMX functions have return values, which indicate, if operation was successful,
timeout occurs of function end with error
• Is recommended handle this return values to be sure that program working as expected
Ex: Poll for process complete

HAL_OK HAL_ERROR HAL_BUSY
DMA transfer was successfully

finished and data was
transferred to destination
without error
• Return values

Error occurs during DMA

transfer you use
HAL_DMA_GetError for
details what happened
• Return values

DMA transfer in progress,

user can only abort the
transfer

• HAL functions for DMA

• HAL_DMA_Start(DMA_HandleTypeDef *hdma, uint32_t SrcAddress, uint32_t DstAddress,
uint32_t DataLength)
• HAL_DMA_PollForTransfer(DMA_HandleTypeDef *hdma, uint32_t CompleteLevel, uint32_t
Timeout)
• We create two buffers

• One with source data
• Second as destination buffer

uint8_t Buffer_Src[]={0,1,2,3,4,5,6,7,8,9};
uint8_t Buffer_Dest[10];
• HAL_DMA_Start start the M2M data transfer

• HAL_DMA_PollForTransfer check if the transfer ends successfully

HAL_DMA_Start(&hdma_memtomem_dma2_stream0, (uint32_t) (Buffer_Src), (uint32_t) (Buffer_Dest), 10);
while(HAL_DMA_PollForTransfer(&hdma_memtomem_dma2_stream0, HAL_DMA_FULL_TRANSFER, 100) != HAL_OK)
{
__NOP();
}
1.3.2 Data transfer over DMA with
interrupt lab

1.3.2 Use DMA M2M with interrupt 77
• Objective
• Learn how to setup DMA transfer with interrupt in CubeMX
• Create simple DMA memory to memory transfer from RAM to RAM
• Goal
• Use CubeMX and Generate Code with DMA
• Learn how to setup the DMA in HAL
• Verify the correct functionality by comparing transferred buffers

• For DMA we don’t need to configure any pins


• System>DMA
• TAB>DMA2
1. TAB >
• Button ADD
Configuration
2. System DMA
3. TAB>DMA 2
4. Add DMA
channel
• Select MEMTOMEM
1. MEMTOMEM
DMA request
• Normal mode
• Increment source and
destination address
• FIFO setup
• Byte data width 3. Increment
• Burst size 5. Data width and addresses
• Button OK Burst
2. Normal
mode
4. FIFO setup
6. OK
• DMA configuration 1. TAB >

• System > NVIC Configuration
• Enable DMA2 Stream interrupt
• Button OK
2. System > NVIC
3. Enable DMA2
interrupts
4. OK


HAL Library DMA with IT flow

DMA Initializations
initializations
Start process with interrupt generation at end

of process
HAL_DMA_Start_IT
HAL_OK HAL_ERROR HAL_BUSY HAL_DMA_IRQHandler DMA2_Stream0_IRQHandler
end of process callback

DMA_XferCpltCallback
process Error callback

DMA_XferErrorCallback

DMA Initializations
including peripheral interrupt NVIC Generated by CubeMX
initializations

of process
HAL_DMA_Start_IT



DMA Initializations
initializations

of process
HAL_DMA_Start_IT

process Error callback Defined by user


DMA Initializations
initializations
Generated in main.c
of process
HAL_DMA_Start_IT



DMA Initializations
initializations

of process
HAL_DMA_Start_IT

We recommend to use it
in main.c

DMA Initializations
initializations

of process
HAL_DMA_Start_IT

User defined functions. The

user must define functions by
process Error callback himself and put function names
into DMA structure

DMA Initializations
initializations

of process
HAL_DMA_Start_IT

Generated in
stm32f4xx_it.c

DMA Initializations
initializations

of process
HAL_DMA_Start_IT

Defined in
stm32f4xx_hal_dma.c

DMA Initializations
including peripheral interrupt NVIC Start DMA buffer transfer
initializations
Not blocking function
program can continue
of process
HAL_DMA_Start_IT



DMA Initializations
Interrupt indicate DMA
including peripheral interrupt NVIC process is half/complete
initializations or error was detected
of process
HAL_DMA_Start_IT



DMA Initializations
initializations
Process interrupt
Start process with interrupt generation at end information
of process
HAL_DMA_Start_IT



DMA Initializations
initializations

of process
HAL_DMA_Start_IT

Data correctly transferred
Complete callback
function

DMA Initializations
initializations

of process
HAL_DMA_Start_IT

DMA_XferCpltCallback Error was detected
Error callback function


DMA Initializations 1. DMA init
initializations
2. DMA transfer
of process
start
HAL_DMA_Start_IT
4. HAL DMA 3. DMA transfer

5. DMA transfer management complete or error
DMA_XferCpltCallback was correct
process Error callback 5. Error in DMA

DMA_XferErrorCallback transfer

• DMA callback function

• We need to add the name of callback function into DMA structure
• HAL functions for DMA

• HAL_DMA_Start_IT(DMA_HandleTypeDef *hdma, uint32_t SrcAddress, uint32_t DstAddress,
uint32_t DataLength)
• We create two buffers

• One with source data
• Second as destination buffer

uint8_t Buffer_Src[]={0,1,2,3,4,5,6,7,8,9};
• DMA callback creation function prototype

uint8_t Buffer_Src[]={0,1,2,3,4,5,6,7,8,9};
void XferCpltCallback(DMA_HandleTypeDef *hdma);

• DMA complete callback with nop where we can put breakpoint

void XferCpltCallback(DMA_HandleTypeDef *hdma)
{
__NOP();//we reach this only if DMA transfer was correct
}
• DMA Start
• Before we start the DMA with interrupt we need to set the callback into DMA structure
• Then is possible use the HAL_DMA_Start_IT to begin DMA transfer

hdma_memtomem_dma2_stream0.XferCpltCallback=&XferCpltCallback;
HAL_DMA_Start_IT(&hdma_memtomem_dma2_stream0,(uint32_t)Buffer_Src,(uint32_t)Buffer_Dest,10);
2.1.1 UART Poll lab

2.1.1 Simple UART communication 103
• Objective
• Learn how to setup UART in CubeMX
• Work in pairs, one will create transmitter and second receiver
• Goal
• Configure UART in CubeMX and Generate Code
• Learn how to send and receive data over UART without interrupts
• Verify the correct functionality

• Pin selection
• We are looking for free pins where is possible to create wire loopback connection
• Pin selection
• We are looking for free pins
where is possible to create
wire loopback connection
Image from
STM32F429-Discovery
user manual
• Pin selection
Image from
STM32F429
datasheet
• Hardware preparation
• We connect selected pins together by jumper, this help us to create loopback on UART
Hardware
connection
RX <-TX
TX>RX

• CubeMX UART selection

• Select USART1 in asynchronous mode
• Select PA9 and PA10 for USART1 if weren't selected

• CubeMX UART configuration

• Tab>Configuration>Connectivity>USART1
• CubeMX USART configuration check:

• BaudRate
• World length
• Parity
• Stop bits
• Data direction
• Oversampling
• CubeMX USART GPIO configuration check:

• On high baud rate set the
GPIO speed to HIGH
• TAB>Configuration>System>
>GPIO
• Set the HIGH output speed
Button OK


HAL Library init flow

CubeMX UART init start in
main.c file
MX_USART1_UART_Init();
Init UART1 structure
HAL_UART_Init(&huart1);
HAL_UART_MspInit callback
Init GPIO and NVIC for UART


1. We need init
Peripheral Initializations UART1


1. We need init
CubeMX create for us
function which handle
Init UART1 structure UART initialization


1. We need init
2. Call UART1 init

MX_USART1_UART_Init(); function


1. We need init
2. Call UART1 init

Init UART1 structure CubeMX fill the UART

structure with parameters
which we choose in
Configuration window


1. We need init
2. Call UART1 init

Init UART1 structure 3. Store UART1 configuration

into structure


1. We need init
2. Call UART1 init


into structure
Function wrote
parameters from structure
HAL_UART_MspInit callback into UART1 registers


1. We need init
2. Call UART1 init


into structure
HAL_UART_Init(&huart1); 4. Write to UART1 registers
HAL_UART_MspInit callback Optional callback from

HAL_UART_Init function,
be default empty weak
function

1. We need init
2. Call UART1 init


into structure
HAL_UART_MspInit callback CubeMX configure here

UART1 GPIOs and
enable UART1 clock
system

1. We need init
2. Call UART1 init


into structure
HAL_UART_MspInit callback 5. UART1 init callback
Init GPIO and NVIC for UART CubeMX configure here

UART1 GPIOs and
enable UART1 clock
system and NVIC

1. We need init
2. Call UART1 init


into structure
Init GPIO and NVIC for UART 6. UART1 GPIOS, NVIC and RCC init

1. We need init
2. Call UART1 init


into structure
Init GPIO and NVIC for UART 6. UART1 GPIOS, NVIC and RCC init
7. Next periph init or user code

HAL Library transmit flow
Peripheral Initializations Generated by

CubeMX
Polling process Function blocks
HAL_UART_Transmit Polling with timeout
HAL_TIMEOUT HAL_OK HAL_ERROR HAL_BUSY

HAL Library transmit flow
Created by user

HAL_UART_Transmit Polling with timeout

HAL Library receive flow
Peripheral Initializations Generated by

CubeMX
HAL_UART_Receive Polling with timeout

HAL Library receive flow
Created by user

HAL_UART_Receive Polling with timeout

• Open the project in our IDE

• Into infinite while function
• For transmit use function

• HAL_UART_Transmit(UART_HandleTypeDef *huart, uint8_t *pData, uint16_t Size, uint32_t Timeout)
• For receive use function

• HAL_UART_Receive(UART_HandleTypeDef *huart, uint8_t *pData, uint16_t Size, uint32_t Timeout);
• Transmit solution
• Create data structure for data

uint8_t data[]={0,1,2,3,4,5,6,7,8,9};
• Call transmit function from while loop

/* Infinite loop */
while (1)
{
HAL_UART_Transmit(&huart1,data,10,1000);
}
• Receive solution

uint8_t data[10];
• Call transmit function from while loop

/* Infinite loop */
while (1)
{
HAL_UART_Receive(&huart1,data,10,1000);
}
2.1.2 UART Interrupt lab

2.1.2 Use UART with interrupt 134
• Objective
• Learn how to setup UART with interrupts in CubeMX
• Create simple loopback example with interrupts
• Goal
• Learn how to send and receive data over UART with interrupts

• Pin selection
• It will be same as previous lab we use again PA9 and PA10
Hardware
loopback


• CubeMX UART configuration check:

• BaudRate
• World length
• Parity
• Stop bits
• Data direction
• Oversampling
• CubeMX USART configuration NVIC settings

• TAB>NVIC Settings
• Enable interrupts
• OK


HAL Library UART with IT receive flow

initializations

of process
HAL_UART_Receive_IT
HAL_OK HAL_ERROR HAL_BUSY HAL_UART_IRQHandler USART1_IRQHandler

HAL_UART_RxCpltCallback

HAL_UART_ErrorCallback
HAL Library UART with IT transmit flow

initializations

of process
HAL_UART_Transmit_IT

HAL_UART_TxCpltCallback

HAL Library UART with IT transmit flow

including peripheral interrupt NVIC Generated by CubeMX
initializations

of process



initializations

of process

process Error callback Defined by user


initializations Generated in main.c and
stm32f4xx_hal_msp.c
of process



initializations

of process

We recommend to use it
in main.c

initializations

of process

Defined as __weak you can

process Error callback find name of this functions in
HAL_UART_ErrorCallback stm32f4xx_hal_uart.c

initializations

of process

Generated in
stm32f4xx_it.c

initializations

of process

Defined in
stm32f4xx_hal_uart.c

including peripheral interrupt NVIC Send buffer over UART
initializations
program can continue
of process



Interrupt indicate the data
Peripheral Initializations register is empty we can
initializations send more data or error
was detected
of process



initializations
Process interrupt
Start process with interrupt generation at end information
of process



initializations
Send more data if is buffer
not empty
of process



initializations

of process

If data buffer is empty use
Complete callback
function

initializations

of process

Or if error was detected
use Error callback
function

Peripheral Initializations 1. UART1 init
initializations
2. UART1 send
of process
buffer
4. Send more 3. UART1 Tx

data or manage register empty
end of process callback 5. Buffer sent error
process Error callback 5. Transmit error



• HAL_UART_Transmit_IT(UART_HandleTypeDef *huart, uint8_t *pData, uint16_t Size);

• HAL_UART_Receive_IT(UART_HandleTypeDef *huart, uint8_t *pData, uint16_t Size);
• Buffer definition
uint8_t tx_buff[]={0,1,2,3,4,5,6,7,8,9};
uint8_t rx_buff[10];
• Sending and receiving methods

HAL_UART_Receive_IT(&huart1,rx_buff,10);
HAL_UART_Transmit_IT(&huart1,tx_buff,10);
• Complete callback check

• We can put brakepoints on NOPs to watch if we send or receive complete buffer

void HAL_UART_RxCpltCallback(UART_HandleTypeDef *huart)
{
__NOP();//test if we reach this position
}
void HAL_UART_TxCpltCallback(UART_HandleTypeDef *huart)

{
__NOP();//test if we reach this position
}
2.1.3 UART DMA lab

2.1.3 Use UART with DMA transfer 163
• Objective
• Learn how to setup UART with DMA in CubeMX
• Create simple loopback example with DMA
• Goal
• Learn how to send and receive data over UART with DMA

• Pin selection
• It will be same as previous lab we use again PA9 and PA10
Hardware
loopback


• CubeMX USART configuration check:

• BaudRate
• World length
• Parity
• Stop bits
• Data direction
• Oversampling
• CubeMX USART configuration DMA settings

• TAB>DMA Settings
• Button ADD
• CubeMX USART configuration DMA Tx settings

• Set USART1_TX request
• Memory to peripheral direction
• Normal mode
• Byte data width
• Increment memory address
• CubeMX USART configuration DMA Rx settings

• Button ADD
• Set USART1_RX request
• Peripheral to memory direction
• Normal mode
• Byte data width
• Increment memory address
• CubeMX USART configuration NVIC settings

• Enable DMA2 interrupts for
USART1
• Button OK


HAL Library UART with DMA RX flow

including DMA stream initializations
Start process with DMA end of transfer

interrupt generation at end of process
HAL_UART_Receive_DMA
HAL_OK HAL_ERROR HAL_ERROR

DMA_Stream_IRQ
HAL_DMA_IRQHandler
Handler



including DMA stream initializations Generated by CubeMX


DMA_Stream_IRQ
HAL_DMA_IRQHandler
Handler





DMA_Stream_IRQ
HAL_DMA_IRQHandler
Handler

Defined by user

Generated in main.c and
stm32f4xx_hal_msp.c

DMA_Stream_IRQ
HAL_DMA_IRQHandler
Handler





DMA_Stream_IRQ
HAL_DMA_IRQHandler
Handler

HAL_UART_RxCpltCallback We recommend to use it
in main.c




DMA_Stream_IRQ
HAL_DMA_IRQHandler
Handler

Generated in
stm32f4xx_it.c



DMA_Stream_IRQ
HAL_DMA_IRQHandler
Handler

Defined in
stm32f4xx_hal_dma.c and
then linked to
HAL_UART_ErrorCallback stm32f4xx_hal_uart.c

Receive buffer over UART
with DMA
Start process with DMA end of transfer program can continue

DMA_Stream_IRQ
HAL_DMA_IRQHandler
Handler



Peripheral Initializations Interrupt indicate the DMA
including DMA stream initializations receive half/complete
buffer or DMA error was
Start process with DMA end of transfer detected

DMA_Stream_IRQ
HAL_DMA_IRQHandler
Handler



Process interrupt
Start process with DMA end of transfer information from DMA and
interrupt generation at end of process UART

DMA_Stream_IRQ
HAL_DMA_IRQHandler
Handler





DMA_Stream_IRQ
HAL_DMA_IRQHandler
Handler

HAL_UART_RxCpltCallback If data buffer is full HAL
use Complete callback
function



DMA_Stream_IRQ
HAL_DMA_IRQHandler
Handler

HAL_UART_RxCpltCallback Or if DMA error was
detected use Error
callback function

Peripheral Initializations 1. UART1 and
including DMA stream initializations DMA2 init
Start process with DMA end of transfer 2. UART1

interrupt generation at end of process receive buffer

DMA_Stream_IRQ
HAL_DMA_IRQHandler
Handler
3. DMA buffer
4. Process
5. Buffer full
end of process callback interrupt
HAL_UART_RxCpltCallback received
process Error callback 5. Receive error



• HAL_UART_Transmit_DMA(UART_HandleTypeDef *huart, uint8_t *pData, uint16_t Size);

• HAL_UART_Receive_DMA(UART_HandleTypeDef *huart, uint8_t *pData, uint16_t Size);
uint8_t tx_buff[]={0,1,2,3,4,5,6,7,8,9};
• Sending and receiving methods with DMA

HAL_UART_Receive_DMA(&huart1,rx_buff,10);
HAL_UART_Transmit_DMA(&huart1,tx_buff,10);

• We can put breakpoints on NOPs to watch if we receive complete buffer

void HAL_UART_RxCpltCallback(UART_HandleTypeDef *huart)
{
__NOP();//check if we receive all data
}
2.2.1 SPI Poll lab

2.2.1 Simple SPI communication 191
• Objective
• Learn how to setup SPI in CubeMX
• Goal
• Configure SPI in CubeMX and Generate Code
• Learn how to send and receive data over SPI without interrupts

• Pin selection

• CubeMX SPI selection

• Select SPI1 Full-Duplex Master
• Select PA5, PA6, PA7 for SPI1 if weren't selected
• Connect PA6 and PA7 together with jumper
Hardware
loopback

• CubeMX SPI configuration

• Tab>Configuration>Connectivity>SPI1
• Check the settings
• Button OK
• The CLK frequency

with core on 180MHz
is now 45MHz
• For this clock use
HIGH GPIO speed
• CubeMX SPI – GPIO configuration

• The SPI CLK frequency
with core on 180MHz
is now 45MHz
• For this clock use
HIGH GPIO speed
• Tab>Configuration>System>
>GPIO
• Tab>SPI1
• Seth High output speed
• Button OK


HAL Library transmit receive flow

HAL_SPI_TransmitReceive Polling with timeout


• For transmit and receive use function

• HAL_SPI_TransmitReceive(SPI_HandleTypeDef *hspi, uint8_t *pTxData, uint8_t
*pRxData, uint16_t Size, uint32_t Timeout)
• Transmit receive solution

/* USER CODE BEGIN PV */
uint8_t tx_buffer[]={0,1,2,3,4,5,6,7,8,9};
uint8_t rx_buffer[10];
/* USER CODE END PV */
• Call transmit receive function
HAL_SPI_TransmitReceive(&hspi1,tx_buffer,rx_buffer,10,100);
2.2.2 SPI Interrupt lab

2.2.2 Use SPI with interrupt 203
• Objective
• Learn how to setup SPI with interrupts in CubeMX
• Goal
• Learn how to send and receive data over SPI with interrupts


Hardware
loopback


• Button OK

• Enable SPI interrupt
• Button OK


HAL Library SPI with IT transmit receive flow

initializations

of process
HAL_SPI_TransmitReceive_IT
HAL_OK HAL_ERROR HAL_BUSY HAL_SPI_IRQHandler SPI1_IRQHandler

HAL_SPI_TxRxCpltCallback

HAL_SPI_ErrorCallback


• HAL_SPI_TransmitReceive_IT(SPI_HandleTypeDef *hspi, uint8_t *pTxData, uint8_t
*pRxData, uint16_t Size)
uint8_t tx_buff[]={0,1,2,3,4,5,6,7,8,9};

HAL_SPI_TransmitReceive_IT(&hspi1,tx_buff,rx_buff,10);

• We can put breakpoints on NOPs to watch if we send or receive complete buffer

void HAL_SPI_TxRxCpltCallback(SPI_HandleTypeDef *hspi)
{
__NOP();
}
2.2.3 SPI DMA lab

2.2.3 Use SPI with DMA transfer 215
• Objective
• Learn how to setup SPI with DMA in CubeMX
• Goal
• Learn how to send and receive data over SPI with DMA


Hardware
loopback


• Button OK
• CubeMX SPI configuration DMA settings

• Button ADD
• SPI1_RX
• Memory increment
• Button ADD
• SPI1_Tx
• Button OK
• CubeMX SPI configuration NVIC settings

• Enable DMA2 interrupts for
SPI1
• Button OK


HAL Library SPI with DMA TX RX flow


HAL_SPI_TransmitReceive_DMA

DMA2_Stream0_IRQ
HAL_DMA_IRQHandler
Handler

HAL_SPI_TxRxCpltCallback

HAL_SPI_ErrorCallback


• HAL_SPI_TransmitReceive_DMA(SPI_HandleTypeDef *hspi, uint8_t *pTxData, uint8_t
*pRxData, uint16_t Size)
uint8_t tx_buff[]={0,1,2,3,4,5,6,7,8,9};

HAL_SPI_TransmitReceive_DMA(&hspi1,tx_buff,rx_buff,10);

• We can put breakpoints on NOPs to watch if we send or receive complete buffer

void HAL_SPI_TxRxCpltCallback(SPI_HandleTypeDef *hspi)
{
__NOP();
}
2.3.1 I2C Poll lab

2.3.1 Simple I2C communication 228
• Objective
• Learn how to setup i2C in CubeMX
• Work in pairs, one will create I2C transmitter and second I2C receiver
• Goal
• Configure I2C in CubeMX and Generate Code
• Learn how to send and receive data over I2C without interrupts


• Select I2C3 Periphery
• Select PA8, PC9 for I2C3 if weren't selected
• Connect together PA8 and PC9 pins from both boards, and GND
Hardware connection
PA8 <-> PA8
PC9<->PC9
• CubeMX I2C configuration

• Tab>Configuration>Connectivity>I2C3
• Define Slave address
to 20
• Button OK

• Tab>GPIO Settings
• Check Pull-UP
• Check GPIO speed
Check if the Pull-UP resistor are

necessary in case you are using
external one
Check the GPIO speed
This two parameters can limit
I2C maximum speed


/* Private variables
uint8_t data_tx[10]={1,2,3,4,5,6,7,8,9,0};
uint8_t data_rx[10];
• Master simple send and receive functions

HAL_Delay(100);
HAL_I2C_Master_Transmit(&hi2c3,20,data_tx,10,1000);
HAL_Delay(2);
HAL_I2C_Master_Receive(&hi2c3,20,data_rx,10,1000);
• Slave simple send and receive functions

status1=HAL_I2C_Slave_Receive(&hi2c3,data_rx,10,10000);
status2=HAL_I2C_Slave_Transmit(&hi2c3,data_rx,10,10000);
• During this example the SLAVE must begin the code execution first to be
prepared on MASTER Receive/Send requests
2.3.2 I2C Interrupt lab

2.3.2 Use I2C with interrupt 237
• Objective
• Learn how to setup I2C with interrupts in CubeMX
• Goal
• Configure I2C in CubeMX and Generate Code
• Learn how to send and receive data over I2C with interrupts


• Select I2C3 Periphery
• Select PA8, PC9 for I2C3 if weren't selected
• Connect together PA8 and PC9 pins from both boards, and GND
Hardware connection
PA8 <-> PA8
PC9<->PC9

• Tab>Configuration>Connectivity>I2C3
• Define Slave address
to 20
• Button OK

• Tab>GPIO Settings
• Check Pull-UP
• Check GPIO speed
Check if the Pull-UP resistor are

necessary in case you are using
external one
Check the GPIO speed
This two parameters can limit
I2C maximum speed

• Tab>NVIC settings
• Enable interrupts
• Button OK


/* Private variables
uint8_t data_tx[10]={1,2,3,4,5,6,7,8,9,0};
uint8_t data_rx[10];
• Master simple send and receive functions with interrupts

HAL_I2C_Master_Transmit_IT(&hi2c3,20,data_tx,10);
HAL_Delay(2);
HAL_I2C_Master_Receive_IT(&hi2c3,20,data_rx,10);
• Master callbacks
void HAL_I2C_MasterTxCpltCallback(I2C_HandleTypeDef *hi2c){}
void HAL_I2C_MasterRxCpltCallback(I2C_HandleTypeDef *hi2c){}
• Slave receive
HAL_I2C_Slave_Receive_IT(&hi2c3,data_rx,10);
• Slave transmit in callback

void HAL_I2C_SlaveTxCpltCallback(I2C_HandleTypeDef *hi2c){
}
void HAL_I2C_SlaveRxCpltCallback(I2C_HandleTypeDef *hi2c){

HAL_I2C_Slave_Transmit_IT(&hi2c3,data_rx,10);
}
2.3.3 I2C DMA lab

2.3.3 Use I2C with DMA transfer 247
• Objective
• Learn how to setup UART with DMA in CubeMX
• Goal
• Learn how to send and receive data over UART with DMA
3.1.1 Use RTC Alarm lab

3.1.1 Use RTC and Alarm with interrupt 249
• Objective
• Learn how to setup RTC with interrupt in CubeMX
• Create simple RTC project with periodic alarm interrupt
• Goal
• Use CubeMX and Generate Code with RTC
• Learn how to setup the RTC in HAL
• Verify the correct functionality by periodic RTC alarm interrupts

• Set Internal Alarm on Alarm A or Alarm B

• Set GPIO to toggle with LED as alarm indication

• RTC Configuration
• Control > RTC
1. TAB > Configuration
• Set parameters which you want
2. RTC
3. Check configuration
• RTC Configuration NVIC

1. TAB > NVIC
• TAB>NVIC Setup
• Enable Alarm interrupt
• Button OK
2. Enable RTC Alarm
3. Button OK


• The RTC can be preserved during RESET(ok LP modes)

• CubeMX not enable the RTC by default
• We need to add HAL_PWR_EnableBkUpAccess() and __HAL_RCC_RTC_ENABLE() before
we call MX_RTC_Init()
• Set the first alarm to 1s

• In MX_RTC_Init
• We create the RTC interrupt handler and we reconfigure the Alarm A time
• HAL_RTC_AlarmAEventCallback(RTC_HandleTypeDef *hrtc)
• HAL_RTC_GetAlarm(RTC_HandleTypeDef *hrtc, RTC_AlarmTypeDef *sAlarm, uint32_t Alarm,
uint32_t Format)
• HAL_RTC_SetAlarm_IT(RTC_HandleTypeDef *hrtc, RTC_AlarmTypeDef *sAlarm, uint32_t
Format)
• RTC alarm indication will be done by LED

• HAL_GPIO_TogglePin(GPIO_TypeDef* GPIOx, uint16_t GPIO_Pin)
• RTC enable
/* Initialize all configured peripherals */
HAL_PWR_EnableBkUpAccess();//enable PWR backup domain access (RTC,BKReg)
__HAL_RCC_RTC_ENABLE();//Enable RTC. not created by cube because the RTC can run.
MX_GPIO_Init();
MX_RTC_Init();
• In MX_RTC_Init we set first Alarm to 1s
/**Enable the Alarm A

*/
sAlarm.AlarmTime.Hours = 0;
sAlarm.AlarmTime.Minutes = 0;
sAlarm.AlarmTime.Seconds = 1;
sAlarm.AlarmTime.SubSeconds = 0;
• RTC enable
void HAL_RTC_AlarmAEventCallback(RTC_HandleTypeDef *hrtc){
RTC_AlarmTypeDef sAlarm;
HAL_RTC_GetAlarm(hrtc,&sAlarm,RTC_ALARM_A,FORMAT_BIN);
if(sAlarm.AlarmTime.Seconds>58){
sAlarm.AlarmTime.Seconds=0;
}else{
sAlarm.AlarmTime.Seconds=sAlarm.AlarmTime.Seconds+1;
}
while(HAL_RTC_SetAlarm_IT(hrtc, &sAlarm, FORMAT_BIN)!=HAL_OK){}
HAL_GPIO_TogglePin(GPIOG,GPIO_PIN_14);
}
• Advanced task
• The counting stops after 1minute
• Modify the project to create alarm every 1s for infinite time
/**Enable the Alarm A
*/
sAlarm.AlarmTime.Hours = 0;
sAlarm.AlarmTime.Minutes = 0;
sAlarm.AlarmTime.Seconds = 1;
sAlarm.AlarmTime.SubSeconds = 0;
sAlarm.AlarmTime.TimeFormat = RTC_HOURFORMAT12_AM;
sAlarm.AlarmTime.DayLightSaving = RTC_DAYLIGHTSAVING_NONE;
sAlarm.AlarmTime.StoreOperation = RTC_STOREOPERATION_RESET;
sAlarm.AlarmMask = RTC_ALARMMASK_DATEWEEKDAY|RTC_ALARMMASK_HOURS|RTC_ALARMMASK_MINUTES;
sAlarm.AlarmSubSecondMask = RTC_ALARMSUBSECONDMASK_ALL;
sAlarm.AlarmDateWeekDaySel = RTC_ALARMDATEWEEKDAYSEL_DATE;
sAlarm.AlarmDateWeekDay = 1;
sAlarm.Alarm = RTC_ALARM_A;
HAL_RTC_SetAlarm_IT(&hrtc, &sAlarm, FORMAT_BCD);
• We only need to modify the Alarm mask to ignore Days, Hours and Minutes
3.2.1 TIM with interrupt lab

3.2.1 Use TIM with interrupt 260
• Objective
• Learn how to setup TIM with Interrupt in CubeMX
• Indicate TIM interrupt with LED toggle
• Goal
• Configure TIM in CubeMX and Generate Code
• Learn how start timer and handle interrupt

• CubeMX TIM selection

• Select TIM clock source Internal clock
• Enable GPIO for LED PG14
• CubeMX TIM configuration

• Tab>Configuration>Control>TIM1

• Tab>Parameter Settings
• Prescaler to 18000
• Counter period to 10000
• Together with 180MHz TIMER1
clock we get period 1Hz

• Tab>NVIC Settings
• Enable TIM1 Update interrupt
• Button OK


HAL Library TIM with IT flow

TIM Initializations
initializations

of process
HAL_TIM_Base_Start_IT
HAL_OK HAL_ERROR HAL_BUSY HAL_TIM_IRQHandler TIM1_UP_TIM10_IRQHandler
process callback
HAL_TIM_PeriodElapsedCallback

HAL_TIM_ErrorCallback

• For TIM start use function

• HAL_TIM_Base_Start_IT(TIM_HandleTypeDef *htim)
• TIM callback
• void TIM1_UP_TIM10_IRQHandler(void)
• GPIO LED toggle

• Solution
• TIM start
HAL_TIM_Base_Start_IT(&htim1);
• Callback handling
void HAL_TIM_PeriodElapsedCallback(TIM_HandleTypeDef *htim)
{
}
3.2.2 TIM with PWM output lab

3.2.2 Use TIM with PWM output 270
• Objective
• Learn how to setup TIM with PWM out in CubeMX
• Indicate TIM PWM on LED
• Goal
• Learn how start timer and set PWM out
• Verify the correct functionality with LED


• Select TIM clock source - Internal clock
• Set Channel1 to PWM generation

>Control>TIM1
• TAB>Parameter settings
• PWM pulse to 5000 this give
us 1Hz blinking frequency


• Start process TIM with PWM(same for DMA, ADC)

Peripheral
Initializations
Start Process
HAL_TIM_PWM_Start


• HAL_TIM_PWM_Start(TIM_HandleTypeDef *htim, uint32_t Channel)
• GPIO LED toggle

• We wire the Channel1 PE9 with LED PG14
• Solution
• TIM PWM start
HAL_TIM_PWM_Start(&htim1,TIM_CHANNEL_1);
• TIM1 Channel 1 and LED connection
3.2.3 TIM with DMA lab

3.2.3 Use TIM with DMA transfer 278
• Objective
• Learn how to setup TIM with DMA in CubeMX
• Indicate TIM DMA transfer with LED toggle
• Goal
• Learn how start timer and setup DMA
• Verify the correct functionality with DMA transfer into GPIO register


• Select TIM clock source Internal clock



• Button ADD
• Select TIM1_UP DMA request
• Memory to peripheral direction
• Set Memory increment
• Circular mode
• Half word data width
• Button OK


HAL Library TIM with DMA flow
Start process with DMA

HAL_DMA_Start
Start process with TIM

HAL_TIM_Base_Start



• HAL_TIM_Base_Start_DMA(TIM_HandleTypeDef *htim, uint32_t *pData, uint16_t
Length)
• TIM1 trigger DMA transfer

• __HAL_TIM_ENABLE_DMA
• DMA start function

• HAL_DMA_Start(DMA_HandleTypeDef *hdma, uint32_t SrcAddress, uint32_t
DstAddress, uint32_t DataLength)
• GPIO LED register address

• (uint32_t)(&GPIOG->ODR)
• Variable data definition

uint16_t data[]={GPIO_PIN_14,0x0000};
• DMA and TIM start

__HAL_TIM_ENABLE_DMA(&htim1, TIM_DMA_UPDATE);
HAL_DMA_Start(&hdma_tim1_up,(uint32_t)data,(uint32_t)&GPIOG->ODR,2);
HAL_TIM_Base_Start(&htim1);
3.2.4 TIM as counter lab

3.2.4 Use TIM as pulse counter 288
• Objective
• Learn how to setup TIM as counter in CubeMX
• Indicate TIM count 5 button press with LED toggle
• Goal
• Configure TIM as counter in CubeMX and Generate Code
• Learn how start timer and handle interrupt
• Verify the correct functionality with LED toggle after 5 button press


• Select TIM clock source ETR2
• Hard ware setting

• Connect Button PA0 and ETR pin PE7 with wire together


• Counter set to 5, 5 button press
• Clock set the ETR pin filter and
edge reaction

• Tab>NVIC Settings
• Enable TIM1 Update interrupt
• Button OK


HAL Library TIM with IT flow

TIM Initializations
initializations

of process
HAL_TIM_Base_Start_IT
HAL_OK HAL_ERROR HAL_BUSY HAL_TIM_IRQHandler TIM1_UP_TIM10_IRQHandler
process callback
HAL_TIM_PeriodElapsedCallback

HAL_TIM_ErrorCallback


• HAL_TIM_Base_Start_IT(TIM_HandleTypeDef *htim)
• TIM callback
• void TIM1_UP_TIM10_IRQHandler(void)
• GPIO LED toggle

• Solution
• TIM start
HAL_TIM_Base_Start_IT(&htim1);
• Callback handling
void HAL_TIM_PeriodElapsedCallback(TIM_HandleTypeDef *htim)
{
}
3.3.1 WWDG lab

3.3.1 Use WWDG 299
• Objective
• Learn how to setup WWDG in CubeMX
• Create simple application to test WWDG
• Goal
• Configure WDGin in CubeMX and Generate Code
• Learn how to start WWDG
• WWDG indication via LED
3.3.1 Use WWDG 300

• CubeMX WWDG selection

• Select WWDG
• Configure PG14 for LED indication
3.3.1 Use WWDG 301

• CubeMX WWDG selection

• Select WWDG
3.3.1 Use WWDG 302

3.3.1 Use WWDG 303
• CubeMX ADC configuration

>WWDG>Parameter Settings
• Set prescaller to 8
• WWDG window to 80
• And free running counter to 127
• Button OK
3.3.1 Use WWDG 304


3.3.1 Use WWDG 305
• How calculate the window APB1freq=45MHz, prescaller 8
twwdg min  f APB1* 4096*NWWDG_PRESCALLER*(N REFRESH  NWINDOW ) 

1
( 6
)* 4096*8*( 127-80 )  34.2ms
45*10
1
twwdg max  ( 6
) * 4096 * 8 * (127 - 63)  46.6ms
45 *10
We refresh the
WWDG to 127
In our case 80
Fixed 63
3.3.1 Use WWDG 306
• Solution
• WWDG Start

HAL_WWDG_Start(&hwwdg);
• WWDG refresh
/* Infinite loop */
while (1)
{
//30ms or 50ms is outside the WWDG window, 40ms fits inside the window
HAL_Delay(40);
HAL_WWDG_Refresh(&hwwdg, 127);
}
3.3.2 IWDG lab

3.3.2 Use IWDG 308
• Objective
• Learn how to setup IWDG in CubeMX
• Create simple application to test IWDG
• Goal
• Configure IWDG in CubeMX and Generate Code
• Learn how to start IWDG
• IWDG indication via LED
3.3.2 Use IWDG 309

• CubeMX IWDG selection

• Select IWDG
3.3.2 Use IWDG 310

3.3.2 Use IWDG 311

>IWDG>Parameter Settings
• Set prescaller to 4
• Max value to 50
• Button OK
3.3.2 Use IWDG 312


3.3.2 Use IWDG 313
• IWDG refresh interval

1 1
t iwdg  * PIWDG _ PRESCALLER * N IWDG _ COUNTERVAL  ( 3
) * 4 * 50  6.25ms
f LSI 32 *10
3.3.2 Use IWDG 314
• Solution
• IWDG Start

HAL_IWDG_Start(&hiwdg);
• IWDG refresh
/* Infinite loop */
while (1)
{
HAL_Delay(7);//try delay 6ms and 7ms
HAL_GPIO_WritePin(GPIOG,GPIO_PIN_14,GPIO_PIN_SET);
HAL_IWDG_Refresh(&hiwdg);
}
3.3.2 Use IWDG 315
• Hardware IWDG
• Remove IWDG start from project

• Use ST-Link utility and enable IWDG Hardware start

3.3.2 Use IWDG 316
• Hardware IWDG
• Start ST-Link utility
• Menu>Target>Option bytes
or CTRL+B
• Uncheck the WDG_WS
• Button APPLY
• Now the IWDG is automatically started after reset
• !!! DO NOT FORGET disable

IWDG automatic start after
you end this example
4.1.1 DAC wave generator lab

4.1.1 Use DAC as wave generator 318
• Objective
• Learn how to setup DAC as wave generator in CubeMX
• Goal
• Configure DAC as wave generator in CubeMX and Generate Code
• Learn how start it in project

• CubeMX DAC selection

• Select DAC OUT2
• CubeMX DAC configuration

• TAB>Configuration>Analog>DAC>Parametr Settings
• Enable
Output buffer
• Button OK


• Start process DAC generation (same for DMA, ADC)

Peripheral
Initializations
Start Process
HAL_DAC_Start
Set value
HAL_DAC_SetValue

• and /* USER CODE BEGIN 3 */ and /* USER CODE END 3 */ tags
• For DAC start use function

• HAL_DAC_Start(DAC_HandleTypeDef* hdac, uint32_t Channel)
• DAC set DAC value

• HAL_DAC_SetValue(DAC_HandleTypeDef* hdac, uint32_t Channel, uint32_t Alignment,
uint32_t Data)
• Solution
• DAC setup and start
HAL_DAC_Start(&hdac,DAC_CHANNEL_2);
• Create the wave

/* Infinite loop */
while (1)
{
HAL_DAC_SetValue(&hdac, DAC_CHANNEL_2, DAC_ALIGN_12B_R, value_dac);
if(value_dac>4095)
{
value_dac=0;
}
HAL_Delay(1);
}
4.2.1 ADC Poll lab

4.2.1 Use ADC in polling mode 326
• Objective
• Use the DAC part from previous lab
• Learn how to setup ADC in CubeMX
• Goal
• Configure ADC in poll in CubeMX and Generate Code
• Learn how to start ADC and measure the DAC
• Verify the measured wave in STMStudio
(http://www.st.com/web/en/catalog/tools/PF251373 require JAVA)


• Select DAC OUT2
• Select ADC IN13
• Hardware connection
• Connect DAC out2 PA5 and ADC1 IN13 PC3 together

• TAB>Configuration>Analog>ADC1>Parametr Settings
• Set ADC1
• Set sampling time
for CH13
• Button OK
• DAC from previous

example


• Start process ADC(same for DMA, DAC, TIM)

Peripheral
Initializations
Start Process
HAL_DAC_Start
Peripheral
Initializations
Start Process
HAL_DAC_Start


• HAL_ADC_PollForConversion(ADC_HandleTypeDef* hadc, uint32_t Timeout)
• HAL_ADC_GetValue(ADC_HandleTypeDef* hadc)
• DAC functions
uint32_t Data)
• Solution
• Variables
uint32_t value_adc;
uint32_t value_dac=0;
• DAC setup and start

• Solution
• Main loop with DAC set and ADC set
/* Infinite loop */
while (1)
{
HAL_ADC_Start(&hadc1);
HAL_ADC_PollForConversion(&hadc1,10);
value_adc=HAL_ADC_GetValue(&hadc1);
value_dac++;
if(value_dac>4095){
value_dac=0;
}
HAL_Delay(1);
}
• Test the functionality

• We need the address of variable value_adc
• This can be found usually in debug mode in watch, my address is
0x2000005C (depends on compilator and optimizations)
• Start the STMStudio

• Set the ST Link SWD
• Right click into
Display variable
settings
• Select NEW
• STM studio settings

• Set value_adc address
my 0x2000005C
• Set 16bit unsigned val
• Right click on this line
• Select Send To
VarViewer1

• Viewers settings is on bottom
• Set the correct upper value
to 4096(12bit)

• Now press
green play button
• And you will see
content of
value_adc
4.2.2 ADC Interrupt lab

4.2.2 Use ADC with interrupt 340
• Objective
• Learn how to setup ADC with interrupt in CubeMX
• Goal
• Configure ADC in interrupt in CubeMX and Generate Code


• Select DAC OUT2
• Select ADC IN13

• TAB>Configuration>Analog>ADC1>Parametr Settings
• Set ADC1
for CH13
• Button OK

example

• TAB>NVIC settings
• Enable ADC1 interrupt
• Button OK
• CubeMX NVIC configuration

• Because we want use the
Systick for delay in interrupt
The ADC interrupt priority must
be changed
• TAB>Configuration>System>NVIC
• Change ADC1
preemption priority
to 1


HAL Library ADC with IT flow

ADCInitializations
initializations

of process
HAL_ADC_Start_IT
HAL_OK HAL_ERROR HAL_BUSY HAL_ADC_IRQHandler ADC_IRQHandler
process callback
HAL_ADC_ConvCpltCallback

HAL_ADC_ErrorCallback


• HAL_ADC_Start_IT(ADC_HandleTypeDef* hadc, uint32_t Channel)
• HAL_ADC_GetValue(ADC_HandleTypeDef* hadc)
• ADC complete callback function

• HAL_ADC_ConvCpltCallback(ADC_HandleTypeDef* hadc)
• DAC functions
uint32_t Data)
• Solution
• Variables
uint32_t value_adc;
• DAC setup and start ADC/DAC

HAL_ADC_Start_IT(&hadc1);
• Solution
• ADC complete callback routine
void HAL_ADC_ConvCpltCallback(ADC_HandleTypeDef* hadc)
{
value_adc=HAL_ADC_GetValue(&hadc1);
value_dac++;
if(value_dac>4095){
value_dac=0;
}
HAL_Delay(1);
HAL_ADC_Start_IT(&hadc1);
}

• Check functionality
again with
STMstudio
4.2.3 ADC with DMA lab

4.2.3 Use ADC with DMA 352
• Objective
• Learn how to setup ADC with DMA in CubeMX
• Goal
• Configure ADC in DMA in CubeMX and Generate Code


• Select DAC OUT2
• Select ADC IN13

• TAB>Configuration>Analog>ADC1>Parameter Settings
• Set ADC1
for CH13
• DMA Continuous requests
• Button OK

example

• Button ADD
• DMA request ADC1
• Peripheral to memory direction
• Circular mode
• Half word data width
• Button OK


HAL Library ADC with DMA flow

ADCInitializations
initializations

of process
HAL_ADC_Start_DMA
HAL_OK HAL_ERROR HAL_BUSY HAL_DMA_IRQHandler DMA1_StreamX_IRQHandler
process callback
HAL_ADC_ConvCpltCallback

HAL_ADC_ErrorCallback


• HAL_ADC_Start_DMA(ADC_HandleTypeDef* hadc, uint32_t* pData, uint32_t Length)
• DAC functions
uint32_t Data)
• Solution
• Variables
uint32_t value_adc;
• DAC setup and start ADC/DAC

HAL_ADC_Start_DMA(&hadc1,(uint32_t*)&value_adc,1);
• Solution
• ADC main routine
/* Infinite loop */
while (1)
{
value_dac++;
if(value_dac>4095){
value_dac=0;
}
HAL_Delay(5);
HAL_ADC_Start(&hadc1);
HAL_Delay(5);
}

• Check functionality
again with
STMstudio
5.1 BSP SDRAM lab

5.1 Use BSP for SDRAM initialization 363
• Objective
• Learn how import BSP into project
• Which part need to by configured in GUI
• Try to write data into SDRAM and read it
• Goal
• Successfully import BSP into your project
• Learn which part you need to import
• How to setup the project

• We need only blank project with clock initialization

• We only set the RCC and configure the core to maximum speed


• Now we have bank project

• For SDRAM we need to include more parts
Our project
BSP package
Discovery drivers
stm32f4xx_discovery.c stm32f4xx_discovery_sdram.c stm32f4xx_discovery_io.c
Components
ili9341.c lis3dsh.c stmpe811.c
HAL API
stm32f4xx_hal_spi.c
stm32f4xx_II_fmc.c stm32f4xx_hal_sdram.c stm32f4xx_hal.c
stm32f4xx_hal_i2c.c
BSP SDRAM organization
Our project
BSP package
Discovery drivers
Components
HAL API
stm32f4xx_hal_spi.c
stm32f4xx_hal_i2c.c

1. include
Our project stm32f4xx_discovery_sdram.h
BSP package
Discovery drivers
Components 2. include
stm32f4xx_discovery.h
HAL API
stm32f4xx_hal_spi.c
stm32f4xx_hal_i2c.c
Our project
BSP package 3. include stm32f4xx_hal.h
Discovery drivers
Components 4. stm32f4xx_hal.h include all

peripherals which are used in
ili9341.c lis3dsh.c stmpe811.c stm32f4xx_discovery.c
HAL API
stm32f4xx_hal_spi.c
stm32f4xx_hal_i2c.c
Our project
BSP package
Discovery drivers
Components 5. stm32f4xx_hal.h include all

peripherals which are used in
ili9341.c lis3dsh.c stmpe811.c stm32f4xx_discovery_sdram.c
HAL API
stm32f4xx_hal_spi.c
stm32f4xx_hal_i2c.c
Our project 6. HAL_SDRAM_Init

is function from
7. HAL_SDRAM_Init stm32f4xx_discovery_sdram.c
BSP package
call functions from
stm32f4xx_II_fmc.c Discovery drivers
Components
8. stm32f4xx_II_fmc.c use
ili9341.c lis3dsh.c stmpe811.c functions from
stm32f4xx_hal_sdram.c
HAL API
stm32f4xx_hal_spi.c
stm32f4xx_hal_i2c.c
Source files Include files

user_code.h
user_code.c
User Code
stm32f4xx_it.c stm32f4xx_it.h
Stm32f4xx_discovery.c Stm32f4xx_discovery.h
BSP Drivers Stm32ffxx_discovery_sdram.h
Stm32ffxx_discovery_sdram.c
stm32f4xx_hal.h
stm32f4xx_hal_ppp.c
stm32f4xx_hal_ppp_ex.c
HAL Drivers stm32f4xx_hal_conf.h
stm32f4xx_hal.c
stm32f4xx_hal_ppp.h
stm32f4xx_hal_ppp_ex.h
stm32f4xx_hal_def.h
• The copy part

• In our project in Drivers folder create folder BSP
• Now go into CubeMX repository …\STM32Cube_FW_F4_V1.3.0\Drivers\BSP\

• And copy Components and STM32F429I-Discovery into BSP folder
Copy folders into BSP

• Now we need to add this files also in project

• Create BSP folder in project
• Right click on project in Workplace>ADD>Group
• Name it BSP
• Now right click on BSP>ADD>Files
• From Drivers\BSP\STM32F429I-Discovery\
add stm32f429i_discovery.c
and stm32f429i_discovery_sdram.c
• The stm32f429i_discovery.c contains functions

for all components on discovery kit
(LCD, GYRO,…)
• Then we also need add into project HAL library
which handle their interface (I2C, SPI, … )
• Right click on STM32F4xx_HAL_Drive>ADD
from \Drivers\STM32F4xx_HAL_Driver\Src
• stm32f4xx_hal_i2c.c
• stm32f4xx_hal_spi.c
• stm32f4xx_hal_sdram.c
• stm32f4xx_II_fmc.c
• Now add the include paths for this new files

• Right click on project>Options>Category C/C++Compiler>Preprocesor
• Into Defined symbols add USE_STM32F429I_DISCO
• This allow use BSP functions
• Into additional includes add
$PROJ_DIR$\..\..\Drivers\BSP\STM32F429I-Discovery
• Button OK
• Button OK close project options
• Now last thing is allow to include

new HAL files which we added
• Open stm32f4xx_hal_conf.h in ..\Inc\
• Uncomment files which we added
• HAL_SDRAM_MODULE_ENABLED
• HAL_I2C_MODULE_ENABLED
• HAL_SPI_MODULE_ENABLED
• Into main.c now we add include of stm32f429i_discovery_sdram.h

/* USER CODE BEGIN Includes */
#include "stm32f429i_discovery_sdram.h"
/* USER CODE END Includes */
• Now we can use the SDRAM init functions from BSP
BSP_SDRAM_Init();
• Now you can try to write into SDRAM area

In stm32f429i_discovery_sdram.h you can find where is the SDRAM
memory and how is their size
• SDRAM_DEVICE_ADDR ((uint32_t)0xD0000000)
• SDRAM_DEVICE_SIZE ((uint32_t)0x800000) /* SDRAM device size in MBytes */
• SDRAM test
volatile uint32_t value;

BSP_SDRAM_Init();
*((uint32_t*)SDRAM_DEVICE_ADDR)=0x12345678;
value=*((uint32_t*)SDRAM_DEVICE_ADDR);
5.2 BSP LCD lab

5.2 Use BSP for LCD init and writing 381
• Objective
• Learn how import BSP LCD into project
• Because the LCD use the SDRAM we use project from lab 25
• Try to write text on LCD
• Goal
• Successfully import BSP LCD into your project
BSP LCD organization
Our project
BSP package
Discovery drivers
stm32f4xx_discovery.c stm32f4xx_discovery_lcd.c stm32f4xx_discovery_sdram.c
Components Utilities
ili9341.c lis3dsh.c stmpe811.c Fonts
HAL API
stm32f4xx_hal_sdram.c stm32f4xx_hal_spi.c
stm32f4xx_hal_ltdc.c stm32f4xx_hal.c
stm32f4xx_II_fmc.c stm32f4xx_hal_i2c.c

1. include
Our project stm32f4xx_discovery_lcd.h
BSP package
Discovery drivers
Components 2. stm32f4xx_discovery_lcd.h
Utilities
use the discovery BSP and
ili9341.c lis3dsh.c stmpe811.c SDRAM Fonts
HAL API
Our project
3. stm32f4xx_discovery_lcd.h
BSP package
use driver ili9341.c which is
TFT LCD controller Discovery drivers
use LCTD controller from HAL
HAL API
Our project
BSP package
Discovery drivers
use fonts from utility folder
HAL API
• We use the project from BSP SDRAM

because the LCD also use the SDRAM
• We need copy the Fonts from Utilities
folder in CubeMX repository
• The copy part

• In our project in Drivers folder create folder Utilities
• Now go into CubeMX repository …\STM32Cube_FW_F4_V1.3.0\Utilities\

• And copy Fonts into Utilities folder
Copy folders into

Utilities
• We add the driver for LCD from HAL

• Right click on STM32F4xx_HAL_Drive>ADD
from \Drivers\STM32F4xx_HAL_Driver\Src
• stm32f4xx_hal_ltdc.c
• Stm32f4xx_hal_dma2d.c
• We add the driver for BSP LDC

• Right click on BSP>ADD from \Drivers\BSP\STM32F429I-Discovery\
• stm32f429i_discovery_lcd.c
• Right click on BSP>ADD from \Drivers\BSP\Components\ili9341\

• ili9341.c
• Now last thing is allow to include

new HAL files which we added
• Open stm32f4xx_hal_conf.h in ..\Inc\
• Uncomment files which we added
• HAL_DMA2D_MODULE_ENABLED
• HAL_LTDC_MODULE_ENABLED
• Into main.c now we modify include from

stm32f429i_discovery_sdram.h to stm32f429i_discovery_lcd.h
#include "stm32f429i_discovery_lcd.h"
• And remove the BSP_SDRAM_Init()

• Simple LCD demonstration

BSP_LCD_Init();//init LCD
//set the layer buffer address into SDRAM
BSP_LCD_LayerDefaultInit(1, SDRAM_DEVICE_ADDR);
BSP_LCD_SelectLayer(1);//select on which layer we write
BSP_LCD_DisplayOn();//turn on LCD
BSP_LCD_Clear(LCD_COLOR_BLUE);//clear the LCD on blue color
BSP_LCD_SetBackColor(LCD_COLOR_BLUE);//set text background color
BSP_LCD_SetTextColor(LCD_COLOR_WHITE);//set text color
//write text
BSP_LCD_DisplayStringAtLine(2,"Cube STM32");
BSP_LCD_DisplayStringAtLine(3,"BSP");
BSP_LCD_DisplayStringAtLine(4,"LCD DEMO");
5.3 BSP EEPROM lab

5.3 Use BSP to access EEPROM 394
• Objective
• Learn how import BSP EEPROM into project
• We use the project from lab 26
• Try to write text into EEPROM and read it
• Read text from EEPROM and display it on LCD
• Goal
• Successfully import BSP EEPROM drivers into your project
BSP EEPROM organization
Our project
BSP package
Discovery drivers stm32f4xx_discovery_lcd.c
stm32f4xx_discovery_sdram.c
stm32f4xx_discovery_io.c stm32f4xx_discovery_eeprom.c
stm32f4xx_discovery.c
HAL API
stm32f4xx_II_fmc.c
stm32f4xx_hal_i2c.c

1. Use functions from
Our project
stm32f4xx_discovery_eeprom.c
BSP package
HAL API
stm32f4xx_II_fmc.c
stm32f4xx_hal_i2c.c

2. stm32f4xx_discovery_eeprom.c
call functions from Our project
stm32f4xx_discovery_io.c
BSP package
3. stm32f4xx_discovery_io.c call
Components functions from Utilities

pin init and write/read functions Fonts
HAL API
stm32f4xx_II_fmc.c
stm32f4xx_hal_i2c.c
Our project
BSP package
Components 4. stm32f4xx_discovery.c Utilities

Use stm32f4xx_hal_i2c to
commutate with eeprom memory
HAL API
stm32f4xx_II_fmc.c
stm32f4xx_hal_i2c.c
• We use the project from BSP LCD lab 26

because we want to display the memory
content on LCD

• stm32f429i_discovery_eeprom.c
• stm32f429i_discovery_io.c
• Add the define of EEPROM into project options

• Right click on project>Options>Category C/C++Compiler>Preprocesor
• Into Defined symbols add EE_M24LR64
• This allow use EEPROM functions
• Button OK close project options
• Use the ATM7-M24LR-A board with M24LR memory

and connect it into STM32F429i-Discovery kit
• Into main.c now modify include

#include "stm32f429i_discovery_io.h"
#include "stm32f429i_discovery_eeprom.h"
#include <string.h>
• Define variables
uint8_t text_to_write[]="test text";//write to eeprom
uint8_t text_to_read[200];//read from eeprom
uint32_t address=0;//address in eeprom
uint16_t read_num=1;//number of bytes which we want to read from
eeprom
• Into stm32f4xx_hal_it.c add global variable for i2c handle

extern I2C_HandleTypeDef I2cHandle;
• and define handler functions for I2C DMA

void DMA1_Stream4_IRQHandler()
{
HAL_DMA_IRQHandler(I2cHandle.hdmatx);
}
void DMA1_Stream2_IRQHandler()
{
HAL_DMA_IRQHandler(I2cHandle.hdmarx);
}
• Into main.c add

/*LCD init*/
BSP_LCD_Init();
BSP_LCD_SelectLayer(1);
BSP_LCD_DisplayOn();
BSP_LCD_Clear(LCD_COLOR_BLUE);
BSP_LCD_SetBackColor(LCD_COLOR_BLUE);
BSP_LCD_SetTextColor(LCD_COLOR_WHITE);
/*EEPROM init*/
BSP_EEPROM_Init();
/*Write text into EEPROM*/
BSP_EEPROM_WriteBuffer(text_to_write,0,(strlen(text_to_write)+1));
/*Read text from EEPROM*/
do{
BSP_EEPROM_ReadBuffer((uint8_t*)&(text_to_read[address]),address,(uint16_t*)&read_num);
}while(text_to_read[address++]!=0x0);
/*Display text*/
BSP_LCD_DisplayStringAtLine(2,text_to_read);
5.4 BSP GYRO lab

5.4 Use BSP to access GYROSCOPE 407
• Objective
• Learn how import BSP GYROSCOPE into project
• We use the project from lab 26
• Read data from GYROSCOPE and display it on LCD
• Goal
• Successfully import BSP GYROSCOPE drivers into your project
BSP GYRO organization
Our project
BSP package
stm32f4xx_discovery_io.c stm32f4xx_discovery_gyroscope.c
HAL API
stm32f4xx_II_fmc.c
stm32f4xx_hal_i2c.c

1. Use functions from
Our project
stm32f4xx_discovery_eeprom.c
BSP package
HAL API
stm32f4xx_II_fmc.c
stm32f4xx_hal_i2c.c

2. stm32f4xx_discovery_gyroscope.c
call functions from Our project
stm32f4xx_discovery_io.c
BSP package
3. stm32f4xx_discovery_io.c call
Components functions from Utilities

pin init and read functions Fonts
HAL API
stm32f4xx_II_fmc.c
stm32f4xx_hal_i2c.c
Our project
BSP package
Components 4. stm32f4xx_discovery.c Utilities

Use stm32f4xx_hal_spi to
commutate with gyroscope
HAL API
stm32f4xx_II_fmc.c
stm32f4xx_hal_i2c.c
• We use the project from BSP LCD lab 26

because we want to display gyro values
on LCD

• stm32f429i_discovery_gyroscope.c
• stm32f429i_discovery_io.c
• Right click on BSP>ADD from \Drivers\BSP\Components\

• l3gd20.c
• Into main.c now modify include

#include "stm32f429i_discovery_gyroscope.h"
#include "stm32f429i_discovery_io.h"
#include <stdio.h>
• Define variables
float valxyz[3];//gyroscope values
uint8_t buffer[200];//text buffer
• Into main.c add

/*LCD init*/
BSP_LCD_Init();
BSP_LCD_SelectLayer(1);
BSP_LCD_DisplayOn();
BSP_LCD_Clear(LCD_COLOR_BLUE);
BSP_LCD_SetBackColor(LCD_COLOR_BLUE);
BSP_LCD_SetTextColor(LCD_COLOR_WHITE);
/*Gyroscope init*/
BSP_GYRO_Init();
• Into main.c add

/* Infinite loop */
while (1)
{
/*Get Gyrospope value*/
BSP_GYRO_GetXYZ(valxyz);
/*Display X*/
sprintf(buffer,"x:%f",valxyz[0]);
BSP_LCD_DisplayStringAtLine(2,buffer);
/*Display Y*/
sprintf(buffer,"y:%f",valxyz[1]);
/*Display Z*/
sprintf(buffer,"z:%f",valxyz[2]);
/*Delay*/
HAL_Delay(1000);
}
Appendix A CubeMX install

A CubeMX install 418
• CubeMX tool
• http://www.st.com/web/catalog/tools/FM147/CL1794/SC961/SS1533/PF259242?s_searchtype=
partnumber
• The CubeMX tool need the java

• Please check if you have actual java on your pc, for sure 32bit and 64bit version
• Optionally you can download the Cube packages for STM32 device if you
don’t want to download them throe CubeMX
• STM32CubeL0
• STM32CubeL1
• STM32CubeF0
• STM32CubeF2
• STM32CubeF3
• STM32CubeF4
• Install the CubeMX

• After installation run CubeMX
• In case you download the package from web we need to find the place where
they need to be stored
• MENU>Help>Updater Settings…
• You will see where is the repository folder
• Default is C:/User/Acc_name/STM32Cube/Repository/
• You need to download STM32 packages into this folder

• Or CubeMX automatically download them into this folder
• The comparison of the CubeMX repository settings and structure in this folder
• In case you want to download this files

automatically use in CubeMX
• MENU>Help>Install New Libraries
• Select libraries which you want
• Force download with button Install Now
• For the code generation the CubeMX use the package from the Repository
folder
• The CubeMX can generate the code for some GUI
• Keil
• IAR
• Atollic
• For the debugging is necessity to have the ST-Link drivers

• STSW-LINK003 driver for Win XP/Vista/7
• STSW-LINK006 driver for Win 8
• For driver installation you will need the Admin rights on your PC
Appendix B Documents

B CubeMX documentation 423
• CubeMX user manual UM1718

• http://www.st.com/st-web-
ui/static/active/en/resource/technical/document/user_manual/DM00104712.pdf
• CubeMX release note RN0094

• CubeMX technical note TN0072

ui/static/active/en/resource/technical/document/technical_note/CD00214439.pdf
B STM32F4 documentation 424
• STM32F429ZI web page

• http://www.st.com/web/en/catalog/mmc/FM141/SC1169/SS1577/LN1806/PF255419#
• STM32F429 Datasheet
• http://www.st.com/st-web-ui/static/active/en/resource/technical/document/datasheet/DM00071990.pdf
• STM32F429 Reference Manual

ui/static/active/en/resource/technical/document/reference_manual/DM00031020.pdf
• STM32F429 Programming manual

ui/static/active/en/resource/technical/document/programming_manual/DM00046982.pdf
STM32F429i-Discovery
B documentation
425
• STM32F429i-Discovery page
• http://www.st.com/web/en/catalog/tools/FM116/SC959/SS1532/LN1848/PF259090?s_searchtyp
e=keyword
• STM32F429i-Discovery user manual with discovery schematics

www.st.com/stm32

STM32F4 Labs

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

STM32F4 Labs

Uploaded by

Copyright:

Available Formats

STM32F4 Labs

T.O.M.A.S – Technically Oriented Microcontroller Application Services

1. GPIO & EXTI (1.1)

1. FMC SDRAM BSP lab (5.1)

STM32F42xx Technical Training 02/08/2016

• Create project in CubeMX

• Configure LED pin as GPIO_Output

• For debug purpose is recommended to select debug pins

Clock Configuration overview 10

1. Set HSE crystal

2. CubeMX reserve pins

• In order to run on maximum frequency, setup clock system

• GPIO(Pin) output speed configuration

GPIO output LOW speed GPIO output MEDIUM speed

GPIO output FAST speed GPIO output HIGH speed

• Now we set the project details for generation

• Now we can Generate Code

• Now we open the project in our IDE

• For toggling we need to use this functions

• Now we open the project in our IDE

• For toggling we need to use this functions

/* USER CODE BEGIN 3 */

HAL_GPIO_WritePin(GPIOG, GPIO_PIN_14, GPIO_PIN_RESET);

STM32F42xx Technical Training 02/08/2016

• Create project in CubeMX

• Configure LED pin as GPIO_Output

• Create project in CubeMX

• Configure LED pin as GPIO_Output

• In order to run on maximum frequency, setup clock system

• Now we set the project details for generation

• Now we can Generate Code

HAL Library work flow 1

Edge detection callback

HAL Library work flow 2

Edge detection callback

HAL Library working flow 3

Edge detection callback

HAL Library work flow 4

Configure the GPIO to generate interrupt on

Edge detection callback

User must define Callback

HAL Library work flow 5

Configure the GPIO to generate interrupt on

Edge detection callback

Usually in main.c between

HAL Library work flow summary

Edge detection callback

• Now we open the project in our IDE

• The HAL callback function for EXTI

• For LED turn on we need to use this functions

• Now we open the project in our IDE

• The HAL callback function for EXTI

• For LED turn on we need to use this functions

/* USER CODE BEGIN 4 */

STM32F42xx Technical Training 02/08/2016

HAL Library work flow summary

Edge detection callback

• Now we open the project in our IDE

• Function to enter SLEEP

• Now we open the project in our IDE

• Function to enter SLEEP

/* USER CODE BEGIN 3 */