Hi Andrew, I tried the recent changes to Shared BRAM on ska-sa but I ran into an error during Update Diagram in munge_init.m resulting from commit 2c13dab where it's trying to index div_size which is just a integer. I attach a patch which fixes this issue; however I'm now running into another error during the Design Rules Check:
Problem with block: adc5g_test_slow/hist_0/count_a : The gateway : adc5g_test_slow/hist_0/count_a/adc5g_test_slow_hist_0_count_a_addr is not preceded by a Xilinx converter block as it should be. Where count_a is a Shared BRAM block. If I understand correctly the toolflow uses convert blocks preceding gateway out blocks to determine the port attributes for the top level netlist. Perhaps these were removed for Shared BRAM in the effort to support other data types? Thanks, Rurik On Fri, Jul 19, 2013 at 9:21 AM, Andrew Martens <[email protected]> wrote: > Hey Jason > > >> When I try to set the "Data Binary Point" parameter in the Shared BRAM >> block I get the error: "Illegal parametrization: Binary point Binary point >> must be less than or equal to the number of bits, X." X appears to be the >> index of the Data Width rather than the actual value selected by the Data >> Width parameter. For example if I select 64 bits, X will say 4, 32 bits, X >> is 3, 16bits, X is 2. It seems like and easy bug that I could track down, >> but you black belts can probably figure it out in seconds. If so, can >> someone tell me what the fix is? >> > > We ordinarily use Unsigned with 0 binary point and reinterpret data going in > and out. However, the option is there and should work if needed. It was a > bit of a rabbit hole but the fix is in the current ska-sa repo on github. > The fix should also be backwards compatible but have not done any extensive > testing on this. > > Regards > Andrew > > >
munge_init.patch
Description: Binary data
