roll: third_party/pigweed pw_spi_mcuxpresso: Implement proper fix for fsl_spi_dma v2.2.2 This reverts fce05b3e882d31419edce031d4f62f2d0cfece3c. That previous attempt misunderstood the problem: SPI_SlaveTransferGetCountDMA() was _not_ changed to return the number of bytes remaining. Rather, a bug was introduced in v2.2.2 which caused it to return an incorrect value. That bug, coupled with the previous change, resulted in McuxpressoResponder always assuming that all bytes had been been transferred. The SDK bug is caused by the following line in SPI_MasterTransferDMA() being lost in v2.2.2: handle->transferSize = xfer->dataSize; See https://github.com/nxp-mcuxpresso/mcuxsdk-core/issues/19 handle->transferSize is only used by SPI_MasterTransferGetCountDMA() so this omission was probably not obvious and didn't affect any other code paths. To work around this bug, we simply set handle_.transferSize ourselves before calling SPI_SlaveTransferDMA(). Original-Bug: 449001277 Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/340992 Original-Revision: 0741a19a69cafa0b6bb64fcb3525bb27fec3a400 Rolled-Repo: https://pigweed.googlesource.com/pigweed/pigweed Rolled-Commits: 1f42b7bed7acb1..0741a19a69cafa Roll-Count: 1 Roller-URL: https://cr-buildbucket.appspot.com/build/8699013936067749201 GitWatcher: ignore CQ-Do-Not-Cancel-Tryjobs: true Change-Id: I16597956023e716be2e0cb91e080c456189a4889 Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/examples/+/341192 Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com> Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com> Bot-Commit: 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.