| 30 Mar 2021 |
|  Olof Kindgren joined the room. | 11:56:33 |
| Olof Kindgren | Hey there, space cats | 11:57:02 |
|  Luisovich joined the room. | 12:01:39 |
 Lofty | Hi Olof Kindgren | 12:03:14 |
| Olof Kindgren | Hi Lofty. Shouldn't you be in the 7400 channel? 🙂 | 13:38:45 |
| Lofty | Heh | 13:39:29 |
| Olof Kindgren | Oh, just realized something. I'm planning to make it possible to use SERV with a single-port SRAM. Remembered just now that you said at some point that it was hard to find synchronous dual-port SRAM chips | 13:41:19 |
 mehdi | In reply to@_slack_skywater-pdk_U01S3KU0DFX:matrix.org
Hopefully not bringing up an old question here, but something that strikes me when reading the the docs is how there is a singular CLOCK_PERIOD and CLOCK_NET/PORT variable. Are designs with multiple clocks not supported? There is only support for one clock in openroad. Bu i think there are plans to enhance that. | 13:45:08 |
 Klas Nordmark | In reply to@_slack_skywater-pdk_U0169AQ41L6:matrix.org
There is only support for one clock in openroad. Bu i think there are plans to enhance that. Thanks! Not a problem for me right now, but good to know. | 13:46:16 |
| Olof Kindgren | So, I'll pop the question here too. I'm looking at config.tcl and how it is referenced by flow.tcl in an attempt to make it slightly more convenient to use from FuseSoC/Edalize. And out of nowhere pops up a reference to config.json. Anyone knows how it all fits together? | 13:47:17 |
 matt venn | In reply to@_slack_skywater-pdk_U01S3KU0DFX:matrix.org
Thanks! Not a problem for me right now, but good to know. I've seen this as a way of specifying multi clocks: https://github.com/miscellaneousbits/caravel_sha3_256_crypto_miner/blob/b85a2b0a8d[…]1617f3471db70718e9a9d1c84/openlane/user_proj_example/config.tcl | 15:06:56 |
| matt venn | In reply to@_slack_skywater-pdk_U0172QZ342D:matrix.org
I've seen this as a way of specifying multi clocks: https://github.com/miscellaneousbits/caravel_sha3_256_crypto_miner/blob/b85a2b0a8d[…]1617f3471db70718e9a9d1c84/openlane/user_proj_example/config.tcl but not really looked into it | 15:07:07 |
|  Matthew Pauly joined the room. | 16:46:18 |
|  Christopher Torng joined the room. | 18:33:20 |
| 31 Mar 2021 |
|  Amod Wani joined the room. | 05:18:02 |
 Ahmed Ghazy | In reply to@_slack_skywater-pdk_U016HSA1H5Y:matrix.org
So, I'll pop the question here too. I'm looking at config.tcl and how it is referenced by flow.tcl in an attempt to make it slightly more convenient to use from FuseSoC/Edalize. And out of nowhere pops up a reference to config.json. Anyone knows how it all fits together? config.json is an optional alternative to config.tcl in situations where it's not a good idea to source a tcl file (e.g., for security reasons). You can ignore it altogether if it makes your life easier. | 07:46:28 |
| Olof Kindgren | In reply to@_slack_skywater-pdk_U016HSALFAN:matrix.org
config.json is an optional alternative to config.tcl in situations where it's not a good idea to source a tcl file (e.g., for security reasons). You can ignore it altogether if it makes your life easier. Cool. I'll probably go with the tcl file then | 07:51:04 |
 Nguyen.Dao | Hi, does anybody know whether we can set timing constraints for OpenPhySyn Timing Optimization? Seems this tool doesn’t support STA commands like get_pins, etc.
(We also discuss this issue in #skywater-pdk_fpga:matrix.org channel) | 10:13:01 |
| Klas Nordmark | Does anyone know where the add_macro_obs command is implemented? Going through the caravel scripts to learn some lessons, and this rather important command in particular is invalid and doesn't seem to show up anywhere in the repo except documentation? | 12:13:11 |
| Klas Nordmark | working with rc7, if relevant | 12:14:17 |
| matt venn | 
Download image.png | 13:00:30 |
| matt venn | In reply to@_slack_skywater-pdk_U01S3KU0DFX:matrix.org
working with rc7, if relevant all.tcl looks like it defines it | 13:00:41 |
| Klas Nordmark | In reply to@_slack_skywater-pdk_U0172QZ342D:matrix.org
all.tcl looks like it defines it Where I would expect it. I'm working on the wrong tag I guess | 13:22:41 |
| Klas Nordmark | In reply to@_slack_skywater-pdk_U01S3KU0DFX:matrix.org
Where I would expect it. I'm working on the wrong tag I guess Thanks | 13:23:11 |
| Olof Kindgren | In reply to@_slack_skywater-pdk_U01S3KU0DFX:matrix.org
Thanks So, are we switching tags? | 13:35:25 |
| Klas Nordmark | In reply to@_slack_skywater-pdk_U016HSA1H5Y:matrix.org
So, are we switching tags? I've just switched to mpw-one-b, gonna make sure everything works | 13:35:54 |
| Nguyen.Dao | Hi, can we run the openlane flow on multiple cores? Or is there any option to speed it up? | 13:38:43 |
| Olof Kindgren | In reply to@_slack_skywater-pdk_U01S3KU0DFX:matrix.org
I've just switched to mpw-one-b, gonna make sure everything works Is it enough to just switch tags in the runner script? | 13:39:45 |
| Ahmed Ghazy | In reply to@_slack_skywater-pdk_U01L8BR7FFA:matrix.org
Hi, can we run the openlane flow on multiple cores? Or is there any option to speed it up? Currently you can only set the number of threads to use for detailed routing, which takes the longest, using the ROUTING_CORES parameter. | 13:39:59 |
| Olof Kindgren | In reply to@_slack_skywater-pdk_U016HSA1H5Y:matrix.org
Is it enough to just switch tags in the runner script? I haven't figured out how these docker workflows work | 13:40:17 |
