News for hackers. Stuff that matters.
Re:GRVI Phalanx joins The Kilocore Club by nickpsecurity on Friday January 20, 2017 @11:18PM (#13448754)
Can't the tools do it relatively fast with a geometric method if the individual cores already have area/timing data to use and are homogenous? And a FPGA instead of an ASIC?

My reading the various papers on synthesis as a non-hardware guy made me think this job shouldn't be as hard on that as the SOC's whose components vary considerably in individual attributes.

Re:GRVI Phalanx joins The Kilocore Club by jsgray on Saturday January 21, 2017 @08:45AM (#13450001)
I wish it were so. While it is straightforward to do regular placement at the block level or even at the individual LUT/slice level using RPMs (relationally placed macros) or absolute LOC placement of LUTs in the XDC implementation constraints file, most of the implementation time goes into routing and there is not an easy mainstream way to take a routed one tile design and step and repeat it (say) 210 times across the die. In part this is due to non homogeneity across the columns and sometimes rows of the chip.
Re:GRVI Phalanx joins The Kilocore Club by nickpsecurity on Saturday January 21, 2017 @10:28AM (#13450428)
That makes sense. Thanks.
Re:GRVI Phalanx joins The Kilocore Club by jackyinger on Friday January 20, 2017 @11:22PM (#13448771)
If you floor plan it yourself you can make the tool's job a lot easier. You can create a grid of regions on the FPGA and assign a core to each.