| commit | 9a965cc7e7caa438e8b940cc9534bc475ca7caf1 | [log] [tgz] |
|---|---|---|
| author | Austin Foxley <afoxley@pigweed.infra.roller.google.com> | Tue Sep 24 22:58:13 2024 +0000 |
| committer | CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Sep 24 22:58:13 2024 +0000 |
| tree | a393fb069acf8a305ece16c0ddcd2b52dbae4e34 | |
| parent | 5e9e52cb2f75fc748f630f7344ccb78139fd1153 [diff] |
roll: third_party/pigweed pw_uart_mcuxpresso: Simplify configuration struct - Utilize the pw_dma_mcuxpresso module to manage DMA channels. - Directly query flexcomm clock freq after the clock is turned on during init. Also fix const application in pw_dma_mcuxpresso that arm compiler in mac CI didn't like and looked like a mistake anyways. This was needed to dma_uart_example.cc could compile. Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/236919 Original-Revision: ca679a238320e25cdf6649e74dcb76af21e2beb9 Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: a4dab0be18a649..ca679a238320e2 Roller-URL: https://ci.chromium.org/b/8735874310189115841 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: Iaebb32fd2bc247e2f633ff2e53d1e9ac61d1072e Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/237735 Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
This repository outlines the recommended way of using Pigweed in a new or existing project. Feel free to fork this repository, or read it as a reference.
For more information see the Pigweed Getting started guide.
Check back for more complex examples and features coming soon!
Make sure you've set up Pigweed's prerequisites.
If you're on Windows, you can automate the initial setup by downloading the first-time setup script from cmd.exe:
curl https://pigweed.googlesource.com/pigweed/sample_project/+/main/tools/setup_windows_prerequisites.bat?format=TEXT > setup_pigweed_prerequisites.b64 && certutil -decode -f setup_pigweed_prerequisites.b64 setup_pigweed_prerequisites.bat && del setup_pigweed_prerequisites.b64
Then you can run the script with the following command in cmd.exe:
setup_pigweed_prerequisites.bat
Note: You may see a few UAC prompts as the script installs Git, Python, and enables developer mode.
Once that is done, you can clone this project with the following command:
git clone https://pigweed.googlesource.com/pigweed/sample_project
Pigweed uses a local development environment for most of its tools. This means tools are not installed to your machine, and are instead stored in a directory inside your project (Note: git ignores this directory). The tools are temporarily added to the PATH of the current shell session.
To make sure the latest tooling has been fetched and set up, run the bootstrap command for your operating system:
Windows
bootstrap.bat
Linux & Mac
source ./bootstrap.sh
After tooling updates, you might need to run bootstrap again to ensure the latest tools.
After the initial bootstrap, you can use use the activate scripts to configure the current shell for development without doing a full update.
Windows
activate.bat
Linux & Mac
source ./activate.sh
All of these commands must be run from inside an activated developer environment. See Environment setup
To build the project, documentation, and tests, run the following command in an activated environment:
pw build
Alternatively, if you'd like an automatic rebuild to trigger whenever you save changes to files, use pw watch:
pw watch
When you pull latest repository changes, run bootstrap:
source ./bootstrap.sh
If you're just launching a new shell session, you can activate instead:
source ./activate.sh
and rebuild with:
pw build
Extended documentation and examples are built along code changes. You can view them at out/gn/docs/gen/docs/html/index.html.