[mask_rom] Add mask ROM ePMP functional test

Adds a test ROM that shares the same ePMP configuration as the mask
ROM. It takes about 30-60s to execute in verilator on my laptop.

The test attempts to execute code in RAM, eFlash and the read-only
part of the ROM to check that instruction access faults are
generated correctly. It also tests that the region unlocked by
a call to `mask_rom_epmp_unlock_rom_ext_rx` is correct.

Blocking unwanted execution is the primary purpose of the ePMP module.
For now the test does not check other types of access are allowed
or blocked. It may be desirable to add other tests for these
accesses (e.g. a stack overflow test for the stack guard) later.

The test is unusual in that it executes from ROM and does not
communicate any status information until the test is over (because
the address space used by DV is blocked by the ePMP configuration
that is being tested).

Disabling the ePMP setup code results in the following output:

```
I00000 mask_rom_epmp_test.c:358] Starting MaskROM ePMP functional test.
E00001 mask_rom_epmp_test.c:363] CHECK-fail: epmp_state_check(&epmp) == kErrorOk
E00002 mask_rom_epmp_test.c:251] CHECK-fail: execute(illegal_ins_ro, kExceptionInstructionAccessFault)
E00003 mask_rom_epmp_test.c:263] CHECK-fail: execute(illegal_ins_rw, kExceptionInstructionAccessFault)
E00004 mask_rom_epmp_test.c:275] CHECK-fail: execute(&eflash[0], kExceptionInstructionAccessFault)
E00005 mask_rom_epmp_test.c:276] CHECK-fail: execute(&eflash[eflash_len - 1], kExceptionInstructionAccessFault)
E00006 mask_rom_epmp_test.c:283] eflash execution not blocked @ 0x20000418
E00007 mask_rom_epmp_test.c:331] CHECK-fail: epmp_state_check(epmp) == kErrorOk
E00008 mask_rom_epmp_test.c:342] CHECK-fail: execute(&image[-1], kExceptionInstructionAccessFault)
E00009 mask_rom_epmp_test.c:343] CHECK-fail: execute(&image[image_len], kExceptionInstructionAccessFault)
E00010 mask_rom_epmp_test.c:378] CHECK-fail: epmp_unlock_test_status(&epmp)
I00011 test_status.c:34] FAIL!
```

Signed-off-by: Michael Munday <mike.munday@lowrisc.org>
4 files changed
tree: 50942264dea80c7b59b9928347a159db4a65e194
  1. .github/
  2. ci/
  3. doc/
  4. hw/
  5. site/
  6. sw/
  7. test/
  8. util/
  9. .clang-format
  10. .dockerignore
  11. .flake8
  12. .gitignore
  13. .style.yapf
  14. .svlint.toml
  15. .svls.toml
  16. _index.md
  17. apt-requirements.txt
  18. azure-pipelines.yml
  19. check_tool_requirements.core
  20. CLA
  21. COMMITTERS
  22. CONTRIBUTING.md
  23. LICENSE
  24. meson.build
  25. meson_init.sh
  26. meson_options.txt
  27. python-requirements.txt
  28. README.md
  29. tool_requirements.py
  30. toolchain.txt
  31. topgen-generator.core
  32. topgen-reg-only.core
  33. topgen.core
  34. yum-requirements.txt
README.md

OpenTitan

OpenTitan logo

About the project

OpenTitan is an open source silicon Root of Trust (RoT) project. OpenTitan will make the silicon RoT design and implementation more transparent, trustworthy, and secure for enterprises, platform providers, and chip manufacturers. OpenTitan is administered by lowRISC CIC as a collaborative project to produce high quality, open IP for instantiation as a full-featured product. See the OpenTitan site and OpenTitan docs for more information about the project.

About this repository

This repository contains hardware, software and utilities written as part of the OpenTitan project. It is structured as monolithic repository, or “monorepo”, where all components live in one repository. It exists to enable collaboration across partners participating in the OpenTitan project.

Documentation

The project contains comprehensive documentation of all IPs and tools. You can access it online at docs.opentitan.org.

How to contribute

Have a look at CONTRIBUTING and our documentation on project organization and processes for guidelines on how to contribute code to this repository.

Licensing

Unless otherwise noted, everything in this repository is covered by the Apache License, Version 2.0 (see LICENSE for full text).