| commit | f905d011d79364216b0ddcd1f2969f6c832655a6 | [log] [tgz] |
|---|---|---|
| author | Ted Pudlik <tpudlik@pigweed.infra.roller.google.com> | Sat Jul 27 00:42:43 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sat Jul 27 00:42:43 2024 +0000 |
| tree | a8da5e263b539ff3871f2ffc54dbbbf372cda0f2 | |
| parent | 4e37f4fb5cfb2092b528ae23d8e262dadac50649 [diff] |
roll: pigweed, pw_toolchain: bazel: Partial revert of http://pwrev.dev/226007 Revert the changes to the keys in the dicts in targets/rp2040/transition.bzl. Changing what strings appear as keys leads to issues in downstream projects that rely on overriding them. We still need to remove these "@pigweed" string instances, but need to tread more carefully. Will update the bug with ideas. NO_IFTTT=The values of the flags are not changed. Original-Bug: 352389854 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/226271 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: c605a3b205089cd..542cb9290ee366a Roller-URL: https://ci.chromium.org/b/8741303043712871761 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I2e70affbeed286aafa9773064f9f9da4b86f4ad4 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/226292 Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Commit-Queue: 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!