Google Git
Sign in
chromium / chromiumos / platform / hps-firmware / refs/heads/factory-14778.B
commitb42193a9b85b61a40c0dbff43a6378ccee89aa25[log] [tgz]
authorDan Callaghan <dcallagh@google.com>Mon May 02 06:14:04 2022
committerChromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon May 02 21:55:09 2022
tree9d66eebdf503c83bd7943a3097746479ebcecdbf
parent07c6831e82b156f887ef8f7c3ff9af7b2fe77e8a [diff]
PRESUBMIT.cfg: don't run Rust builds and tests

Don't run scripts/run-tests on every commit before upload.

The important stuff in that script is now covered by CQ (namely:
compiling HPS MCU firmware, FPGA firmware, host tools, and running Rust
unit tests and gateware unit tests) which is the best place for it.
Developers can continue to invoke scripts/run-tests or some more
specific test commands locally to validate their changes. But we don't
need to force everyone to do it on every commit.

BUG=b:215275939
TEST=repo upload

Change-Id: I16b33aacac559d2b2052ef984ed3d6548b3e3667
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/hps-firmware/+/3617828
Tested-by: Dan Callaghan <dcallagh@chromium.org>
Commit-Queue: Dan Callaghan <dcallagh@chromium.org>
Reviewed-by: David Lattimore <dml@chromium.org>
1 file changed
tree: 9d66eebdf503c83bd7943a3097746479ebcecdbf
  1. .vscode/
  2. bin/
  3. buildtools/
  4. docs/
  5. models/
  6. rust/
  7. scripts/
  8. soc/
  9. test_data/
  10. third_party/
  11. toolchain/
  12. .clang-format
  13. .gitignore
  14. .gitmodules
  15. .gn
  16. BUILD.gn
  17. BUILDCONFIG.gn
  18. DIR_METADATA
  19. environment
  20. LICENSE
  21. OWNERS
  22. PRESUBMIT.cfg
  23. pylintrc
  24. 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 .)