Important Information for this Arm website

This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies. If you are not happy with the use of these cookies, please review our Cookie Policy to learn how they can be disabled. By disabling cookies, some features of the site will not work.

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. NUCLEO-F429ZI_BSP

NUCLEO-F429ZI_BSP

1.0.0
Keil

  • Pack Type

    Board Support

STMicroelectronics STM32F4 Series NUCLEO-F429ZI Board Support Pack

NUCLEO-F429ZI_BSP

The STMicroelectronics NUCLEO-F429ZI Board Support Pack (BSP):

Content in csolution format

Provided API Interface Description
CMSIS_ETH CMSIS-Driver Ethernet connected to Ethernet RJ45 connector (CN14)
CMSIS_USART CMSIS-Driver USART connected to ZIO pins D52..D53 (CN9)
CMSIS_USB_Device CMSIS-Driver USB Device connected to User USB connector (CN13)
CMSIS_VIO CMSIS-Driver VIO connected to LEDs (LD3, LD1, LD2) and USER button (B1)
STDIN, STDOUT, STDERR Standard I/O connected to Virtual COM port on ST-LINK connector (CN1)
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_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 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.