Difference between revisions of "Talk:NES 2.0"

From Nesdev wiki
Jump to navigationJump to search
Line 38: Line 38:
 
To my eyes NES 2.0 sounds like a program along with its version number. Usually file formats don't undergo constant revision and thus don't have x.y version numbers. Maybe the name NES 2.0 has already stuck, but even NES 2 file format doesn't look much like a program and version number. I'm thinking of phrases like "YANES supports NES 2.0" where it might sound like it is compatible in some way with the 2.0 version of a program called NES. OTOH, NES 2 sounds like a second version of the NES hardware. Maybe there are plans for NES 2.1 etc. Anyway, just noting how the name sounds. [[User:Blargg|Blargg]] ([[User talk:Blargg|talk]]) 01:09, 19 January 2014 (MST)
 
To my eyes NES 2.0 sounds like a program along with its version number. Usually file formats don't undergo constant revision and thus don't have x.y version numbers. Maybe the name NES 2.0 has already stuck, but even NES 2 file format doesn't look much like a program and version number. I'm thinking of phrases like "YANES supports NES 2.0" where it might sound like it is compatible in some way with the 2.0 version of a program called NES. OTOH, NES 2 sounds like a second version of the NES hardware. Maybe there are plans for NES 2.1 etc. Anyway, just noting how the name sounds. [[User:Blargg|Blargg]] ([[User talk:Blargg|talk]]) 01:09, 19 January 2014 (MST)
 
:If I remember correctly, some publications referred to NES-101 (the 72-pin toploader) as "NES 2". As for the naming rationale, you could always get on [[IRC]], bug kevtris, and report your results here. --[[User:Tepples|Tepples]] ([[User talk:Tepples|talk]]) 08:07, 19 January 2014 (MST)
 
:If I remember correctly, some publications referred to NES-101 (the 72-pin toploader) as "NES 2". As for the naming rationale, you could always get on [[IRC]], bug kevtris, and report your results here. --[[User:Tepples|Tepples]] ([[User talk:Tepples|talk]]) 08:07, 19 January 2014 (MST)
::USB & SCSI come to mind...  [[Special:Contributions/50.170.133.216|50.170.133.216]] 03:56, 29 August 2014 (MDT)
+
::USB & SCSI come to mind...  [[Special:Contributions/50.170.133.216|50.170.133.216]] 03:56, 29 August 2014 (MDT) Resigned with account... [[User:Alphamule|alphamule]] ([[User talk:Alphamule|talk]]) 13:53, 29 August 2014 (MDT)

Revision as of 19:53, 29 August 2014

Nintendulator

"Kevin Horton reports that Nintendulator supports NES 2.0."

No it doesn't - it detects them (and the mapper interface has room for them), but it doesn't actually read any of the fields. --Quietust 01:58, 5 January 2010 (UTC)

  • ...though now it at least handles larger ROM images (including "Super 8-in-1 99 King Fighter (Unl).nes", which should actually be Mapper 45 with 1MB PRG and 2MB CHR, but with the 256KB CHR blocks 0/1/2/3/4/5/6/7 rearranged to be 0/2/3/1/4/5/6/7). --Quietust 03:30, 5 January 2010 (UTC)

An observation: it would've made more sense for the TV system byte to use bit 0 to mean "Supports NTSC" and bit 1 to mean "Supports PAL", since it would've made it trivial to support Dendy timing by just adding another bit. --Quietust 04:52, 14 January 2011 (UTC)

Zero CHR ROM

Observation: if a ROM is marked as NES 2.0 and has zero banks of CHR ROM, it must set the CHR RAM size field to a nonzero value (ideally 0x07, for 8KB non-batteried), otherwise it technically doesn't have anything at all connected to the PPU bus. --Quietust 02:20, 26 August 2011 (UTC)

Good point. I'll mention 0x07 as the most common CHR RAM size in the article. But I do know of two ways to make a cart with no CHR ROM or CHR RAM. The Game Genie uses one way: wire CHR address lines to data lines through a mux to make 4x4 pixel squares. The other way, which I've talked about before on the forum but have never seen used in a game, involves always enabling CIRAM and wiring PA13 to CIRAM A10, which gives 1-screen mirroring (all banks at $400-$7FF) plus 64 tiles of CHR RAM (at $000-$1FF). --Tepples 10:57, 26 August 2011 (UTC)
Just to close the loop- nocash built a game that used VRAM as CHRRAM: (http://forums.nesdev.com/viewtopic.php?t=9342) and allocated it to iNES Mapper 218.—Lidnariq (talk) 14:46, 13 March 2013 (MDT)
I think it would makes sense that if there is neither CHR ROM nor CHR RAM and the mapper is one that normally has at least one of these, then it should just use CIRAM for pattern tables, as if CIRAM A10 is wired according to the mirroring header (and/or software-controlled), and CIRAM is always enabled. Should you specify this? --Zzo38 (talk) 22:29, 21 March 2013 (MDT)

RAM size

I'm torn about how to deal with RAM-inside-mappers. As far as I know, there are five ICs that have some: MMC5, MMC6, X1-005, X1-017, and Namco 163.

Some of these are easy: for the MMC6, X1-005, and X1-017, their internal RAM is at the exclusion of external RAM. The RAM size byte can just hold $40, $01, $10, or (per rounding up) $70 as appropriate.

For the MMC5, that RAM can be thought of as either of CPU or PPU memory, it's not clear whether it should be marked (and where it should be marked). Apparently no game ever battery-backed only the 1k internal RAM, so perhaps leaving the RAM size byte at 0 for MMC5s without external RAM is best, even if it's contradictory to the advice for the previous three. Only 2k, 8k, and 32k RAMs were available during the MMC5's commercial life, and they were only ever combined as (none, 8+0, 8+8, 32+0); clearly adding 1024 and rounding up would cause nonintuitive values here. (As an aside, there's also no way to express the 2+8 or 8+32 configurations in NES2.0; fortunately neither were used commercially)

