On Wed, May 21, 2014 at 4:25 PM, yann orlarey wrote:
> rdtable has three input signals. The first one must be contant and known at
> compile time, it define the size of the table, The second input signal
> defines the content of the table and must be also known at compile time. And
> the third sig
rdtable has three input signals. The first one must be contant and known at
compile time, it define the size of the table, The second input signal
defines the content of the table and must be also known at compile time.
And the third signal is the read index and it must generate values in the
limit
On Tue, May 13, 2014 at 9:02 PM, Orlarey Yann wrote:
> Hi Stephen,
>
> The third input signal of rdtable is the read index. In your case it should
> be an integer signal with values in the interval [0..2047]. But in your
> example cnt will generate reads outside the boundaries of the table causing
Hi Stephen,
The third input signal of rdtable is the read index. In your case it should be
an integer
signal with values in the interval [0..2047]. But in your example cnt will
generate reads
outside the boundaries of the table causing segfaults. In other words you
should use a
phasor as rea
Hello,
I've been struggling a bit with the semantics of rdtable(). I'm using
the plot.cpp architecture for testing my functions, and piping the
data into python/matplotlib for visualization. I'm not sure if I've
encountered a bug or if it is my misunderstanding of how rdtable()
works.
Trying to
