Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ac_range_check,doc] Testplan for ac_range_check_smoke #26656

Open
martin-velay opened this issue Mar 18, 2025 · 0 comments · May be fixed by #26717
Open

[ac_range_check,doc] Testplan for ac_range_check_smoke #26656

martin-velay opened this issue Mar 18, 2025 · 0 comments · May be fixed by #26717
Assignees
Labels

Comments

@martin-velay
Copy link
Contributor

martin-velay commented Mar 18, 2025

After having mostly covered the smoke test with this PR #26513.

I wonder if the testplan for ac_range_check_smoke is correct:

# Stimulus Status
1 Assert range_check_overwrite_i to MuBi8False OK
2 Randomize RANGE_BASE and RANGE_LIMIT OK
3 Randomize RANGE_PERM and set the enable bit to 1 OK
4 Set read_perm and write_perm to 0xFFFF OK
5 TLUL requests where ... RACL role bit is set Does it matters for this smoke test as read_perm and write_perm are always 0xFFFF?
# Checks Status
6 If a request falls ... TLUL error is returned Could you elaborate on the expected TLUL error? Where is it expected to be reported?
7 Read requests return all zero as data Is it true? I think, the request should be filtered and noting should be returned at this level. No?
8 Read and Execute request return the expected data At block level, I believe any requests (R/W/X) should go through. Isn't it?
martin-velay added a commit to martin-velay/opentitan that referenced this issue Mar 24, 2025
- This PR is linked to issue lowRISC#26656.

Signed-off-by: Martin Velay <[email protected]>
martin-velay added a commit to martin-velay/opentitan that referenced this issue Mar 25, 2025
- This PR is linked to issue lowRISC#26656.

Signed-off-by: Martin Velay <[email protected]>
martin-velay added a commit to martin-velay/opentitan that referenced this issue Mar 25, 2025
- This PR is linked to issue lowRISC#26656.

Signed-off-by: Martin Velay <[email protected]>
martin-velay added a commit to martin-velay/opentitan that referenced this issue Mar 26, 2025
- This PR is linked to issue lowRISC#26656.

Signed-off-by: Martin Velay <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants