| commit | 3e7eca50357db335a19caeb6d0315ee44ade6df7 | [log] [tgz] |
|---|---|---|
| author | Rob Mohr <mohrr@pigweed.infra.roller.google.com> | Sat Aug 03 02:14:00 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sat Aug 03 02:14:00 2024 +0000 |
| tree | e29dbfe1309692d2df91bee6600a4447442c8a34 | |
| parent | dc4d4de3d60505b0f4eb88c4e0cb5c895aaf761a [diff] |
roll: pigweed, pw_toolchain: pw_presubmit: Fix incl-lang when not at repo root Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/227185 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: 474eecbbc9c11d0..61f8b7ee89ec9e4 Roller-URL: https://ci.chromium.org/b/8740663063460741761 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I46c73968f5f2e51524571c75fe4d20577ff81ef4 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/227531 Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.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!