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

avatar2/handbook/0x03_memory.md Qemu Properties dict possible types and values details #127

Open
RazerNinjas opened this issue Mar 12, 2024 · 1 comment

Comments

@RazerNinjas
Copy link

Hi there! I was trying to figure out what are the possible values for the QEMU properties when adding a QEMU device memory range or where I could be directed to find how set that up within the QEMU docs. I was just curious since Firmwire on the Shannon loader for the timers uses a different format than the provided example in the handbook, so I wanted to understand that better for what types, and their values etc. and how that works if you a list of properties. I tried checking the documentation as well but didn't get anything on what are the possible values to add in the type and values in the qemu_properties kwarg.

Any help would be appreciated. Thanks!

@mariusmue
Copy link
Member

Hi @RazerNinjas,

You are totally right, this is not a well documented feature of avatar2.

Under the hood, avatar2 creates a "configurable machine", which takes a json file and generates a QEMU machine from this on the fly. You can find the implementation here (it does not differ significantly from the PANDA configurable machine implementation FirmWire uses).

Now, the qemu_properties is a way to directly pass arguments to created peripherals in case they take additional one. In the instance of shannon_timer, a specialized timer was created which can be configured via these properties, the according code example is here.

I hope that helps!

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

2 participants