• Locked Locked
  • Replies 1 reply
  • Subscribers 51 subscribers
  • Views 609 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.

(Bug report) CCS6.1.3 throws NullPointerException when building another configuration of the same project

Benedikt
Prodigy 210 points

Problem: I get a null pointer exception during a Build Configuration step.

How to reproduce:

  1. Use a new installation of CCS 6.1.3 and a new/empty workspace directory, get ISDK 6.1.1.2 from TI
  2. Open CCS, do "Import CCS Projects..." with the starterware/board project from ISDK.
    This CCS comes with 8 configurations. They appear to have been built in the delivery state, see below.
  3. Pick the default config "am335x_release" selected in ISDK installation at the beginning, build it.
    => I am getting an error popup, saying "Errors occurred during the build. Errors running builder 'CDT Builder' on project 'board.' java.lang.NullPointerException"
  4. Delete the 8 build directories (through CCS IDE) "am335x_boot_debug", ..., "am43xx_release", so that no one is left.
  5. Build the configuration "am335x_release" again.
    => This works for me.
  6. Again, mark the project and build "am335x_debug".
    => Here, I am getting the same error popup
  7. Delete the 2 build directories just created by the preceding steps.
  8. Build the configuration "am335x_debug"
    => Now this works for me.
  9. Build "am335x_release" afterwards, and you get the same error popup again.

I consider this a bug, because I would like to build several library configurations (such as with and without debug symbols) side-by-side.

As it appears to me, the error might be somewhere in the library projects delivered with ISDK or in the CCS toolchain (including plugins and Eclipse).

Is it a known problem? Are there any workarounds other than creating a separate workspace for every additional configuration to be built?

Edit:

Details on my build environment:

  • CCS 6.1.3.00034
  • Windows 7 (64 Bit) Service Pack 1
  • TI__Guru**** 173310 points

    Benedikt,

    This was a bug in CCS 6.1.3 (tracking # CCSIDE-2879) that is fixed in CCS 6.2. Could you please install CCS 6.2 (download from here) and let us know if you still encounter the problem? You can even keep CCS 6.1.3 and 6.2 side-by-side if you wish, by installing them to different directories.