(06-12-2017, 08:11 AM)leolam Wrote: The Wii U has a Wii OTP bank (IIRC), so you can just use that for the OTP data. Thank you for posting that! I was able to find the page that talks about the SEEPROM data on WiiBrew. (06-12-2017, 08:11 AM)leolam Wrote: Anyway, the file is mostly composed of several dumps. Was it stated what parts in the keys.bin will be made use of in the future? (06-12-2017, 08:11 AM)leolam Wrote: Dolphin is indeed probably going to make use of some additional, currently unused fields in the future. I apologize if I posted this in the wrong section. It does not seem like everything inside the keys.bin file are actually used in the emulator, but I am worried about placing zero in those spots if Dolphin is actually going to make use of those data in the future. Then there are others where I am not sure if they even exist, such as prng_seed and fill (I had to do some guesswork since some data were called different things on WiiUBrew vs the Wii Tools). ![]() Going from the WiiUBrew site, there is no section that would remotely resemble eep_ctr_t. ![]() Unfortunately, some of the information that the keys.bin include are not in the otp.bin file. I am currently taking a look at the ec_wii.h since that gives a complete picture of how the keys.bin would actually look like (at least it did a better job at explaining what every single part is then what WiiBrew provided). To be exact, it takes a Wii U's OTP file and puts the keys in a newly generated keys.bin file. I am currently making an application that generates BootMii keys.bin files.
0 Comments
Leave a Reply. |