Google Git
Sign in
chromium / chromiumos / platform / hps-firmware / refs/heads/factory-ambassador-14265.B
commit801df2541634795541431d0eeaf61c5710f5f621[log] [tgz]
authorJakub Mlynarczyk <jakubm@chromium.org>Tue Oct 05 03:24:35 2021
committerCommit Bot <commit-bot@chromium.org>Tue Oct 05 03:39:08 2021
tree6e7850e189a5b2a4939e05cba336b9f9c911b098
parent38eb80f2f19a13a81c9b5929e24e21e7f745574a [diff]
third_party: Update TFLM with CFU-Playground HPS ops (part 2)

Forgot to amend very important change in path...
It was building locally, but I did not notice that missing file.

BUG=b:200217830
TEST=scripts/soc-load --build; scripts/proto2-run;
scripts/proto2-mon (classification on);
scripts/pyrun scripts/proto2-term

Change-Id: I1b5b93e0eaa7f5ebcb473c1e9071cb288da0df89
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/hps-firmware/+/3203722
Tested-by: Jakub Młynarczyk <jakubm@chromium.org>
Reviewed-by: Dan Callaghan <dcallagh@chromium.org>
Reviewed-by: Alan Green <avg@chromium.org>
Commit-Queue: Jakub Młynarczyk <jakubm@chromium.org>
1 file changed
tree: 6e7850e189a5b2a4939e05cba336b9f9c911b098
  1. buildtools/
  2. docs/
  3. mcu_rom/
  4. scripts/
  5. soc/
  6. soc_rom/
  7. third_party/
  8. toolchain/
  9. .clang-format
  10. .gitignore
  11. .gitmodules
  12. .gn
  13. BUILD.gn
  14. BUILDCONFIG.gn
  15. environment
  16. LICENSE
  17. OWNERS
  18. PRESUBMIT.cfg
  19. pylintrc
  20. README.md
README.md

ChromiumOS HPS

See design document

Initial Setup

  1. Run the setup script. This will set up git submodules and prompt to install missing packages.

    1. ./scripts/setup

  2. To install Radiant you can try to run directly from CLI the extracted binary. In some cases this may fail with “Floating point exception.” error.

    In that case run: `./2.2.0.97.3_Radiant_lin.run --console --prefix ~/lscc/radiant/2.2`

Analogously for any update binaries available.
    1. Set RADIANT_DIR to the path where it is installed. e.g. in your .bashrc, you might add:
      1. export RADIANT_DIR=$HOME/lscc/radiant/2.2/bin/lin64
    2. Run sudo ~/lscc/radiant/2.2/programmer/data/vmdata/udevsetup_ubuntu (or one of the other udevsetup scripts) to correctly configure USB subsystem for Radiant.

Building and programming:

Editing code

If your editor has IDE features for Python (e.g. vscode with the Python extension installed), then you should open it with the appropriate environment variables set. e.g.:

(source environment; code .)