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

Most (all?) integration parameters are not in the RTL #278

Closed
steven-bellock opened this issue Nov 3, 2023 · 1 comment · Fixed by #279
Closed

Most (all?) integration parameters are not in the RTL #278

steven-bellock opened this issue Nov 3, 2023 · 1 comment · Fixed by #279
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@steven-bellock
Copy link
Contributor

Table 2 says

Parameter name Width Description
APB_ADDR_WIDTH 32 Width of the APB Address field. Default to 32.
APB_DATA_WIDTH 32 Width of the APB Data field. Default to 32.
APB_USER_REQ_WIDTH TODO Width of the APB PAUSER field.
CPTRA_SET_MBOX_PAUSER_INTEG 5 Each bit hardcodes the valid PAUSER for mailbox at integration time.
CPTRA_MBOX_VALID_PAUSER [4:0][31:0] Each parameter corresponds to a hardcoded valid PAUSER value for mailbox, set at integration time. Must set corresponding bit in the CPTRA_SET_MBOX_PAUSER_INTEG parameter for this valid pauser override to be used.
CPTRA_DEF_MBOX_VALID_PAUSER 32 Sets the default valid PAUSER for mailbox accesses. This PAUSER is valid when any VALID_PAUSER is unlocked or not set by INTEG parameter.
CPTRA_SET_FUSE_PAUSER_INTEG 1 Sets the valid PAUSER for fuse accesses at integration time.
CPTRA_FUSE_VALID_PAUSER 32 Overrides the programmable valid PAUSER for fuse accesses when CPTRA_SET_FUSE_PAUSER_INTEG is set to 1.

but, for example, APB_ADDR_WIDTH does not exist in the RTL.

@Nitsirks
Copy link
Contributor

Nitsirks commented Nov 3, 2023

Unfortunately these are spread around the design and not conveniently located for integrators. We will consolidate these into one place at the top wrapper level for a future release.

I will update the integration spec to fix the names and add where they exist.

@Nitsirks Nitsirks self-assigned this Nov 3, 2023
@Nitsirks Nitsirks added the documentation Improvements or additions to documentation label Nov 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants