Ada_Drivers_Library/boards
Maxim Reznik c45af336d0 Add missing `aliased` keywords in STM32_F4VE board
to allow `'Access` attributes
2023-12-20 18:23:27 +02:00
..
HiFive1 Move 'for Target use xxx;' up 2023-12-01 14:45:54 +02:00
HiFive1_rev_B Move 'for Target use xxx;' up 2023-12-01 14:45:54 +02:00
MicroBit Move 'for Target use xxx;' up 2023-12-01 14:45:54 +02:00
NRF52_DK Move 'for Target use xxx;' up 2023-12-01 14:45:54 +02:00
OpenMV2 Move 'for Target use xxx;' up 2023-12-01 14:45:54 +02:00
Unleashed Move 'for Target use xxx;' up 2023-12-01 14:45:54 +02:00
crazyflie Move 'for Target use xxx;' up 2023-12-01 14:45:54 +02:00
feather_stm32f405 Move 'for Target use xxx;' up 2023-12-01 14:45:54 +02:00
native Community 2021 (#386) 2021-05-26 12:24:22 +02:00
nucleo_f446ze Add FSMC for stm32f40X 2023-12-06 16:38:32 +02:00
stm32_common Split ili9341 into several files 2023-12-06 16:38:32 +02:00
stm32_f4ve Add missing `aliased` keywords in STM32_F4VE board 2023-12-20 18:23:27 +02:00
stm32_h405 Move 'for Target use xxx;' up 2023-12-01 14:45:54 +02:00
stm32f4xx_m Add TFT LCD ILI9341 to STM32 F4VE board. 2023-12-06 16:38:32 +02:00
stm32f407_discovery Add FSMC for stm32f40X 2023-12-06 16:38:32 +02:00
stm32f429_discovery Move 'for Target use xxx;' up 2023-12-01 14:45:54 +02:00
stm32f469_discovery Move 'for Target use xxx;' up 2023-12-01 14:45:54 +02:00
stm32f746_discovery Move 'for Target use xxx;' up 2023-12-01 14:45:54 +02:00
stm32f769_discovery Move 'for Target use xxx;' up 2023-12-01 14:45:54 +02:00
README.md Change the project architecture to emphasis both on device and board levels 2016-02-10 21:47:53 +01:00
board_projects_generator.py Switch to GNAT FSF 12 support (#418) 2023-01-02 11:34:55 +01:00

README.md

These projects represent specific implementations, "boards" such as the *_Discovery kit boards.

They include the peripheral declarations for their specific MCU device, such as the GPIO ports and timers on the F405 or F429, as well as declarations specific to that board, such as the LEDs.

Use one of these project if that is the specific target you are using.

Alternatively, if you have some platform that is based on a given MCU device but is not a specific board (e.g., not one of the *_Discovery boards), use the corresponding MCU device project instead. For example, the Crazyflie 2.0 uses an STM32F405, so project stm32f40x.gpr would be appropriate. With that approach the hardware that the *_Discovery boards include will not be available, such as the user buttons.