commit | 85635ac05aa85dac3d9c5f4a6e34395ce6510e94 | [log] [tgz] |
---|---|---|
author | pigweed-roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> | Sat Jul 13 18:03:09 2024 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sat Jul 13 18:03:09 2024 +0000 |
tree | 0ef24bf4ef1663209146c6c57561c8d8754d5082 | |
parent | 2c3240dcb247db57c434bcbb5cece92b68dd6220 [diff] |
roll: pigweed, pw_toolchain: pw_bluetooth_sapphire: Add more values to LEEventMask Add additional bit definitions (values [20,40]) to the LEEventMask enum. Test: fx test //src/connectivity/bluetooth/core/bt-host Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1010356 GitOrigin-RevId: 7413c861fa187e1f574cbecfb28adfb3b8b99c1b Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/221022 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed pigweed, pw_toolchain Rolled-Commits: b216eb7fb3a472d..f150ac17e8fde07 Roller-URL: https://ci.chromium.org/b/8742505908597928609 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I448b8ed7bb4af5f32c266c67266c9de141f6d64d Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/222865 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>
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!