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

Investigate the semantics of step/resume operations in context of HW trigger state. #1079

Open

aap-sc opened this issue Jun 4, 2024 · 0 comments

Collaborator

aap-sc commented Jun 4, 2024 •

edited

Loading

This ticket is a result of a discussion we had with @JanMatCodasip in #1056 (comment)

Currently, when performing "step"-like operation OpenOCD does the following:

disables breakpoint at the current PC (if one is found)
disables all HW triggers.
Once step is performed, the triggers are restored.

It's not quite clear if the second item is required. We need to investigate this and maybe ask in openocd-devel mailing list.

@en-sc , @MarekVCodasip FYI.

aap-sc mentioned this issue

target/riscv: fix halt reason for targets that do not support hit bit on triggers #1056

Merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment