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.

Code Red: complete failure to run

Other Parts Discussed in Thread: LM3S8962I just installed Code Red from the CD that came with my EKT-LM3S8962 board. After I first ran Code Red, it asked if I wanted to upgrade. I said yes, and it upgraded me to 2009-09-24 (2.0.18).

Continuing the install process in Quickstart-Eval-Kit-CodeRed.pdf, I then requested, received and installed a timebombed license. Finally, I imported the Stellarisware stuff, but nothing compiles. Instead, the compiler binary dies on execution. Here's what happens when I try to build Hello:

**** Build of configuration Debug for project hello ****

make all
Building file: ../hello.c
Invoking: MCU C Compiler
arm-none-eabi-gcc -DDEBUG -D__CODE_RED -Dcodered -DPART_LM3S8962 -I"C:Documents and SettingsiceMy Documentsred_suiteworkspace" -I.. -O2 -g3 -Wall -c -fmessage-length=0 -fno-builtin -ffunction-sections -mcpu=cortex-m3 -mthumb -MMD -MP -MF"hello.d" -MT"hello.d" -o"hello.o" "../hello.c"

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
make: *** [hello.o] Error 3

Any ideas?
  • What version of StellarisWare did you import? Have you downloaded the latest version from the software update site (http://www.luminarymicro.com/products/software_updates.html) and tried the import with the latest version of StellarisWare?

    --Bobby
  • The latest and greatest StellarisWare, SW-LM3S-5228.EXE.

    But I am pretty certain it's a problem with the Code Red compiler, not with Stellarisware; this is what happens if I try to compile from inside cmd.exe:

    C:> code_redred_suiteToolsbinarm-none-eabi-gcc.exe hello.c

    This application has requested the Runtime to terminate it in an unusual way.
    Please contact the application's support team for more information.

    I looked at the arm-none-eabi-gcc.exe binary with Dependency Walker (dependencywalker.com) and it's complaining it can't find two delay-load dependency modules (ieshims.dll and wer.dll), but that may be a red herring. Some googling indicates that it may be a VC++ runtime problem, oh joy.
  • To no one's surprise, it turned out to be a Microsoft problem. Specifically, the .NET stuff had gotten wedged something fierce.

    Fix: uninstall all the .NET stuff. I had to use Aaron Stebner's .NET cleanup tool: http://blogs.msdn.com/astebner/pages/8904493.aspx

    Then install .NET 1.1 SP1, reboot, .NET 2.0 SP2, reboot, .NET 3.5 SP1, reboot, let Windows Update do its thing, and reboot some more. Good times.