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

operation_resp missing implementation #9

Open
mslijepc opened this issue Nov 10, 2023 · 4 comments
Open

operation_resp missing implementation #9

mslijepc opened this issue Nov 10, 2023 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@mslijepc
Copy link

Hi, I can just see the function prototype

void operation_resp(payload_type& trans, unsigned clk_delay = 0);

but the implementation is missing. Is this function intended to be used, or is obsolete?

@mslijepc
Copy link
Author

I am using simple memory for read-write, and have created callbacks for this purpose which I set in set_operation_cb

@eyck eyck added the bug Something isn't working label Nov 10, 2023
@eyck
Copy link
Member

eyck commented Nov 10, 2023

For the purposes so far there was no need to implement the operation_resp since it just forwards accesses using the axi4 initiator socket (as noted in #10)

@mslijepc
Copy link
Author

In that case, memory should implement ace protocol state machine?

@hliu71
Copy link
Collaborator

hliu71 commented Nov 15, 2023

you do not need to implement the protocol state machine in the memory. you can do the conneciton it in this way:
ace_target_pe->axi_target_pe->memory.
to some extend ace_target_pe acts here as adapter between ace and axi, which forwards the normal read/write to axi. Besides it exends with snoop function.
you can imagin that, the real function of ace target pe includes ace_target_pe+axi_target_pe.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants