Awesome

STM32H743I-EVAL_BSP

This is the development repository for the STMicroelectronics STM32H743I-EVAL Board Support Pack (BSP) - a CMSIS software pack that is designed to work with all compiler toolchains (Arm Compiler, GCC, IAR, LLVM). It is released as CMSIS software pack and therefore accessible by CMSIS-Pack enabled software development tools.

This BSP uses the generator integration of the CMSIS-Toolbox to Configure STM32 Devices with CubeMX that is also supported in µVision 5.40 and higher.

Repository top-level structure

Directory	Description
.ci	Files that are related to the Continuous Integration (CI) tests of this BSP.
.github/workflows	GitHub Actions scripts described below.
CMSIS/Driver	Contains a CMSIS-Driver VIO that is configured for the board peripherals.
Documents	Usage overview for examples and board documentation provided by STMicroelectronics.
Examples/Blinky	Blinky example in csolution project format using CMSIS-Driver VIO and CMSIS-Compiler for printf I/O retargeting.
Images	Pictures of the board.
Layers	Board layers for using the board with CMSIS-Toolbox - Reference Applications.

Using the development repository

This development repository can be used in a local directory and mapped as software pack using for example cpackget with:

cpackget add <path>/Keil.STM32H743I-EVAL_BSP.pdsc

Generate software pack

The software pack is generated using bash shell scripts.

./gen_pack.sh based on Open-CMSIS-Pack/gen-pack generates the software pack. Run this script locally with:
```
STM32H743I-EVAL_BSP $ ./gen_pack.sh
```

GitHub Actions

The repository uses GitHub Actions to generate the pack and build examples:

.github/workflows/pack.yml based on Open-CMSIS-Pack/gen-pack-action generates pack using the Generate software pack scripts.
.github/workflows/Test-Examples.yml test build of examples.
.github/workflows/Test-MDK-Middleware-RefApps.yml test build of MDK Middleware Reference Applications with different compilers.

Issues

Please feel free to raise an issue on GitHub to report misbehavior (i.e. bugs) or start discussions about enhancements. This is your best way to interact directly with the maintenance team and the community. We encourage you to append implementation suggestions as this helps to decrease the workload of the maintenance team.