Custom Components

I good rule of the thumb with sopc builder when you make a change to any component you created is to remove it and then add it back in.

Cheers

Rob

Dear Rob,

Is it enough to remove the component and then re-add it, or do I need to go into the component editor and remove the VHDL and re-add it in again ?

Shmuel

--- Quote Start ---

originally posted by rmorley78@Mar 13 2006, 04:27 PM

i good rule of the thumb with sopc builder when you make a change to any component you created is to remove it and then add it back in.

cheers

rob

<div align='right'><{post_snapback}> (index.php?act=findpost&pid=13371)

--- quote end ---

--- Quote End ---

Bad choice! I think.

For example, I have designed my avalon component consists from 3 modules.

Top module has 1 slave and 2 masters. This means that I have to

reassign all signals. It is so nervious work, because SOPC works so slowly.

I may recommend, firstly, just replace modules has changed by you.

When you replaced files, secondly, you should regenerate your design.

This method saves your time and nerves.

Dear Slava,

Sorry I didn&#39;t understand your recommendation. Please could you explain again

Shmuel

--- Quote Start ---

originally posted by shmueld@Mar 13 2006, 04:50 PM

dear slava,

sorry i didn&#39;t understand your recommendation. please could you explain again

shmuel

<div align='right'><{post_snapback}> (index.php?act=findpost&pid=13375)

--- quote end ---

--- Quote End ---

Step by step:

1) We are making some modules in HDL.

2) Adding to SOPC builder and assigning all signals - CHIPSELECT,WRITE and etc

3) Adding software files is option

4) Now we have added our component and we can add it to design in SOPC builder

5) If we have changed any modules in HDL or in software we can just replace HDL files and software files in directory of our generated component

6) When files have replaced you should regenerate your design in SOPC builder

That is all.

5) If we have changed any modules in HDL or in software we can just replace HDL files and software files in directory of our generated component

That is all.

<div align='right'><{post_snapback}> (index.php?act=findpost&pid=13377)</div>

--- Quote End ---

This last step is what I am interested in! Once you change the VHDL code don&#39;t you atleast have to recompile the design ? I would have thought you would also need to regenerated the the system ? If not why ?

Shmuel

--- Quote Start ---

originally posted by shmueld@Mar 13 2006, 05:04 PM

this last step is what i am interested in! once you change the vhdl code don&#39;t you atleast have to recompile the design ? i would have thought you would also need to regenerated the the system ? if not why ?

shmuel

<div align='right'><{post_snapback}> (index.php?act=findpost&pid=13378)

--- quote end ---

--- Quote End ---

I have added step 6 :-)

BUT!

As you can see,SOPC builder generates some files in your quartus project directory and there are your HDL files these files would copied from component directory.

So, you can also replaced files in your quartus project directory.

:-)

But, I think that is not good choice for save time :-)

And I am using step 6.

--- Quote Start ---

originally posted by slava+mar 13 2006, 12:22 pm--><div class='quotetop'>quote (slava @ mar 13 2006, 12:22 pm)</div>

--- quote start ---

<!--quotebegin-shmueld@Mar 13 2006, 05:04 PM

this last step is what i am interested in! once you change the vhdl code don&#39;t you atleast have to recompile the design ? i would have thought you would also need to regenerated the the system ? if not why ?

shmuel

<div align='right'><{post_snapback}> (index.php?act=findpost&pid=13378)

--- quote end ---

--- Quote End ---

I have added step 6 :-)

BUT!

As you can see,SOPC builder generates some files in your quartus project directory and there are your HDL files these files would copied from component directory.

So, you can also replaced files in your quartus project directory.

:-)

But, I think that is not good choice for save time :-)

And I am using step 6.

<div align='right'><{post_snapback}> (index.php?act=findpost&pid=13380)</div>

[/b]

--- Quote End ---

While developing a component, you can safely copy the altered design files into the design directory, overwriting the old version. Then, you only have to recompile your design, without going through the SOPC builder. This is a tremendous time saver. After component development has finished, copy the updated files into the /hdl directory in the component tree, and regenerate.

Only if you change the interface you have to remove the component from SOPC builder and add it again.

I&#39;m using this practice extensively, and no problems so far.

Avishay

While developing a component, you can safely copy the altered design files into the design directory, overwriting the old version. Then, you only have to recompile your design, without going through the SOPC builder. This is a tremendous time saver. After component development has finished, copy the updated files into the /hdl directory in the component tree, and regenerate.

Only if you change the interface you have to remove the component from SOPC builder and add it again.

I&#39;m using this practice extensively, and no problems so far.

Avishay

Dear Avishay,

Thanks for your reply. When you stated "you only have to recompile your design" are you referring to compiling the VHDL code only or the system as a whole at the upper level ? The reason Why I am asking is I tried a couple of times changing my original vhdl code that I had added to my custom coponent (even compilign it) and then compiled the system as a whole at the upper level. I found that my updated version of VHDL code was over written by the old version. I tried different things. I removed the component within SOPC Builder and re-instantiated, I even openned and closed the component editor without making any changes to the component. All with the same result. The only way I manage to incorporate the new VHDL code into the component was to go into the component editor in SOPC Builder and delete the VHDL code that was associated with the custom component and re-add the code to the component. This is very time consuming especially with generation and compilation of the upper design - is there a faster method ?