Forum Discussion

AMare2's avatar
AMare2
Icon for New Contributor rankNew Contributor
6 years ago

Compilation of design with Nios fails when adding Signaltap

Hi, I am using Quartus Prime Lite 17.1 and have a design with Nios II e on a Max 10 FPGA. If I add a signaltap file to the design and try to compile I get the following errors: Error (11176): Facto...
AMare2's avatar
AMare2
Icon for New Contributor rankNew Contributor
6 years ago

Thank you for the tips.

I have finally found the problem. It was a non-English character in the folder name of the project! I am not sure why this caused a problem with Signaltap only but by coincidence I noticed that the project including Signaltap would run successfully if I copied the project to another folder so I tried changing the folder name and it worked.

  • RRomano001's avatar
    RRomano001
    Icon for Contributor rankContributor
    6 years ago

    Hi Amare, try compare the xml code on .qsys file, sometimes help you track why fail. this must be responsibility of Altera (now intel) to produce a quality software. Seems they use M$ market strategy to use customer as free beta tester.

    They forgot this is not a PC computer product and cannot be sold uncertified.

    I found some issue coming from these files, I found something general about path are stored as M$ mode absolute path... Bad practice to be avoided.

    About character I think you are on win platform, if so some character like "&" on filename (or dir aka folder name) i learnt in the past can generate catastrofic failure on disk storage too.

    We are here to see if Altera (Now intel) grasp the importance of what was bought or simply leave in it agony to death.

    (Edit: Many of these issue are present from long long time ago and never addressed. Example linux PLL issue appeared 2015)

    Regard.

    Roberto

  • AnandRaj_S_Intel's avatar
    AnandRaj_S_Intel
    Icon for Regular Contributor rankRegular Contributor
    6 years ago

    ​Hi,

    Intel Altera only supports standard alphanumeric characters and underscores (_) in installation paths and project directory.

    Examples of unsupported characters: \/:*?"<>|!£$%^&()

    Regards

    Anand

    • RRomano001's avatar
      RRomano001
      Icon for Contributor rankContributor
      6 years ago

      Hi Anand, a parser to pinpoint wrong path is not so difficult to write, at almost jut test path string. Not forever just when path var is created.

      About catastrophic "&" behavior appear just on windows OS, Unix, Linux too accept also control character on path/file name. It is good taste of user not to do.

      If \ / character are not supported, how can we specify path?? Maybe one of two can be confused with escape sequences, but on path one of this is a standard.

      It is better prevent what can hurt code than leaving untested and not clearly stated

      Regards

      Roberto.