diff --git a/Changes.txt b/Changes.txt index 22a60f4b2..278a1bc5f 100644 --- a/Changes.txt +++ b/Changes.txt @@ -12,7 +12,7 @@ Release History =========================================================================== -3.1.2 to 3.2: (August 16, 2010) +3.1.2 to 3.2: (August 20, 2010) * NOTE: because of the many event-related changes in this release, all event mapping should be reset to defaults after starting Stella for @@ -34,12 +34,21 @@ now works exactly like an axis in UI mode (holding down a direction continues that direction until the hat is released/centered). - * Several improvements to the debugger: - - user labels are now supported again - - 'runto' debugger command is now case-insensitive, and shows a - progressbar while searching through the disassembly + * Several major improvements to the debugger: + - the disassembler can now process multiple entry points, and + caches entry points as they're encountered (ie, the disassembly + isn't 'reset' each time a bank change occurs or you exit and + re-enter the debugger) + - preliminary support for disassembling from zero-page RAM + - re-added ability to change banks with the 'bank' debugger + prompt command and within the ROM disassembly UI + - user labels in disassembly are now supported again + - 'runto' command is now case-insensitive, and shows a progressbar + while searching through the disassembly - the debugger window can be resized between ROM loads (previously, the app had to be restarted) + - fixed bug in Distella disassembler output, where it sometimes + generated addresses above $FFFF - a vertical line separates the disassembly from the raw bytes * Fixed behaviour of SWCHB and SWBCNT; pins set to output now remember @@ -48,15 +57,23 @@ and test ROMs in this area. * Fixed bug when reading from illegal TIA addresses; a Space Invaders - hack was showing pink enemies instead of white ones. + hack was showing pink enemies instead of white ones. Again, special + thanks to to Omegamatrix of AtariAge for advice and test ROMs in this + area. * Fixed bug in handling INPT4/INPT5 latches from VBLANK; a least one ROM was working in Stella when it didn't on real hardware. + * Added 'ramrandom' commandline argument, which is used to randomize + all RAM in the system; otherwise, the RAM is zeroed. This defaults + to off, which is different than previous versions of Stella. + * Added 'finishing touches' to some of the UI descriptions, giving a better explanation of the functions. Related to this, certain options now show a message box explaining the option in further - detail (particularly the ROM Audit mode). + detail (particularly the ROM Audit mode). As well, when starting + Stella for the first time, a prompt appears to select a ROM + directory. * Fixed bugs in the ROM launcher when viewing certain PNG images not created by Stella. Related to this, the official PNG library is now @@ -64,9 +81,6 @@ snapshots for those ROMs which consist of several games. Thanks go to Buzbard of AtariAge for these images. - * Fixed bug in Distella disassembler output, where it sometimes - generated addresses above $FFFF. - * Added several fixes for crashes on 'small' systems (those systems where the maximum resolution is less than 640x480). diff --git a/Readme.txt b/Readme.txt index 7860d6733..509b34e7e 100644 --- a/Readme.txt +++ b/Readme.txt @@ -9,4 +9,4 @@ the Stella Website at: Enjoy, The Stella Team -August 16, 2010 +August 20, 2010 diff --git a/docs/debugger.html b/docs/debugger.html index 60121243e..b2cc9128f 100644 --- a/docs/debugger.html +++ b/docs/debugger.html @@ -64,8 +64,8 @@ feature that no other 2600 debugger has; it's completely cross-platform.<
a - Set Accumulator to value xx + bank - Show # of banks, or switch to bank xx base - Set default base (hex, dec, or bin) break - Set/clear breakpoint at address xx (default=PC) breakif - Set breakpoint on condition xx @@ -932,11 +933,10 @@ TIA/RIOT labels will still be present.The top area contains two items:
The 6502 mnemonic will be UPPERCASE for all standard instructions, or lowercase for "illegal" 6502 instructions (like "dcp"). If resolving of data sections has been disabled for any reason, you'll likely see a lot -of illegal opcodes if you scroll to a data table in ROM.
+of illegal opcodes if you scroll to a data table in ROM. This can also +occur if the disassembler hasn't yet encountered addresses in the PC. +If you step/trace/scanline/frame advance into such an area, the disassembler +will make note of it, and disassemble it correctly from that point on.