Google Git
Sign in
chromium / chromiumos / platform / hps-firmware / refs/heads/stabilize-14324.41.B
commit6599ca7cbfcb1864648c29a13cca6eecbf86ffe8[log] [tgz]
authorJakub Mlynarczyk <[email protected]>Thu Nov 04 04:12:24 2021
committerCommit Bot <[email protected]>Thu Nov 04 11:06:09 2021
tree2bf2e2877063425d1244a66db2a8e8daabaafeba
parentb9008cf15c2525ad8907a620cb3cdadeb0bec4a6 [diff]
soc_rom: Remove FPGA's ability to read AE config

BUG=b:205045580
TEST=proto2-run; proto2-mon

Change-Id: I7612c3735334cc5829f52e334a209fad09c7fd40
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/hps-firmware/+/3260291
Tested-by: Jakub Młynarczyk <[email protected]>
Reviewed-by: David Lattimore <[email protected]>
Commit-Queue: Jakub Młynarczyk <[email protected]>
3 files changed
tree: 2bf2e2877063425d1244a66db2a8e8daabaafeba
  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 .)