Talk:UNROM 512: Difference between revisions
From NESdev Wiki
Jump to navigationJump to search
No edit summary |
No edit summary |
||
Line 4: | Line 4: | ||
:As for the jumpers that configure the CHR Ram, there is 4 of them on the board. Two of them tie the respective CHR-RAM address lines to Vcc, and the other two tie the respective CHR Ram lines to the 377 outputs. Basically, for 8KB, both CHR-RAM lines are tied to Vcc, for 16KB, only one of them is tied to Vcc, and for 32KB, none of them are tied to Vcc. [[User:Caitsith2|Caitsith2]] ([[User talk:Caitsith2|talk]]) 08:50, 1 April 2014 (MDT) | :As for the jumpers that configure the CHR Ram, there is 4 of them on the board. Two of them tie the respective CHR-RAM address lines to Vcc, and the other two tie the respective CHR Ram lines to the 377 outputs. Basically, for 8KB, both CHR-RAM lines are tied to Vcc, for 16KB, only one of them is tied to Vcc, and for 32KB, none of them are tied to Vcc. [[User:Caitsith2|Caitsith2]] ([[User talk:Caitsith2|talk]]) 08:50, 1 April 2014 (MDT) | ||
:I have formed a [[https://dl.dropboxusercontent.com/u/20737085/nes%202.0%2C%20mapper%2030.patch patch]] for FCEUX that both puts the mapper as 30, and implements NES 2.0. [[User:Caitsith2|Caitsith2]] ([[User talk:Caitsith2|talk]]) 09:01, 1 April 2014 (MDT) | :I have formed a [[https://dl.dropboxusercontent.com/u/20737085/nes%202.0%2C%20mapper%2030.patch patch]] for FCEUX that both puts the mapper as 30, and implements NES 2.0. [[User:Caitsith2|Caitsith2]] ([[User talk:Caitsith2|talk]]) 09:01, 1 April 2014 (MDT) | ||
::OK, now it makes sense; no submapper numbers are needed. The jumpers would then be to make the board act as if there is less CHR RAM than there actually is (I suppose, it is in case you have a ROM image that specifies only 8K (or 16K) CHR RAM, and you will want to use it with the existing board). I further suppose, then, I would guess that you would set the PRG RAM sizes in the NES 2.0 header (at least one of which is zero) to put into $6000-$7FFF, which would seem to be the default specification of such a thing, if not otherwise specified; since battery bit means something else with this mapper, these PRG battery/non-battery RAM would be separate from flashed ROM (although, probably you should not install battery RAM anyways, in case something is mixed up due to that). --[[User:Zzo38|Zzo38]] ([[User talk:Zzo38|talk]]) 17:17, 1 April 2014 (MDT) | ::OK, now it makes sense; no submapper numbers are needed. The jumpers would then be to make the board act as if there is less CHR RAM than there actually is (I suppose, it is in case you have a ROM image that specifies only 8K (or 16K) CHR RAM, and you will want to use it with the existing board). I further suppose, then, I would guess that you would set the PRG RAM sizes in the NES 2.0 header (at least one of which is zero) to put into $6000-$7FFF, which would seem to be the default specification of such a thing (although FCEUX and some others may not necessarily implement it), if not otherwise specified; since battery bit means something else with this mapper, these PRG battery/non-battery RAM would be separate from flashed ROM (although, probably you should not install battery RAM anyways, in case something is mixed up due to that). --[[User:Zzo38|Zzo38]] ([[User talk:Zzo38|talk]]) 17:17, 1 April 2014 (MDT) |
Revision as of 23:26, 1 April 2014
What is the iNES number for this? Do you need submapper numbers for one-screen mirroring mode and flashing configuration? What are the jumpers for configuring CHR RAM? --Zzo38 (talk) 06:30, 1 April 2014 (MDT)
- Was planning on having this as iNES number 30. The flashing configuration is enabled by the iNES battery flag, and the one-screen mirroring is done by setting the four-screen mirroring flag. If the rom is using NES 2.0, then the non-battery backed CHR RAM field is used to specify how much CHR Ram is enabled.
- As for the jumpers that configure the CHR Ram, there is 4 of them on the board. Two of them tie the respective CHR-RAM address lines to Vcc, and the other two tie the respective CHR Ram lines to the 377 outputs. Basically, for 8KB, both CHR-RAM lines are tied to Vcc, for 16KB, only one of them is tied to Vcc, and for 32KB, none of them are tied to Vcc. Caitsith2 (talk) 08:50, 1 April 2014 (MDT)
- I have formed a [patch] for FCEUX that both puts the mapper as 30, and implements NES 2.0. Caitsith2 (talk) 09:01, 1 April 2014 (MDT)
- OK, now it makes sense; no submapper numbers are needed. The jumpers would then be to make the board act as if there is less CHR RAM than there actually is (I suppose, it is in case you have a ROM image that specifies only 8K (or 16K) CHR RAM, and you will want to use it with the existing board). I further suppose, then, I would guess that you would set the PRG RAM sizes in the NES 2.0 header (at least one of which is zero) to put into $6000-$7FFF, which would seem to be the default specification of such a thing (although FCEUX and some others may not necessarily implement it), if not otherwise specified; since battery bit means something else with this mapper, these PRG battery/non-battery RAM would be separate from flashed ROM (although, probably you should not install battery RAM anyways, in case something is mixed up due to that). --Zzo38 (talk) 17:17, 1 April 2014 (MDT)