Dear Casper community,
I seek your wisdom once again. I was doing floorplanning to my model when I noticed something interesting. My model has 40 vector accumulator blocks (simple_bram_vacc). When I opened my model in PlanAhead, I noticed that all the BRAMs of every vacc were sharing the same single counter implementation for addressing, instead of each vacc having its independent counter. I understand that these two implementations are equivalent because all the counters are equivalent and can be replaced by a single one addressing all the BRAMs, but it makes me wonder:
1) Why this substitution happened? Was the Xilinx/EDK tools that tried to do some optimization? Or it has something to do with the simple_bram_vacc block implementation?
2) Isn't this implementation detrimental for routing proposes? I mean a single counter must address 40 different BRAMs across the FPGA. (My critical paths don't involve the counter, but they do involve a lot of vacc BRAMs with other components).
3) What would you recommend me to increase the speed of my model? Force every vacc to implement their own counter (if that's even possible)? Group my BRAMs around or near the lonely counter? Something else?
As always, many thanks, Franco Curotto -- You received this message because you are subscribed to the Google Groups "[email protected]" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected].

