open-source-silicon.dev

<@U017REC9K36>:  I assumed that the DFFRAM had something to do with the caravel chip, but reading the above lines closer, it seems to be within the openlane distribution, not caravel?

Checking now with openlane master. I was on openlane "rc4".

Ignore what I said, then.  Has nothing to do with openlane.

adding
````define MEM_WORDS 256```
at the top of DFFRAM.v seems to have kicked that issue. Have a few "no network has been linked" issues in OpenSTA now

<@U017REC9K36>: Pull caravel again now. I have pushed the config I am using locally, so hardening DFFRAM should work now.

<@U017REC9K36>: I am still working on the other blocks though, so the config may not yet be perfect.

okay, much appreciated! I pulled the latest release branch and still have the same error. I think I've about figured it out though.

Slightly different this time around: <https://gist.github.com/sjkelly/5d547f4197828cae60f747369355f64d>

Okay I see it is this issue: <https://github.com/google/skywater-pdk/issues/172> <@U016HSALFAN> <@U016EM8L91B>. Looks like <@U01634FSETZ> is resolving in a few days. xref <#C016H8WJMBR|openlane>

<@U017REC9K36>: just to clarify, we will resolve it on *develop* in a day or two. But, it will take an extra 3~4 days to get to *master*. So, if you want the VNB and VPB pins right away, you can use the latest open_pdks/skywater-pdk with openlane:rc4 (the current master).

<@U017REC9K36>: Please re-try with the latest commit of caravel. This should build successfully now.

<https://github.com/efabless/caravel/issues/1> Should I try again with openlane master? That is with develop branch