Google Git
Sign in
pigweed / pigweed / quickstart / bazel / d0d8596cb72c7b20e603adee3aa7ce473619c24b
commitd0d8596cb72c7b20e603adee3aa7ce473619c24b[log] [tgz]
authorpigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>Wed Aug 07 23:22:09 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Aug 07 23:22:09 2024 +0000
treeba25c1c59c3e87327ed75bd420b1c94c8ae274df
parentfd09669a92ecea9612848052c0b76bbf6b55ca06 [diff]
roll: pigweed, pw_toolchain: pw_toolchain: Clang support for Arm Cortex-M33

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

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 1d487225d2e5fc6..04109d522e8b54b
Roller-URL: https://ci.chromium.org/b/8740220870553192513
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I0a864d7b6fca022303036b1dda816b2d154af09d
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/228280
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>
1 file changed
tree: ba25c1c59c3e87327ed75bd420b1c94c8ae274df
  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!