| commit | 6112b488b60bee1c72b3b57893a2119b45f74709 | [log] [tgz] |
|---|---|---|
| author | Aaron Green <aarongreen@pigweed.infra.roller.google.com> | Wed May 29 16:23:50 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed May 29 16:23:50 2024 +0000 |
| tree | 4cbe4c7dc7ad13b053ac6cc657bb0d7dbb442621 | |
| parent | e0ae9c5a74d7a4ed604e9b2248b62d1191b34e14 [diff] |
[roll third_party/pigweed] pw_allocator: Add BlockAllocator::MeasureFragmentation This CL adds a Fragmentation type that provide the sum of squares of and sum of the inner sizes of free blocks. If this information is provided to a platform with floating point support (e.g. host unit tests, over RPC, etc.), it can be used to calculate a fragmentation metric: Frag = 1 - sqrt(sum_of_squares)/sum Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/209933 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: 69fa240add6d3f3..9edec04e128ec8d Roller-URL: https://ci.chromium.org/b/8746589015346249313 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Ide7ccf8a1048e54c90befaafa3733d804d7c71dc Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/211974 Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Commit-Queue: 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!