commit | d72e51cdf22c4b3e7b08b4a2c556e545a46ec128 | [log] [tgz] |
---|---|---|
author | Ted Pudlik <tpudlik@pigweed.infra.roller.google.com> | Fri Jun 21 01:42:40 2024 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jun 21 01:42:40 2024 +0000 |
tree | a99eefd84c65d80806c5ef322ce4b6dd058c9d00 | |
parent | c40cfeb6da41766309143b6b47f2251bd3a72446 [diff] |
roll: pw_toolchain, pw_toolchain: pw_presubmit: Build STM32F429i baremetal in CI This platform and config were added in http://pwrev.dev/214626, but prior to this CL there was no CI coverage of it. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/217231 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pw_toolchain, pw_toolchain Rolled-Commits: d9bba5855b72a9f..4b96f4d43938c31 Roller-URL: https://ci.chromium.org/b/8744560756668273377 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ib6eaeaeaab300f3b3ebd762ed1dc5df51c0f472c Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/217332 Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
This repository contains a minimal example of a Bazel-based Pigweed project. It's an echo application for the STM32F429 Discovery Board.
git clone --recursive https://pigweed.googlesource.com/pigweed/quickstart/bazel
If you already cloned but forgot to include --recursive
, run git submodule update --init
to pull all submodules.
TODO: b/300695111 - Don't require submodules for this example.
We‘ll assume you already have Bazel on your system. If you don’t, the recommended way to get it is through Bazelisk.
To build the entire project (including building the application for both the host and the STM32 Discovery Board), run
bazel build //...
To run the application locally on your machine, run,
bazel run //src:echo
To flash the firmware to a STM32F429 Discovery Board connected to your machine, run,
bazel run //tools:flash
Note that you don't need to build the firmware first: Bazel knows that the firmware images are needed to flash the board, and will build them for you. And if you edit the source of the firmware or any of its dependencies, it will get rebuilt when you flash.
Run,
bazel run //tools:miniterm -- /dev/ttyACM0 --filter=debug
to communicate with the board. When you transmit a character, you should get the same character back!