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

to confirm whether the change of nvseq and nvlreq is right #11

Open
gxlong1983 opened this issue Mar 15, 2019 · 0 comments
Open

to confirm whether the change of nvseq and nvlreq is right #11

gxlong1983 opened this issue Mar 15, 2019 · 0 comments

Comments

@gxlong1983
Copy link

Hi,

When we change the value of the parameter HwachaNVectorRegs and HwachaNSRAMRFEntries into 32, we found that the nvsreq and nvlreq in hwacha.scala are not satisfied and an error is reported as follows.
firrtl.passes.CheckWidths$BitsWidthException: @[dcc-mem.scala 613:33:[email protected]]: [module VLU] High bit 9 in bits operator is larger than input width 5 in bits(_T_1675, 9, 0).
firrtl.passes.PassException: 4 errors detected!

after we change the nvsreq and nvlreq as below, there is no error.

val nvsreq = math.max(p(HwachaNVectorRegs), p(HwachaNSRAMRFEntries)) * p(HwachaBankWidth) / p(HwachaRegLen)
val nvlreq = math.max(p(HwachaNVectorRegs), p(HwachaNSRAMRFEntries)) * p(HwachaBankWidth) / p(HwachaRegLen)

Could you please confirm whether the change for nvsreq and nvlreq is right? thanks.

--gao

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

No branches or pull requests

1 participant