Forum Discussion

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

Altera-SOPC Handling

Hi all,

I am new at the Software, and would be very grateful for some help.

When I try to generate a Code with the SOPC-Generator (Chip : NIOS2, Memory, Jtag-UART) an Error occurs.

LOGFilemessage:

Altera SOPC Builder Version 4.10 Build 181

Copyright © 1999-2004 Altera Corporation. All rights reserved.# 2004.09.24 11:00:59 (*) mk_custom_sdk starting# 2004.09.24 11:00:59 (*) Reading project C:/test/NIOS/templates_microtronix/all_on_chip_32/nios_32.ptf.# 2004.09.24 11:00:59 (*) Finding all CPUs# 2004.09.24 11:00:59 (*) Finding all available components

no install.ptf file found at c:/altera/quartus41/sopc_builder/bin/europa/europa_utils.pm line 1700.

Error in processing. System NOT successfully generated.

tried to reinstall the whole software, but it still doesn't work.

I am using a full license of Quartus2, evalversion of NIOS2 IDE and the StratixDevelopboard A6009 from Microtronix.

Has anyone a clue how I got this thing working?

Thank you very much!!

3 Replies

  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    21 years ago

    hi, the install.ptf file is typically located in:

    c:\documents and settings\<username>\.sopc_builder

    I&#39;ve noticed a similar problem once or twice but it always seems to resolve itself after re-booting the PC. I believe that the problem occurred after installing the USB-blaster driver for the first time.

    You&#39;ll probably have to contact Altera tech support about this because I&#39;m reasonably certain that there isn&#39;t anything in the Stratix Development Kit that would affect the ability to find the install.ptf file.

    If you have a reason to believe otherwise, please let me know.
  • Altera_Forum's avatar
    Altera_Forum
    Icon for Honored Contributor rankHonored Contributor
    21 years ago

    That sounds like the problem I ran into as well. I found out the cause for me was the lack of page space (virtual memory) on my computer. Instead of windows expanding the v-ram the build would just end.

    The system I was using had 384kB of RAM and hardly any page space (was trying to make the system faster keeping more in physical RAM).

    If you have a similar setup try increasing the V-ram that the system uses and that&#39;ll probably fix your problem.

    Good-luck