nesdev.com

Sour's confirmed that he's not planning on returning to these projects, so further development will need to be in a fork.

My desoldering station arrived, so tonight I pulled a 3195A and a 3198A for dumping. The good news is that the 3195A matches the 508 accessible bytes of the existing 512 byte dump, as expected. The bad news is that the 3198A matches Patnukem's dump, with the low 2 bits missing. As it's very unlikely...

We should change the read loop to try to get 762 (or 1016) bytes in case the chip is trying to change fields on its own, though I have some skepticism. It also looks like the code should be printing 508 iterations, so I'm not sure why it's ending early. [I see before posting that you did get it to p...

I'm a bit confused. With the newer code run on the 3199A, what does it output for i1F5-i1FB, and does it start repeating the i0+ data at i1FC? With the older code, when it starts at a different spot, is there evidence of it outputting anything that is not included in the 508 bytes from the new code'...

That 3199A dump has all the bits, so that's a great start. It's missing 7 bytes at the end, though, just like your last dump, and those bytes look in this case like they're probably not all 0. Why are these getting dropped now? I'm a little uneasy about the fact that these pages don't have a bunch o...

No need to rush on this stuff. :) I'll be working on 3198A dumps soon, and 3199(A?) hopefully in the next couple months. I forgot to comment on the FamicomStation menu cart. It's unsurprising it wouldn't work in a normal system; the FamicomBox has a number of additional features, such as additional ...

Ah, I had my pins mixed up and was thinking 0 and 1 were outputted on R1_2 and R1_3, which are slot ID inputs.

Aside from missing seven 00's at the end of the dump, that matches my dump and the accessible portion of the existing 512 byte dump. Regarding the 3198A, there's no actual need for a hardware difference to support the slot ID pins; all the port pins can be read from and written to in software. Howev...

I've actually made use of that a lot, though sometimes it can cost you extra cycles, and you need to be careful that the embedded instruction doesn't point into registers that are modified on read.

Not sure about your setup, but the dump looks like bit 2 has been moved to bit 0. I'm more confident in the previous version because it better matched up with instructions I expect to see.

Accesses to unmapped regions should return open bus, which holds the last value that was placed on the bus. Under normal circumstances, that BIT should operate on value $58, the high byte of the address, which was previously put on the data bus by the cartridge ROM. Things can get complicated if you...

I have not. My components are at my friend's place, so that'll wait until the next time we meet up.

If you'd like a 6113B1, I believe they're the standard in NES Play Action Football, which is a very cheap game; I was getting mine for $2 at the local game shop.

I have a desoldering station coming in the next couple weeks and will try to dump a 3198A after that arrives. Another thing I'd like to look at is the Famicom Modem CIC. The modem uses an 8633AN and its carts an 8634A. These are surface-mounted 18-pin chips. The wiring looks like it might match the ...

I'm using Mesen 0.9.9.62, but the emulator shouldn't matter. I checked the first ROM you posted and it seems to run without issue. Your second ROM introduces the bad pause-every-6th-frame behavior.