Arm Keil MDK v6 Essential and Professional editions are now available to buy as monthly or annual subscriptions from our Developer Tools store. Visit the store to get access to the tools suite today!

  1. Packs
  2. STM32F769I-EVAL_BSP

STM32F769I-EVAL_BSP

The STMicroelectronics STM32F769I-EVAL Board Support Pack (BSP):

Content in csolution format

Provided API Interface Description
CMSIS_ETH CMSIS-Driver Ethernet connected to Ethernet RJ45 connector (CN9)
CMSIS_MCI CMSIS-Driver MCI connected to microSD card slot (CN17)
CMSIS_USB_Device CMSIS-Driver USB Device connected to USB OTG1 FS connector (CN13)
CMSIS_USB_Host CMSIS-Driver USB Host connected to USB OTG2 HS connector (CN8)
CMSIS_VIO CMSIS-Driver VIO connected to LEDs (LD3, LD1, LD4, LD2) and Tamper button (B2)
STDIN, STDOUT, STDERR Standard I/O connected to Virtual COM port on ST-LINK connector (CN22)

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 select compiler: 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 disable Generate Under Root.
  • Click GENERATE CODE to recreate the CubeMX generated files for the GCC compiler.

  • In the Board.clayer.yml file, update linker: node configuration to reference appropriate GCC linker script. The GCC linker script is typically generated in the STM32CubeMX/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.