Rom implementation on Quartus

[Niv_Amsalem]

Hi All,

i am working on a project with Stratix 10 Device.

i have tried to implement System Verilog Rom (not as IP) in my design.

the problem is that some ROM's Quartus translate correctly as a RAM and some Not (i saw Register implementation).

my Syn flow it's like that:

Compile & Mapping - Synplify Premier 21.9

Place & Route - Quartus  21.2

can you please look at the code below and understand what is the issue?

Thanks

Niv.

[sstrell]

Looking at a template in the text editor, there is no CS signal used.  Also, why are you using a generate statement and a genvar that you are not using anywhere?

[SyafieqS]

Hi,

Have you tried to use any Quartus template for the ROM?

You may take a look a the template ROM insert template --> sv--> full design --> ram/rom

[SyafieqS]

May I know if there is any update from previous reply? 

As the snippet you posted is different from the Quartus template

[Niv_Amsalem]

Hi,

i suspect that the Synplify Premier in the Mapping stage determine if it's implemented as Registers or not.

so it's under investigation.

i will update once i will have an answer.

Thanks

Niv.

[SyafieqS]

Hello Niv,

Understood. Let me know if there is any other concern or update on this.

[SyafieqS]

As we do not receive any response from you on the previous question/reply/answer that we have provided. Please login to ‘https://supporttickets.intel.com’, view details of the desire request, and post a feed/response within the next 15 days to allow me to continue to support you. After 15 days, this thread will be transitioned to community support. The community users will be able to help you on your follow-up questions.

p/s: If any answer from community or Intel support are helpful, please feel free to mark as solution, give Kudos and rate 10/10 survey

[Niv_Amsalem]

Hi,

i have a question.

when i open Quartus IP of ROM i see that the address must be registered, why is that?

is that a mandatory demand for ROM?

Thanks

Niv.

[FvM]

The keypoint is that block RAM hardware in all Intel FPGA families uses registered addresses. Read data can be optionally registered. Therefore HDL code that shall successfully infer block RAM must register address.

If you look at simple ROM HDL templates, the address register must not necessarily appear as such. If you register the ROM output, e.g. as in your code but without the read enable (cs) function, synthesis converts the data register into an address register.

The cs function in your code however blocks this possibility. You would need a second output register to make your code synthesizable in block RAM. That's due to properties of the FPGA hardware and has nothing to do with tool, e.g. Synplify limitations. Quartus software manual explains the requirements for RAM/ROM inference in detail, just study.