Cyclone 3 - device has 66 M9K blocks. I set up 16384x36 memory chunk. It is 589824 bits, with device having 608256 bits. However quartus says it is too much, and says device needs to have 72 blocks to fit memory I need. What's an issue? Thank you for tips.

The issue will be the way you are using the ram, and you're not using it in an efficient way, so some on board ram is wasted.

Waisted? I try to use it the best way - as a single contiguous chunk. At leat it is my current understanding. Any suggestion other than stating that I do _something_ wrong?

It should be possible to build that memory using 64 M9K blocks and some logic elements as well. This memory will be spread across the entire chip so do you really need such a large memory? Are you sure that memory is the only one in your design? If you include IP or large lookup tables they could also be consuming on-chip memory resources.

--- Quote Start --- It should be possible to build that memory using 64 M9K blocks and some logic elements as well. This memory will be spread across the entire chip so do you really need such a large memory? Are you sure that memory is the only one in your design? If you include IP or large lookup tables they could also be consuming on-chip memory resources. --- Quote End --- This is what I am curious about. I planned to have 64 blocks, but it wants 72. error (170048): selected device has 66 ram location(s) of type m9k. however, the current design needs more than 66 to successfully fit After splitting to two memories 16K words each * 18 bits, it still wants 72 blocks scope_mem:buffer0_ram|altsyncram:altsyncram_component|altsyncram_pho1:auto_generated|ALTSYNCRAM AUTO Simple Dual Port Dual Clocks 16384 18 16384 18 yes no yes no 294912 16384 18 16384 18 294912 36 None Unassigned 1 scope_mem:buffer1_ram|altsyncram:altsyncram_component|altsyncram_pho1:auto_generated|ALTSYNCRAM AUTO Simple Dual Port Dual Clocks 16384 18 16384 18 yes no yes no 294912 16384 18 16384 18 294912 36 None Unassigned 2 And yes, I need large buffer, spanning through whole internal memory. edit: just notices i use dual-port memory model. does it change anything while size of the memory remains the same?

It depends on the dual-port mode you are using - see pages 43-46. http://www.altera.com/literature/hb/cyc3/cyclone3_handbook.pdf Based on the error message, I'd guess you were trying to use true dual-port mode. Cheers, Dave

Why it wants mofr M9K blocks | Altera Community

13 Replies

Altera_Forum
Honored Contributor
12 years ago
--- Quote Start ---
Wizard says block type "auto" and max block depth "auto". Resource really says 72 M9K.
I have played with number of words. Choosing 1024 gives 4 M9Ks, but choosing 2048 (twice more) gives 9 (nine!) M9Ks!
I also played with bus width and it seems to me that 9th bit of the M9Ks is being lost in my setup. When I set bus width to 32 bits, it properly displays 64 M9Ks.
--- Quote End ---

if you set width to 36, depth to 16384, block depth to 1024 or less you should get 64 M9Ks plus extra logic. Is that what you mean?
Altera_Forum
Honored Contributor
12 years ago
and the explanation (as far as I know) is that the parity bit is available across 1024 locations (or spread across as 2*512,4*256). any depth > 1024 loses it. This parity bit itself is not used as parity in the first place! as far as I know.
Altera_Forum
Honored Contributor
12 years ago
--- Quote Start ---
and the explanation (as far as I know) is that the parity bit is available across 1024 locations (or spread across as 2*512,4*256). any depth > 1024 loses it. This parity bit itself is not used as parity in the first place! as far as I know.
--- Quote End ---

Oh thank you so much - it worked!

Forum Discussion

Why it wants mofr M9K blocks

13 Replies

Recent Discussions

Avalon-ST configuration with Agilex 3 fails

Cyclone IV E – PLL Power Track Width Recommendation Clarification

Operating temperature for 10M08DCF256A7G

System PLL of Agliex5 PCIE example design cannot be locked after configuration

Download links not working