qiling VS mu

Sounds more like r/ReverseEngineering. If what you want to do is some dynamic analysis or just play around, maybe try using qiling, it's built on top of unicorn and is made by the same authors. It will take care of loading the file for you.

https://github.com/qilingframework/qiling Is probably what you are looking for

It is s binary emulation framework, which you can use to emulate different binaries for different architectures. On top of that you can use Qiling APIs to debug the emulation process, hook syscalls, etc. It's like Unicorn + Qemu + Frida. More info here: https://github.com/qilingframework/qiling

qiling is built on unicorn directly. qiling focuses on emulating binaries (read: emulating a single program and not an OS). It uses the binary blob work to load binaries and their associated shared objects. It then hooks the OS calls and presents an interface to the program as though it has interacted with an OS. see here

We started this project since 2019 Nov, currently they are around 70+ developers and 2,200++ stars in our Github page (https://github.com/qilingframework/qiling)

yes kkkkkk, the project mu have a strange way to build, and project mu have a not usable documentation, i think is because microsoft is microsoft, the project mu is a OEM Firmware as Service, the reason for not have a easy documentation can be for seal a service. in the past i have make a question about coreboot support https://github.com/microsoft/mu/issues/121

The stock edk2 menu has, like, two items.

System76 have built a more serious setup UI: https://github.com/system76/firmware-setup

Microsoft’s https://github.com/microsoft/mu also probably contains UI from the Surface line or something??