- Packs
- STM32L562E-DK_BSP
STM32L562E-DK_BSP
2.0.0-
Pack Type
Board Support
STMicroelectronics STM32L5 Series STM32L562E-DK Board Support Pack
-
Add to CMSIS Solution
packs:
- pack: Keil::STM32L562E-DK_BSP@2.0.0
Add with cpackget
> cpackget add Keil::STM32L562E-DK_BSP@2.0.0
Download
STM32L562E-DK_BSP 2.0.0STM32L562E-DK_BSP
The STMicroelectronics STM32L562E-DK Board Support Pack (BSP):
- Contains examples in csolution format for usage with the CMSIS-Toolbox and the VS Code CMSIS Solution extension.
- Requires the Device Family Pack (DFP) for the STM32L5 series.
- Is configured with STM32CubeMX for the Arm Compiler 6 (MDK).
Content in csolution format
-
Examples/Blinky shows the basic usage of this board.
-
Board Layer for device-agnostic Reference Applications that implements these API interfaces:
Provided API Interface Description CMSIS_MCI CMSIS-Driver MCI connected to microSD card slot (CN1) CMSIS_USART CMSIS-Driver USART connected to Pmod™ pins 2S1, 3S1 (CN4) CMSIS_USB_Device CMSIS-Driver USB Device connected to User USB connector (CN15) CMSIS_VIO CMSIS-Driver VIO connected to LEDs (LD9, LD10) and USER button (B2) STDIN, STDOUT, STDERR Standard I/O connected to Virtual COM port on ST-LINK connector (CN17) ARDUINO_UNO_D2..D10, D14..D19 CMSIS-Driver GPIO connected to Arduino digital I/O pins D2..D10 and D14..D19 ARDUINO_UNO_I2C CMSIS-Driver I2C connected to Arduino I2C pins D20..D21 ARDUINO_UNO_SPI CMSIS-Driver SPI connected to Arduino SPI pins D11..D13 ARDUINO_UNO_UART CMSIS-Driver USART connected to Arduino UART pins D0..D1 Using GCC Compiler
By default the Board Layers are configured for the Arm Compiler 6 (AC6). Using STM32CubeMX it can be reconfigured for a different compiler. To configure it for the GCC compiler execute these steps:
- In the
<solution_name>.csolution.yml
project file selectcompiler: GCC
. - Launch the STM32CubeMX generator with this CMSIS-Toolbox command:
csolution <solution_name>.csolution.yml run -g CubeMX -c <context>
- In STM32CubeMX:
- Open from the menu
Project Manager - Project - Toolchain/IDE
: - Select
STM32CubeIDE
and disableGenerate Under Root
. -
Click
GENERATE CODE
to recreate the CubeMX generated files for the GCC compiler. -
In the
Board.clayer.yml
file, updatelinker:
node configuration to reference appropriate GCC linker script. The GCC linker script is typically generated in theSTM32CubeMX/STM32CubeIDE
folder. Customize the GCC linker script file to your project's requirements. - Rebuild the project using the CMSIS-Toolbox command
cbuild <solution_name>.csolution.yml
.