• State Answer Suggested
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 97 subscribers
  • Views 347 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.

UBL for DM355 building failed

Thalib
Intellectual 580 points

Hi,

I want to build UBL for custom board, before that I want to try it on DM355 EVM.

I got the ubl source from ti website and imported it in CCS4.1, When I try to build it. I got the following error.

Can someone help in resolving the build issue.

Regards,

Thalib.

 

<ramtest> Sat Apr 24 11:54:43 2010
Building file: E:/thalib/flash_utils/Common/src/util.c'
'Invoking: Compiler'
"D:/Program Files/Texas Instruments/ccsv4/tools/compiler/tms470/bin/cl470" -mv5e --symdebug:none -O3 --define="UBL_NAND" --include_path="D:/Program Files/Texas Instruments/ccsv4/tools/compiler/tms470/include" --include_path="D:/Program Files/Texas Instruments/xdais_6_25_01_08/packages/ti/xdais" --include_path="../include" --include_path="E:/thalib/flash_utils/Common/arch/arm926ejs/include" --include_path="E:/thalib/flash_utils/Common/ubl/include" --include_path="E:/thalib/flash_utils/Common/gnu/include" --include_path="E:/thalib/flash_utils/DM35x/Common/include" --include_path="E:/thalib/flash_utils/Common/include" --include_path="E:/thalib/flash_utils/Common/drivers/include" --diag_warning=225 -me --abi=eabi --asm_directory="../NAND" --obj_directory="../NAND" --preproc_with_compile --preproc_dependency="util.pp"  "E:/thalib/flash_utils/Common/src/util.c"
"E:/thalib/flash_utils/Common/src/util.c", line 41: warning: function "LOCAL_CalcBitWiseParity" was declared but never referenced
'Finished building: E:/thalib/flash_utils/Common/src/util.c'
' '
'Building target: ../NAND/UBL_DM35x_NAND.out'
'Invoking: Linker'
"D:/Program Files/Texas Instruments/ccsv4/tools/compiler/tms470/bin/cl470" -@ccsLinker.opt -o "../NAND/UBL_DM35x_NAND.out"
<Linking>
warning: creating output section ".cinit" without a SECTIONS specification

 undefined      first referenced
  symbol            in file    
 ---------      ----------------
 __TI_zero_init                

error: unresolved symbols remain
warning: entry-point symbol other than "_c_int00" specified:  "boot"
error: errors encountered during linking; "../NAND/UBL_DM35x_NAND.out" not
   built

>> Compilation failure
D:\Program Files\Texas Instruments\ccsv4\utils\gmake\gmake: *** [../NAND/UBL_DM35x_NAND.out] Error 1
D:\Program Files\Texas Instruments\ccsv4\utils\gmake\gmake: Target `all' not remade because of errors.
Build complete for project UBL

  • 0
    Intellectual 580 points

    I searched some the forum and found some one saying to change the compiler name to arm_v5t_le-gcc and change to DM35x/GNU path and run make, when I did I got the following error.

    DM35x/GNU$ make
    make -C sft all
    make[1]: Entering directory `/home/thalib/src/flash_utils/DM35x/GNU/sft'
    make -C build TYPE=nand
    make[2]: Entering directory `/home/thalib/src/flash_utils/DM35x/GNU/sft/build'
    arm_v5t_le-gcc -c -Os -Wall -ffreestanding -I../../../Common/include -I../../../../Common/include -I../../../../Common/arch/arm926ejs/include -I../../../../Common/sft/include -I../../../../Common/ubl/include -I../../../../Common/drivers/include -I../../../../Common/gnu/include  -DUBL_NAND ../../../../Common/arch/arm926ejs/src/boot.c -o boot_nand.o     
    /tmp/ccxJxxJO.s: Assembler messages:
    /tmp/ccxJxxJO.s:22: Error: bad expression -- `mrc p15,#0,r0,c1,c0,#0'
    /tmp/ccxJxxJO.s:27: Error: bad expression -- `mcr p15,#0,r0,c1,c0,#0'
    make[2]: *** [boot_nand.o] Error 1
    make[2]: Leaving directory `/home/thalib/projects/bellatrix/src/flash_utils/DM35x/GNU/sft/build'
    make[1]: *** [all] Error 2
    make[1]: Leaving directory `/home/thalib/projects/bellatrix/src/flash_utils/DM35x/GNU/sft'
    make: *** [all] Error 2

  • 0 in reply to Thalib
    Intellectual 580 points

    For the abvoe issue. I have solve using the below link. It seems the default tool chain comes with DVSDK is buggy, I downloaded the tool chain from code sorcery and able to build without any problem. and also issue caused with uboot when using MV tool chain. solved with code sorcery

    http://www.mail-archive.com/davinci-linux-open-source@linux.davincidsp.com/msg08330.html