Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP] Group LRAM timings by cell configuration #29

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

mkurc-ant
Copy link
Contributor

The LRAM clock-to-q timings seem pretty high (~10ns) as the datasheet says that the worst case fmax is around 130MHz.

To investigate this I isolated LRAM fuzzing to a separate fuzzer, added randomizing output register enabling and added grouping of fuzzed timings by cell types and their configurations.

This is a work in progress, currently I get the following results for the grouping:

LRAM timing groups (CLK -> DOA|DOB) speed 10:
DPC512K
 ('NO_REG', 'CLK_to_DOA') {((13880, 14646), (13880, 14646))}
 ('NO_REG', 'CLK_to_DOB') {((13979, 14732), (13979, 14732)), ((1145, 2022), (1145, 2022))}
 ('OUT_REG', 'CLK_to_DOA') {((1099, 1994), (1099, 1994))}
 ('OUT_REG', 'CLK_to_DOB') {((13979, 14732), (13979, 14732)), ((1145, 2022), (1145, 2022))}
PDPSC512K
 ('OUT_REG', 'CLK_to_DOB') {((1145, 2022), (1145, 2022))}
 ('NO_REG', 'CLK_to_DOB') {((13979, 14732), (13979, 14732))}
SP512K
 ('OUT_REG', 'CLK_to_DOA') {((1096, 1995), (1096, 1995))}
 ('NO_REG', 'CLK_to_DOA') {((9019, 9788), (9019, 9788))}

For some combinations there are two timing sets while there should be only one.

# Leave only the relevant OUTREG setting
if rewritten[2] == "DOA" and "OUTREG_A" in cf["params"]:
cf["params"]["OUTREG"] = cf["params"]["OUTREG_A"]
del cf["params"]["OUTREG_A"]
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this del of both params seems kind of suspicious to me

@gatecat
Copy link
Owner

gatecat commented Oct 19, 2022

no worries if you've been busy but I'm wondering if the force-push fixed things at all?

@mkurc-ant
Copy link
Contributor Author

Hi, I'll do the rebase once I carve some time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants