ROM cartridge writing detection

[clinton/Virtual-Jaguar-Rx.git] / docs / vj_ReleaseNotes.txt

diff --git a/docs/vj_ReleaseNotes.txt b/docs/vj_ReleaseNotes.txt
index 8c5964f..b968540 100644 (file)
--- a/docs/vj_ReleaseNotes.txt
+++ b/docs/vj_ReleaseNotes.txt
@@ -7,6 +7,9 @@ Release 4 (TBD)
 4) Switch to SDL 1.2.15 static library 64bits for VS 2017\r
 5) Local variables window displays values from function's parameters\r
 6) Fixed the typedef's name display in Local and Watch variables window\r
+7) ROM cartridge writing detection follow the alpine "allow writes to cartridge rom"'s flag check\r
+-- Breakpoint can now occur in the case of a ROM cartridge writing\r
+-- Alert box will display a message with possibility to pass or not the breakpoint only if this is related to a 8 or 16 bits ROM access\r
 \r
 Release 3 (13th November 2017)\r
 ------------------------------\r
@@ -101,7 +104,8 @@ Known issues
 1) Video output is not displayed due to my OpenGL / QT5 5.5.1 integration with VS 2015 but solved when using the QT 5.9.1 package for VS 2017\r
 2) The BPM (Breapoint) remains stuck on his address when user wants to continue the code execution\r
 -- Need to trace over the BPM or unset the BPM\r
-3) To handle DWARF 2 issues with GCC, the code must be compiled with the -gdwarf-2 option\r
+-- The issue can be prevented if the code doesn't set IRQ, otherwise the IRQ will need to be traced to get back control\r
+3) To support DWARF 2 with GCC, the code must be compiled with the -gdwarf-2 option\r
 4) The Local and Watch variables list may display not available (N/A) type information\r
 -- Such missing information may be included in future release\r
 5) The 2MB mirroring is no longer applied in case of --dram-max option usage\r
@@ -111,7 +115,8 @@ Known issues
 -- Missing vectors may be added in future release\r
 8) User needs to manualy check if the Atari Jaguar executable match his source code files\r
 -- Otherwise, source code and assembly may not match or leads to instabilities\r
-9) Application needs to be restarted in case of keybindings changes\r
+9) The emulator needs to be restarted in case of keybindings changes\r
+10) In the case of a ROM cartridge writing, and an occuring breakpoint, the PC pointer will point at the next instruction and not at the instruction causing the breakpoint\r
 \r
 Cosmetic / UX issues\r
 ====================\r