M20K block related build error

[Altera_Forum]

I try to build the opencl code.  

The memory blocks in estimated resource usage summary is 35%. But there is a error message as below: Error (170048): Selected device has 2713 RAM location(s) of type M20K block. However, the current design needs more than 2713 to successfully fit   How come the memory blocks usage does not exceed 100%, but it still has RAM prolbem related error? how to avoid the kind of error? any suggestion?   +--------------------------------------------------------------------+ ; Estimated Resource Usage Summary ; +----------------------------------------+---------------------------+ ; Resource + Usage ; +----------------------------------------+---------------------------+ ; Logic utilization ; 26% ; ; ALUTs ; 14% ; ; Dedicated logic registers ; 12% ; ; Memory blocks ; 35% ; ; DSP blocks ; 1% ; +----------------------------------------+---------------------------;   Error (170048): Selected device has 2713 RAM location(s) of type M20K block. However, the current design needs more than 2713 to successfully fit   Thanks

[Altera_Forum]

Hi mattsai, 

 No sure which Quartus version you are using. I think you need to check at the latest Quartus version Fitter Resource Usage Summary report to know the numbers of M20K RAM that is being use. The attached screen shot shows the numbers of M9K RAM utilization.  Regards, nyusof (This message was posted on behalf of Intel Corporation)

[Altera_Forum]

Hi, 

 FPGAs have different types of SRAM blocks in them , for example, M512, M4K, M-RAM, MLAB, M9K, M144K, M10K, M20K. The density of these types of RAM vary from FPGA to FPGA and are used by the tool to fit in various types of memories that are required for the design.   If the tool complains that the current device selected does not have enough resources of a particular type of MRAM, you have a couple of options:  1. Look up the FPGA selector guidelines and find out an FPGA alternative that meets/exceeds the required amount of stated MRAM. 2. Modify your design so as to use all/different type of MRAMs so that the MRAM usage is distributed among the available types.  3. Look up the tool settings for MRAM implementation and force the tool to use other types if it cannot meet the required type.