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.

Sign up for GitHub

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

Jump to bottom

Propagate non-default parameters down to OPAE axi top level #14

Open
johanpel opened this issue Jan 11, 2021 · 0 comments
Open

Propagate non-default parameters down to OPAE axi top level #14

johanpel opened this issue Jan 11, 2021 · 0 comments

Comments

@johanpel
Copy link

At the OPAE top level .sv file, there are two files included:

`include "ofs_plat_if.vh"
`include "afu_json_info.vh"

These may contain some interface parameters that we think can be changed.

It would be good if these parameters, as far as they are applicable, would be propagated to the Fletcher top level.

A trail of some preliminary investigation is:

https://github.com/OPAE/ofs-platform-afu-bbb/blob/master/plat_if_develop/ofs_plat_if/src/rtl/ofs_plat_if.vh ?
https://github.com/OPAE/ofs-platform-afu-bbb/blob/master/plat_if_develop/ofs_plat_if/src/rtl/ifc_classes/host_chan/afu_ifcs https://github.com/OPAE/ofs-platform-afu-bbb/tree/master/plat_if_develop/ofs_plat_if/src/rtl/base_ifcs/axi
https://github.com/OPAE/ofs-platform-afu-bbb/blob/master/plat_if_develop/ofs_plat_if/src/rtl/ifc_classes/host_chan
https://github.com/OPAE/intel-fpga-bbb/tree/master/samples/tutorial/04_PIM#standard-definitions-burst-mapping-and-
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@johanpel