CCSV4.2.3.0004 compile problem in MS Vusual studio 2011 installed computer...

Jeongwhan Lee

Other Parts Discussed in Thread: MSP430F247

Hi, there?

I am using CCSv4.2.3.004. Whenever I tried to build current active project, I got a error message(below). I also have installed MS Visual studio 2010 in my computer.

Whenever I got error message, MS Viauls C++ Debug Library error( Debug Assertion Filed! in isctype.c (line 56)) dialog came out.

I am very frustrated with this problem.......

**** Build of configuration Debug for project CompileTest ****

D:\Texas Instruments\ccsv4\utils\gmake\gmake -k all
'Building file: ../Main.c'
'Invoking: Compiler'
"D:/Texas Instruments/ccsv4/tools/compiler/msp430/bin/cl430" -vmsp -g --define=__MSP430F247__ --include_path="D:/Texas Instruments/ccsv4/msp430/include" --include_path="D:/Texas Instruments/ccsv4/tools/compiler/msp430/include" --diag_warning=225 --printf_support=minimal --preproc_with_compile --preproc_dependency="Main.pp" "../Main.c"

INTERNAL ERROR: D:/Texas Instruments/ccsv4/tools/compiler/msp430/bin/cl430 aborted while
processing file ../Main.c

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: *** [Main.obj] Error 2
gmake: Target `all' not remade because of errors.
Build complete for project CompileTest

over 14 years ago

0 AartiG over 14 years ago

TI__Guru**** 173310 points

Which version of the compiler tools are you using? You can check by going into the project Build Properties->CCS Build ->Code Generation tools field under Project settings. Also, is this the Code size limited version of CCS or the full version?

0 Jeongwhan Lee over 14 years ago in reply to AartiG

Prodigy 60 points

Well, in my CCS configuration, Code generation tool TI v3.3.3 and 3.3.2 are installed. Even though I chosse both tools, the same pop-up dialog appears.

I am now using university license version, and I think, it would be a full version.

Well, I am really curious that why microsoft visula c++ debug library program( message with "debug assertion failed") is invoked while compiling MSP430 source code by cl430.exe

thanks in advance.

regards,

p.s: As I found, isctype.c is a c source file from microsoft visual studio (generally located in Program Files\Microsoft Visual Studio xx\VC\crt )

In my opinion, whenever cl430.exe is invoked, there is a conflicts while searching PATH environment...-_-;;

0 AartiG over 14 years ago in reply to Jeongwhan Lee

TI__Guru**** 173310 points

Do you have any non-ascii characters in your source file nams or directory names? We have identified some issues with using non-ascii characters that results in such errors . We have a defect report submitted to investigate this issue, you can check more information on it using the SDOWP link in my signature. Just type in the defect # "SDSCM00037582" in the "Find Record ID" field.

The current workaround is to remove any non-ascii characters in source file or directory names.

0 Jeongwhan Lee over 14 years ago in reply to AartiG

Prodigy 60 points

Oh, I found the problem of using non-ASCII characters in directory path name.^_^;;

Thanks a lot!....

0 chengyuan li over 13 years ago in reply to Jeongwhan Lee

Prodigy 30 points

I have met the same problem,please tell me which directory path did you find? what is the differences between ASCII and non-ASCII? non-english words?

0 George Mock over 13 years ago in reply to chengyuan li

TI__Guru**** 250490 points

chengyuan li said:
what is the differences between ASCII and non-ASCII?

Do an internet search on "ASCII characters" to find lots of links that describe ASCII characters. In this context, it means your directory name can only contain the characters A-Z, a-z, 0-9, and underscores. The space character is usually OK too, though that has caused a few problems in the past. There are a few other punctuation characters that might be OK, but are not worth the trouble. Any other characters should be avoided.

Thanks and regards,

-George