• Locked Locked
  • Replies 61 replies
  • Subscribers 65 subscribers
  • Views 15014 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.

Compiler crashes on Windows 7

Mateja Putic11728
Intellectual 275 points

Hello all,

I'm using CCSv4.0.0.16000 to develop for the MSP430.  This issue has occurred with previous versions of CCSv4.  From time to time, when I "Build Active Project" or "Rebuild Active Project", I get the following messages:

Then when I click on details I get:

I have pasted the technical information here: http://pastebin.com/m263d40a3

Does anyone have a clue about how to debug this problem?  I have tried uninstalling CCS and reinstalling and I still get the error.  I have not been able to recreate this error deterministically.  It will happen that I build, get the error, then clean and build, with no error.

Any help is appreciated, thank you!

Mateja

  • TI__Guru**** 173310 points

    This error is coming from the compiler. To debug it further, we would need to be able to reproduce the crash first. Could you either attach the necessary files to your Forum Profile or forward it to support@ti.com? We would need the specific source file being built when the crash happens and any header files included by it. Or you could zip up and send the entire project, if its not too large.

  • in reply to AartiG
    Prodigy 165 points

    Hi,

    is there any update on this issue? I am facing the same kind of error with the cl2000.exe, version 5.2.2.

     

    Thanks,

    Malte

  • in reply to Malte Krebs
    TI__Guru**** 427890 points

    Hi Malte,

    Without a reproducible test case, it is very difficult for us to investigate this. Could you provide an example project (the smaller the better) that consistently crashes the compiler? Let me know if you wish to send it to me privately and we can take the conversation private.

    ki

  • in reply to Ki
    Expert 1890 points

    I've had the compiler crash as well.  It is infrequent/erratic but happens maybe every 100-200 compile cycles. I cannot post the example project (among other reasons, I'm using an external makefile which for the moment is really hard to guarantee works right on another computer), if I can reproduce with a test project I will post.

  • in reply to Ki
    Prodigy 165 points

    Hi Ki,

    thank you for your very fast response. I've created a tiny project which causes the compiler to crash on my computer. Please let me know how I can send the project to you.

    Best regards,

    Malte

  • in reply to Malte Krebs
    Guru 17650 points

    Hi Malte,

    you can attach the project to your post (see here for details: http://e2e.ti.com/support/microcontrollers/msp43016-bit_ultra-low_power_mcus/f/165/t/35675.aspx) or you can upload it to 'your files' (from your profile page).

    Rgds
    aBUGSworstnightmare

  • in reply to Joerg Quinten
    Prodigy 165 points

    OK, here it is.

    Just unzip the CL2000_Crash.zip file somewhere and start the compile.bat. It will compile doNothing.c 1000 times. Executing the batch file caused the compiler to crash on my computer every time I've started it -- sometimes sooner, sometimes later.

    Please let me know if I can support you with more stuff.

    Thanks,

    Malte

     

     

     

     

     

    CL2000_Crash.zip
  • in reply to Malte Krebs
    Prodigy 165 points

    What also might be of interest is that this problem only occurs on my PC -- three of my colleagues were able to compile the 1000 times without any crash. So, the problem could be related to some local settings.

    Maybe the attached file is helpful for finding the root cause of the problem (9646_appcompat.txt). This file is the error report which is included in the dialogs with information about the crash.

    Regards,

    Malte

     

  • in reply to Malte Krebs
    Expert 1890 points

    I just got a crash with executable return code -1073741819.

  • in reply to Malte Krebs
    Expert 2040 points

    I do have the same problem on my pc. With CCS3.3 it came perhaps every 100 compile.

    WIth CCS4.0.2 the error appears almost every time, working is not possible.

    I am using CG 5.2.4, but same behaviour with 5.2.2.

     

    For another project I do use the same installation of CG tools (5.2.4) but the build is initiated by a ruby script in eclipse CDT. The error did never appear!

     

    cl2000.exe does produce the 0xc0000005 exception in ntdll.dll

    The return code listed in"console" is: Error -1073741819

     

  • in reply to Roger Périat
    TI__Expert 6550 points

    We have seen similar shell crashes in the past caused by corrupt Microsoft ntdll.dll files.  These were cases where we could not reproduce the crashes when duplicating the project setups.  Debugging the shell in these situations has not shown, yet anyways, any memory problems or leaks in the shell.  The errors are found deep in the Microsoft library code.  These crashes have disappeared when the PC has a clean Window reinstall.  There are many known ways the ntdll.dll file can get corrupt, from viruses to driver updates.  I'm attaching a debug version of the cl2000.exe that you can use.  This may give us additional information on the problem.

    cl2000.zip
  • TI__Expert 6550 points

    See my previous post concerning corrupt ntdll.dll files.  Attached is a debug version of cl430.exe that you can try.  This may give us additional information.

    cl430.zip
  • in reply to ThomasS
    Expert 1890 points

    ThomasS said:
    We have seen similar shell crashes in the past caused by corrupt Microsoft ntdll.dll files.  These were cases where we could not reproduce the crashes when duplicating the project setups.  Debugging the shell in these situations has not shown, yet anyways, any memory problems or leaks in the shell.  The errors are found deep in the Microsoft library code.  These crashes have disappeared when the PC has a clean Window reinstall.  There are many known ways the ntdll.dll file can get corrupt, from viruses to driver updates.  I'm attaching a debug version of the cl2000.exe that you can use.  This may give us additional information on the problem.

    Thanks. It could be a Heisenbug: I've just cleaned & compiled my project (roughly 40 C++ and assembly files) 3 times using the debug version of cl2000 you posted, and have had no crashes. This seems unusually good... perhaps the release version does something different than debug w/r/t memory allocation or something.

     

  • in reply to Jason R Sachs
    Expert 1890 points

    ThomasS said:
    I'm attaching a debug version of the cl2000.exe that you can use.

    For what it's worth, the regular version that causes sporadic crashes is the Evaluation Compiler version 5.2.1 (vs. the debug compiler version 5.2.5P10064)

     

  • in reply to ThomasS
    Expert 2040 points

    ThomasS, thank you for your reply. I did replace my cl2000.exe 5.2.4 by yours, since then (about 50 builds later) the error did not appear.

    For the moment I am trying to reproduce the error, I will notify you if I find something.

    Have a nice day

    Roger

     

  • in reply to Jason R Sachs
    Prodigy 165 points

    Hi,

    unfortunately I also had no crashes in my project using the debug version of the compiler. My original project still crashes.

    Best regards,

    Malte

     

  • in reply to ThomasS
    Prodigy 80 points

    Hi Thomas, with the cl2000 debug version you attached I got no error at all when doing a rebuild (~130 C files). With official 5.2.4 release I typically got ~20 error messages.

    Will this good behaviour be the same when you release v5.2.5? For when the release is planned?

    Thanks and regards, Volker

  • in reply to vzens
    Genius 4026 points

    The same here, the debug version is fine and error free.

    Before, I was not able to do a full build without segmentation failures.

    So is this a corrected version, will it be available in the next cgtools - and what about corrupted ntdll.dll that you mentioned?

  • in reply to StephanS
    Genius 4026 points

    Now I have compared my ntdll.dll to the one of a colleague who can compile without problems.

    They are identical in content.

  • in reply to StephanS
    TI__Guru**** 235955 points

    Please do not think the cl2000 executable that Tom posted is the answer to your problems.  It isn't.  No one knows why it works.  That bothers me.  A lot.  We posted it to see if someone would find something that would lead us to the source of the problem.  That hasn't happened, and I'm increasingly doubtful it ever will.  

    We have only seen one solution to this problem that clearly works: reinstall Windows.  Of course, that's quite painful.  But, at some point, that is better than wondering when the mystery solution you currently use will blow up on you again.

    Thanks and regards,

    -George

     

  • in reply to George Mock
    Prodigy 80 points

    Hi George, understood. But maybe you could give us some hints what you expect us to find (and what would lead you to the source of the problem). Or, to put the ball back into your court, what exactly is the difference between the well working cl2000 from Tom, and the standard one with the many crashes. Best regards, Volker

  • in reply to George Mock
    Genius 4026 points

    Georgem said:

    Please do not think the cl2000 executable that Tom posted is the answer to your problems.  It isn't.  No one knows why it works.  

     

    Okay, agreed. But I think it's a little bit too easy to blame a corrupted dll for this when in fact it is not corrupted.

    Reinstalling Windows is a solution to many problems.

    It helps you easily filling one week's time if you don't know what to do else.

    But (kidding mode off): Nobody tells you that reinstalling windows helps long-term. What if some service-pack, driver or something else causes the problem and it reappears after 3 weeks? So this is no real solution.

    Since no other software has a similar problem (at least not on my PC), I have to rely on TI to fix the tool and find a solution.

    I am willing to help, but a clean install is definitely NO solution.

     

  • in reply to George Mock
    Expert 1890 points

    Georgem said:
    Please do not think the cl2000 executable that Tom posted is the answer to your problems.  It isn't.  No one knows why it works.  That bothers me.  A lot.

    Is it a debug build (vs. a release build)? Some of the differences between debug + release builds in Microsoft VC++ have to do with memory management where the debug build will handle problems fine but the release build will crash, so I'm not surprised if the debug build masks the problem instead of revealing it.

    Is there any way you could make a compiled version of cl2000 that is a release build but which allows (via a --verbose-log switch?) a verbose event log which appends to a file during compilation? Presumably that would help narrow down at what point the crash occurs.

    We have only seen one solution to this problem that clearly works: reinstall Windows.  Of course, that's quite painful.  But, at some point, that is better than wondering when the mystery solution you currently use will blow up on you again.

    I strongly beg to differ. For most of us, the compiler crashes are occasional and we just have to rebuild again. A minor nuisance which is annoying and takes extra time, but tolerable. Reinstalling Windows is a serious disruption that is a last resort that can involve several days of downtime if a lot of programs are installed.

     

  • in reply to George Mock
    Prodigy 165 points

    Georgem,

    re-installing Windows is very painful, indeed. I would take days to re-setup my computer. I think, we need a less painful solution. Have you been in contact with Microsoft? What do they say?

    Do you know which instance of the ntdll is used? When I search for ntdll.dll on my local C: drive, it finds six files called ntdll.dll.

    Have a nice weekend.

    Malte

  • in reply to Jason R Sachs
    Prodigy 165 points

    For most of us, the compiler crashes are occasional and we just have to rebuild again. A minor nuisance which is annoying and takes extra time, but tolerable.

    No, this is definitely not tolerable. In bigger projects (>100 calls of cl2000.exe) the crash occurs at nearly every build cycle (at least on my computer).

    Nobody tells you that reinstalling windows helps long-term. What if some service-pack, driver or something else causes the problem and it reappears after 3 weeks? So this is no real solution.

    In fact, this is true. Btw: my Windows installation is newer compared to the installation of the colleagues that don't see the crash.

    Regards,

    Malte

  • in reply to Malte Krebs
    TI__Guru**** 235955 points

    Whether anyone re-installs Windows is totally up to them.  My goal here is give you the best information we have, so you can make the decision that is best for your situation.  It is going to be different for everyone.  

    That said, no one at TI is pleased with the quality of the information we have about this bug.  We'd like nothing more than to tell you exactly what to do so that this problem never affects you again.  We don't have that information, and the prospects of getting it are dim.  This is a bug, which intermittently occurs in the field, that we cannot reproduce.  The simple fact is we are unlikely to make progress until we can reliably reproduce this bug on a machine where we have full control.  Until then, we just have to hope we get lucky.  Yuck!

    The cl2000 Tom posted is a debug build.  

    Thanks and regards,

    -George

     

  • in reply to George Mock
    Genius 4026 points

    What about Jason R. Sachs' proposal

    Jason R Sachs said:

    Is there any way you could make a compiled version of cl2000 that is a release build but which allows (via a --verbose-log switch?) a verbose event log which appends to a file during compilation? Presumably that would help narrow down at what point the crash occurs.

    This seems to be a good way to try to localize the error since it is obviously not reproducable at TI.

    What about the differences in the working debug version that ThomasS posted? It is really strange that the segmentation fault seems to occur in all cgtools versions since 5.0.0, but not in this debug version.

     

    So I think everybody who has this error at his PC is willing to help. Since it is not reproducable at TI, there must be a different way to solve this.

  • in reply to StephanS
    TI__Expert 6550 points

    This is a good suggestion.  If you are willing to run the crashing shells again, there are some hidden options that will print to stdout the executables the shell is invoking and the options passed to those execuatables.  You can add the --v switch, which which show the command line used in each compilation pass.  There is also the --d switch which will show the contents of the command files.  Also, there is the --f switch which will turn off the shell command files.  So either:

    cl2000 --v --d ...

    or

    cl2000 --v --f ...

    should work.  It would be interesting to know if the crash occurs with the same files, or different files as well as knowing which compiler tool is getting invoked when the crash occurs.

  • in reply to ThomasS
    Expert 2040 points

    built with --v --d

    crash occurred with 5.2.4

    'Building file: D:/project/XXX/match_firmware_trunk_online/match/src/opmode.c'
    'Invoking: C2000 Compiler'
    "C:/Programme/Texas Instruments/C2000CodeGenerationTools5.2.4/bin/cl2000" --v --d --silicon_version=28 -g --include_path="C:/Programme/Texas Instruments/C2000CodeGenerationTools5.2.4/include" --include_path="../../YYYLib1180/includes" --include_path="../../match/includes" --diag_error=225 --sat_reassoc=off --large_memory_model --fp_reassoc=off --preproc_with_compile --preproc_dependency="src_match/opmode.pp" --obj_directory="src_match"  "D:/project/XXX/match_firmware_trunk_online/match/src/opmode.c"
    C:\Programme\Texas Instruments\ccsv4\utils\gmake\gmake: *** [src_match/opmode.obj] Error -1073741819

     

    As you can see, the error occurred at the very beginning of the call of cl2000.exe.

    I did some more investigations.

    The error occurrs always at the beginning of the call (if called with --verbose the error occurrs before any line is logged).

    The error is a read of address 0

    in my ntdll.dll this is at address

    7C921689  mov         ecx,dword ptr [ecx]

    (ecx is 0 )

    My ntdll.dll is loaded at address 0x7c910000

     

    The call stack shown below shows that the last call from cl2000.exe did came from

    cl2000.exe!00440e6b()

    (with visual C++ studio 2003 the call stack shows the address after the call)

    my cl2000.exe has at this point:

    00440E65  call        dword ptr ds:[44D024h]

    which is a call to 7C91FF2D (=offset FF2D) and this is RtlFreeHeap() (Info from dependency walker)

     

    Conclusion:

    I do think that it is at least possible that the error is in cl2000.exe

    Perhaps some not correctly initialized memory

    Perhaps a timing issue (releasing while still accessing)

    The difference of debug / release version could explain both of the possibilities:

      uninitialized memory -> debug versions do often init memory to 0 and / or place some stuffing bytes around arrays

      timing: debug version is not as fast as release version

    Hope this helps

    Roger

    >    ntdll.dll!7c921689()    
         ntdll.dll!7c92a3f5()    
         ntdll.dll!7c921937()    
         ntdll.dll!7c92043e()    
         ntdll.dll!7c920a36()    
         ntdll.dll!7c92084c()    
         ntdll.dll!7c92005d()    
         ntdll.dll!7c9200b8()    
         ntdll.dll!7c920041()    
         ntdll.dll!7c92005d()    
         ntdll.dll!7c92005d()    
         cl2000.exe!00440e6b()    
         cl2000.exe!00408aca()    
         cl2000.exe!00446a85()    
         cl2000.exe!00446240()    
         cl2000.exe!0044627f()    
         cl2000.exe!0044627f()    
         cl2000.exe!004415bf()    
         cl2000.exe!00441178()    
         cl2000.exe!0044118a()    
         cl2000.exe!004411b5()    
         cl2000.exe!0044613d()    
         cl2000.exe!00445059()    
         cl2000.exe!004445be()    
         cl2000.exe!00444876()    
         ntdll.dll!7c921028()    
         ntdll.dll!7c921086()    
         ntdll.dll!7c9201db()    
         ntdll.dll!7c924e91()    
         ntdll.dll!7c925239()    
         ntdll.dll!7c92542b()    
         ntdll.dll!7c925239()    
         ntdll.dll!7c92542b()    
         ntdll.dll!7c920222()    
         ntdll.dll!7c920222()    
         ntdll.dll!7c92019b()    
         ntdll.dll!7c9201db()    
         cl2000.exe!00441570()    
         ntdll.dll!7c925ce9()    
         ntdll.dll!7c925d47()    
         ntdll.dll!7c925239()    
         ntdll.dll!7c92542b()    
         ntdll.dll!7c9257c1()    
         ntdll.dll!7c91d3aa()    
         ntdll.dll!7c9313b2()    
         ntdll.dll!7c920435()    
         cl2000.exe!00440af4()    
         cl2000.exe!0040339b()    
         cl2000.exe!004426b0()    
         cl2000.exe!0040ab16()    
         cl2000.exe!00446a67()    
         cl2000.exe!004418b2()    
         cl2000.exe!00446365()    
         ntdll.dll!7c920460()    
         cl2000.exe!00446677()    
         cl2000.exe!0044672a()    
         cl2000.exe!0044692b()    
         ntdll.dll!7c920323()    
         cl2000.exe!004469cd()    
         cl2000.exe!004415bf()    
         ntdll.dll!7c9132a8()    
         ntdll.dll!7c91327a()    
         cl2000.exe!0044c5b6()    
         ntdll.dll!7c93aa0f()    
         cl2000.exe!0044c5b6()    
         ntdll.dll!7c9200b8()    
         ntdll.dll!7c920041()    
         ntdll.dll!7c92005d()    
         ntdll.dll!7c91e48a()    

  • in reply to Roger Périat
    Genius 4026 points

    Here, it mostly crashes during asm2000, but also during cl2000.

    I am running gnu make 3.81, not the CCS make.

    With --v --d, I get many debug outputs, but none for the crashing file (the file is varying with every make).

    Crashing for C-file:

    /-----------------------------------------------------------------------------\
    | asm2000 COMMAND FILE C

     

    :\DOKUME~1\user\LOKALE~1\Temp\0671213: |
    \-----------------------------------------------------------------------------/
    --"define    =MODULETYPE"
    --"define    =MAINBOARDTYPE"
    --"define    =BOARDTYPE_DEBUG"
    --"define    =MAKE"
    --"include_path    =c:\\ti33\\c2000\\cgtools_5_2_4\\include"
    --"include_path    =e:\\projekte\\DSP\\Code\\aktuell"
    --"object_format    =coff"
    --suppress_asm_extension
    --output_all_syms
    --parser_opts
    17
    --remarks
    --display_error_number
    --no_brief_diagnostics
    --keep_unneeded_types
    --"symdebug    :coff"
    -q
    -DMODULETYPE
    -DMAINBOARDTYPE
    -DBOARDTYPE_DEBUG
    -DMAKE
    -"Ic    :\\ti33\\c2000\\cgtools_5_2_4\\include"
    -"Ie    :\\projekte\\DSP\\Code\\aktuell"
    --"version    =28"
    --"fp_mode    =strict"
    --"mem_model    :code=flat"
    --"mem_model    :data=large"
    --"size_speed_goal    =medium_risk_performance"
    InvCarr.lis
    "e    :\\projekte\\DSP\\GR_LLC\\Code\\aktuell\\OBJ_MODULETYPE_BOARDTYPE_DEBUG\\InvCarr.obj"
    -------------------------------------------------------------------------------

    "c:\ti33\c2000\cgtools_5_2_4\bin\cl2000" IPC.c -v28 --f --d -ss -ealis -ma -mi -mf -ml -q -pdr -pden -pdv --gen_func_subsections -i"c:\ti33\c2000\cgtools_5_2_4\include" -i"e:\projekte\DSP\GR_LLC\Code\aktuell" -dMODULETYPE -dMAINBOARDTYPE -dBOARDTYPE_DEBUG -dMAKE --symdebug:coff -fr"e:\projekte\DSP\Code\aktuell\OBJ_DSP_MODULETYPE_BOARDTYPE_DEBUG" -mn -o2
    make.exe    : *** [e:\projekte\DSP\Code\aktuell\OBJ_DSP_MODULETYPE_BOARDTYPE_DEBUG\IPC.obj] Error -1073741819

    Crashing for asm file:

    "c

    :\\ti33\\c2000\\cgtools_5_2_4\\bin\\asm2000.exe" -"@C:\\DOKUME~1\\user\\LOKALE~1\\Temp\\0729212"
    del "C    :\DOKUME~1\user\LOKALE~1\Temp\0729212"
    c    :\ti33\c2000\cgtools_5_2_4\bin\ar2000 -rq Filt28x.src L_Delay_ROM.asm
    The names of all the prerequisites that are newer than the target L_Delay2.asm    : MakeFile.mke
    c    :\ti33\c2000\cgtools_5_2_4\bin\cl2000 L_Delay2.asm -v28 -q -ml -dMAKE --symdebug:coff --v --d
    gmake[    1]: *** [L_Delay2.obj] Error -1073741819
    gmake[    1]: Leaving directory `E:/Projekte/DSP/Code/Aktuell/Filt28x'
    make.exe    : *** [e:\projekte\DSP\Code\aktuell\Filt28x\Filt28x.lib] Error 2


    So here no real additional infos - it seems to crash before the debug outputs.

  • in reply to StephanS
    Prodigy 165 points

    Stephan,

    it looks like the last program that is called before the crash is the cl2000 in both variants, isn't it?

    Btw: my project crashes with the same error code.

    Does anybody know where the corrupt ntdll.dll is located? As I said earlier, a search on my c drive detected this file six times in different locations.

    Best regards,

    Malte

  • in reply to Malte Krebs
    Genius 4026 points

    Malte, you are right, cl2000 is called in both cases.

    It only happens more often here when calling with an .asm file and less often when calling with a .c file.

    I have 5 different dll locations here:

    C:\WINDOWS\$hf_mig$\KB956572\SP3GDR\ntdll.dll
    C:\WINDOWS\$hf_mig$\KB956572\SP3QFE\ntdll.dll
    C:\WINDOWS\$NtUninstallKB956572$\ntdll.dll
    C:\WINDOWS\system32\dllcache\ntdll.dll
    C:\WINDOWS\system32\ntdll.dll

    I think only the last 2 are relevant. There ntdll is identical (5.1.2600.3520 (xpsp_sp2_qfe.090206-1239)) and - it is identical to the one of a colleague who has no crashes.

    So I think it is not a corrupt ntdll.dll. Maybe some registry entry that affects it. But most probably the compiler...

  • in reply to StephanS
    Prodigy 165 points

    Yes, I agree -- only the last two instances could be relevant. On my computer both files are of version 5.1.2600.5755 (xpsp_sp3_gdr.090206-1234). A colleague who has no crashes has got the same version of the ntdll.

    I would also suspect the compiler. And I totally agree with Roger's assumptions.

    Best regards,

    Malte

  • in reply to Malte Krebs
    TI__Expert 6550 points

    I have found one possible culprit in the shell if the OS were to run out of memory or heap space while invoking the other compiler executables.  See issue SDSCM00035558 at the SDOWP ClearQuest bug tracking site.  Any chance that the systems that have these crashes have less memory, or more processes running, that could affect available heap space versus the machines that don't experience the crashes?  If interested, I may post shells that have the potential fix to see if this is indeed the problem.

  • in reply to ThomasS
    Genius 4026 points

    I am running 3 GB Ram, but have many processes open (Taskmanager lists 56 processes).

    How can I see the actual heap size?

    I would be very interested in cl2000 that has the potential fix.

  • in reply to StephanS
    Expert 2040 points

    My machine has 3 GB RAM. The error occurrs also after a fresh reboot. 48 processes running.

    Roger

  • in reply to ThomasS
    TI__Expert 6550 points

    The shell has some calls to malloc where the return value is not checked.  This bug occurs one location just before the other compiler executables are invoked.  In theory this could be the cause.  I have fixed the memory allocation issues in the attached cl2000.exe and cl430.exe shells.  If this is the cause, you should see crashes with an "out of memory" error.  From here I see 2 paths to take.  If the shells crash with the out of memory error, I'll need to figure out why the shell runs out of heap space.  I'm not currently seeing any memory leaks in the shell.  Or, if they crash with no new error message, I'll dig deeper into the shell.

    ti_alpha_shells_10078.zip
  • in reply to ThomasS
    Genius 4026 points

    Okay, I still got a crash, but no segmentation fault, see attached file

    8168.5c25_appcompat.txt 
    <?xml version="1.0" encoding="UTF-16"?>
<DATABASE>
<EXE NAME="cl2000.exe" FILTER="GRABMI_FILTER_PRIVACY">
    <MATCHING_FILE NAME="abs2000.exe" SIZE="525824" CHECKSUM="0x8AD6E89" BIN_FILE_VERSION="5.2.4.0" BIN_PRODUCT_VERSION="5.2.4.0" PRODUCT_VERSION="v5.2.4" FILE_DESCRIPTION="TMS320C2000 Absolute Lister v5.2.4" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.4" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.4.0" UPTO_BIN_PRODUCT_VERSION="5.2.4.0" LINK_DATE="12/13/2009 15:32:49" UPTO_LINK_DATE="12/13/2009 15:32:49" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="ac2000.exe" SIZE="1360896" CHECKSUM="0x73367649" BIN_FILE_VERSION="5.2.4.0" BIN_PRODUCT_VERSION="5.2.4.0" PRODUCT_VERSION="v5.2.4" FILE_DESCRIPTION="TMS320C2000 C/C++ Parser v5.2.4" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.4" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.4.0" UPTO_BIN_PRODUCT_VERSION="5.2.4.0" LINK_DATE="12/13/2009 15:34:15" UPTO_LINK_DATE="12/13/2009 15:34:15" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="ar2000.exe" SIZE="518656" CHECKSUM="0x9D98FAF9" BIN_FILE_VERSION="5.2.4.0" BIN_PRODUCT_VERSION="5.2.4.0" PRODUCT_VERSION="v5.2.4" FILE_DESCRIPTION="TMS320C2000 Archiver v5.2.4" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.4" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.4.0" UPTO_BIN_PRODUCT_VERSION="5.2.4.0" LINK_DATE="12/13/2009 15:32:39" UPTO_LINK_DATE="12/13/2009 15:32:39" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="asm2000.exe" SIZE="1291776" CHECKSUM="0xD41B85A1" BIN_FILE_VERSION="5.2.4.0" BIN_PRODUCT_VERSION="5.2.4.0" PRODUCT_VERSION="v5.2.4" FILE_DESCRIPTION="TMS320C2000 Assembler v5.2.4" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.4" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.4.0" UPTO_BIN_PRODUCT_VERSION="5.2.4.0" LINK_DATE="12/13/2009 15:43:09" UPTO_LINK_DATE="12/13/2009 15:43:09" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="bti2000.dll" SIZE="118784" CHECKSUM="0xCA366BEB" BIN_FILE_VERSION="2.4.0.19" BIN_PRODUCT_VERSION="3.3.0.0" PRODUCT_VERSION="3, 3, 0, 0" FILE_DESCRIPTION="CCS C2000 BTI Driver" COMPANY_NAME="Texas Instruments Inc." PRODUCT_NAME="Code Composer Studio" FILE_VERSION="2, 4, 0, 19" ORIGINAL_FILENAME="BTI2000.DLL" INTERNAL_NAME="BTI2000.DLL" LEGAL_COPYRIGHT="Copyright © 1994-2006 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="2.4.0.19" UPTO_BIN_PRODUCT_VERSION="3.3.0.0" LINK_DATE="04/27/2009 16:16:51" UPTO_LINK_DATE="04/27/2009 16:16:51" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="cg2000.exe" SIZE="1899008" CHECKSUM="0x4328E40F" BIN_FILE_VERSION="5.2.4.0" BIN_PRODUCT_VERSION="5.2.4.0" PRODUCT_VERSION="v5.2.4" FILE_DESCRIPTION="TMS320C2000 C/C++ Codegen v5.2.4" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.4" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.4.0" UPTO_BIN_PRODUCT_VERSION="5.2.4.0" LINK_DATE="12/13/2009 16:03:28" UPTO_LINK_DATE="12/13/2009 16:03:28" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="cl2000.exe" SIZE="574464" CHECKSUM="0x642E8C57" BIN_FILE_VERSION="5.2.6.0" BIN_PRODUCT_VERSION="5.2.6.0" PRODUCT_VERSION="v5.2.6A10078" FILE_DESCRIPTION="TMS320C2000 C/C++ Compiler v5.2.6A10078" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.6A10078" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2010 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.6.0" UPTO_BIN_PRODUCT_VERSION="5.2.6.0" LINK_DATE="03/19/2010 21:13:32" UPTO_LINK_DATE="03/19/2010 21:13:32" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="clist2000.exe" SIZE="64000" CHECKSUM="0x43393D43" BIN_FILE_VERSION="5.2.4.0" BIN_PRODUCT_VERSION="5.2.4.0" PRODUCT_VERSION="v5.2.4" FILE_DESCRIPTION="TMS320C2000 C Source Interlister v5.2.4" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.4" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.4.0" UPTO_BIN_PRODUCT_VERSION="5.2.4.0" LINK_DATE="12/13/2009 15:28:57" UPTO_LINK_DATE="12/13/2009 15:28:57" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="dem2000.exe" SIZE="78848" CHECKSUM="0xCC05B641" BIN_FILE_VERSION="5.2.4.0" BIN_PRODUCT_VERSION="5.2.4.0" PRODUCT_VERSION="v5.2.4" FILE_DESCRIPTION="TMS320C2000 C++ Demangler v5.2.4" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.4" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.4.0" UPTO_BIN_PRODUCT_VERSION="5.2.4.0" LINK_DATE="12/13/2009 15:28:45" UPTO_LINK_DATE="12/13/2009 15:28:45" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="dis2000.exe" SIZE="110592" CHECKSUM="0xA18CAFBA" BIN_FILE_VERSION="5.2.4.0" BIN_PRODUCT_VERSION="5.2.4.0" PRODUCT_VERSION="v5.2.4" FILE_DESCRIPTION="TMS320C2000 COFF Disassembler v5.2.4" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.4" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.4.0" UPTO_BIN_PRODUCT_VERSION="5.2.4.0" LINK_DATE="12/13/2009 15:28:49" UPTO_LINK_DATE="12/13/2009 15:28:49" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="embed2000.exe" SIZE="512512" CHECKSUM="0x96163054" BIN_FILE_VERSION="5.2.4.0" BIN_PRODUCT_VERSION="5.2.4.0" PRODUCT_VERSION="v5.2.4" FILE_DESCRIPTION="TMS320C2000 Embed Utility v5.2.4" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.4" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.4.0" UPTO_BIN_PRODUCT_VERSION="5.2.4.0" LINK_DATE="12/13/2009 15:32:36" UPTO_LINK_DATE="12/13/2009 15:32:36" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="hex2000.exe" SIZE="770560" CHECKSUM="0x5D46468A" BIN_FILE_VERSION="5.2.4.0" BIN_PRODUCT_VERSION="5.2.4.0" PRODUCT_VERSION="v5.2.4" FILE_DESCRIPTION="TMS320C2000 Hex Converter v5.2.4" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.4" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.4.0" UPTO_BIN_PRODUCT_VERSION="5.2.4.0" LINK_DATE="12/13/2009 15:35:01" UPTO_LINK_DATE="12/13/2009 15:35:01" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="ilk2000.exe" SIZE="168960" CHECKSUM="0xC64457D2" BIN_FILE_VERSION="5.2.4.0" BIN_PRODUCT_VERSION="5.2.4.0" PRODUCT_VERSION="v5.2.4" FILE_DESCRIPTION="TMS320C2000 C/C++ File Merge v5.2.4" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.4" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.4.0" UPTO_BIN_PRODUCT_VERSION="5.2.4.0" LINK_DATE="12/13/2009 15:29:13" UPTO_LINK_DATE="12/13/2009 15:29:13" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="libinfo2000.exe" SIZE="627200" CHECKSUM="0x1BFA500B" BIN_FILE_VERSION="5.2.4.0" BIN_PRODUCT_VERSION="5.2.4.0" PRODUCT_VERSION="v5.2.4" FILE_DESCRIPTION="TMS320C2000 Library Information Archiver v5.2.4" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.4" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.4.0" UPTO_BIN_PRODUCT_VERSION="5.2.4.0" LINK_DATE="12/13/2009 15:34:01" UPTO_LINK_DATE="12/13/2009 15:34:01" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="lnk2000.exe" SIZE="1619456" CHECKSUM="0xDDFC43E2" BIN_FILE_VERSION="5.2.4.0" BIN_PRODUCT_VERSION="5.2.4.0" PRODUCT_VERSION="v5.2.4" FILE_DESCRIPTION="TMS320C2000 Linker v5.2.4" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.4" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.4.0" UPTO_BIN_PRODUCT_VERSION="5.2.4.0" LINK_DATE="12/13/2009 15:50:07" UPTO_LINK_DATE="12/13/2009 15:50:07" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="mk2000.exe" SIZE="73728" CHECKSUM="0x16B81729" BIN_FILE_VERSION="5.2.4.0" BIN_PRODUCT_VERSION="5.2.4.0" PRODUCT_VERSION="v5.2.4" FILE_DESCRIPTION="TMS320C2000 Library Builder v5.2.4" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.4" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.4.0" UPTO_BIN_PRODUCT_VERSION="5.2.4.0" LINK_DATE="12/13/2009 15:28:55" UPTO_LINK_DATE="12/13/2009 15:28:55" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="nm2000.exe" SIZE="541696" CHECKSUM="0x850537F0" BIN_FILE_VERSION="5.2.4.0" BIN_PRODUCT_VERSION="5.2.4.0" PRODUCT_VERSION="v5.2.4" FILE_DESCRIPTION="TMS320C2000 Name Utility v5.2.4" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.4" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.4.0" UPTO_BIN_PRODUCT_VERSION="5.2.4.0" LINK_DATE="12/13/2009 15:32:55" UPTO_LINK_DATE="12/13/2009 15:32:55" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="ofd2000.exe" SIZE="716800" CHECKSUM="0xBB5477D8" BIN_FILE_VERSION="5.2.4.0" BIN_PRODUCT_VERSION="5.2.4.0" PRODUCT_VERSION="v5.2.4" FILE_DESCRIPTION="TMS320C2000 Object File Display v5.2.4" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.4" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.4.0" UPTO_BIN_PRODUCT_VERSION="5.2.4.0" LINK_DATE="12/13/2009 15:33:49" UPTO_LINK_DATE="12/13/2009 15:33:49" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="opt2000.exe" SIZE="2040832" CHECKSUM="0x4BD050A2" BIN_FILE_VERSION="5.2.4.0" BIN_PRODUCT_VERSION="5.2.4.0" PRODUCT_VERSION="v5.2.4" FILE_DESCRIPTION="TMS320C2000 C/C++ Optimizer v5.2.4" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.4" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.4.0" UPTO_BIN_PRODUCT_VERSION="5.2.4.0" LINK_DATE="12/13/2009 15:37:08" UPTO_LINK_DATE="12/13/2009 15:37:08" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="plink2000.exe" SIZE="351232" CHECKSUM="0x633A5D81" BIN_FILE_VERSION="5.2.4.0" BIN_PRODUCT_VERSION="5.2.4.0" PRODUCT_VERSION="v5.2.4" FILE_DESCRIPTION="TMS320C2000 Post Link Optimizer v5.2.4" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.4" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.4.0" UPTO_BIN_PRODUCT_VERSION="5.2.4.0" LINK_DATE="12/13/2009 15:30:11" UPTO_LINK_DATE="12/13/2009 15:30:11" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="strip2000.exe" SIZE="520704" CHECKSUM="0x3722753" BIN_FILE_VERSION="5.2.4.0" BIN_PRODUCT_VERSION="5.2.4.0" PRODUCT_VERSION="v5.2.4" FILE_DESCRIPTION="TMS320C2000 Strip Utility v5.2.4" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.4" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.4.0" UPTO_BIN_PRODUCT_VERSION="5.2.4.0" LINK_DATE="12/13/2009 15:33:11" UPTO_LINK_DATE="12/13/2009 15:33:11" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="xref2000.exe" SIZE="530944" CHECKSUM="0x9A51632B" BIN_FILE_VERSION="5.2.4.0" BIN_PRODUCT_VERSION="5.2.4.0" PRODUCT_VERSION="v5.2.4" FILE_DESCRIPTION="TMS320C2000 XREF Utility v5.2.4" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.4" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.4.0" UPTO_BIN_PRODUCT_VERSION="5.2.4.0" LINK_DATE="12/13/2009 15:33:09" UPTO_LINK_DATE="12/13/2009 15:33:09" VER_LANGUAGE="Englisch (USA) [0x409]" />
</EXE>
<EXE NAME="ntdll.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
    <MATCHING_FILE NAME="ntdll.dll" SIZE="740864" CHECKSUM="0x1E776169" BIN_FILE_VERSION="5.1.2600.3520" BIN_PRODUCT_VERSION="5.1.2600.3520" PRODUCT_VERSION="5.1.2600.3520" FILE_DESCRIPTION="DLL für NT-Layer" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Betriebssystem Microsoft® Windows®" FILE_VERSION="5.1.2600.3520 (xpsp_sp2_qfe.090206-1239)" ORIGINAL_FILENAME="ntdll.dll" INTERNAL_NAME="ntdll.dll" LEGAL_COPYRIGHT="© Microsoft Corporation. Alle Rechte vorbehalten." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xBBE9E" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.3520" UPTO_BIN_PRODUCT_VERSION="5.1.2600.3520" LINK_DATE="02/09/2009 10:00:58" UPTO_LINK_DATE="02/09/2009 10:00:58" VER_LANGUAGE="Deutsch (Deutschland) [0x407]" />
</EXE>
<EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
    <MATCHING_FILE NAME="kernel32.dll" SIZE="1059840" CHECKSUM="0xF704C86B" BIN_FILE_VERSION="5.1.2600.3541" BIN_PRODUCT_VERSION="5.1.2600.3541" PRODUCT_VERSION="5.1.2600.3541" FILE_DESCRIPTION="Client-DLL für Windows NT-Basis-API" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Betriebssystem Microsoft® Windows®" FILE_VERSION="5.1.2600.3541 (xpsp_sp2_gdr.090321-1320)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="© Microsoft Corporation. Alle Rechte vorbehalten." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x107569" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.3541" UPTO_BIN_PRODUCT_VERSION="5.1.2600.3541" LINK_DATE="03/21/2009 14:20:10" UPTO_LINK_DATE="03/21/2009 14:20:10" VER_LANGUAGE="Deutsch (Deutschland) [0x407]" />
</EXE>
</DATABASE>

    Does this help?

  • in reply to StephanS
    Prodigy 165 points

    Same here - still crashes.

    Here are the dialogs:

     

    And the error report:

    5126.2e40_appcompat.txt 
    <?xml version="1.0" encoding="UTF-16"?>
<DATABASE>
<EXE NAME="cl2000.exe" FILTER="GRABMI_FILTER_PRIVACY">
    <MATCHING_FILE NAME="abs2000.exe" SIZE="525824" CHECKSUM="0x8AD6E89" BIN_FILE_VERSION="5.2.2.0" BIN_PRODUCT_VERSION="5.2.2.0" PRODUCT_VERSION="v5.2.2" FILE_DESCRIPTION="TMS320C2000 Absolute Lister v5.2.2" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.2" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.2.0" UPTO_BIN_PRODUCT_VERSION="5.2.2.0" LINK_DATE="07/22/2009 01:35:35" UPTO_LINK_DATE="07/22/2009 01:35:35" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="ac2000.exe" SIZE="1360384" CHECKSUM="0x3B4E06D8" BIN_FILE_VERSION="5.2.2.0" BIN_PRODUCT_VERSION="5.2.2.0" PRODUCT_VERSION="v5.2.2" FILE_DESCRIPTION="TMS320C2000 C/C++ Parser v5.2.2" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.2" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.2.0" UPTO_BIN_PRODUCT_VERSION="5.2.2.0" LINK_DATE="07/22/2009 01:37:09" UPTO_LINK_DATE="07/22/2009 01:37:09" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="ar2000.exe" SIZE="518656" CHECKSUM="0x9D98FAF9" BIN_FILE_VERSION="5.2.2.0" BIN_PRODUCT_VERSION="5.2.2.0" PRODUCT_VERSION="v5.2.2" FILE_DESCRIPTION="TMS320C2000 Archiver v5.2.2" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.2" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.2.0" UPTO_BIN_PRODUCT_VERSION="5.2.2.0" LINK_DATE="07/22/2009 01:35:33" UPTO_LINK_DATE="07/22/2009 01:35:33" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="asm2000.exe" SIZE="1291264" CHECKSUM="0x740C148D" BIN_FILE_VERSION="5.2.2.0" BIN_PRODUCT_VERSION="5.2.2.0" PRODUCT_VERSION="v5.2.2" FILE_DESCRIPTION="TMS320C2000 Assembler v5.2.2" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.2" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.2.0" UPTO_BIN_PRODUCT_VERSION="5.2.2.0" LINK_DATE="07/22/2009 01:45:09" UPTO_LINK_DATE="07/22/2009 01:45:09" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="bti2000.dll" SIZE="118784" CHECKSUM="0xCA366BEB" BIN_FILE_VERSION="2.4.0.15" BIN_PRODUCT_VERSION="3.3.0.0" PRODUCT_VERSION="3, 3, 0, 0" FILE_DESCRIPTION="CCS C2000 BTI Driver" COMPANY_NAME="Texas Instruments Inc." PRODUCT_NAME="Code Composer Studio" FILE_VERSION="2, 4, 0, 15" ORIGINAL_FILENAME="BTI2000.DLL" INTERNAL_NAME="BTI2000.DLL" LEGAL_COPYRIGHT="Copyright © 1994-2006 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="2.4.0.15" UPTO_BIN_PRODUCT_VERSION="3.3.0.0" LINK_DATE="05/22/2009 00:13:26" UPTO_LINK_DATE="05/22/2009 00:13:26" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="cg2000.exe" SIZE="1892864" CHECKSUM="0x2107BE9C" BIN_FILE_VERSION="5.2.2.0" BIN_PRODUCT_VERSION="5.2.2.0" PRODUCT_VERSION="v5.2.2" FILE_DESCRIPTION="TMS320C2000 C/C++ Codegen v5.2.2" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.2" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.2.0" UPTO_BIN_PRODUCT_VERSION="5.2.2.0" LINK_DATE="07/22/2009 01:57:54" UPTO_LINK_DATE="07/22/2009 01:57:54" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="cl2000.exe" SIZE="574464" CHECKSUM="0x642E8C57" BIN_FILE_VERSION="5.2.6.0" BIN_PRODUCT_VERSION="5.2.6.0" PRODUCT_VERSION="v5.2.6A10078" FILE_DESCRIPTION="TMS320C2000 C/C++ Compiler v5.2.6A10078" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.6A10078" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2010 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.6.0" UPTO_BIN_PRODUCT_VERSION="5.2.6.0" LINK_DATE="03/19/2010 21:13:32" UPTO_LINK_DATE="03/19/2010 21:13:32" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="cl430.exe" SIZE="552448" CHECKSUM="0x82A9FA94" BIN_FILE_VERSION="3.2.4.0" BIN_PRODUCT_VERSION="3.2.4.0" PRODUCT_VERSION="v3.2.4A10078" FILE_DESCRIPTION="MSP430 C/C++ Compiler v3.2.4A10078" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="MSP430 Compiler Tools" FILE_VERSION="v3.2.4A10078" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 2003-2010 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="3.2.4.0" UPTO_BIN_PRODUCT_VERSION="3.2.4.0" LINK_DATE="03/19/2010 21:15:03" UPTO_LINK_DATE="03/19/2010 21:15:03" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="clist2000.exe" SIZE="64000" CHECKSUM="0x43393D43" BIN_FILE_VERSION="5.2.2.0" BIN_PRODUCT_VERSION="5.2.2.0" PRODUCT_VERSION="v5.2.2" FILE_DESCRIPTION="TMS320C2000 C Source Interlister v5.2.2" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.2" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.2.0" UPTO_BIN_PRODUCT_VERSION="5.2.2.0" LINK_DATE="07/22/2009 01:32:15" UPTO_LINK_DATE="07/22/2009 01:32:15" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="dem2000.exe" SIZE="78848" CHECKSUM="0xCC05B641" BIN_FILE_VERSION="5.2.2.0" BIN_PRODUCT_VERSION="5.2.2.0" PRODUCT_VERSION="v5.2.2" FILE_DESCRIPTION="TMS320C2000 C++ Demangler v5.2.2" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.2" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.2.0" UPTO_BIN_PRODUCT_VERSION="5.2.2.0" LINK_DATE="07/22/2009 01:32:43" UPTO_LINK_DATE="07/22/2009 01:32:43" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="dis2000.exe" SIZE="110592" CHECKSUM="0xA18CAFBA" BIN_FILE_VERSION="5.2.2.0" BIN_PRODUCT_VERSION="5.2.2.0" PRODUCT_VERSION="v5.2.2" FILE_DESCRIPTION="TMS320C2000 COFF Disassembler v5.2.2" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.2" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.2.0" UPTO_BIN_PRODUCT_VERSION="5.2.2.0" LINK_DATE="07/22/2009 01:33:37" UPTO_LINK_DATE="07/22/2009 01:33:37" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="embed2000.exe" SIZE="512512" CHECKSUM="0x96163054" BIN_FILE_VERSION="5.2.2.0" BIN_PRODUCT_VERSION="5.2.2.0" PRODUCT_VERSION="v5.2.2" FILE_DESCRIPTION="TMS320C2000 Embed Utility v5.2.2" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.2" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.2.0" UPTO_BIN_PRODUCT_VERSION="5.2.2.0" LINK_DATE="07/22/2009 01:37:30" UPTO_LINK_DATE="07/22/2009 01:37:30" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="hex2000.exe" SIZE="770048" CHECKSUM="0x41A0F929" BIN_FILE_VERSION="5.2.2.0" BIN_PRODUCT_VERSION="5.2.2.0" PRODUCT_VERSION="v5.2.2" FILE_DESCRIPTION="TMS320C2000 Hex Converter v5.2.2" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.2" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.2.0" UPTO_BIN_PRODUCT_VERSION="5.2.2.0" LINK_DATE="07/22/2009 01:39:41" UPTO_LINK_DATE="07/22/2009 01:39:41" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="ilk2000.exe" SIZE="168960" CHECKSUM="0xC64457D2" BIN_FILE_VERSION="5.2.2.0" BIN_PRODUCT_VERSION="5.2.2.0" PRODUCT_VERSION="v5.2.2" FILE_DESCRIPTION="TMS320C2000 C/C++ File Merge v5.2.2" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.2" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.2.0" UPTO_BIN_PRODUCT_VERSION="5.2.2.0" LINK_DATE="07/22/2009 01:34:25" UPTO_LINK_DATE="07/22/2009 01:34:25" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="libinfo2000.exe" SIZE="627200" CHECKSUM="0x1BFA500B" BIN_FILE_VERSION="5.2.2.0" BIN_PRODUCT_VERSION="5.2.2.0" PRODUCT_VERSION="v5.2.2" FILE_DESCRIPTION="TMS320C2000 Library Information Archiver v5.2.2" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.2" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.2.0" UPTO_BIN_PRODUCT_VERSION="5.2.2.0" LINK_DATE="07/22/2009 01:38:28" UPTO_LINK_DATE="07/22/2009 01:38:28" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="lnk2000.exe" SIZE="1617920" CHECKSUM="0xF8CE6ECF" BIN_FILE_VERSION="5.2.2.0" BIN_PRODUCT_VERSION="5.2.2.0" PRODUCT_VERSION="v5.2.2" FILE_DESCRIPTION="TMS320C2000 Linker v5.2.2" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.2" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.2.0" UPTO_BIN_PRODUCT_VERSION="5.2.2.0" LINK_DATE="07/22/2009 01:54:28" UPTO_LINK_DATE="07/22/2009 01:54:28" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="mk2000.exe" SIZE="73728" CHECKSUM="0x16B81729" BIN_FILE_VERSION="5.2.2.0" BIN_PRODUCT_VERSION="5.2.2.0" PRODUCT_VERSION="v5.2.2" FILE_DESCRIPTION="TMS320C2000 Library Builder v5.2.2" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.2" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.2.0" UPTO_BIN_PRODUCT_VERSION="5.2.2.0" LINK_DATE="07/22/2009 01:34:23" UPTO_LINK_DATE="07/22/2009 01:34:23" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="nm2000.exe" SIZE="541696" CHECKSUM="0x850537F0" BIN_FILE_VERSION="5.2.2.0" BIN_PRODUCT_VERSION="5.2.2.0" PRODUCT_VERSION="v5.2.2" FILE_DESCRIPTION="TMS320C2000 Name Utility v5.2.2" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.2" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.2.0" UPTO_BIN_PRODUCT_VERSION="5.2.2.0" LINK_DATE="07/22/2009 01:38:11" UPTO_LINK_DATE="07/22/2009 01:38:11" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="ofd2000.exe" SIZE="716800" CHECKSUM="0xBB5477D8" BIN_FILE_VERSION="5.2.2.0" BIN_PRODUCT_VERSION="5.2.2.0" PRODUCT_VERSION="v5.2.2" FILE_DESCRIPTION="TMS320C2000 Object File Display v5.2.2" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.2" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.2.0" UPTO_BIN_PRODUCT_VERSION="5.2.2.0" LINK_DATE="07/22/2009 01:38:59" UPTO_LINK_DATE="07/22/2009 01:38:59" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="opt2000.exe" SIZE="2039808" CHECKSUM="0x5FF7F77B" BIN_FILE_VERSION="5.2.2.0" BIN_PRODUCT_VERSION="5.2.2.0" PRODUCT_VERSION="v5.2.2" FILE_DESCRIPTION="TMS320C2000 C/C++ Optimizer v5.2.2" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.2" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.2.0" UPTO_BIN_PRODUCT_VERSION="5.2.2.0" LINK_DATE="07/22/2009 01:39:59" UPTO_LINK_DATE="07/22/2009 01:39:59" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="plink2000.exe" SIZE="351232" CHECKSUM="0xCA41C843" BIN_FILE_VERSION="5.2.2.0" BIN_PRODUCT_VERSION="5.2.2.0" PRODUCT_VERSION="v5.2.2" FILE_DESCRIPTION="TMS320C2000 Post Link Optimizer v5.2.2" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.2" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.2.0" UPTO_BIN_PRODUCT_VERSION="5.2.2.0" LINK_DATE="07/22/2009 01:35:52" UPTO_LINK_DATE="07/22/2009 01:35:52" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="strip2000.exe" SIZE="520704" CHECKSUM="0x3722753" BIN_FILE_VERSION="5.2.2.0" BIN_PRODUCT_VERSION="5.2.2.0" PRODUCT_VERSION="v5.2.2" FILE_DESCRIPTION="TMS320C2000 Strip Utility v5.2.2" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.2" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.2.0" UPTO_BIN_PRODUCT_VERSION="5.2.2.0" LINK_DATE="07/22/2009 01:38:22" UPTO_LINK_DATE="07/22/2009 01:38:22" VER_LANGUAGE="Englisch (USA) [0x409]" />
    <MATCHING_FILE NAME="xref2000.exe" SIZE="530944" CHECKSUM="0x9A51632B" BIN_FILE_VERSION="5.2.2.0" BIN_PRODUCT_VERSION="5.2.2.0" PRODUCT_VERSION="v5.2.2" FILE_DESCRIPTION="TMS320C2000 XREF Utility v5.2.2" COMPANY_NAME="Texas Instruments Incorporated" PRODUCT_NAME="TMS320C2000 Compiler Tools" FILE_VERSION="v5.2.2" INTERNAL_NAME="Code Generation Tools" LEGAL_COPYRIGHT="Copyright © 1996-2009 Texas Instruments" VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x10004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="5.2.2.0" UPTO_BIN_PRODUCT_VERSION="5.2.2.0" LINK_DATE="07/22/2009 01:38:24" UPTO_LINK_DATE="07/22/2009 01:38:24" VER_LANGUAGE="Englisch (USA) [0x409]" />
</EXE>
<EXE NAME="ntdll.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
    <MATCHING_FILE NAME="ntdll.dll" SIZE="714752" CHECKSUM="0xC695BA95" BIN_FILE_VERSION="5.1.2600.5755" BIN_PRODUCT_VERSION="5.1.2600.5755" PRODUCT_VERSION="5.1.2600.5755" FILE_DESCRIPTION="NT Layer DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="5.1.2600.5755 (xpsp_sp3_gdr.090206-1234)" ORIGINAL_FILENAME="ntdll.dll" INTERNAL_NAME="ntdll.dll" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xBC674" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.5755" UPTO_BIN_PRODUCT_VERSION="5.1.2600.5755" LINK_DATE="02/09/2009 12:10:48" UPTO_LINK_DATE="02/09/2009 12:10:48" VER_LANGUAGE="Englisch (USA) [0x409]" />
</EXE>
<EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
    <MATCHING_FILE NAME="kernel32.dll" SIZE="989696" CHECKSUM="0x2D998938" BIN_FILE_VERSION="5.1.2600.5781" BIN_PRODUCT_VERSION="5.1.2600.5781" PRODUCT_VERSION="5.1.2600.5781" FILE_DESCRIPTION="Windows NT BASE API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="5.1.2600.5781 (xpsp_sp3_gdr.090321-1317)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xFE572" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.5781" UPTO_BIN_PRODUCT_VERSION="5.1.2600.5781" LINK_DATE="03/21/2009 14:06:58" UPTO_LINK_DATE="03/21/2009 14:06:58" VER_LANGUAGE="Englisch (USA) [0x409]" />
</EXE>
</DATABASE>

    Best regards,

    Malte

  • in reply to Malte Krebs
    TI__Expert 6550 points

    Thank you for this information.  This rules out one area in the shell.  After talking this over with one of my colleagues there a some other memory related issues that I'm going to investigate further and work on a fix in the shell.

  • in reply to ThomasS
    Genius 4026 points

    The newest C2000 cgtools 5.2.5 are still crashing.

    We are actually living with the modified 5.2.4 version posted somewhere above.

    Are there some news regarding this issue?

  • in reply to StephanS
    TI__Expert 6550 points

    We are still working on additional changes to the shell.  So the issue is still in progress.

  • in reply to ThomasS
    Genius 4026 points

    Just as an update:

    The newest C2000 cgtools 5.2.6 are also crashing.

  • in reply to ThomasS
    Prodigy 50 points

    May I suggest that the label "Verified Answer" be removed from this issue since it is misleading?  Thanks!

    I am quite anxious to see this issue resolved since it is ends up absorbing a lot of time.  In my case, I'm using CCS v3.3.82.13, and, initially, cgtools v6.1.9.  My target is a custom board with a set of 6203s.  The TI tools are on a Windows XP Professional PC v2002 with SP3.  The PC is an HP with AMD Phenom 9600B, Quad-Core Processor, 2.29 GHz, 1.75 GB of RAM and Physical Address Extension.

    The problem appeared when I installed cgtools v6.1.13 a couple of days before v6.1.14 appeared in the Update Advisor list.  I have a couple of CCS projects and a bunch that are just spin-offs from those two, i.e., all similar to the original two.  The first project is moderately mature and stable.  It has no serious speed or size requirements (and because we inherited it and it is missing a volatile qualifier somewhere, or something similar, we are able to use only the Debug branch of it).  It is compiled with:

    -g -rtti -pdsw225 -fg -fr"$(Proj_dir)\..\Debug" -fs"$(Proj_dir)\..\Debug" -i"$(Proj_dir)\..\HPU\bin\include" -i"$(Proj_dir)\..\HPU\include" -i"$(Proj_dir)\..\HPU\fsm\include" -i"$(Proj_dir)\..\HPU\hal\include" -i"$(Proj_dir)\..\HPU\utilities\include" -i"$(Proj_dir)\..\HPU\dc\include" -i"$(Proj_dir)\..\common\include" -d"_DEBUG" -d"CHIP_6203" -d"Env_UseCSL" -mv6200

    and linked with:

     -q -a -c -m"$(Proj_dir)\..\Debug\hpuDaq.map" -o"$(Proj_dir)\..\Debug\hpuDaq.out" -w -x -i"$(Proj_dir)\..\Debug" -l"hpuLib.lib"

    This project was building fine for a long time now, but with the appearence of the problem the only way to get an executeable is to incrementally build 3 or more times.

    The second project has severe speed requirements.  It is not as mature, but at the stage where I'm trying to learn and apply optimization techniques.  Part of that is fiddling with the compiler switches and the different compilers.  I've therefore got cgtools v6.1.9, v6.1.11, v6.0.8, v6.0.25 (not sure when one should choose the 6.1.x vs 6.0.x series, but I saw somewhere that 6.0.x might give a faster result), v6.1.13 and now 6.1.14 installed.  It is compiled with:

    -k -s -pm -pdr -pdv -pdsw225 -pden -pds403 -pds195 -pds885 -pds238 -al -as -os -on2 -o3 -fr"$(Proj_dir)\..\Release" -fs"$(Proj_dir)\..\Release" -i"$(Proj_dir)\..\DPU\dataflow\include" -i"$(Proj_dir)\..\DPU\asm" -i"$(Proj_dir)\..\DPU\handlers\include" -i"$(Proj_dir)\..\DPU\builder\include" -i"$(Proj_dir)\..\common\include" -d"CHIP_6203" -mw -ms1 -mf1 -mv6200

    and linked with:

    -q -a -c -m"$(Proj_dir)\..\Release\thruput.map" -o"$(Proj_dir)\..\Release\thruput.out" --verbose_diagnostics -w -x -i"$(Proj_dir)\..\Release" -l"dpuLib.lib"

    although, as I indicated, there are some variations in the switches from time to time.

    The build seems to crash at random times.  The crash doesn't seem to favor any particular source file or build step.  Sometimes it's during compilation, sometimes its during linking, assembly or optimization.  There seem to be 4 versions of the crash, which I believe are all related:

    • Bomb box with "...Compiler vX.X.X has encountered a problem and needs to close" (BTW, does Send Error Report really go to Microsoft or to TI?)
    • "INTERNAL ERROR: ...cl6x experienced a segmentation fault..."
    • the normal link time is exceeded by a large amount of time, reporting <Optimizing>, <Generating>, <Assembling> over and over again until it either crashes or completes
    • "error: must link using compiler shell to complete template instantiations"

    The first case happens the most frequently.  When I use Component Manager to switch to one (any) of the other installed compilers, I get the same behaviour.  Whatever the install of v6.1.13 did affected all versions. 

    Another symptom I have seen is that warnings normally printed in black are printed in red partway through the build.  They are then counted as errors when the build completes.  This may be unrelated, but perhaps its relevant.  No .out file is created in such cases.  Retrying the build will often succeed, with the same warning printed out, but this time only in black and counted as such.

    It sure smacks of a resource starvation issue, not necessarily heap.  I don't believe it has anything to do with ntdll.dll since it hasn't changed.  I also don't believe it has anything to do with my code since it stays constant during the build retries.  Reinstalling Windows presumably works because it cleans out the registery.  Is there a way to capture and verify the portions of the registery that affect the TI tools?

    If there is anything I can do to help get to the bottom of this, please don't hesitate to let me know.

    Thanks,
                  Ric

  • in reply to Ric Claus
    Prodigy 20 points

    I too have been dealing with this issue.  I have a relatively small project but I cannot rebuild without several crashes in the cl2000 (v5.2.5) compiler.  I would like to lend some support for the idea that there is perhaps something in the registry that causes it.  I had everything installed with the C2000 version of the CCS tools and everything worked fine.  I needed to be able to build for a C6000 target, so I uninstalled all of the tools, reinstalled the full Platinum CCS v3.3 and ever since I have been stuck with this issue.

    On a related note, there are no problems when building for the c6000, only the projects that use the c2000 compiler.

    I cannot rebuild this machine even if I wanted to (and I sure don't) so that "solution" is not available to me.

    Any help would be greatly appreciated.

    Danny

  • in reply to Daniel Allen
    TI__Expert 6550 points

    Attached are alpha builds of the following shells.  I believe these may prevent the reported shell crashes.  I do not have a root cause of the problem, although after many weeks I believe that this issue is caused by a bug in either the Microsoft ntdll.dll library or the Microsoft compiler.  Please feel free to test these shell executables and report results.  If successful, these changes will be included in the next compiler updates of these releases.

    The attached file ti_shell_alpha_5-12-10.zip contains:

    1. cl2000_5-2-7A10132.zip - alpha version of 5.2.7 cl2000.exe

    2. cl430_4-3-4A10132.zip - alpha version of 4.3.4 cl430.exe

    3. cl470_4-6-4A10132.zip - alpha version of 4.6.4 cl470.exe

    4. cl6x_6.1.15A10132.zip - alpha version of 6.1.15 cl6x.exe

    ti_shell_alpha_5-12-10.zip
  • in reply to ThomasS
    Prodigy 20 points

    For the first time in a few weeks, I just rebuilt my entire project in one continuous build (twice1).  I guess I picked the right day to complain!  Thank you for your help.

  • in reply to ThomasS
    Expert 2040 points

    Hi ThomasS,

    I did build my project about 20 times without any crash with your 5.2.7 cl2000.exe.

    Before, it was not possible for me to build the whole project without crash (ok, perhaps once, but never twice).

    Thank you for support!

    Roger

  • in reply to Roger Périat
    Genius 4026 points

    Roger said:

    I did build my project about 20 times without any crash with your 5.2.7 alpha cl2000.exe.

    Before, it was not possible for me to build the whole project without crash (ok, perhaps once, but never twice).

    Roger

    The same here. It works fine, without a crash. Thank you!

  • in reply to ThomasS
    Prodigy 140 points

    Hi Thomas,

    I also had problems with a crashing compiler (cl430). With the alpha version of 4.3.4.cl430.exe the compiler didn't crash anymore! Thanks.

    Regards,

    Norbert