Emulation/Wii-U-Firmware-Emulator
1
0
Fork 0
mirror of https://github.com/kinnay/Wii-U-Firmware-Emulator.git synced 2024-05-31 18:47:27 -04:00
Code Issues Packages Projects Releases Wiki Activity
Emulates IOSU and part of Cafe OS
12 commits 2 branches 0 tags 725 KiB
C++ 99.8%
C 0.1%
Go to file
James Benton 0236bbda49 Fix EnableIf / DisableIf macros. 
This fixes two things:

You cannot have a std::enable_if on a member function which is only
conditional on the template parameters of the class it belongs to. The
typical way to solve this is by doing redeclaring the type in the function
template, eg:
template<typename T>
class Foo {
template<typename U = T, std::enable_if<is_something<U>> void bar();
}

However that would require usage of the macro to look like:
template<typename U = T, EnableIf(is_something<U>)>

So instead we can make your macro add a bool type to the template paramater
list which is the result of the enable_if, and then use std::enable_if on
that instead, eg:
bool B = (__VA_ARGS__), typename std::enable_if_t<B, int> = 0

However there is one more problem, as you overload your functions with this
macro (eg Matrix::determinant), this leads to both overloads having the
same type signature template<bool B, typename std::enable_if_t<B, int>> so
you end up with duplicated function error.

The way to fix that is to ensure both functions have separate type
signatures, to do that we can repeat the __VA_ARGS__ condition inside the
std::enable_if usage - whilst still being sure to use B to satisfy the
previously mentioned constraint. Which finally leads us to:
bool B = (__VA_ARGS__), typename std::enable_if_t<!B && !(__VA_ARGS__), int> = 0
2020-06-14 17:39:56 +02:00
.github/workflows Add github actions build 2020-06-14 17:18:41 +02:00
files Make sure that files and logs folders are pushed to github 2020-03-18 09:43:27 +01:00
logs Make sure that files and logs folders are pushed to github 2020-03-18 09:43:27 +01:00
src Fix EnableIf / DisableIf macros. 2020-06-14 17:39:56 +02:00
.gitignore Make sure that files and logs folders are pushed to github 2020-03-18 09:43:27 +01:00
LICENSE Pick a random license 2020-03-18 09:55:00 +01:00
Makefile Complete rewrite in c++ 2020-03-18 08:03:42 +01:00
README.md Create README.md 2020-03-18 09:52:10 +01:00

README.md

Wii U Firmware Emulator

This emulator emulates the Wii U processors and hardware at the lowest level. It's currently able to emulate all the way through boot1, IOSU and Cafe OS until hbm.rpx calls OSPanic for some reason.

This emulator used to be written in a combination of Python and C++. You can still find the source code of this emulator in the branch 'old'.

Instructions

  1. Make sure you have a linux system, a g++ compiler that supports c++14 and the OpenSSL library.
  2. Dump the following files from your Wii U (with hexFW for example) and put them into the 'files' folder: boot1.bin, otp.bin, seeprom.bin, mlc.bin, slc.bin and slccmpt.bin. This emulator may write to some of these files, use a backup if you want to keep your original dumps.
  3. Create files/espresso_key.bin and put the espresso ancast key into it.
  4. Run make to compile the emulator

Configuration

src/config.h contains a few macros that enable/disable certain features of the emulator, such as breakpoints. Enabling a feature adds interesting commands to the debugger but may slow down the emulator a bit.

Option Description
STATS Tracks some statistics about the emulator, such as the number of instructions that are executed or the number of system calls.
METRICS Tracks even more statistics: counts how often each individual PowerPC instruction is executed and how often each system call is taken.
WATCHPOINTS Enables memory watchpoints in the debugger.
BREAKPOINTS Enables instruction breakpoints in the debugger.
SYSLOG Writes the system log into logs/syslog.txt.

Additionally, you can adjust the log level in src/main.cpp. To disable warnings about unimplemented hardware features set the log level to ERROR or NONE.

Debugger

Using this emulator you can actually see what boot1, IOSU and Cafe OS look like at runtime, and even perform debugging operations on them. You can stop execution and show the debugger by pressing Ctrl+C at any point.

Command Description
help Print list of commands.
exit Stop the emulator.
quit Same as exit.
select arm/ppc0/ppc1/ppc2 Select a processor to debug.
step (<steps>) Execute a fixed number of instructions on the current processor.
run Continue emulation normally.
reset Reset the emulator to its initial state.
restart Restart emulation from the beginning. This is the same as executing reset and then run.
stats Print some interesting statistics, such as the number of instructions that have been executed so far. Only valid if STATS is enabled.
metrics ppc0/ppc1/ppc2 category/frequency Print how often every PowerPC instruction has been executed on the given core, either sorted by category or sorted by frequency. Only valid if METRICS is enabled.
syscalls ppc0/ppc1/ppc2 Print how often each system call has been executed on the given core, sorted by frequency. Only valid if METRICS is enabled.
break add/del <address> Add or remove a breakpoint. Only valid if BREAKPOINTS is enabled.
break list Print breakpoint list. Only valid if BREAKPOINTS is enabled.
break clear Remove all breakpoints. Only valid if BREAKPOINTS is enabled.
watch add/del virt/phys read/write <address> Add/remove a memory read/write watchpoint at the given virtual or physical address. Only valid if WATCHPOINTS is enabled.
watch list Print watchpoint list. Only valid if WATCHPOINTS is enabled.
watch clear Remove all watchpoints. Only valid if WATCHPOINTS is enabled.
state (full) Print all general purpose registers on the current processor and some other important registers. If full is passed, many other special registers are printed as well.
print <expr> Evaluate the given expression and print the result.
trace Print stack trace on the current processor
read virt/phys <address> <length> Read length bytes at the given virtual or physical address and print them both in hex and ascii characters. If a virtual address is given, the MMU of the current processor is used to translate the address.
translate <address> Translate the given virtual address and print the physical address, using the MMU of the current processor.
memmap Print the virtual memory map of the current processor.
modules Print the list of loaded RPL files and the starting address of their .text segment.
module <name> Print more information about a specific module.
threads Print thread list for IOSU or COS (depending on the current processor).
thread <id> Print more information about a specific thread for IOSU or COS (depending on the current processor). If a thread is waiting, this command tries to figure out what it is waiting for. If a PPC processor is begin debugged, this command also tries to print a stack trace for the given thread.
queues Print list of message queues in IOSU.
queue <id> Print more information about a specific message queue in IOSU.
devices Print the state of all ipc devices in IOSU.
hardware Print the content of a few hardware registers (PI/GPU/LATTE).
volumes Print list of filesystem volumes in IOSU.
fileclients Print list of filesystem clients.
slccache Print information about SLC cache in IOSU.