nesdev.com

Fiskbit, thank you once again! :D I realize, from new thread conversation, that Sour is on an indefinite break now. He’s done so much; though, I hope he comes back sometime. :) I have a suggestion: You say that it would be rough to allow Mesen to show serial registers bc there are so many mappers. T...

tokumaru, NESASM is so weird.

I’m sorry Pixel_Kronicle and sdm2.

Based on your edit, you mean w in the PPU? That's shown in the debugger as "Write Toggle", and yeah, you can see the state of w in the event viewer on $2005 and $2006 writes. Thank you so much Fiskbit! :D “Write Toggle” in the debugger makes the process much faster! :) I’m not sure if I mean w in t...

According to nesdev wiki , the serial register can be lost if NMIs occur, but rendering and NMIs on VBlank have been disabled... so this still doesn’t make sense. Will continue to work this weirdness out. :) edit: Fiskbit, (Thank you Fiskbit! :D), sheds light on this problem in Sour’s Mesen thread: ...

Is is possible to see the state of the serial register while using Mesen? (Maybe I’ve asked this before.)

edit: sry, if the debugger’s Event Viewer is opened, it’s evident that the last write to $2006 set the 2nd write flag.

sdm2’s code: lda paddley clc adc #1 cmp <temp bcc coll_no can be simplified with x or y register use: ldy paddley iny cpy temp bcc coll_no bc incrementing by 1 is much easier when using either the x or y register. That code change saves you 2 bytes and 2 cycles. Yes, the 6502 chip was created with r...

< returns low byte of memory location > returns high byte of memory location < and > only work in certain assemblers; if you are using another assembler, like NESASM, the low-byte and high-byte syntax will be different. Don’t know that “sta <temp” is possible. It doesn’t make much sense to me anyway...

I’ve never used NESASM, so I don’t know what’s possible, but CHR should be written to $0000-0FFF (and $1000-$1FFF) on the PPU. At least, in asm6, it’s impossible to use .org to access PPU memory space. Sry, forgot that I’m using CHRRAM. When using CHRROM, like I used to, you can .incbin “blah.chr”,...

I strongly suspect that PRG ROM only occupies banks 0 and 1 and that bank 2 actually corresponds to the PPU's address space, which would be totally normal if NESASM was the assembler being used (which seems to be the case). I’ve never used NESASM, so I don’t know what’s possible, but CHR should be ...

If you remove the spaces-indent, needed by NESASM for assembler directives, on assembler directive lines (the . starts an assembler directive), that will cause the assembler to throw convoluted errors at you. That happens to me sometimes when asm6, the assembler I’m using, gives odd error messages f...

It doesn’t seem that simple to me... As Dwedit said, lda #n is two cycles; it’s also 2 bytes. lda zpg is three cycles; but also 2 bytes. Oooh, you mean you’d start with 2 cycles and add 1 cycle for the byte fetched from memory. :) Though, you’d have to add another cycle for the high byte used in the...

Ooh, I use .cdl hex codes: If bit7 is set, that marks the start of a function. If bit0 is set, that makes the code active (or makes it appear like it has already been run). A hex code of #$02 specifies that the byte is part of a data section. A hex code of #$00 specifies that the byte is part of unk...

This can be done with the "Mark selection as..." option in the right click menu either in the memory tools or the debugger's disassembly view, though the latter has the shortcoming that it can't be done on a byte-by-byte granularity. tokumaru, to speed up the “Mark selection as...” process, and to ...

^What would you check if the MMC1 PRG banks suddenly become bank #0 and bank #1, after the first, of 5, bank-switching writes to ROM?

PRAISE GOD!! :D :mrgreen: Wow! Can log in again! Thank you so much tepples, and, on IRC, Kufat, jero32, and genuisAZK (I think that’s how it’s spelled)! :D —- Our game uses MMC1; it’s set to use 32 PRGROM banks, 8kb of PRGRAM, and 8kb of CHRRAM. PRGROM Banks #15 and #31 are the only banks that can b...