• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 53 subscribers
  • Views 1411 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.

CCS/TMS320F28379S: Problem with build clean

Ralf Koester
Expert 1400 points
Part Number: TMS320F28379S

Tool/software: Code Composer Studio

Hi,
I held 2 build configurations, one for FLASH, and one for RAM, this for debugging!
I checked now all the settings between FLASH and RAM, they are nearly the same, apart from optimization and of course a different cmd-file.
Now I can build with FLASH configuration, but it will not start with RAM configuration.
THe error message is:
"Errors occurred during the build. Errors running builder 'CDT Builder' on project 'VVK1'. java.lang.NullPointerException"
In the cosole this appears:
**** Clean-only build of configuration F2833x_RAM for project VVK1 ****
"C:\\ti\\ccsv6\\utils\\bin\\gmake" -k clean
gmake: *** No rule to make target 'clean'.
**** Build Finished ****
Any idea?
br Ralf

  • 0
    TI__Guru**** 451281 points
    Hi Ralf,
    What is the exact CCS version you are using (I know you are using CCSv6, but which CCSv6 version)?

    Would it be possible to provide your project? At minimum, it may be enough to provide just your project metadata files (.*project)

    Thanks
    ki
  • 0 in reply to Ki
    Expert 1400 points

    Hi ki,

    sorry for not telling exact CCS version, it's CCSv6.1.3!

    I attached the complete project!

    br Ralf

    092-0070.zip

  • 0 in reply to Ralf Koester
    TI__Guru**** 451281 points
    Hi Ralf,
    Thank you for providing a complete test case! It is so helpful to be able to have a complete reproducible test case to help us debug the issue.

    I was able to reproduce the issue with my 6.1.3 environment. However, when trying it out with CCSv6.2.0 and CCSv7, the issue does not exist. It is likely that it was a known issue that was fixed. I suggest updating your CCS version

    Note that there is one known issue that you may encounter when you try to build your project in CCSv6.2/7.0.. You may get some build error about XDAIS. If that happens, please use the workaround described by Aarti in the thread below:
    e2e.ti.com/.../2046257

    Thanks
    ki
  • 0 in reply to Ki
    Expert 1400 points

    Hi Ki-Soo,

    I've updated the CCS to version 6.2.0 and I've got the error with XDAIS as promised.

    But I installed the xdais version 7.24.00.04 and now it is working so far.

    Thanks!

    By the way:

    I found it a little bit strange to install xdais, because the downloaded file was twice zipped, and there was no installing procedure, only to unpack was the task.

    I unpacked the file system and copied it in the C:\Ti\ folder. Because I did not found an update offer in the CCS update window.

    CCS did not find the new tool, although I close the CCS.

    Only when I openden another workspace CCS recognized the new tool and finalized the installation process.

  • 0 in reply to Ralf Koester
    TI__Guru**** 451281 points

    Ralf Koester said:
    But I installed the xdais version 7.24.00.04 and now it is working so far.

    Good to hear. You didn't have to install XDAIS, you could have just removed the dependency from the project since it is not really needed. But installing XDAIS will do the trick also

    Ralf Koester said:
    I found it a little bit strange to install xdais

    Thanks for the feedback on your installation troubles. We will look into making this a better process.

    Ralf Koester said:

    CCS did not find the new tool, although I close the CCS.

    Only when I openden another workspace CCS recognized the new tool and finalized the installation process.


    It could be that you disabled the auto-discovery feature when launching CCS with the old workspace. You can always force a rediscovery via the button below:

    Thanks

    ki