The N163 came in 3 of the 4 possible variants: neither battery nor external RAM; battery but no external RAM; battery and external RAM. The first two would easily be $01 and $10, but the last worries me—adding internal+external and storing the rounded-up value in the "RAM size" means we'd have $80=16384 for 8192+128 battery-backed, or $60=4096 for 2048+128 battery-backed. This feels unintuitive to me. Simply always excluding internal RAM here (in addition to being contradictory to the advice given for the MMC6) means we'll have the nonsensical value 0 with the battery bit set in the rest of the header. Maybe the right answer is to only count the internal RAM when there's no external RAM? —Lidnariq (talk) 13:43, 10 February 2013 (MST)

We can add the Datach system to the list. It provides a 256 byte EEPROM that is not strictly speaking part of the game, but rather the cartridge converter, and thus is shared between games. Perhaps here the byte should indicate whether the game uses the EEPROM, rather than whether it's available. —Lidnariq (talk) 03:04, 14 August 2013 (MDT)

Vs PPUs and $2002

"RC2C05-02 (with ID ([2002h] AND 3Fh)=3Dh)" - How can that be? Does the RC2C05-02 not implement the sprite overflow flag? --Quietust (talk) 21:30, 21 March 2013 (MDT)

"Mighty Bomb Jack" checks it right on power-up— $8011: lda $2002; and #$3F; cmp #$3D; bne Reset. But after startup (where it spins on $2002.7) and checking these bits here, it seems to never read from $2002 for anything other than the side effect of resetting the $2006 lo/hi toggle. —Lidnariq (talk) 17:41, 22 March 2013 (MDT)

Use of unused features

I like the feature that for mappers that don't otherwise use the PRG RAM size header, it should specify 8K if it is mapped to $6000-$7FFF or zero if it is open bus or registers or whatever. However, I have some other suggestion: For CHR RAM, if it is a mapper with no CHR bankswitching and no other special use of the PPU address space, then if 16K CHR RAM (battery or non-battery) is specified, zero CHR ROM is specified, and four-screen mirroring is specified, to just map all the CHR RAM to the PPU address space. If a mapper that normally uses non-battery CHR RAM is specified, and the non-battery CHR RAM amount is set to zero but the battery CHR RAM amount is nonzero, then it should emulate it the same as that mapper normally does, but save the contents of the CHR RAM to a file. One other possible concern is, what will the trainer ROM do in mappers that already have something mapped to $7000-$71FF area? I suppose it could simply override it. Also, you say don't assign mapper numbers greater than 255 yet. However, if you have to define a mapper which depends on NES 2.0 features and that the older iNES format is insufficient, then you should assign numbers greater than 255. For example, I have worked on my own mappers and wish to assign them; the other mappers discussed in discrete logic mapper toolbox should also be assigned, and then it could be used to make up games using them on an emulator. (I could write the articles in my user space and they are moved once numbers are assigned.) --Zzo38 (talk) 00:59, 29 June 2013 (MDT)

NES 2.0 allows the description a lot of things that don't have preexisting meanings. For example, only MMC1 and MMC5 have well defined meanings for having both the "nonvolatile" and "static" PRG-RAM nybbles set, but they can be set in the header regardless. Simply deciding that if both nybbles are set to signify 4KiB that e.g. the battery-backed one comes first doesn't make this definition useful or worth the complexity, nevermind that it precludes correct behavior if a later discovery reveals the opposite behavior. To rapidly run through your suggestions: Providing general purpose memory from PPU $3000-$3EFF isn't useful, and 16KiB SRAMs have always been rare. I do agree that "just specifying battery-backed CHR-RAM should DTRT", but once again, it's waiting on an implementation. The "trainer" question is ancient, but has been mostly rendered moot by getting rid of all dumps that request trainers (In general: trainers override any other device mapped in that range, because they are assumed necessary for operation). Mapper numbers will be allocated when a hardware implementation exists. A general purpose mapper description language (as your m768 proposal) is not an obvious fit for the iNES file format. —Lidnariq (talk) 02:09, 29 June 2013 (MDT)

Call it NES 2 file format?

To my eyes NES 2.0 sounds like a program along with its version number. Usually file formats don't undergo constant revision and thus don't have x.y version numbers. Maybe the name NES 2.0 has already stuck, but even NES 2 file format doesn't look much like a program and version number. I'm thinking of phrases like "YANES supports NES 2.0" where it might sound like it is compatible in some way with the 2.0 version of a program called NES. OTOH, NES 2 sounds like a second version of the NES hardware. Maybe there are plans for NES 2.1 etc. Anyway, just noting how the name sounds. Blargg (talk) 01:09, 19 January 2014 (MST)

If I remember correctly, some publications referred to NES-101 (the 72-pin toploader) as "NES 2". As for the naming rationale, you could always get on IRC, bug kevtris, and report your results here. --Tepples (talk) 08:07, 19 January 2014 (MST)
USB & SCSI come to mind... 50.170.133.216 03:56, 29 August 2014 (MDT) Resigned with account... alphamule (talk) 13:53, 29 August 2014 (MDT)