-
Dear Prof @limbo018 , when I doing timing-driven placement with my own case, the OpenTimer seems failed to find net in timer.
 function if I can avoid it.
Particularly not in something networked, that might have its’ own timeout behaviours.
So, I’m going to look at anywhere that is used and se…
-
### Describe the bug
In megaboom v6, the resulting floorplan/macro/std cell placement results in paths that appear to "lap" one of the macros multiple times, which intuitively seems wrong:
![CTS_T…
-
Routability mode usually performs "reverts," where it goes back to a saved snapshot of the placement position of cells. When this happens, the slack weights calculated by the timing-driven mode are no…
gudeh updated
5 months ago
-
### Description
This is the megaboom test-case, in case it is useful...
untar https://drive.google.com/file/d/187o-cj4575guAmgYxNS4v7XYCVtmDcAd/view?usp=sharing
```
./run-me-BoomTile-asap7-bas…
-
### Problem Description
The core RN Animated API affords users the ability to animate arbitrary props. For example, you can animate a square to a circle by animating the `borderRadius` prop.
This …
-
Change from vsync driven to timer driven (like in Mame)
Links to check :
- https://www.reddit.com/r/EmuDev/comments/hgyigv/precision_timing_strategies_in_emulators/
- https://aarongiles.com/mamemem…
-
### Describe the bug
global place is failing with `[ERROR GPL-0303] Use a higher -density or re-floorplan with a larger core area.` after the call to resizer.
Seems like the density should have been…
-
Now that IceStorm has documented the timing for these devices (and in fact can generate a nice static timing report via icetime), would you consider adding timing-driven P&R to arachne? We really nee…
-
VPR is does timing driven packing and routing. Hence it needs to know the timing information.
The iCE40 timing information is already known thanks to project icestorm. We just need to import it int…