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

Integrate UEFI targets #80

Open
pedrolamarao opened this issue Aug 18, 2021 · 2 comments
Open

Integrate UEFI targets #80

pedrolamarao opened this issue Aug 18, 2021 · 2 comments

Comments

@pedrolamarao
Copy link
Owner

Integrate UEFI targets with Psys test driver.

@pedrolamarao
Copy link
Owner Author

This is a summary of the problem.

UEFI relocates the application at load time.
Therefore, when we launch the debugger, it is necessary to relocate the debugging symbols.
Otherwise, setting break and watchpoints on symbols will set them on the wrong address.

UEFI provides a way to discover the application load address at runtime.
That requires breaking test execution at an appropriate point and then searching physical memory for a well known memory object, from which one can navigate pointers towards a certain object which describes the application load information.
The test driver must driver the emulator and/or the debugger to automate the discovery of this information.
This driver will be very different from the Multiboot2 driver, requiring the test architecture to acommodate two drivers.

@pedrolamarao pedrolamarao added this to the M06 milestone Mar 12, 2022
@pedrolamarao
Copy link
Owner Author

Also, UEFI requires a FAT disk image.
See #129

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

No branches or pull requests

1 participant