
Though it has dozens and fixes and tweaks under the hood, there are some pretty major features to announce, including full e-Reader support, some new enhanced utilities such as a save type converter and a bug report tool, and more. While this did lead to 0.9 being effectively “coming soon” for many, many months in a row, it has led to what I believe to be an extremely polished release, so I’m now happy to announce that mGBA 0.9.0 is done and out. Remember, mGBA currently only has one major developer, so things can take quite a long time to finish, and if I’m not actively working on it any given week then there isn’t progress made that week. In the interest of releasing a properly exciting new version of mGBA, I decided to hold off on releasing 0.9 until it was polished and featureful.ĭuring the latter half of the year I finally started a push for features, and released 0.8.4 as the last of the 0.8 line. It’s been a difficult year for the entire world and that definitely had an impact on development this cycle too.Īs progress marched on with mGBA for the first few months of last year, I was able to release 0.8.1 through 0.8.3 picking up most of the bug fixes I made along the way towards 0.9.Īfter several months there were lots changes under the surface, but not many new user-visible features. It's all hardware.After the seemingly longest year possible, mGBA 0.9.0 is finally here.

There is absolutely zero emulation going on for either DS or GBA games on the 3DS. This disables all 3DS specific features like the arm11 CPUs and lets the arm9 core sit idle while clocking down the arm7 to play GBA games with (theoretically) perfect compatibility.Įven the original GBA bios is burnt onto the arm7. So when a GBA game is selected to play, the 3DS loads a near identical firmware to when you load a DS game. Here's the thing, the arm9 CPU in the 3DS is actually a dual core package as well! It contains a full arm7 core with all of the associated registers. This means the arm11 cpu cores are not used at ALL for either DS or GBA modes. The reason why the system menu is disabled when you play a DS or GBA game is because the system has to boot out of 3DS mode so a hacker can't obtain entrance once the security co-processor is busy doing other things (clocking down and working as a DS or GBA processor).



The arm9 core is predominantly used as a security co-processor in 3DS mode which is why 3DS software actually doesn't use the arm9 even though it's sitting in there. Alright! After some digging I found the answers!
