• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 492 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.

about link NDK libaries issue

brenden lai
Intellectual 380 points
Other Parts Discussed in Thread: SYSBIOS

Hi all , 

      I am new to sysbios , I have some ndk link lib issue . I am using mcusdk_1_00_00_68 , target platform is Cortex-M3 CCS versio 5.2.0.00069

. Somehow  , I need to rebuild ndk , that let me confuse . 

      I refer http://processors.wiki.ti.com/index.php/Rebuilding_The_NDK_Core_Using_Gmake to build ndk .below is the command

gmake -f ndk.mak XDC_INSTALL_DIR=C:\ti\xdctools_3_23_03_53 ti.targets.arm.elf.M3=C:\ti\ccsv5\tools\compiler\tms470_4.9.1

and found  the aem3 file is generated which prove build scuess! but when i install package is fail !  below is the command 

gmake -f ndk.mak install-packages

      1. aem3 files need to pack to a libary?(like libc.a or driverlib-cm3.lib)

      2. I check CCS file search path , there are not include NDK path . Why I  can use NDK in my project ? what RTSC do ? Below is build message 


**** Build of configuration Debug for project test_NDK2 ****

C:\ti\ccsv5\utils\bin\gmake -k all
'Building file: ../empty.cfg'
'Invoking: XDCtools'
"C:/ti/xdctools_3_23_03_53/xs" --xdcpath="C:/ti/mcusdk_1_00_00_68/packages;C:/ti/mcusdk_1_00_00_68/products/bios_6_33_04_39/packages;C:/ti/mcusdk_1_00_00_68/products/ipc_1_24_02_27/packages;C:/ti/mcusdk_1_00_00_68/products/ndk_2_21_01_38/packages;C:/ti/mcusdk_1_00_00_68/products/uia_1_01_01_14/packages;C:/ti/mcusdk_1_00_00_68/products/xdctools_3_23_04_60/packages;C:/ti/ccsv5/ccs_base;C:/ti/mcusdk_1_00_00_68/products/ndk_2_21_01_38_custom/packages;" xdc.tools.configuro -o configPkg -t ti.targets.arm.elf.M3 -p ti.platforms.stellaris:LM3S9D96 -r release -c "C:/ti/ccsv5/tools/compiler/tms470_4.9.1" "../empty.cfg"
making package.mak (because of package.bld) ...
generating interfaces for package configPkg (because package/package.xdc.inc is older than package.xdc) ...
configuring empty.xem3 from package/cfg/empty_pem3.cfg ...
remark: No frequency info found for CPU timestamp. See ti.uia.runtime.LogSync module for help on how to provide this info for System Analyzer.
clem3 package/cfg/empty_pem3.c ...
'Finished building: ../empty.cfg'
' '
'Building file: ../DK_LM3S9D96.c'
'Invoking: ARM Compiler'
"C:/ti/ccsv5/tools/compiler/tms470_4.9.1/bin/cl470" -mv7M3 --code_state=16 --abi=eabi -me -g --include_path="C:/ti/ccsv5/tools/compiler/tms470_4.9.1/include" --include_path="C:/ti/mcusdk_1_00_00_68/products/ndk_2_21_01_38/packages/ti/ndk/inc/tools" --include_path="C:/ti/mcusdk_1_00_00_68/products/StellarisWare_9107" --gcc --define=PART_LM3S9D96 --define=INCLUDE_NIMU_CODE --define=TARGET_IS_TEMPEST_RB1 --diag_warning=225 --display_error_number --gen_func_subsections=on --preproc_with_compile --preproc_dependency="DK_LM3S9D96.pp" --cmd_file="./configPkg/compiler.opt" "../DK_LM3S9D96.c"
'Finished building: ../DK_LM3S9D96.c'
' '
'Building file: ../empty.c'
'Invoking: ARM Compiler'
"C:/ti/ccsv5/tools/compiler/tms470_4.9.1/bin/cl470" -mv7M3 --code_state=16 --abi=eabi -me -g --include_path="C:/ti/ccsv5/tools/compiler/tms470_4.9.1/include" --include_path="C:/ti/mcusdk_1_00_00_68/products/ndk_2_21_01_38/packages/ti/ndk/inc/tools" --include_path="C:/ti/mcusdk_1_00_00_68/products/StellarisWare_9107" --gcc --define=PART_LM3S9D96 --define=INCLUDE_NIMU_CODE --define=TARGET_IS_TEMPEST_RB1 --diag_warning=225 --display_error_number --gen_func_subsections=on --preproc_with_compile --preproc_dependency="empty.pp" --cmd_file="./configPkg/compiler.opt" "../empty.c"
"../empty.c", line 115: warning #179-D: variable "hRt" was declared but never referenced
"../empty.c", line 143: warning #179-D: variable "dev_table" was declared but never referenced
"../empty.c", line 146: warning #179-D: variable "num_device" was declared but never referenced
"../empty.c", line 190: warning #179-D: variable "index" was declared but never referenced
"../empty.c", line 233: warning #552-D: variable "IFType" was set but never used
"../empty.c", line 239: warning #552-D: variable "status" was set but never used
'Finished building: ../empty.c'
' '
'Building file: ../task.c'
'Invoking: ARM Compiler'
"C:/ti/ccsv5/tools/compiler/tms470_4.9.1/bin/cl470" -mv7M3 --code_state=16 --abi=eabi -me -g --include_path="C:/ti/ccsv5/tools/compiler/tms470_4.9.1/include" --include_path="C:/ti/mcusdk_1_00_00_68/products/ndk_2_21_01_38/packages/ti/ndk/inc/tools" --include_path="C:/ti/mcusdk_1_00_00_68/products/StellarisWare_9107" --gcc --define=PART_LM3S9D96 --define=INCLUDE_NIMU_CODE --define=TARGET_IS_TEMPEST_RB1 --diag_warning=225 --display_error_number --gen_func_subsections=on --preproc_with_compile --preproc_dependency="task.pp" --cmd_file="./configPkg/compiler.opt" "../task.c"
'Finished building: ../task.c'
' '
'Building target: test_NDK2.out'
'Invoking: ARM Linker'
"C:/ti/ccsv5/tools/compiler/tms470_4.9.1/bin/cl470" -mv7M3 --code_state=16 --abi=eabi -me -g --gcc --define=PART_LM3S9D96 --define=INCLUDE_NIMU_CODE --define=TARGET_IS_TEMPEST_RB1 --diag_warning=225 --display_error_number --gen_func_subsections=on -z --stack_size=256 -m"test_NDK2.map" --heap_size=0 -i"C:/ti/ccsv5/tools/compiler/tms470_4.9.1/lib" -i"C:/ti/ccsv5/tools/compiler/tms470_4.9.1/include" --reread_libs --warn_sections --display_error_number --rom_model -o "test_NDK2.out" -l"./configPkg/linker.cmd" "./task.obj" "./empty.obj" "./DK_LM3S9D96.obj" -l"libc.a" -l"C:/ti/mcusdk_1_00_00_68/products/StellarisWare_9107/driverlib/ccs-cm3/Debug/driverlib-cm3.lib" "../DK_LM3S9D96.cmd"
<Linking>
'Finished building target: test_NDK2.out'
' '

