I hope this project will bring some new life into the SNES-on-DS scene. It looks like all the existing emulators for the DS are dormant or discontinued, which is sad.


lolSnes is a project I had started two years ago. I wanted to make a SNES emulator for the DS, that could render most sane games without glitches. But I followed a wrong approach with the PPU side: trying to make a line-accurate software renderer. The DS just isn't powerful enough to handle such a renderer. That discovery pretty much shattered my motivation and the project stayed dormant for two years.

And now, for some reason, I felt like working on it again. I trashed the software PPU attempt and coded the PPU using the DS's 2D video hardware.

So far, SMW is playable, to some extent.

You can't get past Donut Plains 2, though: for some reason, the camera keeps rewinding and moving forward a bit at the start of the level, keeping you from going further. Aside from this bug, gameplay is near perfect. The game also runs at fullspeed (albeit with a speedhack).

Screenshots

Version 1.0:



Older screenshots: (pre-1.0, many issues there have since been fixed)



Emulator in emulator. Wee.

What is currently supported

* CPU -- 99% (all opcodes emulated; may miss a few unimportant bits about timing)
* PPU -- ~40% (mode 1 BGs, OBJs, mosaic, master brightness, giant kludge for BG3 prio)
* SPC700 -- 80% (most useful opcodes implemented, CPU/SPC I/O, timers)
* DSP -- 0% (yep, no sound)
* SRAM with auto-saving

Download link

Version 1.0

Unofficial Git builds

People may have built Git versions and distributed those. (if your lolSnes build's version is above the last released version, it's a Git build)

Keep in mind that Git builds may be unstable. They may explode in your face at any time, so don't be surprised.

Git builds can offer features that aren't in the last version, though.

How to use it

Place lolsnes.nds in your flashcart's root folder (or wherever DS ROMs are). In the same folder, create a folder
named 'snes', and place your ROMs in there.

You can place savefiles from other emulators too. They have to have the same name as the corresponding ROMs and have
.srm extensions.

lolSnes is able to properly detect the ROM type in most cases. Headered and headerless ROMs are supported, both
LoROM and HiROM.


Start lolSnes and select your ROM in the menu. If all goes well, you should see it run. If not, you'll stay in the
menu. Oh also, there's no pause/stop/reset feature yet, so if you want to run a different ROM, you need to reset your DS.

Github repo

For those who are interested, the source code is available in a Github repo.

Even though it isn't explicitly mentioned in the code files, the code is under the GPL license.

A lot of this is written in ARM ASM. If you don't have some knowledge of ARM ASM and GCC calling convention, the code may look like black magic to you...


Have fun!

 

By the way, I'd have continued on SNemulDS if possible, the only problem is that the source code of the last version seems to be completely gone from the internet, and SNemulDS being a port of an emulator made for DOS, it won't be as efficient as an emulator made specifically for the DS.

 

Are you saying you are the SNemulDS dev?

 

I hope that You will finish it!

 

Oh sorry, my bad. I just realized you are the OP. When I asked you the question I thought you weren't the OP because I had forgotten your name and avatar so quickly

 

cool. Just saw the source code..

on ARM7 source:
https://github.com/Mega-Mario/lolSnes/blob/master/arm7/source/main.c

Code:

//checks EXMEMSTAT flag busy?? (ARM7)
[B][SIZE=12px][FONT=Consolas][COLOR=#333333]*[/COLOR][/FONT][/SIZE][/B][SIZE=12px][FONT=Consolas][COLOR=#333333]([/COLOR][/FONT][/SIZE][SIZE=12px][FONT=Consolas][COLOR=#333333]u32[/COLOR][/FONT][/SIZE][B][SIZE=12px][FONT=Consolas][COLOR=#333333]*[/COLOR][/FONT][/SIZE][/B][SIZE=12px][FONT=Consolas][COLOR=#333333])[/COLOR][/FONT][/SIZE][COLOR=#009999][SIZE=12px][FONT=Consolas]0x04000210[/FONT][/SIZE][/COLOR][B][SIZE=12px][FONT=Consolas][COLOR=#333333]|=[/COLOR][/FONT][/SIZE][/B][COLOR=#009999][SIZE=12px][FONT=Consolas]0x00000008[/FONT][/SIZE][/COLOR][SIZE=12px][FONT=Consolas][COLOR=#333333];[/COLOR][/FONT][/SIZE]
//timer value set to 64489 cycles ?? (0) (arm7)
[B][SIZE=12px][FONT=Consolas][COLOR=#333333]*[/COLOR][/FONT][/SIZE][/B][SIZE=12px][FONT=Consolas][COLOR=#333333]([/COLOR][/FONT][/SIZE][SIZE=12px][FONT=Consolas][COLOR=#333333]u16[/COLOR][/FONT][/SIZE][B][SIZE=12px][FONT=Consolas][COLOR=#333333]*[/COLOR][/FONT][/SIZE][/B][SIZE=12px][FONT=Consolas][COLOR=#333333])[/COLOR][/FONT][/SIZE][COLOR=#009999][SIZE=12px][FONT=Consolas]0x04000100[/FONT][/SIZE][/COLOR][B][SIZE=12px][FONT=Consolas][COLOR=#333333]=[/COLOR][/FONT][/SIZE][/B][COLOR=#009999][SIZE=12px][FONT=Consolas]0xFBE9[/FONT][/SIZE][/COLOR][SIZE=12px][FONT=Consolas][COLOR=#333333];[/COLOR][/FONT][/SIZE]
//timer value set to 192 cycles 2 bytes after??
[B][SIZE=12px][FONT=Consolas][COLOR=#333333]*[/COLOR][/FONT][/SIZE][/B][SIZE=12px][FONT=Consolas][COLOR=#333333]([/COLOR][/FONT][/SIZE][SIZE=12px][FONT=Consolas][COLOR=#333333]u16[/COLOR][/FONT][/SIZE][B][SIZE=12px][FONT=Consolas][COLOR=#333333]*[/COLOR][/FONT][/SIZE][/B][SIZE=12px][FONT=Consolas][COLOR=#333333])[/COLOR][/FONT][/SIZE][COLOR=#009999][SIZE=12px][FONT=Consolas]0x04000102[/FONT][/SIZE][/COLOR][B][SIZE=12px][FONT=Consolas][COLOR=#333333]=[/COLOR][/FONT][/SIZE][/B][COLOR=#009999][SIZE=12px][FONT=Consolas]0x00C0[/FONT][/SIZE][/COLOR][SIZE=12px][FONT=Consolas][COLOR=#333333];[/COLOR][/FONT][/SIZE]

great work!

 

I'd recommend you read GBAtek a bit

The first write enables timer 0 IRQ in IE. The second write sets the reload value for timer 0, and the third configures timer 0 to run.

That's weird. It looks like a bad ROM or some other weird issue.

It'd be helpful if you opened desmume's disassemblers and gave me a screenshot of the ARM9 disassembler.

 

This looks like the SRAM size entry in the ROM is set to an insanely big value. The computed SRAM mask is 0xFFFFFFFF, which causes the code to allocate a zero-byte buffer and then proceed to zerofill the whole 4GB of memory.

I have no idea why that would be, but I'll add some code to make sure the SRAM size remains reasonable.

Edit- nevermind, it was a silly issue in my code (forgetting to set a variable, leaving it unitinialized). I don't get how this hasn't broken shit on my side yet.

It's fixed, anyway. I also added a line to ensure the SRAM size stays reasonable.