• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 54 subscribers
  • Views 1482 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.

Windows Command Processor Has Stopped Working When Building from ccs5

Peter Van Oudenaren
Prodigy 20 points

Other Parts Discussed in Thread: OMAPL138

I'm trying to build an example project from CCS5 OMAPL138.

Whenever I build from CCS5 when gmake -k all runs a Windows dialogue opens and Says

"Windows Command Processor Has Stopped Working"

I've experimented running "gmake -k all" from command line from inside the build\css4\Debug directory and the build succeeds.

Any ideas ? 

  • 0
    TI__Guru**** 482071 points

    Hi Peter,

    Peter Van Oudenaren said:
    I'm trying to build an example project from CCS5 OMAPL138.

    What exact version of CCSv5 are you using?

    Peter Van Oudenaren said:

    I've experimented running "gmake -k all" from command line from inside the build\css4\Debug directory and the build succeeds.

    I'm not quite sure what you did here. Did you run the gmake utility that came with v4 on your v5 project? Or did you simply run 'gmake -k all' on your project, using the same gmake that comes with v5, from the command-line?

  • 0 in reply to Ki
    Prodigy 20 points

    Thanks for your response. The problem is resolved, it turned out that the workstation was infected with the "Windows Command Processor" malware which didn't seem to effect most programs but the malware itself crashed (I think) when invoking gmake from CCS5.5. That may also have caused problems with the installation since the USB drivers for the debuggers weren't properly installed by the CCS installation.

    Thanks again.

  • 0 in reply to Peter Van Oudenaren
    TI__Guru**** 482071 points

    Thanks for the update and glad to hear you have resolved the issue.

    ki