M9K memory block issue in Cyclone IV

I'd observe the signals "cpt" and "Write_ok" in the Simulator (anyway, 
observe them all, so you'll learn what's going on, and what is possibly 
not solved very good in your test module).

From the code, it's not clear, what "cpt" is, and how it has been 
initialzed. If it's not 0 or 1 at start, you'll end up with Trouble 
(e.g. if ist value is -37 or 2). Anyway, ist not quite clear to me what 
this "cpt" is good for...

Thanks you pek for your answer. cpt is integer range 0 to 15 and 
initialized zero, i used it because in the beginning i have a loop of 16 
iterations.
Now, i remove the cpt from my code and I always have the same problem.
You find enclosed a screenshot of my signals.
Best regards

If SignalTap shows signals in red they are (in case of a bus sometimes 
partially, so open it to see more) not available (after synthesis).

So check why those (red marked) signals where synthesized away. Make an 
interpretation of the warnings Quartus issues.

I did not pay attention to red signals thinks.
I have this warning concerning the output but i don't understand:
Warning (14320): Synthesized away node 
"RAM_1Port:RAM1|altsyncram:altsyncram_component|altsyncram_hci1:auto_gen 
erated|q_a[0]".
How can I resolve this warning ?
Best regards

That means as much as "your RAM output is never assigned". In other 
words, your code is erroneous. Time to set up a simulation (the thing 
you do BEFORE synthesis) with all signals displayed...

It's very strange when i assign RAM output to LED(mapped to the leds in 
the board) the warning disappear but when it assigned to a an internal 
signal there is a warning.
Any case i can't exploit the output of this RAM.
I don't know what going with the magafuntions of altera, never work for 
me.
Best regards

jeorges FrenchRivera wrote:
> I don't know what going with the magafuntions of altera, never work for
> me.

I think it's useless to blame the mega function. Start to simulate your 
design and display _ALL_ your signals to learn what happens.

You are right pek,it's unless to blame the mega function.
I simulated as you suggested and it works. But with quartus and using 
the signal tap, i still have Zero in the output of the RAM.
Best regards

You should look out for the warning

> Warning (14284): Synthesized away the following node(s):

And investigate what it says. Even when observing with SignalTap, the 
synthesizer throws unused logic (not having influence on any outputs) 
away. To maintain the function, attach the outputs to any unused output 
pin of the FPGA and observe again.

I don't have the
> Warning (14284): Synthesized away the following node(s): because i connected as 
you suggested the output to the LED in my board, in the same time i can see that 
it works. But, when this output is connected to a global signal, its value is 
always zero.  It's normal ?
Best regards

jeorges FrenchRivera wrote:
> But, when this output is connected to a global signal, its value is
> always zero.  It's normal ?

If the global signal leads to nowhere, the answer is yes. Even a 
"global" signal that does not drive any output has no function and 
therefore may be taken out of the design by optimisation.

The fact that a SignalTap logging is not considered as an "output" and 
the logic is optimized away anyway is a little nuisance but you can deal 
with: As soon as signals either are registered or going through the 
interface of a (sub)-entity you will be able to observe them with 
SignalTap (however, they will be optimized away anyway as soon as you 
switch of SignalTap, as they still have no influence on any output).

thank you very much Pek for your help. Have a good day.
Best regards