Forum Discussion

Altera_Forum's avatar
Altera_Forum
Icon for Honored Contributor rankHonored Contributor
20 years ago

Custom kits

Hi all,

suppose that I developed a set of SOPC Builder components and software, and I want to distribute them together with examples and documentation.

I feel the best way to do that is to create somehow a sort of additional kit that is made of SOPCBuilder components, software, demos, ...

... In some sense similar to the "Nios-II kit"...

Is it possible?

I started in that direction on NiosII 5.0 beta, adding a "mykit" directory under c:\altera\kits. inside it, I put a "components" directory (with the SOPC Builder components), and an "example" directory. Then I added a .sopc_builder file in c:\altera\kits\mykit as following:

<div class='quotetop'>QUOTE </div>

--- Quote Start ---

kit_id = "mykit";

nios2_ide_project_name = "mykit";

kit_version = "1.0";[/b]

--- Quote End ---

the result is:

- I got Eclipse automatically inserting a dummy project that shows the components under c:\altera\kits\mykit\components

- but I did not get SOPCBuilder automatically find my components. To do that, I have to go in the SOPCBuilder properties and add "c:/altera/kits/mykit/components" to the list of the component directories

Is there a way to let SOPCBuilder automatically find that "mykit" exists, adding automatically the components to the list? I ask that because in the SOPCBuilder Manual, page 4-6, it is written that

<div class='quotetop'>QUOTE </div>

--- Quote Start ---

If a directory is recognized as a kit directory (indicated by the

presence of a file named .sopc_builder), then SOPC Builder further

searches in the components/ subdirectory.[/b]

--- Quote End ---

bye

Paolo

4 Replies

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor

    Paolo,

    You might check the .sopc_builder file that is placed in the user&#39;s home directory. I *think* this is where all the SOPC Builder settings are saved to. If your kit installer can modify this file it should be all that is necessary.

    By the way, your kit idea sounds interesting. Do you have a website where this is discussed? What sort of add-on components are you thinking of? If it is not something that can be publicly discussed right now I understand -- but when the time is right I&#39;d like to see what you&#39;re doing.
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor

    Hi Jesse,

    I just sent you an e-mail about it. I&#39;ll take a look at the user .sopcbuilder file...

    bye

    PJ
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor

    Maybe Microtronix&#39;s linux distribution for Nios II is a good reference for you. And I think the "installer" should do something to implement the idea as Jesse said.

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor

    --- Quote Start ---

    originally posted by mountain8848@Apr 20 2005, 07:48 AM

    maybe microtronix&#39;s linux distribution for nios ii is a good reference for you. and i think the "installer" should do something to implement the idea as jesse said.

    --- Quote End ---

    I agree the installer have to do the real work about modifying files, adding things and so on...

    My concern is not about putting everything spreaded out in the c:\altera\kits\nios2 directory, like the linux distribution currently does, but to create -another- directory under c:\altera\kits that contains everything (for example, I would like to have all the linux distribution under c:\altera\kits\linux\* instead of having it spread out in many places). in that way people will know exactly what is provided by Altera and what is provided by third parties...

    That requires at least the following things:

    - tell Quartus about additional libraries

    - tell SOPCBuilder about additional components

    - tell Eclipse about additional plugins

    These things can be done by now using mostly manual configurations... it would be nice to have the possibility to just put there a directory, and letting the system find out what is in... In practice something like what happens for each component, where the class.ptf tells SOPCBuilder about the existence of a component. Whenever SOPCBuilder finds a class.ptf, it knows what to do with it and what to do with the component that it is implementing...

    bye

    Paolo