Awesome work!

Yeah, super-cool. Just need BS-X now

the main problem is that depending on writes to the BS-X registers, the memory map changes heavily and this is not so easy to implement with the way base SNES memory is handled...

I'd like to at least reach the point where the city whose name has been stolen can be finally reached (i.e. the single BS-X cart is correctly handled), before dealing with the flash cart details...

http://mess.redump.net/datasheets:mitsubishi

I will soon upload it to the FTP(s). Thanks again to Ingo Sangmeister.

Before I forgot about it:

Super Gussun Oyoyo has a weird bug with the BGMs (it skips to play entire sub-loops), apparently this is NOT caused by the timing stuff (tested latest SVN and MESS 0.132, still the same).

I am not sure if this will be useful to anyone, but I found this on another emulation site which I am a member.

Complete SNES SDK and programming manuals - includes.

• SASM SNES DEV tools
• SSBUG (Super Nintendo Development System Debugger)
• Nintendo's SNES Official Programming Manual
• SNES Development Manual (Book 1 & Book 2)
• Super Famicom Documents

If anyone is interested in the documentation let me know. I also found one for the N64.

• Nintendo64 OS Version 2.0L (PC version)
• LFC-N64 (Official N64 Development Libraries and manuals)
• Official and Confidential Nintendo N64 Hardware/Programming Manuals
• PSYQ and PSYQN64 SDK
• Sample source code

Thanks,
Scott

Well, first of all, offering all that stuff is highly illegal, but besides that, anyone who actually works for an authorized Nintendo developer can tell you that all of Nintendo's documents are shit and loaded with inaccuracies - and more importantly, lack pretty much all information that would be remotely useful for accurate emulation of the console. Additionally, the MAME and MESS teams are made up of people who have been around the emulation community for well over a decade in most places, so we have pretty much every single document that you're ever going to come across, and some that you probably won't.

Love the Super System research, will be following that very closely. So awesome to emulate things for the very first time.

Official documentation is nothing but problems. Since they are confidential, using them may introduce legal problems as it is no longer clean room reverse engineering. Add Just Desserts' comments to that, and it's clear that they should be avoided entirely.

Current emulation is blocked by a missing dump of the M50458 char ROM, I bet that it won't be dumpable hence we need to write a trojan on a real board. I also don't think that is currently putting any reasonable vram data yet, but we'll see once that we find a board ...

Current MAME driver is here, with my current discoveries:

http://mamedev.org/source/src/mame/drivers/nss.c.html

It sounds like the device is some kind of video overlay thing (teletext type / vcr control type systems?) with internal ascii rom so you might just be able to throw a fake ascii rom in, and patch the checksum code until it's dumped? (or it might be something standard?)