Google Git
Sign in
pigweed / pigweed / quickstart / bazel / d0896f6b521b8ecd96ce4c189468b1e1c808b111
commitd0896f6b521b8ecd96ce4c189468b1e1c808b111[log] [tgz]
authorTaylor Cramer <cramertj@pigweed.infra.roller.google.com>Sat May 18 04:14:52 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Sat May 18 04:14:52 2024 +0000
tree418faaadd4e7e7f8364d1328eef2decb68fea4d6
parent50be15e7154d5fafdc22a8a234ec1b3498341911 [diff]
[roll third_party/pigweed] rp2040_utils: Replace exceptions with logging

This change significantly reduces the log spam of the rp2040 utils by
replacing exceptions with error logs / sys exits. This prevents the
(usually unhelpful) Python stack trace from being printed as part of
error messages.

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

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: efcc36b25be8339..894f848bccb6dbb
Roller-URL: https://ci.chromium.org/b/8747631424047835521
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I143eb318c7555f08842e0cfca26410002ac379f8
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/210403
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>
1 file changed
tree: 418faaadd4e7e7f8364d1328eef2decb68fea4d6
  1. .github/
  2. src/
  3. targets/
  4. third_party/
  5. tools/
  6. .bazelrc
  7. .bazelversion
  8. .gitignore
  9. .gitmodules
  10. BUILD.bazel
  11. echo.bzl
  12. LICENSE
  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!