Good First Issues in Verilog

The Toki core have a sound issue with the game’s main theme. There is a high-pitched crackling noise that is clearly audible. Strangely, the game’s other tracks do not seem to be affected. Here is the theme in question played correctly, as on the PCB: https://www.youtube.com/watch?v=J5d-D4bVIJY&list=PLErsx10Ke4uzcHIBInycHw1smZvgnkVUU&index=4 An audio crackle (not present on the PCB) can also be heard when flying enemies are destroyed only.

We should include logger_->metric() for some relevant metrics, this allows for having them available in the dashboard for evaluations. For example, these final values, which are only available in the log files, not json currently: [INFO GPL-1001] Global placement finished at iteration 2047 [INFO GPL-1017] Routability mode iteration count: 1604 [INFO GPL-1005] Routability final weighted congestion: 1.1051 [INFO GPL-1011] Original area (um^2): 26000.50 [INFO GPL-1012] Total routability artificial inflation: 1284.63 (+4.94%) [INFO GPL-1013] Total timing-driven delta area: 8451.95 (+32.51%) [INFO GPL-1014] Final placement area: 35737.08 (+37.45%) [INFO GPL-1018] Final HPWL (um): 694084.76 Easy to implement, we just need a logger_->metric() for each with a proper naming.

Description The previous issue #10749 and PR #10769 had some tests which were not yet isolated. aberndt@dev-secure-augusto:~/workspace/masterCode/tools/OpenROAD/src$ grep -rin detailed_placement cts/test/array_dummy.tcl:147:detailed_placement cts/test/array_full_flow.tcl:146:detailed_placement cts/test/array_no_blockages.tcl:145:detailed_placement cts/test/array_max_wl.tcl:147:detailed_placement cts/test/array.tcl:148:detailed_placement cts/test/array_repair_clock_nets.tcl:149:detailed_placement cts/test/array_ins_delay.tcl:146:detailed_placement The PR #11089 required updating some of those, we would not need to update them if CTS tests were all isolated. Suggested Solution We should remove DPL and GPL calls from CTS regression tests. We should generate a DEF file including the output of tools other than CTS commands, replacing the necessity of the exterior commands. Additional Context No response

Did some lengthy playthroughs of the updated core today and noted 1 semi-common sprite glitch and 1 audio glitch that only happened once. The sprite glitch seems to happen only sometimes at the end of level (when the player does the little dance animation). https://neondagger.com/upload/cabal/Cabal_sprite_glitch.MOV The conditions for the glitch seem somewhat predictable but also somewhat random. It usually does not happen, but seems to happen every time at the end of Level1 boss battle (see video). I could be wrong, but I think it also is more likely to occur if the character is on the right hand side of the screen when the animation occurs. The sprite glitch is a vertical and sometimes horizontal line through the player, and sometimes even briefly flashes a garbled cluster of sprite data around where the player is. But this is only for a frame or two so I wasn't able to capture it or note the exact detail from observation alone. For the audio glitch, I wasn't recording but at one tim

NGPC Link Cable Support through MiSTer USERIO and Pocket Link Port Supported Games: https://www.mygamer.com/neogeo-pocket-color-2-player-link-cable-games-the-complete-ultimate-list/ Supposedly, NeoPop had support for the link cable: https://github.com/ONLYUSEmeFEET/NeoPop0.71-Win32-FINAL-Source-Code Some technical information: https://devrs.com/ngp/files/DoNotLink/ngpcspec.txt

Description This is a public tracker for feature development for the ram tool. Add support for endcap insertion Endcaps need to be inserted around the perimeter of the RAM bounding box after fill Physical verification Check that timing, LVS, and DRC are clean via external tools Sweep word and bit sizes 1-64 (all values) to verify support for arbitrary array sizes (no placement or routing errors, LVS clean, DRC clean, passes STA) Add support for AND3/AND4 cells in the decoder Only AND2 is supported now. Larger arrays can be more efficient with wider ANDs Add support for automatic master selection Find and identify FFs, ICGs, buffers, inverters, tristates, AND2/3/4s automatically if not user specified Automatic detection of the followpin metal layer and width The current implementation requires manual specification of the followpin layer and width. This should be automatically extractable from the library. The user should not need to specify this. Add support for

Could not find the documentation, how the LED's are used by the NanoMig. It seems that LED Nr. 1 is Core Ready? LED 2 Floppy Activity? LED 3 and 5 blink on HDD activity simultaniously? What are 4 and 6 for? What does the RGB LED signal? Would like to add the information to the readme.... Thanks!