-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
6fc0f4c
commit 6279aed
Showing
1 changed file
with
29 additions
and
48 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,70 +1,51 @@ | ||
| - [ ] Why are some sprites flipped around? | ||
| - [x] Figure out why sprites aren't drawing | ||
| - wasn't writing to OAM DMA correctly | ||
| - [ ] integrate code coverage into CI. (maybe add a repo tag in README) | ||
| - [ ] Add scrolling support | ||
| - [ ] Bug: Why are some sprites flipped around? | ||
| - afaict it's a bug with drawing or tile lookup, not with flip horiz / flip vertical | ||
| - [..] Add tests cases for PPU registers | ||
| - [ ] Integrate code coverage into CI. (maybe add a repo tag in README) | ||
| https://github.com/xd009642/tarpaulin | ||
| https://medium.com/@gnanaganesh/robust-rust-how-code-coverage-powers-rust-software-quality-417ef3ac2360 | ||
| https://blog.balthazar-rouberol.com/measuring-the-coverage-of-a-rust-program-in-github-actions | ||
| - [ ] migrate to bitfields (from bitflags) | ||
| - [ ] Migrate to bitfields (from bitflags) | ||
| - https://docs.rs/bilge/latest/bilge/ | ||
| - https://gitlab.com/SmartAcoustics/sparrow/-/blob/master/sparrow-bitpacker/src/bitfields.rs | ||
| - https://github.com/wrenger/bitfield-struct-rs | ||
| - https://github.com/gregorygaines/bitfields-rs | ||
|
|
||
| - [ ] Try an external debugger and setting breakpts | ||
| - [ ] Debugger view | ||
| - show both pattern tables beside the UI | ||
| - allow play/pause of CPU | ||
| - show current instruction | ||
| - when we get to sprite drawing, | ||
| - log the details | ||
| - highlight which pattern is being used | ||
| - show state of CPU (same idea as "trace") | ||
| - [ ] Debugger | ||
| - allow requesting a to break at a given pc position (run until pc=X) or at a given OP (run until op=STA) | ||
| - this would let me quickly inspect processor state to repair issues in nestest | ||
| - this would help me not run too far when isolating an issue. in particular in my current PPU debugging | ||
| - Try an external debugger and setting breakpts | ||
| - Debugger view | ||
| - show both pattern tables beside the UI | ||
| - allow play/pause of CPU | ||
| - show current instruction | ||
| - when we get to sprite drawing, | ||
| - log the details | ||
| - highlight which pattern is being used | ||
| - show state of CPU (same idea as "trace") | ||
| - Is there a way to get a nice trace that doesn't manipulate registers which cause side effects of READ operations? | ||
| - consider a non-mut mem_peek() fn, that's safe in debugging/tracing | ||
| - [ ] Try running more NES Test roms, maybe they can help now that i have some graphics? | ||
| - lots of the PPU test rom links here are broken.. https://www.nesdev.org/wiki/Emulator_tests | ||
| - [ ] Investigate crash that is trying to write to wrong memory | ||
| - Right now, running a trace causes a program to fail | ||
| I wrote a `tracelite` operation to explore this. | ||
| I also modified `trace` to skip the address lookups, and this was usable enough for debugging (but broke some hard-coding in tests). | ||
| - PR upstream: Explain in the book that trace() needs to be deactivated (if it does) due to side-effects of READ ops | ||
| - [ ] More NES Test roms | ||
| - Try running more NES Test roms, maybe they can help now that i have some graphics? | ||
| - Lots of the PPU test rom links here are broken.. https://www.nesdev.org/wiki/Emulator_tests | ||
| - [ ] Bug: crash that is trying to write to wrong memory | ||
| - Repro-able by running Pacman a few times | ||
| ``` | ||
| thread 'main' panicked at src/ppu.rs:362:26: | ||
| attempt to write to CHR ROM: 0000 (read-only) | ||
| ``` | ||
|
|
||
| -- | ||
|
|
||
| - [ ] refactor to split up functionality more | ||
| - why? one of my goals is to learn better Rust patterns for project layout | ||
| - why? I would find it easier to think about testable units | ||
| - [ ] Debugger | ||
| - [ ] allow requesting a to break at a given pc position (run until pc=X) or at a given OP (run until op=STA) | ||
| - this would let me quickly inspect processor state to repair issues in nestest | ||
| - this would help me not run too far when isolating an issue. in particular in my current PPU debugging | ||
| - [ ] allow lookup of opcode from op name + addressing mode, esp for use in tests to give clarity and reduce typos of op codes | ||
| - [ ] add tests cases for PPU registers | ||
| - [ ] Allow lookup of opcode from op name + addressing mode, esp for use in tests to give clarity and reduce typos of op codes | ||
| - [ ] Modify the test "Snake" game to work without changing the program start address | ||
| - This should require updating any jmp instructions | ||
| - [ ] Extract "tileset viewer" subproject | ||
| - CLI that you run and it pops up a view of the game's tilesets | ||
| - [ ] Extract subproject: 6502 emulator .. as REPL? | ||
| - review emails/etc where I suggested other nice subprojects, too. | ||
| - [ ] Is there a way to get a nice trace that doesn't manipulate registers which cause side effects of READ operations? | ||
| Right now, running a trace causes a program to fail :( :( | ||
| I wrote a `tracelite` operation to explore this. | ||
| I also modified `trace` to skip the address lookups, and this was usable enough for debugging (but broke some hard-coding in tests). | ||
|
|
||
| - Get the snake game running | ||
| ``` | ||
| pc=0x06cc (program idx=204) op=0x10 | ||
| pc=0x07c7 (program idx=455) op=0x00 | ||
| SHOULD BE: 06c7 | ||
| - 00110001 (bits 45 are on in snake.. BRK ones) | ||
| Learn | ||
| - arithmetic vs logical shift | ||
| ------------- | ||
| PRs upstream: | ||
| - [ ] Explain in the book that trace() needs to be deactivated (if it does) due to side-effects of READ ops |