Google Git
Sign in
pigweed / pigweed / quickstart / bazel / 213b66c1d478c8f3aab909594b42a86bdbb4290a
commit213b66c1d478c8f3aab909594b42a86bdbb4290a[log] [tgz]
authorAaron Green <aarongreen@pigweed.infra.roller.google.com>Wed Apr 24 15:56:41 2024 +0000
committerCQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Apr 24 15:56:41 2024 +0000
tree837c9775cd597bdc1fa4c5b5a219d7c79b51caa8
parent9d447e821a6ae0e2a44892529b9dda8553d35d07 [diff]
[roll third_party/pigweed] pw_allocator: Add BuddyAllocator

This allocator uses buddy memory allocation to allocate power-of-two
sized blocks.

Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/195952

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: e01ca5820679aeb..6f9099b2b688bf6
Roller-URL: https://ci.chromium.org/b/8749761662407924289
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I4c9fc988bb4020b2450ac9963a992df517ade313
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/206152
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: 837c9775cd597bdc1fa4c5b5a219d7c79b51caa8
  1. src/
  2. targets/
  3. third_party/
  4. tools/
  5. .bazelrc
  6. .bazelversion
  7. .gitignore
  8. .gitmodules
  9. BUILD.bazel
  10. echo.bzl
  11. LICENSE
  12. README.md
  13. requirements.in
  14. requirements_lock.txt
  15. 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!