This version of QEMU is modified to reverse engineer the ESP32 wifi registers. Was built on the latest espressif qemu release, with the patches from Ebiroll ported to that newer version
- Implements registers enough to get AP mode working (QEMU is the access point, the emulated ESP32 is a client); the client can connect to the AP, obtain an IP address, ...
- Can log all unknown peripheral accesses to a log-file. Because we have to unwind the stack ourselves, this feature only works in single-step mode. The log file contains: - mode (read or write) - address - value read or written - the callstack
Building:
`
mkdir build
cd build
../configure --target-list=xtensa-softmmu --enable-gcrypt --enable-debug --disable-sanitizers --disable-strip --disable-user --disable-capstone --disable-vnc --disable-sdl --disable-gtk --disable-curl
cd ..
ninja -C build
`
After compiling with ninja -C build, build a flash_image.bin by cd'ing to the build directory of your ESP32 project, then running esptool.py --chip esp32 merge_bin --fill-flash-size 4MB -o flash_image.bin @flash_args
`
build/qemu-system-xtensa -singlestep -d unimp -nic user,model=misc.esp32_wifi,id=u1 -no-reboot -S -s -nographic -machine esp32 -drive file=/home/user/Projects/esp32-open-mac/tx-example-esp32-plain/build/flash_image.bin,if=mtd,format=raw -object filter-dump,id=f1,file=/tmp/dump.pcap,netdev=u1 -drive file=../efuse/efuse.bin,if=none,format=raw,id=efuse -global driver=nvram.esp32.efuse,property=drive,value=efuse 2>&1
`
- -singlestep, so we can trace all peripheral writes/reads and get the callstack (this is written to a file in /tmp)
- -d unimp, so we log unimplemented memory peripherals
You will need to extract efuse.bin yourself, by dumping it from a real ESP32 (can be done with esptool.py, then concatenating the different files into efuse.bin)
QEMU is a generic and open source machine & userspace emulator and virtualizer.
QEMU is capable of emulating a complete machine in software without any need for hardware virtualization support. By using dynamic translation, it achieves very good performance. QEMU can also integrate with the Xen and KVM hypervisors to provide emulated hardware while allowing the hypervisor to manage the CPU. With hypervisor support, QEMU can achieve near native performance for CPUs. When QEMU emulates CPUs directly it is capable of running operating systems made for one machine (e.g. an ARMv7 board) on a different machine (e.g. an x86_64 PC board).
QEMU is also capable of providing userspace API virtualization for Linux and BSD kernel interfaces. This allows binaries compiled against one architecture ABI (e.g. the Linux PPC64 ABI) to be run on a host using a different architecture ABI (e.g. the Linux x86_64 ABI). This does not involve any hardware emulation, simply CPU and syscall emulation.
QEMU aims to fit into a variety of use cases. It can be invoked directly by users wishing to have full control over its behaviour and settings. It also aims to facilitate integration into higher level management layers, by providing a stable command line interface and monitor API. It is commonly invoked indirectly via the libvirt library when using open source applications such as oVirt, OpenStack and virt-manager.
QEMU as a whole is released under the GNU General Public License, version 2. For full licensing details, consult the LICENSE file.
Documentation can be found hosted online at
https://www.qemu.org/documentation/. The documentation for the
current development version that is available at
https://www.qemu.org/docs/master/ is generated from the docs/
folder in the source tree, and is built by Sphinx.
QEMU is multi-platform software intended to be buildable on all modern Linux platforms, OS-X, Win32 (via the Mingw64 toolchain) and a variety of other UNIX targets. The simple steps to build QEMU are:
mkdir build
cd build
../configure
makeAdditional information can also be found online via the QEMU website:
The QEMU source code is maintained under the GIT version control system.
git clone https://gitlab.com/qemu-project/qemu.gitWhen submitting patches, one common approach is to use 'git format-patch' and/or 'git send-email' to format & send the mail to the qemu-devel@nongnu.org mailing list. All patches submitted must contain a 'Signed-off-by' line from the author. Patches should follow the guidelines set out in the style section of the Developers Guide.
Additional information on submitting patches can be found online via the QEMU website
The QEMU website is also maintained under source control.
git clone https://gitlab.com/qemu-project/qemu-web.gitA 'git-publish' utility was created to make above process less cumbersome, and is highly recommended for making regular contributions, or even just for sending consecutive patch series revisions. It also requires a working 'git send-email' setup, and by default doesn't automate everything, so you may want to go through the above steps manually for once.
For installation instructions, please go to
The workflow with 'git-publish' is:
$ git checkout master -b my-feature
$ # work on new commits, add your 'Signed-off-by' lines to each
$ git publishYour patch series will be sent and tagged as my-feature-v1 if you need to refer back to it in the future.
Sending v2:
$ git checkout my-feature # same topic branch
$ # making changes to the commits (using 'git rebase', for example)
$ git publishYour patch series will be sent with 'v2' tag in the subject and the git tip will be tagged as my-feature-v2.
The QEMU project uses GitLab issues to track bugs. Bugs found when running code built from QEMU git or upstream released sources should be reported via:
If using QEMU via an operating system vendor pre-built binary package, it is preferable to report bugs to the vendor's own bug tracker first. If the bug is also known to affect latest upstream code, it can also be reported via GitLab.
For additional information on bug reporting consult:
For version history and release notes, please visit https://wiki.qemu.org/ChangeLog/ or look at the git history for more detailed information.
The QEMU community can be contacted in a number of ways, with the two main methods being email and IRC
- mailto:qemu-devel@nongnu.org
- https://lists.nongnu.org/mailman/listinfo/qemu-devel
- #qemu on irc.oftc.net
Information on additional methods of contacting the community can be found online via the QEMU website: