| commit | 8c352dc5dd026d470deda1671e091ff5cc147741 | [log] [tgz] |
|---|---|---|
| author | Keir Mierle <keir@google.com> | Sun Feb 02 13:58:19 2020 -0800 |
| committer | CQ Bot Account <commit-bot@chromium.org> | Mon Feb 03 23:21:15 2020 +0000 |
| tree | f81bcfd8135f682eb441a294690cfb2c7984ebad | |
| parent | de27674bc67c895e0b8c26bcfca63e31423d73e9 [diff] |
pw_kvs: Implement KVS load from flash This starts the implementation of loading the KVS from flash. Much remains to do before this is done. This patch also includes some extensions to how the tests are handled, to make it easier to instantiate multiple KVS and flash backends for testing. Changes is this CL to potentially split out: - KVS dump command to log contents - Re-enabling function and file display in log (useful!) - Hex dumping to log Change-Id: Ib1b25a01aa29eec3d3acd09e40205c23ded7bf6a
Pigweed is a collection of embedded-focused libraries, called “modules”. These modules are designed for small-footprint MMU-less microcontrollers like the ST Micro STM32L452 or the Nordic NRF82832. The modules are designed to facilitate easy integration into existing codebases.
Some Pigweed modules have been used in the development of Google’s first-party devices, including the Stadia Controller and Pixel Buds.
Pigweed is in the early stages of development, and should be considered experimental. We’re continuing to evolve the platform and add new modules. We value developer feedback along the way.
Pigweed is an open source project with a code of conduct that we expect everyone who interacts with the project to respect.
$ git clone sso://pigweed.googlesource.com/pigweed/pigweed ~/pigweed $ cd ~/pigweed $ env_setup/cipd/wrapper.py auth-login # Once per machine. $ . env_setup/bootstrap.sh
You can use . env_setup/env_setup.sh in place of . env_setup/bootstrap.sh. Both should work every time, but bootstrap.sh tends to remove and reinstall things at the expense of time whereas env_setup.sh tends to do basic checks to see if time can be saved by skipping expensive operations.
If you‘re using Homebrew and you get an error saying module 'http.client' has no attribute 'HTTPSConnection' then your Homebrew Python was not set up to support SSL. Ensure it’s installed with brew install openssl and then run brew uninstall python && brew install python. After that things should work.
The environment setup script will pull down the versions of tools necessary to build Pigweed and add them to your environment. You can then build with GN, CMake, or Bazel. You can also confirm you're getting the right versions of tools—they should be installed under .cipd/.
Build for the host with GN
$ which gn ~/pigweed/.cipd/pigweed.ensure/gn $ gn gen out/host $ ninja -C out/host
Build for the host with CMake
$ which cmake ~/pigweed/.cipd/pigweed.ensure/bin/cmake $ cmake -B out/cmake-host -S . -G Ninja $ ninja -C out/cmake-host
Build for the host with Bazel
$ which bazel ~/pigweed/.cipd/pigweed.ensure/bazel $ bazel test //...
Build for the STM32F429 Discovery board
$ gn gen --args='pw_target_config = "//targets/stm32f429i-disc1/target_config.gni"' out/disco $ ninja -C out/disco $ pw test --root out/disco/ --runner stm32f429i_disc1_unit_test_runner
The CMake and Bazel builds do not yet support building for hardware.
To flash firmware to an STM32 Discovery development board (and run pw test) from macOS, you need to install OpenOCD. Install Homebrew using the latest instructions at https://brew.sh/, then install OpenOCD with brew install openocd.
If any of this doesn't work please file a bug.