Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 70c40def5eb9be851049a2b9e02cbb471c19d099
commit70c40def5eb9be851049a2b9e02cbb471c19d099[log] [tgz]
authorTed Pudlik <tpudlik@pigweed.infra.roller.google.com>Fri Jun 28 02:43:03 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Jun 28 02:43:03 2024 +0000
treebae28245250ce51a3f5a2731efb01a0ed76a9df8
parenta20c2c0792aae45ffc41eed1d28c67df106b8c3f [diff]
roll: pigweed, pw_toolchain: pw_sys_io_stm32cube: Remove target_compatible_with

This is a step towards removing the associated constraint_value
altogether.

We don't need to replace it with anything, because the compatibility
restrictions flow from the dependency on `//third_party/stm32cube`.

Original-Bug: 347998044
Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/218704
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 77630d60f4d98ff..a75e7f2f295b7c6
Roller-URL: https://ci.chromium.org/b/8743922986719336577
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I4939c7e9dfd7468b3ff832e2f65ed14bdbb1c0ad
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/218778
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: bae28245250ce51a3f5a2731efb01a0ed76a9df8
  1. .github/
  2. src/
  3. targets/
  4. tools/
  5. .bazelignore
  6. .bazelrc
  7. .bazelversion
  8. .gitignore
  9. BUILD.bazel
  10. echo.bzl
  11. LICENSE
  12. pigweed.json
  13. README.md
  14. requirements.in
  15. requirements_lock.txt
  16. WORKSPACE
README.md

Pigweed: minimal Bazel example

This repository contains a minimal example of a Bazel-based Pigweed project. It's an echo application for the STM32F429 Discovery Board.

Cloning

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.

Building

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

Flashing

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.

Communicating

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!