• State TI Thinks Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 102 subscribers
  • Views 1036 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.

Source code DaVinci-PSP-SDK-03.20.00.13 not building

deepak ramegowda
Expert 1465 points
Other Parts Discussed in Thread: OMAP-L137, CCSTUDIO, TPS65023

As per the document provided in the release DaVinci-PSP-SDK-03.20.00.13 in 50 page

For OMAP-L137 (or DA830, AM17xx)
When using CCStudiov3.3:
1. Start CCStudio v3.3.
2. From the menus, choose Project->Open.
3. Browse to the extracted ARM UBL source and open the ubl-omapl1x7.pjt project.
• To build for SPI Flash, select the "Config" option as BOOT_SPI in CCStudio window.
• To build for NAND Flash, select the "Config" option as BOOT_NAND in CCStudio window.
4. From the menus, choose Project->Build. When the build is complete:
• The Intel hex format binary (ubl-xxx.bin) file is generated in the Project Root directory.
• The executable ELF binary (ubl-xxx.out) file is generated in the Project Root directory.
• The Project Root directory is <armubl-install-dir>\ccsv3.3\
5. The files generated by the build procedure, have to be flashed.
• In case of DSP BOOT devices like OMAP-L137 or DA830, the Intel hex format binary file is suitable for
flashing.

when I try building(Build) the project i get an error as attached in the image! But rebuilding (rebuild)the code compiles

I am trying to do this to Check weather the .bin files gets generated or not as specified in the document 

HELP REQUIRED ON THIS!

Thank you

