• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 52 subscribers
  • Views 660 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.

CCS/CC2652R: CCS and linking time

cabled
Intellectual 425 points
Part Number: CC2652R

Tool/software: Code Composer Studio

Hi gents,

Am just playing around with the Thread Stack examples for the CC2652R Launchpad. I know it says linking dependencies etc takes a few minutes but its closer to 15 minutes in my case before i can get anything into the board or debugger. Is this normal? Or am I missing something here? 

I've seen some older threads alluding to parallel compilation, which I've already checked is enabled... If anyone has any pointers, it would be greatly appreciated...

Cheers

  • 0
    TI__Guru**** 173310 points

    cabled said:
    I know it says linking dependencies etc takes a few minutes but its closer to 15 minutes in my case before i can get anything into the board or debugger.

    Do you mean that it takes 15 mins to build an example project from the Simplelink SDK? If so, that is certainly unusual.

    Which version of CCS are you using and which example takes that long to build? Is it just one project or do other example projects also take that long to build?

  • 0 in reply to AartiG
    Intellectual 425 points

    Yes, I do mean that it takes 15 minutes to build... so far I've tried pretty much all the Thread examples save the thermostat one... CCS is version 8.1.0.11 on Windows 10 17134. 

    Console steps through all the builds etc then gets to linker, and stops at <Linking> for about 15 minutes. Its not like the rest of the process is lightning fast but the 15 minutes here really makes the whole process dead inefficient...

    Invoking: ARM Linker
    "C:/ti/ccsv8/tools/compiler/ti-cgt-arm_18.1.2.LTS/bin/armcl" -mv7M4 --code_state=16 --float_support=FPv4SPD16 -me -O4 --opt_for_speed=0 --define=OPENTHREAD_CONFIG_FILE='"openthread-config-cc2652-ccs-ftd.h"' --define=OPENTHREAD_PROJECT_CORE_CONFIG_FILE='"openthread-core-cc2652-config-ide.h"' --define=MBEDTLS_CONFIG_FILE='"mbedtls-config-cc2652-ccs.h"' --define=HAVE_CONFIG_H --define=SIMPLELINK_OPENTHREAD_SDK_BUILD=1 --define=SIMPLELINK_OPENTHREAD_CONFIG_FTD=1 --define=SIMPLELINK_OPENTHREAD_CONFIG_CC2652=1 --define=DeviceFamily_CC26X2 -g --c99 --gcc --printf_support=nofloat --diag_warning=225 --diag_warning=255 --diag_wrap=off --display_error_number --gen_func_subsections=on --gen_data_subsections=on --abi=eabi -z -m"cli_ftd_CC26X2R1_LAUNCHXL_tirtos_ccs.map" --heap_size=0 -i"C:/Users/xxxx/workspace_v8/libopenthread_diag_ftd_CC26X2R1_LAUNCHXL_ccs/OptimizeSize" -i"C:/Users/xxxx/workspace_v8/libopenthread_cli_ftd_CC26X2R1_LAUNCHXL_ccs/OptimizeSize" -i"C:/Users/xxxx/workspace_v8/libopenthread_ftd_CC26X2R1_LAUNCHXL_ccs/OptimizeSize" -i"C:/Users/xxxx/workspace_v8/libopenthread_platform_utils_ftd_CC26X2R1_LAUNCHXL_ccs/OptimizeSize" -i"C:/Users/xxxx/workspace_v8/libmbedcrypto_CC26X2R1_LAUNCHXL_ccs/OptimizeSize" -i"C:/ti/simplelink_cc26x2_sdk_2_10_00_44/source" -i"C:/ti/simplelink_cc26x2_sdk_2_10_00_44/kernel/tirtos/packages" -i"C:/ti/ccsv8/tools/compiler/ti-cgt-arm_18.1.2.LTS/lib" --diag_wrap=off --display_error_number --warn_sections --xml_link_info="cli_ftd_CC26X2R1_LAUNCHXL_tirtos_ccs_linkInfo.xml" --rom_model --unused_section_elimination=on -o "cli_ftd_CC26X2R1_LAUNCHXL_tirtos_ccs.out" "./CC26X2R1_LAUNCHXL.obj" "./ccfg.obj" "./cli.obj" "./main.obj" "./otstack.obj" "./otsupport/otrtosapi.obj" "./platform/alarm.obj" "./platform/debug_uart.obj" "./platform/diag.obj" "./platform/misc.obj" "./platform/platform.obj" "./platform/radio.obj" "./platform/random.obj" "./platform/uart.obj" "./platform/crypto/aes_alt.obj" "./platform/crypto/ecjpake_alt.obj" "./platform/crypto/sha256_alt.obj" "./platform/nv/crc.obj" "./platform/nv/nvoctp.obj" "./platform/nv/settings.obj" "../CC26X2R1_LAUNCHXL_TIRTOS.cmd" -l"configPkg/linker.cmd" -llibopenthread_diag_ftd.lib -llibopenthread_cli_ftd.lib -llibopenthread_ftd.lib -llibopenthread_platform_utils_ftd.lib -llibmbedcrypto.lib -l"ti/display/lib/display.aem4f" -l"ti/grlib/lib/ccs/m4f/grlib.a" -l"third_party/spiffs/lib/ccs/m4f/spiffs_cc26xx.a" -l"ti/drivers/rf/lib/rf_multiMode_cc26x2_v1.aem4f" -l"ti/drivers/lib/drivers_cc26x2_v1.aem4f" -l"ti/dpl/lib/dpl_cc26x2_v1.aem4f" -l"ti/devices/cc13x2_cc26x2_v1/driverlib/bin/ccs/driverlib.lib" -llibc.a
    <Linking>

  • 0 in reply to cabled
    TI__Guru**** 173310 points

    I see similar behavior - it stays for about 9 mins in the link step for the cli_ftd project. That project seems to take particularly long time to link, other examples under TI Thread are more in the order of 4-5 mins build time. 

    Unfortunately I do think this is normal as I tried the build with a couple different CCS and compiler versions and got similar results. I would suggest asking in the Bluetooth low energy forum though to confirm, as they create and validate these example projects.

  • 0 in reply to AartiG
    Intellectual 425 points
    hmm ok i'll try that i guess. it does seem to have gotten slightly quicker somehow... or maybe i'm just numb to the time now...
  • 0 in reply to cabled
    TI__Guru**** 173310 points
    Note that it will take the most time during first build and rebuilds. Successive incremental builds should be faster (although it will still have to go through the link step any time a source change is made).