• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 96 subscribers
  • Views 640 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.

Failed to build UBL project with CCSv5

Qmax
Expert 2280 points

Other Parts Discussed in Thread: AM1808, OMAP-L138

Hi

I'm trying to build UBL_SPI_MEM project which cames with flash-utils-03.21.00.04.tar.gz with CCS 5.1.0.09000, following the instructions of the wiki.
I have imported the project with some minor problems, but then the build for AM1808 fails.

First of all, an old compiler version was specified in the project, so I have modified it to the one available, TI v.4.9.1.
Then, some undeclared variables where used in the include paths: EXT_ROOT__UBL_SPI_MEM and XDAIS_CG_ROOT.
I've added them into Properties -> CCS Build -> Environment section, setting EXT_ROOT__UBL_SPI_MEM to the root path of extracted flash-utils-03.21.00.04 and XDAIS_CG_ROOT to C:\Program Files\Texas Instruments\xdais_7_10_00_06.

Is it correct?

Now, when I try to build the project I have the following fatal error (and several minor warnings):

...
"C:/flash-utils-03.21.00.04/OMAP-L138/CCS/UBL_ARM/UBL.cmd"
<Linking>
error #10016-D: --retain=*(.selfcopy) not supported when producing TI-COFF
   output files
fatal error #10011: cannot continue with specified options; aborting

>> Compilation failure
gmake: *** [C:\flash-utils-03.21.00.04/OMAP-L138/CCS/UBL_ARM/SPI_MEM/UBL_AM1808_SPI_MEM.out] Error 1
gmake: Target `all' not remade because of errors.

**** Build Finished ****


Any suggestion?

I've followed exactly wiki instructions, so I would have expected to import and build the project with no issue, nor required changes to it...

Thanks in advance.
Best regards, Max

  • 0
    Expert 2280 points

    Just an additional note: if I try to import the project with option "Copy into workspace", an error message says it cannot write .project file.

    Hope anybody can help, thanks.

  • 0 in reply to Qmax
    Expert 2280 points

    This is an update on the issue and its solution, maybe can help someone else.

    I've found that the very first problem is the fact that .project files (for all projects inside flash-utils tar.gz) are considered hidden by Windows and this prevents them to be written, at least by some applications (I can modify them with notepad but not using wordpad). I do not understand details of these winsozz-related issues, neither want to. But after changing files status from hidden to normal, I've been able to import projects into CCSv5.

    Now, using "Copy into workspace" does not do exactly what I expect to: not all files are copied (c source files are not). Moreover importing in this way breaks building process: at least post-build batch files have hard-coded path and will not work.

    So the solution is to import without "Copy into workspace" option: the build seems to complete with success and several warnings...

    EXT_ROOT__UBL_SPI_MEM is set into project from macros.ini

    But XDAIS_CG_ROOT is still missing, but not fatal for build process.

    Also compiler version is not up-to-date (TI v4.6.4 instead of TI v4.9.1).