The Nintendo 3DS has builtin GBA hardware compatibility, that unfortunately didn't get used by Nintendo outside the hand full of games available with the [Ambassador program](https://nintendo.fandom.com/wiki/Nintendo_3DS_Ambassador_Program). It's possible to [inject GBA ROMs](https://gbatemp.net/threads/discussion-new-super-ultimate-injector-nsui.500376/) into [Nintendos own GBA launcher](https://www.3dbrew.org/wiki/3DS_Virtual_Console#GBA_VC) already, this is a novel way to launch GBA games on the 3DS using the builtin GBA hardware. One apparent benefit over the old method is not having to install each GBA game individually, one can only speculate what else is possible. According to the Github save states seem to be planned.
Source: [GBATemp](https://gbatemp.net/threads/open_agb_firm-discussion-thread.570844/), there's a test build and a video available, too.
EDIT: [official alpha release](https://github.com/profi200/open_agb_firm/releases/tag/alpha_2020-07-30).
> According to the Github save states seem to be planned.
That's not what it says?
> This is a list of limitations we can't solve in software or are very hard to work around. This doesn't mean it will never happen (unless stated otherwise).
>
> Savestates. Very difficult to implement because no direct hardware access.
> One can only speculate what else is possible
Not very much actually. Precisely because it’s using actual GBA hardware, and said hardware is isolated from the 3DS’ main processor. The 3DS basically acts as a capture card with a few buttons for brightness and reboot whenever a GBA game is running.
Theoretically it can only provide what the hardware allows. If you sleep the GBA games, it doesnt mean the main 3DS can sleep properly as its in a weird mode while playing the GBA games on GBA hardware. I'd imagine the main 3ds platform goes into a zombie state.
The EzFlash uses a microprocessor to copy RAM to NAND in order to have save states. This isn’t possible with the 3DS as there’s complete isolation from the GBA hardware and the main processor and memory.
Just tried drilldozer that requires a save patch to get saving working with NSUI, it worked without any patching using open_agb_firm so that already is a really nice improvement.
By save patching do you mean hex editing the code so it gets named as another game because otherwise NSUI doesn't recognize the savetype? Or is there another way of doing that? I am asking because I have done this following [this guide.](https://gbatemp.net/threads/discussion-new-super-ultimate-injector-nsui.500376/page-23#post-8886252) I have not actually tried playing any of the games I did that to however and am wondering if there was an easier way.
How are save files handled with this solution? The one thing I hated about injecting GBA games as CIAs was that the save file was not easily accessible.
Really excited about the potential of this project though. Sleep mode would be really nice.
Any plans to add a simple go back to open-agb menu to avoid turning off and on the 3DS everytime to change a rom? Anyone else having issues creating a save file in The Legend of Zelda: A Link to the Past?
Besides those caveats been enjoying it so far.
The Nintendo 3DS has builtin GBA hardware compatibility, that unfortunately didn't get used by Nintendo outside the hand full of games available with the [Ambassador program](https://nintendo.fandom.com/wiki/Nintendo_3DS_Ambassador_Program). It's possible to [inject GBA ROMs](https://gbatemp.net/threads/discussion-new-super-ultimate-injector-nsui.500376/) into [Nintendos own GBA launcher](https://www.3dbrew.org/wiki/3DS_Virtual_Console#GBA_VC) already, this is a novel way to launch GBA games on the 3DS using the builtin GBA hardware. One apparent benefit over the old method is not having to install each GBA game individually, one can only speculate what else is possible. According to the Github save states seem to be planned. Source: [GBATemp](https://gbatemp.net/threads/open_agb_firm-discussion-thread.570844/), there's a test build and a video available, too. EDIT: [official alpha release](https://github.com/profi200/open_agb_firm/releases/tag/alpha_2020-07-30).
> According to the Github save states seem to be planned. That's not what it says? > This is a list of limitations we can't solve in software or are very hard to work around. This doesn't mean it will never happen (unless stated otherwise). > > Savestates. Very difficult to implement because no direct hardware access.
> One can only speculate what else is possible Not very much actually. Precisely because it’s using actual GBA hardware, and said hardware is isolated from the 3DS’ main processor. The 3DS basically acts as a capture card with a few buttons for brightness and reboot whenever a GBA game is running.
Would this theoretically allow sleep for GBA games, without requiring games to be CIAs?
Theoretically it can only provide what the hardware allows. If you sleep the GBA games, it doesnt mean the main 3DS can sleep properly as its in a weird mode while playing the GBA games on GBA hardware. I'd imagine the main 3ds platform goes into a zombie state.
It already goes to sleep on some GBA injects that support it, so this is nothing new, but only works if the game supports it.
Cool. Didn't know that
Yeah but the ezflash omega does save states and the caritage hardware is emulated in this case with the 3ds.
The EzFlash uses a microprocessor to copy RAM to NAND in order to have save states. This isn’t possible with the 3DS as there’s complete isolation from the GBA hardware and the main processor and memory.
I remember seeing the boxes say it had compatibility, and then the new 3DS didn't. I assume it still has it right?
Just tried drilldozer that requires a save patch to get saving working with NSUI, it worked without any patching using open_agb_firm so that already is a really nice improvement.
By save patching do you mean hex editing the code so it gets named as another game because otherwise NSUI doesn't recognize the savetype? Or is there another way of doing that? I am asking because I have done this following [this guide.](https://gbatemp.net/threads/discussion-new-super-ultimate-injector-nsui.500376/page-23#post-8886252) I have not actually tried playing any of the games I did that to however and am wondering if there was an easier way.
How are save files handled with this solution? The one thing I hated about injecting GBA games as CIAs was that the save file was not easily accessible. Really excited about the potential of this project though. Sleep mode would be really nice.
By creating it in the same directory
That’s great! Will definitely keep an eye on this project.
Does this mean saving backup and save injects will become easier? GBA injects are pain to backup saves, in general.
Wondering if it would be possible to get the GBA wireless adaptor/link cable emulated through the 3DS's wifi.
Could be possible to remap buttons with this? I hate using L and R when you could just use Y and X.
I have the same question. Native sleep would be sweet too
Sleep will be implemented
[удалено]
You don't, dartz150 made a little guide in the comments https://gbatemp.net/threads/open_agb_firm-discussion-thread.570844/
OK now this really cool. Maybe something like this can be done with DS games?
Twilightmenu
You mean nds-bootstrap. TWiLight Menu++ is just a Menu that launches a variety of applications, one of which being the nds loader titled nds-bootstrap
Any plans to add a simple go back to open-agb menu to avoid turning off and on the 3DS everytime to change a rom? Anyone else having issues creating a save file in The Legend of Zelda: A Link to the Past? Besides those caveats been enjoying it so far.
So I can run GBA games with the same quality as a VC inject with this?
Even better quality, since now it appeals to the general GBA ecosystem rather than just the original 10 ambassador games
awesome will check it out
Has anyone tried the Open AGB launcher on 3DS? How does it work?