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.

TDA4VH-Q1: Windows C7x Codegen Tools Crash

Part Number: TDA4VH-Q1
Other Parts Discussed in Thread: TDA4VH

Tool/software:

I am trying to build the C7x DSPLIB_add test project under Windows and the cl7x.exe application crashes during the linker phase of the build. The error reported is the Microsoft Visual C++ Runtime Library assertion failure shown in the screenshot attached below. What can cause this?

  • Hi,

    Could you please provide the steps you have taken? I will attempt to debug the issue on my side following the same procedure.

    Regards,
    Sivadeep

  • Hi Sivadeep. The CCS project itself is not important to me and it is my failed attempt at trying to replicate the DSPLIB_add_test results from TDA4VH DSPLIB v10.01.00.04. This will never work because the DSPLIB project has dependencies on scripts called from cmake that are difficult to reproduce within Windows CCS. That being said, I wanted to share this project with the C7x compiler team because it generates an assertion failure during the linker phase, which I assume we never want to happen. I will need to do some work to make local copies of the header files so that the project is self contained and makes it to the linker stage where the crash happens. I will work on this and will provide a ZIP to you offline from e2e.

  • It is likely you are experiencing a problem similar to the ones described in this forum thread, or this forum thread.

    Thanks and regards,

    -George

  • Thank you for the attention on this George. The project I saw this on uses source files that built without errors under Linux in a cmake build, so I'm not sure its exactly like those other examples. That being said, I know there are problems with my CCS project because I'm missing some files that were generated by scripts in the Linux cmake build. So I will just assume the code is doing something bad with strings to cause that linker crash. Sorry I assumed we would want to debug the usecase for the sake of future linker revisions, since assertion failures shouldn't happen, but its not important to me. We can close this thread. 

  • Just updating this for others that may encounter a similar problem. We figured out that the compiler was crashing because we copied-pasted pre-processor macros from a Word document which was introducing characters that the link does not support. The same can happen for the compiler predefined symbols and even though the CCS GUI displays the characters normally, the codegen tools crash when these characters are processed. See below screenshots to get the full meaning.

  • Hi,

    Thanks for the update. Closing this thread as discussed above.

    Regards,
    Sivadeep