• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 31 subscribers
  • Views 1552 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Unable to program my Launchpad Stellaris ek-lm4f120xl in linux

Jazmin Antonio
Prodigy 10 points

Hi, I'm pretty new to Linux I have been using Ubuntu 12.10 for 1 week so far I've tried 3 different ways to program my Stellaris Launchpad that I just bought but I have not had success,I am using the guide at http://processors.wiki.ti.com/index.php/Stellaris_Launchpad_with_OpenOCD_and_Linux I get stuck when trying to install OpenOCD, I get an error after typing ./configure –enable-maintainer-mode –enable-ti-icdi

I get this:

jazmin@familia:~/openocd$ ./configure –enable-maintainer-mode –enable-ti-icdi configure: WARNING: you should use --build, --host, --target configure: WARNING: invalid host type: –enable-maintainer-mode configure: WARNING: you should use --build, --host, --target configure: WARNING: invalid host type: –enable-ti-icdi checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for –enable-maintainer-mode-gcc... no checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking for gcc option to accept ISO C99... -std=gnu99 checking whether gcc -std=gnu99 and cc understand -c and -o together... yes checking for –enable-maintainer-mode-ranlib... no checking for ranlib... ranlib checking build system type... Invalid configuration `–enable-maintainer-mode': machine `–enable-maintainer' not recognized configure: error: /bin/sh ./config.sub –enable-maintainer-mode failed jazmin@familia:~/openocd$


Please help me, I don't want to go back to Windows haha

  • 0
    Guru 11940 points

    Sorry, but this forum might not be the right place for your question. The problem you describe happens obviously while trying to build the openocd software.  An openocd related forum would give a better chance for a helpful answer.

    While staying with Linux, you can try Code Composer Studio, look there: http://processors.wiki.ti.com/index.php/Linux_Host_Support

    I'm using Crossworks under Linux for the Launchpad. Both (Crossworks and CCS) have the advantage of supporting the 'native' debug adapter out of the box, so no need to spend hours or days to get another one running.

  • 0
    Intellectual 865 points

    Why not try from the terminal:

    sudo apt-get install openocd

    I also tried building it from source but I failed at the configure stage just like you :-)

    I'm successfully using OpenOCD and Ubuntu 10.04.

  • 0 in reply to Lubomir Bogdanov1
    Guru 26105 points

    Hi,

    Did you run ./bootstrap first? Was it run without errors?

    Petrei

  • 0 in reply to Petrei
    Guru 11940 points

    I had not been checking openocd for long time, and was surprised to see it supports a lot of debug adapters, including ICDI and the embedded STLink. So I gave it a try, too.Installing the binary with apt-get worked, but resulted in an older version (0.5.0).

    So I fetched the sources, and built it. That worked almost out of the box for me. In difference to you, I downloaded the project archive from sourceforge, not using a GIT checkout. The openocd project page states in regard to you issue:

    Maintainer Mode

    After a fresh checkout, bootstrap, and a simple configure, you may experience errors when running make that some files cannot be found (e.g. version.texi), and a second make will "mysteriously" solve the problems. The isssue is well-known and expected, if unfortunate.

    The OpenOCD project requires that all developers building from the git repository use the --enable-maintainer-mode option when running the configure script. This option ensures that certain files are created during the build process that would normally be packaged in the distribution tarball. The bootstrap script will remind you of this requirement when it runs.

    In addition to solving these problems, this option enables Makefile rules (provided by automake) that allow the normal make process to rebuild the autotools outputs, included the automake-generated Makefiles themselves. This avoids the heavy-handed approach of running the bootstrap script after changing one of these files.

    I hope this helps.

  • 0
    Prodigy 40 points

    The same thing just happened to me.  The fix was to to put two dashes in front of each option.  The line from the instructions was:

    ./configure -enable-maintainer-mode -enable-ti-icdi

    It should have been:

    ./configure --enable-maintainer-mode --enable-ti-icdi

  • 0 in reply to Chris Rhodin
    Guru 11940 points

    For linux commands, long options generally start with two dashes. As an example, the ls command knows the equivalent options '-a' and '--all'.

    And second, configure scripts are 'plain' text, so it's suggested to read and check it for possibly required options before starting, or at least after errors.