[third_party/pigweed] Roll 3 commits

1e0836bd99fd09a pw_allocator: Refactor optional Allocator methods
8b5396011e33fcb docs: Instructions for freertos.BUILD.bazel
38c302a47fda3b8 docs: Create files in current directory

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 4551fc59f3ea7e1..1e0836bd99fd09a
Roller-URL: https://ci.chromium.org/b/8747189541451032465
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I655c187049083fc888d2fec1b081958693b6c65f
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/211197
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: 57a4db75e0a2b163bdf151a6d39b0af9b6522beb
  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!