Deepak R

  • 0
    TI__Guru** 116100 points
    Can you please delete the "BOOT_NAND" and "BOOT_SPI" folder and rebuild the project.
    You didn't get any issues while rebuilding right ?
    Then its okay.
  • 0 in reply to Titusrathinaraj Stalin
    Expert 1465 points

    Hi

    Titu

    Thanks for your response

    As specified in the document it should generate the .bin file in the folder with .out. I am not able to find that.I have ubl2bin in that folder but no generation of bin files is happening!

    What to do for this

    nEED HELP !

    Thank you

    Deepak R

  • 0
    Guru 26430 points
    Those programs were developed and built using CCS 3.3. You are using CCS 5.x. The error is probably coming from old .obj files built using CCS 3.3. that CCS 5.x do not like. Build will check the date of existing .obj files. Rebuild will delete the .obj files. As Titus suggests, if rebuild works, it should be okay.

    In another thread, you say that are using a omapl137 digital spectrum kit. If you want to recreate the bin files exactly, you need use the source and tools from the CD-ROM supplied with the kit.
  • 0 in reply to Norman Wong
    Expert 1465 points

    Hi

    Wong

    Thanks for response!

    But my need is to build and generate the .bin file for the ARM ubl  source for our custom board omapl137 !

    I need help on this ......How .bin ARMUBL  get created from source of  davinci and what version .

    kindly let me know how to do this on ccsv5 /6 as its already use in my machine!

    Thank you

    Deepak R

  • 0 in reply to deepak ramegowda
    Guru 26430 points
    I am unsure about your current state. You mention that rebuild works. What are you getting from the rebuild? Are you getting ".out" files? No ".bin" files. The import by CCS 5 of a CCS3.3 project may have dropped the .out to .bin steps. Look in your CCS3 prj file for the command line to convert .out to .bin. Look for hex470 commands.
  • 0 in reply to Norman Wong
    Expert 1465 points

    Hi

    Thanks for your immediate response!

    Yes exactly same issue I am facing I am able to generate the .out file not the .bin file!

    I have attached the logs of rebuilding for reference!

    "C:/ti/ccsv5/tools/compiler/tms470_4.9.5/bin/cl470" -mv5e --abi=ti_arm9_abi -me -O3 -g --include_path="C:/ti/ccsv5/tools/compiler/tms470_4.9.5/include" --include_path="C:/ti/xdais_7_21_01_07/packages/ti/xdais" --include_path="C:/Users/1011467/Desktop/armubl-03.20.00.14.tar/armubl-03.20.00.14/include" --define="UBL_SPI" --define="USE_IN_ROM" --define="CONFIG_MACH_DAVINCI_DA830_EVM" --define="DEVICE_UART2_FOR_DEBUG" --display_error_number --asm_directory=".." --obj_directory=".." --preproc_with_compile --preproc_dependency="ubl.pp" "C:/Users/1011467/Desktop/armubl-03.20.00.14.tar/armubl-03.20.00.14/src/ubl.c"

    'Finished building: C:/Users/1011467/Desktop/armubl-03.20.00.14.tar/armubl-03.20.00.14/src/ubl.c'

    ' '

    'Building file: C:/Users/1011467/Desktop/armubl-03.20.00.14.tar/armubl-03.20.00.14/src/util.c'

    'Invoking: ARM Compiler'

    "C:/ti/ccsv5/tools/compiler/tms470_4.9.5/bin/cl470" -mv5e --abi=ti_arm9_abi -me -O3 -g --include_path="C:/ti/ccsv5/tools/compiler/tms470_4.9.5/include" --include_path="C:/ti/xdais_7_21_01_07/packages/ti/xdais" --include_path="C:/Users/1011467/Desktop/armubl-03.20.00.14.tar/armubl-03.20.00.14/include" --define="UBL_SPI" --define="USE_IN_ROM" --define="CONFIG_MACH_DAVINCI_DA830_EVM" --define="DEVICE_UART2_FOR_DEBUG" --display_error_number --asm_directory=".." --obj_directory=".." --preproc_with_compile --preproc_dependency="util.pp" "C:/Users/1011467/Desktop/armubl-03.20.00.14.tar/armubl-03.20.00.14/src/util.c"

    'Finished building: C:/Users/1011467/Desktop/armubl-03.20.00.14.tar/armubl-03.20.00.14/src/util.c'

    ' '

    'Building target: ../ubl-spi.out'

    'Invoking: ARM Linker'

    "C:/ti/ccsv5/tools/compiler/tms470_4.9.5/bin/cl470" -mv5e --abi=ti_arm9_abi -me -O3 -g --define="UBL_SPI" --define="USE_IN_ROM" --define="CONFIG_MACH_DAVINCI_DA830_EVM" --define="DEVICE_UART2_FOR_DEBUG" --display_error_number --asm_directory=".." --obj_directory=".." -z -m"../ubl-spi.map" -i"C:/ti/ccsv5/tools/compiler/tms470_4.9.5/lib" -i"C:/ti/ccsv5/tools/compiler/tms470_4.9.5/include" -i"C:/Users/1011467/Desktop/Deepak_folder/ubl-omapl1x7" -i"C:/Users/1011467/Desktop/armubl-03.20.00.14.tar/armubl-03.20.00.14/ccsv3.3" --reread_libs --warn_sections --display_error_number -o "../ubl-spi.out" "C:/Users/1011467/Desktop/Deepak_folder/ubl-omapl1x7/util.obj" "C:/Users/1011467/Desktop/Deepak_folder/ubl-omapl1x7/ubl.obj" "C:/Users/1011467/Desktop/Deepak_folder/ubl-omapl1x7/uartboot.obj" "C:/Users/1011467/Desktop/Deepak_folder/ubl-omapl1x7/uart.obj" "C:/Users/1011467/Desktop/Deepak_folder/ubl-omapl1x7/tps65023.obj" "C:/Users/1011467/Desktop/Deepak_folder/ubl-omapl1x7/spiboot.obj" "C:/Users/1011467/Desktop/Deepak_folder/ubl-omapl1x7/spi_mem.obj" "C:/Users/1011467/Desktop/Deepak_folder/ubl-omapl1x7/spi.obj" "C:/Users/1011467/Desktop/Deepak_folder/ubl-omapl1x7/nandboot.obj" "C:/Users/1011467/Desktop/Deepak_folder/ubl-omapl1x7/nand.obj" "C:/Users/1011467/Desktop/Deepak_folder/ubl-omapl1x7/i2c.obj" "C:/Users/1011467/Desktop/Deepak_folder/ubl-omapl1x7/device_nand.obj" "C:/Users/1011467/Desktop/Deepak_folder/ubl-omapl1x7/device.obj" "C:/Users/1011467/Desktop/Deepak_folder/ubl-omapl1x7/debug.obj" "C:/Users/1011467/Desktop/Deepak_folder/ubl-omapl1x7/boot.obj" "C:/Users/1011467/Desktop/armubl-03.20.00.14.tar/armubl-03.20.00.14/ubl.cmd"

    <Linking>

    warning #10247-D: creating output section ".const" without a SECTIONS

    specification

    'Finished building target: ../ubl-spi.out'

    ' '

    C:/ti/ccsv5/utils/bin/gmake --no-print-directory post-build

    "C:/Users/1011467/Desktop/Deepak_folder/ubl-omapl1x7/postBuildStep_BOOT_SPI.bat" PROJECT_ROOT C:/Users/1011467/Desktop/Deepak_folder/ubl-omapl1x7 !

    'hex470.exe' is not recognized as an internal or external command,

    operable program or batch file.

    ' '

    **** Build Finished ****

     

    Thank you

    Deepak R

  • 0 in reply to deepak ramegowda
    Guru 26430 points
    I currently don't have access to a development machine to check for the location of hex470.exe. Check your CCS install directory. Change the postBuild.bat file with proper path.

    That's all I got. Hopefully Titus has a better way to migrate a CCS 3.3 hex470.exe call.
  • 0 in reply to Norman Wong
    Expert 1465 points
    Hi
    Team
    This method holds good for the CCSV5
    Thanks for your support!
    Finally able to get a alternative solution for the building of the ARM.BIN file
    NOTE:the ccsv 5/6/4 sometimes dosent build the .bin bin file so
    kindly make sure you get the .out file first and and check for the hex470.exe in my case path in the installation directory
    and try to build the .bin file from the command prompt
    For example I have added the commands :

    hex470.exe C:\Users\1011467\Desktop\armubl-03.20.00.14.tar\armubl-03.20.00.14\ubl2bin.cmd -o C:\Users\1011467\Desktop\Arm\ubl-omapl1x7\ubl-spi.bin C:\Users\1011467\Desktop\Arm\ubl-omapl1x7\ubl-spi.out

    hex470.exe C:\Users\1011467\Desktop\EVALUATION_BOARD_SOFTWARE\DaVinci-PSP-SDK-03.20.00.13\src\boot-strap\ARM\armubl-03.20.00.13\ubl2bin.cmd -o C:\Users\1011467\Desktop\ARM_2\ubl-omapl1x7\ARM_2.bin C:\Users\1011467\Desktop\ARM_2\ubl-omapl1x7\ubl-spi.out


    Thank you
    Deepak R
  • 0 in reply to deepak ramegowda
    Expert 1465 points
    you can also specify the path
    echo C:\ti\ccsv5\tools\compiler\tms470_4.9.5\hex470.exe %PROJECT_ROOT%\..\ubl2bin.cmd -o %PROJECT_ROOT%\ubl-spi.bin %PROJECT_ROOT%\ubl-spi.out >> temp_postBuildStep_BOOT_SPI.bat in the .bat file