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

Configuration of physical access size #104

Open
jreineckearm opened this issue Mar 12, 2024 · 0 comments
Open

Configuration of physical access size #104

jreineckearm opened this issue Mar 12, 2024 · 0 comments

Comments

@jreineckearm
Copy link
Contributor

jreineckearm commented Mar 12, 2024

Description

The debug logic in some CPU architectures allows to configure how data is read from a memory bus.
In some corner cases, this physical access size may have an impact on the success of reading memory. On the contrary a debugger may want to read as much data as possible with a single operation. Finding a good balance isn't always easy, and a user from time to time may want/need to have a more fine granular configuration to override the default strategy of a debugger. For example if they want to test the target system and that the memories are wired in correctly.

To enable such use cases, we should offer an expert setting to let the user specify this for individual memory window instances.

Additional information

This has a strong dependency on potential Microsoft DAP protocol enhancements or customizations.

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

1 participant