<_whitenotifier-3>
[yosys-symbiflow-plugins] tmichalak opened issue #6: Travis: Add travis utility functions to for adding sections instead of echos - https://git.io/JvOuE
proteus-guy has quit [Ping timeout: 268 seconds]
seraxis has quit [Quit: おやすみ]
synaption[m] has left #symbiflow ["Kicked by @appservice-irc:matrix.org : User has been idle for 30+ days."]
synaption[m] has quit [Quit: User has been idle for 30+ days.]
seraxis has joined #symbiflow
proteus-guy has joined #symbiflow
seraxis has quit [Quit: おやすみ]
luaraneda has left #symbiflow ["Kicked by @appservice-irc:matrix.org : User has been idle for 30+ days."]
Bertl_zZ is now known as Bertl
space_zealot has joined #symbiflow
galv[m] has quit [Quit: User has been idle for 30+ days.]
lromor[m] has quit [Quit: User has been idle for 30+ days.]
hzeller[m] has quit [Quit: User has been idle for 30+ days.]
seraxis has quit [Remote host closed the connection]
seraxis has joined #symbiflow
seraxis has quit [Client Quit]
seraxis has joined #symbiflow
seraxis has joined #symbiflow
<sf-slack1>
<acomodi> litghost/mithro: By looking at the dcp, placement is kinda spread across many clock regions, while the minitest occupies only one + a little portion of the adjacent clock regions
seraxis has quit [Client Quit]
seraxis has joined #symbiflow
<sf-slack1>
<acomodi> I wonder whether it would be worth adding a way to constrain the placer to use a specific area. I have looked through the code and it should be fairly straightforward
<litghost>
acomodi: The placer has a tuning parameter that changes wirelength vs timing strength
<litghost>
acomodi: You could try switch the placer to a heavier wirelength focus, and see what happens
<sf-slack1>
<acomodi> mithro: Yeah, I am trying to get more info there, but it seems to output one path only. The `report_timing_summary` option outputs something that does not include one single timing information (there are a bunch of N/As) and blank tables
<sf-slack1>
<acomodi> @mithro: Yep, the design checkpoint includes that
<mithro>
acomodi: Great, just checking...
<sf-slack1>
<acomodi> mithro: I think that we need to include reports extraction during fasm2bels
<mithro>
hrm
<mithro>
?
<sf-slack1>
<acomodi> I mean, when we generate the bitstream from Vivado through fasm2bels, we need also to output all the possible reports, not only the .dcp, .bit.fasm, and .bit
citypw has quit [Ping timeout: 268 seconds]
<litghost>
I believe we might be missing "create_clocks" on some of the interior clocks
<litghost>
When I wrote the initial fasm2bels tcl, there was only 1 clock, no PLL, etc
Bertl is now known as Bertl_oO
<mithro>
acomodi: So - you need to put the sdc file somewhere