• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 556 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.

Debug assertion failed and can the CCS v6.1.2 work in 64-bit Win10 OS?

Will Gao
Intellectual 2335 points

Hi experts, 

There are two questions from the customer, and I need your help.  

The first question is that the "debug assertion failed" window jumped out when they built their project. However, there is no non-ASCII characters in paths, compiler option, account name and TMP/TEMP environment variables. Please give some suggestions to debug this problem. The CCS version that they use is v6.1.2, and the compiler version is v6.1.3. 

The second question, is the CCS v6.1.2 supported by 64-bit Win10 OS? 

Thanks

-Will

  • 0
    TI__Guru**** 483141 points
    Will Gao said:
    The first question is that the "debug assertion failed" window jumped out when they built their project. However, there is no non-ASCII characters in paths, compiler option, account name and TMP/TEMP environment variables. Please give some suggestions to debug this problem. The CCS version that they use is v6.1.2, and the compiler version is v6.1.3. 

    Hello, can they provide a screenshot of the exact error? have the provide a screenshot of the error and the CCS IDE. Also what device are they using?

    Will Gao said:
    The second question, is the CCS v6.1.2 supported by 64-bit Win10 OS? 

    CCSv6.1.3 is the first version that is officially supported on Windows 10. Technically they should be using at least that version. Note that CCSv6 is very old in general and unsupported. They really should think of updating their CCS environment to something more recent if it is possible.

    Thanks

    ki

  • 0 in reply to Ki
    TI__Intellectual 2335 points

    Hi Ki,

    I don't know why this customer insists on using this version of CCS. But actually, some computers don't have the "debug assertion failed" problem even they use CCSv6.1.2 in Win10 OS. So could you please tell me the detail features which not supported by Win10? 

    On the other hand, I am asking the customer to provide the screenshot of the "debug assertion failed" error. And I will give feedback to you as soon as possible. 

    Thanks

    -Will

  • 0 in reply to Will Gao
    TI__Guru**** 483141 points
    Will Gao said:
    I don't know why this customer insists on using this version of CCS. But actually, some computers don't have the "debug assertion failed" problem even they use CCSv6.1.2 in Win10 OS. So could you please tell me the detail features which not supported by Win10? 

    The issue is that versions 6.1.2 (and earlier) were never officially tested on Windows 10. Hence it is unknown which features are not supported on Windows 10. I have run 6.1.2 on Windows 10 without issue so I am fairly confident that Windows 10 is not the issue here. But the customer should understand that old versions on CCS are unsupported.

    Will Gao said:
    On the other hand, I am asking the customer to provide the screenshot of the "debug assertion failed" error. And I will give feedback to you as soon as possible. 

    Thank you

    ki