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

R_OPERATION_CTRL behavior ambiguity #5

Open
Poofjunior opened this issue Sep 28, 2023 · 3 comments
Open

R_OPERATION_CTRL behavior ambiguity #5

Poofjunior opened this issue Sep 28, 2023 · 3 comments

Comments

@Poofjunior
Copy link

Poofjunior commented Sep 28, 2023

In the R_OPERATION_CTRL register specification, what should the defined behavior be in this case?

  • When the DUMP bit is asserted from a PC-to-Device Harp Write message, does the device issue one reply per register, or a single reply where the payload contains the serialized register contents of all registers?
    • Does this reply (or replies) include just core registers or both core and app registers?
@filcarv
Copy link
Contributor

filcarv commented Oct 12, 2023

The device issues one reply per register (i.e., one Harp Message per register) for all registers, including the core ones.

@Poofjunior
Copy link
Author

Ok, it would be great to get this noted in the docs somehow, or just merge #6 .

@bruno-f-cruz
Copy link
Member

We unfortunately lost #6 with the previous merge we did on this repo. Can you re-do the PR to explicitly state this behavior in the protocol? Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants