[pentest] Fix the GDB penetration tests to accommodate for the FPGA bkdr_loader flow
Nobody has claimed this yet.
- Dominant language
- SystemVerilog
- Stars
- 3.6k
- Forks
- 1.1k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 141
Description
Description
After #30543 was merged, the GDB penetration tests are unlikely to continue working properly on master. That PR adds the necessary functionality for all the penetration tests to be able to take a passed in ROM and OTP image and load it via the backdoor loader flow (mimicking the FPGA test implementation in the Bazel opentitan_test flow) - but the Bazel plumbing to actually provide these values to the Python test scripts has not been completed.
This only impacts tests that will actually need to clear and reload the bitstream, which - from a cursory glance - appears to just be the GDB FI penetration tests. These should be investigated and fixed the next time that we need them to be working properly.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the GDB FI penetration tests and the Python test scripts affected by the backdoor loader changes in #30543. Compare their Bazel setup with the FPGA implementation in the Bazel opentitan_test flow, focusing on how ROM and OTP images are provided. Done means the affected tests can clear and reload the bitstream through the bkdr_loader flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- security, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100