Help-about peripheral IP design

the resulting frequency at the output of your dac depends upon the speed you feed the dac with new values. the faster the cpu is and or its clock, the faster the while (1) loop will be executed the faster the dac gets its next value, hence the output frequency will increase.

but you will also get jitter, if the cpu is executing some kind of interupt and during that time cannot feed the dac with new values.

if you want to get rid of jitter and cpu dependencies. you should use hardware instead of software to feed your dac to provide a stable and well known updating frequency of your dac data.

Thank you for suggestion!

I got your meaning.But I still confused that how to set the cpu clock can I get the right 40KHz signal,I think the cpu running at uncertain rate.Select the standard the result is 23KHz,as the fast is 37KHz,I also set the cpu as fast and clock as 40MHz,the result is 43KHz.So I got a big confusion.

Have you ever design the parallel DAC as a IP?I appreciate your great help.

I feel a little down having done it for a long time.

a software based solution will never be as accurate as a hardware based solution.

there a several possible solutions for this

you dac ip can act as a master, so the nios cpu will programm this ip via its slave ports and setup memory adr of the first value and the number of values. after this you enable the master via one control bit. the master port of your dac will read value after value from the memory location without getting "help" from the cpu. a simple FSM will obey the required DAC clock and store the last read value (by your master) into your dac and start the next read from the memory.

in that case, when the cpu has started this functionality, the cpu does not have anything left to do.

or you place all the values into onchip memory inside your ip module, and when done you ip will read out value by value and feed your dac with it, assuming you have enough onchip memory availble

Thank you very much!

I do it as you said ,I save the signal during the DAC IP(by NCO).

--- Quote Start ---

you place all the values into onchip memory inside your ip module, and when done you ip will read out value by value and feed your dac with it, assuming you have enough onchip memory availble/QUOTE],and I got the right answer.

Though I set the ports like read,write,readdata,writedata,I didn't use them at all.That means the whole process have nothing business with cpu.

So I'm still a little confused.what's function of cpu during the transmiton?

Besides,I couldn't understand that the avalon bus have read,write, how long does the reading and writing take?

Best regards!

well, without more knowledge how your design is done between nios cpu and your dac i can't give you precise hints.

the avalon bus is similar to lets compare it with a telephone switching center, where masters (like nios cpu or DMA) cann call slaves (like memory or ip registers).

some customer ips can have master and slave ports. a master like the nios cpu tells the customer ip via its slave ports that the next couple of data is stored under slave memory location 0xsomething and enables this ip functionality to fetch via its master ports the data without the help of some other master funtionality.

such read and writes can be as fast a 1 clock cycle, but could also be longer depending upon waitstates a slave can assert if this slave is slower, or if the slaves is occupied by another master, in last case the calling master must wait until the currently accessing master is finished.

I see.Thank you for your kindness.

--- Quote Start ---

some customer ips can have master and slave ports. a master like the nios cpu tells the customer ip via its slave ports that the next couple of data is stored under slave memory location 0xsomething and enables this ip functionality to fetch via its master ports the data without the help of some other master funtionality.

--- Quote End ---

Now if I want to design a AD IP,then it must have input ports and output ports.I'm not sure that whether the input data go into the fifo,and then fifo send the data to avalon bus,at last avalon bus write the data to AD IP register.It seems complex.

Besides,I occure another problem.I made a memory initialization(use Tightly-Coupled Memory).I want to get data from the on-chip-memory to dataout ports.But it doesn't work.(in the attachment)

during Nios IDE,I do like this

volatile int i;

volatile int *data_tcm_memory_ptr;

data_tcm_memory_ptr = (alt_u32*) (0x00000000);//on-chip-memory base

while(1)

{

for(i=0;i<=24;i++)

IOWR_ALTERA_AVALON_PIO_DATA(DATAOUT_BASE,(alt_u32*)(data_tcm_memory_ptr+i));

}

Best regards!

--- Quote Start ---

how about:

for(i=0;i<=24;i++)
    IOWR_ALTERA_AVALON_PIO_DATA(DATAOUT_BASE,*(alt_u32* )(data_tcm_memory_ptr+i));

--- Quote End ---

Yeah,I got it.

I do it as you said and get the result ,but the ouput has harmonic wave and a little jitter.

So I think through on-chip-memory(data saved in it) can enhance the speed ,but can not get the exact answer.When the nios do high-speed signal processing ,I'm not sure it can get the right answer .

And ,I guess that the whole transmission is like this: when I put initial data in on-chip-memory,the avalon bus read the data and then write the data to output.Maybe my idea is wrong.Could you give me a suggestion how does the avalon bus work?

To remove jitter you'll need to ensure that the instructions take the same time each time thay are exectuted.

The dynamic branch prediction will scupper this.

As will any contention on the Avalon MM slave device.

(Even assuming there are no cacahe delays.)

You also need to check the assembler generated by the compiler to ensure the first loop iteration isn't coded separately.

--- Quote Start ---

To remove jitter you'll need to ensure that the instructions take the same time each time thay are exectuted.

The dynamic branch prediction will scupper this.

As will any contention on the Avalon MM slave device.

(Even assuming there are no cacahe delays.)

You also need to check the assembler generated by the compiler to ensure the first loop iteration isn't coded separately.

--- Quote End ---

Thanks a lot!

I can not understant totally.I don't know about the dynamic branch prediction.

And you said checking the assembler generated by the complier to ensure the first loop iteration isn't coded separately. During my design there only have one peripheral,I don't understand the first loop iteration's meaning.

Best regards!