• Locked Locked
  • Replies 16 replies
  • Subscribers 56 subscribers
  • Views 1732 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Compiler Problems on Windows 7 64-bit

Mike Wilson
Prodigy 215 points
Other Parts Discussed in Thread: MSP430F2132

Hello!

I am having problems compiling. The compiler reports:

INTERNAL ERROR: C:/Program Files/Texas Instruments/ccsv4/tools/compiler/msp430/bin/cl430 experienced a segmentation fault while
                processing

This is a serious problem.  Please contact Customer
Support with this message and a copy of the input file
and help us to continue to make the tools more robust.

The thing is, that it is not consistent. If I do a "build all", it is almost guaranteed that I will experience at least one file that will not compile. If I then "build", 50% chance the same file will then compile fine. It often takes 3 -4 attempts to build a project before all of the files will compile and then link. I do not seem to be experiencing the linker failing.

I do not have problems compiling the same files on another (much much slower) computer that runs windows XP, 32 bit.

This is tiresome, and it makes me distrust consistency of the compiler.

My setup:

CCS Version: 4.2.0.10017

Compiler:

"C:/Program Files/Texas Instruments/ccsv4/tools/compiler/msp430/bin/cl430"

MSP430 Evaluation C/C++ Compiler        v3.3.0

Compiling for MSP430F2132.

Typical command line as shown in CCSv4:

"C:/Program Files/Texas Instruments/ccsv4/tools/compiler/msp430/bin/cl430" -vmsp -g -O2 --opt_for_speed=0 --cpp_default --gcc --static_template_instantiation --define=DEBUG=ON --include_path="C:/Program Files/Texas Instruments/ccsv4/msp430/include" --include_path="C:/Program Files/Texas Instruments/ccsv4/tools/compiler/msp430/include" --verbose_diagnostics --diag_warning=225 --display_error_number --diag_suppress=238 --issue_remarks --code_model=small --data_model=small --small_enum --plain_char=signed --optimize_with_debug --single_inline --remove_hooks_when_inlining --std_lib_func_not_defined --preproc_with_compile --preproc_dependency="SMBSmaster.pp"  "../SMBSmaster.c"

Computer:

Windows 7 Professional

AMD Phenom II X4 955 3.2Ghz

4.00GB memory

64-bit operating system

 

Any suggestions? Do you need more information?

 

Thanks a bunch!

Mike

  • TI__Guru**** 249680 points

    An upgrade to to compiler v3.3.1 may help.  I'll get some other folks to look at this one.

    Thanks and regards,

    -George

  • TI__Expert 6550 points

    I have another internal report of shell crashes on 64-bit Windows 7.  We will attempt to reproduce that issue and determine the cause.  Does the crash pop up an error dialog?  If so, does that dialog contain any additional information?  I have logged this into our defect tracking database as issue SDSCM00038677.

  • in reply to ThomasS
    Prodigy 215 points

    I have seen a pop up an error only 2 or 3 times in the last 2 months, and do not remember the circumstances, it has been several weeks since I saw a pop up, that may have even been an earlier version that I saw that in.

    Thanks for looking into this! Please let me know if there is anything I can test for you.

    I'll look into v3.3.1 in the meantime.

  • in reply to Mike Wilson
    Prodigy 215 points

    OK, I updated to v3.3.2, didn't realize I wasn't using the latest. Well, anyway, the same problem exists with 3.3.2.

    Here is my result:

    'Building file: ../FuelGauge.c'

    'Invoking: Compiler'

    "C:/Program Files/Texas Instruments/ccsv4/tools/compiler/MSP430 Code Generation Tools 3.3.2/bin/cl430" -vmsp -g -O2 --opt_for_speed=0 --cpp_default --gcc --static_template_instantiation --define=DEBUG=ON --include_path="C:/Program Files/Texas Instruments/ccsv4/msp430/include" --include_path="C:/Program Files/Texas Instruments/ccsv4/tools/compiler/MSP430 Code Generation Tools 3.3.2/include" --verbose_diagnostics --diag_warning=225 --display_error_number --diag_suppress=238 --issue_remarks --code_model=small --data_model=small --small_enum --plain_char=signed --optimize_with_debug --single_inline --remove_hooks_when_inlining --std_lib_func_not_defined --preproc_with_compile --preproc_dependency="FuelGauge.pp" "../FuelGauge.c"

    INTERNAL ERROR: C:/Program Files/Texas Instruments/ccsv4/tools/compiler/MSP430 Code Generation Tools 3.3.2/bin/cl430 experienced a segmentation fault while

    processing

    This is a serious problem. Please contact Customer

    Support with this message and a copy of the input file

    and help us to continue to make the tools more robust.

    gmake: *** [FuelGauge.obj] Error 2

     

    The very next time I compiled it, it compiled just fine.

    Thanks!

    Mike

  • in reply to Mike Wilson
    TI__Expert 6550 points

    The shell crash may occur with the evaluation version of the shell.  The non-evaluation tools should not have these crashes.  The next release of the tools, 3.3.3 scheduled for late January, will have this fixed.

  • in reply to George Mock
    Prodigy 80 points

    I have the same problem, often traps 3 or 4 times in a row.  I have the latest CCS4 installed with 3.3.1 compiler.

    OS is Win7 (x64) on a i7 CPU with 4GB ram

    Simon

  • in reply to Simon Peacock
    TI__Guru**** 249680 points

    Have you tried upgrading the compiler to v3.3.3?

    -George

  • in reply to George Mock
    Prodigy 215 points

    I tried to update through CCS, and it found no updates. I couldn't find another way to update. Any ideas?

  • in reply to George Mock
    Prodigy 80 points

    according to the download, I have the latest tools.. so how do I get 3.3.3?

  • in reply to Simon Peacock
    TI__Guru**** 162305 points

    Simon,

    It looks like the 3.3.3 release is completed, however it may not be live on the update site yet.  I will check.

    Regards,

    John

  • in reply to JohnS
    TI__Guru**** 162305 points

    Simon,

    I have confirmed that the 3.3.3 release is on Update Manager.  However depending on what compiler release you have installed today it may not show up when you do the default update check.  If you have X.Y.Z installed the automatic update check will only show the Z updates.  If instead you select the option to search for new features it will find the X and Y updates as well.

    Regards,

    John

     

  • in reply to JohnS
    Prodigy 80 points

    sorry.. but it doesn't upgrade, there is nothing to select . I have 3.3.1 and nothing appears either as automatic update or search for update

  • in reply to Simon Peacock
    TI__Guru**** 162305 points

    Simon I will send you a private message with a download link

  • in reply to JohnS
    Prodigy 215 points

    I would appreciate a link as well, I posted my same issue in the CCS support forum, and the response was "that's weird".

    Thanks,

     

    Mike

    mnwdesign.com

  • in reply to Mike Wilson
    Intellectual 595 points

    Yeah.... so where is the link? 

    I seem to be having the same problem.  CCS tells me I am using Code Generations 3.3.3 (and gives me options that only 3.3.3 understands), yet I am really using 3.2.2.

    To top that off it will not let me install any updates through Eclipse.

     

    Why does anybody use Eclipse anymore?

  • in reply to Tim C.
    TI__Guru**** 162305 points

    We can't post the link on this thread but I will send you a private message with the link.