Repository navigation
Conversation
The output muxes above the 16-word slices (RAM32 and up) selected by the current address, while the slices register their output at the rising edge. A read was only correct if the upper address bits stayed the same in the next cycle. Register the select at the rising edge as well, so the output is the word addressed at that edge (read latency 1). - MUX2x1/MUX4x1 (sky130, gf180): CLK input and a select register (SELREG); every output mux gets its module's clock - placeram: place SELREG in front of the select buffers - clock tree: the select registers load the clock nets, which made the input hold times worse. Stronger root clock buffer (CLKBUF_16) in RAM128/RAM1024/RAM2048, and a root clock buffer in RAM256/RAM512, where the clock pin drove the whole macro directly
7FM
force-pushed
the
registered-mux-select
branch
from
October 2, 2026 08:43
fa3d964 to
6ebaec5
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The output muxes above the 16-word slices (RAM32 and up) selected by the current address, while the slices register their output at the rising edge. A read was only correct if the upper address bits stayed the same in the next cycle. Register the select at the rising edge as well, so the output is the word addressed at that edge (read latency 1).