**** Build Finished ****

      3.I use the NDK under MCUSDK . after rebuild NDK ,How to let MCUSDK include rebuilded NDK version ? Do i need rebuild MCUSDK , too ? 

Brenden

 

       

  • 0
    TI__Mastermind 21645 points

    Hi Brenden,

    It looks like you are not pointing to the newly built NDK tree. Here are the steps that you can follow to point to the rebuilt tree before rebuilding your project:

    - Open CCS and select the application project you want to rebuild.

    - Right click on your project and choose Properties.

    - In CCS General category of the Properties dialog, choose the RTSC tab.

    - Click the Add button next to Product and Repositories tab.

    - Choose Select repository from file-system, and browse to the "packages" directory of the location where you copied and rebuilt NDK. For example the location may be:

    C:\ti\mcusdk_1_00_00_68\products\copy_ndk_2_21_00_32\packages on Windows

    - Choose the Order tab and select the repository you just added. Click the Up button to move the repository to the top. The idea is to make sure the new repository is placed higher than mcu sdk's ndk installation so it is searched first. For more details on this you can refer Section 4.3 (on pg 33) of mcusdk_1_00_00_68\docs\spruhd4a.pdf

    - Click OK to apply these changes to the project.

    - You may now rebuild your project. It should build with the rebuilt version of NDK.

    Best,

    Ashish

  • 0 in reply to Ashish Kapania
    TI__Guru* 96960 points

    Brenden,

    Out of curiousity, why did you rebuild the NDK?

    Todd

  • 0 in reply to Ashish Kapania
    Intellectual 380 points

    Thanks Ashish , 

    I will try this !

    TOD , 

          I want to include NIMU code , See http://e2e.ti.com/support/embedded/bios/f/355/t/211139.aspx

    Brenden