• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 55 subscribers
  • Views 1098 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.

MCSA Tutorial Build Errors with CCSv5.1 M6

MikeH
Guru 15580 points

I am running CCSv5.1 M6 and have run into the following build error when trying to build the project.

 

**** Build of configuration Debug for project MCSA Tutorial 1 ****

 

C:\ccs\ccsv5\utils\bin\gmake -k all 

'Building target: MCSA Tutorial 1.out'

'Invoking: C6000 Linker'

"C:/ccs/ccsv5/tools/compiler/c6000/bin/cl6x" -mv6600 -g --diag_warning=225 --abi=eabi -z -m"MCSA Tutorial 1.map" --warn_sections -i"C:/ccs/ccsv5/tools/compiler/c6000/lib" -i"C:/ccs/ccsv5/tools/compiler/c6000/include" --reread_libs --rom_model -o "MCSA Tutorial 1.out" -l"./configPkg/linker.cmd"  "./tutorial1d.obj" "./tutorial1c.obj" "./tutorial1b.obj" "./tutorial1a.obj" "./main.obj" -l"libc.a" 

<Linking>

 

 undefined                    first referenced                                                                    

  symbol                          in file                                                                         

 ---------                    ----------------                                                                    

 xdc_runtime_Diags_setMask__E ./tutorial1c.obj                                                                    

 xdc_runtime_Startup_exec__E  C:\ccs2\xdctools_3_22_02_27\packages\ti\targets\rts6000\lib\boot.ae66<autoinit.oe66>

 

 

error: unresolved symbols remain

>> Compilation failure

error: errors encountered during linking; "MCSA Tutorial 1.out" not built

gmake: *** [MCSA Tutorial 1.out] Error 1

