| commit | 5a72b390622a801c4872308ad530a9e42a9dd29c | [log] [tgz] |
|---|---|---|
| author | Aaron Green <aarongreen@pigweed.infra.roller.google.com> | Wed May 22 16:18:12 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed May 22 16:18:12 2024 +0000 |
| tree | adc08df9a6c1c839b963a8afe60f59af6db6a5d5 | |
| parent | 759b8e573cf49ec19a41f12fa273972b511d9a37 [diff] |
[roll third_party/pigweed] pw_allocator: Reduce Block fragmentation This CL modifies how leading padding is handled when allocating aligned blocks. Previously, if padding was needed a block was always allocated, and the padding had to be at least the minimum block size. Now, if the padding needed is smaller than the minimum block size, the padding is instead appended to the previous block. This reduces fragmentation and leads to better space utilization. As part of this CL, the Block::*Alloc* methods have also been cleaned up according to a recent suggestions, e.g. simpilified to use Layouts. Original-Bug: 328831791 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/209538 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: 5e6b6c962de2402..c4cf469a53bed01 Roller-URL: https://ci.chromium.org/b/8747223530239282865 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I7c37efccb2c4d60d752ea5236b691e90039bbe13 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/211014 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>
This repository contains a minimal example of a Bazel-based Pigweed project. It's an echo application for the STM32F429 Discovery Board.
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.
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
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.
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!