commit | c9058e66b10d3907cf5050e505a6c4b55103e70f | [log] [tgz] |
---|---|---|
author | Jonathon Reinhart <jrreinhart@pigweed.infra.roller.google.com> | Fri May 03 01:02:55 2024 +0000 |
committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri May 03 01:02:55 2024 +0000 |
tree | 4c6e9abd1c01ad2501564f726ba92633d73ee905 | |
parent | 0f5e9826d1332aa8dd7ff2910d239dd3e6b26aa0 [diff] |
[roll third_party/pigweed] pw_digital_io_linux: Remove OwnedFd::operator=(int fd) There is no need to assign a raw int fd to an existing OwnedFd object. This also prevents the bug where assigning {} actually assigns fd=0, which is not the intent. Instead, we explicitly use Close(). Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/207832 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> https://pigweed.googlesource.com/pigweed/pigweed third_party/pigweed Rolled-Commits: 9818527a8610c7a..9cbecdc781e3706 Roller-URL: https://ci.chromium.org/b/8749002461745129169 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: If376e9526c72a3e545d8c589c61aff3fa1a49971 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/208020 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Commit-Queue: 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!