gmake: Target `all' not remade because of errors.

 

**** Build Finished ****

Can someone give me a hand with this?

thx

MikeH

 

  • 0
    Genius 4375 points

    Hi Mike,

    Could you tell me the version of BIOS, IPC, XDCTools and UIA that you are using to build your project?  I'd like to try to reproduce your problem.

    Thanks,

    Shreyas

  • 0 in reply to Shreyas Oppanthaya
    Guru 15580 points

    Shreyas,

    I downloaded an installed the complete M6 install package which included the following:

      BIOS 5 5.41.10.36 com.ti.bios.5.41.win32.feature.group

      BIOS 6 6.32.2.39 com.ti.bios.6.32.win32.feature.group

      IPC 1.23.2.27 com.ti.ipc.1.23.win32.feature.group

      IPC (Multicore and I/O) 1.23.2.27 com.ti.ipc_1.23.feature.group

      XDCTools 3.22.1.21 com.ti.xdctools.3.22.win32.feature.group

    DVT UIA 3.1.0.201106101153

    Thx,

    MikeH

     

  • 0 in reply to MikeH
    Genius 4375 points

    Hi Mike,

    I tried reproducing your problem using CCS 5.1.0M6 along with its target content (same version as yours) with no success.  I was able to build the application just fine (see below).     Did you modify your project in any way after passing through the wizard?  Did you try re-generating the project to see if this problem can be reliably reproduced?

    Regards,
    Shreyas

     
    **** Build of configuration Debug for project MCSA Tutorial 1 ****

    /home/shreyas/ccs5/ccsv5/utils/bin/gmake -k all
    Building file: ../mcsaTutorial1.cfg
    Invoking: XDCtools
    "/db/rtree/products/xdcprod/xdcprod-o27/product/Linux/xdctools_3_22_02_27//xs" --xdcpath="/home/shreyas/ccs5/uia_1_00_01_17/packages;/home/shreyas/ccs5/bios_6_32_02_39/packages;/home/shreyas/ccs5/ipc_1_23_02_27/packages;" xdc.tools.configuro -o configPkg -t ti.targets.elf.C66 -p ti.platforms.evm6678 -r debug -c "/home/shreyas/ccs5/ccsv5/tools/compiler/c6000" "../mcsaTutorial1.cfg"
    making package.mak (because of package.bld) ...
    generating interfaces for package configPkg (because package/package.xdc.inc is older than package.xdc) ...
    configuring mcsaTutorial1.pe66 from package/cfg/mcsaTutorial1_pe66.cfg ...
    cle66 package/cfg/mcsaTutorial1_pe66.c ...
    Finished building: ../mcsaTutorial1.cfg
     
    Building file: ../main.c
    Invoking: C6000 Compiler
    "/home/shreyas/ccs5/ccsv5/tools/compiler/c6000/bin/cl6x" -mv6600 -g --include_path="/home/shreyas/ccs5/ccsv5/tools/compiler/c6000/include" --diag_warning=225 --abi=eabi --preproc_with_compile --preproc_dependency="main.pp" --cmd_file="./configPkg/compiler.opt"  "../main.c"
    Finished building: ../main.c
     
    Building file: ../tutorial1a.c
    Invoking: C6000 Compiler
    "/home/shreyas/ccs5/ccsv5/tools/compiler/c6000/bin/cl6x" -mv6600 -g --include_path="/home/shreyas/ccs5/ccsv5/tools/compiler/c6000/include" --diag_warning=225 --abi=eabi --preproc_with_compile --preproc_dependency="tutorial1a.pp" --cmd_file="./configPkg/compiler.opt"  "../tutorial1a.c"
    Finished building: ../tutorial1a.c
     
    Building file: ../tutorial1b.c
    Invoking: C6000 Compiler
    "/home/shreyas/ccs5/ccsv5/tools/compiler/c6000/bin/cl6x" -mv6600 -g --include_path="/home/shreyas/ccs5/ccsv5/tools/compiler/c6000/include" --diag_warning=225 --abi=eabi --preproc_with_compile --preproc_dependency="tutorial1b.pp" --cmd_file="./configPkg/compiler.opt"  "../tutorial1b.c"
    Finished building: ../tutorial1b.c
     
    Building file: ../tutorial1c.c
    Invoking: C6000 Compiler
    "/home/shreyas/ccs5/ccsv5/tools/compiler/c6000/bin/cl6x" -mv6600 -g --include_path="/home/shreyas/ccs5/ccsv5/tools/compiler/c6000/include" --diag_warning=225 --abi=eabi --preproc_with_compile --preproc_dependency="tutorial1c.pp" --cmd_file="./configPkg/compiler.opt"  "../tutorial1c.c"
    Finished building: ../tutorial1c.c
     
    Building file: ../tutorial1d.c
    Invoking: C6000 Compiler
    "/home/shreyas/ccs5/ccsv5/tools/compiler/c6000/bin/cl6x" -mv6600 -g --include_path="/home/shreyas/ccs5/ccsv5/tools/compiler/c6000/include" --diag_warning=225 --abi=eabi --preproc_with_compile --preproc_dependency="tutorial1d.pp" --cmd_file="./configPkg/compiler.opt"  "../tutorial1d.c"
    Finished building: ../tutorial1d.c
     
    Building target: MCSA Tutorial 1.out
    Invoking: C6000 Linker
    "/home/shreyas/ccs5/ccsv5/tools/compiler/c6000/bin/cl6x" -mv6600 -g --diag_warning=225 --abi=eabi -z -m"MCSA Tutorial 1.map" --warn_sections -i"/home/shreyas/ccs5/ccsv5/tools/compiler/c6000/lib" -i"/home/shreyas/ccs5/ccsv5/tools/compiler/c6000/include" --reread_libs --rom_model -o "MCSA Tutorial 1.out" -l"./configPkg/linker.cmd"  "./tutorial1d.obj" "./tutorial1c.obj" "./tutorial1b.obj" "./tutorial1a.obj" "./main.obj" -l"libc.a"
    <Linking>
    Finished building target: MCSA Tutorial 1.out
     

    **** Build Finished ****

  • 0 in reply to MikeH
    TI__Intellectual 1270 points

    I'd like to point out that the XDC version in the error and the XDC version you thought you were using aren't the same.  There is probably some hard-coded path or -- if you imported the project via CCS, there is almost 0 chance of getting it to configure correctly  unless you use the exact version numbers that were using to generate the project before importing -- you are better off just copying the source files and rebuilding it (though that might be difficult for some projects with linked resources).

  • 0 in reply to Tim Wentz
    Guru 15580 points

    Gents,

    I don't know what to tell you. I merely followed the TI Wiki Tutorials for MCSA after downloading and installing CCSv5.1 M6. The project comes from the templates distributed with CCS. I did not modify the project in any way. It will not build without errors show previously. 

    However, I *do* have two version of ccsv5.1. Since the M6 (.06000) release generated a known ".dll not found error",  I was given the opportunity to download ccsv5.1.06019, which I did and which includes xdctools_3_22_02_27. What is interesting is that, when I build with .06000 the XDCtools path is 

    --xdcpath="C:/ccs/uia_1_00_01_16_eng/packages;" xdc.tools.configuro -o configPkg -t ti.targets.elf.C66 -p ti.platforms.evm6678 -r whole_program -c "C:/ccs/ccsv5/tools/compiler/c6000"

    and the XDCtools listed in the config in Help says:

      XDCTools 3.22.1.21 com.ti.xdctools

    ...but the error in the build console says

    <Linking>

     

     undefined                    first referenced                                                                    

      symbol                          in file                                                                         

     ---------                    ----------------                                                                    

     xdc_runtime_Diags_setMask__E ./tutorial1c.obj                                                                    

     

     xdc_runtime_Startup_exec__E  C:\ccs2\xdctools_3_22_02_27\packages\ti\targets\rts6000\lib\boot.ae66<autoinit.oe66>

    which is the path to v5.1.06019.

    I am confused....

     

  • 0 in reply to MikeH
    Genius 4375 points

    I think I found the source of your problem.  You are using the 'whole_program' build profile which has been deprecated in BIOS 6.32, IPC 1.23, and XDCTools 3.22.  The UIA examples need to be fixed to choose either 'release' or 'debug' as the build profile in the project example wizard.   The 'release' profile now offers performance similar to 'whole_program[_debug]' without the long build times associated with 'WPD'.   I suggest switching to either 'debug' or 'release' in your project's RTSC configuration (see the screenshot below). 

    Since the WPD build profile has been depricated, you should see a build warning while building an applicaiton that uses this profile.  I'll investigate why this warning didn't appear as I reproduced your problem.

    Regards,

    Shreyas

  • 0 in reply to Shreyas Oppanthaya
    Genius 4375 points

    FYI, this was fixed in later releases of UIA.   The 'release' profile is now the default for the UIA examples.

    Regards,

    Shreyas

  • 0 in reply to Shreyas Oppanthaya
    Guru 15580 points

    Shreyas Prasad said:
    You are using the 'whole_program' build profile which has been deprecated in BIOS 6.32, IPC 1.23, and XDCTools 3.22.  The UIA examples need to be fixed to choose either 'release' or 'debug' as the build profile in the project example wizard.   The 'release' profile now offers performance similar to 'whole_program[_debug]' without the long build times associated with 'WPD'.   I suggest switching to either 'debug' or 'release' in your project's RTSC configuration (see the screenshot below). 

    BINGO!! That did it! No errors, no warnings!

    Thanks!

    MikeH

     

  • 0 in reply to MikeH
    Guru 15580 points

    FYI, problem still exists in M7 release. Default is still set at "whole program".