Forum Discussion

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

"14736 ERROR: Cannot find sequencer/sequencer.elf" on Lite 16.1 -- how to debug?

Hello,

The EMI megawizard gives the aforementioned error while trying to generate "altera_mem_if_lpddr2_emif".

Using Quartus Prime Lite 16.1 on an unsupported Linux amd64 distribution. Here's the various env settings I have tried: 

wmname LG3D
export PATH=$PATH:/opt/alt/16.1/modelsim_ase/linux:/opt/alt/16.1/quartus/bin
export QSYS_ROOTDIR=/opt/alt/16.1/quartus/sopc_builder/bin
export QUARTUS_ROOTDIR=/opt/alt/16.1/quartus
export SOPC_KIT_NIOS2=/opt/alt/16.1/nios2eds
export TEMP=/tmp
export TMP=/tmp

After trying to tackle this for a few days, I am now out of ideas. Looking for any suggestions how to debug the complex java/Tcl maze and find out what is it that I am missing - a library, an env setting, or something else.

I have the suspicion that the NIOS part of the IP generation is failing, so it could be something with the EDS, but I have no prior experience with EDS at all. The synthesis/fit/programming portions of Quartus behave as expected.

2 Replies

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

    Well, after lots of debugging I finally have Quartus 16.1 run without throwing errors.

    The topic problem of "14736 error: cannot find sequencer/sequencer.elf" seems to be the result of missing GNU "make". This was a fresh Linux installation, so I haven't bothered installing "make" initially. What is worse, Quartus has a copy of GNU make 3.81 in "quartus/linux64/gnu" and I thought it's all set up, but whatever script is invoking "make" is not inheriting the path. :mad: Altera guys reading this could eventually help fixing this for a later release.

    Another problem was a bug in libc6, which I had to workaround manually until the distro catches up:

    https://www.sourceware.org/ml/libc-alpha/2016-12/msg00859.html

    Hope this could be useful to somebody.

    Last but not least - still no clue how to debug the Java/Tcl hotch-potch. Saw a "_dprint" in the Tcl scripts, but that's all.