Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
05719 Misc. Minor Always Oct 12, 2014, 16:14 Dec 22, 2022, 00:09
Tester demotester View Status Public Platform
Assigned To Resolution Open OS
Status [?] Confirmed Driver
Version 0.154 Fixed in Version Build
Fixed in Git Commit Github Pull Request #
Summary MESS-specific 05719: nes: Failed on some of known CPU tests.
Description CPU-Tests (for NTSC Nes)
-------------------------------------
nestest ........................ http://wiki.nesdev.com/w/index.php/Emulator_Tests ...... Passed
instr_test ..................... http://wiki.nesdev.com/w/index.php/Emulator_Tests ...... Passed
instr_misc ................... http://wiki.nesdev.com/w/index.php/Emulator_Tests ...... Failed -> 04-dummy_reads_apu
instr_timing ................. http://wiki.nesdev.com/w/index.php/Emulator_Tests ...... Failed all
cpu_interrupts_v2 ...... http://wiki.nesdev.com/w/index.php/Emulator_Tests ...... Failed all
cpu_reset ..................... http://wiki.nesdev.com/w/index.php/Emulator_Tests ......Failed -> registers
cpu_dummy_writes ... http://forums.nesdev.com/viewtopic.php?t=8738 ............ Failed all
cpu_exec_space ........ http://forums.nesdev.com/viewtopic.php?t=8755 ............ Failed -> test_cpu_exec_space_apu
Steps To Reproduce
Additional Information JFI ... AFAIK, only emu that passed all CPU tests is puNES v0.90
Github Commit
Flags
Regression Version
Affected Sets / Systems nes
Attached Files
 
Relationships
There are no relationship linked to this issue.
Notes
2
User avatar
No.20582
AJR
Developer
Oct 2, 2022, 01:44
Some of these are not faults in the CPU emulation itself, but in the emulation of the on-chip APU. For instance, the frame IRQ which the 04-dummy_reads_apu test relies on is missing entirely.
User avatar
No.20974
kmg
Senior Tester
Dec 22, 2022, 00:09
Upcoming 0.251 has bare minimum frame IRQ support—especially useful because it is used in some test programs that aren't even meant to test the APU IRQs.

Anyway, along with other improvements current status is:
nestest ........................ Passed
instr_test ..................... Passed
instr_misc ................... Passed
instr_timing ................. Passed
cpu_interrupts_v2 ....... Failed #2 and beyond
cpu_reset .................... Failed -> registers*
cpu_dummy_writes .... Passed
cpu_exec_space ........ Failed -> test_cpu_exec_space_apu

* Could be fixed by setting X = 80 and Z flag at power up. Is this actually reliable hardware behavior or just of the test author's particular CPU?