Google Git
Sign in
pigweed/pigweed/quickstart/bazel/00cf6b92889d227b805d4d2b222bb04153f4867b
commit
00cf6b92889d227b805d4d2b222bb04153f4867b
[log]
author
Alexei Frolov <frolv@pigweed.infra.roller.google.com>
Sat Jun 29 02:40:21 2024 +0000
committer
CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>
Sat Jun 29 02:40:21 2024 +0000
tree
4178e24cc92d7321df52c3095e185fd5f0c5da67
parent
fbcd595ae8b29f507aff2325e761227ad3db398d [diff]
roll: pigweed, pw_toolchain: pw_transfer: Don't assert on resource status responder

An RPC call can close for various reasons, such as a client requesting a
cancel or their channel shutting down. Code should never assert on RPC
call objects being open. This updates the GetResourceStatus RPC callback
to simply log an error if its responder object is no longer active.

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

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 62da50a4f4cb9b5..4200619994a4a8d
Roller-URL: https://ci.chromium.org/b/8743832773401697153
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ib32becb4a6343572087f1712af1107c40cb83341
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/218804
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: 4178e24cc92d7321df52c3095e185fd5f0c5da67
  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!