[roll third_party/pigweed] pw_build: GN template to evaluate expressions in a file

Pigweed's GN build wraps all invocations of a Python script with a
Python runner. One of the runner's main purposes is to determine the
binary outputs of GN libraries and executables, as this information
is not available through GN itself.

Sometimes, it is cumbersome or unfeasible to pass information to a
script through its command line arguments. Instead, the necessary
data is often written to a file for the script to parse. However,
doing so from within GN bypasses Pigweed's Python runner binary
resolution. `bloat.py` is an example of this -- it needed to import
and run the resolution logic itself.

This adds a template which runs GN binary resolution on files, enabling
the above use case more generally through the build system.

Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/108990

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 566dda4bd355bd3..60498cb65400f90
Roller-URL: https://ci.chromium.org/b/8802375993736992049
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I77241571b817ad8dea96901c10270a9d2c2b6cfc
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/experimental/+/111430
Commit-Queue: Pigweed Integration Roller <pigweed-integration-roller@pigweed.google.com.iam.gserviceaccount.com>
Bot-Commit: Pigweed Integration Roller <pigweed-integration-roller@pigweed.google.com.iam.gserviceaccount.com>
1 file changed
tree: e4b02f8bded0ea83d6e9e962f342a945efe8af74
  1. applications/
  2. build_overrides/
  3. infra/
  4. pw_board_led/
  5. pw_board_led_arduino/
  6. pw_board_led_host/
  7. pw_board_led_pico/
  8. pw_board_led_stm32cube/
  9. pw_board_led_stm32f429i_disc1/
  10. pw_graphics/
  11. pw_spin_delay/
  12. pw_spin_delay_arduino/
  13. pw_spin_delay_host/
  14. pw_spin_delay_pico/
  15. pw_spin_delay_stm32cube/
  16. pw_spin_delay_stm32f429i_disc1/
  17. targets/
  18. third_party/
  19. tools/
  20. .gitattributes
  21. .gitignore
  22. .gitmodules
  23. .gn
  24. activate.bat
  25. banner.txt
  26. bootstrap.bat
  27. bootstrap.sh
  28. BUILD.gn
  29. BUILDCONFIG.gn
  30. env_setup.json
  31. navbar.md
  32. OWNERS
  33. PW_PLUGINS
  34. README.md
README.md

Pigweed Experimental

This repository contains experimental pigweed modules.

Repository setup

Clone this repo with --recursive to get all required submodules.

git clone --recursive https://pigweed.googlesource.com/pigweed/experimental

This will pull the Pigweed source repository into third_party/pigweed. If you already cloned but forgot to --recursive run git submodule update --init to pull all submodules.

pw_graphics

The //pw_graphics folder contains some libraries for drawing to an RGB565 framebuffer and displaying it on various platforms.

The demo applications that make use of these libraries are:

Build instructions

First time setup:

git clone --recursive https://pigweed.googlesource.com/pigweed/experimental
cd experimental
. ./bootstrap.sh
pw package install imgui
pw package install glfw
pw package install stm32cube_f4
pw package install pico_sdk

STM32F429-DISC1

Compile:

gn gen out --export-compile-commands --args="
  dir_pw_third_party_stm32cube_f4=\"$PW_PROJECT_ROOT/environment/packages/stm32cube_f4\"
"
ninja -C out

Flash:

openocd -f third_party/pigweed/targets/stm32f429i_disc1/py/stm32f429i_disc1_utils/openocd_stm32f4xx.cfg -c "program out/stm32f429i_disc1_stm32cube_debug/obj/applications/terminal_display/bin/terminal_demo.elf verify reset exit"

Linux, Windows or Mac

Compile:

gn gen out --export-compile-commands --args="
  dir_pw_third_party_imgui=\"$PW_PROJECT_ROOT/environment/packages/imgui\"
  dir_pw_third_party_glfw=\"$PW_PROJECT_ROOT/environment/packages/glfw\"
"
ninja -C out

Run:

out/host_debug/obj/applications/terminal_display/bin/terminal_demo

Raspberry Pi Pico Connected to an external SPI display

Working displays:

Compile:

gn gen out --export-compile-commands --args="
  PICO_SRC_DIR=\"$PW_PROJECT_ROOT/environment/packages/pico_sdk\"
"
ninja -C out

Flash:

  • Using a uf2 file:

    ./out/host_debug/obj/targets/rp2040/bin/elf2uf2 ./out/rp2040/obj/applications/terminal_display/bin/terminal_demo.elf ./out/rp2040/obj/applications/terminal_display/bin/terminal_demo.uf2
    

    Copy ./out/rp2040/obj/applications/terminal_display/bin/terminal_demo.uf2 to your Pi Pico.

  • Using a Pico Probe and openocd:

    This requires installing the Raspberry Pi foundation's OpenOCD fork for the Pico probe. More details including how to connect the two Pico boards is available at Raspberry Pi Pico and RP2040 - C/C++ Part 2: Debugging with VS Code

    Install RaspberryPi's OpenOCD Fork:

    git clone https://github.com/raspberrypi/openocd.git \
      --branch picoprobe \
      --depth=1 \
      --no-single-branch \
      openocd-picoprobe
    
    cd openocd-picoprobe
    
    ./bootstrap
    ./configure --enable-picoprobe --prefix=$HOME/apps/openocd --disable-werror
    make -j2
    make install
    

    Setup udev rules (Linux only):

    cat <<EOF > 49-picoprobe.rules
    SUBSYSTEMS=="usb", ATTRS{idVendor}=="2e8a", ATTRS{idProduct}=="0004", MODE:="0666"
    KERNEL=="ttyACM*", ATTRS{idVendor}=="2e8a", ATTRS{idProduct}=="0004", MODE:="0666"
    EOF
    sudo cp 49-picoprobe.rules /usr/lib/udev/rules.d/49-picoprobe.rules
    sudo udevadm control --reload-rules
    

    Flash the Pico:

    ~/apps/openocd/bin/openocd -f ~/apps/openocd/share/openocd/scripts/interface/picoprobe.cfg -f ~/apps/openocd/share/openocd/scripts/target/rp2040.cfg -c 'program out/rp2040/obj/applications/terminal_display/bin/terminal_demo.elf verify reset exit'